Re: SATA driver sata_sil24

Re: SATA driver sata_sil24

[Richard Mawson]

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

Tejun,

On Thu, Apr 22, 2010 at 12:09:00PM +0200, Tejun Heo wrote:
> > I'm having difficulty with the system locking up as I load the module,
> > and I wondered whether this chip has been seen to actually work with
> > this driver? Perhaps there is a good reason for not mentioning this
> > chipset in the discription?
> 
> Yeap, they should work.  They're just different flavors of about the
> same chip.  How does it lock up?  Which kernel version?  Does the
> kernel complain about anything?

Initially this was a problem on debian testing 2.6.26-2-xen-686 and I didn't
investigate any more than to blacklist the module. The symptom with this was
that the keyboard was unresponsive.

I've briefly tried debian unstable's 2.6.32-4-xen-686.
All I tried was manually loading the module in single user mode. This printed
to the console a line including the PCI slot occupied by the card, then seemed
to be hung. The keyboard was still responsive (ctl-c would display ^C on the
console for example, but it was stuck in kernel space at a guess so the signal
wasn't delivered?) -- I then gave up. I didn't look at dmesg as I was in single
user mode and couldn't easily.

As you suggest that this should work, I will persist and see if I can find out
the problem. I wanted to avoid flogging a dead horse..

If you have any suggestions as to what the likely problem is, or things to look
for I am all ears.

regards,

Richard

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: SATA driver sata_sil24

[Tejun Heo]

Hello,

On 04/22/2010 02:17 PM, Richard Mawson wrote:
> As you suggest that this should work, I will persist and see if I can find out
> the problem. I wanted to avoid flogging a dead horse..

The hourse is very alive. :-)

> If you have any suggestions as to what the likely problem is, or
> things to look for I am all ears.

Please try non-xen vanialla kernel and report the failing kernel log.

Thanks.

-- 
tejun

Re: SATA driver sata_sil24

[Richard Mawson]

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

Tejun,

On Thu, Apr 22, 2010 at 03:33:55PM +0200, Tejun Heo wrote:
> > If you have any suggestions as to what the likely problem is, or
> > things to look for I am all ears.
> 
> Please try non-xen vanialla kernel and report the failing kernel log.

I have compiled 2.6.33-2, and the same thing happens.
That is, modprobe sata_sil24 prints one message to the console suggesting the PCI slot,
then freezes the system.

Unfortunately it doesn't seem to have managed to write anything to messages/kernel.log,
which is on a p-ata disk.

I managed to hand copy some of the output from alt-sysrq-t which looks like it includes the
stack running as a result of the modprobe -- does this help to explain where the problem is?
This was manually copied, so there might be a typo or two:

c03118f8 ? schedule+0x897/0x94e
c014406a ? ktime_get_ts+0xd7/0xdf
c0217b42 ? cfq_rb_erase+0x1b/0x2a
c021f449 ? number+0x149/0x20e
c023a9cb ? vgacon_scroll+0x180/0x19a
c0194e0c ? __insert_vmap_area+0x5e/0x96
c017fac3 ? __alloc_pages_nodemask+0xe2/0x4ec
c019b409 ? cache_alloc_refill+0x63/0x417
c02995c9 ? pci_conf1_write+0xb2/0xc0
c029a9fb ? raw_pci_write+0x4e/0x56
c029aa40 ? pci_write+0x1c/0x21
c0228a3e ? pci_bus_write_config_dword+0x46/0x50
c022ae0c ? pcie_set_readrq+0x8c/0x9e
f9f185bc ? sil24_init_one+0x1ax/0x21a [sata_sil24]
c022d899 ? local_pci_probe+0xb/0xc
c022de7d ? pci_device_probe+0x41/0x63
c0287489 ? driver_probe_device+0x76/0xfe
c0287451 ? __driver_attach+0x40/0x5b
c0286dcd ? bus_for_each_dev0x37/0x5f
c0287270 ? driver_attach+0x11/0x13
c0287411 ? __driver_attach+0x0/0x5b
c0286852 ? bus_add_driver+0xd6/0x201
c028766b ? driver_register+0x87/0xe0
c022e050 ? __pci_register_driver+0x33/0x89
f9f1d000 ? sil24_init+0x0/0x14 [sata_sil24]
c010112d ? do_one_initcall+0x44/0x120
c014f1c2 ? sys_init_module+0xa7/0x1d7
c03130f5 ? syscall_call+0x7/0xb

I don't know that it is relevant, but the pcie card is plugged into a pci-pcie
converter card.


Let me know if there is anything else I can supply to help analyse this (anything
I do will have to be in the next couple of days as thats all the time I have to
return the goods for a refund!!).

-- 
Richard Mawson
Mawson IT Services

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: SATA driver sata_sil24

[Robert Hancock]

On 04/22/2010 04:33 PM, Richard Mawson wrote:
> Tejun,
>
> On Thu, Apr 22, 2010 at 03:33:55PM +0200, Tejun Heo wrote:
>>> If you have any suggestions as to what the likely problem is, or
>>> things to look for I am all ears.
>>
>> Please try non-xen vanialla kernel and report the failing kernel log.
>
> I have compiled 2.6.33-2, and the same thing happens.
> That is, modprobe sata_sil24 prints one message to the console suggesting the PCI slot,
> then freezes the system.
>
> Unfortunately it doesn't seem to have managed to write anything to messages/kernel.log,
> which is on a p-ata disk.
>
> I managed to hand copy some of the output from alt-sysrq-t which looks like it includes the
> stack running as a result of the modprobe -- does this help to explain where the problem is?
> This was manually copied, so there might be a typo or two:
>
> c03118f8 ? schedule+0x897/0x94e
> c014406a ? ktime_get_ts+0xd7/0xdf
> c0217b42 ? cfq_rb_erase+0x1b/0x2a
> c021f449 ? number+0x149/0x20e
> c023a9cb ? vgacon_scroll+0x180/0x19a
> c0194e0c ? __insert_vmap_area+0x5e/0x96
> c017fac3 ? __alloc_pages_nodemask+0xe2/0x4ec
> c019b409 ? cache_alloc_refill+0x63/0x417
> c02995c9 ? pci_conf1_write+0xb2/0xc0
> c029a9fb ? raw_pci_write+0x4e/0x56
> c029aa40 ? pci_write+0x1c/0x21
> c0228a3e ? pci_bus_write_config_dword+0x46/0x50
> c022ae0c ? pcie_set_readrq+0x8c/0x9e
> f9f185bc ? sil24_init_one+0x1ax/0x21a [sata_sil24]
> c022d899 ? local_pci_probe+0xb/0xc
> c022de7d ? pci_device_probe+0x41/0x63
> c0287489 ? driver_probe_device+0x76/0xfe
> c0287451 ? __driver_attach+0x40/0x5b
> c0286dcd ? bus_for_each_dev0x37/0x5f
> c0287270 ? driver_attach+0x11/0x13
> c0287411 ? __driver_attach+0x0/0x5b
> c0286852 ? bus_add_driver+0xd6/0x201
> c028766b ? driver_register+0x87/0xe0
> c022e050 ? __pci_register_driver+0x33/0x89
> f9f1d000 ? sil24_init+0x0/0x14 [sata_sil24]
> c010112d ? do_one_initcall+0x44/0x120
> c014f1c2 ? sys_init_module+0xa7/0x1d7
> c03130f5 ? syscall_call+0x7/0xb
>
> I don't know that it is relevant, but the pcie card is plugged into a pci-pcie
> converter card.
>
>
> Let me know if there is anything else I can supply to help analyse this (anything
> I do will have to be in the next couple of days as thats all the time I have to
> return the goods for a refund!!).

