Fwd: [LIBATA] drives not detected

Fwd: [LIBATA] drives not detected

[Patrick Ale]

[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]

Hi All,

I got asked to forward this email I sent to the lkml to here :)
So that's what I do.


The problem below exists with 2.6.20-git11 and the Jeff's libata-dev
linus-upstream tree, which I cloned yesterday evening at the unholy
hour of 00:10 GMT

I am not on the ide list, so if you could CC me in anything regarding
my problem I'd be very thankfull :)


I attached a complete dmesg output.


Patrick

---------- Forwarded message ----------
From: Patrick Ale <patrick.ale@gmail.com>
Date: Feb 15, 2007 9:52 AM
Subject: Re: [LIBATA] drives not detected
To: linux-kernel <linux-kernel@vger.kernel.org>


On 2/15/07, Patrick Ale <patrick.ale@gmail.com> wrote:
> Good morning all,

> Now, when I boot up, I miss two drives, exactly the two connected to
> this promise card.
> I have another onboard Promise controller which works just fine, so
> the driver gets loaded properly, and since i see all my other disks
> but these two I think we can rule out a misconfiguration of the kernel
> config this time ;-)

It would be nice if I'd also mention the kernel I use eh.
It's linux-2.6-git8


Patrick

[-- Attachment #2: dmesg-lilith.txt --]
[-- Type: text/plain, Size: 20110 bytes --]

Linux version 2.6.20-g66efc5a7 (root@localhost) (gcc version 3.4.6 (Gentoo 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.10)) #1 PREEMPT Wed Feb 14 15:20:37 GMT 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2
copy_e820_map() start: 00000000000f0000 size: 0000000000010000 end: 0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 00000000bfef0000 end: 00000000bfff0000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 00000000bfff0000 size: 0000000000003000 end: 00000000bfff3000 type: 4
copy_e820_map() start: 00000000bfff3000 size: 000000000000d000 end: 00000000c0000000 type: 3
copy_e820_map() start: 00000000fec00000 size: 0000000000001000 end: 00000000fec01000 type: 2
copy_e820_map() start: 00000000fee00000 size: 0000000000001000 end: 00000000fee01000 type: 2
copy_e820_map() start: 00000000ffff0000 size: 0000000000010000 end: 0000000100000000 type: 2
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000bfff0000 (usable)
 BIOS-e820: 00000000bfff0000 - 00000000bfff3000 (ACPI NVS)
 BIOS-e820: 00000000bfff3000 - 00000000c0000000 (ACPI data)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
2175MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000f4c30
Entering add_active_range(0, 0, 786416) 0 entries of 256 used
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->   229376
  HighMem    229376 ->   786416
early_node_map[1] active PFN ranges
    0:        0 ->   786416
On node 0 totalpages: 786416
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 4064 pages, LIFO batch:0
  Normal zone: 1760 pages used for memmap
  Normal zone: 223520 pages, LIFO batch:31
  HighMem zone: 4351 pages used for memmap
  HighMem zone: 552689 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP 000F65A0, 0014 (r0 GBT   )
ACPI: RSDT BFFF3000, 002C (r1 GBT    AWRDACPI 42302E31 AWRD  1010101)
ACPI: FACP BFFF3040, 0074 (r1 GBT    AWRDACPI 42302E31 AWRD  1010101)
ACPI: DSDT BFFF30C0, 3BD9 (r1 GBT    AWRDACPI     1000 MSFT  100000C)
ACPI: FACS BFFF0000, 0040
ACPI: APIC BFFF6CC0, 005A (r1 GBT    AWRDACPI 42302E31 AWRD  1010101)
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:8 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at c4000000 (gap: c0000000:3ec00000)
Detected 2009.482 MHz processor.
Built 1 zonelists.  Total pages: 780273
Kernel command line: root=/dev/sda3
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 3114512k/3145664k available (3001k kernel code, 30084k reserved, 999k data, 196k init, 2228160k highmem)
virtual kernel memory layout:
    fixmap  : 0xfffaa000 - 0xfffff000   ( 340 kB)
    pkmap   : 0xffc00000 - 0xffe00000   (2048 kB)
    vmalloc : 0xf8800000 - 0xffbfe000   ( 115 MB)
    lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
      .init : 0xc04ec000 - 0xc051d000   ( 196 kB)
      .data : 0xc03ee529 - 0xc04e830c   ( 999 kB)
      .text : 0xc0100000 - 0xc03ee529   (3001 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4020.84 BogoMIPS (lpj=2010422)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000 00000000 00000000 00000000
CPU: CLK_CTL MSR was 6003d22f. Reprogramming to 2003d22f
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000420 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
CPU: AMD Athlon(tm) XP 2400+ stepping 01
Checking 'hlt' instruction... OK.
ACPI: Core revision 20070126
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xf9ee0, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 4000-407f claimed by vt8235 PM
PCI quirk: region 5000-500f claimed by vt8235 SMB
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 *6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [ALKA] (IRQs 20) *0
ACPI: PCI Interrupt Link [ALKB] (IRQs 21) *0
ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *0
ACPI: PCI Interrupt Link [ALKD] (IRQs 23) *0
SCSI subsystem initialized
libata version 2.10 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
ACPI: PCI Interrupt 0000:00:14.0[A] -> GSI 16 (level, low) -> IRQ 16
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[16]  MMIO=[eb00c000-eb00c7ff]  Max Packet=[2048]  IR/IT contexts=[8/8]
PCI: Bridge: 0000:00:01.0
  IO window: 7000-7fff
  MEM window: e8000000-e9ffffff
  PREFETCH window: c0000000-dfffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Machine check exception polling timer started.
microcode: CPU0 not a capable Intel processor
IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk>
highmem bounce pool size: 64 pages
Total HugeTLB memory allocated, 0
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
SGI XFS with ACLs, realtime, large block numbers, no debug enabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered (default)
io scheduler cfq registered
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
radeonfb: Found Intel x86 BIOS ROM Image
radeonfb: Retrieved PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=398.25 Mhz, System=200.00 MHz
radeonfb: PLL min 20000 max 40000
i2c_adapter i2c-1: unable to read EDID block.
i2c_adapter i2c-1: unable to read EDID block.
i2c_adapter i2c-1: unable to read EDID block.
radeonfb: Monitor 1 type CRT found
radeonfb: EDID probed
radeonfb: Monitor 2 type no found
Console: switching to colour frame buffer device 160x64
radeonfb (0000:01:00.0): ATI Radeon AP 
input: Power Button (FF) as /class/input/input0
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input1
ACPI: Power Button (CM) [PWRB]
ACPI: CPU0 (power states: C1[C1] C2[C2])
ACPI: Processor [CPU0] (supports 2 throttling states)
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
Hangcheck: Using get_cycles().
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
loop: loaded (max 8 devices)
pata_via 0000:00:11.1: version 0.2.1
ACPI: PCI Interrupt Link [ALKA] BIOS reported IRQ 0, using IRQ 20
ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
ACPI: PCI Interrupt 0000:00:11.1[A] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 17
ata1: PATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001dc00 irq 14
ata2: PATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001dc08 irq 15
scsi0 : pata_via
ata1.00: ATA-6: WDC WD2000JB-00GVA0, 08.02D08, max UDMA/100
ata1.00: 390721968 sectors, multi 16: LBA48 
ata1.00: configured for UDMA/100
scsi1 : pata_via
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[000020ed006adc65]
scsi 0:0:0:0: Direct-Access     ATA      WDC WD2000JB-00G 08.0 PQ: 0 ANSI: 5
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
sd 0:0:0:0: Attached scsi disk sda
ieee1394: raw1394: /dev/raw1394 device initialized
ACPI: PCI Interrupt Link [ALKB] BIOS reported IRQ 0, using IRQ 21
ACPI: PCI Interrupt Link [ALKB] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:10.3[D] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 18
ehci_hcd 0000:00:10.3: EHCI Host Controller
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.3: irq 18, io mem 0xeb00a000
ehci_hcd 0000:00:10.3: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 18
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.0: irq 18, io base 0x0000d000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 18
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.1: irq 18, io base 0x0000d400
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.2[C] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 18
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:10.2: irq 18, io base 0x0000d800
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usb 1-4: new high speed USB device using ehci_hcd and address 3
usb 1-4: configuration #1 chosen from 1 choice
usb 2-1: new low speed USB device using uhci_hcd and address 2
usb 2-1: configuration #1 chosen from 1 choice
input: Logitech USB Receiver as /class/input/input2
input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:10.0-1
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input3
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
oprofile: using NMI interrupt.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
ACPI: (supports S0 S1 S4 S5)
Time: tsc clocksource has been installed.
md: Autodetecting RAID arrays.
Time: acpi_pm clocksource has been installed.
md: autorun ...
md: ... autorun DONE.
XFS mounting filesystem sda3
Ending clean XFS mount for filesystem: sda3
VFS: Mounted root (xfs filesystem) readonly.
Freeing unused kernel memory: 196k freed
sd 0:0:0:0: Attached scsi generic sg0 type 0
8139too Fast Ethernet driver 0.9.28
ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 18 (level, low) -> IRQ 19
eth0: RealTek RTL8139 at 0xf884a000, 00:20:ed:61:8a:9c, IRQ 19
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
pata_pdc2027x 0000:00:0b.0: version 0.74-ac5
ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 19 (level, low) -> IRQ 20
pata_pdc2027x 0000:00:0b.0: PLL input clock 16754 kHz
ata3: PATA max UDMA/133 cmd 0xf88597c0 ctl 0xf8859fda bmdma 0xf8859000 irq 20
ata4: PATA max UDMA/133 cmd 0xf88595c0 ctl 0xf8859dda bmdma 0xf8859008 irq 20
scsi2 : pata_pdc2027x
input: PC Speaker as /class/input/input4
Initializing USB Mass Storage driver...
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
scsi 4:0:0:0: Direct-Access     USB2.0   CardReader CF RW 0.0> PQ: 0 ANSI: 0
sd 4:0:0:0: Attached scsi removable disk sdb
sd 4:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
scsi3 : pata_pdc2027x
ATA: abnormal status 0x8 on port 0xf88595df
pata_sil680 0000:00:0c.0: version 0.4.1
sil680: BA5_EN = 1 clock = 00
sil680: BA5_EN = 1 clock = 10
sil680: 133MHz clock.
ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 16 (level, low) -> IRQ 16
ata5: PATA max UDMA/133 cmd 0x0001a800 ctl 0x0001ac02 bmdma 0x0001b800 irq 16
ata6: PATA max UDMA/133 cmd 0x0001b000 ctl 0x0001b402 bmdma 0x0001b808 irq 16
scsi5 : pata_sil680
ata5.00: ATA-6: WDC WD1200JB-00EVA0, 15.05R15, max UDMA/100
ata5.00: 234441648 sectors, multi 0: LBA48 
ata5.01: ATA-7: Maxtor 6L250R0, BAH41E00, max UDMA/133
ata5.01: 490234752 sectors, multi 0: LBA48 
ata5.00: configured for UDMA/100
ata5.01: configured for UDMA/133
scsi6 : pata_sil680
ata6.00: ATA-6: WDC WD1600JB-00EVA0, 15.05R15, max UDMA/100
ata6.00: 312581808 sectors, multi 0: LBA48 
ata6.00: configured for UDMA/100
scsi 5:0:0:0: Direct-Access     ATA      WDC WD1200JB-00E 15.0 PQ: 0 ANSI: 5
SCSI device sdc: 234441648 512-byte hdwr sectors (120034 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdc: 234441648 512-byte hdwr sectors (120034 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdc: sdc1
sd 5:0:0:0: Attached scsi disk sdc
sd 5:0:0:0: Attached scsi generic sg2 type 0
scsi 5:0:1:0: Direct-Access     ATA      Maxtor 6L250R0   BAH4 PQ: 0 ANSI: 5
SCSI device sdd: 490234752 512-byte hdwr sectors (251000 MB)
sdd: Write Protect is off
sdd: Mode Sense: 00 3a 00 00
SCSI device sdd: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdd: 490234752 512-byte hdwr sectors (251000 MB)
sdd: Write Protect is off
sdd: Mode Sense: 00 3a 00 00
SCSI device sdd: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdd: sdd1
sd 5:0:1:0: Attached scsi disk sdd
sd 5:0:1:0: Attached scsi generic sg3 type 0
scsi 6:0:0:0: Direct-Access     ATA      WDC WD1600JB-00E 15.0 PQ: 0 ANSI: 5
SCSI device sde: 312581808 512-byte hdwr sectors (160042 MB)
sde: Write Protect is off
sde: Mode Sense: 00 3a 00 00
SCSI device sde: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sde: 312581808 512-byte hdwr sectors (160042 MB)
sde: Write Protect is off
sde: Mode Sense: 00 3a 00 00
SCSI device sde: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sde: sde1
sd 6:0:0:0: Attached scsi disk sde
sd 6:0:0:0: Attached scsi generic sg4 type 0
sata_sil 0000:00:08.0: version 2.0
ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 17 (level, low) -> IRQ 21
ata7: SATA max UDMA/100 cmd 0xf8874080 ctl 0xf887408a bmdma 0xf8874000 irq 21
ata8: SATA max UDMA/100 cmd 0xf88740c0 ctl 0xf88740ca bmdma 0xf8874008 irq 21
scsi7 : sata_sil
ata7: SATA link down (SStatus 0 SControl 310)
scsi8 : sata_sil
ata8: SATA link down (SStatus 0 SControl 310)
ACPI: PCI Interrupt Link [ALKC] BIOS reported IRQ 0, using IRQ 22
ACPI: PCI Interrupt Link [ALKC] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [ALKC] -> GSI 22 (level, low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:11.5 to 64
ACPI: PCI Interrupt 0000:00:0f.0[A] -> GSI 19 (level, low) -> IRQ 20
pata_pdc2027x 0000:00:0f.0: PLL input clock 33508 kHz
ata9: PATA max UDMA/133 cmd 0xf98a97c0 ctl 0xf98a9fda bmdma 0xf98a9000 irq 20
ata10: PATA max UDMA/133 cmd 0xf98a95c0 ctl 0xf98a9dda bmdma 0xf98a9008 irq 20
scsi9 : pata_pdc2027x
ata9.00: ATA-7: Maxtor 6Y160P0, YAR41BW0, max UDMA/133
ata9.00: 320173056 sectors, multi 16: LBA48 
ata9.01: ATA-6: WDC WD1200JB-00DUA3, 75.13B75, max UDMA/100
ata9.01: 234441648 sectors, multi 16: LBA48 
ata9.00: configured for UDMA/133
ata9.01: configured for UDMA/100
scsi10 : pata_pdc2027x
ATA: abnormal status 0x78 on port 0xf98a95df
scsi 9:0:0:0: Direct-Access     ATA      Maxtor 6Y160P0   YAR4 PQ: 0 ANSI: 5
SCSI device sdf: 320173056 512-byte hdwr sectors (163929 MB)
sdf: Write Protect is off
sdf: Mode Sense: 00 3a 00 00
SCSI device sdf: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdf: 320173056 512-byte hdwr sectors (163929 MB)
sdf: Write Protect is off
sdf: Mode Sense: 00 3a 00 00
SCSI device sdf: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdf: sdf1
sd 9:0:0:0: Attached scsi disk sdf
sd 9:0:0:0: Attached scsi generic sg5 type 0
scsi 9:0:1:0: Direct-Access     ATA      WDC WD1200JB-00D 75.1 PQ: 0 ANSI: 5
SCSI device sdg: 234441648 512-byte hdwr sectors (120034 MB)
sdg: Write Protect is off
sdg: Mode Sense: 00 3a 00 00
SCSI device sdg: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdg: 234441648 512-byte hdwr sectors (120034 MB)
sdg: Write Protect is off
sdg: Mode Sense: 00 3a 00 00
SCSI device sdg: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdg: sdg1
sd 9:0:1:0: Attached scsi disk sdg
sd 9:0:1:0: Attached scsi generic sg6 type 0
md: md1 stopped.
md: bind<sdg1>
md: md2 stopped.
md: bind<sdc1>
md: md3 stopped.
md: bind<sdf1>
raid1: raid set md3 active with 1 out of 2 mirrors
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
XFS mounting filesystem sda6
Ending clean XFS mount for filesystem: sda6
Adding 5863716k swap on /dev/disk/by-id/scsi-SATA_WDC_WD2000JB-00_WD-WCAL81971867-part2.  Priority:-1 extents:1 across:5863716k
i2c_adapter i2c-2: sendbytes: error - bailout.
it87: Found IT8705F chip at 0x290, revision 2
it87-isa 9191-0290: Detected broken BIOS defaults, disabling PWM interface
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1

Re: Fwd: [LIBATA] drives not detected

[Albert Lee]

Patrick Ale wrote:
> Hi All,
> 
> I got asked to forward this email I sent to the lkml to here :)
> So that's what I do.
> 
> 
> The problem below exists with 2.6.20-git11 and the Jeff's libata-dev
> linus-upstream tree, which I cloned yesterday evening at the unholy
> hour of 00:10 GMT
> 
> I am not on the ide list, so if you could CC me in anything regarding
> my problem I'd be very thankfull :)
> 
> 
> I attached a complete dmesg output.
> 
> 
> Patrick
> 
> ---------- Forwarded message ----------
> From: Patrick Ale <patrick.ale@gmail.com>
> Date: Feb 15, 2007 9:52 AM
> Subject: Re: [LIBATA] drives not detected
> To: linux-kernel <linux-kernel@vger.kernel.org>
> 
> 
> On 2/15/07, Patrick Ale <patrick.ale@gmail.com> wrote:
> 
>> Good morning all,
> 
> 
>> Now, when I boot up, I miss two drives, exactly the two connected to
>> this promise card.
>> I have another onboard Promise controller which works just fine, so
>> the driver gets loaded properly, and since i see all my other disks
>> but these two I think we can rule out a misconfiguration of the kernel
>> config this time ;-)
> 
> 
> It would be nice if I'd also mention the kernel I use eh.
> It's linux-2.6-git8
> 
> 

It's strange that your on-board Promise adapter works but the add-on
adapter detects no devices.

Could you please try reloading the pata_pdc2027x driver by
"rmmod pata_pdc2027x; modprobe pata_pdc2027x" and send the dmesg.

Thanks,

Albert

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

[-- Attachment #1: Type: text/plain, Size: 878 bytes --]

On 2/16/07, Albert Lee <albertcc@tw.ibm.com> wrote:
:

> It's strange that your on-board Promise adapter works but the add-on
> adapter detects no devices.
>
> Could you please try reloading the pata_pdc2027x driver by
> "rmmod pata_pdc2027x; modprobe pata_pdc2027x" and send the dmesg.

Ofcourse I can :)

The output is attached as dmesg-reprobe.txt

Maybe this it totaly unrelated, but I remember that in the IDE drivers
there was an option to force the card online, even when the BIOS was
disabled. I *do* see the drives being detected and it tells me the
BIOS is installed on boot time, but you never know :)

The controller with problems is scsi11 if I see correctly. Since on
that channel no disks are attached and no "abnormal status" is
outputted, you do see this "error" twice tho, since i have nothing
connected to the secundary channel on both controllers.


Patrick

[-- Attachment #2: dmesg-reprobe.txt --]
[-- Type: text/plain, Size: 2616 bytes --]

ata9.00: disabled
ata9.01: disabled
Synchronizing SCSI cache for disk sdf:
FAILED
  status = 0, message = 00, host = 4, driver = 00
  <5>Synchronizing SCSI cache for disk sdg:
FAILED
  status = 0, message = 00, host = 4, driver = 00
  <6>ACPI: PCI interrupt for device 0000:00:0f.0 disabled
ACPI: PCI interrupt for device 0000:00:0b.0 disabled
pata_pdc2027x 0000:00:0b.0: version 0.74-ac5
ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 19 (level, low) -> IRQ 20
pata_pdc2027x 0000:00:0b.0: PLL input clock 16754 kHz
ata11: PATA max UDMA/133 cmd 0xf88597c0 ctl 0xf8859fda bmdma 0xf8859000 irq 20
ata12: PATA max UDMA/133 cmd 0xf88595c0 ctl 0xf8859dda bmdma 0xf8859008 irq 20
scsi11 : pata_pdc2027x
scsi12 : pata_pdc2027x
ATA: abnormal status 0x8 on port 0xf88595df
ACPI: PCI Interrupt 0000:00:0f.0[A] -> GSI 19 (level, low) -> IRQ 20
pata_pdc2027x 0000:00:0f.0: PLL input clock 33508 kHz
ata13: PATA max UDMA/133 cmd 0xf98a97c0 ctl 0xf98a9fda bmdma 0xf98a9000 irq 20
ata14: PATA max UDMA/133 cmd 0xf98a95c0 ctl 0xf98a9dda bmdma 0xf98a9008 irq 20
scsi13 : pata_pdc2027x
ata13.00: ATA-7: Maxtor 6Y160P0, YAR41BW0, max UDMA/133
ata13.00: 320173056 sectors, multi 16: LBA48
ata13.01: ATA-6: WDC WD1200JB-00DUA3, 75.13B75, max UDMA/100
ata13.01: 234441648 sectors, multi 16: LBA48
ata13.00: configured for UDMA/133
ata13.01: configured for UDMA/100
scsi14 : pata_pdc2027x
ATA: abnormal status 0x78 on port 0xf98a95df
scsi 13:0:0:0: Direct-Access     ATA      Maxtor 6Y160P0   YAR4 PQ: 0 ANSI: 5
SCSI device sdf: 320173056 512-byte hdwr sectors (163929 MB)
sdf: Write Protect is off
sdf: Mode Sense: 00 3a 00 00
SCSI device sdf: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdf: 320173056 512-byte hdwr sectors (163929 MB)
sdf: Write Protect is off
sdf: Mode Sense: 00 3a 00 00
SCSI device sdf: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdf: sdf1
sd 13:0:0:0: Attached scsi disk sdf
sd 13:0:0:0: Attached scsi generic sg5 type 0
scsi 13:0:1:0: Direct-Access     ATA      WDC WD1200JB-00D 75.1 PQ: 0 ANSI: 5
SCSI device sdg: 234441648 512-byte hdwr sectors (120034 MB)
sdg: Write Protect is off
sdg: Mode Sense: 00 3a 00 00
SCSI device sdg: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdg: 234441648 512-byte hdwr sectors (120034 MB)
sdg: Write Protect is off
sdg: Mode Sense: 00 3a 00 00
SCSI device sdg: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdg: sdg1
sd 13:0:1:0: Attached scsi disk sdg
sd 13:0:1:0: Attached scsi generic sg6 type 0

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

[-- Attachment #1: Type: text/plain, Size: 308 bytes --]

On 2/16/07, Patrick Ale <patrick.ale@gmail.com> wrote:
> On 2/16/07, Albert Lee <albertcc@tw.ibm.com> wrote:

Maybe the output of an lspci -vvv helps, sorry if this is unnecesary
information, I just wanna help where I can :)

For clearance: The RAID controller is the onboard Promise, which works.


Patrick

[-- Attachment #2: lspci-lilith.txt --]
[-- Type: text/plain, Size: 13211 bytes --]

00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge
	Subsystem: Giga-byte Technology GA-7VAX Mainboard
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 8
	Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
	Capabilities: [80] AGP version 3.5
		Status: RQ=32 Iso- ArqSz=0 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
		Command: RQ=32 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
	Latency: 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 00007000-00007fff
	Memory behind bridge: e8000000-e9ffffff
	Prefetchable memory behind bridge: c0000000-dfffffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:08.0 Mass storage controller: Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 02)
	Subsystem: Silicon Image, Inc. SiI 3112 SATALink Controller
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 21
	Region 0: I/O ports at 8000 [size=8]
	Region 1: I/O ports at 8400 [size=4]
	Region 2: I/O ports at 8800 [size=8]
	Region 3: I/O ports at 8c00 [size=4]
	Region 4: I/O ports at 9000 [size=16]
	Region 5: Memory at eb009000 (32-bit, non-prefetchable) [size=512]
	[virtual] Expansion ROM at ea000000 [disabled] [size=512K]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=2 PME-

00:0b.0 Mass storage controller: Promise Technology, Inc. 20269 (rev 02) (prog-if 85)
	Subsystem: Promise Technology, Inc. Ultra133TX2
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (1000ns min, 4500ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 20
	Region 0: I/O ports at 9400 [size=8]
	Region 1: I/O ports at 9800 [size=4]
	Region 2: I/O ports at 9c00 [size=8]
	Region 3: I/O ports at a000 [size=4]
	Region 4: I/O ports at a400 [size=16]
	Region 5: Memory at eb000000 (32-bit, non-prefetchable) [size=16K]
	[virtual] Expansion ROM at ea100000 [disabled] [size=16K]
	Capabilities: [60] Power Management version 1
		Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0c.0 RAID bus controller: Silicon Image, Inc. PCI0680 Ultra ATA-133 Host Controller (rev 02)
	Subsystem: Silicon Image, Inc. Winic W-680 (Silicon Image 680 based)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32, Cache Line Size: 4 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: I/O ports at a800 [size=8]
	Region 1: I/O ports at ac00 [size=4]
	Region 2: I/O ports at b000 [size=8]
	Region 3: I/O ports at b400 [size=4]
	Region 4: I/O ports at b800 [size=16]
	Region 5: Memory at eb008000 (32-bit, non-prefetchable) [size=256]
	[virtual] Expansion ROM at ea080000 [disabled] [size=512K]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=2 PME-

00:0f.0 RAID bus controller: Promise Technology, Inc. PDC20276 (MBFastTrak133 Lite) (rev 01) (prog-if 85)
	Subsystem: Giga-byte Technology MBUltra 133
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (1000ns min, 4500ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 20
	Region 0: I/O ports at bc00 [size=8]
	Region 1: I/O ports at c000 [size=4]
	Region 2: I/O ports at c400 [size=8]
	Region 3: I/O ports at c800 [size=4]
	Region 4: I/O ports at cc00 [size=16]
	Region 5: Memory at eb004000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [60] Power Management version 1
		Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
	Subsystem: Giga-byte Technology GA-7VAX Mainboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 18
	Region 4: I/O ports at d000 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME+

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
	Subsystem: Giga-byte Technology GA-7VAX Mainboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin B routed to IRQ 18
	Region 4: I/O ports at d400 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) (prog-if 00 [UHCI])
	Subsystem: Giga-byte Technology GA-7VAX Mainboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin C routed to IRQ 18
	Region 4: I/O ports at d800 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])
	Subsystem: Giga-byte Technology GA-7VAX Mainboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32, Cache Line Size: 64 bytes
	Interrupt: pin D routed to IRQ 18
	Region 0: Memory at eb00a000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
	Subsystem: Giga-byte Technology GA-7VAX Mainboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
	Subsystem: Giga-byte Technology GA-7VAX Mainboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32
	Interrupt: pin A routed to IRQ 17
	Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
	Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
	Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
	Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
	Region 4: I/O ports at dc00 [size=16]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
	Subsystem: Giga-byte Technology GA-7VAX Onboard Audio (Realtek ALC650)
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin C routed to IRQ 22
	Region 0: I/O ports at e000 [size=256]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:13.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
	Subsystem: Realtek Semiconductor Co., Ltd. RT8139
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (8000ns min, 16000ns max)
	Interrupt: pin A routed to IRQ 19
	Region 0: I/O ports at e400 [size=256]
	Region 1: Memory at eb00b000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:14.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) (prog-if 10 [OHCI])
	Subsystem: Giga-byte Technology GA-7VT600-1394 Motherboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (8000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at eb00c000 (32-bit, non-prefetchable) [size=2K]
	Region 1: I/O ports at e800 [size=128]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] (prog-if 00 [VGA])
	Subsystem: ATI Technologies Inc RV350 AP [Radeon 9600]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (2000ns min), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at c0000000 (32-bit, prefetchable) [size=256M]
	Region 1: I/O ports at 7000 [size=256]
	Region 2: Memory at e9000000 (32-bit, non-prefetchable) [size=64K]
	[virtual] Expansion ROM at e8000000 [disabled] [size=128K]
	Capabilities: [58] AGP version 3.0
		Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
		Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none>
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary)
	Subsystem: ATI Technologies Inc Unknown device 4151
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (2000ns min), Cache Line Size: 32 bytes
	Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
	Region 1: Memory at e9010000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Re: Fwd: [LIBATA] drives not detected

