I understand. Unfortunately this machine wasn't turned on frequently so it was running an old kernel and pinpointing the commit is time consuming. Sam Søren Schmidt wrote: > HI > > There havn't been any changes (AFAIK) to the ATA subsystem lately, so > it would help if I could get a pointer to when more precisely it > stopped working ? > > -Søren > > On 31May, 2008, at 22:13 , Sam Leffler wrote: > >> Joe Marcus Clarke wrote: >>> I have a Dell Precision 360 workstation (i386) with an ATA DVD-RW drive >>> and an SATA Seagate drive. After a long time (Feb 14, 2008), I supped >>> -CURRENT, and rebooted. Now the box hangs in what appears to be a >>> probe >>> of the ATA devices. Here are the last few lines of the verbose boot >>> (copied from screen): >>> >>> ata0: identify ch->devices=00000000 >>> ata1: identify ch->devices=00010000 >>> The GEOM class LABEL is already loaded. >>> ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=80 wire >>> acd0: setting PIO4 on ICH5 chip >>> acd0: setting UDMA33 on ICH5 chip >>> acd0: <HL-DT-ST DVD+RW GRA-4120B/F114> CDRW driver at ata1 as master >>> acd0: read 6890KB/s (6890KB/s) write 6890KB/s (6890KB/s), 2048KB >>> buffer, >>> UDMA33 >>> acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet >>> acd0: Writes: CD, CDRW, test write, burnproof >>> acd0: Audio: play, 256 volume levels >>> acd0: Mechanism: ejectable tray, unlocked >>> acd0: Medium: no/blank disc >>> ata2: identify ch->devices=00000000 >>> ata3: identify ch->devices=00000001 >>> >>> That's it. After the DVD drive, the only other ATA device is the >>> SATA-attached Seagate disk which is master on ata3. The previous >>> kernel's verbose boot reported: >>> >>> ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire >>> ad6: 152627MB <Seagate ST3160815AS 3.AAD> at ata3-master SATA150 >>> ad6: 312581808 sectors [310101C/16H/63S] 16 sectors/interrupt 1 depth >>> queue >>> >>> This drive is located on a Promise controller: >>> >>> atapci0: <Promise PDC20375 SATA150 controller> port >>> 0xcc00-0xcc3f,0xcbf0-0xcbff,0xcc80-0xccff mem >>> 0xfe73f000-0xfe73ffff,0xfe740000-0xfe75ffff irq 22 at device 1.0 on >>> pci2 >>> ... >>> ata3: <ATA channel 1> on atapci0 >>> >>> Any ideas? Thanks. >>> >>> >> >> Not really, just "me too". I updated a machine w/ the same >> controller and hit the same issue. >> >> Sam >> >> >> _______________________________________________ >> freebsd-current_at_freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe_at_freebsd.org" >> > > >Received on Sat May 31 2008 - 19:10:54 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:31 UTC