Hmm, that seems like this line in drivers/ata/sata_sil24.c:

         /* Set max read request size to 4096.  This slightly increases
          * write throughput for pci-e variants.
          */
         pcie_set_readrq(pdev, 4096);

Can you try commenting out or deleting that line and rebuilding, and see 
if things work better? That's not really a solution, but if it worked, 
it would indicate there's something about the system configuration with 
that converter card installed that explodes when trying to set the max 
read request size. In that case can you post the output of "lspci -vv" 
and the full dmesg boot log?

Re: SATA driver sata_sil24

[Richard Mawson]

[-- Attachment #1.1: Type: text/plain, Size: 1039 bytes --]

On Thu, Apr 22, 2010 at 09:23:10PM -0600, Robert Hancock wrote:
> Hmm, that seems like this line in drivers/ata/sata_sil24.c:
>
>         /* Set max read request size to 4096.  This slightly increases
>          * write throughput for pci-e variants.
>          */
>         pcie_set_readrq(pdev, 4096);
>
> Can you try commenting out or deleting that line and rebuilding, and see  
> if things work better? That's not really a solution, but if it worked,  
> it would indicate there's something about the system configuration with  
> that converter card installed that explodes when trying to set the max  
> read request size. In that case can you post the output of "lspci -vv"  
> and the full dmesg boot log?

This did not solve the problem -- it did stop the alt-sysrq-t trick from working
though, so it changed something. Is there an easy way to get a crashdump -- does
it require patching the kernel? I've not done this before.

I've attached dmesg and lspci output.

-- 
Richard Mawson
Mawson IT Services

[-- Attachment #1.2: dmesg_2.6.33.2 --]
[-- Type: text/plain, Size: 22744 bytes --]

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.33.2 (root@dom0.mawsonit.co.uk) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Thu Apr 22 19:06:15 UTC 2010
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
[    0.000000]  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 00000000bfffb000 (usable)
[    0.000000]  BIOS-e820: 00000000bfffb000 - 00000000bffff000 (ACPI data)
[    0.000000]  BIOS-e820: 00000000bffff000 - 00000000c0000000 (ACPI NVS)
[    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
[    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
[    0.000000] Notice: NX (Execute Disable) protection missing in CPU or disabled in BIOS!
[    0.000000] DMI 2.3 present.
[    0.000000] last_pfn = 0xbfffb max_arch_pfn = 0x1000000
[    0.000000] MTRR default type: uncachable
[    0.000000] MTRR fixed ranges enabled:
[    0.000000]   00000-9FFFF write-back
[    0.000000]   A0000-BFFFF uncachable
[    0.000000]   C0000-C7FFF write-protect
[    0.000000]   C8000-EFFFF uncachable
[    0.000000]   F0000-FFFFF write-protect
[    0.000000] MTRR variable ranges enabled:
[    0.000000]   0 base 000000000 mask F80000000 write-back
[    0.000000]   1 base 080000000 mask FC0000000 write-back
[    0.000000]   2 disabled
[    0.000000]   3 disabled
[    0.000000]   4 disabled
[    0.000000]   5 disabled
[    0.000000]   6 disabled
[    0.000000]   7 disabled
[    0.000000] PAT not supported by CPU.
[    0.000000] initial memory mapped : 0 - 00a00000
[    0.000000] found SMP MP-table at [c00f5270] f5270
[    0.000000] init_memory_mapping: 0000000000000000-00000000379fe000
[    0.000000]  0000000000 - 0000200000 page 4k
[    0.000000]  0000200000 - 0037800000 page 2M
[    0.000000]  0037800000 - 00379fe000 page 4k
[    0.000000] kernel direct mapping tables up to 379fe000 @ 7000-d000
[    0.000000] RAMDISK: 7f899000 - 7ffef9d1
[    0.000000] Allocated new RAMDISK: 004e9000 - 00c3f9d1
[    0.000000] Move RAMDISK from 000000007f899000 - 000000007ffef9d0 to 004e9000 - 00c3f9d0
[    0.000000] ASUS CUR-DLS detected: force use of acpi=ht
[    0.000000] ACPI: RSDP 000f6250 00014 (v00 ASUS  )
[    0.000000] ACPI: RSDT bfffb000 00030 (v01 ASUS   CUR-DLS  30303031 MSFT 31313031)
[    0.000000] ACPI: FACP bfffb100 00074 (v01 ASUS   CUR-DLS  30303031 MSFT 31313031)
[    0.000000] ACPI: DSDT bfffb180 032BD (v01   ASUS CUR-DLS  00001000 MSFT 0100000B)
[    0.000000] ACPI: FACS bffff000 00040
[    0.000000] ACPI: BOOT bfffb040 00028 (v01 ASUS   CUR-DLS  30303031 MSFT 31313031)
[    0.000000] ACPI: APIC bfffb080 00068 (v01 ASUS   CUR-DLS  30303031 MSFT 31313031)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] 2181MB HIGHMEM available.
[    0.000000] 889MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 379fe000
[    0.000000]   low ram: 0 - 379fe000
[    0.000000]   node 0 low ram: 00000000 - 379fe000
[    0.000000]   node 0 bootmap 00009000 - 0000ff40
[    0.000000] (14 early reservations) ==> bootmem [0000000000 - 00379fe000]
[    0.000000]   #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
[    0.000000]   #1 [0000001000 - 0000002000]    EX TRAMPOLINE ==> [0000001000 - 0000002000]
[    0.000000]   #2 [0000100000 - 00004e2808]    TEXT DATA BSS ==> [0000100000 - 00004e2808]
[    0.000000]   #3 [00004e3000 - 00004e8150]              BRK ==> [00004e3000 - 00004e8150]
[    0.000000]   #4 [00000f5280 - 0000100000]    BIOS reserved ==> [00000f5280 - 0000100000]
[    0.000000]   #5 [00000f5270 - 00000f5280]     MP-table mpf ==> [00000f5270 - 00000f5280]
[    0.000000]   #6 [000009f000 - 00000f4e60]    BIOS reserved ==> [000009f000 - 00000f4e60]
[    0.000000]   #7 [00000f4f7c - 00000f5270]    BIOS reserved ==> [00000f4f7c - 00000f5270]
[    0.000000]   #8 [00000f4e60 - 00000f4f7c]     MP-table mpc ==> [00000f4e60 - 00000f4f7c]
[    0.000000]   #9 [0000002000 - 0000003000]       TRAMPOLINE ==> [0000002000 - 0000003000]
[    0.000000]   #10 [0000003000 - 0000007000]      ACPI WAKEUP ==> [0000003000 - 0000007000]
[    0.000000]   #11 [0000007000 - 0000009000]          PGTABLE ==> [0000007000 - 0000009000]
[    0.000000]   #12 [00004e9000 - 0000c3f9d1]      NEW RAMDISK ==> [00004e9000 - 0000c3f9d1]
[    0.000000]   #13 [0000009000 - 0000010000]          BOOTMAP ==> [0000009000 - 0000010000]
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000000 -> 0x00001000
[    0.000000]   Normal   0x00001000 -> 0x000379fe
[    0.000000]   HighMem  0x000379fe -> 0x000bfffb
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[2] active PFN ranges
[    0.000000]     0: 0x00000000 -> 0x000000a0
[    0.000000]     0: 0x00000100 -> 0x000bfffb
[    0.000000] On node 0 totalpages: 786331
[    0.000000] free_area_init_node: node 0, pgdat c0407440, node_mem_map c1001000
[    0.000000]   DMA zone: 32 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 3968 pages, LIFO batch:0
[    0.000000]   Normal zone: 1748 pages used for memmap
[    0.000000]   Normal zone: 221994 pages, LIFO batch:31
[    0.000000]   HighMem zone: 4364 pages used for memmap
[    0.000000]   HighMem zone: 554225 pages, LIFO batch:31
[    0.000000] Using APIC driver default
[    0.000000] ACPI: PM-Timer IO Port: 0xe408
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x03] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[    0.000000] Using ACPI for processor (LAPIC) configuration information
[    0.000000] Intel MultiProcessor Specification v1.4
[    0.000000]     Virtual Wire compatibility mode.
[    0.000000] MPTABLE: OEM ID: OEM00000
[    0.000000] MPTABLE: Product ID: PROD00000000
[    0.000000] MPTABLE: APIC at: 0xFEE00000
[    0.000000] I/O APIC #2 Version 17 at 0xFEC00000.
[    0.000000] I/O APIC #3 Version 17 at 0xFEC01000.
[    0.000000] Processors: 2
[    0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
[    0.000000] nr_irqs_gsi: 32
[    0.000000] Allocating PCI resources starting at c0000000 (gap: c0000000:3ec00000)
[    0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
[    0.000000] PERCPU: Embedded 13 pages/cpu @c2a00000 s29688 r0 d23560 u1048576
[    0.000000] pcpu-alloc: s29688 r0 d23560 u1048576 alloc=1*2097152
[    0.000000] pcpu-alloc: [0] 0 1 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 780187
[    0.000000] Kernel command line: root=/dev/mapper/vg0-dom0_root ro init=/bin/bash
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Enabling fast FPU save and restore... done.
[    0.000000] Enabling unmasked SIMD FPU exception support... done.
[    0.000000] Initializing CPU#0
[    0.000000] Initializing HighMem for node 0 (000379fe:000bfffb)
[    0.000000] Memory: 3107296k/3145708k available (2128k kernel code, 37100k reserved, 1005k data, 320k init, 2234356k highmem)
[    0.000000] virtual kernel memory layout:
[    0.000000]     fixmap  : 0xfff1f000 - 0xfffff000   ( 896 kB)
[    0.000000]     pkmap   : 0xffa00000 - 0xffc00000   (2048 kB)
[    0.000000]     vmalloc : 0xf81fe000 - 0xff9fe000   ( 120 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xf79fe000   ( 889 MB)
[    0.000000]       .init : 0xc0410000 - 0xc0460000   ( 320 kB)
[    0.000000]       .data : 0xc0314232 - 0xc040f688   (1005 kB)
[    0.000000]       .text : 0xc0100000 - 0xc0314232   (2128 kB)
[    0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[    0.000000] Hierarchical RCU implementation.
[    0.000000] RCU-based detection of stalled CPUs is enabled.
[    0.000000] NR_IRQS:512
[    0.000000] Console: colour VGA+ 80x25
[    0.000000] console [tty0] enabled
[    0.000000] Fast TSC calibration using PIT
[    0.000000] Detected 1399.808 MHz processor.
[    0.004010] Calibrating delay loop (skipped), value calculated using timer frequency.. 2799.61 BogoMIPS (lpj=5599232)
[    0.004253] Security Framework initialized
[    0.004345] SELinux:  Disabled at boot.
[    0.004448] Mount-cache hash table entries: 512
[    0.004827] Initializing cgroup subsys ns
[    0.004908] Initializing cgroup subsys cpuacct
[    0.004987] Initializing cgroup subsys devices
[    0.005137] Performance Events: p6 PMU driver.
[    0.005245] ... version:                0
[    0.005317] ... bit width:              32
[    0.005390] ... generic registers:      2
[    0.005462] ... value mask:             00000000ffffffff
[    0.005540] ... max period:             000000007fffffff
[    0.005617] ... fixed-purpose events:   0
[    0.008017] ... event mask:             0000000000000003
[    0.008104] Checking 'hlt' instruction... OK.
[    0.024600] Enabling APIC mode:  Flat.  Using 2 I/O APICs
[    0.024796] ExtINT not setup in hardware but reported by MP table
[    0.025090] BIOS bug, IO-APIC#1 ID 3 is already used!...
[    0.025169] ... fixing up to 1. (tell your hw vendor)
[    0.025470] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
[    0.028000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[    0.028000] ...trying to set up timer (IRQ0) through the 8259A ...
[    0.028000] ..... (found apic 0 pin 0) ...
[    0.069145] ....... works.
[    0.069212] CPU0: Intel(R) Pentium(R) III CPU family      1400MHz stepping 01
[    0.072000] Booting Node   0, Processors  #1 Ok.
[    0.008000] Initializing CPU#1
[    0.164098] Brought up 2 CPUs
[    0.164239] Total of 2 processors activated (5599.92 BogoMIPS).
[    0.166173] NET: Registered protocol family 16
[    0.168499] PCI: PCI BIOS revision 2.10 entry at 0xf0a80, last bus=2
[    0.168585] PCI: Using configuration type 1 for base access
[    0.172784] bio: create slab <bio-0> at 0
[    0.173163] ACPI: Interpreter disabled.
[    0.173537] vgaarb: loaded
[    0.174121] PCI: Probing PCI hardware
[    0.174195] PCI: Probing PCI hardware (bus 00)
[    0.174323] * The chipset may have PM-Timer Bug. Due to workarounds for a bug,
[    0.174325] * this clock source is slow. If you are sure your timer does not have
[    0.174328] * this bug, please use "acpi_pm_good" to disable the workaround
[    0.174667] * The chipset may have PM-Timer Bug. Due to workarounds for a bug,
[    0.174669] * this clock source is slow. If you are sure your timer does not have
[    0.174672] * this bug, please use "acpi_pm_good" to disable the workaround
[    0.175027] pci 0000:00:02.0: reg 10: [mem 0xfe000000-0xfe000fff]
[    0.175035] pci 0000:00:02.0: reg 14: [io  0xd800-0xd83f]
[    0.175043] pci 0000:00:02.0: reg 18: [mem 0xfd800000-0xfd8fffff]
[    0.175070] pci 0000:00:02.0: supports D1 D2
[    0.175074] pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot
[    0.175080] pci 0000:00:02.0: PME# disabled
[    0.175170] pci 0000:00:07.0: reg 10: [mem 0xfb000000-0xfbffffff]
[    0.175178] pci 0000:00:07.0: reg 14: [io  0xb800-0xb8ff]
[    0.175187] pci 0000:00:07.0: reg 18: [mem 0xfa800000-0xfa800fff]
[    0.175205] pci 0000:00:07.0: reg 30: [mem 0xfebe0000-0xfebfffff pref]
[    0.175222] pci 0000:00:07.0: supports D1 D2
[    0.175292] pci 0000:00:0f.1: reg 20: [io  0xb400-0xb40f]
[    0.175322] pci 0000:00:0f.2: reg 10: [mem 0xfa000000-0xfa000fff]
[    0.175423] pci 0000:01:00.0: reg 10: [mem 0xfd000000-0xfd00007f 64bit]
[    0.175445] pci 0000:01:00.0: reg 18: [mem 0xfc800000-0xfc801fff 64bit]
[    0.175458] pci 0000:01:00.0: reg 20: [io  0xc800-0xc87f]
[    0.175521] pci 0000:01:00.0: supports D1 D2
[    0.175568] pci 0000:00:05.0: PCI bridge to [bus 01-01]
[    0.175651] pci 0000:00:05.0:   bridge window [io  0xc000-0xcfff]
[    0.175658] pci 0000:00:05.0:   bridge window [mem 0xfc800000-0xfd7fffff]
[    0.176223] vgaarb: device added: PCI:0000:00:07.0,decodes=io+mem,owns=io+mem,locks=none
[    0.177029] PCI: Discovered peer bus 02
[    0.177237] pci 0000:02:05.0: reg 10: [io  0xb000-0xb0ff]
[    0.177249] pci 0000:02:05.0: reg 14: [mem 0xf9800000-0xf98003ff 64bit]
[    0.177261] pci 0000:02:05.0: reg 1c: [mem 0xf9000000-0xf9001fff 64bit]
[    0.177285] pci 0000:02:05.0: supports D1 D2
[    0.177313] pci 0000:02:05.1: reg 10: [io  0xa800-0xa8ff]
[    0.177325] pci 0000:02:05.1: reg 14: [mem 0xf8800000-0xf88003ff 64bit]
[    0.177337] pci 0000:02:05.1: reg 1c: [mem 0xf8000000-0xf8001fff 64bit]
[    0.177359] pci 0000:02:05.1: supports D1 D2
[    0.177656] pci 0000:00:0f.0: ServerWorks IRQ router [1166:0200]
[    0.177751] PCI: pci_cache_line_size set to 32 bytes
[    0.178147] Switching to clocksource tsc
[    0.180000] pnp: PnP ACPI: disabled
[    0.214619] pci 0000:00:05.0: PCI bridge to [bus 01-01]
[    0.214709] pci 0000:00:05.0:   bridge window [io  0xc000-0xcfff]
[    0.214795] pci 0000:00:05.0:   bridge window [mem 0xfc800000-0xfd7fffff]
[    0.214882] pci 0000:00:05.0:   bridge window [mem pref disabled]
[    0.214978] pci 0000:00:05.0: can't find IRQ for PCI INT A; probably buggy MP table
[    0.215103] pci_bus 0000:00: resource 0 [io  0x0000-0xffff]
[    0.215108] pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffffffffffff]
[    0.215114] pci_bus 0000:01: resource 0 [io  0xc000-0xcfff]
[    0.215119] pci_bus 0000:01: resource 1 [mem 0xfc800000-0xfd7fffff]
[    0.215125] pci_bus 0000:02: resource 0 [io  0x0000-0xffff]
[    0.215130] pci_bus 0000:02: resource 1 [mem 0x00000000-0xffffffffffffffff]
[    0.215252] NET: Registered protocol family 2
[    0.215478] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.216241] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.220894] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[    0.223431] TCP: Hash tables configured (established 131072 bind 65536)
[    0.223530] TCP reno registered
[    0.223615] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.223779] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.227881] NET: Registered protocol family 1
[    0.228046] pci 0000:00:02.0: Firmware left e100 interrupts enabled; disabling
[    0.228177] pci 0000:00:07.0: Boot video device
[    0.228220] PCI: CLS 32 bytes, default 32
[    0.228355] Trying to unpack rootfs image as initramfs...
[    0.628557] Freeing initrd memory: 7514k freed
[    0.649988] Simple Boot Flag at 0x3a set to 0x80
[    0.650418] platform rtc_cmos: registered platform RTC device (no PNP device found)
[    0.651396] audit: initializing netlink socket (disabled)
[    0.651507] type=2000 audit(1272031804.649:1): initialized
[    0.652023] highmem bounce pool size: 64 pages
[    0.652335] VFS: Disk quotas dquot_6.5.2
[    0.652466] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.652639] msgmni has been set to 1721
[    0.653112] alg: No test for stdrng (krng)
[    0.653378] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    0.653496] io scheduler noop registered
[    0.653569] io scheduler deadline registered
[    0.653674] io scheduler cfq registered (default)
[    0.661906] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.662232] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    0.662529] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[    0.667436] brd: module loaded
[    0.667852] PNP: No PS/2 controller found. Probing ports directly.
[    0.918282] serio: i8042 KBD port at 0x60,0x64 irq 1
[    0.918744] mice: PS/2 mouse device common for all mice
[    0.919178] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[    0.919303] rtc0: alarms up to one day, 114 bytes nvram
[    0.919465] cpuidle: using governor ladder
[    0.919545] No iBFT detected.
[    0.920198] TCP cubic registered
[    0.920270] NET: Registered protocol family 17
[    0.920360] Using IPI No-Shortcut mode
[    0.920754] registered taskstats version 1
[    0.921142] rtc_cmos rtc_cmos: setting system clock to 2010-04-23 14:10:06 UTC (1272031806)
[    0.921354] Freeing unused kernel memory: 320k freed
[    0.940036] input: AT Translated Set 2 keyboard as /class/input/input0
[    1.450556] SCSI subsystem initialized
[    1.475051] sym53c8xx 0000:02:05.0: PCI->APIC IRQ transform: INT A -> IRQ 24
[    1.510788] Uniform Multi-Platform E-IDE driver
[    1.561525] serverworks 0000:00:0f.1: IDE controller (0x1166:0x0211 rev 0x00)
[    1.561670] serverworks 0000:00:0f.1: not 100% native mode: will probe irqs later
[    1.561793]     ide0: BM-DMA at 0xb400-0xb407
[    1.561877]     ide1: BM-DMA at 0xb408-0xb40f
[    1.561958] Probing IDE interface ide0...
[    1.583147] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[    1.583238] e100: Copyright(c) 1999-2006 Intel Corporation
[    1.587617] usbcore: registered new interface driver usbfs
[    1.587788] usbcore: registered new interface driver hub
[    1.610775] usbcore: registered new device driver usb
[    1.615546] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.625669] sym0: <896> rev 0x7 at pci 0000:02:05.0 irq 24
[    1.627878] sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking
[    1.627962] sym0: open drain IRQ line driver, using on-chip SRAM
[    1.628044] sym0: using LOAD/STORE-based firmware.
[    1.628119] sym0: handling phase mismatch from SCRIPTS.
[    1.629948] sym0: SCSI BUS has been reset.
[    1.635033] scsi0 : sym-2.2.3
[    1.635429] sym53c8xx 0000:02:05.1: PCI->APIC IRQ transform: INT B -> IRQ 25
[    1.785098] sym1: <896> rev 0x7 at pci 0000:02:05.1 irq 25
[    1.787248] sym1: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking
[    1.787332] sym1: open drain IRQ line driver, using on-chip SRAM
[    1.787413] sym1: using LOAD/STORE-based firmware.
[    1.787489] sym1: handling phase mismatch from SCRIPTS.
[    1.789983] sym1: SCSI BUS has been reset.
[    1.794387] scsi1 : sym-2.2.3
[    1.858305] hda: WDC WD3200JB-00KFA0, ATA DISK drive
[    2.194219] hdb: WDC WD3200JB-00KFA0, ATA DISK drive
[    2.194407] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[    2.194481] hda: MWDMA2 mode selected
[    2.194631] hdb: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[    2.194705] hdb: MWDMA2 mode selected
[    2.194862] Probing IDE interface ide1...
[    2.482438] hdc: WDC WD2500SB-01KBA0, ATA DISK drive
[    2.818358] hdd: WDC WD2500SB-01KBA0, ATA DISK drive
[    2.818493] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[    2.819714] hdc: MWDMA2 mode selected
[    2.821047] hdd: host max PIO4 wanted PIO255(auto-tune) selected PIO4
[    2.822292] hdd: MWDMA2 mode selected
[    2.823668] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[    2.823842] ide1 at 0x170-0x177,0x376 on irq 15
[    2.824294] e100 0000:00:02.0: PCI->APIC IRQ transform: INT A -> IRQ 20
[    2.847348] e100 0000:00:02.0: PME# disabled
[    2.847798] e100: eth0: e100_probe: addr 0xfe000000, irq 20, MAC addr 00:e0:18:51:e6:be
[    2.847994] ohci_hcd 0000:00:0f.2: PCI->APIC IRQ transform: INT A -> IRQ 30
[    2.848094] ohci_hcd 0000:00:0f.2: OHCI Host Controller
[    2.848215] ohci_hcd 0000:00:0f.2: new USB bus registered, assigned bus number 1
[    2.848370] ohci_hcd 0000:00:0f.2: irq 30, io mem 0xfa000000
[    2.876989] libata version 3.00 loaded.
[    2.904429] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
[    2.904524] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.904639] usb usb1: Product: OHCI Host Controller
[    2.904715] usb usb1: Manufacturer: Linux 2.6.33.2 ohci_hcd
[    2.904795] usb usb1: SerialNumber: 0000:00:0f.2
[    2.905112] hub 1-0:1.0: USB hub found
[    2.905196] hub 1-0:1.0: 4 ports detected
[    2.952771] ide-gd driver 1.18
[    2.952913] hda: max request size: 512KiB
[    2.962567] hda: 625142448 sectors (320072 MB) w/8192KiB Cache, CHS=38913/255/63
[    2.962891] hda: cache flushes supported
[    2.963079]  hda: hda1 hda2
[    2.975367] hdb: max request size: 512KiB
[    2.986491] hdb: 625142448 sectors (320072 MB) w/8192KiB Cache, CHS=38913/255/63
[    2.986746] hdb: cache flushes supported
[    2.986906]  hdb: hdb1 hdb2
[    2.997934] hdc: max request size: 512KiB
[    3.023633] hdc: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63
[    3.025736] hdc: cache flushes supported
[    3.025886]  hdc: unknown partition table
[    3.040207] hdd: max request size: 512KiB
[    3.063660] hdd: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63
[    3.065779] hdd: cache flushes supported
[    3.065932]  hdd: unknown partition table
[    3.278485] usb 1-2: new low speed USB device using ohci_hcd and address 2
[    3.497208] md: raid1 personality registered for level 1
[    3.514623] md: md0 stopped.
[    3.603688] md: bind<hdb1>
[    3.604173] md: bind<hda1>
[    3.623974] raid1: raid set md0 active with 2 out of 2 mirrors
[    3.624095] md0: detected capacity change from 0 to 98566144
[    3.624699] md: md1 stopped.
[    3.624959]  md0: unknown partition table
[    3.781889] md: bind<hdb2>
[    3.782406] md: bind<hda2>
[    3.802355] raid1: raid set md1 active with 2 out of 2 mirrors
[    3.802519] md1: detected capacity change from 0 to 319971524608
[    3.803225] md: md2 stopped.
[    3.803531]  md1: unknown partition table
[    3.992177] md: bind<hdd>
[    3.997028] md: bind<hdc>
[    4.016906] raid1: raid set md2 active with 2 out of 2 mirrors
[    4.017027] md2: detected capacity change from 0 to 250059227136
[    4.017533]  md2: unknown partition table
[    4.164606] device-mapper: uevent: version 1.0.3
[    4.164968] device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@redhat.com
[    8.279579] ohci_hcd 0000:00:0f.2: Unlink after no-IRQ?  Controller is probably using the wrong IRQ.
[    8.675548] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[    8.676738] SGI XFS Quota Management subsystem
[    8.768197] XFS mounting filesystem dm-26
[    8.931046] Starting XFS recovery on filesystem: dm-26 (logdev: internal)
[    9.096115] Ending XFS recovery on filesystem: dm-26 (logdev: internal)