[Albert Lee]

Patrick Ale wrote:
> On 2/16/07, Albert Lee <albertcc@tw.ibm.com> wrote:
> :
> 
>> It's strange that your on-board Promise adapter works but the add-on
>> adapter detects no devices.
>>
>> Could you please try reloading the pata_pdc2027x driver by
>> "rmmod pata_pdc2027x; modprobe pata_pdc2027x" and send the dmesg.
> 
> 
> Ofcourse I can :)
> 
> The output is attached as dmesg-reprobe.txt
> 
> Maybe this it totaly unrelated, but I remember that in the IDE drivers
> there was an option to force the card online, even when the BIOS was
> disabled. I *do* see the drives being detected and it tells me the
> BIOS is installed on boot time, but you never know :)
> 
> The controller with problems is scsi11 if I see correctly. Since on
> that channel no disks are attached and no "abnormal status" is
> outputted, you do see this "error" twice tho, since i have nothing
> connected to the secundary channel on both controllers.
> 
> 

Maybe the Promise BIOS set the adapter as disabled...
Could you please try the attached patch?

--
albert

--- linux-2.6.20-git11/drivers/ata/pata_pdc2027x.c~	2007-02-16 13:35:31.000000000 +0800
+++ linux-2.6.20-git11/drivers/ata/pata_pdc2027x.c	2007-02-16 17:02:02.000000000 +0800
@@ -315,8 +315,8 @@ static inline int pdc2027x_port_enabled(
 static int pdc2027x_prereset(struct ata_port *ap)
 {
 	/* Check whether port enabled */
-	if (!pdc2027x_port_enabled(ap))
-		return -ENOENT;
+	//if (!pdc2027x_port_enabled(ap))
+		//return -ENOENT;
 	pdc2027x_cbl_detect(ap);
 	return ata_std_prereset(ap);
 }

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/16/07, Albert Lee <albertcc@tw.ibm.com> wrote:
> Maybe the Promise BIOS set the adapter as disabled...
> Could you please try the attached patch?

This patch is against what? I get a hunk rejected.
patching file drivers/ata/pata_pdc2027x.c
Hunk #1 FAILED at 315.
1 out of 1 hunk FAILED -- saving rejects to file drivers/ata/pata_pdc2027x.c.rej

Can you make a patch against the libata-dev tree that I pulled last night?
It's impossible for me to reboot at the moment since my grub gives me
an attitude.

If it's too much work, don't worry, I can test it when I am at home :)


