* pata_via refuses to detect one drive
@ 2007-10-17 14:41 Michael Tokarev
2007-10-17 15:50 ` Alan Cox
0 siblings, 1 reply; 5+ messages in thread
From: Michael Tokarev @ 2007-10-17 14:41 UTC (permalink / raw)
To: linux-ide
I tried switching one machine here from old IDE
modules to a new pata subsystem today. And it
failed, for the first time I ever tried this
procedure. Pata_via refuses to recognize one
of the drives.
Here's the dmesg with via82cxxx (2.6.20):
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8233 (rev 02) IDE UDMA100 controller on pci0000:00:11.1
ide0: BM-DMA at 0x3c00-0x3c07, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x3c08-0x3c0f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: Hitachi HDS721680PLAT80, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: Hitachi HDS721680PLAT80, ATA DISK drive
hdd: FX4830T, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
loading module ide-disk
hda: max request size: 512KiB
hda: 160836480 sectors (82348 MB) w/7384KiB Cache, CHS=16383/255/63<6>hda: hw_config=600b
, UDMA(100)
hda: cache flushes supported
hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
hdc: max request size: 512KiB
hdc: 160836480 sectors (82348 MB) w/7384KiB Cache, CHS=16383/255/63, UDMA(33)
hdc: cache flushes supported
hdc: hdc1 hdc2 hdc3 hdc4 < hdc5 hdc6 hdc7 >
(yes, the second IDE cable isn't UDMA one).
And here's the same when booted with pata_via module. 2.6.20
and 2.6.23 behaves the same way:
Oct 17 18:30:59 linux kernel: scsi0 : pata_via
Oct 17 18:30:59 linux kernel: scsi1 : pata_via
Oct 17 18:30:59 linux kernel: ata1: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x00013c00 irq 14
Oct 17 18:30:59 linux kernel: ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x00013c08 irq 15
Oct 17 18:30:59 linux kernel: ata1.00: ATA-7: Hitachi HDS721680PLAT80, P21OA60A, max UDMA/133
Oct 17 18:30:59 linux kernel: ata1.00: 160836480 sectors, multi 16: LBA48
Oct 17 18:30:59 linux kernel: ata1.00: configured for UDMA/100
Oct 17 18:30:59 linux kernel: ata2: port is slow to respond, please be patient (Status 0x80)
Oct 17 18:30:59 linux kernel: ata2: SRST failed (errno=-16)
Oct 17 18:30:59 linux kernel: ata2.01: ATAPI: FX4830T, R02E, max UDMA/33
Oct 17 18:30:59 linux kernel: ata2.01: configured for UDMA/33
Oct 17 18:30:59 linux kernel: scsi 0:0:0:0: Direct-Access ATA Hitachi HDS72168 P21O PQ: 0 ANSI: 5
Oct 17 18:30:59 linux kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Oct 17 18:30:59 linux kernel: ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
Oct 17 18:30:59 linux kernel: res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
Oct 17 18:30:59 linux kernel: ata2: soft resetting port
Oct 17 18:30:59 linux kernel: ata2.01: configured for UDMA/33
Oct 17 18:30:59 linux kernel: ata2: EH complete
Oct 17 18:30:59 linux kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Oct 17 18:30:59 linux kernel: ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
Oct 17 18:30:59 linux kernel: res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
Oct 17 18:30:59 linux kernel: ata2: soft resetting port
Oct 17 18:30:59 linux kernel: ata2.01: configured for UDMA/33
Oct 17 18:30:59 linux kernel: ata2: EH complete
Oct 17 18:30:59 linux kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Oct 17 18:30:59 linux kernel: ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
Oct 17 18:30:59 linux kernel: res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
Oct 17 18:30:59 linux kernel: ata2: soft resetting port
Oct 17 18:30:59 linux kernel: ata2.01: configured for UDMA/33
Oct 17 18:30:59 linux kernel: ata2: EH complete
Oct 17 18:30:59 linux kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
Oct 17 18:30:59 linux kernel: ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in
Oct 17 18:30:59 linux kernel: res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation)
Oct 17 18:30:59 linux kernel: ata2: soft resetting port
Oct 17 18:30:59 linux kernel: ata2.01: configured for UDMA/33
Oct 17 18:30:59 linux kernel: ata2: EH complete
Oct 17 18:30:59 linux kernel: loading module sd_mod
Oct 17 18:30:59 linux kernel: sd 0:0:0:0: [sda] 160836480 512-byte hardware sectors (82348 MB)
Oct 17 18:30:59 linux kernel: sd 0:0:0:0: [sda] Write Protect is off
Oct 17 18:30:59 linux kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Oct 17 18:30:59 linux kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 17 18:30:59 linux kernel: sd 0:0:0:0: [sda] 160836480 512-byte hardware sectors (82348 MB)
Oct 17 18:30:59 linux kernel: sd 0:0:0:0: [sda] Write Protect is off
Oct 17 18:30:59 linux kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Oct 17 18:30:59 linux kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 17 18:30:59 linux kernel: sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
Oct 17 18:30:59 linux kernel: sd 0:0:0:0: [sda] Attached SCSI disk
That's it - no sdb (or should it be sdc?) detected, only sda.
Any ideas?
Thanks.
P.S. By the way, there are two lists - linux-ide@ and linux-scsi@.
Which one should be used to discuss pata- (and sata-) related stuff
like this?
/mjt
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: pata_via refuses to detect one drive 2007-10-17 14:41 pata_via refuses to detect one drive Michael Tokarev @ 2007-10-17 15:50 ` Alan Cox 2007-10-17 18:26 ` Michael Tokarev 0 siblings, 1 reply; 5+ messages in thread From: Alan Cox @ 2007-10-17 15:50 UTC (permalink / raw) To: Michael Tokarev; +Cc: linux-ide > Oct 17 18:30:59 linux kernel: ata2: port is slow to respond, please be patient (Status 0x80) > Oct 17 18:30:59 linux kernel: ata2: SRST failed (errno=-16) So it failed to reset and come back to sanity. > Oct 17 18:30:59 linux kernel: ata2.01: ATAPI: FX4830T, R02E, max UDMA/33 > Oct 17 18:30:59 linux kernel: ata2.01: configured for UDMA/33 > Oct 17 18:30:59 linux kernel: scsi 0:0:0:0: Direct-Access ATA Hitachi HDS72168 P21O PQ: 0 ANSI: 5 > Oct 17 18:30:59 linux kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 > Oct 17 18:30:59 linux kernel: ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in > Oct 17 18:30:59 linux kernel: res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation) This looks like both drives end up trying to be the slave ? Its certainly very vey confused at this point. Interesting it works with the BIOS doing the reset, wonder what the difference is. How are the drives jumpered and does it work with just one of the two present ? Alan ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: pata_via refuses to detect one drive 2007-10-17 15:50 ` Alan Cox @ 2007-10-17 18:26 ` Michael Tokarev 2007-10-17 20:31 ` Alan Cox 0 siblings, 1 reply; 5+ messages in thread From: Michael Tokarev @ 2007-10-17 18:26 UTC (permalink / raw) To: Alan Cox; +Cc: linux-ide Alan Cox wrote: >> Oct 17 18:30:59 linux kernel: ata2: port is slow to respond, please be patient (Status 0x80) >> Oct 17 18:30:59 linux kernel: ata2: SRST failed (errno=-16) > > So it failed to reset and come back to sanity. > >> Oct 17 18:30:59 linux kernel: ata2.01: ATAPI: FX4830T, R02E, max UDMA/33 >> Oct 17 18:30:59 linux kernel: ata2.01: configured for UDMA/33 >> Oct 17 18:30:59 linux kernel: scsi 0:0:0:0: Direct-Access ATA Hitachi HDS72168 P21O PQ: 0 ANSI: 5 >> Oct 17 18:30:59 linux kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 >> Oct 17 18:30:59 linux kernel: ata2.01: cmd a0/00:00:00:00:20/00:00:00:00:00/b0 tag 0 cdb 0x12 data 36 in >> Oct 17 18:30:59 linux kernel: res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation) > > This looks like both drives end up trying to be the slave ? Its certainly > very vey confused at this point. Interesting it works with the BIOS doing > the reset, wonder what the difference is. Not only it works with BIOS, it also works with via82cxxx just fine. hdc: Hitachi HDS721680PLAT80, ATA DISK drive hdc: max request size: 512KiB hdc: 160836480 sectors (82348 MB) w/7384KiB Cache, CHS=16383/255/63, UDMA(33) hdc: cache flushes supported hdc: hdc1 hdc2 hdc3 hdc4 < hdc5 hdc6 hdc7 > hdd: FX4830T, ATAPI CD/DVD-ROM drive hdd: ATAPI 48X CD-ROM drive, 128kB Cache, UDMA(33) # hdparm -i /dev/hdc /dev/hdc: Model=Hitachi HDS721680PLAT80, FwRev=P21OA60A, SerialNo=PV2100Z106Z9EF Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=51 BuffType=DualPortCache, BuffSize=7384kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=160836480 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 *udma2 udma3 udma4 udma5 udma3 udma4 udma5 udma6 AdvancedPM=yes: disabled (255) WriteCache=enabled Drive conforms to: ATA/ATAPI-7 T13 1532D revision 1: ATA/ATAPI-2 ATA/ATAPI-3 ATA/ATAPI-4 ATA/ATAPI-5 ATA/ATAPI-6 ATA/ATAPI-7 # hdparm -i /dev/hdd /dev/hdd: Model=FX4830T, FwRev=R02E, SerialNo= Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic } RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=128kB, MaxMultSect=0 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 *udma2 AdvancedPM=no (both drives are on "plain" IDE cable, second IDE channel). > How are the drives jumpered and does it work with just one of the two > present ? That's an interesting question. The machine is remote, and there's no one on site who's able to check it. I'll try to get reach of it, hopefully it will be soon enough. In any case, it looks like the jumpers are OK, or else it shouldnt work with IDE module as well. /mjt ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: pata_via refuses to detect one drive 2007-10-17 18:26 ` Michael Tokarev @ 2007-10-17 20:31 ` Alan Cox 2007-10-19 20:53 ` Manaï Mehdi 0 siblings, 1 reply; 5+ messages in thread From: Alan Cox @ 2007-10-17 20:31 UTC (permalink / raw) To: Michael Tokarev; +Cc: linux-ide > > This looks like both drives end up trying to be the slave ? Its certainly > > very vey confused at this point. Interesting it works with the BIOS doing > > the reset, wonder what the difference is. > > Not only it works with BIOS, it also works with via82cxxx just fine. The via82cxxx driver doesn't go off and reset everything unless it gets bad error cases. > > How are the drives jumpered and does it work with just one of the two > > present ? > > That's an interesting question. The machine is remote, and there's > no one on site who's able to check it. I'll try to get reach of it, > hopefully it will be soon enough. In any case, it looks like the > jumpers are OK, or else it shouldnt work with IDE module as well. Maybe. But its useful to know and it helps narrow down the fault. I've no idea whether the problem is hardware or software. What I am sure of though is if the BIOS and old driver work we should be able to make the new one work. My first guess is still a driver bug, and second some kind of probing interaction. BIOSen usually use Hal's code so we've got a fair idea of what the BIOS will do. Alan ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: pata_via refuses to detect one drive 2007-10-17 20:31 ` Alan Cox @ 2007-10-19 20:53 ` Manaï Mehdi 0 siblings, 0 replies; 5+ messages in thread From: Manaï Mehdi @ 2007-10-19 20:53 UTC (permalink / raw) To: linux-ide Alan Cox a écrit : >>> This looks like both drives end up trying to be the slave ? Its certainly >>> very vey confused at this point. Interesting it works with the BIOS doing >>> the reset, wonder what the difference is. >> Not only it works with BIOS, it also works with via82cxxx just fine. > > The via82cxxx driver doesn't go off and reset everything unless it gets > bad error cases. > >>> How are the drives jumpered and does it work with just one of the two >>> present ? >> That's an interesting question. The machine is remote, and there's >> no one on site who's able to check it. I'll try to get reach of it, >> hopefully it will be soon enough. In any case, it looks like the >> jumpers are OK, or else it shouldnt work with IDE module as well. > > Maybe. But its useful to know and it helps narrow down the fault. I've no > idea whether the problem is hardware or software. What I am sure of > though is if the BIOS and old driver work we should be able to make the > new one work. My first guess is still a driver bug, and second some kind > of probing interaction. BIOSen usually use Hal's code so we've got a fair > idea of what the BIOS will do. > > Alan > - > To unsubscribe from this list: send the line "unsubscribe linux-ide" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > I've got the same problem and I really don't know what to do here is my dmesg : SCSI subsystem initialized usb 1-2: new low speed USB device using uhci_hcd and address 2 libata version 2.21 loaded. pata_via 0000:00:11.1: version 0.3.1 scsi0 : pata_via scsi1 : pata_via ata1: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001ff00 irq 14 ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001ff08 irq 15 usb 1-2: configuration #1 chosen from 1 choice input: Logitech Inc. iFeel Mouse as /class/input/input2 input: USB HID v1.00 Mouse [Logitech Inc. iFeel Mouse ] on usb-0000:00:11.2-2 ata1.00: ATA-7: Maxtor 6Y160P0, YAR41BW0, max UDMA/133 ata1.00: 320173056 sectors, multi 16: LBA48 ata1.01: ATA-4: IBM-DJNA-351520, J56OA30K, max UDMA/33 ata1.01: 30033360 sectors, multi 16: LBA ata1.00: configured for UDMA/100 ata1.01: configured for UDMA/33 usb 2-2: new full speed USB device using uhci_hcd and address 2 ata2.00: ATAPI: SONY DVD RW DW-U18A, UYS1, max UDMA/33 usb 2-2: configuration #1 chosen from 1 choice ata2.00: configured for UDMA/33 scsi 0:0:0:0: Direct-Access ATA Maxtor 6Y160P0 YAR4 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 320173056 512-byte hardware sectors (163929 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:0:0: [sda] 320173056 512-byte hardware sectors (163929 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 < sda5 sda6 sda7 > sd 0:0:0:0: [sda] Attached SCSI disk scsi 0:0:1:0: Direct-Access ATA IBM-DJNA-351520 J56O PQ: 0 ANSI: 5 sd 0:0:1:0: [sdb] 30033360 512-byte hardware sectors (15377 MB) sd 0:0:1:0: [sdb] Write Protect is off sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00 sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:1:0: [sdb] 30033360 512-byte hardware sectors (15377 MB) sd 0:0:1:0: [sdb] Write Protect is off sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00 sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdb: sdb1 sdb2 < sdb5 sdb6 > sd 0:0:1:0: [sdb] Attached SCSI disk ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x12 data 36 in res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation) ata2: soft resetting port ata2.00: configured for UDMA/33 ata2: EH complete ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x12 data 36 in res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation) ata2: soft resetting port ata2.00: configured for UDMA/33 ata2: EH complete ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x12 data 36 in res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation) ata2: soft resetting port ata2.00: configured for UDMA/33 ata2: EH complete ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x12 data 36 in res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM violation) ata2: soft resetting port ata2.00: configured for UDMA/33 ata2: EH complete device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. SELinux: Disabled at runtime. SELinux: Unregistering netfilter hooks audit(1192825830.852:2): selinux=0 auid=4294967295 sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:1:0: Attached scsi generic sg1 type 0 ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2007-10-20 12:40 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2007-10-17 14:41 pata_via refuses to detect one drive Michael Tokarev 2007-10-17 15:50 ` Alan Cox 2007-10-17 18:26 ` Michael Tokarev 2007-10-17 20:31 ` Alan Cox 2007-10-19 20:53 ` Manaï Mehdi
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).