[-- Attachment #1.3: lspci_vv --]
[-- Type: text/plain, Size: 9280 bytes --]

00:00.0 Host bridge: Broadcom CNB20LE Host Bridge (rev 05)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Kernel modules: sworks-agp

00:00.1 Host bridge: Broadcom CNB20LE Host Bridge (rev 05)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 48, Cache Line Size: 32 bytes
	Kernel modules: sworks-agp

00:02.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 08)
	Subsystem: Intel Corporation EtherExpress PRO/100+ Server Adapter (PILA8470B)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (2000ns min, 14000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 20
	Region 0: Memory at fe000000 (32-bit, non-prefetchable) [size=4K]
	Region 1: I/O ports at d800 [size=64]
	Region 2: Memory at fd800000 (32-bit, non-prefetchable) [size=1M]
	Capabilities: [dc] 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-
	Kernel driver in use: e100
	Kernel modules: e100, eepro100

00:05.0 PCI bridge: Pericom Semiconductor Device e111 (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000c000-0000cfff
	Memory behind bridge: fc800000-fd7fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [80] PCI-X bridge device
		Secondary Status: 64bit- 133MHz- SCD- USC- SCO- SRD- Freq=conv
		Status: Dev=ff:1f.0 64bit- 133MHz- SCD- USC- SCO- SRD-
		Upstream: Capacity=16 CommitmentLimit=16
		Downstream: Capacity=16 CommitmentLimit=16
	Capabilities: [a8] Subsystem: Gammagraphx, Inc. Device 0000
	Capabilities: [b0] Express (v1) PCI/PCI-X Bridge, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE- FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- BrConfRtry-
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr+ UnsuppReq- AuxPwr+ TransPend+
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <1us
			ClockPM- Suprise- LLActRep+ BwNot-
		LnkCtl:	ASPM Disabled; Disabled- Retrain- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
	Capabilities: [d8] Vital Product Data <?>
	Capabilities: [f0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Kernel modules: shpchp

00:07.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. Device 802b
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (2000ns min), Cache Line Size: 32 bytes
	Region 0: Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: I/O ports at b800 [size=256]
	Region 2: Memory at fa800000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at febe0000 [disabled] [size=128K]
	Capabilities: [5c] 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:0f.0 ISA bridge: Broadcom OSB4 South Bridge (rev 50)
	Subsystem: Broadcom OSB4 South Bridge
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Kernel driver in use: piix4_smbus
	Kernel modules: i2c-piix4

00:0f.1 IDE interface: Broadcom OSB4 IDE Controller (prog-if 8a [Master SecP PriP])
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] [size=8]
	Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled] [size=1]
	Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] [size=8]
	Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled] [size=1]
	Region 4: I/O ports at b400 [size=16]
	Kernel driver in use: Serverworks_IDE
	Kernel modules: serverworks