Thanks for your time so far.


Patrick

Re: Fwd: [LIBATA] drives not detected

[Albert Lee]

Patrick Ale wrote:
> On 2/16/07, Albert Lee <albertcc@tw.ibm.com> wrote:
> 
>> Maybe the Promise BIOS set the adapter as disabled...
>> Could you please try the attached patch?
> 
> 
> This patch is against what? I get a hunk rejected.
> patching file drivers/ata/pata_pdc2027x.c
> Hunk #1 FAILED at 315.
> 1 out of 1 hunk FAILED -- saving rejects to file
> drivers/ata/pata_pdc2027x.c.rej
> 
> Can you make a patch against the libata-dev tree that I pulled last night?
> It's impossible for me to reboot at the moment since my grub gives me
> an attitude.
> 

1. Hmm, the patch looks useless: if the port is disabled, there should
be a error message saying "port disabled. ignoring". But we don't see such
message. So, please disregard the patch. If you have time, please try if any
previous kernel version like 2.6.17 to 2.6.19 works.

2. 
>From the dmesg, 

pata_pdc2027x 0000:00:0b.0: version 0.74-ac5
ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 19 (level, low) -> IRQ 20
pata_pdc2027x 0000:00:0b.0: PLL input clock 16754 kHz
ata11: PATA max UDMA/133 cmd 0xf88597c0 ctl 0xf8859fda bmdma 0xf8859000 irq 20
ata12: PATA max UDMA/133 cmd 0xf88595c0 ctl 0xf8859dda bmdma 0xf8859008 irq 20
scsi11 : pata_pdc2027x
(==> There should be some boot probe activities here... )
scsi12 : pata_pdc2027x
ATA: abnormal status 0x8 on port 0xf88595df

It seems scsi_add_host() is completed for scsi11. But the boot probe
detects nothing. Adding Tejun to the cc list for advice.

--
albert

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

> >

>
> 1. Hmm, the patch looks useless: if the port is disabled, there should
> be a error message saying "port disabled. ignoring". But we don't see such
> message. So, please disregard the patch. If you have time, please try if any
> previous kernel version like 2.6.17 to 2.6.19 works.

Yep, will do, I'm sorry I cant test it right away, but when I reboot I
get dumped into the GRUB bash shell, which is not very cool when
you're 60KM away from where the server is (at home).

>
> It seems scsi_add_host() is completed for scsi11. But the boot probe
> detects nothing. Adding Tejun to the cc list for advice.

This is actually what I find the weirdest, (not the CC-ing Tejun :P) ,
I'd expect the driver to give me the same abnormal status error it
gives me for the ports I have no drives attached to.

I'll test asap!

Patrick

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