00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 04) (prog-if 10 [OHCI])
	Subsystem: Broadcom OSB4/CSB5 OHCI USB Controller
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (20000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 30
	Region 0: Memory at fa000000 (32-bit, non-prefetchable) [size=4K]
	Kernel driver in use: ohci_hcd
	Kernel modules: ohci-hcd

01:00.0 Mass storage controller: Silicon Image, Inc. Sil 3531 [SATALink/SATARaid] Serial ATA Controller (rev 01)
	Subsystem: Silicon Image, Inc. Sil 3531 [SATALink/SATARaid] Serial ATA Controller
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 18
	Region 0: Memory at fd000000 (64-bit, non-prefetchable) [size=128]
	Region 2: Memory at fc800000 (64-bit, non-prefetchable) [size=8K]
	Region 4: I/O ports at c800 [size=128]
	Capabilities: [54] Power Management version 2
		Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [5c] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [70] Express (v1) Legacy Endpoint, MSI 00
		DevCap:	MaxPayload 1024 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 unlimited, L1 unlimited
			ClockPM- Suprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
	Kernel modules: sata_sil24

02:05.0 SCSI storage controller: LSI Logic / Symbios Logic 53C896/897 (rev 07)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 72 (4250ns min, 16000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 24
	Region 0: I/O ports at b000 [size=256]
	Region 1: Memory at f9800000 (64-bit, non-prefetchable) [size=1K]
	Region 3: Memory at f9000000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [40] 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-
	Kernel driver in use: sym53c8xx
	Kernel modules: sym53c8xx

02:05.1 SCSI storage controller: LSI Logic / Symbios Logic 53C896/897 (rev 07)
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 72 (4250ns min, 16000ns max), Cache Line Size: 32 bytes
	Interrupt: pin B routed to IRQ 25
	Region 0: I/O ports at a800 [size=256]
	Region 1: Memory at f8800000 (64-bit, non-prefetchable) [size=1K]
	Region 3: Memory at f8000000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [40] 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-
	Kernel driver in use: sym53c8xx
	Kernel modules: sym53c8xx


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: SATA driver sata_sil24

[Richard Mawson]

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

On Thu, Apr 22, 2010 at 09:23:10PM -0600, Robert Hancock wrote:
> Hmm, that seems like this line in drivers/ata/sata_sil24.c:
>
>         /* Set max read request size to 4096.  This slightly increases
>          * write throughput for pci-e variants.
>          */
>         pcie_set_readrq(pdev, 4096);
>
> Can you try commenting out or deleting that line and rebuilding, and see  
> if things work better? That's not really a solution, but if it worked,  
> it would indicate there's something about the system configuration with  
> that converter card installed that explodes when trying to set the max  
> read request size. In that case can you post the output of "lspci -vv"  
> and the full dmesg boot log?

Having put printk messages all over the driver, I see it currently locks up
during this readl call:

                /* Clear port RST */
                tmp = readl(port + PORT_CTRL_STAT);

.. but as this is clearly later on from the previously mentioned stack, I'm
starting to suspect that this is failing in random places when talking across
this pci-pcie bridge. Do you agree that this sounds plausible?

I did attempt to get a crash dump, but failed to get any joy from using the
nmi watchdog to trigger the use of the debug kernel in this state.

I will attempt using a different machine, hopefully tomorrow, but I have no
native pcie machines so can't eliminate the pci-pcie bridge being at fault.

Thanks for your help.

-- 
Richard Mawson
Mawson IT Services

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: SATA driver sata_sil24

[Robert Hancock]

On Fri, Apr 23, 2010 at 2:34 PM, Richard Mawson
<richard@crow.mawsonit.co.uk> wrote:
> On Thu, Apr 22, 2010 at 09:23:10PM -0600, Robert Hancock wrote:
>> Hmm, that seems like this line in drivers/ata/sata_sil24.c:
>>
>>         /* Set max read request size to 4096.  This slightly increases
>>          * write throughput for pci-e variants.
>>          */
>>         pcie_set_readrq(pdev, 4096);
>>
>> Can you try commenting out or deleting that line and rebuilding, and see
>> if things work better? That's not really a solution, but if it worked,
>> it would indicate there's something about the system configuration with
>> that converter card installed that explodes when trying to set the max
>> read request size. In that case can you post the output of "lspci -vv"
>> and the full dmesg boot log?
>
> Having put printk messages all over the driver, I see it currently locks up
> during this readl call:
>
>                /* Clear port RST */
>                tmp = readl(port + PORT_CTRL_STAT);
>
> .. but as this is clearly later on from the previously mentioned stack, I'm
> starting to suspect that this is failing in random places when talking across
> this pci-pcie bridge. Do you agree that this sounds plausible?

I suspect it's something like that - not sure what else could cause
things to explode at that point..

>
> I did attempt to get a crash dump, but failed to get any joy from using the
> nmi watchdog to trigger the use of the debug kernel in this state.
>
> I will attempt using a different machine, hopefully tomorrow, but I have no
> native pcie machines so can't eliminate the pci-pcie bridge being at fault.
>
> Thanks for your help.
>
> --
> Richard Mawson
> Mawson IT Services
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkvSBGYACgkQEqu+mbnN8VKZTgCeMu3flpdyVdp7smp8qaaJPGIp
> 8h8AnReBz04O1NVYqD16zLnYcnN9NNHZ
> =bANg
> -----END PGP SIGNATURE-----
>
>

Re: SATA driver sata_sil24

[Stan Hoeppner]

My reply-list plugin sometimes has problems.  Apologies for the double hit
to your inbox Robert.

Robert Hancock put forth on 4/23/2010 7:34 PM:
> On Fri, Apr 23, 2010 at 2:34 PM, Richard Mawson
> <richard@crow.mawsonit.co.uk> wrote:

>> .. but as this is clearly later on from the previously mentioned stack, I'm
>> starting to suspect that this is failing in random places when talking across
>> this pci-pcie bridge. Do you agree that this sounds plausible?
> 
> I suspect it's something like that - not sure what else could cause
> things to explode at that point..

Hay Richard, if you've not already, try booting with the eSATA cable _not_
connected to the HBA and see if that prevents the lock up.  If it boots,
make sure both the server and disk box PSUs are both plugged into the same
AC circuit, preferably the same UPS, and that all equipment shares the same
earth ground, and give it another go.  Having equipment like this on
different earth ground paths can cause issues like what you're seeing due to
voltage differences on the eSATA wire.  Or, at least, this used to occur on
occasion with external SCSI array boxen, so I'm guessing eSATA isn't immune
given the interconnect is copper, not fiber.

Replace the eSATA cable with a "known good" cable if you haven't already.
Just helping you dot all the Ts and cross all the Is.  I know I've
overlooked small "simple" stuff on at least more than one occasion--happens
to all of us at one point or another.

Would you mind supplying the specific branded server or mobo model # so I
can do some research on possible board and/or chipset errata, known bad
card/slot combinations, etc?

-- 
Stan

Re: SATA driver sata_sil24

[Richard Mawson]

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

Robert, Tejun,

On Fri, Apr 23, 2010 at 06:34:36PM -0600, Robert Hancock wrote:
> > Having put printk messages all over the driver, I see it currently locks up
> > during this readl call:
> >
> >                /* Clear port RST */
> >                tmp = readl(port + PORT_CTRL_STAT);
> >
> > .. but as this is clearly later on from the previously mentioned stack, I'm
> > starting to suspect that this is failing in random places when talking across
> > this pci-pcie bridge. Do you agree that this sounds plausible?
> 
> I suspect it's something like that - not sure what else could cause
> things to explode at that point..

Thank you for your help with this. I believe this was a hardware problem, as the same
pci-pcie converter with the same pcie sata adapter work perfectly in a different 
system (now why didn't I try that first..?).

-- 
Richard Mawson
Mawson IT Services

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: SATA driver sata_sil24

[Richard Mawson]

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

Apologies for not replying to the correct part of this thread,
but my server locked up loosing recent emails.. I think this
kind of suggests that the server has a hardware fault, so is
in-line for replacement.

In response to Stan Hoeppner (sorry, I don't have your email address),
the problem occurs with and without the sata cable plugged in. The
motherboard is a CUR-DLS for your interest.

-- 
Richard Mawson
Mawson IT Services

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: SATA driver sata_sil24

[Richard Mawson]

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

Stan,

On Sun, Apr 25, 2010 at 09:53:06PM -0500, Stan Hoeppner wrote:
> Did I read correctly in a previous post that you're using some kind of
> PCI<->PCIe adapter?  Could you post the manufacturer and part/model # of
> this adapter?  Could you also post the manufacturer/model of the SATA card?

This is all the info I have on it:

http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItemVersion&item=320473532811

The sata card has no real distinguishing features except the chip used - SI 3531.

-- 
Richard Mawson
Mawson IT Services

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: SATA driver sata_sil24

[Richard Mawson]

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

On Mon, Apr 26, 2010 at 05:15:42AM -0500, Stan Hoeppner wrote:
> > http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItemVersion&item=320473532811
> 
> Won't let me view it without signing in.  And I don't have an Ebay UK
> account. :(

sorry about that.. This is the text of the advert:

ADVERT:The PCI to PCI Express Adapter card lets you use low profile PCIe expansion cards in a server/desktop motherboard PCI slot.
ADVERT:The adapter connects through a 32-bit PCI slot to provide a low profile PCIe x1 slot in its place; a spare, full size bracket is
ADVERT: included for installation in larger desktop or server expansion slots that can accomodate a full-sized card.
ADVERT:
ADVERT:The PCI to PCI Express Adapter features an innovative bracket design that adapts and secures the low profile PCI Express card
ADVERT:into the converted slot, ensuring a versatile and economical solution for extending the usability of older PCI motherboards or using
ADVERT:low profile PCIe cards that do not have PCI equivalents.
ADVERT:
ADVERT:Features
ADVERT:
ADVERT:•      Innovative Bracket Design Adapts and Secures the Existing Low Profile Bracket of the PCI Card
ADVERT:•      Compliant with PCI-to-PCIe Bridge Architecture spec Revision 1.2
ADVERT:•      Compliant with PCI BUS Power Management Rev 1.1
ADVERT:•      Compliant with PCI Express to PCI/PCI-X Bridge spec 1.0
ADVERT:•      PCI Express base spec 1.0a compliant
ADVERT:•      Compliant with PCI spec Revision 2.3
ADVERT:•      No Drivers or software required
ADVERT:
ADVERT:
ADVERT:Broad operating system support including device drivers for
ADVERT:
ADVERT: Windows® 2000, Windows® XP(32/64)
ADVERT:
ADVERT: Windows® Vista(32/64), Win7 (32/64)
ADVERT:
ADVERT:
ADVERT:Accessories:
ADVERT:
ADVERT:1 x Manual 

> Does the adapter convert a PCIe slot into a PCI slot or the other way round?

other way round, it slots in to a PCI 32 bit slot -- has both 3.3 and 5v notches --
and provides a PCI-e x1 slot. Low profile PCI-e cards sit in it making the two cards
take up a full height card space.

> > The sata card has no real distinguishing features except the chip used - SI 3531.
> 
> No sticker on the back?  No manufacturer name or code anywhere on the PCB?

Here is what I can see etched on the PCB - I don't know if this helps much:

EX-75-326G
20062507_V1.0

There is a sticker on the back: Q0907Sil3531A

This is the bundle that it came with, but it doesn't really tell you much:

http://www.lambda-tek.com/componentshop/index.pl?prodID=B139009

> It makes it difficult to track down problem reports on the web without
> knowing who made the cards and which models they are...
> 
> Some manufacturers are known for putting out shoddy gear, or marginally
> compatible gear.

Lacking enough spare parts, it is difficult for me to point the finger at the card
as it could well be the machine it was plugged in to. I will in the coming days buy
a replacement server that should provide another reference point, but I do suspect
the fault is with my old server.

thanks for your help,

Richard

-- 
Richard Mawson
Mawson IT Services

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: SATA driver sata_sil24

[Tim Small]

On 24/04/10 06:10, Richard Mawson wrote:
> Thank you for your help with this. I believe this was a hardware problem, as the same
> pci-pcie converter with the same pcie sata adapter work perfectly in a different
> system (now why didn't I try that first..?)

If you want to try to debug this further - you could turn on PCI parity 
error detection (either using EDAC module, or via userspace with 
lspci/setpci)?

# modprobe  edac_core
# echo 1 > /sys/module/edac_core/parameters/check_pci_errors

If you're after a different solution for that machine, you can buy Sii 
3124 based cards (PCI-X to 4x SATA) for about the same price as that 
adaptor....

http://www.siliconimage.com/products/product.aspx?pid=27

Tim.


-- 
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53  http://seoss.co.uk/ +44-(0)1273-808309

Re: SATA driver sata_sil24

[Robert Hancock]

On Thu, Apr 29, 2010 at 3:14 AM, Richard Mawson
<richard@crow.mawsonit.co.uk> wrote:
> Tim,
>
> On Mon, Apr 26, 2010 at 12:59:05PM +0100, Tim Small wrote:
>> If you want to try to debug this further - you could turn on PCI parity
>> error detection (either using EDAC module, or via userspace with
>> lspci/setpci)?
>>
>> # modprobe  edac_core
>> # echo 1 > /sys/module/edac_core/parameters/check_pci_errors
>>
>> If you're after a different solution for that machine, you can buy Sii
>> 3124 based cards (PCI-X to 4x SATA) for about the same price as that
>> adaptor....
>>
>> http://www.siliconimage.com/products/product.aspx?pid=27
>
> Thanks for your suggestions.
>
> I'm not too familiar with debugging pci errors, but I'm willing to try things
> out if there are suggestions as to what to look for.
>
> Having moves this to another system, still using the pci-pcie bridge, there
> are problems too -- it just takes longer to show up. The system locks up when
> copying large quantities of data to the disks.
>
> The symptom is the following code in the interrupt handler being called many
> many times:
>
>        if (status == 0xffffffff) {
>                printk(KERN_ERR DRV_NAME ": IRQ status == 0xffffffff, "
>                       "PCI fault or device removal?\n");
>
> Does this indicate a hardware error? Is there a safe way to reset the device
> in this state to avoid the repeated calls to the interrupt handler that I
> suspect is the cause of the machine being unresponsive?
>
> I'm looking into pci debugging techniques, but any pointers would be welcome.

Register reads returning all 1s would indicate that there are likely
PCI aborts happening - could be either the bridge or the chip itself
has stopped responding.