[-- Attachment #1: Type: text/plain, Size: 245 bytes --]

On 2/16/07, Albert Lee <albertcc@tw.ibm.com> wrote:

Hi,

To make the fun even more fun.
when I compile the old IDE drivers, rmmod the libata ones and modprobe
the IDE drivers for my Promise card, the drives DO get detected.

See here my dmesg.

[-- Attachment #2: linux-dmesg-ide.txt --]
[-- Type: text/plain, Size: 18798 bytes --]

Linux version 2.6.20 (root@localhost) (gcc version 3.4.6 (Gentoo 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.10)) #2 PREEMPT Thu Feb 15 18:27:08 GMT 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2
copy_e820_map() start: 00000000000f0000 size: 0000000000010000 end: 0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 00000000bfef0000 end: 00000000bfff0000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 00000000bfff0000 size: 0000000000003000 end: 00000000bfff3000 type: 4
copy_e820_map() start: 00000000bfff3000 size: 000000000000d000 end: 00000000c0000000 type: 3
copy_e820_map() start: 00000000fec00000 size: 0000000000001000 end: 00000000fec01000 type: 2
copy_e820_map() start: 00000000fee00000 size: 0000000000001000 end: 00000000fee01000 type: 2
copy_e820_map() start: 00000000ffff0000 size: 0000000000010000 end: 0000000100000000 type: 2
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000bfff0000 (usable)
 BIOS-e820: 00000000bfff0000 - 00000000bfff3000 (ACPI NVS)
 BIOS-e820: 00000000bfff3000 - 00000000c0000000 (ACPI data)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
2175MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000f4c30
Entering add_active_range(0, 0, 786416) 0 entries of 256 used
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->   229376
  HighMem    229376 ->   786416
early_node_map[1] active PFN ranges
    0:        0 ->   786416
On node 0 totalpages: 786416
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 4064 pages, LIFO batch:0
  Normal zone: 1760 pages used for memmap
  Normal zone: 223520 pages, LIFO batch:31
  HighMem zone: 4351 pages used for memmap
  HighMem zone: 552689 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v000 GBT                                   ) @ 0x000f65a0
ACPI: RSDT (v001 GBT    AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0xbfff3000
ACPI: FADT (v001 GBT    AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0xbfff3040
ACPI: MADT (v001 GBT    AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0xbfff6cc0
ACPI: DSDT (v001 GBT    AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:8 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at c4000000 (gap: c0000000:3ec00000)
Detected 2009.386 MHz processor.
Built 1 zonelists.  Total pages: 780273
Kernel command line: 
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 3114528k/3145664k available (2994k kernel code, 30068k reserved, 994k data, 196k init, 2228160k highmem)
virtual kernel memory layout:
    fixmap  : 0xfffaa000 - 0xfffff000   ( 340 kB)
    pkmap   : 0xffc00000 - 0xffe00000   (2048 kB)
    vmalloc : 0xf8800000 - 0xffbfe000   ( 115 MB)
    lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
      .init : 0xc04e8000 - 0xc0519000   ( 196 kB)
      .data : 0xc03eca09 - 0xc04e530c   ( 994 kB)
      .text : 0xc0100000 - 0xc03eca09   (2994 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4020.82 BogoMIPS (lpj=2010411)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000 00000000 00000000 00000000
CPU: CLK_CTL MSR was 6003d22f. Reprogramming to 2003d22f
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000420 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
CPU: AMD Athlon(tm) XP 2400+ stepping 01
Checking 'hlt' instruction... OK.
ACPI: Core revision 20060707
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xf9ee0, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region 4000-407f claimed by vt8235 PM
PCI quirk: region 5000-500f claimed by vt8235 SMB
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 *6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [ALKA] (IRQs 20) *0, disabled.
ACPI: PCI Interrupt Link [ALKB] (IRQs 21) *0, disabled.
ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *0, disabled.
ACPI: PCI Interrupt Link [ALKD] (IRQs 23) *0, disabled.
SCSI subsystem initialized
libata version 2.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
ACPI: PCI Interrupt 0000:00:14.0[A] -> GSI 16 (level, low) -> IRQ 16
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[16]  MMIO=[eb00c000-eb00c7ff]  Max Packet=[2048]  IR/IT contexts=[8/8]
PCI: Bridge: 0000:00:01.0
  IO window: 7000-7fff
  MEM window: e8000000-e9ffffff
  PREFETCH window: c0000000-dfffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Machine check exception polling timer started.
microcode: CPU0 not a capable Intel processor
IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk>
highmem bounce pool size: 64 pages
Total HugeTLB memory allocated, 0
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
SGI XFS with ACLs, realtime, large block numbers, no debug enabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered (default)
io scheduler cfq registered
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
radeonfb: Found Intel x86 BIOS ROM Image
radeonfb: Retrieved PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=398.25 Mhz, System=200.00 MHz
radeonfb: PLL min 20000 max 40000
i2c_adapter i2c-1: unable to read EDID block.
i2c_adapter i2c-1: unable to read EDID block.
i2c_adapter i2c-1: unable to read EDID block.
radeonfb: Monitor 1 type CRT found
radeonfb: EDID probed
radeonfb: Monitor 2 type no found
Console: switching to colour frame buffer device 160x64
radeonfb (0000:01:00.0): ATI Radeon AP 
input: Power Button (FF) as /class/input/input0
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input1
ACPI: Power Button (CM) [PWRB]
ACPI: CPU0 (power states: C1[C1] C2[C2])
ACPI: Processor [CPU0] (supports 2 throttling states)
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
Hangcheck: Using get_cycles().
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
loop: loaded (max 8 devices)
pata_via 0000:00:11.1: version 0.2.1
ACPI: PCI Interrupt Link [ALKA] BIOS reported IRQ 0, using IRQ 20
ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
ACPI: PCI Interrupt 0000:00:11.1[A] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 17
ata1: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xDC00 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xDC08 irq 15
scsi0 : pata_via
ata1.00: ATA-6, max UDMA/100, 390721968 sectors: LBA48 
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/100
scsi1 : pata_via
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[000020ed006adc65]
scsi 0:0:0:0: Direct-Access     ATA      WDC WD2000JB-00G 08.0 PQ: 0 ANSI: 5
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
sd 0:0:0:0: Attached scsi disk sda
ieee1394: raw1394: /dev/raw1394 device initialized
ACPI: PCI Interrupt Link [ALKB] BIOS reported IRQ 0, using IRQ 21
ACPI: PCI Interrupt Link [ALKB] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:10.3[D] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 18
ehci_hcd 0000:00:10.3: EHCI Host Controller
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.3: irq 18, io mem 0xeb00a000
ehci_hcd 0000:00:10.3: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 18
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.0: irq 18, io base 0x0000d000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 18
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.1: irq 18, io base 0x0000d400
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.2[C] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 18
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:10.2: irq 18, io base 0x0000d800
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usb 1-4: new high speed USB device using ehci_hcd and address 3
usb 1-4: configuration #1 chosen from 1 choice
usb 2-1: new low speed USB device using uhci_hcd and address 2
usb 2-1: configuration #1 chosen from 1 choice
input: Logitech USB Receiver as /class/input/input2
input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:10.0-1
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input3
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
oprofile: using NMI interrupt.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
ACPI: (supports S0 S1 S4 S5)
Time: tsc clocksource has been installed.
Time: acpi_pm clocksource has been installed.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
XFS mounting filesystem sda3
Ending clean XFS mount for filesystem: sda3
VFS: Mounted root (xfs filesystem) readonly.
Freeing unused kernel memory: 196k freed
sd 0:0:0:0: Attached scsi generic sg0 type 0
input: PC Speaker as /class/input/input4
sata_sil 0000:00:08.0: version 2.0
ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 17 (level, low) -> IRQ 19
ata3: SATA max UDMA/100 cmd 0xF883E080 ctl 0xF883E08A bmdma 0xF883E000 irq 19
ata4: SATA max UDMA/100 cmd 0xF883E0C0 ctl 0xF883E0CA bmdma 0xF883E008 irq 19
scsi2 : sata_sil
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
8139too Fast Ethernet driver 0.9.28
Initializing USB Mass Storage driver...
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ata3: SATA link down (SStatus 0 SControl 310)
scsi3 : sata_sil
ata4: SATA link down (SStatus 0 SControl 310)
ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 18 (level, low) -> IRQ 20
eth0: RealTek RTL8139 at 0xf883a000, 00:20:ed:61:8a:9c, IRQ 20
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
SiI680: IDE controller at PCI slot 0000:00:0c.0
ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 16 (level, low) -> IRQ 16
SiI680: chipset revision 2
SiI680: BASE CLOCK == 133
SiI680: 100% native mode on irq 16
    ide0: MMIO-DMA , BIOS settings: hda:pio, hdb:pio
    ide1: MMIO-DMA , BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: WDC WD1200JB-00EVA0, ATA DISK drive
hdb: Maxtor 6L250R0, ATA DISK drive
ide0 at 0xf8840080-0xf8840087,0xf884008a on irq 16
Probing IDE interface ide1...
hdc: WDC WD1600JB-00EVA0, ATA DISK drive
ide1 at 0xf88400c0-0xf88400c7,0xf88400ca on irq 16
PDC20269: IDE controller at PCI slot 0000:00:0b.0
ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 19 (level, low) -> IRQ 21
PDC20269: chipset revision 2
PDC20269: ROM enabled at 0xea100000
PDC20269: PLL input clock is 16763 kHz
PDC20269: 100% native mode on irq 21
    ide2: BM-DMA at 0xa400-0xa407, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0xa408-0xa40f, BIOS settings: hdg:pio, hdh:pio
Probing IDE interface ide2...
hde: probing with STATUS(0x50) instead of ALTSTATUS(0x0a)
hde: WDC WD1200JB-00EVA0, ATA DISK drive
hdf: probing with STATUS(0x50) instead of ALTSTATUS(0x0a)
hdf: ST3120022A, ATA DISK drive
ide2 at 0x9400-0x9407,0x9802 on irq 21
Probing IDE interface ide3...
PDC20276: IDE controller at PCI slot 0000:00:0f.0
ACPI: PCI Interrupt 0000:00:0f.0[A] -> GSI 19 (level, low) -> IRQ 21
PDC20276: chipset revision 1
PDC20276: PLL input clock is 33526 kHz
PDC20276: 100% native mode on irq 21
    ide4: BM-DMA at 0xcc00-0xcc07, BIOS settings: hdi:pio, hdj:pio
    ide5: BM-DMA at 0xcc08-0xcc0f, BIOS settings: hdk:pio, hdl:pio
Probing IDE interface ide4...
hdi: Maxtor 6Y160P0, ATA DISK drive
hdj: WDC WD1200JB-00DUA3, ATA DISK drive
ide4 at 0xbc00-0xbc07,0xc002 on irq 21
Probing IDE interface ide5...
ACPI: PCI Interrupt Link [ALKC] BIOS reported IRQ 0, using IRQ 22
ACPI: PCI Interrupt Link [ALKC] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [ALKC] -> GSI 22 (level, low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:11.5 to 64
hda: max request size: 64KiB
hda: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)
hda: cache flushes supported
 hda: hda1
hdb: max request size: 64KiB
hdb: 490234752 sectors (251000 MB) w/16384KiB Cache, CHS=30515/255/63, UDMA(133)
hdb: cache flushes supported
 hdb: hdb1
hdc: max request size: 64KiB
hdc: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(100)
hdc: cache flushes supported
 hdc: hdc1
hde: max request size: 512KiB
hde: Host Protected Area detected.
	current capacity is 234441648 sectors (120034 MB)
	native  capacity is 274103470214064 sectors (140340976749 MB)
hde: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hde: task_no_data_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: 0x37
hde: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)
hde: cache flushes supported
 hde: hde1
hdf: max request size: 512KiB
hdf: Host Protected Area detected.
	current capacity is 234441648 sectors (120034 MB)
	native  capacity is 274103470214064 sectors (140340976749 MB)
hdf: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdf: task_no_data_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: 0x37
hdf: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100)
hdf: cache flushes supported
 hdf: hdf1
hdi: max request size: 512KiB
hdi: 320173056 sectors (163928 MB) w/7936KiB Cache, CHS=19929/255/63, UDMA(133)
hdi: cache flushes supported
 hdi: hdi1
hdj: max request size: 512KiB
hdj: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)
hdj: cache flushes supported
 hdj: hdj1
scsi 4:0:0:0: Direct-Access     USB2.0   CardReader CF RW 0.0> PQ: 0 ANSI: 0
sd 4:0:0:0: Attached scsi removable disk sdb
sd 4:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
md: md1 stopped.
md: md2 stopped.
md: md3 stopped.
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
XFS mounting filesystem sda6
Ending clean XFS mount for filesystem: sda6
Adding 5863716k swap on /dev/disk/by-id/scsi-SATA_WDC_WD2000JB-00_WD-WCAL81971867-part2.  Priority:-1 extents:1 across:5863716k
i2c_adapter i2c-2: sendbytes: error - bailout.
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/17/07, Patrick Ale <patrick.ale@gmail.com> wrote:

Something is very off here... i know I have fever and all but this is
a "wt*" moment.

So, libata doesnt detect any drive, and the old IDE drivers give me

PDC20276: chipset revision 1
PDC20276: PLL input clock is 33527 kHz
PDC20276: 100% native mode on irq 20
    ide4: BM-DMA at 0xcc00-0xcc07, BIOS settings: hdi:pio, hdj:pio
    ide5: BM-DMA at 0xcc08-0xcc0f, BIOS settings: hdk:pio, hdl:pio
Probing IDE interface ide4...
hde: Host Protected Area detected.
        current capacity is 234441648 sectors (120034 MB)
        native  capacity is 274103470214064 sectors (140340976749 MB)

I can't even calculate how many terrabyte that'd be on just hde but I
can only wish I had that amount of diskspace.

So, probably, controller broken? I don't have another promise card to
check, I can buy one tho.

This still doesn't explain why libata doesn't detect the drives at
least, even with invalid drive specifications. Or why it doesnt give
me any sort of error at all.

Ah well, I probably shouldnt be messing around right now anyway.... :)

Tejun, Albert, thanks for the help so far, and to all people in Asia,
happy new year :)


Patrick

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/17/07, Patrick Ale <patrick.ale@gmail.com> wrote:

> I can't even calculate how many terrabyte that'd be on just hde but I
> can only wish I had that amount of diskspace.

More updates;

Either my controller is totaly borked or the driver doesn't totaly
like my PCI card.
When resyncing my md0 device, which is attached to the card, it stops
at 0.4%, gives lots of DMA timeouts and hde becomes unavailable.

Now, I attached the two drives to the onboard promise controller
(which had still one bus free) and all works fine, disks gets detected
properly (now testing with the legacy IDE drivers since that is what
at least detected my disks).


Patrick

Re: Fwd: [LIBATA] drives not detected

[Tejun Heo]

Patrick Ale wrote:
> On 2/16/07, Albert Lee <albertcc@tw.ibm.com> wrote:
> 
> Hi,
> 
> To make the fun even more fun.
> when I compile the old IDE drivers, rmmod the libata ones and modprobe
> the IDE drivers for my Promise card, the drives DO get detected.

Hmm...if you can use IDE driver for your root partition, change #undef
ATA_DEBUG to #define ATA_DEBUG in include/linux/libata.h and rebuild the
kernel.  After booting, insmod pata_pdc2027x and please report what the
kernel says.  It might be that the controller doesn't interact well with
libata's device discovery code using reset.  IDE drivers use different
method for device detection so that's probably where the difference is
coming from.

Thanks.

-- 
tejun

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/20/07, Tejun Heo <htejun@gmail.com> wrote:
> Hmm...if you can use IDE driver for your root partition, change #undef
> ATA_DEBUG to #define ATA_DEBUG in include/linux/libata.h and rebuild the
> kernel.  After booting, insmod pata_pdc2027x and please report what the
> kernel says.  It might be that the controller doesn't interact well with
> libata's device discovery code using reset.  IDE drivers use different
> method for device detection so that's probably where the difference is
> coming from.

Hi,

Yep, I can do that. My root partition is served by a VIA chipset, so
no problems recompiling and testing stuff.

Give me a day tho, I am doing a pvmove /dev/md/3 /dev/md/5 so I can
safely mess around with the disks without having to worry about the
data :)

I'll keep you posted,

Patrick

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

[-- Attachment #1: Type: text/plain, Size: 365 bytes --]

On 2/20/07, Patrick Ale <patrick.ale@gmail.com> wrote:
Hi,

Here is the output of the dmesg after inserting pata_pdc207x

I seriously start to think that one of my drives is acting in a way
that makes it unable for libata to detect the disks but makes the
legacy ide drivers do detect the disks...

I see things like "Port is frozen" in the dmesg output.


Patrick

[-- Attachment #2: dmesg-lilith-debug.txt --]
[-- Type: text/plain, Size: 23607 bytes --]

ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 00 b4 2c 5f 00 00 10
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
pata_pdc2027x 0000:00:0f.0: version 0.74-ac5
ACPI: PCI Interrupt 0000:00:0f.0[A] -> GSI 19 (level, low) -> IRQ 20
pata_pdc2027x 0000:00:0f.0: PLL input clock 33508 kHz
ata_device_add: ENTER
ata_port_add: ENTER
ata_port_start: prd alloc, virt f78db000, dma 378db000
ata11: PATA max UDMA/133 cmd 0xf99797c0 ctl 0xf9979fda bmdma 0xf9979000 irq 20
__ata_port_freeze: ata11 port frozen
ata_port_add: ENTER
ata_port_start: prd alloc, virt f7a29000, dma 37a29000
ata12: PATA max UDMA/133 cmd 0xf99795c0 ctl 0xf9979dda bmdma 0xf9979008 irq 20
__ata_port_freeze: ata12 port frozen
ata_device_add: probe begin
scsi11 : pata_pdc2027x
ata_port_schedule_eh: port EH scheduled
ata_scsi_error: ENTER
ata_port_flush_task: ENTER
ata_port_flush_task: flush #1
ata11: ata_port_flush_task: flush #2
ata11: ata_port_flush_task: EXIT
ata_eh_autopsy: ENTER
ata_eh_recover: ENTER
ata_eh_prep_resume: ENTER
ata_eh_prep_resume: EXIT
__ata_port_freeze: ata11 port frozen
ata_std_softreset: ENTER
ata_std_softreset: about to softreset, devmask=3
ata_bus_softreset: ata11: bus reset via SRST
ata_dev_classify: found ATA device by sig
ata_dev_classify: found ATA device by sig
ata_std_softreset: EXIT, classes[0]=1 [1]=1
ata_std_postreset: ENTER
ata_std_postreset: EXIT
ata_eh_thaw_port: ata11 port thawed
ata_eh_revalidate_and_attach: ENTER
ata11.00: ata_dev_read_id: ENTER, host 11, dev 0
ata_exec_command: ata11: cmd 0xEC
ata_hsm_move: ata11: protocol 2 task_state 1 (dev_stat 0x58)
ata_pio_sector: data read
ata_hsm_move: ata11: protocol 2 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_port_flush_task: ENTER
ata_port_flush_task: flush #1
ata11: ata_port_flush_task: flush #2
ata11: ata_port_flush_task: EXIT
ata11.00: ATA-7: Maxtor 6Y160P0, YAR41BW0, max UDMA/133
ata11.00: 320173056 sectors, multi 16: LBA48 
ata11.01: ata_dev_read_id: ENTER, host 11, dev 1
ata_exec_command: ata11: cmd 0xEC
ata_hsm_move: ata11: protocol 2 task_state 1 (dev_stat 0x58)
ata_pio_sector: data read
ata_hsm_move: ata11: protocol 2 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_port_flush_task: ENTER
ata_port_flush_task: flush #1
ata11: ata_port_flush_task: flush #2
ata11: ata_port_flush_task: EXIT
ata11.01: ATA-6: WDC WD1200JB-00DUA3, 75.13B75, max UDMA/100
ata11.01: 234441648 sectors, multi 16: LBA48 
ata_eh_revalidate_and_attach: EXIT
ata_eh_resume: ENTER
ata_eh_resume: EXIT
ata_dev_set_xfermode: set features - xfer mode
ata_exec_command: ata11: cmd 0xEF
ata_hsm_move: ata11: protocol 1 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_port_flush_task: ENTER
ata_port_flush_task: flush #1
ata11: ata_port_flush_task: flush #2
ata11: ata_port_flush_task: EXIT
ata_dev_set_xfermode: EXIT, err_mask=0
ata11.00: ata_dev_read_id: ENTER, host 11, dev 0
ata_exec_command: ata11: cmd 0xEC
ata_hsm_move: ata11: protocol 2 task_state 1 (dev_stat 0x58)
ata_pio_sector: data read
ata_hsm_move: ata11: protocol 2 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_port_flush_task: ENTER
ata_port_flush_task: flush #1
ata11: ata_port_flush_task: flush #2
ata11: ata_port_flush_task: EXIT
ata_dev_set_mode: xfer_shift=12, xfer_mode=0x42
ata11.00: configured for UDMA/33
ata_dev_set_xfermode: set features - xfer mode
ata_exec_command: ata11: cmd 0xEF
ata_hsm_move: ata11: protocol 1 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_port_flush_task: ENTER
ata_port_flush_task: flush #1
ata11: ata_port_flush_task: flush #2
ata11: ata_port_flush_task: EXIT
ata_dev_set_xfermode: EXIT, err_mask=0
ata11.01: ata_dev_read_id: ENTER, host 11, dev 1
ata_exec_command: ata11: cmd 0xEC
ata_hsm_move: ata11: protocol 2 task_state 1 (dev_stat 0x58)
ata_pio_sector: data read
ata_hsm_move: ata11: protocol 2 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_port_flush_task: ENTER
ata_port_flush_task: flush #1
ata11: ata_port_flush_task: flush #2
ata11: ata_port_flush_task: EXIT
ata_dev_set_mode: xfer_shift=12, xfer_mode=0x45
ata11.01: configured for UDMA/100
ata_eh_suspend: ENTER
ata_eh_suspend: EXIT
ata_eh_recover: EXIT, rc=0
ata_scsi_error: EXIT
scsi12 : pata_pdc2027x
ata_port_schedule_eh: port EH scheduled
ata_scsi_error: ENTER
ata_port_flush_task: ENTER
ata_port_flush_task: flush #1
ata12: ata_port_flush_task: flush #2
ata12: ata_port_flush_task: EXIT
ata_eh_autopsy: ENTER
ata_eh_recover: ENTER
ata_eh_prep_resume: ENTER
ata_eh_prep_resume: EXIT
__ata_port_freeze: ata12 port frozen
ata_std_softreset: ENTER
ata_std_softreset: about to softreset, devmask=3
ata_bus_softreset: ata12: bus reset via SRST
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 01 5b d4 87 00 00 10
ata_sg_setup: 2 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 02 83 10 e7 00 00 10
ata_sg_setup: 2 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 07 41 a6 8f 00 00 10
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 35 00 00 00 00 00 00 00 00
ata_exec_command: ata1: cmd 0xEA
ata_hsm_move: ata1: protocol 1 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 05 f1 93 28 00 00 02
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 35 00 00 00 00 00 00 00 00
ata_exec_command: ata1: cmd 0xEA
ata_hsm_move: ata1: protocol 1 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 02 83 10 f7 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 07 41 a6 8f 00 00 10
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_dev_classify: unknown device
ata_std_softreset: EXIT, classes[0]=5 [1]=5
ata_std_postreset: ENTER
ata_std_postreset: EXIT, no device
ata_eh_thaw_port: ata12 port thawed
ata_eh_revalidate_and_attach: ENTER
ata_eh_revalidate_and_attach: EXIT
ata_eh_resume: ENTER
ata_eh_resume: EXIT
ata_eh_suspend: ENTER
ata_eh_suspend: EXIT
ata_eh_recover: EXIT, rc=0
ata_scsi_error: EXIT
ata_device_add: host probe begin
ata_scsi_dump_cdb: CDB (11:0,0,0) 12 00 00 00 24 00 00 00 00
ata_scsi_dump_cdb: CDB (11:0,0,0) 12 00 00 00 60 00 00 00 00
scsi 11:0:0:0: Direct-Access     ATA      Maxtor 6Y160P0   YAR4 PQ: 0 ANSI: 5
ata_scsi_dump_cdb: CDB (11:0,0,0) 00 00 00 00 00 00 00 00 00
ata_scsi_dump_cdb: CDB (11:0,0,0) 25 00 00 00 00 00 00 00 00
SCSI device sdc: 320173056 512-byte hdwr sectors (163929 MB)
ata_scsi_dump_cdb: CDB (11:0,0,0) 5a 00 3f 00 00 00 00 00 08
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
ata_scsi_dump_cdb: CDB (11:0,0,0) 5a 00 08 00 00 00 00 00 08
ata_scsi_dump_cdb: CDB (11:0,0,0) 5a 00 08 00 00 00 00 00 24
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata_scsi_dump_cdb: CDB (11:0,0,0) 00 00 00 00 00 00 00 00 24
ata_scsi_dump_cdb: CDB (11:0,0,0) 25 00 00 00 00 00 00 00 00
SCSI device sdc: 320173056 512-byte hdwr sectors (163929 MB)
ata_scsi_dump_cdb: CDB (11:0,0,0) 5a 00 3f 00 00 00 00 00 08
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
ata_scsi_dump_cdb: CDB (11:0,0,0) 5a 00 08 00 00 00 00 00 08
ata_scsi_dump_cdb: CDB (11:0,0,0) 5a 00 08 00 00 00 00 00 24
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdc:<3>ata_scsi_dump_cdb: CDB (11:0,0,0) 28 00 00 00 00 00 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
 sdc1
sd 11:0:0:0: Attached scsi disk sdc
sd 11:0:0:0: Attached scsi generic sg2 type 0
ata_scsi_dump_cdb: CDB (11:0,1,0) 12 00 00 00 24 00 00 00 00
ata_scsi_dump_cdb: CDB (11:0,1,0) 12 00 00 00 60 00 00 00 00
scsi 11:0:1:0: Direct-Access     ATA      WDC WD1200JB-00D 75.1 PQ: 0 ANSI: 5
ata_scsi_dump_cdb: CDB (11:0,1,0) 00 00 00 00 00 00 00 00 00
ata_scsi_dump_cdb: CDB (11:0,1,0) 25 00 00 00 00 00 00 00 00
SCSI device sdd: 234441648 512-byte hdwr sectors (120034 MB)
ata_scsi_dump_cdb: CDB (11:0,1,0) 5a 00 3f 00 00 00 00 00 08
sdd: Write Protect is off
sdd: Mode Sense: 00 3a 00 00
ata_scsi_dump_cdb: CDB (11:0,1,0) 5a 00 08 00 00 00 00 00 08
ata_scsi_dump_cdb: CDB (11:0,1,0) 5a 00 08 00 00 00 00 00 24
SCSI device sdd: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata_scsi_dump_cdb: CDB (11:0,1,0) 00 00 00 00 00 00 00 00 24
ata_scsi_dump_cdb: CDB (11:0,1,0) 25 00 00 00 00 00 00 00 00
SCSI device sdd: 234441648 512-byte hdwr sectors (120034 MB)
ata_scsi_dump_cdb: CDB (11:0,1,0) 5a 00 3f 00 00 00 00 00 08
sdd: Write Protect is off
sdd: Mode Sense: 00 3a 00 00
ata_scsi_dump_cdb: CDB (11:0,1,0) 5a 00 08 00 00 00 00 00 08
ata_scsi_dump_cdb: CDB (11:0,1,0) 5a 00 08 00 00 00 00 00 24
SCSI device sdd: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdd:<3>ata_scsi_dump_cdb: CDB (11:0,1,0) 28 00 00 00 00 00 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,0,0) 12 01 80 00 fe 00 00 00 00
 sdd1
sd 11:0:1:0: Attached scsi disk sdd
sd 11:0:1:0: Attached scsi generic sg3 type 0
ata_scsi_dump_cdb: CDB (11:0,1,0) 12 01 80 00 fe 00 00 00 00
ata_scsi_dump_cdb: CDB (11:0,1,0) 28 00 0d f9 4b 00 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,0,0) 28 00 13 15 73 80 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0x25
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,1,0) 28 00 0d f9 4b a8 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,0,0) 28 00 13 15 73 f8 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0x25
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,1,0) 28 00 0d f9 4b 70 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,0,0) 28 00 13 15 73 c0 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0x25
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,1,0) 28 00 0d f9 4a b0 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,0,0) 28 00 13 15 73 00 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0x25
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,1,0) 28 00 0d f9 4b a0 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,0,0) 28 00 13 15 73 f0 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0x25
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,1,0) 28 00 0d f9 4a 20 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,0,0) 28 00 13 15 72 70 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0x25
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,1,0) 28 00 00 00 00 00 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,0,0) 28 00 00 00 00 00 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,1,0) 28 00 00 00 00 08 00 00 20
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,0,0) 28 00 00 00 00 08 00 00 20
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,1,0) 28 00 00 00 00 28 00 00 60
ata_sg_setup: 2 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,0,0) 28 00 00 00 00 28 00 00 60
ata_sg_setup: 2 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,1,0) 28 00 00 00 02 00 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,0,0) 28 00 00 00 02 00 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,1,0) 28 00 0d f9 37 3f 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0xC8
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 1 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (11:0,0,0) 28 00 12 a1 8a 3f 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata11: cmd 0x25
ata_hsm_move: ata11: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata11: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 00 b4 2c 5f 00 00 10
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 02 83 10 ff 00 00 18
ata_sg_setup: 3 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 35 00 00 00 00 00 00 00 00
ata_exec_command: ata1: cmd 0xEA
ata_hsm_move: ata1: protocol 1 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 05 f1 93 2a 00 00 04
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 35 00 00 00 00 00 00 00 00
ata_exec_command: ata1: cmd 0xEA
ata_hsm_move: ata1: protocol 1 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 00 b4 2c 1f 00 00 01
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 02 83 11 17 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 07 41 a6 8f 00 00 10
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 02 83 10 df 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 02 83 10 ef 00 00 10
ata_sg_setup: 2 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 02 83 11 0f 00 00 10
ata_sg_setup: 2 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 07 41 a6 8f 00 00 10
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 02 03 7b 90 00 00 01
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 02 03 7b 97 00 00 10
ata_sg_setup: 2 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 07 44 22 c7 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 35 00 00 00 00 00 00 00 00
ata_exec_command: ata1: cmd 0xEA
ata_hsm_move: ata1: protocol 1 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 05 f1 93 2e 00 00 02
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 35 00 00 00 00 00 00 00 00
ata_exec_command: ata1: cmd 0xEA
ata_hsm_move: ata1: protocol 1 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 35 00 00 00 00 00 00 00 00
ata_exec_command: ata1: cmd 0xEA
ata_hsm_move: ata1: protocol 1 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 05 f1 93 30 00 00 05
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 35 00 00 00 00 00 00 00 00
ata_exec_command: ata1: cmd 0xEA
ata_hsm_move: ata1: protocol 1 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 01 5f df 4f 00 00 08
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 28 00 01 5f 14 17 00 00 10
ata_sg_setup: 2 sg elements mapped
ata_exec_command: ata1: cmd 0xC8
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 35 00 00 00 00 00 00 00 00
ata_exec_command: ata1: cmd 0xEA
ata_hsm_move: ata1: protocol 1 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 05 f1 93 35 00 00 07
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 35 00 00 00 00 00 00 00 00
ata_exec_command: ata1: cmd 0xEA
ata_hsm_move: ata1: protocol 1 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 00 b4 2c 1f 00 00 01
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 02 83 11 1f 00 00 10
ata_sg_setup: 2 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 2a 00 07 41 a6 8f 00 00 10
ata_sg_setup: 1 sg elements mapped
ata_exec_command: ata1: cmd 0xCA
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50
ata_scsi_dump_cdb: CDB (1:0,0,0) 28 00 01 5f 98 47 00 00 10
ata_sg_setup: 2 sg elements mapped
ata_exec_command: ata1: cmd 0xC8
ata_hsm_move: ata1: protocol 3 task_state 2 (dev_stat 0x50)
ata_hsm_move: ata1: dev 0 command complete, drv_stat 0x50

Re: Fwd: [LIBATA] drives not detected

[Tejun Heo]

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

Patrick Ale wrote:
> On 2/20/07, Patrick Ale <patrick.ale@gmail.com> wrote:
> Hi,
> 
> Here is the output of the dmesg after inserting pata_pdc207x
> 
> I seriously start to think that one of my drives is acting in a way
> that makes it unable for libata to detect the disks but makes the
> legacy ide drivers do detect the disks...
> 
> I see things like "Port is frozen" in the dmesg output.

That's normal but your drives are failing classification.  Can you
please apply the attached patch and report what the kernel says.  You
can turn off DEBUG options.

Thanks.

-- 
tejun

[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 513 bytes --]

diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 2cf8251..1263d1b 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -716,6 +716,8 @@ ata_dev_try_classify(struct ata_port *ap, unsigned int device, u8 *r_err)
 	memset(&tf, 0, sizeof(tf));
 
 	ap->ops->tf_read(ap, &tf);
+	ata_port_printk(ap, KERN_INFO, "CLASSIFY: device %u %02x:%02x %02x:%02x:%02x\n",
+			device, tf.command, tf.feature, tf.lbal, tf.lbam, tf.lbah);
 	err = tf.feature;
 	if (r_err)
 		*r_err = err;

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/21/07, Tejun Heo <htejun@gmail.com> wrote:

>
> That's normal but your drives are failing classification.  Can you
> please apply the attached patch and report what the kernel says.  You
> can turn off DEBUG options.

Hi,

The patch fails on both 2.6.20 and the linus-upstream source.
patching file drivers/ata/libata-core.c
Hunk #1 FAILED at 716.
1 out of 1 hunk FAILED -- saving rejects to file drivers/ata/libata-core.c.rej

I see only two lines have to be added, can I do this manualy?


Patrick

Re: Fwd: [LIBATA] drives not detected

[Tejun Heo]

Patrick Ale wrote:
> On 2/21/07, Tejun Heo <htejun@gmail.com> wrote:
> 
>>
>> That's normal but your drives are failing classification.  Can you
>> please apply the attached patch and report what the kernel says.  You
>> can turn off DEBUG options.
> 
> Hi,
> 
> The patch fails on both 2.6.20 and the linus-upstream source.
> patching file drivers/ata/libata-core.c
> Hunk #1 FAILED at 716.
> 1 out of 1 hunk FAILED -- saving rejects to file
> drivers/ata/libata-core.c.rej
> 
> I see only two lines have to be added, can I do this manualy?

Sure.  Thanks.

-- 
tejun

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/21/07, Tejun Heo <htejun@gmail.com> wrote:

> Sure.  Thanks.

Okay, done. :)

And here is the dmesg output for my pata_pdc207x driver.

pata_pdc2027x 0000:00:0f.0: version 0.74-ac5
ACPI: PCI Interrupt 0000:00:0f.0[A] -> GSI 19 (level, low) -> IRQ 21
pata_pdc2027x 0000:00:0f.0: PLL input clock 34020 kHz
ata7: PATA max UDMA/133 cmd 0xf98a17c0 ctl 0xf98a1fda bmdma 0xf98a1000 irq 21
ata8: PATA max UDMA/133 cmd 0xf98a15c0 ctl 0xf98a1dda bmdma 0xf98a1008 irq 21
scsi7 : pata_pdc2027x
cx2388x v4l2 driver version 0.0.6 loaded
ata7: CLASSIFY: device 0 50:01 01:00:00
ata7: CLASSIFY: device 1 50:01 01:00:00
ata7.00: ATA-7: Maxtor 6Y160P0, YAR41BW0, max UDMA/133
ata7.00: 320173056 sectors, multi 16: LBA48
ata7.01: ATA-6: WDC WD1200JB-00DUA3, 75.13B75, max UDMA/100
ata7.01: 234441648 sectors, multi 16: LBA48
ata7.00: configured for UDMA/33
ata7.01: configured for UDMA/100
scsi8 : pata_pdc2027x
scsi 4:0:0:0: Direct-Access     USB2.0   CardReader CF RW 0.0> PQ: 0 ANSI: 0
sd 4:0:0:0: Attached scsi removable disk sde
sd 4:0:0:0: Attached scsi generic sg4 type 0
usb-storage: device scan complete
ata8: CLASSIFY: device 0 50:00 aa:fe:3f
ata8: CLASSIFY: device 1 50:00 aa:10:00
scsi 7:0:0:0: Direct-Access     ATA      Maxtor 6Y160P0   YAR4 PQ: 0 ANSI: 5
SCSI device sdf: 320173056 512-byte hdwr sectors (163929 MB)
sdf: Write Protect is off
sdf: Mode Sense: 00 3a 00 00
SCSI device sdf: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
SCSI device sdf: 320173056 512-byte hdwr sectors (163929 MB)
sdf: Write Protect is off
sdf: Mode Sense: 00 3a 00 00
SCSI device sdf: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
 sdf: sdf1
sd 7:0:0:0: Attached scsi disk sdf
sd 7:0:0:0: Attached scsi generic sg5 type 0
scsi 7:0:1:0: Direct-Access     ATA      WDC WD1200JB-00D 75.1 PQ: 0 ANSI: 5
SCSI device sdg: 234441648 512-byte hdwr sectors (120034 MB)
sdg: Write Protect is off
sdg: Mode Sense: 00 3a 00 00
SCSI device sdg: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
SCSI device sdg: 234441648 512-byte hdwr sectors (120034 MB)
sdg: Write Protect is off
sdg: Mode Sense: 00 3a 00 00
SCSI device sdg: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
 sdg: sdg1
sd 7:0:1:0: Attached scsi disk sdg
sd 7:0:1:0: Attached scsi generic sg6 type 0


Patrick

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/21/07, Patrick Ale <patrick.ale@gmail.com> wrote:
> On 2/21/07, Tejun Heo <htejun@gmail.com> wrote:

[snippet]
> sd 7:0:1:0: Attached scsi generic sg6 type 0
>
>
> Patrick
>

Should I start worrying allready? I mean.. does this mean both disks
are (soon to be) dead?

Patrick

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/21/07, Patrick Ale <patrick.ale@gmail.com> wrote:

I think something snuffed it or is just playing a trick on me, look.

I detach the master disk and boot.

ata7: PATA max UDMA/133 cmd 0xf98a97c0 ctl 0xf98a9fda bmdma 0xf98a9000 irq 21
ata8: PATA max UDMA/133 cmd 0xf98a95c0 ctl 0xf98a9dda bmdma 0xf98a9008 irq 21
scsi6 : pata_pdc2027x
cx2388x v4l2 driver version 0.0.6 loaded
ata7: CLASSIFY: device 0 50:01 01:00:00
ata7: CLASSIFY: device 1 50:01 01:00:00
ata7.00: ATA-7: Maxtor 6Y160P0, YAR41BW0, max UDMA/133
ata7.00: 320173056 sectors, multi 16: LBA48
ata7.01: ATA-6: WDC WD1200JB-00DUA3, 75.13B75, max UDMA/100
ata7.01: 234441648 sectors, multi 16: LBA48
ata7.00: configured for UDMA/33
ata7.01: configured for UDMA/100
scsi7 : pata_pdc2027x
ata8: CLASSIFY: device 0 20:20 20:20:20
ata8: CLASSIFY: device 1 50:01 01:00:00
ATA: abnormal status 0x78 on port 0xf98a95df
ATA: abnormal status 0x78 on port 0xf98a95df
ata8.01: ATA-6: ST3120022A, 8.54, max UDMA/100
ata8.01: 234441648 sectors, multi 16: LBA48
ata8.01: configured for UDMA/100


Lookit!!! A seagate disk on the slave port!!

So, I halt the system, detach the slave and and attach the master.

pata_pdc2027x 0000:00:0f.0: version 0.74-ac5
ACPI: PCI Interrupt 0000:00:0f.0[A] -> GSI 19 (level, low) -> IRQ 19
pata_pdc2027x 0000:00:0f.0: PLL input clock 57326 kHz
ata3: PATA max UDMA/133 cmd 0xf88517c0 ctl 0xf8851fda bmdma 0xf8851000 irq 19
ata4: PATA max UDMA/133 cmd 0xf88515c0 ctl 0xf8851dda bmdma 0xf8851008 irq 19
scsi2 : pata_pdc2027x
input: PC Speaker as /class/input/input4
8139too Fast Ethernet driver 0.9.28
ata3: CLASSIFY: device 0 50:01 01:00:00
ata3: CLASSIFY: device 1 50:01 01:00:00
ata3.00: ATA-7: Maxtor 6Y160P0, YAR41BW0, max UDMA/133
ata3.00: 320173056 sectors, multi 16: LBA48
ata3.01: ATA-6: WDC WD1200JB-00DUA3, 75.13B75, max UDMA/100
ata3.01: 234441648 sectors, multi 16: LBA48
ata3.00: configured for UDMA/33
ata3.01: configured for UDMA/100
scsi3 : pata_pdc2027x
Linux video capture interface: v2.00
ata4: CLASSIFY: device 0 50:01 01:00:00
ata4: CLASSIFY: device 1 00:01 01:00:00
ata4.00: ATA-6: WDC WD1200JB-00EVA0, 15.05R15, max UDMA/100
ata4.00: 234441648 sectors, multi 16: LBA48
ata4.00: configured for UDMA/100


Ye gods! A Western Digital drive on the master port!
Please note how my ata busses change from ata7,ata8 to ata3,ata4 ,
this immediately solves my question how come my drive order mangles up
at times.

I tried to change the master/slave order aswell, so make the Seagate
master and the WD slave, no success, disks wont get detected.

Guess my only way out of this is to use both drives on seperate channels.

Unless there are patches I can try of course :)


Patrick

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

Hi,

I am going to do a last ressort attempt.
I am going to switch cables with a set of harddrives that are working
properly and see if that works.

I changed cables allready, but with my luck the cables I changed them
for are faulty.
Jumpers and all look ok, I changed the jumpers, on advice from Greg
and this didnt solve the problem.

Eric's comment about master slave collision made me think about a
probable cable problem, which I am going to test now.

Stays weird that the legacy ide drivers do find the drives tho.

I will let you know.

Patrick

Re: Fwd: [LIBATA] drives not detected

[Tejun Heo]

Hello, Patrick Ale.

Patrick Ale wrote:
> I am going to do a last ressort attempt.
> I am going to switch cables with a set of harddrives that are working
> properly and see if that works.

I don't think cables or the drives are the problems here but please keep
me posted about your test result.

> I changed cables allready, but with my luck the cables I changed them
> for are faulty.
> Jumpers and all look ok, I changed the jumpers, on advice from Greg
> and this didnt solve the problem.
> 
> Eric's comment about master slave collision made me think about a
> probable cable problem, which I am going to test now.
> 
> Stays weird that the legacy ide drivers do find the drives tho.

libata and ide use different methods to discover devices.  libata
depends on reset to work.  After reset, devices are supposed to send
diagnostic and the classfication code via TF registers.  OTOH, ide just
issues IDENTIFY and then IDENTIFY PACKET to each device slot without
resetting the channel.  Maybe we're doing something wrong in the pdc
driver or the controller just doesn't like libata's probing method.

Summoning (P)ATA gurus.  Hi! Here's the bullet.

The whole thread can be viewed at the following page.

  http://thread.gmane.org/gmane.linux.kernel/493605

It seems we can't read TF containing reset result reliable iff both
master and slave are present.  Please take a look at the following message.

  http://article.gmane.org/gmane.linux.ide/16216

  ata8: CLASSIFY: device 0 50:00 aa:fe:3f
  ata8: CLASSIFY: device 1 50:00 aa:10:00

Dumped TF regs are "status:error lbal:lbam:lbah".  Leaving only one
device on the channel, be it master or slave, works.

  http://article.gmane.org/gmane.linux.ide/16219

  ata8: CLASSIFY: device 0 20:20 20:20:20
  ata8: CLASSIFY: device 1 50:01 01:00:00

  or

  ata4: CLASSIFY: device 0 50:01 01:00:00
  ata4: CLASSIFY: device 1 00:01 01:00:00

Could it be timing issue like not using compatible pio timing during
reset?  Please keep in mind that we also have bug reports about solitary
slave device doesn't get detected in some cases.

Thanks.

-- 
tejun

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/23/07, Tejun Heo <htejun@gmail.com> wrote:
>
> libata and ide use different methods to discover devices.  libata
> depends on reset to work.  After reset, devices are supposed to send
> diagnostic and the classfication code via TF registers.  OTOH, ide just
> issues IDENTIFY and then IDENTIFY PACKET to each device slot without
> resetting the channel.  Maybe we're doing something wrong in the pdc
> driver or the controller just doesn't like libata's probing method.

Extra info for you:

Tejun, you have way more libata experience as me, all of you do
probably and I don't question your theory but let me try to give you
my theory about why I think it's a drive or cable.

As you remember I have this onboard controller,also Promise, with
master and slave on one controller. And this works just fine, which
makes it kind of hard for me to believe that it is something in the
driver. Why would one bus work great and the other doesnt?

A very short summary for the gurus:

- The secundaiy bus on the onboard promise board wasnt in use yet, so
I connected the drives to this bus, and you can guess it, the drives
got detected by the BIOS but not by the drivers. So we can rule out at
least that my PCI-Add on Promise controller is broken and that we have
to look for the problem some where else.

- Legacy IDE drivers DO work, but, as you say yourself, they dont
depend on a drive reset,

- libata detects the drives, but only with one drive attached to the cable.

Now, taking the single drive operation working with libata and the old
ide drives not needing a reset to detect disks into account, plus this
information above in account: my theory.

What if, the Promise BIOS doesn't depend on this reset either?
What if the BIOS does something along the line of screaming "HELLO?!"
and the drives, both independent from each other yell back: "Ola, I am
a Seagate ST8whatever and I can do UDMA100", and the BIOS just takes
this for granted. With other words, what if the BIOS only cares for
the disk controller to be able to give its identification information
from the firmware, even if the platters are all to the moon? It
wouldn't  be the first time I see disks being detected by an ATA BIOS
and the disks being totally useless, not to mention, disks lying about
their capabilities,

Please note in past dmesg-es I sent that the legacy IDE drivers claim
how the native capacity of both drives is something like 102 petabyte.
Do disks these size exist even?
Based on what you tell me, the legacy IDE drivers tend to take things
for granted too, either it just reads what the ATA BIOS tells the
drivers or it does it own check, just by screaming "HELLO" and getting
the same "Ola" back from the drives.

Now, libata seems to be way more suffisticated and handles drives and
detection in a way more fancy matter. So, what if the machine boots
fine, less suffisticated BIOS "detects" the drives and its sizes and
now we boot the kernel. Libata does its stuff, does a reset of the bus
and *bang* a collision of some sort comes forth?

I checked the jumpers, changed them, changed the ATA bus even, nothing helps.
And even tho I changed the ATA cable allready, who guarantees me that
this cable is correct? With my luck, it isnt. Which is why I want to
just yank the cables from the other _working_ master and slave combo
and see how this goes.

Right now I am moving data from the "problem" disks to a safe
location, just to guarantee I dont fry my data in any sort.

Please let me know if my theory makes any sense or if I should cut on
the slibovica and palinka :)


Patrick

Re: Fwd: [LIBATA] drives not detected

[Jeff Garzik]

Is this detection problem limited to Promise controllers?

It's possible we might be programming the Promise controllers in "dual 
master" mode, and then accidentally missing the second channel somehow.

	Jeff

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/23/07, Jeff Garzik <jeff@garzik.org> wrote:
> Is this detection problem limited to Promise controllers?
>
> It's possible we might be programming the Promise controllers in "dual
> master" mode, and then accidentally missing the second channel somehow.

Good point and good news, I have a free bus on my VIA controller
aswell, not really free, but I can disconnect the DVD writer to test
this.

Will do so when I am home.


Patrick

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/23/07, Patrick Ale <patrick.ale@gmail.com> wrote:
> On 2/23/07, Jeff Garzik <jeff@garzik.org> wrote:
> > Is this detection problem limited to Promise controllers?

No, seems to limited to stupid cables only.

Look, I bought a new cable and see what happens:

pata_pdc2027x 0000:00:0f.0: PLL input clock 33509 kHz
Linux video capture interface: v2.00
ata5: PATA max UDMA/133 cmd 0xf98a17c0 ctl 0xf98a1fda bmdma 0xf98a1000 irq 19
ata6: PATA max UDMA/133 cmd 0xf98a15c0 ctl 0xf98a1dda bmdma 0xf98a1008 irq 19
scsi4 : pata_pdc2027x
ata5: CLASSIFY: device 0 50:01 01:00:00
ata5: CLASSIFY: device 1 50:01 01:00:00
ata5.00: ATA-7: Maxtor 6Y160P0, YAR41BW0, max UDMA/133
ata5.00: 320173056 sectors, multi 16: LBA48
ata5.01: ATA-6: WDC WD1200JB-00DUA3, 75.13B75, max UDMA/100
ata5.01: 234441648 sectors, multi 16: LBA48
ata5.00: configured for UDMA/33
ata5.01: configured for UDMA/100
scsi5 : pata_pdc2027x
ata6: CLASSIFY: device 0 50:01 01:00:00
ata6: CLASSIFY: device 1 50:01 01:00:00
ata6.00: ATA-6: WDC WD1200JB-00EVA0, 15.05R15, max UDMA/100
ata6.00: 234441648 sectors, multi 16: LBA48
ata6.01: ATA-6: ST3120022A, 8.54, max UDMA/100
ata6.01: 234441648 sectors, multi 16: LBA48
ata6.00: configured for UDMA/100
ata6.01: configured for UDMA/100


I can't believe this sh*t, I tried 3 sets of cables, non of them
worked, now I buy a new cable and things get detected at once?

*sigh*

Thanks for your help all, I really appriciate it... it still looks
very weird to me but a fact is, with this new cable things do seem to
work.


Patrick

Re: Fwd: [LIBATA] drives not detected

[Tejun Heo]

Patrick Ale wrote:
> I can't believe this sh*t, I tried 3 sets of cables, non of them
> worked, now I buy a new cable and things get detected at once?
> 
> *sigh*
> 
> Thanks for your help all, I really appriciate it... it still looks
> very weird to me but a fact is, with this new cable things do seem to
> work.

Hmmm.. Is your new cable 80c while the older ones are 40c?

  http://upload.wikimedia.org/wikipedia/commons/2/26/ATA_cables.jpg

The upper one is 40c while the other one is 80c.

-- 
tejun

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/24/07, Tejun Heo <htejun@gmail.com> wrote:
> Patrick Ale wrote:


>
> The upper one is 40c while the other one is 80c.

No, they are all 80 , two of them came with the mainboard, the so
called "green" connectors as gigabyte calls them, the other one was an
80c with blue connector.

I dunno, I guess I should review my "spare" parts and see what's
really useable from this pile of hardware I have here.

But hey, one thing is for sure, and I think it's a positive thing.
If libata sees problems or seems to have problems, you can be 99% sure
there IS a problem, where the legacy drivers just act all happy and
keep you thinking everything is peachy and all.

So again, thumbs up for libata.

Patrick

Re: Fwd: [LIBATA] drives not detected

[Bartlomiej Zolnierkiewicz]

On Saturday 24 February 2007, Patrick Ale wrote:
> On 2/24/07, Tejun Heo <htejun@gmail.com> wrote:
> > Patrick Ale wrote:
> 
> 
> >
> > The upper one is 40c while the other one is 80c.
> 
> No, they are all 80 , two of them came with the mainboard, the so
> called "green" connectors as gigabyte calls them, the other one was an
> 80c with blue connector.
> 
> I dunno, I guess I should review my "spare" parts and see what's
> really useable from this pile of hardware I have here.
> 
> But hey, one thing is for sure, and I think it's a positive thing.
> If libata sees problems or seems to have problems, you can be 99% sure
> there IS a problem, where the legacy drivers just act all happy and
> keep you thinking everything is peachy and all.

I'm really sorry that legacy drivers just work.  I will try harder. ;-)

The real problem is that while legacy drivers contain a ton of workarounds
and fixes for problems like that they often lacks the documentation about it.

> So again, thumbs up for libata.
> 
> Patrick

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

Haha,

Well, I am not sure if they "work" as in, do the right thing.
I don't know if you had a chance to look at my dmesg-es but acording
to the legacy IDE drivers my both disks were 2048 Peta byte each, I
wish I had this kind of storage :P

Btw, I just bought myself 2 500GB sata disks, care for any tests to be
executed? Are there things in particulair you guys would like to have
tested?

Patrick

On 2/24/07, Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
>
> On Saturday 24 February 2007, Patrick Ale wrote:
> > On 2/24/07, Tejun Heo <htejun@gmail.com> wrote:
> > > Patrick Ale wrote:
> >
> >
> > >
> > > The upper one is 40c while the other one is 80c.
> >
> > No, they are all 80 , two of them came with the mainboard, the so
> > called "green" connectors as gigabyte calls them, the other one was an
> > 80c with blue connector.
> >
> > I dunno, I guess I should review my "spare" parts and see what's
> > really useable from this pile of hardware I have here.
> >
> > But hey, one thing is for sure, and I think it's a positive thing.
> > If libata sees problems or seems to have problems, you can be 99% sure
> > there IS a problem, where the legacy drivers just act all happy and
> > keep you thinking everything is peachy and all.
>
> I'm really sorry that legacy drivers just work.  I will try harder. ;-)
>
> The real problem is that while legacy drivers contain a ton of workarounds
> and fixes for problems like that they often lacks the documentation about
> it.
>
> > So again, thumbs up for libata.
> >
> > Patrick
>

Re: Fwd: [LIBATA] drives not detected

[Bartlomiej Zolnierkiewicz]

Hi,

On Saturday 24 February 2007, Patrick Ale wrote:
> Haha,
> 
> Well, I am not sure if they "work" as in, do the right thing.
> I don't know if you had a chance to look at my dmesg-es but acording
> to the legacy IDE drivers my both disks were 2048 Peta byte each, I
> wish I had this kind of storage :P

This is the newest feature! ;-)

Now a bit more seriously - I didn't have a chance to look at the problem
before since it was posted under this thread ("Re: Fwd: [LIBATA] drives not
detected") and I wasn't on cc: list (please always cc: me on IDE driver
related problems).

Now looking at the problem:

> hde: max request size: 512KiB
> hde: Host Protected Area detected.
>         current capacity is 234441648 sectors (120034 MB)
>         native  capacity is 274103470214064 sectors (140340976749 MB)

We know that drive uses LBA48 from the max request size and that
WIN_READ_NATIVE_MAX_EXT command is used to read maximum native capacity.

Digging deeper into the code and looking at the reported capacity values:

0xf94baff94bb0 == 274103470214064
0x00000df94bb0 == 234441648 (== the native capacity for this drive)

it turns out that for some reason HOB (LBA48) hcyl/lcyl/sector register
values are incorrectly reported as 0xf94baf (instead of 0x00000d)
and are actually equivalent to the reported values of non-LBA48 registers
(0xf94baf became 0xf94bb0 because idedisk_read_native_max_address_ext()
adds 1 to the computed address).

Googling returns me some correct dmesgs for this particular drive
(WDC WD1200JB-00EVA0) with Promise controllers so I presume that the drive
reports correct info and that this is not some problem caused by drive/host
combination.  Therefore I think that the most likely causes are:

* you have tried IDE driver _after_ first removing libata driver module,
  could you please retry _without_ libata loaded et all (yes it can
  influence the behavior of the driver/hardware since libata resets
  drives and reprograms the controller/drives)

* "gcc version 3.4.6 (Gentoo 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.10)"
  gcc looks to be heavily modified from the mainstream version and it might
  be possible that this compiler is buggy and some code gets miscompiled,
  is it possible to try some newer/unmodified version?

* pdc202xx_new rewrite which happend in 2.6.20 has some side-effects
  (highly unlikely since the code was in -mm for months and is the same
  as used in libata version of the driver), could you try 2.6.19?

> hde: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
> hde: task_no_data_intr: error=0x04 { DriveStatusError }
> ide: failed opcode was: 0x37

IDE driver fails to set new (bogus) capacity and continues operation

> hde: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)

device is configured correctly

> hde: cache flushes supported
>  hde: hde1

partition table is scanned and since the current capacity == the native
capacity there should be absolutely no influence on normal operation
(reading/writing data), if it is not true I would like to hear about
the problems encountered.

The same situation is with hdf drive - ST3120022A since it has exactly
the same native capacity as WD1200JB and is also using the full capacity
by default (HPA is disabled).

Thanks,
Bart

> Btw, I just bought myself 2 500GB sata disks, care for any tests to be
> executed? Are there things in particulair you guys would like to have
> tested?
> 
> Patrick
> 
> On 2/24/07, Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> >
> > On Saturday 24 February 2007, Patrick Ale wrote:
> > > On 2/24/07, Tejun Heo <htejun@gmail.com> wrote:
> > > > Patrick Ale wrote:
> > >
> > >
> > > >
> > > > The upper one is 40c while the other one is 80c.
> > >
> > > No, they are all 80 , two of them came with the mainboard, the so
> > > called "green" connectors as gigabyte calls them, the other one was an
> > > 80c with blue connector.
> > >
> > > I dunno, I guess I should review my "spare" parts and see what's
> > > really useable from this pile of hardware I have here.
> > >
> > > But hey, one thing is for sure, and I think it's a positive thing.
> > > If libata sees problems or seems to have problems, you can be 99% sure
> > > there IS a problem, where the legacy drivers just act all happy and
> > > keep you thinking everything is peachy and all.
> >
> > I'm really sorry that legacy drivers just work.  I will try harder. ;-)
> >
> > The real problem is that while legacy drivers contain a ton of workarounds
> > and fixes for problems like that they often lacks the documentation about
> > it.
> >
> > > So again, thumbs up for libata.
> > >
> > > Patrick
> >
> 

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

> Thanks,

Hey,

Being serious has never been one of my strongest sides ;-)

Anyway, I will do the tests tomorrow, even tho I doubt if I'll run
into the problems I had, cause really.. since i changed the cable this
morning everything seems to work like a charm :)

Assuming by your name you're either in Poland, Croatia or a country
near, which makes us a maximum of one timezone away (I'm in a city
near Amsterdam), so when I write a mail with my findings we wont
suffer from big timezone delays which makes you read the mails 12
hours later or something.

Unless you have a *gasp* real like, in which case I envy you and wish
I were you :P


Thanks for all your help guys and girls,

Patrick

Re: Fwd: [LIBATA] drives not detected

[Bartlomiej Zolnierkiewicz]

On Saturday 24 February 2007, Patrick Ale wrote:
> > Thanks,
> 
> Hey,
> 
> Being serious has never been one of my strongest sides ;-)
> 
> Anyway, I will do the tests tomorrow, even tho I doubt if I'll run
> into the problems I had, cause really.. since i changed the cable this
> morning everything seems to work like a charm :)

OK but please give it a try anyway.

> Assuming by your name you're either in Poland, Croatia or a country
> near, which makes us a maximum of one timezone away (I'm in a city
> near Amsterdam), so when I write a mail with my findings we wont
> suffer from big timezone delays which makes you read the mails 12
> hours later or something.

Poland here so yes exactly the same timezone.

> Unless you have a *gasp* real like, in which case I envy you and wish
> I were you :P

s/real like/real life/ ?  [ or did you mean something else ]

I'm trying hard to still have some. :)

> Thanks for all your help guys and girls,
> 
> Patrick

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/24/07, Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:

Hoi and good afternoon :)

Okay so... this is my dmesg with the legacy IDE drivers loaded.
Please note that I still use libata for my boot drive but that the
current vs native capacity errors disapeared *sniff*, no petabytes
after all!


PDC20276: chipset revision 1
PDC20276: PLL input clock is 33542 kHz
PDC20276: 100% native mode on irq 19
    ide2: BM-DMA at 0xc800-0xc807, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0xc808-0xc80f, BIOS settings: hdg:pio, hdh:pio
Probing IDE interface ide2...
8139too Fast Ethernet driver 0.9.28
Linux video capture interface: v2.00
hde: Maxtor 6Y160P0, ATA DISK drive
cx2388x v4l2 driver version 0.0.6 loaded
hdf: WDC WD1200JB-00DUA3, ATA DISK drive
ide2 at 0xb800-0xb807,0xbc02 on irq 19
Probing IDE interface ide3...
hdg: WDC WD1200JB-00EVA0, ATA DISK drive
hdh: ST3120022A, ATA DISK drive
ide3 at 0xc000-0xc007,0xc402 on irq 19
sata_sil 0000:00:08.0: version 2.0
ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 17 (level, low) -> IRQ 20
ata3: SATA max UDMA/100 cmd 0xF883A080 ctl 0xF883A08A bmdma 0xF883A000 irq 20
ata4: SATA max UDMA/100 cmd 0xF883A0C0 ctl 0xF883A0CA bmdma 0xF883A008 irq 20
scsi2 : sata_sil
hde: max request size: 512KiB
hde: 320173056 sectors (163928 MB) w/7936KiB Cache, CHS=19929/255/63, UDMA(133)
hde: cache flushes supported
 hde: hde1
hdf: max request size: 512KiB
hdf: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)
hdf: cache flushes supported
 hdf: hdf1
hdg: max request size: 512KiB
hdg: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)
hdg: cache flushes supported
 hdg: hdg1
hdh: max request size: 512KiB
hdh: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100)
hdh: cache flushes supported
 hdh: hdh1



Patrick

Re: Fwd: [LIBATA] drives not detected

[Bartlomiej Zolnierkiewicz]

On Sunday 25 February 2007, Patrick Ale wrote:
> On 2/24/07, Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> 
> Hoi and good afternoon :)

Hey!

> Okay so... this is my dmesg with the legacy IDE drivers loaded.
> Please note that I still use libata for my boot drive but that the
> current vs native capacity errors disapeared *sniff*, no petabytes
> after all!

Could you verify that loading pata_pdc2027xx module first,
then unloading it and loading pdc2027xx_new driver also works?

If it does then we can probably blame the bad capacity problem on
some hardware problem fixed by replacing cables...

Thanks,
Bart

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/25/07, Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
>
>
> If it does then we can probably blame the bad capacity problem on
> some hardware problem fixed by replacing cables...

Yea I can do that, however, when my natve capacity was in the peta
bytes the pata_pdc207x module didnt exist either if I recall
correctly.

Anyway, I will let you know :)


Patrick

Re: Fwd: [LIBATA] drives not detected

[Patrick Ale]

On 2/25/07, Patrick Ale <patrick.ale@gmail.com> wrote:
> On 2/25/07, Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:

Dobri dan (I think, I am learning croatian and got told by a friend
this is the polish way of saying it).

Anyway,

I guess it will take a bit before I can do this test for you,
regarding the loading pata_pdc207x and all.

md3 : active raid1 sdc1[2] sdb1[0]
      117218176 blocks [2/1] [U_]
      [======>..............]  recovery = 31.8% (37313792/117218176)
finish=2503.2min speed=531K/sec


A while a go I had a southbridge that wasnt too happy about the fact
that the fan wasnt running for some weeks allready, I guess I am
feeling the pain for it now. Lot's of "Port is slow, please be
patient" warnings.

Good thing is: the disk stays in UDMA100 now, instead of dropping to
PIO mode 1. As soon as i can replace the disk, I will do the tests for
you.

So as the dmesg says: be patient :P


Thanks again for all your help,

Patrick