Problem with ata layer in 2.6.24

Problem with ata layer in 2.6.24

[Gene Heskett]

Greeting;

I had to reboot early this morning due to a freezeup, and I had a 
bunch of these in the messages log:
==============
Jan 27 19:42:11 coyote kernel: [42461.915961] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Jan 27 19:42:11 coyote kernel: [42461.915973] ata1.00: cmd ca/00:08:b1:66:46/00:00:00:00:00/e8 tag 0 dma 4096 out
Jan 27 19:42:11 coyote kernel: [42461.915974]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 27 19:42:11 coyote kernel: [42461.915978] ata1.00: status: { DRDY }
Jan 27 19:42:11 coyote kernel: [42461.916005] ata1: soft resetting link
Jan 27 19:42:12 coyote kernel: [42462.078216] ata1.00: configured for UDMA/100
Jan 27 19:42:12 coyote kernel: [42462.078232] ata1: EH complete
Jan 27 19:42:12 coyote kernel: [42462.090700] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
Jan 27 19:42:12 coyote kernel: [42462.114230] sd 0:0:0:0: [sda] Write Protect is off
Jan 27 19:42:12 coyote kernel: [42462.115079] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA
===============
That one showed up about 2 hours ago, so I expect I'll be locked 
up again before I've managed a 24 hour uptime.  This drive passed
a 'smartctl -t long /dev/sda' with flying colors after the reboot
this morning.

Two instances were logged after I had rebooted to 2.6.24 from 2.6.24-rc8:

Jan 24 20:46:33 coyote kernel: [    0.000000] Linux version 2.6.24 (root@coyote.coyote.den) (gcc version 4.1.2 20070925 
(Red Hat 4.1.2-33)) #1 SMP Thu Jan 24 20:17:55 EST 2008
----
Jan 27 02:28:29 coyote kernel: [193207.445158] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Jan 27 02:28:29 coyote kernel: [193207.445170] ata1.00: cmd 35/00:08:f9:24:0a/00:00:17:00:00/e0 tag 0 dma 4096 out
Jan 27 02:28:29 coyote kernel: [193207.445172]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 27 02:28:29 coyote kernel: [193207.445175] ata1.00: status: { DRDY }
Jan 27 02:28:29 coyote kernel: [193207.445202] ata1: soft resetting link
Jan 27 02:28:29 coyote kernel: [193207.607384] ata1.00: configured for UDMA/100
Jan 27 02:28:29 coyote kernel: [193207.607399] ata1: EH complete
Jan 27 02:28:29 coyote kernel: [193207.609681] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
Jan 27 02:28:29 coyote kernel: [193207.619277] sd 0:0:0:0: [sda] Write Protect is off
Jan 27 02:28:29 coyote kernel: [193207.649041] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA
Jan 27 02:30:06 coyote kernel: [193304.336929] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Jan 27 02:30:06 coyote kernel: [193304.336940] ata1.00: cmd ca/00:20:69:22:a6/00:00:00:00:00/e7 tag 0 dma 16384 out
Jan 27 02:30:06 coyote kernel: [193304.336942]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 27 02:30:06 coyote kernel: [193304.336945] ata1.00: status: { DRDY }
Jan 27 02:30:06 coyote kernel: [193304.336972] ata1: soft resetting link
Jan 27 02:30:06 coyote kernel: [193304.499210] ata1.00: configured for UDMA/100
Jan 27 02:30:06 coyote kernel: [193304.499226] ata1: EH complete
Jan 27 02:30:06 coyote kernel: [193304.499714] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
Jan 27 02:30:06 coyote kernel: [193304.499857] sd 0:0:0:0: [sda] Write Protect is off
Jan 27 02:30:06 coyote kernel: [193304.502315] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA

None were logged during the time I was running an -rc7 or -rc8.

The previous hits on this resulted in the udma speed being downgraded 
till it was actually running in pio just before the freeze that 
required the hardware reset button.

I'll reboot to -rc8 right now and resume.  If its the drive, I should see it.
If not, then 2.6.24 is where I'll point the finger.

Idea's anyone?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yow!  Am I in Milwaukee?

Re: Problem with ata layer in 2.6.24

[Kasper Sandberg]

On Sun, 2008-01-27 at 21:22 -0500, Gene Heskett wrote:
> Greeting;
> 
<snip>
> None were logged during the time I was running an -rc7 or -rc8.
> 
> The previous hits on this resulted in the udma speed being downgraded 
> till it was actually running in pio just before the freeze that 
> required the hardware reset button.
> 
> I'll reboot to -rc8 right now and resume.  If its the drive, I should see it.
> If not, then 2.6.24 is where I'll point the finger.
> 
> Idea's anyone?
I believe there is some sort of bug in libata, not just for this kernel
version.

i run a fileserver with .20, and i get these resets a few times a day..
no freezes though... except when its in progress, then all IO freezes
and locks up applications using it.. but it passes after ~30sec.

i know that since ubuntu started shipping with libata by default for
IDE, a large number of people are seeing these intermittant freezes
aswell(which passes after half a minute or less).

i reported this before, however as far as i know, no reason, and much
less a fix, has been found.

it would be great to get this solved though.


> 
> -- 
> Cheers, Gene
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Yow!  Am I in Milwaukee?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: Problem with ata layer in 2.6.24

[Mikael Pettersson]

Gene Heskett writes:
 > Greeting;
 > 
 > I had to reboot early this morning due to a freezeup, and I had a 
 > bunch of these in the messages log:
 > ==============
 > Jan 27 19:42:11 coyote kernel: [42461.915961] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
 > Jan 27 19:42:11 coyote kernel: [42461.915973] ata1.00: cmd ca/00:08:b1:66:46/00:00:00:00:00/e8 tag 0 dma 4096 out
 > Jan 27 19:42:11 coyote kernel: [42461.915974]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
 > Jan 27 19:42:11 coyote kernel: [42461.915978] ata1.00: status: { DRDY }
 > Jan 27 19:42:11 coyote kernel: [42461.916005] ata1: soft resetting link
 > Jan 27 19:42:12 coyote kernel: [42462.078216] ata1.00: configured for UDMA/100
 > Jan 27 19:42:12 coyote kernel: [42462.078232] ata1: EH complete
 > Jan 27 19:42:12 coyote kernel: [42462.090700] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
 > Jan 27 19:42:12 coyote kernel: [42462.114230] sd 0:0:0:0: [sda] Write Protect is off
 > Jan 27 19:42:12 coyote kernel: [42462.115079] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
 > support DPO or FUA
 > ===============
 > That one showed up about 2 hours ago, so I expect I'll be locked 
 > up again before I've managed a 24 hour uptime.  This drive passed
 > a 'smartctl -t long /dev/sda' with flying colors after the reboot
 > this morning.
 > 
 > Two instances were logged after I had rebooted to 2.6.24 from 2.6.24-rc8:
 > 
 > Jan 24 20:46:33 coyote kernel: [    0.000000] Linux version 2.6.24 (root@coyote.coyote.den) (gcc version 4.1.2 20070925 
 > (Red Hat 4.1.2-33)) #1 SMP Thu Jan 24 20:17:55 EST 2008
 > ----
 > Jan 27 02:28:29 coyote kernel: [193207.445158] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
 > Jan 27 02:28:29 coyote kernel: [193207.445170] ata1.00: cmd 35/00:08:f9:24:0a/00:00:17:00:00/e0 tag 0 dma 4096 out
 > Jan 27 02:28:29 coyote kernel: [193207.445172]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
 > Jan 27 02:28:29 coyote kernel: [193207.445175] ata1.00: status: { DRDY }
 > Jan 27 02:28:29 coyote kernel: [193207.445202] ata1: soft resetting link
 > Jan 27 02:28:29 coyote kernel: [193207.607384] ata1.00: configured for UDMA/100
 > Jan 27 02:28:29 coyote kernel: [193207.607399] ata1: EH complete
 > Jan 27 02:28:29 coyote kernel: [193207.609681] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
 > Jan 27 02:28:29 coyote kernel: [193207.619277] sd 0:0:0:0: [sda] Write Protect is off
 > Jan 27 02:28:29 coyote kernel: [193207.649041] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
 > support DPO or FUA
 > Jan 27 02:30:06 coyote kernel: [193304.336929] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
 > Jan 27 02:30:06 coyote kernel: [193304.336940] ata1.00: cmd ca/00:20:69:22:a6/00:00:00:00:00/e7 tag 0 dma 16384 out
 > Jan 27 02:30:06 coyote kernel: [193304.336942]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
 > Jan 27 02:30:06 coyote kernel: [193304.336945] ata1.00: status: { DRDY }
 > Jan 27 02:30:06 coyote kernel: [193304.336972] ata1: soft resetting link
 > Jan 27 02:30:06 coyote kernel: [193304.499210] ata1.00: configured for UDMA/100
 > Jan 27 02:30:06 coyote kernel: [193304.499226] ata1: EH complete
 > Jan 27 02:30:06 coyote kernel: [193304.499714] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
 > Jan 27 02:30:06 coyote kernel: [193304.499857] sd 0:0:0:0: [sda] Write Protect is off
 > Jan 27 02:30:06 coyote kernel: [193304.502315] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
 > support DPO or FUA
 > 
 > None were logged during the time I was running an -rc7 or -rc8.
 > 
 > The previous hits on this resulted in the udma speed being downgraded 
 > till it was actually running in pio just before the freeze that 
 > required the hardware reset button.
 > 
 > I'll reboot to -rc8 right now and resume.  If its the drive, I should see it.
 > If not, then 2.6.24 is where I'll point the finger.
 > 
 > Idea's anyone?

1. Wrong mailing list; use linux-ide (@vger) instead.
2. Incomplete dmesg, in particular, we can't see what your hardware is.
   Just post the complete dmesg.

Re: Problem with ata layer in 2.6.24

[Peter Zijlstra]

On Mon, 2008-01-28 at 09:17 +0100, Mikael Pettersson wrote:

> 1. Wrong mailing list; use linux-ide (@vger) instead.

What, and keep all us other interested people in the dark?

Re: Problem with ata layer in 2.6.24

[Mikael Pettersson]

Peter Zijlstra writes:
 > 
 > On Mon, 2008-01-28 at 09:17 +0100, Mikael Pettersson wrote:
 > 
 > > 1. Wrong mailing list; use linux-ide (@vger) instead.
 > 
 > What, and keep all us other interested people in the dark?

MAINTAINERS clearly lists linux-ide as the primary mailing
list for all things IDE/ATA.

The original report only went to LKML, thus it has a high
chance of being missed or ignored by those most capable of
dealing with it.

If a topic is of general interest a simple Cc: lkml will
keep other parties in the loop.

Re: Problem with ata layer in 2.6.24

[Ingo Molnar]

* Mikael Pettersson <mikpe@it.uu.se> wrote:

> Peter Zijlstra writes:
>  > 
>  > On Mon, 2008-01-28 at 09:17 +0100, Mikael Pettersson wrote:
>  > 
>  > > 1. Wrong mailing list; use linux-ide (@vger) instead.
>  > 
>  > What, and keep all us other interested people in the dark?
> 
> MAINTAINERS clearly lists linux-ide as the primary mailing list for 
> all things IDE/ATA.
>
> The original report only went to LKML, thus it has a high chance of 
> being missed or ignored by those most capable of dealing with it.

that is a fatal misunderstanding on your part. lkml is a perfectly fine 
place to report Linux bugs, why should testers be aware of the zillions 
of tiny, mostly irrelevant lists mentioned in the MAINTAINERS file?

Maintainers are required to read lkml for bugreports regarding their 
subsystems - not the other way around. If a tester manages to Cc: a 
maintainer (be that a person or a list alias) that's a bonus, but not a 
requirement at all ...

	Ingo

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Peter Zijlstra wrote:
>On Mon, 2008-01-28 at 09:17 +0100, Mikael Pettersson wrote:
>> 1. Wrong mailing list; use linux-ide (@vger) instead.
>
>What, and keep all us other interested people in the dark?

As a test, I tried rebooting to the latest fedora kernel and found it kills X, 
so I'm back to the second to last fedora version ATM, and the 
third 'smartctl -t lng /dev/sda' in 24 hours is running now.  The first two 
completed with no errors.

I've added the linux-ide list to refresh those people of the problem, 
the logs are being spammed by this message stanza:

 Jan 28 04:46:25 coyote kernel: [26550.290016] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Jan 28 04:46:25 coyote kernel: [26550.290028] ata1.00: cmd 35/00:58:c9:9c:0a/00:01:00:00:00/e0 tag 0 dma 176128 out
Jan 28 04:46:25 coyote kernel: [26550.290029]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 28 04:46:25 coyote kernel: [26550.290032] ata1.00: status: { DRDY }
Jan 28 04:46:25 coyote kernel: [26550.290060] ata1: soft resetting link
Jan 28 04:46:25 coyote kernel: [26550.452301] ata1.00: configured for UDMA/100
Jan 28 04:46:25 coyote kernel: [26550.452318] ata1: EH complete
Jan 28 04:46:25 coyote kernel: [26550.455898] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
Jan 28 04:46:25 coyote kernel: [26550.456151] sd 0:0:0:0: [sda] Write Protect is off
Jan 28 04:46:25 coyote kernel: [26550.456403] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
support DPO or FUA


And it just did it again, using the fedora kernel but without logging 
anything at all when it froze.  In other words I had to reboot between 
the word list and the word to above.  So now I'm booted to 2.6.24-rc7.

Before it crashes again, here is the dmesg:
[    0.000000] Linux version 2.6.24-rc7 (root@coyote.coyote.den) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP 
Mon Jan 14 10:00:40 EST 2008
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[    0.000000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
[    0.000000]  BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
[    0.000000]  BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
[    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
[    0.000000] 127MB HIGHMEM available.
[    0.000000] 896MB LOWMEM available.
[    0.000000] Entering add_active_range(0, 0, 262128) 0 entries of 256 used
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA             0 ->     4096
[    0.000000]   Normal       4096 ->   229376
[    0.000000]   HighMem    229376 ->   262128
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[1] active PFN ranges
[    0.000000]     0:        0 ->   262128
[    0.000000] On node 0 totalpages: 262128
[    0.000000]   DMA zone: 32 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 4064 pages, LIFO batch:0
[    0.000000]   Normal zone: 1760 pages used for memmap
[    0.000000]   Normal zone: 223520 pages, LIFO batch:31
[    0.000000]   HighMem zone: 255 pages used for memmap
[    0.000000]   HighMem zone: 32497 pages, LIFO batch:7
[    0.000000]   Movable zone: 0 pages used for memmap
[    0.000000] DMI 2.2 present.
[    0.000000] ACPI: RSDP 000F7220, 0014 (r0 Nvidia)
[    0.000000] ACPI: RSDT 3FFF3000, 002C (r1 Nvidia AWRDACPI 42302E31 AWRD        0)
[    0.000000] ACPI: FACP 3FFF3040, 0074 (r1 Nvidia AWRDACPI 42302E31 AWRD        0)
[    0.000000] ACPI: DSDT 3FFF30C0, 4CC4 (r1 NVIDIA AWRDACPI     1000 MSFT  100000E)
[    0.000000] ACPI: FACS 3FFF0000, 0040
[    0.000000] ACPI: APIC 3FFF7DC0, 006E (r1 Nvidia AWRDACPI 42302E31 AWRD        0)
[    0.000000] Nvidia board detected. Ignoring ACPI timer override.
[    0.000000] If you got timer trouble try acpi_use_timer_override
[    0.000000] ACPI: PM-Timer IO Port: 0x4008
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] Processor #0 6:10 APIC version 16
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: BIOS IRQ0 pin2 override ignored.
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] ACPI: IRQ14 used by override.
[    0.000000] ACPI: IRQ15 used by override.
[    0.000000] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
[    0.000000] swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
[    0.000000] swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000f0000
[    0.000000] swsusp: Registered nosave memory region: 00000000000f0000 - 0000000000100000
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260081
[    0.000000] Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
[    0.000000] mapped APIC to ffffb000 (fee00000)
[    0.000000] mapped IOAPIC to ffffa000 (fec00000)
[    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] CPU 0 irqstacks, hard=c073a000 soft=c071a000
[    0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
[    0.000000] Detected 2079.551 MHz processor.
[   28.725256] Console: colour VGA+ 80x25
[   28.725259] console [tty0] enabled
[   28.725828] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[   28.726361] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[   28.756701] Memory: 1031116k/1048512k available (1938k kernel code, 16656k reserved, 967k data, 236k init, 131008k 
highmem)
[   28.756710] virtual kernel memory layout:
[   28.756711]     fixmap  : 0xffc55000 - 0xfffff000   (3752 kB)
[   28.756713]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
[   28.756714]     vmalloc : 0xf8800000 - 0xff7fe000   ( 111 MB)
[   28.756715]     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
[   28.756716]       .init : 0xc06dc000 - 0xc0717000   ( 236 kB)
[   28.756718]       .data : 0xc05e4944 - 0xc06d66e4   ( 967 kB)
[   28.756719]       .text : 0xc0400000 - 0xc05e4944   (1938 kB)
[   28.756722] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[   28.756770] SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
[   28.816731] Calibrating delay using timer specific routine.. 4160.90 BogoMIPS (lpj=2080452)
[   28.816763] Security Framework initialized
[   28.816770] SELinux:  Initializing.
[   28.816784] SELinux:  Starting in permissive mode
[   28.816797] selinux_register_security:  Registering secondary module capability
[   28.816800] Capability LSM initialized as secondary
[   28.816809] Mount-cache hash table entries: 512
[   28.816976] CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000 00000000 00000000 00000000 
00000000
[   28.816985] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[   28.816987] CPU: L2 Cache: 512K (64 bytes/line)
[   28.816990] CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000420 00000000 00000000 00000000 00000000
[   28.816996] Intel machine check architecture supported.
[   28.816998] Intel machine check reporting enabled on CPU#0.
[   28.817003] Compat vDSO mapped to ffffe000.
[   28.817017] Checking 'hlt' instruction... OK.
[   28.820895] SMP alternatives: switching to UP code
[   28.821401] Freeing SMP alternatives: 12k freed
[   28.821404] ACPI: Core revision 20070126
[   28.824590] CPU0: AMD Athlon(tm) XP 2800+ stepping 00
[   28.824614] Total of 1 processors activated (4160.90 BogoMIPS).
[   28.824820] ENABLING IO-APIC IRQs
[   28.825012] ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1
[   28.936680] Brought up 1 CPUs
[   28.936708] CPU0 attaching sched-domain:
[   28.936711]  domain 0: span 00000001
[   28.936713]   groups: 00000001
[   28.936925] net_namespace: 64 bytes
[   28.937409] Time: 12:43:09  Date: 01/28/08
[   28.937442] NET: Registered protocol family 16
[   28.937683] ACPI: bus type pci registered
[   28.972986] PCI: PCI BIOS revision 2.10 entry at 0xfb4c0, last bus=2
[   28.972989] PCI: Using configuration type 1
[   28.972991] Setting up standard PCI resources
[   28.980763] ACPI: EC: Look up EC in DSDT
[   28.986590] ACPI: Interpreter enabled
[   28.986593] ACPI: (supports S0 S1 S4 S5)
[   28.986608] ACPI: Using IOAPIC for interrupt routing
[   28.997079] ACPI: PCI Root Bridge [PCI0] (0000:00)
[   28.997157] PCI: nForce2 C1 Halt Disconnect fixup
[   28.998175] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[   28.998355] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
[   28.998631] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
[   29.054757] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[   29.054952] ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[   29.055144] ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[   29.055334] ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[   29.055529] ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.055724] ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[   29.055918] ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 10 11 *12 14 15)
[   29.056109] ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 11 *12 14 15)
[   29.056298] ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.056489] ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 6 7 10 11 *12 14 15)
[   29.056685] ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.056876] ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.057066] ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[   29.057258] ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.057448] ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.057642] ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.057803] ACPI: PCI Interrupt Link [APC1] (IRQs *16)
[   29.057951] ACPI: PCI Interrupt Link [APC2] (IRQs *17)
[   29.058099] ACPI: PCI Interrupt Link [APC3] (IRQs *18)
[   29.058246] ACPI: PCI Interrupt Link [APC4] (IRQs *19)
[   29.058402] ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
[   29.058617] ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0
[   29.058827] ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22) *0
[   29.059036] ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0
[   29.059245] ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22) *0, disabled.
[   29.059454] ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22) *0
[   29.059669] ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22) *0, disabled.
[   29.059819] ACPI: PCI Interrupt Link [APCS] (IRQs *23), disabled.
[   29.060028] ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22) *0
[   29.060236] ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0, disabled.
[   29.060446] ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22) *0, disabled.
[   29.060661] ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22) *0, disabled.
[   29.060822] ACPI: Power Resource [ISAV] (on)
[   29.060880] Linux Plug and Play Support v0.97 (c) Adam Belay
[   29.060917] pnp: PnP ACPI init
[   29.060926] ACPI: bus type pnp registered
[   29.066989] pnp: PnP ACPI: found 16 devices
[   29.066992] ACPI: ACPI bus type pnp unregistered
[   29.067179] usbcore: registered new interface driver usbfs
[   29.067257] usbcore: registered new interface driver hub
[   29.067309] usbcore: registered new device driver usb
[   29.067395] PCI: Using ACPI for IRQ routing
[   29.067399] PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
[   29.117453] NetLabel: Initializing
[   29.117455] NetLabel:  domain hash size = 128
[   29.117457] NetLabel:  protocols = UNLABELED CIPSOv4
[   29.117471] NetLabel:  unlabeled traffic allowed by default
[   29.118443] Time: tsc clocksource has been installed.
[   29.120481] system 00:00: ioport range 0x4000-0x407f has been reserved
[   29.120484] system 00:00: ioport range 0x4080-0x40ff has been reserved
[   29.120487] system 00:00: ioport range 0x4400-0x447f has been reserved
[   29.120490] system 00:00: ioport range 0x4480-0x44ff has been reserved
[   29.120492] system 00:00: ioport range 0x4200-0x427f has been reserved
[   29.120495] system 00:00: ioport range 0x4280-0x42ff has been reserved
[   29.120502] system 00:01: ioport range 0x5000-0x503f has been reserved
[   29.120505] system 00:01: ioport range 0x5100-0x513f has been reserved
[   29.120511] system 00:02: iomem range 0xda800-0xdbfff has been reserved
[   29.120514] system 00:02: iomem range 0xf0000-0xf7fff could not be reserved
[   29.120516] system 00:02: iomem range 0xf8000-0xfbfff could not be reserved
[   29.120519] system 00:02: iomem range 0xfc000-0xfffff could not be reserved
[   29.120522] system 00:02: iomem range 0x3fff0000-0x3fffffff could not be reserved
[   29.120525] system 00:02: iomem range 0xffff0000-0xffffffff could not be reserved
[   29.120528] system 00:02: iomem range 0x0-0x9ffff could not be reserved
[   29.120531] system 00:02: iomem range 0x100000-0x3ffeffff could not be reserved
[   29.120534] system 00:02: iomem range 0xfec00000-0xfec00fff could not be reserved
[   29.120537] system 00:02: iomem range 0xfee00000-0xfee00fff could not be reserved
[   29.120543] system 00:04: ioport range 0xb78-0xb7b has been reserved
[   29.120546] system 00:04: ioport range 0xf78-0xf7b has been reserved
[   29.120548] system 00:04: ioport range 0xa78-0xa7b has been reserved
[   29.120551] system 00:04: ioport range 0xe78-0xe7b has been reserved
[   29.120554] system 00:04: ioport range 0xbbc-0xbbf has been reserved
[   29.120556] system 00:04: ioport range 0xfbc-0xfbf has been reserved
[   29.120559] system 00:04: ioport range 0x4d0-0x4d1 has been reserved
[   29.120562] system 00:04: ioport range 0x294-0x297 has been reserved
[   29.151040] PCI: Bridge: 0000:00:08.0
[   29.151044]   IO window: 9000-afff
[   29.151049]   MEM window: e3000000-e6ffffff
[   29.151053]   PREFETCH window: 50000000-500fffff
[   29.151058] PCI: Bridge: 0000:00:1e.0
[   29.151059]   IO window: disabled.
[   29.151063]   MEM window: e0000000-e2ffffff
[   29.151066]   PREFETCH window: d0000000-dfffffff
[   29.151077] PCI: Setting latency timer of device 0000:00:08.0 to 64
[   29.151093] NET: Registered protocol family 2
[   29.160585] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[   29.160952] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[   29.162429] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[   29.163092] TCP: Hash tables configured (established 131072 bind 65536)
[   29.163095] TCP reno registered
[   29.165574] checking if image is initramfs... it is
[   29.446295] Freeing initrd memory: 3628k freed
[   29.446709] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[   29.446712] apm: overridden by ACPI.
[   29.447133] audit: initializing netlink socket (disabled)
[   29.447149] audit(1201524188.569:1): initialized
[   29.447287] highmem bounce pool size: 64 pages
[   29.447291] Total HugeTLB memory allocated, 0
[   29.449941] SELinux:  Registering netfilter hooks
[   29.450082] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[   29.450086] io scheduler noop registered
[   29.450088] io scheduler anticipatory registered
[   29.450090] io scheduler deadline registered
[   29.450101] io scheduler cfq registered (default)
[   29.472109] Boot video device is 0000:02:00.0
[   29.477398] ACPI: Thermal Zone [THRM] (51 C)
[   29.477413] isapnp: Scanning for PnP cards...
[   29.650914] Switched to high resolution mode on CPU 0
[   29.834322] isapnp: No Plug & Play device found
[   29.837157] Real Time Clock Driver v1.12ac
[   29.837309] Non-volatile memory driver v1.2
[   29.837312] Linux agpgart interface v0.102
[   29.837365] agpgart: Detected NVIDIA nForce2 chipset
[   29.853228] agpgart: AGP aperture is 256M @ 0xc0000000
[   29.853255] Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
[   29.853403] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[   29.853542] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[   29.853854] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[   29.854037] 00:0b: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[   29.855000] RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
[   29.855188] PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[   29.855191] PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[   29.855565] serio: i8042 KBD port at 0x60,0x64 irq 1
[   29.855638] mice: PS/2 mouse device common for all mice
[   29.876081] input: AT Translated Set 2 keyboard as /class/input/input0
[   29.878901] cpuidle: using governor ladder
[   29.878904] cpuidle: using governor menu
[   29.878982] usbcore: registered new interface driver hiddev
[   29.879024] usbcore: registered new interface driver usbhid
[   29.879027] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[   29.879098] TCP cubic registered
[   29.879100] Initializing XFRM netlink socket
[   29.879180] NET: Registered protocol family 1
[   29.879196] NET: Registered protocol family 17
[   29.879204] Using IPI No-Shortcut mode
[   29.879217] registered taskstats version 1
[   29.879349]   Magic number: 8:30:735
[   29.879657] Freeing unused kernel memory: 236k freed
[   29.879695] Write protecting the kernel text: 1940k
[   29.879708] Write protecting the kernel read-only data: 758k
[   30.175117] ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
[   30.175126] ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [APCL] -> GSI 22 (level, high) -> IRQ 16
[   30.175139] PCI: Setting latency timer of device 0000:00:02.2 to 64
[   30.175143] ehci_hcd 0000:00:02.2: EHCI Host Controller
[   30.175235] ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
[   30.175275] ehci_hcd 0000:00:02.2: debug port 1
[   30.175280] PCI: cache line size of 64 is not supported by device 0000:00:02.2
[   30.175291] ehci_hcd 0000:00:02.2: irq 16, io mem 0xe7005000
[   30.180677] ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[   30.180795] usb usb1: configuration #1 chosen from 1 choice
[   30.180823] hub 1-0:1.0: USB hub found
[   30.180834] hub 1-0:1.0: 6 ports detected
[   30.287626] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
[   30.288031] ACPI: PCI Interrupt Link [APCF] enabled at IRQ 21
[   30.288038] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 21 (level, high) -> IRQ 17
[   30.288052] PCI: Setting latency timer of device 0000:00:02.0 to 64
[   30.288055] ohci_hcd 0000:00:02.0: OHCI Host Controller
[   30.288129] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
[   30.288148] ohci_hcd 0000:00:02.0: irq 17, io mem 0xe7003000
[   30.340664] usb usb2: configuration #1 chosen from 1 choice
[   30.340691] hub 2-0:1.0: USB hub found
[   30.340704] hub 2-0:1.0: 3 ports detected
[   30.441860] ACPI: PCI Interrupt Link [APCG] enabled at IRQ 20
[   30.441865] ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCG] -> GSI 20 (level, high) -> IRQ 18
[   30.441873] PCI: Setting latency timer of device 0000:00:02.1 to 64
[   30.441876] ohci_hcd 0000:00:02.1: OHCI Host Controller
[   30.441932] ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3
[   30.441945] ohci_hcd 0000:00:02.1: irq 18, io mem 0xe7004000
[   30.487468] usb 1-1: new high speed USB device using ehci_hcd and address 2
[   30.494540] usb usb3: configuration #1 chosen from 1 choice
[   30.494569] hub 3-0:1.0: USB hub found
[   30.494579] hub 3-0:1.0: 3 ports detected
[   30.601427] USB Universal Host Controller Interface driver v3.0
[   30.601865] usb 1-1: configuration #1 chosen from 1 choice
[   30.602052] hub 1-1:1.0: USB hub found
[   30.602151] hub 1-1:1.0: 4 ports detected
[   30.660576] SCSI subsystem initialized
[   30.673851] Driver 'sd' needs updating - please use bus_type methods
[   30.700319] libata version 3.00 loaded.
[   30.702887] pata_amd 0000:00:09.0: version 0.3.10
[   30.703052] PCI: Setting latency timer of device 0000:00:09.0 to 64
[   30.703188] scsi0 : pata_amd
[   30.709313] scsi1 : pata_amd
[   30.710076] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
[   30.710079] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
[   30.864753] ata1.00: ATA-6: WDC WD2000JB-00EVA0, 15.05R15, max UDMA/100
[   30.864756] ata1.00: 390721968 sectors, multi 16: LBA48 
[   30.871629] ata1.00: configured for UDMA/100
[   31.195305] ata2.00: ATAPI: LITE-ON DVDRW SHM-165H6S, HS06, max UDMA/66
[   31.243813] ata2.01: ATA-7: MAXTOR STM3320620A, 3.AAE, max UDMA/100
[   31.243816] ata2.01: 625142448 sectors, multi 16: LBA48 
[   31.243825] ata2.00: limited to UDMA/33 due to 40-wire cable
[   31.417074] ata2.00: configured for UDMA/33
[   31.451769] ata2.01: configured for UDMA/100
[   31.451873] scsi 0:0:0:0: Direct-Access     ATA      WDC WD2000JB-00E 15.0 PQ: 0 ANSI: 5
[   31.451953] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[   31.451967] sd 0:0:0:0: [sda] Write Protect is off
[   31.451970] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   31.451989] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   31.452040] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[   31.452051] sd 0:0:0:0: [sda] Write Protect is off
[   31.452054] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   31.452071] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   31.452075]  sda: sda1 sda2
[   31.467219] sd 0:0:0:0: [sda] Attached SCSI disk
[   31.468093] scsi 1:0:0:0: CD-ROM            LITE-ON  DVDRW SHM-165H6S HS06 PQ: 0 ANSI: 5
[   31.468208] scsi 1:0:1:0: Direct-Access     ATA      MAXTOR STM332062 3.AA PQ: 0 ANSI: 5
[   31.468272] sd 1:0:1:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
[   31.468283] sd 1:0:1:0: [sdb] Write Protect is off
[   31.468286] sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[   31.468303] sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   31.468338] sd 1:0:1:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
[   31.468349] sd 1:0:1:0: [sdb] Write Protect is off
[   31.468352] sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[   31.468370] sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   31.468373]  sdb:<6>usb 2-2: new full speed USB device using ohci_hcd and address 2
[   31.499690]  sdb1 sdb2 sdb3
[   31.500119] sd 1:0:1:0: [sdb] Attached SCSI disk
[   31.637428] usb 2-2: configuration #1 chosen from 1 choice
[   31.856522] usb 2-3: new low speed USB device using ohci_hcd and address 3
[   32.020045] usb 2-3: configuration #1 chosen from 1 choice
[   32.035222] input: Chicony Saitek Eclipse II Keyboard as /class/input/input1
[   32.038424] input,hidraw0: USB HID v1.11 Keyboard [Chicony Saitek Eclipse II Keyboard] on usb-0000:00:02.0-3
[   32.067995] input: Chicony Saitek Eclipse II Keyboard as /class/input/input2
[   32.070422] input,hiddev96,hidraw1: USB HID v1.11 Device [Chicony Saitek Eclipse II Keyboard] on usb-0000:00:02.0-3
[   32.287225] usb 3-3: new full speed USB device using ohci_hcd and address 2
[   32.422699] usb 3-3: configuration #1 chosen from 1 choice
[   32.425658] hub 3-3:1.0: USB hub found
[   32.428631] hub 3-3:1.0: 4 ports detected
[   32.724000] usb 1-1.1: new low speed USB device using ehci_hcd and address 6
[   32.919001] usb 1-1.1: configuration #1 chosen from 1 choice
[   33.655893] hiddev97hidraw2: USB HID v1.11 Device [Belkin  Belkin UPS] on usb-0000:00:02.2-1.1
[   33.833315] usb 1-1.2: new full speed USB device using ehci_hcd and address 7
[   33.925926] usb 1-1.2: configuration #1 chosen from 1 choice
[   34.018028] device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com
[   34.043070] sata_sil 0000:01:0a.0: version 2.3
[   34.043348] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
[   34.043355] ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC1] -> GSI 16 (level, high) -> IRQ 19
[   34.045029] scsi2 : sata_sil
[   34.050031] scsi3 : sata_sil
[   34.050064] ata3: SATA max UDMA/100 mmio m512@0xe6004000 tf 0xe6004080 irq 19
[   34.050068] ata4: SATA max UDMA/100 mmio m512@0xe6004000 tf 0xe60040c0 irq 19
[   34.107056] usb 1-1.4: new high speed USB device using ehci_hcd and address 8
[   34.192310] usb 1-1.4: configuration #1 chosen from 1 choice
[   34.192499] hub 1-1.4:1.0: USB hub found
[   34.192597] hub 1-1.4:1.0: 4 ports detected
[   34.352811] ata3: SATA link down (SStatus 0 SControl 310)
[   34.481823] usb 1-1.4.3: new low speed USB device using ehci_hcd and address 9
[   34.573676] usb 1-1.4.3: configuration #1 chosen from 1 choice
[   34.577917] input: Logitech USB Receiver as /class/input/input3
[   34.580691] input,hidraw3: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:02.2-1.4.3
[   34.757557] usb 1-1.4.4: new full speed USB device using ehci_hcd and address 10
[   34.806514] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   34.810071] ata4.00: ATA-7: Hitachi HDT725040VLA360, V5COA7EA, max UDMA/133
[   34.810074] ata4.00: 781422768 sectors, multi 16: LBA48 NCQ (depth 0/32)
[   34.816059] ata4.00: configured for UDMA/100
[   34.816175] scsi 3:0:0:0: Direct-Access     ATA      Hitachi HDT72504 V5CO PQ: 0 ANSI: 5
[   34.816257] sd 3:0:0:0: [sdc] 781422768 512-byte hardware sectors (400088 MB)
[   34.816271] sd 3:0:0:0: [sdc] Write Protect is off
[   34.816274] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[   34.816293] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   34.816344] sd 3:0:0:0: [sdc] 781422768 512-byte hardware sectors (400088 MB)
[   34.816355] sd 3:0:0:0: [sdc] Write Protect is off
[   34.816358] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[   34.816375] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   34.816379]  sdc: sdc1
[   34.829837] sd 3:0:0:0: [sdc] Attached SCSI disk
[   34.843933] usb 1-1.4.4: configuration #1 chosen from 1 choice
[   37.852458] EXT3-fs: INFO: recovery required on readonly filesystem.
[   37.852464] EXT3-fs: write access will be enabled during recovery.
[   41.522866] kjournald starting.  Commit interval 5 seconds
[   41.522885] EXT3-fs: recovery complete.
[   41.524254] EXT3-fs: mounted filesystem with ordered data mode.
[   41.972449] audit(1201524201.103:2): enforcing=1 old_enforcing=0 auid=4294967295
[   42.187011] SELinux:8192 avtab hash slots allocated.Num of rules:213166
[   42.260611] SELinux:8192 avtab hash slots allocated.Num of rules:213166
[   42.314117] security:  8 users, 11 roles, 2363 types, 114 bools, 1 sens, 1024 cats
[   42.314122] security:  67 classes, 213166 rules
[   42.327287] SELinux:  Completing initialization.
[   42.327290] SELinux:  Setting up existing superblocks.
[   42.353550] SELinux: initialized (dev dm-0, type ext3), uses xattr
[   42.515071] SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
[   42.515088] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[   42.515193] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
[   42.515205] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
[   42.515235] SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
[   42.515244] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts
[   42.515250] SELinux: initialized (dev devpts, type devpts), uses transition SIDs
[   42.515262] SELinux: initialized (dev inotifyfs, type inotifyfs), uses genfs_contexts
[   42.515266] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[   42.515274] SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
[   42.515280] SELinux: initialized (dev anon_inodefs, type anon_inodefs), uses genfs_contexts
[   42.515285] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
[   42.515290] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
[   42.515299] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[   42.515312] SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
[   42.515318] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
[   42.515341] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
[   42.520002] SELinux: policy loaded with handle_unknown=allow
[   42.520011] audit(1201524201.651:3): policy loaded auid=4294967295
[   46.528101] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   46.528126] scsi 1:0:0:0: Attached scsi generic sg1 type 5
[   46.528149] sd 1:0:1:0: Attached scsi generic sg2 type 0
[   46.528174] sd 3:0:0:0: Attached scsi generic sg3 type 0
[   46.931288] input: Power Button (FF) as /class/input/input4
[   46.938141] ACPI: Power Button (FF) [PWRF]
[   46.938186] ACPI Error (evxfevnt-0186): Could not enable SleepButton event [20070126]
[   46.938192] ACPI Warning (evxface-0145): Could not enable fixed event 3 [20070126]
[   46.938283] input: Power Button (CM) as /class/input/input5
[   46.941132] ACPI: Power Button (CM) [PWRB]
[   46.941190] input: Sleep Button (CM) as /class/input/input6
[   46.944347] ACPI: Sleep Button (CM) [SLPB]
[   47.285717] usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x04B8 pid 0x0005
[   47.285742] usbcore: registered new interface driver usblp
[   47.308848] i2c-adapter i2c-0: nForce2 SMBus adapter at 0x5000
[   47.308876] i2c-adapter i2c-1: nForce2 SMBus adapter at 0x5100
[   47.352146] usbcore: registered new interface driver usbserial
[   47.352152] drivers/usb/serial/usb-serial.c: USB Serial Driver core
[   47.455275] drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
[   47.455308] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
[   47.455342] drivers/usb/serial/ftdi_sio.c: Detected FT232RL
[   47.455381] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
[   47.455398] usbcore: registered new interface driver ftdi_sio
[   47.455401] drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
[   47.530751] input: PC Speaker as /class/input/input7
[   47.572764] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
[   47.573147] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 22
[   47.573151] ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCH] -> GSI 22 (level, high) -> IRQ 16
[   47.573158] PCI: Setting latency timer of device 0000:00:04.0 to 64
[   47.615492] Floppy drive(s): fd0 is 1.44M
[   47.630509] FDC 0 is a post-1991 82077
[   48.084769] forcedeth 0000:00:04.0: ifname eth0, PHY OUI 0x20 @ 1, addr 00:04:4b:5d:eb:7d
[   48.084775] forcedeth 0000:00:04.0: timirq lnktim desc-v1
[   48.085214] ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
[   48.085222] ACPI: PCI Interrupt 0000:01:09.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 20
[   48.141308] firewire_ohci: Added fw-ohci device 0000:01:09.0, OHCI version 1.10
[   48.285456] nvidia: module license 'NVIDIA' taints kernel.
[   48.549725] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 20
[   48.550149] NVRM: loading NVIDIA UNIX x86 Kernel Module  169.07  Thu Dec 13 18:42:56 PST 2007
[   48.641028] firewire_core: created new fw device fw0 (0 config rom retries, S400)
[   48.848094] Linux video capture interface: v2.00
[   49.104974] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
[   49.105072] cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV [card=22,autodetected]
[   49.105076] cx88[0]: TV tuner type 60, Radio tuner type -1
[   49.151205] cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
[   49.255507] cx88[0]/2: cx2388x 8802 Driver Manager
[   49.257461] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
[   49.257472] ACPI: PCI Interrupt 0000:01:07.2[A] -> Link [APC2] -> GSI 17 (level, high) -> IRQ 21
[   49.257484] cx88[0]/2: found at 0000:01:07.2, rev: 5, irq: 21, latency: 32, mmio: 0xe4000000
[   49.257561] ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC2] -> GSI 17 (level, high) -> IRQ 21
[   49.257573] cx88[0]/0: found at 0000:01:07.0, rev: 5, irq: 21, latency: 32, mmio: 0xe3000000
[   49.440179] tda8290_probe: not probed - driver disabled by Kconfig
[   49.440185] tuner 2-0043: chip found @ 0x86 (cx88[0])
[   49.440208] tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
[   49.440211] tuner 2-0043: type set to tda9887
[   49.442442] tuner 2-0061: chip found @ 0xc2 (cx88[0])
[   49.442458] tuner-simple 2-0061: type set to 60 (Thomson DTT 761X (ATSC/NTSC))
[   49.442461] tuner 2-0061: type set to Thomson DTT 761X (A
[   49.442464] tuner-simple 2-0061: type set to 60 (Thomson DTT 761X (ATSC/NTSC))
[   49.442466] tuner 2-0061: type set to Thomson DTT 761X (A
[   49.451016] cx88[0]/0: registered device video0 [v4l2]
[   49.451038] cx88[0]/0: registered device vbi0
[   49.451064] cx88[0]/0: registered device radio0
[   49.454722] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
[   49.454731] ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC3] -> GSI 18 (level, high) -> IRQ 22
[   49.459555] Audigy2 value: Special config.
[   49.532042] cx88/2: cx2388x dvb driver version 0.0.6 loaded
[   49.532047] cx88/2: registering cx8802 driver, type: dvb access: shared
[   49.532052] cx88[0]/2: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV [card=22]
[   49.532055] cx88[0]/2: cx2388x based DVB/ATSC card
[   49.548119] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 21
[   49.548125] ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 21 (level, high) -> IRQ 17
[   49.548162] PCI: Setting latency timer of device 0000:00:06.0 to 64
[   49.654575] DVB: registering new adapter (cx88[0])
[   49.654582] DVB: registering frontend 0 (Oren OR51132 VSB/QAM Frontend)...
[   49.859126] intel8x0_measure_ac97_clock: measured 50668 usecs
[   49.859131] intel8x0: clocking to 47378
[   52.910654] EXT3 FS on dm-0, internal journal
[   53.162621] kjournald starting.  Commit interval 5 seconds
[   53.170013] EXT3 FS on sda1, internal journal
[   53.170019] EXT3-fs: mounted filesystem with ordered data mode.
[   53.170144] SELinux: initialized (dev sda1, type ext3), uses xattr
[   53.170540] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[   53.174936] kjournald starting.  Commit interval 5 seconds
[   53.182987] EXT3 FS on sdc1, internal journal
[   53.182992] EXT3-fs: mounted filesystem with ordered data mode.
[   53.188827] SELinux: initialized (dev sdc1, type ext3), uses xattr
[   54.005729] Adding 2031608k swap on /dev/mapper/VolGroup00-LogVol01.  Priority:-1 extents:1 across:2031608k
[   54.009417] SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
...[Linux's] capacity to talk via any medium except smoke signals.
	-- Dr. Greg Wettstein, Roger Maris Cancer Center

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Gene Heskett wrote:
>[    0.000000] If you got timer trouble try acpi_use_timer_override
This is from the dmesg of my previous post.

Can anyone tell me what it actually means?


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
I have a simple rule in life: If I don't understand something, it must be bad.

	- Linus Torvalds

Re: Problem with ata layer in 2.6.24

[Mikael Pettersson]

Gene Heskett writes:
 > On Monday 28 January 2008, Peter Zijlstra wrote:
 > >On Mon, 2008-01-28 at 09:17 +0100, Mikael Pettersson wrote:
 > >> 1. Wrong mailing list; use linux-ide (@vger) instead.
 > >
 > >What, and keep all us other interested people in the dark?
 > 
 > As a test, I tried rebooting to the latest fedora kernel and found it kills X, 
 > so I'm back to the second to last fedora version ATM, and the 
 > third 'smartctl -t lng /dev/sda' in 24 hours is running now.  The first two 
 > completed with no errors.
 > 
 > I've added the linux-ide list to refresh those people of the problem, 
 > the logs are being spammed by this message stanza:
 > 
 >  Jan 28 04:46:25 coyote kernel: [26550.290016] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
 > Jan 28 04:46:25 coyote kernel: [26550.290028] ata1.00: cmd 35/00:58:c9:9c:0a/00:01:00:00:00/e0 tag 0 dma 176128 out
 > Jan 28 04:46:25 coyote kernel: [26550.290029]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
 > Jan 28 04:46:25 coyote kernel: [26550.290032] ata1.00: status: { DRDY }
 > Jan 28 04:46:25 coyote kernel: [26550.290060] ata1: soft resetting link
 > Jan 28 04:46:25 coyote kernel: [26550.452301] ata1.00: configured for UDMA/100
 > Jan 28 04:46:25 coyote kernel: [26550.452318] ata1: EH complete
 > Jan 28 04:46:25 coyote kernel: [26550.455898] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
 > Jan 28 04:46:25 coyote kernel: [26550.456151] sd 0:0:0:0: [sda] Write Protect is off
 > Jan 28 04:46:25 coyote kernel: [26550.456403] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
 > support DPO or FUA

It's not obvious from this incomplete dmesg log what HW or driver
is behind ata1, but if the 2.6.24-rc7 kernel matches the 2.6.24 one,
it should be pata_amd driving a WDC disk:

 > [   30.702887] pata_amd 0000:00:09.0: version 0.3.10
 > [   30.703052] PCI: Setting latency timer of device 0000:00:09.0 to 64
 > [   30.703188] scsi0 : pata_amd
 > [   30.709313] scsi1 : pata_amd
 > [   30.710076] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
 > [   30.710079] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
 > [   30.864753] ata1.00: ATA-6: WDC WD2000JB-00EVA0, 15.05R15, max UDMA/100
 > [   30.864756] ata1.00: 390721968 sectors, multi 16: LBA48 
 > [   30.871629] ata1.00: configured for UDMA/100

Unfortunately we also see:

 > [   48.285456] nvidia: module license 'NVIDIA' taints kernel.
 > [   48.549725] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 20
 > [   48.550149] NVRM: loading NVIDIA UNIX x86 Kernel Module  169.07  Thu Dec 13 18:42:56 PST 2007

We have no way of debugging that module, so please try 2.6.24 without it.
If the problems persist, please try to capture a complete log from the
failing kernel -- the interesting bits are everything from initial boot
up to and including the first few errors. You may need to increase the
kernel's log buffer size if the log gets truncated (CONFIG_LOG_BUF_SHIFT).

There are no pata_amd changes from 2.6.24-rc7 to 2.6.24 final.

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

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

On Monday 28 January 2008, Mikael Pettersson wrote:
>Gene Heskett writes:
> > On Monday 28 January 2008, Peter Zijlstra wrote:
> > >On Mon, 2008-01-28 at 09:17 +0100, Mikael Pettersson wrote:
> > >> 1. Wrong mailing list; use linux-ide (@vger) instead.
> > >
> > >What, and keep all us other interested people in the dark?
> >
> > As a test, I tried rebooting to the latest fedora kernel and found it
> > kills X, so I'm back to the second to last fedora version ATM, and the
> > third 'smartctl -t lng /dev/sda' in 24 hours is running now.  The first
> > two completed with no errors.
> >
> > I've added the linux-ide list to refresh those people of the problem,
> > the logs are being spammed by this message stanza:
> >
> >  Jan 28 04:46:25 coyote kernel: [26550.290016] ata1.00: exception Emask
> > 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Jan 28 04:46:25 coyote kernel:
> > [26550.290028] ata1.00: cmd 35/00:58:c9:9c:0a/00:01:00:00:00/e0 tag 0 dma
> > 176128 out Jan 28 04:46:25 coyote kernel: [26550.290029]          res
> > 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 28 04:46:25
> > coyote kernel: [26550.290032] ata1.00: status: { DRDY } Jan 28 04:46:25
> > coyote kernel: [26550.290060] ata1: soft resetting link Jan 28 04:46:25
> > coyote kernel: [26550.452301] ata1.00: configured for UDMA/100 Jan 28
> > 04:46:25 coyote kernel: [26550.452318] ata1: EH complete
> > Jan 28 04:46:25 coyote kernel: [26550.455898] sd 0:0:0:0: [sda] 390721968
> > 512-byte hardware sectors (200050 MB) Jan 28 04:46:25 coyote kernel:
> > [26550.456151] sd 0:0:0:0: [sda] Write Protect is off Jan 28 04:46:25
> > coyote kernel: [26550.456403] sd 0:0:0:0: [sda] Write cache: enabled,
> > read cache: enabled, doesn't support DPO or FUA
>
>It's not obvious from this incomplete dmesg log what HW or driver
>is behind ata1, but if the 2.6.24-rc7 kernel matches the 2.6.24 one,
>
>it should be pata_amd driving a WDC disk:
> > [   30.702887] pata_amd 0000:00:09.0: version 0.3.10
> > [   30.703052] PCI: Setting latency timer of device 0000:00:09.0 to 64
> > [   30.703188] scsi0 : pata_amd
> > [   30.709313] scsi1 : pata_amd
> > [   30.710076] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000
> > irq 14 [   30.710079] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma
> > 0xf008 irq 15 [   30.864753] ata1.00: ATA-6: WDC WD2000JB-00EVA0,
> > 15.05R15, max UDMA/100 [   30.864756] ata1.00: 390721968 sectors, multi
> > 16: LBA48
> > [   30.871629] ata1.00: configured for UDMA/100
>
>Unfortunately we also see:
> > [   48.285456] nvidia: module license 'NVIDIA' taints kernel.
> > [   48.549725] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI
> > 19 (level, high) -> IRQ 20 [   48.550149] NVRM: loading NVIDIA UNIX x86
> > Kernel Module  169.07  Thu Dec 13 18:42:56 PST 2007
>
>We have no way of debugging that module, so please try 2.6.24 without it.

Sorry, I can't do this and have a working machine.  The nv driver has suffered 
bit rot or something since the FC2 days when it COULD run a 19" crt at 
1600x1200, and will not drive this 20" wide screen lcd 1680x1050 monitor at 
more than 800x600, which is absolutely butt ugly fuzzy, looking like a jpg 
compressed to 10%.  The system is not usable on a day to basis without the 
nvidia driver.

Fix the nv driver so it will run this screen at its native resolution and I'll 
be glad to run it even if it won't run google earth, which I do use from time 
to time.  Now, if in all the hits you can get from google on this, currently 
14,800 just for 'exception Emask', apparently caused by a timeout, if 100% of 
the complainers are running nvidia drivers also, then I see a legit 
complaint.  Again, fix the nv driver so it will run my screen & I'll be glad 
to switch.  I can see the reason, sure, but the machine must be capable of 
doing its common day to day stuff, while using that driver, like running kde 
for kmail, and browsers that work.

>If the problems persist, please try to capture a complete log from the
>failing kernel -- the interesting bits are everything from initial boot
>up to and including the first few errors. You may need to increase the
>kernel's log buffer size if the log gets truncated (CONFIG_LOG_BUF_SHIFT).

If by log you mean /var/log/messages, I have several megabytes of those.
If you mean a live dmesg capture taken right now, its attached. It contains 
several of these at the bottom.  I long ago made the kernel log buffer 
bigger, cuz it couldn't even show the start immediately after the boot, and 
even the dump to syslog was truncated.

>There are no pata_amd changes from 2.6.24-rc7 to 2.6.24 final.

That is what I was afraid of.  I've done some limited grepping in that branch 
of the kernel tree, and cannot seem to locate where this EH handler is being 
invoked from.

There is 2 lines of interest in the dmesg:

[    0.000000] Nvidia board detected. Ignoring ACPI timer override.
[    0.000000] If you got timer trouble try acpi_use_timer_override

But I have NDI what it means, kernel argument/xconfig option?

I've also done some googling, and it appears this problem is fairly widespread 
since the switchover to libata was encouraged.  A stock fedora F8 kernel 
suffers the same freezes and eventually locks up, but does it without the 
error messages being logged, it just freezes, feeling identical to this in 
the minutes before the total freeze.  I've tried 2 of those too, but the 
newest one won't even run X.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"Ada is PL/I trying to be Smalltalk.
-- Codoso diBlini

[-- Attachment #2: dmesg --]
[-- Type: text/plain, Size: 37387 bytes --]

[    0.000000] Linux version 2.6.24-rc7 (root@coyote.coyote.den) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Mon Jan 14 10:00:40 EST 2008
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[    0.000000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
[    0.000000]  BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
[    0.000000]  BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
[    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
[    0.000000] 127MB HIGHMEM available.
[    0.000000] 896MB LOWMEM available.
[    0.000000] Entering add_active_range(0, 0, 262128) 0 entries of 256 used
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA             0 ->     4096
[    0.000000]   Normal       4096 ->   229376
[    0.000000]   HighMem    229376 ->   262128
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[1] active PFN ranges
[    0.000000]     0:        0 ->   262128
[    0.000000] On node 0 totalpages: 262128
[    0.000000]   DMA zone: 32 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 4064 pages, LIFO batch:0
[    0.000000]   Normal zone: 1760 pages used for memmap
[    0.000000]   Normal zone: 223520 pages, LIFO batch:31
[    0.000000]   HighMem zone: 255 pages used for memmap
[    0.000000]   HighMem zone: 32497 pages, LIFO batch:7
[    0.000000]   Movable zone: 0 pages used for memmap
[    0.000000] DMI 2.2 present.
[    0.000000] ACPI: RSDP 000F7220, 0014 (r0 Nvidia)
[    0.000000] ACPI: RSDT 3FFF3000, 002C (r1 Nvidia AWRDACPI 42302E31 AWRD        0)
[    0.000000] ACPI: FACP 3FFF3040, 0074 (r1 Nvidia AWRDACPI 42302E31 AWRD        0)
[    0.000000] ACPI: DSDT 3FFF30C0, 4CC4 (r1 NVIDIA AWRDACPI     1000 MSFT  100000E)
[    0.000000] ACPI: FACS 3FFF0000, 0040
[    0.000000] ACPI: APIC 3FFF7DC0, 006E (r1 Nvidia AWRDACPI 42302E31 AWRD        0)
[    0.000000] Nvidia board detected. Ignoring ACPI timer override.
[    0.000000] If you got timer trouble try acpi_use_timer_override
[    0.000000] ACPI: PM-Timer IO Port: 0x4008
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] Processor #0 6:10 APIC version 16
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: BIOS IRQ0 pin2 override ignored.
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] ACPI: IRQ14 used by override.
[    0.000000] ACPI: IRQ15 used by override.
[    0.000000] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
[    0.000000] swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
[    0.000000] swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000f0000
[    0.000000] swsusp: Registered nosave memory region: 00000000000f0000 - 0000000000100000
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260081
[    0.000000] Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
[    0.000000] mapped APIC to ffffb000 (fee00000)
[    0.000000] mapped IOAPIC to ffffa000 (fec00000)
[    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] CPU 0 irqstacks, hard=c073a000 soft=c071a000
[    0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
[    0.000000] Detected 2079.551 MHz processor.
[   28.725256] Console: colour VGA+ 80x25
[   28.725259] console [tty0] enabled
[   28.725828] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[   28.726361] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[   28.756701] Memory: 1031116k/1048512k available (1938k kernel code, 16656k reserved, 967k data, 236k init, 131008k highmem)
[   28.756710] virtual kernel memory layout:
[   28.756711]     fixmap  : 0xffc55000 - 0xfffff000   (3752 kB)
[   28.756713]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
[   28.756714]     vmalloc : 0xf8800000 - 0xff7fe000   ( 111 MB)
[   28.756715]     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
[   28.756716]       .init : 0xc06dc000 - 0xc0717000   ( 236 kB)
[   28.756718]       .data : 0xc05e4944 - 0xc06d66e4   ( 967 kB)
[   28.756719]       .text : 0xc0400000 - 0xc05e4944   (1938 kB)
[   28.756722] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[   28.756770] SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
[   28.816731] Calibrating delay using timer specific routine.. 4160.90 BogoMIPS (lpj=2080452)
[   28.816763] Security Framework initialized
[   28.816770] SELinux:  Initializing.
[   28.816784] SELinux:  Starting in permissive mode
[   28.816797] selinux_register_security:  Registering secondary module capability
[   28.816800] Capability LSM initialized as secondary
[   28.816809] Mount-cache hash table entries: 512
[   28.816976] CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000 00000000 00000000 00000000 00000000
[   28.816985] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[   28.816987] CPU: L2 Cache: 512K (64 bytes/line)
[   28.816990] CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000420 00000000 00000000 00000000 00000000
[   28.816996] Intel machine check architecture supported.
[   28.816998] Intel machine check reporting enabled on CPU#0.
[   28.817003] Compat vDSO mapped to ffffe000.
[   28.817017] Checking 'hlt' instruction... OK.
[   28.820895] SMP alternatives: switching to UP code
[   28.821401] Freeing SMP alternatives: 12k freed
[   28.821404] ACPI: Core revision 20070126
[   28.824590] CPU0: AMD Athlon(tm) XP 2800+ stepping 00
[   28.824614] Total of 1 processors activated (4160.90 BogoMIPS).
[   28.824820] ENABLING IO-APIC IRQs
[   28.825012] ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1
[   28.936680] Brought up 1 CPUs
[   28.936708] CPU0 attaching sched-domain:
[   28.936711]  domain 0: span 00000001
[   28.936713]   groups: 00000001
[   28.936925] net_namespace: 64 bytes
[   28.937409] Time: 12:43:09  Date: 01/28/08
[   28.937442] NET: Registered protocol family 16
[   28.937683] ACPI: bus type pci registered
[   28.972986] PCI: PCI BIOS revision 2.10 entry at 0xfb4c0, last bus=2
[   28.972989] PCI: Using configuration type 1
[   28.972991] Setting up standard PCI resources
[   28.980763] ACPI: EC: Look up EC in DSDT
[   28.986590] ACPI: Interpreter enabled
[   28.986593] ACPI: (supports S0 S1 S4 S5)
[   28.986608] ACPI: Using IOAPIC for interrupt routing
[   28.997079] ACPI: PCI Root Bridge [PCI0] (0000:00)
[   28.997157] PCI: nForce2 C1 Halt Disconnect fixup
[   28.998175] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[   28.998355] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
[   28.998631] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
[   29.054757] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[   29.054952] ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[   29.055144] ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[   29.055334] ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[   29.055529] ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.055724] ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[   29.055918] ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 10 11 *12 14 15)
[   29.056109] ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 11 *12 14 15)
[   29.056298] ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.056489] ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 6 7 10 11 *12 14 15)
[   29.056685] ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.056876] ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.057066] ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[   29.057258] ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.057448] ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.057642] ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   29.057803] ACPI: PCI Interrupt Link [APC1] (IRQs *16)
[   29.057951] ACPI: PCI Interrupt Link [APC2] (IRQs *17)
[   29.058099] ACPI: PCI Interrupt Link [APC3] (IRQs *18)
[   29.058246] ACPI: PCI Interrupt Link [APC4] (IRQs *19)
[   29.058402] ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
[   29.058617] ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0
[   29.058827] ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22) *0
[   29.059036] ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0
[   29.059245] ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22) *0, disabled.
[   29.059454] ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22) *0
[   29.059669] ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22) *0, disabled.
[   29.059819] ACPI: PCI Interrupt Link [APCS] (IRQs *23), disabled.
[   29.060028] ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22) *0
[   29.060236] ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0, disabled.
[   29.060446] ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22) *0, disabled.
[   29.060661] ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22) *0, disabled.
[   29.060822] ACPI: Power Resource [ISAV] (on)
[   29.060880] Linux Plug and Play Support v0.97 (c) Adam Belay
[   29.060917] pnp: PnP ACPI init
[   29.060926] ACPI: bus type pnp registered
[   29.066989] pnp: PnP ACPI: found 16 devices
[   29.066992] ACPI: ACPI bus type pnp unregistered
[   29.067179] usbcore: registered new interface driver usbfs
[   29.067257] usbcore: registered new interface driver hub
[   29.067309] usbcore: registered new device driver usb
[   29.067395] PCI: Using ACPI for IRQ routing
[   29.067399] PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
[   29.117453] NetLabel: Initializing
[   29.117455] NetLabel:  domain hash size = 128
[   29.117457] NetLabel:  protocols = UNLABELED CIPSOv4
[   29.117471] NetLabel:  unlabeled traffic allowed by default
[   29.118443] Time: tsc clocksource has been installed.
[   29.120481] system 00:00: ioport range 0x4000-0x407f has been reserved
[   29.120484] system 00:00: ioport range 0x4080-0x40ff has been reserved
[   29.120487] system 00:00: ioport range 0x4400-0x447f has been reserved
[   29.120490] system 00:00: ioport range 0x4480-0x44ff has been reserved
[   29.120492] system 00:00: ioport range 0x4200-0x427f has been reserved
[   29.120495] system 00:00: ioport range 0x4280-0x42ff has been reserved
[   29.120502] system 00:01: ioport range 0x5000-0x503f has been reserved
[   29.120505] system 00:01: ioport range 0x5100-0x513f has been reserved
[   29.120511] system 00:02: iomem range 0xda800-0xdbfff has been reserved
[   29.120514] system 00:02: iomem range 0xf0000-0xf7fff could not be reserved
[   29.120516] system 00:02: iomem range 0xf8000-0xfbfff could not be reserved
[   29.120519] system 00:02: iomem range 0xfc000-0xfffff could not be reserved
[   29.120522] system 00:02: iomem range 0x3fff0000-0x3fffffff could not be reserved
[   29.120525] system 00:02: iomem range 0xffff0000-0xffffffff could not be reserved
[   29.120528] system 00:02: iomem range 0x0-0x9ffff could not be reserved
[   29.120531] system 00:02: iomem range 0x100000-0x3ffeffff could not be reserved
[   29.120534] system 00:02: iomem range 0xfec00000-0xfec00fff could not be reserved
[   29.120537] system 00:02: iomem range 0xfee00000-0xfee00fff could not be reserved
[   29.120543] system 00:04: ioport range 0xb78-0xb7b has been reserved
[   29.120546] system 00:04: ioport range 0xf78-0xf7b has been reserved
[   29.120548] system 00:04: ioport range 0xa78-0xa7b has been reserved
[   29.120551] system 00:04: ioport range 0xe78-0xe7b has been reserved
[   29.120554] system 00:04: ioport range 0xbbc-0xbbf has been reserved
[   29.120556] system 00:04: ioport range 0xfbc-0xfbf has been reserved
[   29.120559] system 00:04: ioport range 0x4d0-0x4d1 has been reserved
[   29.120562] system 00:04: ioport range 0x294-0x297 has been reserved
[   29.151040] PCI: Bridge: 0000:00:08.0
[   29.151044]   IO window: 9000-afff
[   29.151049]   MEM window: e3000000-e6ffffff
[   29.151053]   PREFETCH window: 50000000-500fffff
[   29.151058] PCI: Bridge: 0000:00:1e.0
[   29.151059]   IO window: disabled.
[   29.151063]   MEM window: e0000000-e2ffffff
[   29.151066]   PREFETCH window: d0000000-dfffffff
[   29.151077] PCI: Setting latency timer of device 0000:00:08.0 to 64
[   29.151093] NET: Registered protocol family 2
[   29.160585] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[   29.160952] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[   29.162429] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[   29.163092] TCP: Hash tables configured (established 131072 bind 65536)
[   29.163095] TCP reno registered
[   29.165574] checking if image is initramfs... it is
[   29.446295] Freeing initrd memory: 3628k freed
[   29.446709] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[   29.446712] apm: overridden by ACPI.
[   29.447133] audit: initializing netlink socket (disabled)
[   29.447149] audit(1201524188.569:1): initialized
[   29.447287] highmem bounce pool size: 64 pages
[   29.447291] Total HugeTLB memory allocated, 0
[   29.449941] SELinux:  Registering netfilter hooks
[   29.450082] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[   29.450086] io scheduler noop registered
[   29.450088] io scheduler anticipatory registered
[   29.450090] io scheduler deadline registered
[   29.450101] io scheduler cfq registered (default)
[   29.472109] Boot video device is 0000:02:00.0
[   29.477398] ACPI: Thermal Zone [THRM] (51 C)
[   29.477413] isapnp: Scanning for PnP cards...
[   29.650914] Switched to high resolution mode on CPU 0
[   29.834322] isapnp: No Plug & Play device found
[   29.837157] Real Time Clock Driver v1.12ac
[   29.837309] Non-volatile memory driver v1.2
[   29.837312] Linux agpgart interface v0.102
[   29.837365] agpgart: Detected NVIDIA nForce2 chipset
[   29.853228] agpgart: AGP aperture is 256M @ 0xc0000000
[   29.853255] Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
[   29.853403] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[   29.853542] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[   29.853854] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[   29.854037] 00:0b: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[   29.855000] RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
[   29.855188] PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[   29.855191] PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[   29.855565] serio: i8042 KBD port at 0x60,0x64 irq 1
[   29.855638] mice: PS/2 mouse device common for all mice
[   29.876081] input: AT Translated Set 2 keyboard as /class/input/input0
[   29.878901] cpuidle: using governor ladder
[   29.878904] cpuidle: using governor menu
[   29.878982] usbcore: registered new interface driver hiddev
[   29.879024] usbcore: registered new interface driver usbhid
[   29.879027] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[   29.879098] TCP cubic registered
[   29.879100] Initializing XFRM netlink socket
[   29.879180] NET: Registered protocol family 1
[   29.879196] NET: Registered protocol family 17
[   29.879204] Using IPI No-Shortcut mode
[   29.879217] registered taskstats version 1
[   29.879349]   Magic number: 8:30:735
[   29.879657] Freeing unused kernel memory: 236k freed
[   29.879695] Write protecting the kernel text: 1940k
[   29.879708] Write protecting the kernel read-only data: 758k
[   30.175117] ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
[   30.175126] ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [APCL] -> GSI 22 (level, high) -> IRQ 16
[   30.175139] PCI: Setting latency timer of device 0000:00:02.2 to 64
[   30.175143] ehci_hcd 0000:00:02.2: EHCI Host Controller
[   30.175235] ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
[   30.175275] ehci_hcd 0000:00:02.2: debug port 1
[   30.175280] PCI: cache line size of 64 is not supported by device 0000:00:02.2
[   30.175291] ehci_hcd 0000:00:02.2: irq 16, io mem 0xe7005000
[   30.180677] ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[   30.180795] usb usb1: configuration #1 chosen from 1 choice
[   30.180823] hub 1-0:1.0: USB hub found
[   30.180834] hub 1-0:1.0: 6 ports detected
[   30.287626] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
[   30.288031] ACPI: PCI Interrupt Link [APCF] enabled at IRQ 21
[   30.288038] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 21 (level, high) -> IRQ 17
[   30.288052] PCI: Setting latency timer of device 0000:00:02.0 to 64
[   30.288055] ohci_hcd 0000:00:02.0: OHCI Host Controller
[   30.288129] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
[   30.288148] ohci_hcd 0000:00:02.0: irq 17, io mem 0xe7003000
[   30.340664] usb usb2: configuration #1 chosen from 1 choice
[   30.340691] hub 2-0:1.0: USB hub found
[   30.340704] hub 2-0:1.0: 3 ports detected
[   30.441860] ACPI: PCI Interrupt Link [APCG] enabled at IRQ 20
[   30.441865] ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCG] -> GSI 20 (level, high) -> IRQ 18
[   30.441873] PCI: Setting latency timer of device 0000:00:02.1 to 64
[   30.441876] ohci_hcd 0000:00:02.1: OHCI Host Controller
[   30.441932] ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3
[   30.441945] ohci_hcd 0000:00:02.1: irq 18, io mem 0xe7004000
[   30.487468] usb 1-1: new high speed USB device using ehci_hcd and address 2
[   30.494540] usb usb3: configuration #1 chosen from 1 choice
[   30.494569] hub 3-0:1.0: USB hub found
[   30.494579] hub 3-0:1.0: 3 ports detected
[   30.601427] USB Universal Host Controller Interface driver v3.0
[   30.601865] usb 1-1: configuration #1 chosen from 1 choice
[   30.602052] hub 1-1:1.0: USB hub found
[   30.602151] hub 1-1:1.0: 4 ports detected
[   30.660576] SCSI subsystem initialized
[   30.673851] Driver 'sd' needs updating - please use bus_type methods
[   30.700319] libata version 3.00 loaded.
[   30.702887] pata_amd 0000:00:09.0: version 0.3.10
[   30.703052] PCI: Setting latency timer of device 0000:00:09.0 to 64
[   30.703188] scsi0 : pata_amd
[   30.709313] scsi1 : pata_amd
[   30.710076] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
[   30.710079] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
[   30.864753] ata1.00: ATA-6: WDC WD2000JB-00EVA0, 15.05R15, max UDMA/100
[   30.864756] ata1.00: 390721968 sectors, multi 16: LBA48 
[   30.871629] ata1.00: configured for UDMA/100
[   31.195305] ata2.00: ATAPI: LITE-ON DVDRW SHM-165H6S, HS06, max UDMA/66
[   31.243813] ata2.01: ATA-7: MAXTOR STM3320620A, 3.AAE, max UDMA/100
[   31.243816] ata2.01: 625142448 sectors, multi 16: LBA48 
[   31.243825] ata2.00: limited to UDMA/33 due to 40-wire cable
[   31.417074] ata2.00: configured for UDMA/33
[   31.451769] ata2.01: configured for UDMA/100
[   31.451873] scsi 0:0:0:0: Direct-Access     ATA      WDC WD2000JB-00E 15.0 PQ: 0 ANSI: 5
[   31.451953] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[   31.451967] sd 0:0:0:0: [sda] Write Protect is off
[   31.451970] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   31.451989] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   31.452040] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[   31.452051] sd 0:0:0:0: [sda] Write Protect is off
[   31.452054] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   31.452071] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   31.452075]  sda: sda1 sda2
[   31.467219] sd 0:0:0:0: [sda] Attached SCSI disk
[   31.468093] scsi 1:0:0:0: CD-ROM            LITE-ON  DVDRW SHM-165H6S HS06 PQ: 0 ANSI: 5
[   31.468208] scsi 1:0:1:0: Direct-Access     ATA      MAXTOR STM332062 3.AA PQ: 0 ANSI: 5
[   31.468272] sd 1:0:1:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
[   31.468283] sd 1:0:1:0: [sdb] Write Protect is off
[   31.468286] sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[   31.468303] sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   31.468338] sd 1:0:1:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
[   31.468349] sd 1:0:1:0: [sdb] Write Protect is off
[   31.468352] sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[   31.468370] sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   31.468373]  sdb:<6>usb 2-2: new full speed USB device using ohci_hcd and address 2
[   31.499690]  sdb1 sdb2 sdb3
[   31.500119] sd 1:0:1:0: [sdb] Attached SCSI disk
[   31.637428] usb 2-2: configuration #1 chosen from 1 choice
[   31.856522] usb 2-3: new low speed USB device using ohci_hcd and address 3
[   32.020045] usb 2-3: configuration #1 chosen from 1 choice
[   32.035222] input: Chicony Saitek Eclipse II Keyboard as /class/input/input1
[   32.038424] input,hidraw0: USB HID v1.11 Keyboard [Chicony Saitek Eclipse II Keyboard] on usb-0000:00:02.0-3
[   32.067995] input: Chicony Saitek Eclipse II Keyboard as /class/input/input2
[   32.070422] input,hiddev96,hidraw1: USB HID v1.11 Device [Chicony Saitek Eclipse II Keyboard] on usb-0000:00:02.0-3
[   32.287225] usb 3-3: new full speed USB device using ohci_hcd and address 2
[   32.422699] usb 3-3: configuration #1 chosen from 1 choice
[   32.425658] hub 3-3:1.0: USB hub found
[   32.428631] hub 3-3:1.0: 4 ports detected
[   32.724000] usb 1-1.1: new low speed USB device using ehci_hcd and address 6
[   32.919001] usb 1-1.1: configuration #1 chosen from 1 choice
[   33.655893] hiddev97hidraw2: USB HID v1.11 Device [Belkin  Belkin UPS] on usb-0000:00:02.2-1.1
[   33.833315] usb 1-1.2: new full speed USB device using ehci_hcd and address 7
[   33.925926] usb 1-1.2: configuration #1 chosen from 1 choice
[   34.018028] device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com
[   34.043070] sata_sil 0000:01:0a.0: version 2.3
[   34.043348] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
[   34.043355] ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC1] -> GSI 16 (level, high) -> IRQ 19
[   34.045029] scsi2 : sata_sil
[   34.050031] scsi3 : sata_sil
[   34.050064] ata3: SATA max UDMA/100 mmio m512@0xe6004000 tf 0xe6004080 irq 19
[   34.050068] ata4: SATA max UDMA/100 mmio m512@0xe6004000 tf 0xe60040c0 irq 19
[   34.107056] usb 1-1.4: new high speed USB device using ehci_hcd and address 8
[   34.192310] usb 1-1.4: configuration #1 chosen from 1 choice
[   34.192499] hub 1-1.4:1.0: USB hub found
[   34.192597] hub 1-1.4:1.0: 4 ports detected
[   34.352811] ata3: SATA link down (SStatus 0 SControl 310)
[   34.481823] usb 1-1.4.3: new low speed USB device using ehci_hcd and address 9
[   34.573676] usb 1-1.4.3: configuration #1 chosen from 1 choice
[   34.577917] input: Logitech USB Receiver as /class/input/input3
[   34.580691] input,hidraw3: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:02.2-1.4.3
[   34.757557] usb 1-1.4.4: new full speed USB device using ehci_hcd and address 10
[   34.806514] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   34.810071] ata4.00: ATA-7: Hitachi HDT725040VLA360, V5COA7EA, max UDMA/133
[   34.810074] ata4.00: 781422768 sectors, multi 16: LBA48 NCQ (depth 0/32)
[   34.816059] ata4.00: configured for UDMA/100
[   34.816175] scsi 3:0:0:0: Direct-Access     ATA      Hitachi HDT72504 V5CO PQ: 0 ANSI: 5
[   34.816257] sd 3:0:0:0: [sdc] 781422768 512-byte hardware sectors (400088 MB)
[   34.816271] sd 3:0:0:0: [sdc] Write Protect is off
[   34.816274] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[   34.816293] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   34.816344] sd 3:0:0:0: [sdc] 781422768 512-byte hardware sectors (400088 MB)
[   34.816355] sd 3:0:0:0: [sdc] Write Protect is off
[   34.816358] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[   34.816375] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   34.816379]  sdc: sdc1
[   34.829837] sd 3:0:0:0: [sdc] Attached SCSI disk
[   34.843933] usb 1-1.4.4: configuration #1 chosen from 1 choice
[   37.852458] EXT3-fs: INFO: recovery required on readonly filesystem.
[   37.852464] EXT3-fs: write access will be enabled during recovery.
[   41.522866] kjournald starting.  Commit interval 5 seconds
[   41.522885] EXT3-fs: recovery complete.
[   41.524254] EXT3-fs: mounted filesystem with ordered data mode.
[   41.972449] audit(1201524201.103:2): enforcing=1 old_enforcing=0 auid=4294967295
[   42.187011] SELinux:8192 avtab hash slots allocated.Num of rules:213166
[   42.260611] SELinux:8192 avtab hash slots allocated.Num of rules:213166
[   42.314117] security:  8 users, 11 roles, 2363 types, 114 bools, 1 sens, 1024 cats
[   42.314122] security:  67 classes, 213166 rules
[   42.327287] SELinux:  Completing initialization.
[   42.327290] SELinux:  Setting up existing superblocks.
[   42.353550] SELinux: initialized (dev dm-0, type ext3), uses xattr
[   42.515071] SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
[   42.515088] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[   42.515193] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
[   42.515205] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
[   42.515235] SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
[   42.515244] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts
[   42.515250] SELinux: initialized (dev devpts, type devpts), uses transition SIDs
[   42.515262] SELinux: initialized (dev inotifyfs, type inotifyfs), uses genfs_contexts
[   42.515266] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[   42.515274] SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
[   42.515280] SELinux: initialized (dev anon_inodefs, type anon_inodefs), uses genfs_contexts
[   42.515285] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
[   42.515290] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
[   42.515299] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[   42.515312] SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
[   42.515318] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
[   42.515341] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
[   42.520002] SELinux: policy loaded with handle_unknown=allow
[   42.520011] audit(1201524201.651:3): policy loaded auid=4294967295
[   46.528101] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   46.528126] scsi 1:0:0:0: Attached scsi generic sg1 type 5
[   46.528149] sd 1:0:1:0: Attached scsi generic sg2 type 0
[   46.528174] sd 3:0:0:0: Attached scsi generic sg3 type 0
[   46.931288] input: Power Button (FF) as /class/input/input4
[   46.938141] ACPI: Power Button (FF) [PWRF]
[   46.938186] ACPI Error (evxfevnt-0186): Could not enable SleepButton event [20070126]
[   46.938192] ACPI Warning (evxface-0145): Could not enable fixed event 3 [20070126]
[   46.938283] input: Power Button (CM) as /class/input/input5
[   46.941132] ACPI: Power Button (CM) [PWRB]
[   46.941190] input: Sleep Button (CM) as /class/input/input6
[   46.944347] ACPI: Sleep Button (CM) [SLPB]
[   47.285717] usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x04B8 pid 0x0005
[   47.285742] usbcore: registered new interface driver usblp
[   47.308848] i2c-adapter i2c-0: nForce2 SMBus adapter at 0x5000
[   47.308876] i2c-adapter i2c-1: nForce2 SMBus adapter at 0x5100
[   47.352146] usbcore: registered new interface driver usbserial
[   47.352152] drivers/usb/serial/usb-serial.c: USB Serial Driver core
[   47.455275] drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
[   47.455308] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
[   47.455342] drivers/usb/serial/ftdi_sio.c: Detected FT232RL
[   47.455381] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
[   47.455398] usbcore: registered new interface driver ftdi_sio
[   47.455401] drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
[   47.530751] input: PC Speaker as /class/input/input7
[   47.572764] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
[   47.573147] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 22
[   47.573151] ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCH] -> GSI 22 (level, high) -> IRQ 16
[   47.573158] PCI: Setting latency timer of device 0000:00:04.0 to 64
[   47.615492] Floppy drive(s): fd0 is 1.44M
[   47.630509] FDC 0 is a post-1991 82077
[   48.084769] forcedeth 0000:00:04.0: ifname eth0, PHY OUI 0x20 @ 1, addr 00:04:4b:5d:eb:7d
[   48.084775] forcedeth 0000:00:04.0: timirq lnktim desc-v1
[   48.085214] ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
[   48.085222] ACPI: PCI Interrupt 0000:01:09.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 20
[   48.141308] firewire_ohci: Added fw-ohci device 0000:01:09.0, OHCI version 1.10
[   48.285456] nvidia: module license 'NVIDIA' taints kernel.
[   48.549725] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 20
[   48.550149] NVRM: loading NVIDIA UNIX x86 Kernel Module  169.07  Thu Dec 13 18:42:56 PST 2007
[   48.641028] firewire_core: created new fw device fw0 (0 config rom retries, S400)
[   48.848094] Linux video capture interface: v2.00
[   49.104974] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
[   49.105072] cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV [card=22,autodetected]
[   49.105076] cx88[0]: TV tuner type 60, Radio tuner type -1
[   49.151205] cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
[   49.255507] cx88[0]/2: cx2388x 8802 Driver Manager
[   49.257461] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
[   49.257472] ACPI: PCI Interrupt 0000:01:07.2[A] -> Link [APC2] -> GSI 17 (level, high) -> IRQ 21
[   49.257484] cx88[0]/2: found at 0000:01:07.2, rev: 5, irq: 21, latency: 32, mmio: 0xe4000000
[   49.257561] ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC2] -> GSI 17 (level, high) -> IRQ 21
[   49.257573] cx88[0]/0: found at 0000:01:07.0, rev: 5, irq: 21, latency: 32, mmio: 0xe3000000
[   49.440179] tda8290_probe: not probed - driver disabled by Kconfig
[   49.440185] tuner 2-0043: chip found @ 0x86 (cx88[0])
[   49.440208] tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
[   49.440211] tuner 2-0043: type set to tda9887
[   49.442442] tuner 2-0061: chip found @ 0xc2 (cx88[0])
[   49.442458] tuner-simple 2-0061: type set to 60 (Thomson DTT 761X (ATSC/NTSC))
[   49.442461] tuner 2-0061: type set to Thomson DTT 761X (A
[   49.442464] tuner-simple 2-0061: type set to 60 (Thomson DTT 761X (ATSC/NTSC))
[   49.442466] tuner 2-0061: type set to Thomson DTT 761X (A
[   49.451016] cx88[0]/0: registered device video0 [v4l2]
[   49.451038] cx88[0]/0: registered device vbi0
[   49.451064] cx88[0]/0: registered device radio0
[   49.454722] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
[   49.454731] ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC3] -> GSI 18 (level, high) -> IRQ 22
[   49.459555] Audigy2 value: Special config.
[   49.532042] cx88/2: cx2388x dvb driver version 0.0.6 loaded
[   49.532047] cx88/2: registering cx8802 driver, type: dvb access: shared
[   49.532052] cx88[0]/2: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV [card=22]
[   49.532055] cx88[0]/2: cx2388x based DVB/ATSC card
[   49.548119] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 21
[   49.548125] ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 21 (level, high) -> IRQ 17
[   49.548162] PCI: Setting latency timer of device 0000:00:06.0 to 64
[   49.654575] DVB: registering new adapter (cx88[0])
[   49.654582] DVB: registering frontend 0 (Oren OR51132 VSB/QAM Frontend)...
[   49.859126] intel8x0_measure_ac97_clock: measured 50668 usecs
[   49.859131] intel8x0: clocking to 47378
[   52.910654] EXT3 FS on dm-0, internal journal
[   53.162621] kjournald starting.  Commit interval 5 seconds
[   53.170013] EXT3 FS on sda1, internal journal
[   53.170019] EXT3-fs: mounted filesystem with ordered data mode.
[   53.170144] SELinux: initialized (dev sda1, type ext3), uses xattr
[   53.170540] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[   53.174936] kjournald starting.  Commit interval 5 seconds
[   53.182987] EXT3 FS on sdc1, internal journal
[   53.182992] EXT3-fs: mounted filesystem with ordered data mode.
[   53.188827] SELinux: initialized (dev sdc1, type ext3), uses xattr
[   54.005729] Adding 2031608k swap on /dev/mapper/VolGroup00-LogVol01.  Priority:-1 extents:1 across:2031608k
[   54.009417] SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
[   54.393108] warning: process `kudzu' used the deprecated sysctl system call with 1.23.
[   54.885156] NET: Registered protocol family 10
[   54.885386] lo: Disabled Privacy Extensions
[   60.537079] RPC: Registered udp transport module.
[   60.537083] RPC: Registered tcp transport module.
[   60.540347] SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts
[   61.293946] w83627hf: Found W83627HF chip at 0x290
[   61.812622] audit(1201524221.948:4): audit_pid=1910 old=0 by auid=4294967295 subj=system_u:system_r:auditd_t:s0
[   63.746132] SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
[   64.231812] SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
[   64.362173] SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
[   66.015990] eth0: no IPv6 routers present
[  147.668171] agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
[  147.668186] agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
[  147.668257] agpgart: Putting AGP V3 device at 0000:02:00.0 into 8x mode
[ 1712.473539] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 1712.473551] ata1.00: cmd 35/00:18:59:22:a2/00:00:12:00:00/e0 tag 0 dma 12288 out
[ 1712.473553]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1712.473556] ata1.00: status: { DRDY }
[ 1712.473584] ata1: soft resetting link
[ 1712.635816] ata1.00: configured for UDMA/100
[ 1712.635832] ata1: EH complete
[ 1712.636296] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[ 1712.636447] sd 0:0:0:0: [sda] Write Protect is off
[ 1712.636452] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1712.636698] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1772.618397] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 1772.618409] ata1.00: cmd ca/00:08:b9:85:68/00:00:00:00:00/e8 tag 0 dma 4096 out
[ 1772.618410]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1772.618414] ata1.00: status: { DRDY }
[ 1772.618441] ata1: soft resetting link
[ 1772.780653] ata1.00: configured for UDMA/100
[ 1772.780669] ata1: EH complete
[ 1772.804931] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[ 1772.812120] sd 0:0:0:0: [sda] Write Protect is off
[ 1772.812125] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1772.848506] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 8943.320830] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[ 8943.320842] ata1.00: cmd 35/00:18:59:22:a2/00:00:12:00:00/e0 tag 0 dma 12288 out
[ 8943.320844]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 8943.320847] ata1.00: status: { DRDY }
[ 8943.320874] ata1: soft resetting link
[ 8943.483114] ata1.00: configured for UDMA/100
[ 8943.483129] ata1: EH complete
[ 8943.483585] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[ 8943.483738] sd 0:0:0:0: [sda] Write Protect is off
[ 8943.483743] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 8943.483993] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Re: Problem with ata layer in 2.6.24

[Calvin Walton]

On Mon, 2008-01-28 at 11:35 -0500, Gene Heskett wrote:
> On Monday 28 January 2008, Mikael Pettersson wrote:
> >Unfortunately we also see:
> > > [   48.285456] nvidia: module license 'NVIDIA' taints kernel.
> > > [   48.549725] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI
> > > 19 (level, high) -> IRQ 20 [   48.550149] NVRM: loading NVIDIA UNIX x86
> > > Kernel Module  169.07  Thu Dec 13 18:42:56 PST 2007
> >
> >We have no way of debugging that module, so please try 2.6.24 without it.
> 
> Sorry, I can't do this and have a working machine.  The nv driver has suffered 
> bit rot or something since the FC2 days when it COULD run a 19" crt at 
> 1600x1200, and will not drive this 20" wide screen lcd 1680x1050 monitor at 
> more than 800x600, which is absolutely butt ugly fuzzy, looking like a jpg 
> compressed to 10%.  The system is not usable on a day to basis without the 
> nvidia driver.

You should probably give the nouveau[1] driver a try, if only for
testing purposes; if you are running an NV4x (G6x or G7x) card in
particular, it works a lot better than the nv driver for 2d support.

1. http://nouveau.freedesktop.org/wiki/InstallNouveau

-- 
Calvin Walton <calvin.walton@gmail.com>

Re: Problem with ata layer in 2.6.24

[Zan Lynx]

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


On Mon, 2008-01-28 at 11:50 -0500, Calvin Walton wrote:
> On Mon, 2008-01-28 at 11:35 -0500, Gene Heskett wrote:
> > On Monday 28 January 2008, Mikael Pettersson wrote:
> > >Unfortunately we also see:
> > > > [   48.285456] nvidia: module license 'NVIDIA' taints kernel.
> > > > [   48.549725] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI
> > > > 19 (level, high) -> IRQ 20 [   48.550149] NVRM: loading NVIDIA UNIX x86
> > > > Kernel Module  169.07  Thu Dec 13 18:42:56 PST 2007
> > >
> > >We have no way of debugging that module, so please try 2.6.24 without it.
> > 
> > Sorry, I can't do this and have a working machine.  The nv driver has suffered 
> > bit rot or something since the FC2 days when it COULD run a 19" crt at 
> > 1600x1200, and will not drive this 20" wide screen lcd 1680x1050 monitor at 
> > more than 800x600, which is absolutely butt ugly fuzzy, looking like a jpg 
> > compressed to 10%.  The system is not usable on a day to basis without the 
> > nvidia driver.
> 
> You should probably give the nouveau[1] driver a try, if only for
> testing purposes; if you are running an NV4x (G6x or G7x) card in
> particular, it works a lot better than the nv driver for 2d support.
> 
> 1. http://nouveau.freedesktop.org/wiki/InstallNouveau

But nouveau is much less stable than nv.  For testing purposes, go with
stable.

I'm not sure why it won't run his screen though.  I can use nv to run a
1920x1200 laptop LCD.  It *is* dog slow (although nouveau was not any
better with a NV17 / 440-Go -- render support for AA fonts seems to be
missing), but it does work.
-- 
Zan Lynx <zlynx@acm.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Zan Lynx wrote:
>On Mon, 2008-01-28 at 11:50 -0500, Calvin Walton wrote:
>> On Mon, 2008-01-28 at 11:35 -0500, Gene Heskett wrote:
>> > On Monday 28 January 2008, Mikael Pettersson wrote:
>> > >Unfortunately we also see:
>> > > > [   48.285456] nvidia: module license 'NVIDIA' taints kernel.
>> > > > [   48.549725] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] ->
>> > > > GSI 19 (level, high) -> IRQ 20 [   48.550149] NVRM: loading NVIDIA
>> > > > UNIX x86 Kernel Module  169.07  Thu Dec 13 18:42:56 PST 2007
>> > >
>> > >We have no way of debugging that module, so please try 2.6.24 without
>> > > it.
>> >
>> > Sorry, I can't do this and have a working machine.  The nv driver has
>> > suffered bit rot or something since the FC2 days when it COULD run a 19"
>> > crt at 1600x1200, and will not drive this 20" wide screen lcd 1680x1050
>> > monitor at more than 800x600, which is absolutely butt ugly fuzzy,
>> > looking like a jpg compressed to 10%.  The system is not usable on a day
>> > to basis without the nvidia driver.
>>
>> You should probably give the nouveau[1] driver a try, if only for
>> testing purposes; if you are running an NV4x (G6x or G7x) card in
>> particular, it works a lot better than the nv driver for 2d support.
>>
>> 1. http://nouveau.freedesktop.org/wiki/InstallNouveau
>
>But nouveau is much less stable than nv.  For testing purposes, go with
>stable.
>
I believe at this point, its moot.  I captured quite a few instances of that 
error message while rebooting the last time, all of which occurred long 
before I logged in and did a startx (I boot to runlevel 3 here), so the 
kernel was NOT tainted at that point.  That dmesg has been posted and some 
questions asked.

As this has gone on for a while, it seems to me that with 14,800 google hits 
on this problem, Linus should call a halt until this is found and fixed.  But 
I'm not Linus.  I'm also locking up for 30 at a time, & probably ready for 
reboot #7 today.

>I'm not sure why it won't run his screen though.  I can use nv to run a
>1920x1200 laptop LCD.  It *is* dog slow (although nouveau was not any
>better with a NV17 / 440-Go -- render support for AA fonts seems to be
>missing), but it does work.



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
There cannot be a crisis next week.  My schedule is already full.
		-- Henry Kissinger

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

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

On Monday 28 January 2008, Gene Heskett wrote:
>On Monday 28 January 2008, Zan Lynx wrote:
>>On Mon, 2008-01-28 at 11:50 -0500, Calvin Walton wrote:
>>> On Mon, 2008-01-28 at 11:35 -0500, Gene Heskett wrote:
>>> > On Monday 28 January 2008, Mikael Pettersson wrote:
>>> > >Unfortunately we also see:
>>> > > > [   48.285456] nvidia: module license 'NVIDIA' taints kernel.
>>> > > > [   48.549725] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4]
>>> > > > -> GSI 19 (level, high) -> IRQ 20 [   48.550149] NVRM: loading
>>> > > > NVIDIA UNIX x86 Kernel Module  169.07  Thu Dec 13 18:42:56 PST 2007
>>> > >
>>> > >We have no way of debugging that module, so please try 2.6.24 without
>>> > > it.
>>> >
>>> > Sorry, I can't do this and have a working machine.  The nv driver has
>>> > suffered bit rot or something since the FC2 days when it COULD run a
>>> > 19" crt at 1600x1200, and will not drive this 20" wide screen lcd
>>> > 1680x1050 monitor at more than 800x600, which is absolutely butt ugly
>>> > fuzzy, looking like a jpg compressed to 10%.  The system is not usable
>>> > on a day to basis without the nvidia driver.
>>>
>>> You should probably give the nouveau[1] driver a try, if only for
>>> testing purposes; if you are running an NV4x (G6x or G7x) card in
>>> particular, it works a lot better than the nv driver for 2d support.
>>>
>>> 1. http://nouveau.freedesktop.org/wiki/InstallNouveau
>>
>>But nouveau is much less stable than nv.  For testing purposes, go with
>>stable.
>
>I believe at this point, its moot.  I captured quite a few instances of that
>error message while rebooting the last time, all of which occurred long
>before I logged in and did a startx (I boot to runlevel 3 here), so the
>kernel was NOT tainted at that point.  That dmesg has been posted and some
>questions asked.
>
>As this has gone on for a while, it seems to me that with 14,800 google hits
>on this problem, Linus should call a halt until this is found and fixed. 
> But I'm not Linus.  I'm also locking up for 30 at a time, & probably ready
> for reboot #7 today.
>
>>I'm not sure why it won't run his screen though.  I can use nv to run a
>>1920x1200 laptop LCD.  It *is* dog slow (although nouveau was not any
>>better with a NV17 / 440-Go -- render support for AA fonts seems to be
>>missing), but it does work.

I've been trying to run a long selftest on that drive, but the constant 
reboots are fscking that up.  I have attached the last smartctl -a output, 
indicating that the test was aborted probably from all the resets that are 
being issued, the last one froze me for around 5 minutes but I haven't 
rebooted yet.  Its attached.  Can anyone see if there is actually anything 
wrong with the drive?  If a boot will last long enough for the -t long to 
complete, then it passes with no errors, but this was interrupted now for the 
3rd time.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Well begun is half done.
		-- Aristotle

[-- Attachment #2: smart.log --]
[-- Type: text/x-log, Size: 9050 bytes --]

smartctl version 5.37 [i386-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar SE family
Device Model:     WDC WD2000JB-00EVA0
Serial Number:    WD-WMAEH2782398
Firmware Version: 15.05R15
User Capacity:    200,049,647,616 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   6
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Mon Jan 28 12:39:08 2008 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x85)	Offline data collection activity
					was aborted by an interrupting command from host.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 249)	Self-test routine in progress...
					90% of test remaining.
Total time to complete Offline 
data collection: 		 (6942) seconds.
Offline data collection
capabilities: 			 (0x79) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					No General Purpose Logging support.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  88) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   194   194   051    Pre-fail  Always       -       12
  3 Spin_Up_Time            0x0007   180   124   021    Pre-fail  Always       -       1500
  4 Start_Stop_Count        0x0032   100   100   040    Old_age   Always       -       182
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   200   200   051    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   062   062   000    Old_age   Always       -       27779
 10 Spin_Retry_Count        0x0013   100   100   051    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x0013   100   100   051    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       178
194 Temperature_Celsius     0x0022   120   253   000    Old_age   Always       -       30
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0012   200   200   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x000a   200   253   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0009   200   155   051    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 12 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 12 occurred at disk power-on lifetime: 472 hours (19 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 58 8b 3d 07 e0  Error: 

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 c8 00 00 58 00 00      00:03:35.550  NOP [Abort queued commands]
  00 00 00 00 00 00 00 00      00:03:35.550  NOP [Abort queued commands]
  00 00 ef 00 00 45 00 00      00:03:35.550  NOP [Abort queued commands]
  00 00 27 00 00 00 00 00      00:03:35.550  NOP [Abort queued commands]
  00 00 07 00 00 89 3d 00      00:03:35.550  NOP [Abort queued commands]

Error 11 occurred at disk power-on lifetime: 472 hours (19 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 58 8b 3d 07 e0  Error: 

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 c8 00 00 58 00 00      00:03:33.500  NOP [Abort queued commands]
  00 00 00 00 00 00 00 00      00:03:33.500  NOP [Abort queued commands]
  00 00 ef 00 00 45 00 00      00:03:33.500  NOP [Abort queued commands]
  00 00 00 00 00 00 00 00      00:03:33.500  NOP [Abort queued commands]
  00 00 c8 00 00 58 00 00      00:03:33.500  NOP [Abort queued commands]

Error 10 occurred at disk power-on lifetime: 472 hours (19 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 58 8b 3d 07 e0  Error: 

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 c8 00 00 58 00 00      00:03:31.400  NOP [Abort queued commands]
  00 00 ec 00 00 00 00 00      00:03:31.400  NOP [Abort queued commands]
  00 00 00 00 00 00 00 00      00:03:31.400  NOP [Abort queued commands]
  00 00 ec 00 00 00 00 00      00:03:31.400  NOP [Abort queued commands]
  00 00 00 00 00 00 00 00      00:03:31.400  NOP [Abort queued commands]

Error 9 occurred at disk power-on lifetime: 472 hours (19 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 58 8b 3d 07 e0  Error: 

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 c8 00 00 58 00 00      00:03:29.350  NOP [Abort queued commands]
  00 00 00 00 00 00 00 00      00:03:29.350  NOP [Abort queued commands]
  00 00 ef 00 00 45 00 00      00:03:29.350  NOP [Abort queued commands]
  00 00 00 00 00 00 00 00      00:03:29.350  NOP [Abort queued commands]
  00 00 c8 00 00 58 00 00      00:03:29.350  NOP [Abort queued commands]

Error 8 occurred at disk power-on lifetime: 472 hours (19 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 58 8b 3d 07 e0  Error: 

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 c8 00 00 58 00 00      00:03:27.150  NOP [Abort queued commands]
  00 00 00 00 00 00 00 00      00:03:27.150  NOP [Abort queued commands]
  00 00 ef 00 00 45 00 00      00:03:27.150  NOP [Abort queued commands]
  00 00 00 00 00 00 00 00      00:03:27.150  NOP [Abort queued commands]
  00 00 c8 00 00 58 00 00      00:03:27.150  NOP [Abort queued commands]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%       460         -
# 2  Extended offline    Completed without error       00%       452         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Re: Problem with ata layer in 2.6.24

[Daniel Barkalow]

On Mon, 28 Jan 2008, Gene Heskett wrote:

> I believe at this point, its moot.  I captured quite a few instances of that 
> error message while rebooting the last time, all of which occurred long 
> before I logged in and did a startx (I boot to runlevel 3 here), so the 
> kernel was NOT tainted at that point.  That dmesg has been posted and some 
> questions asked.
> 
> As this has gone on for a while, it seems to me that with 14,800 google hits 
> on this problem, Linus should call a halt until this is found and fixed.  But 
> I'm not Linus.  I'm also locking up for 30 at a time, & probably ready for 
> reboot #7 today.

Can you switch back to old IDE to get your work done (and to make sure 
it's not a hardware issue that's developed recently)? I believe libata is 
just a whole lot pickier about behavior than the IDE subsystem was, so 
it's more likely to complain about stuff, both for good reasons and when 
it shouldn't, and there are a slew of potential "we have to accept that 
old PATA hardware does this" bugs that all have the same symptom of "we go 
into error handling when nothing is actually wrong", hence the vast 
quantity of hits. I think it's not exactly that it's a common problem as 
that it's a lot of problems that aren't very distinguishable.

	-Daniel
*This .sig left intentionally blank*

Re: Problem with ata layer in 2.6.24

[Richard Heck]

Daniel Barkalow wrote:
> Can you switch back to old IDE to get your work done (and to make sure 
> it's not a hardware issue that's developed recently)? 
I think it'd be really, REALLY helpful to a lot of people if you, or 
someone, could explain in moderate detail how this might be done. I 
tried doing it myself, but I'm not sufficiently expert at configuring 
kernels that I was ever able to figure out how to do it.

Obviously, the short version is: switch back to Fedora 6. But this kind 
of problem with libata---and yes, you're almost surely right that it's 
not one problem but lots---is sufficiently widespread that a Mini HOWTO, 
say, would be really welcome and, I'm guessing, widely used.

Richard

Re: Problem with ata layer in 2.6.24

[Andrey Borzenkov]

Richard Heck wrote:

> Daniel Barkalow wrote:
>> Can you switch back to old IDE to get your work done (and to make sure
>> it's not a hardware issue that's developed recently)?
> I think it'd be really, REALLY helpful to a lot of people if you, or
> someone, could explain in moderate detail how this might be done. I
> tried doing it myself, but I'm not sufficiently expert at configuring
> kernels that I was ever able to figure out how to do it.
> 

well, here on Mandriva I

1) compile both IDE and libata as modules
2) create initrd that contains either IDE or libata modules
3) use labels for file system mounts, swaps and resume device.


Now 1) should be pretty straightforward (I could send you config if you
like, it is stripped down to bare minimum on my system, you will have to
check drivers for your hardware). 2 and 3 are obviously distribution
dependent. I can explain how to do it on Mandriva that ATM has near to
perfect support for addressing devices via label/UUID; also ide/scsi/ata
switch is trivial using Mandriva mkinitrd. 

-andrey

> Obviously, the short version is: switch back to Fedora 6. But this kind
> of problem with libata---and yes, you're almost surely right that it's
> not one problem but lots---is sufficiently widespread that a Mini HOWTO,
> say, would be really welcome and, I'm guessing, widely used.
> 
> Richard
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Andrey Borzenkov wrote:
>Richard Heck wrote:
>> Daniel Barkalow wrote:
>>> Can you switch back to old IDE to get your work done (and to make sure
>>> it's not a hardware issue that's developed recently)?
>>
>> I think it'd be really, REALLY helpful to a lot of people if you, or
>> someone, could explain in moderate detail how this might be done. I
>> tried doing it myself, but I'm not sufficiently expert at configuring
>> kernels that I was ever able to figure out how to do it.
>
>well, here on Mandriva I
>
>1) compile both IDE and libata as modules
>2) create initrd that contains either IDE or libata modules
>3) use labels for file system mounts, swaps and resume device.
>
>
>Now 1) should be pretty straightforward (I could send you config if you
>like, it is stripped down to bare minimum on my system, you will have to
>check drivers for your hardware). 2 and 3 are obviously distribution
>dependent. I can explain how to do it on Mandriva that ATM has near to
>perfect support for addressing devices via label/UUID; also ide/scsi/ata
>switch is trivial using Mandriva mkinitrd.
>
>-andrey
>
>> Obviously, the short version is: switch back to Fedora 6. But this kind
>> of problem with libata---and yes, you're almost surely right that it's
>> not one problem but lots---is sufficiently widespread that a Mini HOWTO,
>> say, would be really welcome and, I'm guessing, widely used.
>>
>> Richard

I already build as modules, and it would be relatively easy to make 2 boot 
stanza's that used the different initrd's if there were examples that could 
be used as 'excludes' when building the initrd's.  Is such a creature 
breedable?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
It's no wonder they call it WinNT; WNT = VMS++;

   -- Chris Abbey
%   
Peace, Love and Compile the kernel...

   -- Justin L. Herreman

Re: Problem with ata layer in 2.6.24

[Andrey Borzenkov]

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

On Monday 28 January 2008, Gene Heskett wrote:
> On Monday 28 January 2008, Andrey Borzenkov wrote:
> >Richard Heck wrote:
> >> Daniel Barkalow wrote:
> >>> Can you switch back to old IDE to get your work done (and to make sure
> >>> it's not a hardware issue that's developed recently)?
> >>
> >> I think it'd be really, REALLY helpful to a lot of people if you, or
> >> someone, could explain in moderate detail how this might be done. I
> >> tried doing it myself, but I'm not sufficiently expert at configuring
> >> kernels that I was ever able to figure out how to do it.
> >
> >well, here on Mandriva I
> >
> >1) compile both IDE and libata as modules
> >2) create initrd that contains either IDE or libata modules
> >3) use labels for file system mounts, swaps and resume device.
> >
> >
> >Now 1) should be pretty straightforward (I could send you config if you
> >like, it is stripped down to bare minimum on my system, you will have to
> >check drivers for your hardware). 2 and 3 are obviously distribution
> >dependent. I can explain how to do it on Mandriva that ATM has near to
> >perfect support for addressing devices via label/UUID; also ide/scsi/ata
> >switch is trivial using Mandriva mkinitrd.
> >
> 
> I already build as modules, and it would be relatively easy to make 2 boot 
> stanza's that used the different initrd's if there were examples that could 
> be used as 'excludes' when building the initrd's.  Is such a creature 
> breedable?
> 

I am not sure I understand a question (it is not my native language) but here I 
simply do

mkinitrd --omit-ide-modules --preload pata_ali --preload sd_mod ...

or

mkinitrd --omit-scsi-modules --preload alim15x3 --preload ide-disk ...

If you ask how --omit part is implemented I happily send you mkinitrd script.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Andrey Borzenkov wrote:
>On Monday 28 January 2008, Gene Heskett wrote:
>> On Monday 28 January 2008, Andrey Borzenkov wrote:
>> >Richard Heck wrote:
>> >> Daniel Barkalow wrote:
>> >>> Can you switch back to old IDE to get your work done (and to make sure
>> >>> it's not a hardware issue that's developed recently)?
>> >>
>> >> I think it'd be really, REALLY helpful to a lot of people if you, or
>> >> someone, could explain in moderate detail how this might be done. I
>> >> tried doing it myself, but I'm not sufficiently expert at configuring
>> >> kernels that I was ever able to figure out how to do it.
>> >
>> >well, here on Mandriva I
>> >
>> >1) compile both IDE and libata as modules
>> >2) create initrd that contains either IDE or libata modules
>> >3) use labels for file system mounts, swaps and resume device.
>> >
>> >
>> >Now 1) should be pretty straightforward (I could send you config if you
>> >like, it is stripped down to bare minimum on my system, you will have to
>> >check drivers for your hardware). 2 and 3 are obviously distribution
>> >dependent. I can explain how to do it on Mandriva that ATM has near to
>> >perfect support for addressing devices via label/UUID; also ide/scsi/ata
>> >switch is trivial using Mandriva mkinitrd.
>>
>> I already build as modules, and it would be relatively easy to make 2 boot
>> stanza's that used the different initrd's if there were examples that
>> could be used as 'excludes' when building the initrd's.  Is such a
>> creature breedable?
>
>I am not sure I understand a question (it is not my native language) but
> here I simply do
>
>mkinitrd --omit-ide-modules --preload pata_ali --preload sd_mod ...
>
>or
>
>mkinitrd --omit-scsi-modules --preload alim15x3 --preload ide-disk ...
>
This looks doable, thanks.  I was trying to be cute above when I'm rather 
frustrated by all this.  I might have to fiddle a bit but I got the idea.

OTOH, I and about 15,000 others according to google, would be everlastingly 
gratefull if it was just fixed. :)

Thanks

>If you ask how --omit part is implemented I happily send you mkinitrd
> script.



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If everybody minded their own business, the world would go around a deal 
faster.
		-- The Duchess, "Through the Looking Glass"

Re: Problem with ata layer in 2.6.24

[Richard Heck]

Andrey Borzenkov wrote:
> Richard Heck wrote:
>
>   
>> Daniel Barkalow wrote:
>>     
>>> Can you switch back to old IDE to get your work done (and to make sure
>>> it's not a hardware issue that's developed recently)?
>>>       
>> I think it'd be really, REALLY helpful to a lot of people if you, or
>> someone, could explain in moderate detail how this might be done. I
>> tried doing it myself, but I'm not sufficiently expert at configuring
>> kernels that I was ever able to figure out how to do it.
>>
>>     
>
> well, here on Mandriva I
>
> 1) compile both IDE and libata as modules
> 2) create initrd that contains either IDE or libata modules
> 3) use labels for file system mounts, swaps and resume device.
>
>
> Now 1) should be pretty straightforward (I could send you config if you
> like, it is stripped down to bare minimum on my system, you will have to
> check drivers for your hardware). 2 and 3 are obviously distribution
> dependent. I can explain how to do it on Mandriva that ATM has near to
> perfect support for addressing devices via label/UUID; also ide/scsi/ata
> switch is trivial using Mandriva mkinitrd. 
>
>   
Thanks for this. Compiling the IDE stuff as a module is indeed the easy 
part, though I suppose I need to make sure I get the right drivers for 
my chipset, too. Loading e.g. the Fedora 6 LiveCD and then lsmod'ing 
should do it, though. Labels are used by default in Fedora now, so 
that's fine, too. Getting mkinitrd to work right shouldn't be too bad, 
either. So I'll have a go at this when I get some time and report on it. 
What might be REALLY helpful to people would be if we Fedora types could 
produce a modified kernel rpm that would handle this....though, I should 
say, I've also seen a lot of complaints along these same lines on Ubuntu.

Richard

Re: Problem with ata layer in 2.6.24

[Daniel Barkalow]

On Mon, 28 Jan 2008, Richard Heck wrote:

> Daniel Barkalow wrote:
> > Can you switch back to old IDE to get your work done (and to make sure it's
> > not a hardware issue that's developed recently)? 
> I think it'd be really, REALLY helpful to a lot of people if you, or someone,
> could explain in moderate detail how this might be done. I tried doing it
> myself, but I'm not sufficiently expert at configuring kernels that I was ever
> able to figure out how to do it.

As far as configuring the kernel, I can help:

Go to Device Drivers, ATA/ATAPI/MFM/RLL support, and turn on anything that 
looks relevant; go to Device Drivers, Serial ATA and Parallel ATA drivers, 
and turn off anything that's PATA and looks relevant.

(Whether a device uses IDE or PATA depends on which driver that supports 
the device is present and find it first, not on any sort of global 
configuration, which is probably what tripped you up)

Building this and installing it along with the appropriate initrd (which 
might be handled by Fedora's install scripts) will either get you back to 
old IDE or will make your kernel panic on boot, depending on whether you 
got it right (so make sure you can still boot the kernel you're sure of or 
something from a boot disk). This will also cause your hard drives to show 
up as different device nodes, so if your boot process doesn't mount by 
disk uuid but by some other feature (and I don't know what Fedora does), 
you'll also need to change it to something either stable across access 
methods or which works for the one you're now using.

> Obviously, the short version is: switch back to Fedora 6. But this kind of
> problem with libata---and yes, you're almost surely right that it's not one
> problem but lots---is sufficiently widespread that a Mini HOWTO, say, would be
> really welcome and, I'm guessing, widely used.

Fedora really ought to provide documentation, because there's some 
distro-specific stuff (like how you deal with the kernel's device node for 
the root partition changing), and they're using code by default that's at 
least somewhat documented as experimental (although it doesn't seem to be 
actually marked as experimental in all cases).

	-Daniel
*This .sig left intentionally blank*

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Daniel Barkalow wrote:
>On Mon, 28 Jan 2008, Richard Heck wrote:
>> Daniel Barkalow wrote:
>> > Can you switch back to old IDE to get your work done (and to make sure
>> > it's not a hardware issue that's developed recently)?
>>
>> I think it'd be really, REALLY helpful to a lot of people if you, or
>> someone, could explain in moderate detail how this might be done. I tried
>> doing it myself, but I'm not sufficiently expert at configuring kernels
>> that I was ever able to figure out how to do it.
>
>As far as configuring the kernel, I can help:
>
>Go to Device Drivers, ATA/ATAPI/MFM/RLL support, and turn on anything that
>looks relevant; go to Device Drivers, Serial ATA and Parallel ATA drivers,
>and turn off anything that's PATA and looks relevant.
>
Done.

>(Whether a device uses IDE or PATA depends on which driver that supports
>the device is present and find it first, not on any sort of global
>configuration, which is probably what tripped you up)
>
>Building this and installing it along with the appropriate initrd (which
>might be handled by Fedora's install scripts)

Or mine, which I've been using for years.

>will either get you back to 
>old IDE or will make your kernel panic on boot, depending on whether you
>got it right (so make sure you can still boot the kernel you're sure of or
>something from a boot disk). This will also cause your hard drives to show
>up as different device nodes, so if your boot process doesn't mount by
>disk uuid but by some other feature (and I don't know what Fedora does),
>you'll also need to change it to something either stable across access
>methods or which works for the one you're now using.

It mounts by LABEL=.  All of it.

>> Obviously, the short version is: switch back to Fedora 6. But this kind of
>> problem with libata---and yes, you're almost surely right that it's not
>> one problem but lots---is sufficiently widespread that a Mini HOWTO, say,
>> would be really welcome and, I'm guessing, widely used.
>
>Fedora really ought to provide documentation, because there's some
>distro-specific stuff (like how you deal with the kernel's device node for
>the root partition changing), and they're using code by default that's at
>least somewhat documented as experimental (although it doesn't seem to be
>actually marked as experimental in all cases).

Fedora is not the only people having trouble,  name a distro, its probably 
someplace in that 14,800 hit google returns.

>	-Daniel
>*This .sig left intentionally blank*

Thanks Daniel, try #1 is building now.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Those who do not understand Unix are condemned to reinvent it, poorly.
		-- Henry Spencer

Re: Problem with ata layer in 2.6.24

[Daniel Barkalow]

On Mon, 28 Jan 2008, Gene Heskett wrote:

> On Monday 28 January 2008, Daniel Barkalow wrote:
> >Building this and installing it along with the appropriate initrd (which
> >might be handled by Fedora's install scripts)
> 
> Or mine, which I've been using for years.

You're ahead of a surprising number of people, including me, if you 
understand making initrds.

> >will either get you back to 
> >old IDE or will make your kernel panic on boot, depending on whether you
> >got it right (so make sure you can still boot the kernel you're sure of or
> >something from a boot disk). This will also cause your hard drives to show
> >up as different device nodes, so if your boot process doesn't mount by
> >disk uuid but by some other feature (and I don't know what Fedora does),
> >you'll also need to change it to something either stable across access
> >methods or which works for the one you're now using.
> 
> It mounts by LABEL=.  All of it.

That'll save a huge amount of hassle. So long as you manage to get the 
right drivers included and the wrong drivers not included, you should be 
pretty much set.

> Fedora is not the only people having trouble,  name a distro, its probably 
> someplace in that 14,800 hit google returns.

Yeah, but they each may need different instructions, particularly if 
they're not mounting by label in general, or not mounting the root 
partition by label. That was the big hassle going the opposite direction. 
And the procedure is 4 lines to describe to somebody who knows how to 
build and install a new kernel for the distro, which is much shorter than 
the explanation of how you generally build and install a kernel. A real 
howto would have to explain where to get the distro's kernel sources and 
default configuration, for example.

	-Daniel
*This .sig left intentionally blank*

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Daniel Barkalow wrote:
>On Mon, 28 Jan 2008, Gene Heskett wrote:
>> On Monday 28 January 2008, Daniel Barkalow wrote:
>> >Building this and installing it along with the appropriate initrd (which
>> >might be handled by Fedora's install scripts)
>>
>> Or mine, which I've been using for years.
>
>You're ahead of a surprising number of people, including me, if you
>understand making initrds.

In my script, its one line:
mkinitrd -f initrd-$VER.img $VER && \

where $VER is the shell variable I edit to = the version number, located at 
the top of the script.

Unforch, its failing:
No module pata_amd found for kernel 2.6.24, aborting.

This is with pata_amd turned off and its counterpart under ATA/RLL/etc turned 
on.  So something is still dependent on it.  I do have one sata drive, on an 
accessory card in the box, so I need the rest of the sata_sil and friends 
stuff.  Its my virtual tapes for amanda.  Also home built, the amanda 
security model cannot be successfully bent into the shape of an rpm.  They 
BTW are #2 on coverity's list of most secure software.

So I've rebuilt 2.6.24 as it originally was, and added the acpi timer line to 
the 2.6.24-rc8 stanza's kernel argument list.  It will boot one or the other 
when I next reboot.  Its been about 8 hours since the last error was logged, 
which is totally weirdsville to this old fart.  Phase of the moon maybe?  The 
visit to the sawbones to see about my heart?  They are going to fit me with a 
30 day recorder tomorrow, my skip a beat problem is getting worse.  The sort 
of stuff that goes with the 7nth decade I guess.  Officially, I'm wearing out 
me, too much sugar, too many times nearly electrocuted=shingles yadda 
yadda. :-)  Oh, and don't forget Arther, he moved in uninvited about 25 years 
ago too.  Those people that talk about the golden years?  They're full of 
excrement...

>> >will either get you back to
>> >old IDE or will make your kernel panic on boot, depending on whether you
>> >got it right (so make sure you can still boot the kernel you're sure of
>> > or something from a boot disk). This will also cause your hard drives to
>> > show up as different device nodes, so if your boot process doesn't mount
>> > by disk uuid but by some other feature (and I don't know what Fedora
>> > does), you'll also need to change it to something either stable across
>> > access methods or which works for the one you're now using.
>>
>> It mounts by LABEL=.  All of it.
>
>That'll save a huge amount of hassle. So long as you manage to get the
>right drivers included and the wrong drivers not included, you should be
>pretty much set.
>
>> Fedora is not the only people having trouble,  name a distro, its probably
>> someplace in that 14,800 hit google returns.
>
>Yeah, but they each may need different instructions, particularly if
>they're not mounting by label in general, or not mounting the root
>partition by label. That was the big hassle going the opposite direction.
>And the procedure is 4 lines to describe to somebody who knows how to
>build and install a new kernel for the distro, which is much shorter than
>the explanation of how you generally build and install a kernel. A real
>howto would have to explain where to get the distro's kernel sources and
>default configuration, for example.
>
>	-Daniel
>*This .sig left intentionally blank*



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Never drink from your finger bowl -- it contains only water.

Re: Problem with ata layer in 2.6.24

[Daniel Barkalow]

On Mon, 28 Jan 2008, Gene Heskett wrote:

> On Monday 28 January 2008, Daniel Barkalow wrote:
> >On Mon, 28 Jan 2008, Gene Heskett wrote:
> >> On Monday 28 January 2008, Daniel Barkalow wrote:
> >> >Building this and installing it along with the appropriate initrd (which
> >> >might be handled by Fedora's install scripts)
> >>
> >> Or mine, which I've been using for years.
> >
> >You're ahead of a surprising number of people, including me, if you
> >understand making initrds.
> 
> In my script, its one line:
> mkinitrd -f initrd-$VER.img $VER && \
> 
> where $VER is the shell variable I edit to = the version number, located at 
> the top of the script.
> 
> Unforch, its failing:
> No module pata_amd found for kernel 2.6.24, aborting.
> 
> This is with pata_amd turned off and its counterpart under ATA/RLL/etc turned 
> on.  So something is still dependent on it. 

That looks like something in the guts of the initrd; it probably thinks 
you need pata_amd and it's unhappy that you don't have it.

Actually, another thing to try is making the ATA/etc one be "y" and 
pata_amd be "m". Most likely, this should lead to the ATA one claiming the 
drive before the module is loaded (but the module would be loaded later, 
to avoid upsetting the initrd); you should be able to tell from dmesg (or 
/dev, for that matter) which one got it, and I think built-in drivers will 
claim everything they can before an initrd gets loaded.

> I do have one sata drive, on an accessory card in the box, so I need the 
> rest of the sata_sil and friends stuff. 

Assuming it isn't picking up your hard drive, which it isn't, that 
shouldn't matter.

	-Daniel
*This .sig left intentionally blank*

Re: Problem with ata layer in 2.6.24

[Michal Jaegermann]

On Mon, Jan 28, 2008 at 08:31:57PM -0500, Gene Heskett wrote:
> 
> In my script, its one line:
> mkinitrd -f initrd-$VER.img $VER && \
> 
> where $VER is the shell variable I edit to = the version number, located at 
> the top of the script.
> 
> Unforch, its failing:
> No module pata_amd found for kernel 2.6.24, aborting.

mkinitrd is just a shell script.  Even if its options, and there is
a quite a number of these, do not allow to influence a choice of
modules in a desired manner, it is pretty trivial to make yourself a
custom version of it and just hardwire there a fixed list of modules
to use instead of relying on general mechanisms which are trying
hard to guess what you may need.

That way your regular 'mkinitrd' will build something to boot with
libata and 'mkinird.ide' will use IDE modules for that purpose using
the same "core" kernel.

If you are using distribution kernels, as opposed to your own
configuration, it is quite likely that you will need to install
'kernel-devel' package and recompile and add required IDE modules
yourself as those may be not provided.  This is done the same way
like for any other "external" module.

   Michal

Re: Problem with ata layer in 2.6.24

[Alan Cox]

> not one problem but lots---is sufficiently widespread that a Mini HOWTO, 
> say, would be really welcome and, I'm guessing, widely used.

We don't see very many libata problems at the distro level and they for
the most part boil down to

- error messages looking different - Most bugs I get are things like
media errors (timeout looks different, UNC report looks different)

- broken hardware - I've closed a whole raft of bugs that turn out to be
new PC systems where even the BIOS doesn't see the drives

- faulty hardware being picked up because we actually do real error
checking now. We now check for and give some devices more slack while
still doing error checking. Both IDE layers also added blacklists for
stuff like the TSScorp DVD drives. Qemu has now had its bugs patched.

- sata_nv with >4GB of RAM, knowing being worked on, no old IDE driver
anyway
 
- pata_ali MWDMA with ATAPI, PIO works fine, all a bit of a mystery and
as it affects only a few chip variants hard to figure out. Workaround
libata.dma=1

- CS handling. On a few boxes using cable select (particularly on one
drive and not the other) shows up a problem, normally a failed SRST.
That's still under investigation.

- Promise timeouts. The old IDE times out then polls the device and finds
the IRQ was never sent and then recovers so the user sees a short stall
but no errors. The new libata doesn't do this and pdc202xx_old thus
produces some error messages on some boxes. Backup polling is on my todo
list.

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Tuesday 29 January 2008, Alan Cox wrote:
>> not one problem but lots---is sufficiently widespread that a Mini HOWTO,
>> say, would be really welcome and, I'm guessing, widely used.
>
>We don't see very many libata problems at the distro level and they for
>the most part boil down to
>
>- error messages looking different - Most bugs I get are things like
>media errors (timeout looks different, UNC report looks different)
>
>- broken hardware - I've closed a whole raft of bugs that turn out to be
>new PC systems where even the BIOS doesn't see the drives
>
>- faulty hardware being picked up because we actually do real error
>checking now. We now check for and give some devices more slack while
>still doing error checking. Both IDE layers also added blacklists for
>stuff like the TSScorp DVD drives. Qemu has now had its bugs patched.
>
>- sata_nv with >4GB of RAM, knowing being worked on, no old IDE driver
>anyway
>
>- pata_ali MWDMA with ATAPI, PIO works fine, all a bit of a mystery and
>as it affects only a few chip variants hard to figure out. Workaround
>libata.dma=1
>
>- CS handling. On a few boxes using cable select (particularly on one
>drive and not the other) shows up a problem, normally a failed SRST.
>That's still under investigation.
>
>- Promise timeouts. The old IDE times out then polls the device and finds
>the IRQ was never sent and then recovers so the user sees a short stall
>but no errors. The new libata doesn't do this and pdc202xx_old thus
>produces some error messages on some boxes. Backup polling is on my todo
>list.

I have not had a problem, no errors at all, since I rebooted to 
2.6.24-rc8 with the added argument in the kernel line in grub 
(from dmesg):
[    0.000000] Kernel command line: ro root=/dev/VolGroup00/LogVol00 acpi_use_timer_override rhgb quiet

which causes dmesg to log, some time later:

[   27.581823] ENABLING IO-APIC IRQs
[   27.582014] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[   27.592017] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[   27.592068] ...trying to set up timer (IRQ0) through the 8259A ...  failed.
[   27.592071] ...trying to set up timer as Virtual Wire IRQ... works.
[   27.703623] Brought up 1 CPUs

This was about noonish yesterday, and the logs have been silent 
regarding this 'exception Emask' error since then.  The drive itself
has also passed a smartctl -t long test with no errors since then.

Now, the last boot that had the problem was to 2.6.24, which did 
NOT have that 'acpi_use_timer_override' argument, and its dmesg logged:

[   24.934176] ENABLING IO-APIC IRQs
[   24.934367] ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1
[   25.045973] Brought up 1 CPUs

Now, my question is, did the use of that argument, while it looked
like it failed, cause the setup code to do something correct that
the default path didn't do?  Is this the clue we're all looking for?

Since libata is apparently the path taken by TPTB, I'm going to build
and boot to a 2.6.24 using libata, but add that argument to grubs kernel
line in only one of 2 copies of that stanza.

Wish me luck.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The intelligence of any discussion diminishes with the square of the
number of participants.
		-- Adam Walinsky

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Tuesday 29 January 2008, Alan Cox wrote:
>> not one problem but lots---is sufficiently widespread that a Mini HOWTO,
>> say, would be really welcome and, I'm guessing, widely used.
>
>We don't see very many libata problems at the distro level and they for
>the most part boil down to
>
>- error messages looking different - Most bugs I get are things like
>media errors (timeout looks different, UNC report looks different)
>
>- broken hardware - I've closed a whole raft of bugs that turn out to be
>new PC systems where even the BIOS doesn't see the drives
>
>- faulty hardware being picked up because we actually do real error
>checking now. We now check for and give some devices more slack while
>still doing error checking. Both IDE layers also added blacklists for
>stuff like the TSScorp DVD drives. Qemu has now had its bugs patched.
>
>- sata_nv with >4GB of RAM, knowing being worked on, no old IDE driver
>anyway
>
>- pata_ali MWDMA with ATAPI, PIO works fine, all a bit of a mystery and
>as it affects only a few chip variants hard to figure out. Workaround
>libata.dma=1
>
>- CS handling. On a few boxes using cable select (particularly on one
>drive and not the other) shows up a problem, normally a failed SRST.
>That's still under investigation.
>
>- Promise timeouts. The old IDE times out then polls the device and finds
>the IRQ was never sent and then recovers so the user sees a short stall
>but no errors. The new libata doesn't do this and pdc202xx_old thus
>produces some error messages on some boxes. Backup polling is on my todo
>list.

As slight change here, I was going to use the same .config as 2.6.24-rc8, but 
just discovered that neither rc8 nor final is finding the drivers for my
dvd writer while using libata, so its not useable.  So I've enable a couple of 
things in the 2.6.24 build that aren't in the 2.6.24-rc8.  When I find the 
magic twanger, I'll rebuild -rc8 with it too.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
River: "He didn't lie down.  They never lie down."
				--"Serenity"

Re: Problem with ata layer in 2.6.24

[Alan Cox]

> As slight change here, I was going to use the same .config as 2.6.24-rc8, but 
> just discovered that neither rc8 nor final is finding the drivers for my

If it is not finding a driver that is nothing to do with libata. It means
it's not being loaded by the distribution, or the distribution kernel is
too old (2.6.22) for the hardware - in which case see the Fedora respins
which are on 2.6.23.something right now.

Alan

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

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

On Tuesday 29 January 2008, Alan Cox wrote:
>> As slight change here, I was going to use the same .config as 2.6.24-rc8,
>> but just discovered that neither rc8 nor final is finding the drivers for
>> my
>
>If it is not finding a driver that is nothing to do with libata. It means
>it's not being loaded by the distribution, or the distribution kernel is
>too old (2.6.22) for the hardware - in which case see the Fedora respins
>which are on 2.6.23.something right now.
>
>Alan

Home built kernel Alan.  But you are as good as anyone to tell me what I 
need to turn on in order for this dvdwriter to be enabled:
[   28.862478] ata2.00: ATAPI: LITE-ON DVDRW SHM-165H6S, HS06, max UDMA/66
....
[   28.908647] ata2.00: limited to UDMA/33 due to 40-wire cable
[   29.081253] ata2.00: configured for UDMA/33
....
it has had several 80 wire cables tried, hasn't fixed this, and does not
seem to effect its operation when it does work.
....
[   29.132405] scsi 1:0:0:0: CD-ROM            LITE-ON  DVDRW SHM-165H6S HS06 PQ: 0 ANSI: 5
....
[   43.450795] scsi 1:0:0:0: Attached scsi generic sg1 type 5
-------
No further mention of it in dmesg, and k3b cannot find the drive at any 
/dev/sgX address.

.config attached, what else do I need to turn on?

There is also this in the log since I logged in and startx'd:

Jan 29 11:21:26 coyote automount[1923]: create_udp_client:101: hostname lookup failed: Operation not permitted
Jan 29 11:21:26 coyote automount[1923]: create_tcp_client:321: hostname lookup failed: Operation not permitted
Jan 29 11:21:26 coyote automount[1923]: lookup_mount: exports lookup failed for .directory
Jan 29 11:21:26 coyote automount[1923]: lookup_mount: lookup(file): key ".directory" not found in map

however a stop and restart of k3b does not regenerate another set of those.
So I have NDI what actually generated those.

I also discovered that my build nvidia script needs at least one run of
the complete .run version to get all the right versions of the GL stuffs
installed.  That isn't related though, just a passing comment.

FWIW, this is a 2.6.24 kernel ATM, without that kernel argument acpi_use_timer_override.
If my theory is right, I should see some of those errors now.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
You can move the world with an idea, but you have to think of it first.

[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 62140 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.24
# Tue Jan 29 10:15:10 2008
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set
CONFIG_ARCH_SUPPORTS_OPROFILE=y
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_USER_NS=y
# CONFIG_PID_NS is not set
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_TREE=y
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=17
# CONFIG_CGROUPS is not set
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_FAIR_USER_SCHED=y
# CONFIG_FAIR_CGROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_LBD=y
CONFIG_BLK_DEV_IO_TRACE=y
CONFIG_LSF=y
CONFIG_BLK_DEV_BSG=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_X86_VSMP is not set
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
# CONFIG_PARAVIRT_GUEST is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_TSC=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=4
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_NR_CPUS=32
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
CONFIG_X86_MCE_P4THERMAL=y
CONFIG_VM86=y
CONFIG_TOSHIBA=m
CONFIG_I8K=m
# CONFIG_X86_REBOOTFIXUPS is not set
CONFIG_MICROCODE=m
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_SPARSEMEM_STATIC=y
# CONFIG_SPARSEMEM_VMEMMAP_ENABLE is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_NR_QUICK=1
CONFIG_VIRT_TO_BUS=y
CONFIG_HIGHPTE=y
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_EFI=y
# CONFIG_IRQBALANCE is not set
CONFIG_BOOT_IOREMAP=y
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
CONFIG_PHYSICAL_START=0x1000000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x400000
CONFIG_HOTPLUG_CPU=y
# CONFIG_COMPAT_VDSO is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management options
#
CONFIG_PM=y
CONFIG_PM_LEGACY=y
CONFIG_PM_DEBUG=y
# CONFIG_PM_VERBOSE is not set
CONFIG_PM_TRACE=y
CONFIG_PM_SLEEP_SMP=y
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND_SMP_POSSIBLE=y
CONFIG_SUSPEND=y
CONFIG_HIBERNATION_SMP_POSSIBLE=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_PROCFS=y
CONFIG_ACPI_PROCFS_POWER=y
CONFIG_ACPI_SYSFS_POWER=y
CONFIG_ACPI_PROC_EVENT=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=m
# CONFIG_ACPI_VIDEO is not set
# CONFIG_ACPI_FAN is not set
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=1999
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
# CONFIG_ACPI_SBS is not set
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
CONFIG_APM_CPU_IDLE=y
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
# CONFIG_PCIEPORTBUS is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY=y
# CONFIG_PCI_DEBUG is not set
CONFIG_HT_IRQ=y
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
CONFIG_XFRM_SUB_POLICY=y
CONFIG_XFRM_MIGRATE=y
CONFIG_NET_KEY=m
CONFIG_NET_KEY_MIGRATE=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_ASK_IP_FIB_HASH=y
# CONFIG_IP_FIB_TRIE is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_LRO=m
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=m
CONFIG_TCP_CONG_CUBIC=y
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
CONFIG_TCP_CONG_SCALABLE=m
CONFIG_TCP_CONG_LP=m
CONFIG_TCP_CONG_VENO=m
CONFIG_TCP_CONG_YEAH=m
CONFIG_TCP_CONG_ILLINOIS=m
# CONFIG_DEFAULT_BIC is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IP_VS=m
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12

#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y

#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m

#
# IPVS application helper
#
CONFIG_IP_VS_FTP=m
CONFIG_IPV6=m
CONFIG_IPV6_PRIVACY=y
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_IPV6_OPTIMISTIC_DAD=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_IPV6_MIP6=m
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
CONFIG_IPV6_SIT=m
CONFIG_IPV6_TUNNEL=m
CONFIG_IPV6_MULTIPLE_TABLES=y
CONFIG_IPV6_SUBTREES=y
CONFIG_NETLABEL=y
CONFIG_NETWORK_SECMARK=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_BRIDGE_NETFILTER=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK_ENABLED=m
CONFIG_NF_CONNTRACK=m
CONFIG_NF_CT_ACCT=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CT_PROTO_GRE=m
CONFIG_NF_CT_PROTO_SCTP=m
CONFIG_NF_CT_PROTO_UDPLITE=m
CONFIG_NF_CONNTRACK_AMANDA=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_PPTP=m
CONFIG_NF_CONNTRACK_SANE=m
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NETFILTER_XTABLES=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
# CONFIG_NETFILTER_XT_MATCH_TIME is not set
CONFIG_NETFILTER_XT_MATCH_U32=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m

#
# IP: Netfilter Configuration
#
CONFIG_NF_CONNTRACK_IPV4=m
# CONFIG_NF_CONNTRACK_PROC_COMPAT is not set
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_NF_NAT=m
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
CONFIG_NF_NAT_SNMP_BASIC=m
CONFIG_NF_NAT_PROTO_GRE=m
CONFIG_NF_NAT_FTP=m
CONFIG_NF_NAT_IRC=m
CONFIG_NF_NAT_TFTP=m
CONFIG_NF_NAT_AMANDA=m
CONFIG_NF_NAT_PPTP=m
CONFIG_NF_NAT_H323=m
CONFIG_NF_NAT_SIP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_RAW=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m

#
# IPv6: Netfilter Configuration (EXPERIMENTAL)
#
CONFIG_NF_CONNTRACK_IPV6=m
CONFIG_IP6_NF_QUEUE=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_RT=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_OWNER=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_LOG=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_RAW=m

#
# DECnet: Netfilter Configuration
#
# CONFIG_DECNET_NF_GRABULATOR is not set

#
# Bridge: Netfilter Configuration
#
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_ULOG=m
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
CONFIG_IP_DCCP_ACKVEC=y

#
# DCCP CCIDs Configuration (EXPERIMENTAL)
#
CONFIG_IP_DCCP_CCID2=m
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=m
CONFIG_IP_DCCP_TFRC_LIB=m
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_CCID3_RTO=100

#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
CONFIG_TIPC=m
# CONFIG_TIPC_ADVANCED is not set
# CONFIG_TIPC_DEBUG is not set
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set
CONFIG_ATM_LANE=m
# CONFIG_ATM_MPOA is not set
CONFIG_ATM_BR2684=m
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_BRIDGE=m
CONFIG_VLAN_8021Q=m
CONFIG_DECNET=m
CONFIG_DECNET_ROUTER=y
CONFIG_LLC=m
# CONFIG_LLC2 is not set
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
CONFIG_ATALK=m
CONFIG_DEV_APPLETALK=m
# CONFIG_LTPC is not set
# CONFIG_COPS is not set
CONFIG_IPDDP=m
CONFIG_IPDDP_ENCAP=y
CONFIG_IPDDP_DECAP=y
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
CONFIG_WAN_ROUTER=m
CONFIG_NET_SCHED=y

#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_ATM=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RR=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_INGRESS=m

#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=y
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=m
CONFIG_NET_ACT_IPT=m
# CONFIG_NET_ACT_NAT is not set
CONFIG_NET_ACT_PEDIT=m
CONFIG_NET_ACT_SIMP=m
CONFIG_NET_CLS_POLICE=y
CONFIG_NET_CLS_IND=y
CONFIG_NET_SCH_FIFO=y

#
# Network testing
#
CONFIG_NET_PKTGEN=m
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y

#
# Wireless
#
# CONFIG_CFG80211 is not set
CONFIG_WIRELESS_EXT=y
# CONFIG_MAC80211 is not set
CONFIG_IEEE80211=m
# CONFIG_IEEE80211_DEBUG is not set
CONFIG_IEEE80211_CRYPT_WEP=m
CONFIG_IEEE80211_CRYPT_CCMP=m
CONFIG_IEEE80211_CRYPT_TKIP=m
CONFIG_IEEE80211_SOFTMAC=m
# CONFIG_IEEE80211_SOFTMAC_DEBUG is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_DEBUG_DRIVER is not set
CONFIG_DEBUG_DEVRES=y
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
CONFIG_MTD=m
# CONFIG_MTD_DEBUG is not set
CONFIG_MTD_CONCAT=m
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_REDBOOT_PARTS=m
CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-1
# CONFIG_MTD_REDBOOT_PARTS_UNALLOCATED is not set
# CONFIG_MTD_REDBOOT_PARTS_READONLY is not set

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=m
CONFIG_MTD_BLKDEVS=m
CONFIG_MTD_BLOCK=m
CONFIG_MTD_BLOCK_RO=m
CONFIG_FTL=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y
CONFIG_INFTL=m
CONFIG_RFD_FTL=m
CONFIG_SSFDC=m
# CONFIG_MTD_OOPS is not set

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=m
CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_GEN_PROBE=m
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_CFI_STAA=m
CONFIG_MTD_CFI_UTIL=m
CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=m
CONFIG_MTD_ABSENT=m

#
# Mapping drivers for chip access
#
CONFIG_MTD_COMPLEX_MAPPINGS=y
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_PNC2000 is not set
CONFIG_MTD_SC520CDP=m
CONFIG_MTD_NETSC520=m
CONFIG_MTD_TS5500=m
# CONFIG_MTD_SBC_GXX is not set
# CONFIG_MTD_AMD76XROM is not set
# CONFIG_MTD_ICHXROM is not set
CONFIG_MTD_ESB2ROM=m
CONFIG_MTD_CK804XROM=m
CONFIG_MTD_SCB2_FLASH=m
# CONFIG_MTD_NETtel is not set
# CONFIG_MTD_DILNETPC is not set
# CONFIG_MTD_L440GX is not set
CONFIG_MTD_PCI=m
# CONFIG_MTD_INTEL_VR_NOR is not set
# CONFIG_MTD_PLATRAM is not set

#
# Self-contained MTD device drivers
#
CONFIG_MTD_PMC551=m
# CONFIG_MTD_PMC551_BUGFIX is not set
# CONFIG_MTD_PMC551_DEBUG is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
CONFIG_MTD_BLOCK2MTD=m

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOC2001PLUS is not set
CONFIG_MTD_NAND=m
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
CONFIG_MTD_NAND_ECC_SMC=y
# CONFIG_MTD_NAND_MUSEUM_IDS is not set
CONFIG_MTD_NAND_IDS=m
CONFIG_MTD_NAND_DISKONCHIP=m
# CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
# CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set
CONFIG_MTD_NAND_CAFE=m
CONFIG_MTD_NAND_CS553X=m
CONFIG_MTD_NAND_NANDSIM=m
# CONFIG_MTD_NAND_PLATFORM is not set
# CONFIG_MTD_ALAUDA is not set
# CONFIG_MTD_ONENAND is not set

#
# UBI - Unsorted block images
#
CONFIG_MTD_UBI=m
CONFIG_MTD_UBI_WL_THRESHOLD=4096
CONFIG_MTD_UBI_BEB_RESERVE=1
# CONFIG_MTD_UBI_GLUEBI is not set

#
# UBI debugging options
#
# CONFIG_MTD_UBI_DEBUG is not set
# CONFIG_PARPORT is not set
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_ISAPNP=y
# CONFIG_PNPBIOS is not set
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_DEV_XD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
CONFIG_BLK_DEV_RAM_BLOCKSIZE=4096
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_MISC_DEVICES is not set
CONFIG_TIFM_CORE=m
# CONFIG_IDE is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=m
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=m
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=m
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
# CONFIG_SCSI_CONSTANTS is not set
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m
# CONFIG_SCSI_FC_TGT_ATTRS is not set
CONFIG_SCSI_ISCSI_ATTRS=m
CONFIG_SCSI_SAS_ATTRS=m
CONFIG_SCSI_SAS_LIBSAS=m
CONFIG_SCSI_SAS_ATA=y
# CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set
CONFIG_SCSI_SRP_ATTRS=m
# CONFIG_SCSI_SRP_TGT_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_DPT_I2O is not set
CONFIG_SCSI_ADVANSYS=m
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
CONFIG_ATA=m
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_ACPI=y
# CONFIG_SATA_AHCI is not set
# CONFIG_SATA_SVW is not set
# CONFIG_ATA_PIIX is not set
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
CONFIG_SATA_SIL=m
CONFIG_SATA_SIL24=m
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
CONFIG_PATA_ACPI=m
# CONFIG_PATA_ALI is not set
CONFIG_PATA_AMD=m
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5535 is not set
# CONFIG_PATA_CS5536 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
CONFIG_ATA_GENERIC=m
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_ISAPNP is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_LEGACY is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_QDI is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_WINBOND_VLB is not set
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_DM=m
CONFIG_DM_DEBUG=y
# CONFIG_DM_CRYPT is not set
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_UEVENT is not set
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
CONFIG_FIREWIRE=m
CONFIG_FIREWIRE_OHCI=m
CONFIG_FIREWIRE_SBP2=m
# CONFIG_IEEE1394 is not set
CONFIG_I2O=m
# CONFIG_I2O_LCT_NOTIFY_ON_CHANGES is not set
CONFIG_I2O_EXT_ADAPTEC=y
CONFIG_I2O_CONFIG=m
CONFIG_I2O_CONFIG_OLD_IOCTL=y
CONFIG_I2O_BUS=m
CONFIG_I2O_BLOCK=m
CONFIG_I2O_SCSI=m
CONFIG_I2O_PROC=m
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_NETDEVICES_MULTIQUEUE is not set
# CONFIG_IFB is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
# CONFIG_PHYLIB is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
CONFIG_NET_ISA=y
# CONFIG_E2100 is not set
# CONFIG_EWRK3 is not set
# CONFIG_EEXPRESS is not set
# CONFIG_EEXPRESS_PRO is not set
# CONFIG_HPLAN_PLUS is not set
# CONFIG_HPLAN is not set
# CONFIG_LP486E is not set
# CONFIG_ETH16I is not set
# CONFIG_NE2000 is not set
# CONFIG_ZNET is not set
# CONFIG_SEEQ8005 is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
CONFIG_FORCEDETH=m
# CONFIG_FORCEDETH_NAPI is not set
# CONFIG_CS89x0 is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
CONFIG_NE2K_PCI=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_SIS900=m
CONFIG_EPIC100=m
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
CONFIG_TLAN=m
CONFIG_VIA_RHINE=m
CONFIG_VIA_RHINE_MMIO=y
CONFIG_VIA_RHINE_NAPI=y
CONFIG_SC92031=m
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_WAN is not set
# CONFIG_ATM_DRIVERS is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_FF_MEMLESS=y
CONFIG_INPUT_POLLDEV=m

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1680
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1050
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_WISTRON_BTNS is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
# CONFIG_INPUT_ATI_REMOTE is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_UINPUT is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
CONFIG_GAMEPORT=m
# CONFIG_GAMEPORT_NS558 is not set
# CONFIG_GAMEPORT_L4 is not set
CONFIG_GAMEPORT_EMU10K1=m
# CONFIG_GAMEPORT_FM801 is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=2
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_IPMI_HANDLER=m
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_INTEL is not set
CONFIG_HW_RANDOM_AMD=m
# CONFIG_HW_RANDOM_GEODE is not set
# CONFIG_HW_RANDOM_VIA is not set
CONFIG_NVRAM=y
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
# CONFIG_HPET_MMAP is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=m
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
CONFIG_I2C_ALGOPCA=m

#
# I2C Hardware Bus support
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
CONFIG_I2C_AMD756=m
# CONFIG_I2C_AMD756_S4882 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_PIIX4 is not set
CONFIG_I2C_NFORCE2=m
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_SCx200_ACB is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_TINY_USB is not set
# CONFIG_I2C_VIA is not set
CONFIG_I2C_VIAPRO=m
# CONFIG_I2C_VOODOO3 is not set
# CONFIG_I2C_PCA_ISA is not set

#
# Miscellaneous I2C Chip support
#
# CONFIG_SENSORS_DS1337 is not set
# CONFIG_SENSORS_DS1374 is not set
# CONFIG_DS1682 is not set
CONFIG_SENSORS_EEPROM=m
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCA9539 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_MAX6875 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
CONFIG_HWMON=m
CONFIG_HWMON_VID=m
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FSCHER is not set
# CONFIG_SENSORS_FSCPOS is not set
# CONFIG_SENSORS_FSCHMD is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_CORETEMP is not set
# CONFIG_SENSORS_IBMPEX is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83L785TS is not set
CONFIG_SENSORS_W83627HF=m
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_SENSORS_APPLESMC is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
# CONFIG_WATCHDOG is not set

#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_V4L1_COMPAT=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_HELPER_CHIPS_AUTO is not set

#
# Encoders/decoders and other helper chips
#

#
# Audio decoders
#
CONFIG_VIDEO_TVAUDIO=m
CONFIG_VIDEO_TDA7432=m
CONFIG_VIDEO_TDA9840=m
CONFIG_VIDEO_TDA9875=m
CONFIG_VIDEO_TEA6415C=m
CONFIG_VIDEO_TEA6420=m
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_CS53L32A=m
CONFIG_VIDEO_TLV320AIC23B=m
CONFIG_VIDEO_WM8775=m
CONFIG_VIDEO_WM8739=m
CONFIG_VIDEO_VP27SMPX=m

#
# Video decoders
#
CONFIG_VIDEO_BT819=m
CONFIG_VIDEO_BT856=m
CONFIG_VIDEO_BT866=m
CONFIG_VIDEO_KS0127=m
CONFIG_VIDEO_OV7670=m
# CONFIG_VIDEO_TCM825X is not set
CONFIG_VIDEO_SAA7110=m
CONFIG_VIDEO_SAA7111=m
CONFIG_VIDEO_SAA7114=m
CONFIG_VIDEO_SAA711X=m
CONFIG_VIDEO_SAA7191=m
CONFIG_VIDEO_TVP5150=m
CONFIG_VIDEO_VPX3220=m

#
# Video and audio decoders
#
CONFIG_VIDEO_CX25840=m

#
# MPEG video encoders
#
CONFIG_VIDEO_CX2341X=m

#
# Video encoders
#
CONFIG_VIDEO_SAA7127=m
CONFIG_VIDEO_SAA7185=m
CONFIG_VIDEO_ADV7170=m
CONFIG_VIDEO_ADV7175=m

#
# Video improvement chips
#
CONFIG_VIDEO_UPD64031A=m
CONFIG_VIDEO_UPD64083=m
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_PMS is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_CPIA2 is not set
CONFIG_VIDEO_SAA5246A=m
CONFIG_VIDEO_SAA5249=m
CONFIG_TUNER_3036=m
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
CONFIG_VIDEO_CX88=m
CONFIG_VIDEO_CX88_ALSA=m
CONFIG_VIDEO_CX88_BLACKBIRD=m
CONFIG_VIDEO_CX88_DVB=m
CONFIG_VIDEO_CX88_VP3054=m
# CONFIG_VIDEO_CX23885 is not set
# CONFIG_VIDEO_IVTV is not set
# CONFIG_VIDEO_CAFE_CCIC is not set
# CONFIG_V4L_USB_DRIVERS is not set
CONFIG_RADIO_ADAPTERS=y
# CONFIG_RADIO_CADET is not set
# CONFIG_RADIO_RTRACK is not set
# CONFIG_RADIO_RTRACK2 is not set
# CONFIG_RADIO_AZTECH is not set
# CONFIG_RADIO_GEMTEK is not set
CONFIG_RADIO_GEMTEK_PCI=m
CONFIG_RADIO_MAXIRADIO=m
CONFIG_RADIO_MAESTRO=m
# CONFIG_RADIO_SF16FMI is not set
# CONFIG_RADIO_SF16FMR2 is not set
# CONFIG_RADIO_TERRATEC is not set
# CONFIG_RADIO_TRUST is not set
# CONFIG_RADIO_TYPHOON is not set
# CONFIG_RADIO_ZOLTRIX is not set
CONFIG_USB_DSBR=m
CONFIG_DVB_CORE=m
CONFIG_DVB_CORE_ATTACH=y
CONFIG_DVB_CAPTURE_DRIVERS=y

#
# Supported SAA7146 based PCI Adapters
#
CONFIG_DVB_AV7110=m
CONFIG_DVB_AV7110_OSD=y
CONFIG_DVB_BUDGET=m
CONFIG_DVB_BUDGET_CI=m
CONFIG_DVB_BUDGET_AV=m
CONFIG_DVB_BUDGET_PATCH=m

#
# Supported USB Adapters
#
CONFIG_DVB_USB=m
# CONFIG_DVB_USB_DEBUG is not set
CONFIG_DVB_USB_A800=m
CONFIG_DVB_USB_DIBUSB_MB=m
# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set
CONFIG_DVB_USB_DIBUSB_MC=m
CONFIG_DVB_USB_DIB0700=m
CONFIG_DVB_USB_UMT_010=m
CONFIG_DVB_USB_CXUSB=m
CONFIG_DVB_USB_M920X=m
CONFIG_DVB_USB_GL861=m
CONFIG_DVB_USB_AU6610=m
CONFIG_DVB_USB_DIGITV=m
CONFIG_DVB_USB_VP7045=m
CONFIG_DVB_USB_VP702X=m
CONFIG_DVB_USB_GP8PSK=m
CONFIG_DVB_USB_NOVA_T_USB2=m
CONFIG_DVB_USB_TTUSB2=m
CONFIG_DVB_USB_DTT200U=m
CONFIG_DVB_USB_OPERA1=m
CONFIG_DVB_USB_AF9005=m
CONFIG_DVB_USB_AF9005_REMOTE=m
CONFIG_DVB_TTUSB_BUDGET=m
CONFIG_DVB_TTUSB_DEC=m
CONFIG_DVB_CINERGYT2=m
CONFIG_DVB_CINERGYT2_TUNING=y
CONFIG_DVB_CINERGYT2_STREAM_URB_COUNT=32
CONFIG_DVB_CINERGYT2_STREAM_BUF_SIZE=512
CONFIG_DVB_CINERGYT2_QUERY_INTERVAL=250
CONFIG_DVB_CINERGYT2_ENABLE_RC_INPUT_DEVICE=y
CONFIG_DVB_CINERGYT2_RC_QUERY_INTERVAL=100

#
# Supported FlexCopII (B2C2) Adapters
#
CONFIG_DVB_B2C2_FLEXCOP=m
CONFIG_DVB_B2C2_FLEXCOP_PCI=m
CONFIG_DVB_B2C2_FLEXCOP_USB=m
# CONFIG_DVB_B2C2_FLEXCOP_DEBUG is not set

#
# Supported BT878 Adapters
#

#
# Supported Pluto2 Adapters
#
CONFIG_DVB_PLUTO2=m

#
# Supported DVB Frontends
#

#
# Customise DVB Frontends
#
# CONFIG_DVB_FE_CUSTOMISE is not set

#
# DVB-S (satellite) frontends
#
CONFIG_DVB_STV0299=m
CONFIG_DVB_CX24110=m
CONFIG_DVB_CX24123=m
CONFIG_DVB_TDA8083=m
CONFIG_DVB_MT312=m
CONFIG_DVB_VES1X93=m
CONFIG_DVB_S5H1420=m
CONFIG_DVB_TDA10086=m

#
# DVB-T (terrestrial) frontends
#
CONFIG_DVB_SP8870=m
CONFIG_DVB_SP887X=m
CONFIG_DVB_CX22700=m
CONFIG_DVB_CX22702=m
CONFIG_DVB_L64781=m
CONFIG_DVB_TDA1004X=m
CONFIG_DVB_NXT6000=m
CONFIG_DVB_MT352=m
CONFIG_DVB_ZL10353=m
CONFIG_DVB_DIB3000MB=m
CONFIG_DVB_DIB3000MC=m
CONFIG_DVB_DIB7000M=m
CONFIG_DVB_DIB7000P=m

#
# DVB-C (cable) frontends
#
CONFIG_DVB_VES1820=m
CONFIG_DVB_TDA10021=m
CONFIG_DVB_TDA10023=m
CONFIG_DVB_STV0297=m

#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends
#
CONFIG_DVB_NXT200X=m
CONFIG_DVB_OR51211=m
CONFIG_DVB_OR51132=m
CONFIG_DVB_BCM3510=m
CONFIG_DVB_LGDT330X=m
CONFIG_DVB_S5H1409=m

#
# Tuners/PLL support
#
CONFIG_DVB_PLL=m
CONFIG_DVB_TDA826X=m
CONFIG_DVB_TDA827X=m
CONFIG_DVB_TUNER_QT1010=m
CONFIG_DVB_TUNER_MT2060=m
CONFIG_DVB_TUNER_MT2266=m
CONFIG_DVB_TUNER_MT2131=m
CONFIG_DVB_TUNER_DIB0070=m

#
# Miscellaneous devices
#
CONFIG_DVB_LNBP21=m
CONFIG_DVB_ISL6421=m
CONFIG_DVB_TUA6100=m
CONFIG_VIDEO_SAA7146=m
CONFIG_VIDEO_SAA7146_VV=m
CONFIG_VIDEO_TUNER=m
CONFIG_VIDEO_TUNER_CUSTOMIZE=y
# CONFIG_TUNER_MT20XX is not set
# CONFIG_TUNER_TDA8290 is not set
# CONFIG_TUNER_TEA5761 is not set
# CONFIG_TUNER_TEA5767 is not set
CONFIG_TUNER_SIMPLE=m
CONFIG_VIDEOBUF_GEN=m
CONFIG_VIDEOBUF_DMA_SG=m
CONFIG_VIDEOBUF_DVB=m
CONFIG_VIDEO_BTCX=m
CONFIG_VIDEO_IR_I2C=m
CONFIG_VIDEO_IR=m
CONFIG_VIDEO_TVEEPROM=m
CONFIG_DAB=y
CONFIG_USB_DABUSB=m

#
# Graphics support
#
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=m
CONFIG_AGP_NVIDIA=y
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_I915 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
CONFIG_VGASTATE=m
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
CONFIG_FB_DDC=m
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_SYS_FOPS is not set
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_SVGALIB=m
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y

#
# Frame buffer hardware drivers
#
CONFIG_FB_CIRRUS=m
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=m
CONFIG_FB_UVESA=m
CONFIG_FB_VESA=y
# CONFIG_FB_EFI is not set
# CONFIG_FB_IMAC is not set
# CONFIG_FB_HECUBA is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
CONFIG_FB_NVIDIA=m
CONFIG_FB_NVIDIA_I2C=y
# CONFIG_FB_NVIDIA_DEBUG is not set
CONFIG_FB_NVIDIA_BACKLIGHT=y
CONFIG_FB_RIVA=m
# CONFIG_FB_RIVA_I2C is not set
# CONFIG_FB_RIVA_DEBUG is not set
CONFIG_FB_RIVA_BACKLIGHT=y
CONFIG_FB_I810=m
CONFIG_FB_I810_GTF=y
CONFIG_FB_I810_I2C=y
# CONFIG_FB_LE80578 is not set
CONFIG_FB_INTEL=m
# CONFIG_FB_INTEL_DEBUG is not set
CONFIG_FB_INTEL_I2C=y
CONFIG_FB_MATROX=m
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MAVEN=m
CONFIG_FB_MATROX_MULTIHEAD=y
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=m
CONFIG_FB_ATY128_BACKLIGHT=y
CONFIG_FB_ATY=m
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_ATY_BACKLIGHT=y
CONFIG_FB_S3=m
CONFIG_FB_SAVAGE=m
CONFIG_FB_SAVAGE_I2C=y
CONFIG_FB_SAVAGE_ACCEL=y
# CONFIG_FB_SIS is not set
CONFIG_FB_NEOMAGIC=m
CONFIG_FB_KYRO=m
CONFIG_FB_3DFX=m
CONFIG_FB_3DFX_ACCEL=y
CONFIG_FB_VOODOO1=m
# CONFIG_FB_VT8623 is not set
CONFIG_FB_CYBLA=m
CONFIG_FB_TRIDENT=m
CONFIG_FB_TRIDENT_ACCEL=y
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_CORGI is not set
# CONFIG_BACKLIGHT_PROGEAR is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=64
CONFIG_VIDEO_SELECT=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
CONFIG_SND_DYNAMIC_MINORS=y
# CONFIG_SND_SUPPORT_OLD_API is not set
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
# CONFIG_SND_SERIAL_U16550 is not set
CONFIG_SND_MPU401=m

#
# ISA devices
#
# CONFIG_SND_ADLIB is not set
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_DT019X is not set
# CONFIG_SND_ES968 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_SC6000 is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_MIRO is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set
# CONFIG_SND_WAVEFRONT is not set

#
# PCI devices
#
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
CONFIG_SND_EMU10K1=m
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDA_INTEL is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_AC97_POWER_SAVE is not set

#
# USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set

#
# System on Chip audio support
#
# CONFIG_SND_SOC is not set

#
# SoC Audio support for SuperH
#

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=m
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set
CONFIG_HIDRAW=y

#
# USB Input Devices
#
CONFIG_USB_HID=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_DEVICE_CLASS=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_PERSIST is not set
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
# CONFIG_USB_STORAGE_ISD200 is not set
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_STORAGE_ALAUDA=y
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_LIBUSUAL is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
CONFIG_USB_MON=y

#
# USB port drivers
#

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
# CONFIG_USB_SERIAL_GENERIC is not set
# CONFIG_USB_SERIAL_AIRCABLE is not set
# CONFIG_USB_SERIAL_AIRPRIME is not set
# CONFIG_USB_SERIAL_ARK3116 is not set
CONFIG_USB_SERIAL_BELKIN=m
# CONFIG_USB_SERIAL_CH341 is not set
# CONFIG_USB_SERIAL_WHITEHEAT is not set
# CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set
# CONFIG_USB_SERIAL_CP2101 is not set
# CONFIG_USB_SERIAL_CYPRESS_M8 is not set
# CONFIG_USB_SERIAL_EMPEG is not set
CONFIG_USB_SERIAL_FTDI_SIO=m
# CONFIG_USB_SERIAL_FUNSOFT is not set
# CONFIG_USB_SERIAL_VISOR is not set
CONFIG_USB_SERIAL_IPAQ=m
# CONFIG_USB_SERIAL_IR is not set
# CONFIG_USB_SERIAL_EDGEPORT is not set
# CONFIG_USB_SERIAL_EDGEPORT_TI is not set
CONFIG_USB_SERIAL_GARMIN=m
# CONFIG_USB_SERIAL_IPW is not set
# CONFIG_USB_SERIAL_KEYSPAN_PDA is not set
# CONFIG_USB_SERIAL_KEYSPAN is not set
# CONFIG_USB_SERIAL_KLSI is not set
# CONFIG_USB_SERIAL_KOBIL_SCT is not set
# CONFIG_USB_SERIAL_MCT_U232 is not set
# CONFIG_USB_SERIAL_MOS7720 is not set
# CONFIG_USB_SERIAL_MOS7840 is not set
# CONFIG_USB_SERIAL_NAVMAN is not set
CONFIG_USB_SERIAL_PL2303=m
# CONFIG_USB_SERIAL_OTI6858 is not set
# CONFIG_USB_SERIAL_HP4X is not set
# CONFIG_USB_SERIAL_SAFE is not set
# CONFIG_USB_SERIAL_SIERRAWIRELESS is not set
# CONFIG_USB_SERIAL_TI is not set
# CONFIG_USB_SERIAL_CYBERJACK is not set
# CONFIG_USB_SERIAL_XIRCOM is not set
# CONFIG_USB_SERIAL_OPTION is not set
# CONFIG_USB_SERIAL_OMNINET is not set
# CONFIG_USB_SERIAL_DEBUG is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set

#
# USB DSL modem support
#
# CONFIG_USB_ATM is not set

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
CONFIG_MMC=m
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set

#
# MMC/SD Card Drivers
#
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_BOUNCE=y
# CONFIG_SDIO_UART is not set

#
# MMC/SD Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
# CONFIG_MMC_RICOH_MMC is not set
CONFIG_MMC_WBSD=m
CONFIG_MMC_TIFM_SD=m
# CONFIG_NEW_LEDS is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC=y

#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_MM_EDAC=y
CONFIG_EDAC_AMD76X=m
# CONFIG_EDAC_E7XXX is not set
# CONFIG_EDAC_E752X is not set
# CONFIG_EDAC_I82875P is not set
# CONFIG_EDAC_I82975X is not set
# CONFIG_EDAC_I3000 is not set
# CONFIG_EDAC_I82860 is not set
# CONFIG_EDAC_R82600 is not set
# CONFIG_EDAC_I5000 is not set
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
# CONFIG_VIRTUALIZATION is not set

#
# Userspace I/O
#
# CONFIG_UIO is not set

#
# Firmware Drivers
#
CONFIG_EDD=m
CONFIG_EFI_VARS=y
CONFIG_DELL_RBU=m
CONFIG_DCDBAS=m
CONFIG_DMIID=y

#
# File systems
#
CONFIG_EXT2_FS=m
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT2_FS_XIP=y
CONFIG_FS_XIP=y
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
# CONFIG_EXT4DEV_FS is not set
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=m
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
CONFIG_ROMFS_FS=m
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=m
CONFIG_FUSE_FS=m
CONFIG_GENERIC_ACL=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="ascii"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
CONFIG_CONFIGFS_FS=m

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ECRYPT_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_JFFS2_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_SUNRPC_GSS=m
CONFIG_SUNRPC_BIND34=y
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_RPCSEC_GSS_SPKM3=m
# CONFIG_SMB_FS is not set
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
CONFIG_CIFS_WEAK_PW_HASH=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=m
CONFIG_DLM=m
CONFIG_DLM_DEBUG=y
# CONFIG_INSTRUMENTATION is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_PRINTK_TIME=y
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_FS=y
CONFIG_HEADERS_CHECK=y
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_SHIRQ=y
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHED_DEBUG=y
CONFIG_SCHEDSTATS=y
CONFIG_TIMER_STATS=y
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_HIGHMEM=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_VM is not set
CONFIG_DEBUG_LIST=y
# CONFIG_DEBUG_SG is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_FORCED_INLINING is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_SAMPLES is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set

#
# Page alloc debug is incompatible with Software Suspend on i386
#
CONFIG_DEBUG_RODATA=y
CONFIG_4KSTACKS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y

#
# Security options
#
CONFIG_KEYS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=y
CONFIG_SECURITY_CAPABILITIES=y
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
# CONFIG_SECURITY_ROOTPLUG is not set
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
CONFIG_SECURITY_SELINUX_ENABLE_SECMARK_DEFAULT=y
# CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=m
CONFIG_CRYPTO_NULL=m
CONFIG_CRYPTO_MD4=m
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_WP512=m
CONFIG_CRYPTO_TGR192=m
CONFIG_CRYPTO_GF128MUL=m
CONFIG_CRYPTO_ECB=m
CONFIG_CRYPTO_CBC=m
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_LRW=m
# CONFIG_CRYPTO_XTS is not set
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_DES=m
CONFIG_CRYPTO_FCRYPT=m
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
CONFIG_CRYPTO_TWOFISH_586=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_AES_586=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_TEA=m
CONFIG_CRYPTO_ARC4=m
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_ANUBIS=m
# CONFIG_CRYPTO_SEED is not set
CONFIG_CRYPTO_DEFLATE=m
CONFIG_CRYPTO_MICHAEL_MIC=m
CONFIG_CRYPTO_CRC32C=y
CONFIG_CRYPTO_CAMELLIA=m
CONFIG_CRYPTO_TEST=m
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_HW is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=m
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=y
CONFIG_AUDIT_GENERIC=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_REED_SOLOMON=m
CONFIG_REED_SOLOMON_DEC16=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y

Re: Problem with ata layer in 2.6.24

[Mikael Pettersson]

Gene Heskett writes:
 > On Tuesday 29 January 2008, Alan Cox wrote:
 > >> As slight change here, I was going to use the same .config as 2.6.24-rc8,
 > >> but just discovered that neither rc8 nor final is finding the drivers for
 > >> my
 > >
 > >If it is not finding a driver that is nothing to do with libata. It means
 > >it's not being loaded by the distribution, or the distribution kernel is
 > >too old (2.6.22) for the hardware - in which case see the Fedora respins
 > >which are on 2.6.23.something right now.
 > >
 > >Alan
 > 
 > Home built kernel Alan.  But you are as good as anyone to tell me what I 
 > need to turn on in order for this dvdwriter to be enabled:
 > [   28.862478] ata2.00: ATAPI: LITE-ON DVDRW SHM-165H6S, HS06, max UDMA/66
 > ....
 > [   28.908647] ata2.00: limited to UDMA/33 due to 40-wire cable
 > [   29.081253] ata2.00: configured for UDMA/33
 > ....
 > it has had several 80 wire cables tried, hasn't fixed this, and does not
 > seem to effect its operation when it does work.
 > ....
 > [   29.132405] scsi 1:0:0:0: CD-ROM            LITE-ON  DVDRW SHM-165H6S HS06 PQ: 0 ANSI: 5
 > ....
 > [   43.450795] scsi 1:0:0:0: Attached scsi generic sg1 type 5
 > -------
 > No further mention of it in dmesg, and k3b cannot find the drive at any 
 > /dev/sgX address.
 > 
 > .config attached, what else do I need to turn on?

...

 > # CONFIG_BLK_DEV_SR is not set

For starters, enable CONFIG_BLK_DEV_SR.

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Tuesday 29 January 2008, Mikael Pettersson wrote:
>Gene Heskett writes:
> > On Tuesday 29 January 2008, Alan Cox wrote:
> > >> As slight change here, I was going to use the same .config as
> > >> 2.6.24-rc8, but just discovered that neither rc8 nor final is finding
> > >> the drivers for my
> > >
> > >If it is not finding a driver that is nothing to do with libata. It
> > > means it's not being loaded by the distribution, or the distribution
> > > kernel is too old (2.6.22) for the hardware - in which case see the
> > > Fedora respins which are on 2.6.23.something right now.
> > >
> > >Alan
> >
> > Home built kernel Alan.  But you are as good as anyone to tell me what I
> > need to turn on in order for this dvdwriter to be enabled:
> > [   28.862478] ata2.00: ATAPI: LITE-ON DVDRW SHM-165H6S, HS06, max
> > UDMA/66 ....
> > [   28.908647] ata2.00: limited to UDMA/33 due to 40-wire cable
> > [   29.081253] ata2.00: configured for UDMA/33
> > ....
> > it has had several 80 wire cables tried, hasn't fixed this, and does not
> > seem to effect its operation when it does work.
> > ....
> > [   29.132405] scsi 1:0:0:0: CD-ROM            LITE-ON  DVDRW SHM-165H6S
> > HS06 PQ: 0 ANSI: 5 ....
> > [   43.450795] scsi 1:0:0:0: Attached scsi generic sg1 type 5
> > -------
> > No further mention of it in dmesg, and k3b cannot find the drive at any
> > /dev/sgX address.
> >
> > .config attached, what else do I need to turn on?
>
>...
>
> > # CONFIG_BLK_DEV_SR is not set
>
>For starters, enable CONFIG_BLK_DEV_SR.

That could stand to be moved or renamed, it is well buried in the menu for the 
REAL scsi stuffs, which I don't have any of.  Enabled & building now.  
Thanks.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
An air of FRENCH FRIES permeates my nostrils!!

Re: Problem with ata layer in 2.6.24

[Daniel Barkalow]

On Tue, 29 Jan 2008, Gene Heskett wrote:

> >For starters, enable CONFIG_BLK_DEV_SR.
> 
> That could stand to be moved or renamed, it is well buried in the menu for the 
> REAL scsi stuffs, which I don't have any of.  Enabled & building now.  

The "SCSI support type (disk, tape, CD-ROM)" section of that menu actually 
applies to all ATA-command-set devices that don't use the old IDE code. 
For example, usb-storage uses "SCSI disk" out of that section, and 
I've only seen "Probe all LUNs on each SCSI device" be needed for a 
particular USB card reader with two slots. At this point, most of the 
things in the kernel that refer to SCSI probably should say "storage" (or 
"ATA", really, but that would make the acronyms confusing).

Incidentally, you should be able to save debugging time for problems like 
missing "sr" by building it as a module, which will build really quickly 
and not require a reboot to test.

	-Daniel
*This .sig left intentionally blank*

Re: Problem with ata layer in 2.6.24

[Alan Cox]

> things in the kernel that refer to SCSI probably should say "storage" (or 
> "ATA", really, but that would make the acronyms confusing).

SCSI is a command protocol. It is what your CD-ROM drive and USB storage
devices talk (albeit with a bit of an accent).

Alan

Re: Problem with ata layer in 2.6.24

[Daniel Barkalow]

On Tue, 29 Jan 2008, Alan Cox wrote:

> > things in the kernel that refer to SCSI probably should say "storage" (or 
> > "ATA", really, but that would make the acronyms confusing).
> 
> SCSI is a command protocol. It is what your CD-ROM drive and USB storage
> devices talk (albeit with a bit of an accent).

Among other things, yes. But SCSI standards also specify electrical 
interfaces that aren't at all related to the electrical interfaces used by 
a lot of devices, and a lot of the places the kernel uses the term suggest 
that it's also talking about the electrical interface (or, at least, 
connector shape). For example, it's misleading to talk about "SCSI CDROM 
support" meaning the command protocol when hardly anybody has ever seen a 
CDROM drive that doesn't use the SCSI command protocol, but most people 
know about both SCSI-connector and PATA-connector CDROM drives.

	-Daniel
*This .sig left intentionally blank*

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Tuesday 29 January 2008, Daniel Barkalow wrote:
>On Tue, 29 Jan 2008, Gene Heskett wrote:
>> >For starters, enable CONFIG_BLK_DEV_SR.
>>
>> That could stand to be moved or renamed, it is well buried in the menu for
>> the REAL scsi stuffs, which I don't have any of.  Enabled & building now.
>
>The "SCSI support type (disk, tape, CD-ROM)" section of that menu actually
>applies to all ATA-command-set devices that don't use the old IDE code.
>For example, usb-storage uses "SCSI disk" out of that section, and
>I've only seen "Probe all LUNs on each SCSI device" be needed for a
>particular USB card reader with two slots. At this point, most of the
>things in the kernel that refer to SCSI probably should say "storage" (or
>"ATA", really, but that would make the acronyms confusing).
>
>Incidentally, you should be able to save debugging time for problems like
>missing "sr" by building it as a module, which will build really quickly
>and not require a reboot to test.
>
>	-Daniel
>*This .sig left intentionally blank*

I did, Daniel, but while that has worked, its not been 100% foolproof in the 
past, so I just waste the 9 minutes building a new kernel as cheap insurance.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Mal: "If it's Alliance trouble you got, you might want to consider another
ship. Some onboard here fought for the Independents."
				--Episode #8, "Out of Gas"

Re: Problem with ata layer in 2.6.24

[Alan Cox]

> That could stand to be moved or renamed, it is well buried in the menu for the 
> REAL scsi stuffs, which I don't have any of.  

Yes you do - USB storage and ATAPI are SCSI

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Tuesday 29 January 2008, Alan Cox wrote:
>> That could stand to be moved or renamed, it is well buried in the menu for
>> the REAL scsi stuffs, which I don't have any of.
>
>Yes you do - USB storage and ATAPI are SCSI

By the linux software definition maybe.  But I've defined scsi as that which 
uses a 50 wire cable using 50 contact centronics connectors since the 
mid '70's, and which often needs a ready supply of nubile virgins to 
sacrifice to make it work, particularly with the old resistor pack 
terminations & psu's whose 5 volt line is only 4.85 volts due to old age.  
That's what I call REAL scsi.  Its also a REAL PITA if the terms aren't 
active.

You can call what you are doing 'scsi' because you are using much the same 
command structure, and that is good, but its not the real thing with all its 
hardware warts and/or capabilities.  For one thing, this version usually 
works. :)

Furinstance, you can tell 2 scsi devices on the same controller to talk to 
each other, moving files from one to the other, and the host controller can 
then goto sleep & the cpu isn't involved until the devices send it a wakeup 
to advise the controller that the transfer has been done, and the controller 
may or may not then interrupt and advise the cpu.  You can do that with 
separate controllers too as long as they have a compatible DMA channel 
available to both.

I doubt libata has that capability now, or ever will, cuz these ide/atapi 
devices are generally dumber than rocks about that.  But any device claiming 
to be scsi-II is supposed to be able to do those sorts of things while the 
cpu is off crunching numbers for BOINC or whatever.

But that puts my mild objections to classifying this as 'scsi' in a more 
understandable context.  :-)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
When some people decide it's time for everyone to make big changes,
it means that they want you to change first.

Re: Problem with ata layer in 2.6.24

[Alan Cox]

> By the linux software definition maybe.  But I've defined scsi as that which 
> uses a 50 wire cable using 50 contact centronics connectors since the 
> mid '70's, and which often needs a ready supply of nubile virgins t

25, 50 or 68, with multiple voltage levels, plus of course it might be
over fibre or copper FC loop and ..

SCSI is a protocol.

Re: Problem with ata layer in 2.6.24

[Mark Lord]

Gene Heskett wrote:
>
> I doubt libata has that capability now, or ever will, cuz these ide/atapi 
> devices are generally dumber than rocks about that.  But any device claiming 
> to be scsi-II is supposed to be able to do those sorts of things while the 
> cpu is off crunching numbers for BOINC or whatever.
..

The CD/DVD drives all all "MMC" devices internally, which means they speak
a SCSI command protocol.  Regardless of the electrical or optical interface.

Linux is software, and the software protocol is exactly the same for them,
no matter what the cable/bus type happens to be.

Cheers

Re: Problem with ata layer in 2.6.24

[rgheck]

Alan Cox wrote:
>> not one problem but lots---is sufficiently widespread that a Mini HOWTO, 
>> say, would be really welcome and, I'm guessing, widely used.
>>     
>
> We don't see very many libata problems at the distro level and they for
> the most part boil down to
>
> - sata_nv with >4GB of RAM, knowing being worked on, no old IDE driver
> anyway
>   
Is this >4GB or >=4GB? I've seen contradictory reports, and I've got 4GB.

Richard

Re: Problem with ata layer in 2.6.24

[Alan Cox]

  
> Is this >4GB or >=4GB? I've seen contradictory reports, and I've got 4GB.

Depends how the memory is mapped. Any memory physically above the 4GB
boundary

Alan

Re: Problem with ata layer in 2.6.24

[Mark Lord]

rgheck wrote:
> Alan Cox wrote:
>>> not one problem but lots---is sufficiently widespread that a Mini 
>>> HOWTO, say, would be really welcome and, I'm guessing, widely used.
>>>     
>>
>> We don't see very many libata problems at the distro level and they for
>> the most part boil down to
>>
>> - sata_nv with >4GB of RAM, knowing being worked on, no old IDE driver
>> anyway
>>   
> Is this >4GB or >=4GB? I've seen contradictory reports, and I've got 4GB.
..

For all practical purposes, most memory over 3GB (or sometimes even 2GB)
on a 32-bit x86 system is treated as >4GB by the motherboard.

Because it's not the amount of *memory* that matters so much,
but rather the amount of *used address space*.  Video cards,
PCI devices, other motherboard resources etc.. can all subtract
from the available address space, leaving much less than 4GB
for your RAM. 

-ml

Re: Problem with ata layer in 2.6.24

[rgheck]

Mark Lord wrote:
> rgheck wrote:
>> Alan Cox wrote:
>>>> not one problem but lots---is sufficiently widespread that a Mini 
>>>> HOWTO, say, would be really welcome and, I'm guessing, widely used.
>>>>     
>>>
>>> We don't see very many libata problems at the distro level and they for
>>> the most part boil down to
>>>
>>> - sata_nv with >4GB of RAM, knowing being worked on, no old IDE driver
>>> anyway
>>>   
>> Is this >4GB or >=4GB? I've seen contradictory reports, and I've got 
>> 4GB.
> ..
>
> For all practical purposes, most memory over 3GB (or sometimes even 2GB)
> on a 32-bit x86 system is treated as >4GB by the motherboard.
>
> Because it's not the amount of *memory* that matters so much,
> but rather the amount of *used address space*.  Video cards,
> PCI devices, other motherboard resources etc.. can all subtract
> from the available address space, leaving much less than 4GB
> for your RAM.

Right. So it looks like I do have this issue, though I haven't seen any 
actual problems on 24. Is there a known workaround?

rh

Re: Problem with ata layer in 2.6.24

[Mark Lord]

rgheck wrote:
> Mark Lord wrote:
>> rgheck wrote:
>>> Alan Cox wrote:
>>>>> not one problem but lots---is sufficiently widespread that a Mini 
>>>>> HOWTO, say, would be really welcome and, I'm guessing, widely used.
>>>>>     
>>>>
>>>> We don't see very many libata problems at the distro level and they for
>>>> the most part boil down to
>>>>
>>>> - sata_nv with >4GB of RAM, knowing being worked on, no old IDE driver
>>>> anyway
>>>>   
>>> Is this >4GB or >=4GB? I've seen contradictory reports, and I've got 
>>> 4GB.
>> ..
>>
>> For all practical purposes, most memory over 3GB (or sometimes even 2GB)
>> on a 32-bit x86 system is treated as >4GB by the motherboard.
>>
>> Because it's not the amount of *memory* that matters so much,
>> but rather the amount of *used address space*.  Video cards,
>> PCI devices, other motherboard resources etc.. can all subtract
>> from the available address space, leaving much less than 4GB
>> for your RAM.
> 
> Right. So it looks like I do have this issue, though I haven't seen any 
> actual problems on 24. Is there a known workaround?
..

For now, the workaround is to not enable the RAM above 4GB.
Your kernel .config file should therefore have these two lines:

CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set

Later, once the issue is fixed at the driver level (soon),
you can get your high memory back again by enabling CONFIG_HIGHMEM64G,
though this will cost a few percent of performance in the extra
page table overhead it creates.

Cheers

Re: Problem with ata layer in 2.6.24

[Daniel Barkalow]

On Tue, 29 Jan 2008, Alan Cox wrote:

> > not one problem but lots---is sufficiently widespread that a Mini HOWTO, 
> > say, would be really welcome and, I'm guessing, widely used.
> 
> We don't see very many libata problems at the distro level and they for
> the most part boil down to
> 
> - error messages looking different - Most bugs I get are things like
> media errors (timeout looks different, UNC report looks different)

The SCSI error reporting really ought to include a simple interpretation 
of the error for end users ("The drive doesn't support this command" "A 
sector's data got lost" "The drive timed out" "The drive failed" "The 
drive is entirely gone"). There's too much similarity between the message 
you get when you try a SMART test that doesn't apply to the drive and what 
you get when the drive is broken.

> - faulty hardware being picked up because we actually do real error
> checking now. We now check for and give some devices more slack while
> still doing error checking. Both IDE layers also added blacklists for
> stuff like the TSScorp DVD drives. Qemu has now had its bugs patched.

I think this is the big source of unhappy users (and, of course, they all 
look the same and the reports stay findable by Google, so it looks a lot 
worse than it is). People getting this problem in distro kernels probably 
really do want to have a way to report it with enough detail from logs to 
get it dealt with and then switch back to old IDE until the fix propagates 
through.

And it's possible that the error recovery is suboptimal in some cases. It 
seems to like resetting drives too much; perhaps if it keeps seeing the 
same problem and resetting the drive, it should decide that the drive's 
error reporting is just bad and just ignore that error like the old IDE 
did (but, in this case, after saying what it's doing).

	-Daniel
*This .sig left intentionally blank*

Re: Problem with ata layer in 2.6.24

[Alan Cox]

> The SCSI error reporting really ought to include a simple interpretation 
> of the error for end users ("The drive doesn't support this command" "A 
> sector's data got lost" "The drive timed out" "The drive failed" "The 
> drive is entirely gone"). There's too much similarity between the message 
> you get when you try a SMART test that doesn't apply to the drive and what 
> you get when the drive is broken.

That would be the SCSI verbose messages option. I think the Eric
Youngdale consortium added it about Linux 1.2. Nowdays its always built
that way.

> And it's possible that the error recovery is suboptimal in some cases. It 
> seems to like resetting drives too much; perhaps if it keeps seeing the 
> same problem and resetting the drive, it should decide that the drive's 
> error reporting is just bad and just ignore that error like the old IDE 
> did (but, in this case, after saying what it's doing).

Nothing like casually praying the users data hasn't gone for a walk is
there. If we don't act on them the users don't report them until
something really bad occurs so that isn't an option.

Alan

Re: Problem with ata layer in 2.6.24

[Daniel Barkalow]

On Tue, 29 Jan 2008, Alan Cox wrote:

> > The SCSI error reporting really ought to include a simple interpretation 
> > of the error for end users ("The drive doesn't support this command" "A 
> > sector's data got lost" "The drive timed out" "The drive failed" "The 
> > drive is entirely gone"). There's too much similarity between the message 
> > you get when you try a SMART test that doesn't apply to the drive and what 
> > you get when the drive is broken.
> 
> That would be the SCSI verbose messages option. I think the Eric
> Youngdale consortium added it about Linux 1.2. Nowdays its always built
> that way.

I've seen a lot of verbosity out of SCSI messages, but I haven't seen a 
straightforward interpretation of the problem in there. It's all 
information useful for debugging, not information useful for system 
administration.

> > And it's possible that the error recovery is suboptimal in some cases. It 
> > seems to like resetting drives too much; perhaps if it keeps seeing the 
> > same problem and resetting the drive, it should decide that the drive's 
> > error reporting is just bad and just ignore that error like the old IDE 
> > did (but, in this case, after saying what it's doing).
> 
> Nothing like casually praying the users data hasn't gone for a walk is
> there. If we don't act on them the users don't report them until
> something really bad occurs so that isn't an option.

On the other hand, bringing the system down because a device is 
misbehaving is a poor idea. I've personally recovered most of the data off 
of a dying drive because the system was willing to let me keep using the 
drive anyway; IIRC, the drive didn't work at all after a reboot, so I 
would have lost all the data instead of only a little had the system 
insisted on a perfectly functioning drive in order to use it at all.

There ought to be some middle ground between doing nothing until the 
computer really breaks and breaking the computer before then, but that's 
an issue not specific to libata.

	-Daniel
*This .sig left intentionally blank*

Re: Problem with ata layer in 2.6.24

[Alan Cox]

> I've seen a lot of verbosity out of SCSI messages, but I haven't seen a 
> straightforward interpretation of the problem in there. It's all 
> information useful for debugging, not information useful for system 
> administration.

It tells you what is going on. Unfortunately that frequently requires
some basic knowledge of how to interpret the error report. Drive
interface behaviour simply doesn't boil down to a fault light on the
dashboard or a "tighten the cable". For most common fault types you'll
get errors most administrators should find meaningful - like "Media error"

> On the other hand, bringing the system down because a device is 
> misbehaving is a poor idea. I've personally recovered most of the data off 

Hence we have RAID and SATA hotplug.

Alan

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

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

On Monday 28 January 2008, Gene Heskett wrote:
While reading this msg as it came back, I locked up again and rebooted to 
2.6.24, and got lucky (maybe) as the attached dmesg will show quite a few 
instances of this LOOOONNNGG before the nvidia driver is loaded to taint the 
kernel.  Have fun guys!
 
>On Monday 28 January 2008, Mikael Pettersson wrote:
>>Gene Heskett writes:
>> > On Monday 28 January 2008, Peter Zijlstra wrote:
>> > >On Mon, 2008-01-28 at 09:17 +0100, Mikael Pettersson wrote:
>> > >> 1. Wrong mailing list; use linux-ide (@vger) instead.
>> > >
>> > >What, and keep all us other interested people in the dark?
>> >
>> > As a test, I tried rebooting to the latest fedora kernel and found it
>> > kills X, so I'm back to the second to last fedora version ATM, and the
>> > third 'smartctl -t lng /dev/sda' in 24 hours is running now.  The first
>> > two completed with no errors.
>> >
>> > I've added the linux-ide list to refresh those people of the problem,
>> > the logs are being spammed by this message stanza:
>> >
>> >  Jan 28 04:46:25 coyote kernel: [26550.290016] ata1.00: exception Emask
>> > 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Jan 28 04:46:25 coyote kernel:
>> > [26550.290028] ata1.00: cmd 35/00:58:c9:9c:0a/00:01:00:00:00/e0 tag 0
>> > dma 176128 out Jan 28 04:46:25 coyote kernel: [26550.290029]         
>> > res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 28
>> > 04:46:25 coyote kernel: [26550.290032] ata1.00: status: { DRDY } Jan 28
>> > 04:46:25 coyote kernel: [26550.290060] ata1: soft resetting link Jan 28
>> > 04:46:25 coyote kernel: [26550.452301] ata1.00: configured for UDMA/100
>> > Jan 28 04:46:25 coyote kernel: [26550.452318] ata1: EH complete
>> > Jan 28 04:46:25 coyote kernel: [26550.455898] sd 0:0:0:0: [sda]
>> > 390721968 512-byte hardware sectors (200050 MB) Jan 28 04:46:25 coyote
>> > kernel: [26550.456151] sd 0:0:0:0: [sda] Write Protect is off Jan 28
>> > 04:46:25 coyote kernel: [26550.456403] sd 0:0:0:0: [sda] Write cache:
>> > enabled, read cache: enabled, doesn't support DPO or FUA
>>
>>It's not obvious from this incomplete dmesg log what HW or driver
>>is behind ata1, but if the 2.6.24-rc7 kernel matches the 2.6.24 one,
>>
>>it should be pata_amd driving a WDC disk:
>> > [   30.702887] pata_amd 0000:00:09.0: version 0.3.10
>> > [   30.703052] PCI: Setting latency timer of device 0000:00:09.0 to 64
>> > [   30.703188] scsi0 : pata_amd
>> > [   30.709313] scsi1 : pata_amd
>> > [   30.710076] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000
>> > irq 14 [   30.710079] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma
>> > 0xf008 irq 15 [   30.864753] ata1.00: ATA-6: WDC WD2000JB-00EVA0,
>> > 15.05R15, max UDMA/100 [   30.864756] ata1.00: 390721968 sectors, multi
>> > 16: LBA48
>> > [   30.871629] ata1.00: configured for UDMA/100
>>
>>Unfortunately we also see:
>> > [   48.285456] nvidia: module license 'NVIDIA' taints kernel.
>> > [   48.549725] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI
>> > 19 (level, high) -> IRQ 20 [   48.550149] NVRM: loading NVIDIA UNIX x86
>> > Kernel Module  169.07  Thu Dec 13 18:42:56 PST 2007
>>
>>We have no way of debugging that module, so please try 2.6.24 without it.
>
>Sorry, I can't do this and have a working machine.  The nv driver has
> suffered bit rot or something since the FC2 days when it COULD run a 19"
> crt at 1600x1200, and will not drive this 20" wide screen lcd 1680x1050
> monitor at more than 800x600, which is absolutely butt ugly fuzzy, looking
> like a jpg compressed to 10%.  The system is not usable on a day to basis
> without the nvidia driver.
>
>Fix the nv driver so it will run this screen at its native resolution and
> I'll be glad to run it even if it won't run google earth, which I do use
> from time to time.  Now, if in all the hits you can get from google on
> this, currently 14,800 just for 'exception Emask', apparently caused by a
> timeout, if 100% of the complainers are running nvidia drivers also, then I
> see a legit complaint.  Again, fix the nv driver so it will run my screen &
> I'll be glad to switch.  I can see the reason, sure, but the machine must
> be capable of doing its common day to day stuff, while using that driver,
> like running kde for kmail, and browsers that work.
>
>>If the problems persist, please try to capture a complete log from the
>>failing kernel -- the interesting bits are everything from initial boot
>>up to and including the first few errors. You may need to increase the
>>kernel's log buffer size if the log gets truncated (CONFIG_LOG_BUF_SHIFT).
>
>If by log you mean /var/log/messages, I have several megabytes of those.
>If you mean a live dmesg capture taken right now, its attached. It contains
>several of these at the bottom.  I long ago made the kernel log buffer
>bigger, cuz it couldn't even show the start immediately after the boot, and
>even the dump to syslog was truncated.
>
>>There are no pata_amd changes from 2.6.24-rc7 to 2.6.24 final.
>
>That is what I was afraid of.  I've done some limited grepping in that
> branch of the kernel tree, and cannot seem to locate where this EH handler
> is being invoked from.
>
>There is 2 lines of interest in the dmesg:
>
>[    0.000000] Nvidia board detected. Ignoring ACPI timer override.
>[    0.000000] If you got timer trouble try acpi_use_timer_override
>
>But I have NDI what it means, kernel argument/xconfig option?
>
>I've also done some googling, and it appears this problem is fairly
> widespread since the switchover to libata was encouraged.  A stock fedora
> F8 kernel suffers the same freezes and eventually locks up, but does it
> without the error messages being logged, it just freezes, feeling identical
> to this in the minutes before the total freeze.  I've tried 2 of those too,
> but the newest one won't even run X.



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Deprive a mirror of its silver and even the Czar won't see his face.

[-- Attachment #2: dmesg --]
[-- Type: text/plain, Size: 43089 bytes --]

[    0.000000] Linux version 2.6.24 (root@coyote.coyote.den) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Thu Jan 24 20:17:55 EST 2008
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[    0.000000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
[    0.000000]  BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
[    0.000000]  BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
[    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
[    0.000000] 127MB HIGHMEM available.
[    0.000000] 896MB LOWMEM available.
[    0.000000] Entering add_active_range(0, 0, 262128) 0 entries of 256 used
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA             0 ->     4096
[    0.000000]   Normal       4096 ->   229376
[    0.000000]   HighMem    229376 ->   262128
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[1] active PFN ranges
[    0.000000]     0:        0 ->   262128
[    0.000000] On node 0 totalpages: 262128
[    0.000000]   DMA zone: 32 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 4064 pages, LIFO batch:0
[    0.000000]   Normal zone: 1760 pages used for memmap
[    0.000000]   Normal zone: 223520 pages, LIFO batch:31
[    0.000000]   HighMem zone: 255 pages used for memmap
[    0.000000]   HighMem zone: 32497 pages, LIFO batch:7
[    0.000000]   Movable zone: 0 pages used for memmap
[    0.000000] DMI 2.2 present.
[    0.000000] ACPI: RSDP 000F7220, 0014 (r0 Nvidia)
[    0.000000] ACPI: RSDT 3FFF3000, 002C (r1 Nvidia AWRDACPI 42302E31 AWRD        0)
[    0.000000] ACPI: FACP 3FFF3040, 0074 (r1 Nvidia AWRDACPI 42302E31 AWRD        0)
[    0.000000] ACPI: DSDT 3FFF30C0, 4CC4 (r1 NVIDIA AWRDACPI     1000 MSFT  100000E)
[    0.000000] ACPI: FACS 3FFF0000, 0040
[    0.000000] ACPI: APIC 3FFF7DC0, 006E (r1 Nvidia AWRDACPI 42302E31 AWRD        0)
[    0.000000] Nvidia board detected. Ignoring ACPI timer override.
[    0.000000] If you got timer trouble try acpi_use_timer_override
[    0.000000] ACPI: PM-Timer IO Port: 0x4008
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] Processor #0 6:10 APIC version 16
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: BIOS IRQ0 pin2 override ignored.
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] ACPI: IRQ14 used by override.
[    0.000000] ACPI: IRQ15 used by override.
[    0.000000] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
[    0.000000] swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
[    0.000000] swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000f0000
[    0.000000] swsusp: Registered nosave memory region: 00000000000f0000 - 0000000000100000
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260081
[    0.000000] Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
[    0.000000] mapped APIC to ffffb000 (fee00000)
[    0.000000] mapped IOAPIC to ffffa000 (fec00000)
[    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] CPU 0 irqstacks, hard=c0743000 soft=c0723000
[    0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
[    0.000000] Detected 2079.540 MHz processor.
[   24.833457] Console: colour VGA+ 80x25
[   24.833460] console [tty0] enabled
[   24.834029] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[   24.834561] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[   24.865989] Memory: 1031080k/1048512k available (1951k kernel code, 16692k reserved, 986k data, 240k init, 131008k highmem)
[   24.865998] virtual kernel memory layout:
[   24.865999]     fixmap  : 0xffc55000 - 0xfffff000   (3752 kB)
[   24.866001]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
[   24.866002]     vmalloc : 0xf8800000 - 0xff7fe000   ( 111 MB)
[   24.866003]     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
[   24.866004]       .init : 0xc06e4000 - 0xc0720000   ( 240 kB)
[   24.866006]       .data : 0xc05e7cd4 - 0xc06de6e4   ( 986 kB)
[   24.866007]       .text : 0xc0400000 - 0xc05e7cd4   (1951 kB)
[   24.866010] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[   24.866059] SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
[   24.926020] Calibrating delay using timer specific routine.. 4160.90 BogoMIPS (lpj=2080453)
[   24.926053] Security Framework initialized
[   24.926059] SELinux:  Initializing.
[   24.926072] SELinux:  Starting in permissive mode
[   24.926086] selinux_register_security:  Registering secondary module capability
[   24.926088] Capability LSM initialized as secondary
[   24.926098] Mount-cache hash table entries: 512
[   24.926267] CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000 00000000 00000000 00000000 00000000
[   24.926275] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
[   24.926278] CPU: L2 Cache: 512K (64 bytes/line)
[   24.926280] CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000420 00000000 00000000 00000000 00000000
[   24.926286] Intel machine check architecture supported.
[   24.926289] Intel machine check reporting enabled on CPU#0.
[   24.926294] Compat vDSO mapped to ffffe000.
[   24.926308] Checking 'hlt' instruction... OK.
[   24.930188] SMP alternatives: switching to UP code
[   24.930705] Freeing SMP alternatives: 13k freed
[   24.930709] ACPI: Core revision 20070126
[   24.933945] CPU0: AMD Athlon(tm) XP 2800+ stepping 00
[   24.933969] Total of 1 processors activated (4160.90 BogoMIPS).
[   24.934176] ENABLING IO-APIC IRQs
[   24.934367] ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1
[   25.045973] Brought up 1 CPUs
[   25.046000] CPU0 attaching sched-domain:
[   25.046003]  domain 0: span 00000001
[   25.046005]   groups: 00000001
[   25.046221] net_namespace: 64 bytes
[   25.046717] Time: 16:50:13  Date: 01/28/08
[   25.046749] NET: Registered protocol family 16
[   25.046994] ACPI: bus type pci registered
[   25.082395] PCI: PCI BIOS revision 2.10 entry at 0xfb4c0, last bus=2
[   25.082398] PCI: Using configuration type 1
[   25.082400] Setting up standard PCI resources
[   25.090219] ACPI: EC: Look up EC in DSDT
[   25.096032] ACPI: Interpreter enabled
[   25.096036] ACPI: (supports S0 S1 S4 S5)
[   25.096050] ACPI: Using IOAPIC for interrupt routing
[   25.106449] ACPI: PCI Root Bridge [PCI0] (0000:00)
[   25.106527] PCI: nForce2 C1 Halt Disconnect fixup
[   25.107549] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[   25.107727] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
[   25.107996] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
[   25.163644] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[   25.163843] ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[   25.164039] ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[   25.164230] ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[   25.164420] ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   25.164612] ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[   25.164811] ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 10 11 *12 14 15)
[   25.165008] ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 11 *12 14 15)
[   25.165200] ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   25.165392] ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 6 7 10 11 *12 14 15)
[   25.165586] ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   25.165778] ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   25.165977] ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[   25.166171] ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   25.166362] ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   25.166553] ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[   25.166714] ACPI: PCI Interrupt Link [APC1] (IRQs *16)
[   25.166865] ACPI: PCI Interrupt Link [APC2] (IRQs *17)
[   25.167015] ACPI: PCI Interrupt Link [APC3] (IRQs *18)
[   25.167162] ACPI: PCI Interrupt Link [APC4] (IRQs *19)
[   25.167316] ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
[   25.167526] ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0
[   25.167736] ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22) *0
[   25.167953] ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0
[   25.168163] ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22) *0, disabled.
[   25.168373] ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22) *0
[   25.168581] ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22) *0, disabled.
[   25.168731] ACPI: PCI Interrupt Link [APCS] (IRQs *23), disabled.
[   25.168945] ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22) *0
[   25.169154] ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0, disabled.
[   25.169363] ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22) *0, disabled.
[   25.169572] ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22) *0, disabled.
[   25.169732] ACPI: Power Resource [ISAV] (on)
[   25.169789] Linux Plug and Play Support v0.97 (c) Adam Belay
[   25.169831] pnp: PnP ACPI init
[   25.169840] ACPI: bus type pnp registered
[   25.175979] pnp: PnP ACPI: found 16 devices
[   25.175981] ACPI: ACPI bus type pnp unregistered
[   25.176170] usbcore: registered new interface driver usbfs
[   25.176242] usbcore: registered new interface driver hub
[   25.176292] usbcore: registered new device driver usb
[   25.176405] PCI: Using ACPI for IRQ routing
[   25.176409] PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
[   25.226746] NetLabel: Initializing
[   25.226748] NetLabel:  domain hash size = 128
[   25.226750] NetLabel:  protocols = UNLABELED CIPSOv4
[   25.226762] NetLabel:  unlabeled traffic allowed by default
[   25.227736] Time: tsc clocksource has been installed.
[   25.229773] system 00:00: ioport range 0x4000-0x407f has been reserved
[   25.229777] system 00:00: ioport range 0x4080-0x40ff has been reserved
[   25.229780] system 00:00: ioport range 0x4400-0x447f has been reserved
[   25.229783] system 00:00: ioport range 0x4480-0x44ff has been reserved
[   25.229786] system 00:00: ioport range 0x4200-0x427f has been reserved
[   25.229788] system 00:00: ioport range 0x4280-0x42ff has been reserved
[   25.229795] system 00:01: ioport range 0x5000-0x503f has been reserved
[   25.229798] system 00:01: ioport range 0x5100-0x513f has been reserved
[   25.229804] system 00:02: iomem range 0xda800-0xdbfff has been reserved
[   25.229807] system 00:02: iomem range 0xf0000-0xf7fff could not be reserved
[   25.229812] system 00:02: iomem range 0xf8000-0xfbfff could not be reserved
[   25.229815] system 00:02: iomem range 0xfc000-0xfffff could not be reserved
[   25.229818] system 00:02: iomem range 0x3fff0000-0x3fffffff could not be reserved
[   25.229822] system 00:02: iomem range 0xffff0000-0xffffffff could not be reserved
[   25.229825] system 00:02: iomem range 0x0-0x9ffff could not be reserved
[   25.229828] system 00:02: iomem range 0x100000-0x3ffeffff could not be reserved
[   25.229831] system 00:02: iomem range 0xfec00000-0xfec00fff could not be reserved
[   25.229834] system 00:02: iomem range 0xfee00000-0xfee00fff could not be reserved
[   25.229840] system 00:04: ioport range 0xb78-0xb7b has been reserved
[   25.229843] system 00:04: ioport range 0xf78-0xf7b has been reserved
[   25.229845] system 00:04: ioport range 0xa78-0xa7b has been reserved
[   25.229848] system 00:04: ioport range 0xe78-0xe7b has been reserved
[   25.229851] system 00:04: ioport range 0xbbc-0xbbf has been reserved
[   25.229854] system 00:04: ioport range 0xfbc-0xfbf has been reserved
[   25.229856] system 00:04: ioport range 0x4d0-0x4d1 has been reserved
[   25.229859] system 00:04: ioport range 0x294-0x297 has been reserved
[   25.260349] PCI: Bridge: 0000:00:08.0
[   25.260352]   IO window: 9000-afff
[   25.260357]   MEM window: e3000000-e6ffffff
[   25.260361]   PREFETCH window: 50000000-500fffff
[   25.260366] PCI: Bridge: 0000:00:1e.0
[   25.260368]   IO window: disabled.
[   25.260372]   MEM window: e0000000-e2ffffff
[   25.260375]   PREFETCH window: d0000000-dfffffff
[   25.260385] PCI: Setting latency timer of device 0000:00:08.0 to 64
[   25.260402] NET: Registered protocol family 2
[   25.269888] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[   25.270255] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[   25.271729] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[   25.272478] TCP: Hash tables configured (established 131072 bind 65536)
[   25.272481] TCP reno registered
[   25.274871] checking if image is initramfs... it is
[   25.557129] Freeing initrd memory: 3630k freed
[   25.557552] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[   25.557555] apm: overridden by ACPI.
[   25.557974] audit: initializing netlink socket (disabled)
[   25.557991] audit(1201539012.570:1): initialized
[   25.558127] highmem bounce pool size: 64 pages
[   25.558131] Total HugeTLB memory allocated, 0
[   25.560861] SELinux:  Registering netfilter hooks
[   25.560998] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[   25.561002] io scheduler noop registered
[   25.561004] io scheduler anticipatory registered
[   25.561007] io scheduler deadline registered
[   25.561018] io scheduler cfq registered (default)
[   25.582401] Boot video device is 0000:02:00.0
[   25.587554] ACPI: Thermal Zone [THRM] (52 C)
[   25.587569] isapnp: Scanning for PnP cards...
[   25.760206] Switched to high resolution mode on CPU 0
[   25.944487] isapnp: No Plug & Play device found
[   25.947347] Real Time Clock Driver v1.12ac
[   25.947500] Non-volatile memory driver v1.2
[   25.947503] Linux agpgart interface v0.102
[   25.947560] agpgart: Detected NVIDIA nForce2 chipset
[   25.963439] agpgart: AGP aperture is 256M @ 0xc0000000
[   25.963465] Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
[   25.963614] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[   25.963753] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[   25.964066] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[   25.964249] 00:0b: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[   25.965135] RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
[   25.965395] PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[   25.965399] PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[   25.965772] serio: i8042 KBD port at 0x60,0x64 irq 1
[   25.965847] mice: PS/2 mouse device common for all mice
[   25.986718] input: AT Translated Set 2 keyboard as /class/input/input0
[   25.989187] EDAC MC: Ver: 2.1.0 Jan 24 2008
[   25.989315] cpuidle: using governor ladder
[   25.989317] cpuidle: using governor menu
[   25.989396] usbcore: registered new interface driver hiddev
[   25.989433] usbcore: registered new interface driver usbhid
[   25.989437] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[   25.989511] TCP cubic registered
[   25.989513] Initializing XFRM netlink socket
[   25.989589] NET: Registered protocol family 1
[   25.989605] NET: Registered protocol family 17
[   25.989612] Using IPI No-Shortcut mode
[   25.989626] registered taskstats version 1
[   25.989754]   Magic number: 8:557:844
[   25.990071] Freeing unused kernel memory: 240k freed
[   25.990110] Write protecting the kernel text: 1952k
[   25.990123] Write protecting the kernel read-only data: 772k
[   26.282400] ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
[   26.282409] ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [APCL] -> GSI 22 (level, high) -> IRQ 16
[   26.282422] PCI: Setting latency timer of device 0000:00:02.2 to 64
[   26.282425] ehci_hcd 0000:00:02.2: EHCI Host Controller
[   26.282518] ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
[   26.282557] ehci_hcd 0000:00:02.2: debug port 1
[   26.282563] PCI: cache line size of 64 is not supported by device 0000:00:02.2
[   26.282574] ehci_hcd 0000:00:02.2: irq 16, io mem 0xe7005000
[   26.287965] ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[   26.288090] usb usb1: configuration #1 chosen from 1 choice
[   26.288118] hub 1-0:1.0: USB hub found
[   26.288129] hub 1-0:1.0: 6 ports detected
[   26.394914] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
[   26.395326] ACPI: PCI Interrupt Link [APCF] enabled at IRQ 21
[   26.395334] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 21 (level, high) -> IRQ 17
[   26.395348] PCI: Setting latency timer of device 0000:00:02.0 to 64
[   26.395352] ohci_hcd 0000:00:02.0: OHCI Host Controller
[   26.395426] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
[   26.395444] ohci_hcd 0000:00:02.0: irq 17, io mem 0xe7003000
[   26.447950] usb usb2: configuration #1 chosen from 1 choice
[   26.447977] hub 2-0:1.0: USB hub found
[   26.447989] hub 2-0:1.0: 3 ports detected
[   26.549147] ACPI: PCI Interrupt Link [APCG] enabled at IRQ 20
[   26.549151] ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCG] -> GSI 20 (level, high) -> IRQ 18
[   26.549159] PCI: Setting latency timer of device 0000:00:02.1 to 64
[   26.549163] ohci_hcd 0000:00:02.1: OHCI Host Controller
[   26.549217] ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3
[   26.549230] ohci_hcd 0000:00:02.1: irq 18, io mem 0xe7004000
[   26.594755] usb 1-1: new high speed USB device using ehci_hcd and address 2
[   26.601832] usb usb3: configuration #1 chosen from 1 choice
[   26.601856] hub 3-0:1.0: USB hub found
[   26.601866] hub 3-0:1.0: 3 ports detected
[   26.708712] USB Universal Host Controller Interface driver v3.0
[   26.709142] usb 1-1: configuration #1 chosen from 1 choice
[   26.709206] hub 1-1:1.0: USB hub found
[   26.709309] hub 1-1:1.0: 4 ports detected
[   26.767866] SCSI subsystem initialized
[   26.786664] Driver 'sd' needs updating - please use bus_type methods
[   26.804629] libata version 3.00 loaded.
[   26.810772] pata_amd 0000:00:09.0: version 0.3.10
[   26.810934] PCI: Setting latency timer of device 0000:00:09.0 to 64
[   26.811069] scsi0 : pata_amd
[   26.816599] scsi1 : pata_amd
[   26.817343] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
[   26.817347] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
[   26.972040] ata1.00: ATA-6: WDC WD2000JB-00EVA0, 15.05R15, max UDMA/100
[   26.972044] ata1.00: 390721968 sectors, multi 16: LBA48 
[   26.978917] ata1.00: configured for UDMA/100
[   27.302587] ata2.00: ATAPI: LITE-ON DVDRW SHM-165H6S, HS06, max UDMA/66
[   27.346091] ata2.01: ATA-7: MAXTOR STM3320620A, 3.AAE, max UDMA/100
[   27.346094] ata2.01: 625142448 sectors, multi 16: LBA48 
[   27.346103] ata2.00: limited to UDMA/33 due to 40-wire cable
[   27.519360] ata2.00: configured for UDMA/33
[   27.554043] ata2.01: configured for UDMA/100
[   27.554146] scsi 0:0:0:0: Direct-Access     ATA      WDC WD2000JB-00E 15.0 PQ: 0 ANSI: 5
[   27.554222] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[   27.554236] sd 0:0:0:0: [sda] Write Protect is off
[   27.554239] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   27.554259] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   27.554310] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[   27.554321] sd 0:0:0:0: [sda] Write Protect is off
[   27.554324] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   27.554343] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   27.554347]  sda: sda1 sda2
[   27.576777] sd 0:0:0:0: [sda] Attached SCSI disk
[   27.577661] scsi 1:0:0:0: CD-ROM            LITE-ON  DVDRW SHM-165H6S HS06 PQ: 0 ANSI: 5
[   27.577772] scsi 1:0:1:0: Direct-Access     ATA      MAXTOR STM332062 3.AA PQ: 0 ANSI: 5
[   27.577837] sd 1:0:1:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
[   27.577849] sd 1:0:1:0: [sdb] Write Protect is off
[   27.577852] sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[   27.577871] sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   27.577920] sd 1:0:1:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
[   27.577932] sd 1:0:1:0: [sdb] Write Protect is off
[   27.577934] sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[   27.577953] sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   27.577956]  sdb:<6>usb 2-2: new full speed USB device using ohci_hcd and address 2
[   27.601964]  sdb1 sdb2 sdb3
[   27.602376] sd 1:0:1:0: [sdb] Attached SCSI disk
[   27.744716] usb 2-2: configuration #1 chosen from 1 choice
[   27.963802] usb 2-3: new low speed USB device using ohci_hcd and address 3
[   28.127327] usb 2-3: configuration #1 chosen from 1 choice
[   28.142509] input: Chicony Saitek Eclipse II Keyboard as /class/input/input1
[   28.146698] input,hidraw0: USB HID v1.11 Keyboard [Chicony Saitek Eclipse II Keyboard] on usb-0000:00:02.0-3
[   28.175283] input: Chicony Saitek Eclipse II Keyboard as /class/input/input2
[   28.178705] input,hiddev96,hidraw1: USB HID v1.11 Device [Chicony Saitek Eclipse II Keyboard] on usb-0000:00:02.0-3
[   28.395503] usb 3-3: new full speed USB device using ohci_hcd and address 2
[   28.530990] usb 3-3: configuration #1 chosen from 1 choice
[   28.533944] hub 3-3:1.0: USB hub found
[   28.536917] hub 3-3:1.0: 4 ports detected
[   28.832282] usb 1-1.1: new low speed USB device using ehci_hcd and address 6
[   29.020294] usb 1-1.1: configuration #1 chosen from 1 choice
[   29.782033] hiddev97hidraw2: USB HID v1.11 Device [Belkin  Belkin UPS] on usb-0000:00:02.2-1.1
[   29.959457] usb 1-1.2: new full speed USB device using ehci_hcd and address 7
[   30.052190] usb 1-1.2: configuration #1 chosen from 1 choice
[   30.128397] device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com
[   30.152335] sata_sil 0000:01:0a.0: version 2.3
[   30.152614] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
[   30.152622] ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC1] -> GSI 16 (level, high) -> IRQ 19
[   30.158281] scsi2 : sata_sil
[   30.158336] scsi3 : sata_sil
[   30.158370] ata3: SATA max UDMA/100 mmio m512@0xe6004000 tf 0xe6004080 irq 19
[   30.158375] ata4: SATA max UDMA/100 mmio m512@0xe6004000 tf 0xe60040c0 irq 19
[   30.233321] usb 1-1.4: new high speed USB device using ehci_hcd and address 8
[   30.318569] usb 1-1.4: configuration #1 chosen from 1 choice
[   30.318637] hub 1-1.4:1.0: USB hub found
[   30.318738] hub 1-1.4:1.0: 4 ports detected
[   30.461079] ata3: SATA link down (SStatus 0 SControl 310)
[   30.608087] usb 1-1.4.3: new low speed USB device using ehci_hcd and address 9
[   30.699939] usb 1-1.4.3: configuration #1 chosen from 1 choice
[   30.704245] input: Logitech USB Receiver as /class/input/input3
[   30.707939] input,hidraw3: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:02.2-1.4.3
[   30.884824] usb 1-1.4.4: new full speed USB device using ehci_hcd and address 10
[   30.914779] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   30.918331] ata4.00: ATA-7: Hitachi HDT725040VLA360, V5COA7EA, max UDMA/133
[   30.918335] ata4.00: 781422768 sectors, multi 16: LBA48 NCQ (depth 0/32)
[   30.924331] ata4.00: configured for UDMA/100
[   30.924446] scsi 3:0:0:0: Direct-Access     ATA      Hitachi HDT72504 V5CO PQ: 0 ANSI: 5
[   30.924527] sd 3:0:0:0: [sdc] 781422768 512-byte hardware sectors (400088 MB)
[   30.924542] sd 3:0:0:0: [sdc] Write Protect is off
[   30.924545] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[   30.924564] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   30.924616] sd 3:0:0:0: [sdc] 781422768 512-byte hardware sectors (400088 MB)
[   30.924628] sd 3:0:0:0: [sdc] Write Protect is off
[   30.924630] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[   30.924649] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   30.924653]  sdc: sdc1
[   30.937391] sd 3:0:0:0: [sdc] Attached SCSI disk
[   30.971195] usb 1-1.4.4: configuration #1 chosen from 1 choice
[   33.938587] EXT3-fs: INFO: recovery required on readonly filesystem.
[   33.938592] EXT3-fs: write access will be enabled during recovery.
[   38.878587] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   38.878643] ata1.00: BMDMA stat 0x65
[   38.878694] ata1.00: cmd c8/00:f8:59:3d:07/00:00:00:00:00/e0 tag 0 dma 126976 in
[   38.878695]          res 51/40:f8:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
[   38.878746] ata1.00: status: { DRDY ERR }
[   38.878792] ata1.00: error: { UNC }
[   38.905598] ata1.00: configured for UDMA/100
[   38.905606] ata1: EH complete
[   40.923221] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   40.923271] ata1.00: BMDMA stat 0x65
[   40.923320] ata1.00: cmd c8/00:f8:59:3d:07/00:00:00:00:00/e0 tag 0 dma 126976 in
[   40.923322]          res 51/40:00:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
[   40.923372] ata1.00: status: { DRDY ERR }
[   40.923495] ata1.00: error: { UNC }
[   40.950180] ata1.00: configured for UDMA/100
[   40.950185] ata1: EH complete
[   42.967882] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   42.968008] ata1.00: BMDMA stat 0x65
[   42.968134] ata1.00: cmd c8/00:f8:59:3d:07/00:00:00:00:00/e0 tag 0 dma 126976 in
[   42.968135]          res 51/40:f8:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
[   42.968340] ata1.00: status: { DRDY ERR }
[   42.968464] ata1.00: error: { UNC }
[   42.979747] ata1.00: configured for UDMA/100
[   42.979752] ata1: EH complete
[   44.995973] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   44.996102] ata1.00: BMDMA stat 0x65
[   44.996227] ata1.00: cmd c8/00:f8:59:3d:07/00:00:00:00:00/e0 tag 0 dma 126976 in
[   44.996229]          res 51/40:f8:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
[   44.996432] ata1.00: status: { DRDY ERR }
[   44.996554] ata1.00: error: { UNC }
[   45.023334] ata1.00: configured for UDMA/100
[   45.023339] ata1: EH complete
[   47.098786] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   47.098913] ata1.00: BMDMA stat 0x65
[   47.099038] ata1.00: cmd c8/00:f8:59:3d:07/00:00:00:00:00/e0 tag 0 dma 126976 in
[   47.099040]          res 51/40:f8:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
[   47.099244] ata1.00: status: { DRDY ERR }
[   47.099366] ata1.00: error: { UNC }
[   47.110882] ata1.00: configured for UDMA/100
[   47.110887] ata1: EH complete
[   49.276447] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   49.276573] ata1.00: BMDMA stat 0x65
[   49.276698] ata1.00: cmd c8/00:f8:59:3d:07/00:00:00:00:00/e0 tag 0 dma 126976 in
[   49.276699]          res 51/40:f8:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
[   49.276903] ata1.00: status: { DRDY ERR }
[   49.277028] ata1.00: error: { UNC }
[   49.288365] ata1.00: configured for UDMA/100
[   49.288377] sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
[   49.288381] sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
[   49.288385] Descriptor sense data with sense descriptors (in hex):
[   49.288387]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
[   49.288393]         00 07 3d 8b 
[   49.288396] sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
[   49.288399] end_request: I/O error, dev sda, sector 474507
[   49.288415] ata1: EH complete
[   49.297395] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[   49.299276] sd 0:0:0:0: [sda] Write Protect is off
[   49.299280] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   49.303585] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   49.306616] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[   49.317409] sd 0:0:0:0: [sda] Write Protect is off
[   49.317412] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   49.320830] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   53.606855] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   53.606989] ata1.00: BMDMA stat 0x65
[   53.607118] ata1.00: cmd c8/00:58:89:3d:07/00:00:00:00:00/e0 tag 0 dma 45056 in
[   53.607120]          res 51/40:58:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
[   53.607324] ata1.00: status: { DRDY ERR }
[   53.607446] ata1.00: error: { UNC }
[   53.634393] ata1.00: configured for UDMA/100
[   53.634401] ata1: EH complete
[   55.651542] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   55.651672] ata1.00: BMDMA stat 0x65
[   55.651797] ata1.00: cmd c8/00:58:89:3d:07/00:00:00:00:00/e0 tag 0 dma 45056 in
[   55.651799]          res 51/40:00:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
[   55.652002] ata1.00: status: { DRDY ERR }
[   55.652125] ata1.00: error: { UNC }
[   55.678936] ata1.00: configured for UDMA/100
[   55.678941] ata1: EH complete
[   57.845829] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   57.845956] ata1.00: BMDMA stat 0x65
[   57.846084] ata1.00: cmd c8/00:58:89:3d:07/00:00:00:00:00/e0 tag 0 dma 45056 in
[   57.846086]          res 51/40:58:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
[   57.846289] ata1.00: status: { DRDY ERR }
[   57.846411] ata1.00: error: { UNC }
[   57.857425] ata1.00: configured for UDMA/100
[   57.857430] ata1: EH complete
[   59.915393] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   59.915521] ata1.00: BMDMA stat 0x65
[   59.915649] ata1.00: cmd c8/00:58:89:3d:07/00:00:00:00:00/e0 tag 0 dma 45056 in
[   59.915650]          res 51/40:58:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
[   59.915854] ata1.00: status: { DRDY ERR }
[   59.915976] ata1.00: error: { UNC }
[   59.926980] ata1.00: configured for UDMA/100
[   59.926985] ata1: EH complete
[   61.993309] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   61.993436] ata1.00: BMDMA stat 0x65
[   61.993561] ata1.00: cmd c8/00:58:89:3d:07/00:00:00:00:00/e0 tag 0 dma 45056 in
[   61.993563]          res 51/40:58:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
[   61.993766] ata1.00: status: { DRDY ERR }
[   61.993888] ata1.00: error: { UNC }
[   62.020550] ata1.00: configured for UDMA/100
[   62.020555] ata1: EH complete
[   64.037975] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[   64.038102] ata1.00: BMDMA stat 0x65
[   64.038227] ata1.00: cmd c8/00:58:89:3d:07/00:00:00:00:00/e0 tag 0 dma 45056 in
[   64.038229]          res 51/40:58:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
[   64.038432] ata1.00: status: { DRDY ERR }
[   64.038555] ata1.00: error: { UNC }
[   64.050125] ata1.00: configured for UDMA/100
[   64.050134] sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
[   64.050138] sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
[   64.050142] Descriptor sense data with sense descriptors (in hex):
[   64.050143]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
[   64.050149]         00 07 3d 8b 
[   64.050152] sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
[   64.050155] end_request: I/O error, dev sda, sector 474507
[   64.050169] ata1: EH complete
[   64.050382] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[   64.050506] sd 0:0:0:0: [sda] Write Protect is off
[   64.050509] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   64.050756] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   64.051049] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
[   64.051173] sd 0:0:0:0: [sda] Write Protect is off
[   64.051176] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   64.051422] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   64.632360] kjournald starting.  Commit interval 5 seconds
[   64.632378] EXT3-fs: dm-0: orphan cleanup on readonly fs
[   64.632385] ext3_orphan_cleanup: deleting unreferenced inode 17303473
[   64.648547] ext3_orphan_cleanup: deleting unreferenced inode 38797436
[   64.707760] ext3_orphan_cleanup: deleting unreferenced inode 37519565
[   64.730253] EXT3-fs: dm-0: 3 orphan inodes deleted
[   64.730255] EXT3-fs: recovery complete.
[   64.816010] EXT3-fs: mounted filesystem with ordered data mode.
[   65.194899] audit(1201539052.235:2): enforcing=1 old_enforcing=0 auid=4294967295
[   65.408684] SELinux:8192 avtab hash slots allocated.Num of rules:213166
[   65.470766] SELinux:8192 avtab hash slots allocated.Num of rules:213166
[   65.534876] security:  8 users, 11 roles, 2363 types, 114 bools, 1 sens, 1024 cats
[   65.534881] security:  67 classes, 213166 rules
[   65.537006] SELinux:  Completing initialization.
[   65.537009] SELinux:  Setting up existing superblocks.
[   65.559377] SELinux: initialized (dev dm-0, type ext3), uses xattr
[   65.720901] SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
[   65.720917] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[   65.721020] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
[   65.721032] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
[   65.721064] SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
[   65.721073] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts
[   65.721079] SELinux: initialized (dev devpts, type devpts), uses transition SIDs
[   65.721090] SELinux: initialized (dev inotifyfs, type inotifyfs), uses genfs_contexts
[   65.721094] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[   65.721102] SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
[   65.721109] SELinux: initialized (dev anon_inodefs, type anon_inodefs), uses genfs_contexts
[   65.721113] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
[   65.721118] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
[   65.721128] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[   65.721140] SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
[   65.721145] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
[   65.721169] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
[   65.725436] SELinux: policy loaded with handle_unknown=allow
[   65.725446] audit(1201539052.766:3): policy loaded auid=4294967295
[   69.515151] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   69.515177] scsi 1:0:0:0: Attached scsi generic sg1 type 5
[   69.515202] sd 1:0:1:0: Attached scsi generic sg2 type 0
[   69.515231] sd 3:0:0:0: Attached scsi generic sg3 type 0
[   70.057084] input: Power Button (FF) as /class/input/input4
[   70.060611] ACPI: Power Button (FF) [PWRF]
[   70.060653] ACPI Error (evxfevnt-0186): Could not enable SleepButton event [20070126]
[   70.060658] ACPI Warning (evxface-0145): Could not enable fixed event 3 [20070126]
[   70.060742] input: Power Button (CM) as /class/input/input5
[   70.064592] ACPI: Power Button (CM) [PWRB]
[   70.064652] input: Sleep Button (CM) as /class/input/input6
[   70.067603] ACPI: Sleep Button (CM) [SLPB]
[   70.385057] usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x04B8 pid 0x0005
[   70.385082] usbcore: registered new interface driver usblp
[   70.412471] i2c-adapter i2c-0: nForce2 SMBus adapter at 0x5000
[   70.412498] i2c-adapter i2c-1: nForce2 SMBus adapter at 0x5100
[   70.450007] usbcore: registered new interface driver usbserial
[   70.450013] drivers/usb/serial/usb-serial.c: USB Serial Driver core
[   70.569319] drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
[   70.569461] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
[   70.569497] drivers/usb/serial/ftdi_sio.c: Detected FT232RL
[   70.569536] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
[   70.569552] usbcore: registered new interface driver ftdi_sio
[   70.569555] drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
[   70.615332] input: PC Speaker as /class/input/input7
[   70.661362] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
[   70.661752] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 22
[   70.661757] ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCH] -> GSI 22 (level, high) -> IRQ 16
[   70.661764] PCI: Setting latency timer of device 0000:00:04.0 to 64
[   70.719617] Floppy drive(s): fd0 is 1.44M
[   70.736319] FDC 0 is a post-1991 82077
[   71.173281] forcedeth 0000:00:04.0: ifname eth0, PHY OUI 0x20 @ 1, addr 00:04:4b:5d:eb:7d
[   71.173286] forcedeth 0000:00:04.0: timirq lnktim desc-v1
[   71.173697] ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
[   71.173705] ACPI: PCI Interrupt 0000:01:09.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 20
[   71.206469] Linux video capture interface: v2.00
[   71.231784] firewire_ohci: Added fw-ohci device 0000:01:09.0, OHCI version 1.10
[   71.475562] nvidia: module license 'NVIDIA' taints kernel.
[   71.733592] firewire_core: created new fw device fw0 (0 config rom retries, S400)
[   71.738694] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 20
[   71.739120] NVRM: loading NVIDIA UNIX x86 Kernel Module  169.07  Thu Dec 13 18:42:56 PST 2007
[   72.053875] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
[   72.053971] cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV [card=22,autodetected]
[   72.053975] cx88[0]: TV tuner type 60, Radio tuner type -1
[   72.093539] cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
[   72.198076] cx88[0]/2: cx2388x 8802 Driver Manager
[   72.200230] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
[   72.200241] ACPI: PCI Interrupt 0000:01:07.2[A] -> Link [APC2] -> GSI 17 (level, high) -> IRQ 21
[   72.200254] cx88[0]/2: found at 0000:01:07.2, rev: 5, irq: 21, latency: 32, mmio: 0xe4000000
[   72.200328] ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC2] -> GSI 17 (level, high) -> IRQ 21
[   72.200340] cx88[0]/0: found at 0000:01:07.0, rev: 5, irq: 21, latency: 32, mmio: 0xe3000000
[   72.379427] tda8290_probe: not probed - driver disabled by Kconfig
[   72.379432] tuner 2-0043: chip found @ 0x86 (cx88[0])
[   72.379457] tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
[   72.379460] tuner 2-0043: type set to tda9887
[   72.381847] tuner 2-0061: chip found @ 0xc2 (cx88[0])
[   72.381866] tuner-simple 2-0061: type set to 60 (Thomson DTT 761X (ATSC/NTSC))
[   72.381869] tuner 2-0061: type set to Thomson DTT 761X (A
[   72.381871] tuner-simple 2-0061: type set to 60 (Thomson DTT 761X (ATSC/NTSC))
[   72.381874] tuner 2-0061: type set to Thomson DTT 761X (A
[   72.394034] cx88[0]/0: registered device video0 [v4l2]
[   72.394059] cx88[0]/0: registered device vbi0
[   72.394083] cx88[0]/0: registered device radio0
[   72.528367] cx88/2: cx2388x dvb driver version 0.0.6 loaded
[   72.528372] cx88/2: registering cx8802 driver, type: dvb access: shared
[   72.528376] cx88[0]/2: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV [card=22]
[   72.528380] cx88[0]/2: cx2388x based DVB/ATSC card
[   72.581302] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
[   72.581312] ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC3] -> GSI 18 (level, high) -> IRQ 22
[   72.586129] Audigy2 value: Special config.
[   72.695526] DVB: registering new adapter (cx88[0])
[   72.695532] DVB: registering frontend 0 (Oren OR51132 VSB/QAM Frontend)...
[   72.769048] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 21
[   72.769054] ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 21 (level, high) -> IRQ 17
[   72.769090] PCI: Setting latency timer of device 0000:00:06.0 to 64
[   73.080499] intel8x0_measure_ac97_clock: measured 50742 usecs
[   73.080504] intel8x0: clocking to 47447
[   75.947132] EXT3 FS on dm-0, internal journal
[   76.213561] kjournald starting.  Commit interval 5 seconds
[   76.220513] EXT3 FS on sda1, internal journal
[   76.220518] EXT3-fs: mounted filesystem with ordered data mode.
[   76.226324] SELinux: initialized (dev sda1, type ext3), uses xattr
[   76.226733] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[   76.231140] kjournald starting.  Commit interval 5 seconds
[   76.238465] EXT3 FS on sdc1, internal journal
[   76.238469] EXT3-fs: mounted filesystem with ordered data mode.
[   76.245352] SELinux: initialized (dev sdc1, type ext3), uses xattr
[   77.211706] Adding 2031608k swap on /dev/mapper/VolGroup00-LogVol01.  Priority:-1 extents:1 across:2031608k
[   77.215361] SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
[   77.624868] warning: process `kudzu' used the deprecated sysctl system call with 1.23.
[   78.115621] NET: Registered protocol family 10
[   78.115859] lo: Disabled Privacy Extensions
[   83.732476] RPC: Registered udp transport module.
[   83.732480] RPC: Registered tcp transport module.
[   83.735747] SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts
[   84.406333] w83627hf: Found W83627HF chip at 0x290
[   84.927130] audit(1201539072.923:4): audit_pid=1915 old=0 by auid=4294967295 subj=system_u:system_r:auditd_t:s0
[   86.877546] SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
[   87.346561] SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
[   87.501848] SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
[   89.296245] eth0: no IPv6 routers present
[  129.766842] agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
[  129.766858] agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
[  129.766929] agpgart: Putting AGP V3 device at 0000:02:00.0 into 8x mode

Re: Problem with ata layer in 2.6.24

[Mark Lord]

> [   64.037975] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> [   64.038102] ata1.00: BMDMA stat 0x65
> [   64.038227] ata1.00: cmd c8/00:58:89:3d:07/00:00:00:00:00/e0 tag 0 dma 45056 in
> [   64.038229]          res 51/40:58:8b:3d:07/00:00:00:00:00/e0 Emask 0x9 (media error)
> [   64.038432] ata1.00: status: { DRDY ERR }
> [   64.038555] ata1.00: error: { UNC }
> [   64.050125] ata1.00: configured for UDMA/100
> [   64.050134] sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
> [   64.050138] sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
> [   64.050142] Descriptor sense data with sense descriptors (in hex):
> [   64.050143]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
> [   64.050149]         00 07 3d 8b 
> [   64.050152] sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
> [   64.050155] end_request: I/O error, dev sda, sector 474507
..

This error looks somewhat different from the samples posted earlier.
This one is quite definitively a "bad sector".

It should also show up in "smartctl -a -data /dev/sda" (near the bottom)
if SMART was enabled on this drive at boot.

You could try reading that specific sector again just to make sure.
One way is to figure out how to use "dd" for this.
Another way is to use the "make_bad_sector" utility that
is included in the source tarball for hdparm-7.7, as follows:

   make_bad_sector --readback /dev/sda 474507

(when invoked as above, it does *not* "make" a bad sector; no worries).

If it reports an I/O error consistently on that, then the sector is
indeed faulty, and it's contents have long been lost.

You can repair the bad sector (but not the original contents) like this:

   make_bad_sector --rewrite /dev/sda 474507

Cheers

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Mark Lord wrote:
>> [   64.037975] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
>> [   64.038102] ata1.00: BMDMA stat 0x65
>> [   64.038227] ata1.00: cmd c8/00:58:89:3d:07/00:00:00:00:00/e0 tag 0 dma
>> 45056 in [   64.038229]          res 51/40:58:8b:3d:07/00:00:00:00:00/e0
>> Emask 0x9 (media error) [   64.038432] ata1.00: status: { DRDY ERR }
>> [   64.038555] ata1.00: error: { UNC }
>> [   64.050125] ata1.00: configured for UDMA/100
>> [   64.050134] sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
>> [   64.050138] sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
>> [   64.050142] Descriptor sense data with sense descriptors (in hex):
>> [   64.050143]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
>> [   64.050149]         00 07 3d 8b
>> [   64.050152] sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4
>> [   64.050155] end_request: I/O error, dev sda, sector 474507
>
>..
>
>This error looks somewhat different from the samples posted earlier.
>This one is quite definitively a "bad sector".
>
>It should also show up in "smartctl -a -data /dev/sda" (near the bottom)
>if SMART was enabled on this drive at boot.
>
It does not unforch.

>You could try reading that specific sector again just to make sure.
>One way is to figure out how to use "dd" for this.
[root@coyote ~]# dd if=/dev/sda bs=512 skip=474506 count=3
��▒6
{�G���G���libkdecorations.so.1.0.0��c�®���J{�G���G���libkfontinst.so.0.0.0��c�®����"ʂ�GP�~GJ3G 
6�7�8�#��z;����{�G���G���libkhotkeys_shared.so.1.0.0��c�®���N{�G���G���libkickermain.so.1.0.0��c�®���Y{�G���G���libkonq.so.4.2.0��c�®���Z{�G���G���libkonqsidebarplugin.so.1.2.0��c�®���d{�G���G���libksgrd.so.1.2.0��c�®����▒��G7 
G▒�=G▒]��^���▒?����e{�G���G���libksplashthemes.so.0.0.0��c�®����{�G���G���libtaskbar.so.1.2.0��c�®����{�G���G���libtaskmanager.so.1.0.0��c�®�3+0 
records in
3+0 records out
1536 bytes (1.5 kB) copied, 6.1403e-05 s, 25.0 MB/s

>Another way is to use the "make_bad_sector" utility that
>is included in the source tarball for hdparm-7.7, as follows:
>
>   make_bad_sector --readback /dev/sda 474507
>
Apparently not in the rpm, darnit.

>(when invoked as above, it does *not* "make" a bad sector; no worries).
>
>If it reports an I/O error consistently on that, then the sector is
>indeed faulty, and it's contents have long been lost.
>
>You can repair the bad sector (but not the original contents) like this:
>
>   make_bad_sector --rewrite /dev/sda 474507
>
>Cheers

I'm going up to Clarksburg this afternoon to see if I can find a couple of 
drives, one a 2.5" bigger than 40Gb for my 2.5" maxtor usb housing, and 
another pata drive big enough to run this thing & just re-install the 
December respin after I save as much of this as I can, there's nearly 50GB 
here now.

Maybe it won't be so fscking picky about the next drive.

I was hoping someone could look at that last dmseg I attached, but apparently 
everybody is blinded by unrelated details as that bad sector may have been 
transient, caused by the multiple hardware reset type reboots so far today :(

The last 3 reboots have interrupted a 'smartctl -t long /dev/sda' in 
progress. :(

If I reconvert to non libata, can I do that only for the pata drives of which 
there are 3 here including the dvd writer, and still use libata for the lone 
sata drive left?

And can I do that without mucking with the device map, which will make 
amanda/tar attempt to do a level 0 on the whole system if its changed.  I see 
the drives are at 254 again, when are they going to be given a stable device 
address out of the LANANA experimental group so we can reboot without mucking 
with that and driving tar crazy?

Thanks everybody.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
I just had my entire INTESTINAL TRACT coated with TEFLON!

Re: Problem with ata layer in 2.6.24

[Mark Lord]

Gene Heskett wrote:
> On Monday 28 January 2008, Mark Lord wrote:
>..
>> Another way is to use the "make_bad_sector" utility that
>> is included in the source tarball for hdparm-7.7, as follows:
>>
>>   make_bad_sector --readback /dev/sda 474507
>>
> Apparently not in the rpm, darnit.
..

That's okay.  It should still be in the SRPM source file.
And it's a tiny download from sourceforge.net:

http://sourceforge.net/search/?type_of_search=soft&type_of_search=soft&words=hdparm

Cheers

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Mark Lord wrote:
>Gene Heskett wrote:
>> On Monday 28 January 2008, Mark Lord wrote:
>>..
>>
>>> Another way is to use the "make_bad_sector" utility that
>>> is included in the source tarball for hdparm-7.7, as follows:
>>>
>>>   make_bad_sector --readback /dev/sda 474507
>>
>> Apparently not in the rpm, darnit.
>
>..
>
>That's okay.  It should still be in the SRPM source file.
>And it's a tiny download from sourceforge.net:
>
>http://sourceforge.net/search/?type_of_search=soft&type_of_search=soft&words
>=hdparm
>
>Cheers

That's ok, dd seemed to do the job also.

Thanks Mark.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Those who do not understand Unix are condemned to reinvent it, poorly.
		-- Henry Spencer

Re: Problem with ata layer in 2.6.24

[Mark Lord]

Gene Heskett wrote:
..
> That's ok, dd seemed to do the job also.
..

The two programs operate entirely differently from each other,
so it may still be worth trying the make_bad_sector utility there.

dd goes through the regular kernel I/O calls,
whereas make_bad_sector sends raw ATA commands
directly (more or less) to the drive.

-ml

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Mark Lord wrote:
>Gene Heskett wrote:
>..
>
>> That's ok, dd seemed to do the job also.
>
>..
>
>The two programs operate entirely differently from each other,
>so it may still be worth trying the make_bad_sector utility there.
>
>dd goes through the regular kernel I/O calls,
>whereas make_bad_sector sends raw ATA commands
>directly (more or less) to the drive.
>
Humm, if it (the sector error) continues.  I'm rather convinced that was a one 
time transient item caused by doing so many hardware resets.  It has not 
repeated in subsequent stanzas of this error.  Several times it went away 
while the drives long self test was in progress, and the resets that go with 
the reboot, or one of these errors seems to stop the long test, which from my 
reading, should resume with no delay, but maybe that only applies to a 
powerdown restart, which I haven't been doing.  The last such error was about 
11 hours ago now. I just started another long test, which if ok, should clear 
the stuff its showing now because the test was interrupted.  It has passed 
that test twice before in the last 36 hours.

Thanks Mark.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
You are a fluke of the universe; you have no right to be here.

Re: Problem with ata layer in 2.6.24

[Dave Neuer]

On Jan 28, 2008 11:35 AM, Gene Heskett <gene.heskett@gmail.com> wrote:
>
> On Monday 28 January 2008, Mikael Pettersson wrote:
> >
> >We have no way of debugging that module, so please try 2.6.24 without it.
>
> Sorry, I can't do this and have a working machine.  The nv driver has suffered
> bit rot or something since the FC2 days when it COULD run a 19" crt at
> 1600x1200, and will not drive this 20" wide screen lcd 1680x1050 monitor at
> more than 800x600, which is absolutely butt ugly fuzzy, looking like a jpg
> compressed to 10%.  The system is not usable on a day to basis without the
> nvidia driver.

I only have a 15.4" laptop screen, but it does 1650 x 1050 -- the
default w/ my Fedora 8 install -- with the nv driver no problem (I
change it because I have normal human eyesight rather than superhero
micro-vision).

>
> Fix the nv driver so it will run this screen at its native resolution and I'll
> be glad to run it even if it won't run google earth...

<snip>

>  Again, fix the nv driver so it will run my screen & I'll be glad
> to switch.

Wow, 2 separate demands to a Linux-IDE developer to fix an X driver
for you. Pretty sure that the source is available to you as well.

>
> >If the problems persist, please try to capture a complete log from the
> >failing kernel -- the interesting bits are everything from initial boot
> >up to and including the first few errors. You may need to increase the
> >kernel's log buffer size if the log gets truncated (CONFIG_LOG_BUF_SHIFT).
>
> If by log you mean /var/log/messages, I have several megabytes of those.
> If you mean a live dmesg capture taken right now, its attached. It contains
> several of these at the bottom.  I long ago made the kernel log buffer
> bigger, cuz it couldn't even show the start immediately after the boot, and
> even the dump to syslog was truncated.
>
> >There are no pata_amd changes from 2.6.24-rc7 to 2.6.24 final.
>
> That is what I was afraid of.  I've done some limited grepping in that branch
> of the kernel tree, and cannot seem to locate where this EH handler is being
> invoked from.
>
> There is 2 lines of interest in the dmesg:
>
> [    0.000000] Nvidia board detected. Ignoring ACPI timer override.
> [    0.000000] If you got timer trouble try acpi_use_timer_override
>
> But I have NDI what it means, kernel argument/xconfig option?

My own 15 seconds of googling informs me that it's a kernel
command-line option: put it on the command-line as-is.

>
> I've also done some googling, and it appears this problem is fairly widespread
> since the switchover to libata was encouraged.  A stock fedora F8 kernel
> suffers the same freezes and eventually locks up, but does it without the
> error messages being logged, it just freezes, feeling identical to this in
> the minutes before the total freeze.  I've tried 2 of those too, but the
> newest one won't even run X.

As I said, I run F8 w/ nv on my amd64 laptop, so I'm not sure what you
mean by the "won't even run X" part there.

Dave

Re: Problem with ata layer in 2.6.24

[Kasper Sandberg]

On Mon, 2008-01-28 at 11:35 -0500, Gene Heskett wrote:
> On Monday 28 January 2008, Mikael Pettersson wrote:
> >Gene Heskett writes:
> > > On Monday 28 January 2008, Peter Zijlstra wrote:
> > > >On Mon, 2008-01-28 at 09:17 +0100, Mikael Pettersson wrote:
> > > >> 1. Wrong mailing list; use linux-ide (@vger) instead.
> > > >
> > > >What, and keep all us other interested people in the dark?
> > >
> > > As a test, I tried rebooting to the latest fedora kernel and found it
> > > kills X, so I'm back to the second to last fedora version ATM, and the
> > > third 'smartctl -t lng /dev/sda' in 24 hours is running now.  The first
> > > two completed with no errors.
> > >
> > > I've added the linux-ide list to refresh those people of the problem,
> > > the logs are being spammed by this message stanza:
> > >
> > >  Jan 28 04:46:25 coyote kernel: [26550.290016] ata1.00: exception Emask
> > > 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Jan 28 04:46:25 coyote kernel:
> > > [26550.290028] ata1.00: cmd 35/00:58:c9:9c:0a/00:01:00:00:00/e0 tag 0 dma
> > > 176128 out Jan 28 04:46:25 coyote kernel: [26550.290029]          res
> > > 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 28 04:46:25
> > > coyote kernel: [26550.290032] ata1.00: status: { DRDY } Jan 28 04:46:25
> > > coyote kernel: [26550.290060] ata1: soft resetting link Jan 28 04:46:25
> > > coyote kernel: [26550.452301] ata1.00: configured for UDMA/100 Jan 28
> > > 04:46:25 coyote kernel: [26550.452318] ata1: EH complete
> > > Jan 28 04:46:25 coyote kernel: [26550.455898] sd 0:0:0:0: [sda] 390721968
> > > 512-byte hardware sectors (200050 MB) Jan 28 04:46:25 coyote kernel:
> > > [26550.456151] sd 0:0:0:0: [sda] Write Protect is off Jan 28 04:46:25
> > > coyote kernel: [26550.456403] sd 0:0:0:0: [sda] Write cache: enabled,
> > > read cache: enabled, doesn't support DPO or FUA
> >
> >It's not obvious from this incomplete dmesg log what HW or driver
> >is behind ata1, but if the 2.6.24-rc7 kernel matches the 2.6.24 one,
> >
> >it should be pata_amd driving a WDC disk:
> > > [   30.702887] pata_amd 0000:00:09.0: version 0.3.10
> > > [   30.703052] PCI: Setting latency timer of device 0000:00:09.0 to 64
> > > [   30.703188] scsi0 : pata_amd
> > > [   30.709313] scsi1 : pata_amd
> > > [   30.710076] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000
> > > irq 14 [   30.710079] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma
> > > 0xf008 irq 15 [   30.864753] ata1.00: ATA-6: WDC WD2000JB-00EVA0,
> > > 15.05R15, max UDMA/100 [   30.864756] ata1.00: 390721968 sectors, multi
> > > 16: LBA48
> > > [   30.871629] ata1.00: configured for UDMA/100
> >
> >Unfortunately we also see:
> > > [   48.285456] nvidia: module license 'NVIDIA' taints kernel.
> > > [   48.549725] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI
> > > 19 (level, high) -> IRQ 20 [   48.550149] NVRM: loading NVIDIA UNIX x86
> > > Kernel Module  169.07  Thu Dec 13 18:42:56 PST 2007
> >
> >We have no way of debugging that module, so please try 2.6.24 without it.
> 
> Sorry, I can't do this and have a working machine.  The nv driver has suffered 
> bit rot or something since the FC2 days when it COULD run a 19" crt at 
> 1600x1200, and will not drive this 20" wide screen lcd 1680x1050 monitor at 
> more than 800x600, which is absolutely butt ugly fuzzy, looking like a jpg 
> compressed to 10%.  The system is not usable on a day to basis without the 
> nvidia driver.
> 
> Fix the nv driver so it will run this screen at its native resolution and I'll 
> be glad to run it even if it won't run google earth, which I do use from time 
> to time.  Now, if in all the hits you can get from google on this, currently 
> 14,800 just for 'exception Emask', apparently caused by a timeout, if 100% of 
> the complainers are running nvidia drivers also, then I see a legit 
I can invalidate this theory...
i helped a guy on irc debug this problem, and he had ati. I tried having
him stop using fglrx, and go to r300.. same problem, and same problem
even with vesa.. :)

also, i have this on my fileserver with .20, which doesent even run X,
or module support in kernel :)

> complaint.  Again, fix the nv driver so it will run my screen & I'll be glad 
> to switch.  I can see the reason, sure, but the machine must be capable of 
> doing its common day to day stuff, while using that driver, like running kde 
> for kmail, and browsers that work.
> 
> >If the problems persist, please try to capture a complete log from the
> >failing kernel -- the interesting bits are everything from initial boot
> >up to and including the first few errors. You may need to increase the
> >kernel's log buffer size if the log gets truncated (CONFIG_LOG_BUF_SHIFT).
> 
> If by log you mean /var/log/messages, I have several megabytes of those.
> If you mean a live dmesg capture taken right now, its attached. It contains 
> several of these at the bottom.  I long ago made the kernel log buffer 
> bigger, cuz it couldn't even show the start immediately after the boot, and 
> even the dump to syslog was truncated.
> 
> >There are no pata_amd changes from 2.6.24-rc7 to 2.6.24 final.
> 
> That is what I was afraid of.  I've done some limited grepping in that branch 
> of the kernel tree, and cannot seem to locate where this EH handler is being 
> invoked from.
> 
> There is 2 lines of interest in the dmesg:
> 
> [    0.000000] Nvidia board detected. Ignoring ACPI timer override.
> [    0.000000] If you got timer trouble try acpi_use_timer_override
> 
> But I have NDI what it means, kernel argument/xconfig option?
> 
> I've also done some googling, and it appears this problem is fairly widespread 
> since the switchover to libata was encouraged.  A stock fedora F8 kernel 
> suffers the same freezes and eventually locks up, but does it without the 
> error messages being logged, it just freezes, feeling identical to this in 
> the minutes before the total freeze.  I've tried 2 of those too, but the 
> newest one won't even run X.
> 

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Kasper Sandberg wrote:
 [...]
>> >We have no way of debugging that module, so please try 2.6.24 without it.
>>
>> Sorry, I can't do this and have a working machine.  The nv driver has
>> suffered bit rot or something since the FC2 days when it COULD run a 19"
>> crt at 1600x1200, and will not drive this 20" wide screen lcd 1680x1050
>> monitor at more than 800x600, which is absolutely butt ugly fuzzy, looking
>> like a jpg compressed to 10%.  The system is not usable on a day to basis
>> without the nvidia driver.
>>
>> Fix the nv driver so it will run this screen at its native resolution and
>> I'll be glad to run it even if it won't run google earth, which I do use
>> from time to time.  Now, if in all the hits you can get from google on
>> this, currently 14,800 just for 'exception Emask', apparently caused by a
>> timeout, if 100% of the complainers are running nvidia drivers also, then
>> I see a legit
>
>I can invalidate this theory...
>i helped a guy on irc debug this problem, and he had ati. I tried having
>him stop using fglrx, and go to r300.. same problem, and same problem
>even with vesa.. :)
>
No Kasper, you are validating it, that it is not nvidia related, which is what 
I was also saying.

>also, i have this on my fileserver with .20, which doesent even run X,
>or module support in kernel :)

That far back?  Although ISTR I saw it happen once only when I was running 
2.6.18-somethingorother.

>> complaint.  Again, fix the nv driver so it will run my screen & I'll be
>> glad to switch.  I can see the reason, sure, but the machine must be
>> capable of doing its common day to day stuff, while using that driver,
>> like running kde for kmail, and browsers that work.
>>
>> >If the problems persist, please try to capture a complete log from the
>> >failing kernel -- the interesting bits are everything from initial boot
>> >up to and including the first few errors. You may need to increase the
>> >kernel's log buffer size if the log gets truncated
>> > (CONFIG_LOG_BUF_SHIFT).
>>
>> If by log you mean /var/log/messages, I have several megabytes of those.
>> If you mean a live dmesg capture taken right now, its attached. It
>> contains several of these at the bottom.  I long ago made the kernel log
>> buffer bigger, cuz it couldn't even show the start immediately after the
>> boot, and even the dump to syslog was truncated.
>>
>> >There are no pata_amd changes from 2.6.24-rc7 to 2.6.24 final.
>>
>> That is what I was afraid of.  I've done some limited grepping in that
>> branch of the kernel tree, and cannot seem to locate where this EH handler
>> is being invoked from.
>>
>> There is 2 lines of interest in the dmesg:
>>
>> [    0.000000] Nvidia board detected. Ignoring ACPI timer override.
>> [    0.000000] If you got timer trouble try acpi_use_timer_override
>>
>> But I have NDI what it means, kernel argument/xconfig option?
>>
>> I've also done some googling, and it appears this problem is fairly
>> widespread since the switchover to libata was encouraged.  A stock fedora
>> F8 kernel suffers the same freezes and eventually locks up, but does it
>> without the error messages being logged, it just freezes, feeling
>> identical to this in the minutes before the total freeze.  I've tried 2 of
>> those too, but the newest one won't even run X.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
bureaucrat, n:
	A politician who has tenure.

Re: Problem with ata layer in 2.6.24

[Kasper Sandberg]

On Mon, 2008-01-28 at 23:49 -0500, Gene Heskett wrote:
> On Monday 28 January 2008, Kasper Sandberg wrote:
>  [...]
<snip>
> >
> >I can invalidate this theory...
> >i helped a guy on irc debug this problem, and he had ati. I tried having
> >him stop using fglrx, and go to r300.. same problem, and same problem
> >even with vesa.. :)
> >
> No Kasper, you are validating it, that it is not nvidia related, which is what 
> I was also saying.
yeah thats what i mean - i can invalidate the theory that all the
affected boxes run nvidia.

> 
> >also, i have this on my fileserver with .20, which doesent even run X,
> >or module support in kernel :)
> 
> That far back?  Although ISTR I saw it happen once only when I was running 
> 2.6.18-somethingorother.

Yes im afraid so.. i will now provide some complete details, as i feel
they are relevant.

the thing is, i run 6x300gb disks, IDE, in raid5.

i have both an onboard via ide controller, and then i bought a promise
pdc 202 new thingie. i had problem however..

after a bit of time, i would get DMA reset error thing, and it all
kindof went NUTS. it was as if all data access were skewed, and as you
might imagine, this made everything fail badly.

i purchased an ITE based controller for the drives on the promise, but
exactly the same thing happened.

the errors i got was:
hdf: dma_intr: bad DMA status (dma_stat=75)
hdf: dma_intr: status=0x50 { DriveReady SeekComplete }
ide: failed opcode was: unknown
---

i then found new hope, when i heard that libata provided much better
error handling, so i upgraded to .20.

this made my box usable.

the error happens once or twice a day, the disk led will turn on
constantly, and all IO freezes for about half a minute, where it returns
PROPERLY(thank you libata!). as far as i can tell, the only side effect
is that i get those messages like described here, and flooded with on
google.

to put some timeline perspective into this.
i believe it was in 2005 i assembled the system, and when i realized it
was faulty, on old ide driver, i stopped using it - that miht have been
in beginning of 2006. then for almost a year i werent using it, hoping
to somehow fix it, but in january 2007 i think it was, atleast in the
very beginning of 2007, i hit upon the idea of trying libata, and ever
since the system has been running 24/7 - doing these errors around 2
times a day.

i have multiple times reported my problems to lkml, but nothing has
happened, i also tried to aproeach jgarzik direcly, but he was not
interested.

i really hope this can be solved now, its a huge problem

my fileserver has an asus k8v motherboard, with via chipset (k8t880 i
think it is, or something like it). currently using the promise
controller again(strangely enough all the timeouts seems to happen here,
and when the ITE was on, there, not the onboard one), in conjunction
with the onboard via.


> >> complaint.  Again, fix the nv driver so it will run my screen & I'll be
<snip>

Re: Problem with ata layer in 2.6.24

[Tejun Heo]

Kasper Sandberg wrote:
> to put some timeline perspective into this.
> i believe it was in 2005 i assembled the system, and when i realized it
> was faulty, on old ide driver, i stopped using it - that miht have been
> in beginning of 2006. then for almost a year i werent using it, hoping
> to somehow fix it, but in january 2007 i think it was, atleast in the
> very beginning of 2007, i hit upon the idea of trying libata, and ever
> since the system has been running 24/7 - doing these errors around 2
> times a day.
> 
> i have multiple times reported my problems to lkml, but nothing has
> happened, i also tried to aproeach jgarzik direcly, but he was not
> interested.
> 
> i really hope this can be solved now, its a huge problem
> 
> my fileserver has an asus k8v motherboard, with via chipset (k8t880 i
> think it is, or something like it). currently using the promise
> controller again(strangely enough all the timeouts seems to happen here,
> and when the ITE was on, there, not the onboard one), in conjunction
> with the onboard via.

Timeouts are nasty to debug.  It can be caused by whole range of
different problems including transmission errors, bad power, faulty
drive, mishandled media error, IRQ misrouting, dumb hardware bug.  It's
basically 'uh... I told the controller to do something but it never
called me back'.

If you see timeouts on multiple devices connected to different
controllers, the chance is that you have problem somewhere else.  The
most likely culprit is bad power.  Please...

* Post the result of 'lspci -nn' and kernel log including full boot log
and error messages.

* Try to isolate the problem.  ie. Does removing several number of
drives fix the problem?  If the problem is localized to certain device,
what happens if you move it?  Does the problem follow the drive or stay
with the port?  If the failing drives are SATA, it's a good idea to
power some of the failing drives with a separate PSU and see whether
anything is different.

By trying to isolate the hardware problem, more can be learned about the
error condition and even when the problem actually isn't hardware
problem, it gives us much deeper insight of the problem and clues
regarding where to look.

Thanks.

-- 
tejun

Re: Problem with ata layer in 2.6.24

[Richard Heck]

I've recently seen this kind of error myself, under Fedora 8, using the 
Fedora 2.6.23 kernels: I'd see a train of the same sort of error:
>  Jan 28 04:46:25 coyote kernel: [26550.290016] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Jan 28 04:46:25 coyote kernel: [26550.290028] ata1.00: cmd 35/00:58:c9:9c:0a/00:01:00:00:00/e0 tag 0 dma 176128 out
> Jan 28 04:46:25 coyote kernel: [26550.290029]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
>   
usually associated with the optical drive, and then it seems as if the 
whole SATA subsystem would lock up, and the machine then becomes 
useless: I get journal commit errors if I'm lucky; if I'm not, it just 
locks up. My system is also using the pata_amd driver.

I have not seen these sorts of errors with the 2.6.24 kernels.

Richard Heck

Gene Heskett wrote:
> On Monday 28 January 2008, Peter Zijlstra wrote:
>   
>> On Mon, 2008-01-28 at 09:17 +0100, Mikael Pettersson wrote:
>>     
>>> 1. Wrong mailing list; use linux-ide (@vger) instead.
>>>       
>> What, and keep all us other interested people in the dark?
>>     
>
> As a test, I tried rebooting to the latest fedora kernel and found it kills X, 
> so I'm back to the second to last fedora version ATM, and the 
> third 'smartctl -t lng /dev/sda' in 24 hours is running now.  The first two 
> completed with no errors.
>
> I've added the linux-ide list to refresh those people of the problem, 
> the logs are being spammed by this message stanza:
>
>  Jan 28 04:46:25 coyote kernel: [26550.290016] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Jan 28 04:46:25 coyote kernel: [26550.290028] ata1.00: cmd 35/00:58:c9:9c:0a/00:01:00:00:00/e0 tag 0 dma 176128 out
> Jan 28 04:46:25 coyote kernel: [26550.290029]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> Jan 28 04:46:25 coyote kernel: [26550.290032] ata1.00: status: { DRDY }
> Jan 28 04:46:25 coyote kernel: [26550.290060] ata1: soft resetting link
> Jan 28 04:46:25 coyote kernel: [26550.452301] ata1.00: configured for UDMA/100
> Jan 28 04:46:25 coyote kernel: [26550.452318] ata1: EH complete
> Jan 28 04:46:25 coyote kernel: [26550.455898] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
> Jan 28 04:46:25 coyote kernel: [26550.456151] sd 0:0:0:0: [sda] Write Protect is off
> Jan 28 04:46:25 coyote kernel: [26550.456403] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
> support DPO or FUA
>
>
> And it just did it again, using the fedora kernel but without logging 
> anything at all when it froze.  In other words I had to reboot between 
> the word list and the word to above.  So now I'm booted to 2.6.24-rc7.
>
> Before it crashes again, here is the dmesg:
> [    0.000000] Linux version 2.6.24-rc7 (root@coyote.coyote.den) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP 
> Mon Jan 14 10:00:40 EST 2008
> [    0.000000] BIOS-provided physical RAM map:
> [    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
> [    0.000000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
> [    0.000000]  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> [    0.000000]  BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
> [    0.000000]  BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
> [    0.000000]  BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
> [    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
> [    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
> [    0.000000]  BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
> [    0.000000] 127MB HIGHMEM available.
> [    0.000000] 896MB LOWMEM available.
> [    0.000000] Entering add_active_range(0, 0, 262128) 0 entries of 256 used
> [    0.000000] Zone PFN ranges:
> [    0.000000]   DMA             0 ->     4096
> [    0.000000]   Normal       4096 ->   229376
> [    0.000000]   HighMem    229376 ->   262128
> [    0.000000] Movable zone start PFN for each node
> [    0.000000] early_node_map[1] active PFN ranges
> [    0.000000]     0:        0 ->   262128
> [    0.000000] On node 0 totalpages: 262128
> [    0.000000]   DMA zone: 32 pages used for memmap
> [    0.000000]   DMA zone: 0 pages reserved
> [    0.000000]   DMA zone: 4064 pages, LIFO batch:0
> [    0.000000]   Normal zone: 1760 pages used for memmap
> [    0.000000]   Normal zone: 223520 pages, LIFO batch:31
> [    0.000000]   HighMem zone: 255 pages used for memmap
> [    0.000000]   HighMem zone: 32497 pages, LIFO batch:7
> [    0.000000]   Movable zone: 0 pages used for memmap
> [    0.000000] DMI 2.2 present.
> [    0.000000] ACPI: RSDP 000F7220, 0014 (r0 Nvidia)
> [    0.000000] ACPI: RSDT 3FFF3000, 002C (r1 Nvidia AWRDACPI 42302E31 AWRD        0)
> [    0.000000] ACPI: FACP 3FFF3040, 0074 (r1 Nvidia AWRDACPI 42302E31 AWRD        0)
> [    0.000000] ACPI: DSDT 3FFF30C0, 4CC4 (r1 NVIDIA AWRDACPI     1000 MSFT  100000E)
> [    0.000000] ACPI: FACS 3FFF0000, 0040
> [    0.000000] ACPI: APIC 3FFF7DC0, 006E (r1 Nvidia AWRDACPI 42302E31 AWRD        0)
> [    0.000000] Nvidia board detected. Ignoring ACPI timer override.
> [    0.000000] If you got timer trouble try acpi_use_timer_override
> [    0.000000] ACPI: PM-Timer IO Port: 0x4008
> [    0.000000] ACPI: Local APIC address 0xfee00000
> [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> [    0.000000] Processor #0 6:10 APIC version 16
> [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> [    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
> [    0.000000] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
> [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> [    0.000000] ACPI: BIOS IRQ0 pin2 override ignored.
> [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
> [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
> [    0.000000] ACPI: IRQ9 used by override.
> [    0.000000] ACPI: IRQ14 used by override.
> [    0.000000] ACPI: IRQ15 used by override.
> [    0.000000] Enabling APIC mode:  Flat.  Using 1 I/O APICs
> [    0.000000] Using ACPI (MADT) for SMP configuration information
> [    0.000000] Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
> [    0.000000] swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
> [    0.000000] swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000f0000
> [    0.000000] swsusp: Registered nosave memory region: 00000000000f0000 - 0000000000100000
> [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260081
> [    0.000000] Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
> [    0.000000] mapped APIC to ffffb000 (fee00000)
> [    0.000000] mapped IOAPIC to ffffa000 (fec00000)
> [    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] CPU 0 irqstacks, hard=c073a000 soft=c071a000
> [    0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
> [    0.000000] Detected 2079.551 MHz processor.
> [   28.725256] Console: colour VGA+ 80x25
> [   28.725259] console [tty0] enabled
> [   28.725828] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
> [   28.726361] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> [   28.756701] Memory: 1031116k/1048512k available (1938k kernel code, 16656k reserved, 967k data, 236k init, 131008k 
> highmem)
> [   28.756710] virtual kernel memory layout:
> [   28.756711]     fixmap  : 0xffc55000 - 0xfffff000   (3752 kB)
> [   28.756713]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
> [   28.756714]     vmalloc : 0xf8800000 - 0xff7fe000   ( 111 MB)
> [   28.756715]     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
> [   28.756716]       .init : 0xc06dc000 - 0xc0717000   ( 236 kB)
> [   28.756718]       .data : 0xc05e4944 - 0xc06d66e4   ( 967 kB)
> [   28.756719]       .text : 0xc0400000 - 0xc05e4944   (1938 kB)
> [   28.756722] Checking if this processor honours the WP bit even in supervisor mode... Ok.
> [   28.756770] SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1
> [   28.816731] Calibrating delay using timer specific routine.. 4160.90 BogoMIPS (lpj=2080452)
> [   28.816763] Security Framework initialized
> [   28.816770] SELinux:  Initializing.
> [   28.816784] SELinux:  Starting in permissive mode
> [   28.816797] selinux_register_security:  Registering secondary module capability
> [   28.816800] Capability LSM initialized as secondary
> [   28.816809] Mount-cache hash table entries: 512
> [   28.816976] CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000 00000000 00000000 00000000 
> 00000000
> [   28.816985] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> [   28.816987] CPU: L2 Cache: 512K (64 bytes/line)
> [   28.816990] CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000420 00000000 00000000 00000000 00000000
> [   28.816996] Intel machine check architecture supported.
> [   28.816998] Intel machine check reporting enabled on CPU#0.
> [   28.817003] Compat vDSO mapped to ffffe000.
> [   28.817017] Checking 'hlt' instruction... OK.
> [   28.820895] SMP alternatives: switching to UP code
> [   28.821401] Freeing SMP alternatives: 12k freed
> [   28.821404] ACPI: Core revision 20070126
> [   28.824590] CPU0: AMD Athlon(tm) XP 2800+ stepping 00
> [   28.824614] Total of 1 processors activated (4160.90 BogoMIPS).
> [   28.824820] ENABLING IO-APIC IRQs
> [   28.825012] ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1
> [   28.936680] Brought up 1 CPUs
> [   28.936708] CPU0 attaching sched-domain:
> [   28.936711]  domain 0: span 00000001
> [   28.936713]   groups: 00000001
> [   28.936925] net_namespace: 64 bytes
> [   28.937409] Time: 12:43:09  Date: 01/28/08
> [   28.937442] NET: Registered protocol family 16
> [   28.937683] ACPI: bus type pci registered
> [   28.972986] PCI: PCI BIOS revision 2.10 entry at 0xfb4c0, last bus=2
> [   28.972989] PCI: Using configuration type 1
> [   28.972991] Setting up standard PCI resources
> [   28.980763] ACPI: EC: Look up EC in DSDT
> [   28.986590] ACPI: Interpreter enabled
> [   28.986593] ACPI: (supports S0 S1 S4 S5)
> [   28.986608] ACPI: Using IOAPIC for interrupt routing
> [   28.997079] ACPI: PCI Root Bridge [PCI0] (0000:00)
> [   28.997157] PCI: nForce2 C1 Halt Disconnect fixup
> [   28.998175] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> [   28.998355] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
> [   28.998631] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
> [   29.054757] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> [   29.054952] ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> [   29.055144] ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 *5 6 7 10 11 12 14 15)
> [   29.055334] ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 *5 6 7 10 11 12 14 15)
> [   29.055529] ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
> [   29.055724] ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 *5 6 7 10 11 12 14 15)
> [   29.055918] ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 10 11 *12 14 15)
> [   29.056109] ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 11 *12 14 15)
> [   29.056298] ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
> [   29.056489] ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 6 7 10 11 *12 14 15)
> [   29.056685] ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
> [   29.056876] ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
> [   29.057066] ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
> [   29.057258] ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
> [   29.057448] ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
> [   29.057642] ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
> [   29.057803] ACPI: PCI Interrupt Link [APC1] (IRQs *16)
> [   29.057951] ACPI: PCI Interrupt Link [APC2] (IRQs *17)
> [   29.058099] ACPI: PCI Interrupt Link [APC3] (IRQs *18)
> [   29.058246] ACPI: PCI Interrupt Link [APC4] (IRQs *19)
> [   29.058402] ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
> [   29.058617] ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0
> [   29.058827] ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22) *0
> [   29.059036] ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0
> [   29.059245] ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22) *0, disabled.
> [   29.059454] ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22) *0
> [   29.059669] ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22) *0, disabled.
> [   29.059819] ACPI: PCI Interrupt Link [APCS] (IRQs *23), disabled.
> [   29.060028] ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22) *0
> [   29.060236] ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0, disabled.
> [   29.060446] ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22) *0, disabled.
> [   29.060661] ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22) *0, disabled.
> [   29.060822] ACPI: Power Resource [ISAV] (on)
> [   29.060880] Linux Plug and Play Support v0.97 (c) Adam Belay
> [   29.060917] pnp: PnP ACPI init
> [   29.060926] ACPI: bus type pnp registered
> [   29.066989] pnp: PnP ACPI: found 16 devices
> [   29.066992] ACPI: ACPI bus type pnp unregistered
> [   29.067179] usbcore: registered new interface driver usbfs
> [   29.067257] usbcore: registered new interface driver hub
> [   29.067309] usbcore: registered new device driver usb
> [   29.067395] PCI: Using ACPI for IRQ routing
> [   29.067399] PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
> [   29.117453] NetLabel: Initializing
> [   29.117455] NetLabel:  domain hash size = 128
> [   29.117457] NetLabel:  protocols = UNLABELED CIPSOv4
> [   29.117471] NetLabel:  unlabeled traffic allowed by default
> [   29.118443] Time: tsc clocksource has been installed.
> [   29.120481] system 00:00: ioport range 0x4000-0x407f has been reserved
> [   29.120484] system 00:00: ioport range 0x4080-0x40ff has been reserved
> [   29.120487] system 00:00: ioport range 0x4400-0x447f has been reserved
> [   29.120490] system 00:00: ioport range 0x4480-0x44ff has been reserved
> [   29.120492] system 00:00: ioport range 0x4200-0x427f has been reserved
> [   29.120495] system 00:00: ioport range 0x4280-0x42ff has been reserved
> [   29.120502] system 00:01: ioport range 0x5000-0x503f has been reserved
> [   29.120505] system 00:01: ioport range 0x5100-0x513f has been reserved
> [   29.120511] system 00:02: iomem range 0xda800-0xdbfff has been reserved
> [   29.120514] system 00:02: iomem range 0xf0000-0xf7fff could not be reserved
> [   29.120516] system 00:02: iomem range 0xf8000-0xfbfff could not be reserved
> [   29.120519] system 00:02: iomem range 0xfc000-0xfffff could not be reserved
> [   29.120522] system 00:02: iomem range 0x3fff0000-0x3fffffff could not be reserved
> [   29.120525] system 00:02: iomem range 0xffff0000-0xffffffff could not be reserved
> [   29.120528] system 00:02: iomem range 0x0-0x9ffff could not be reserved
> [   29.120531] system 00:02: iomem range 0x100000-0x3ffeffff could not be reserved
> [   29.120534] system 00:02: iomem range 0xfec00000-0xfec00fff could not be reserved
> [   29.120537] system 00:02: iomem range 0xfee00000-0xfee00fff could not be reserved
> [   29.120543] system 00:04: ioport range 0xb78-0xb7b has been reserved
> [   29.120546] system 00:04: ioport range 0xf78-0xf7b has been reserved
> [   29.120548] system 00:04: ioport range 0xa78-0xa7b has been reserved
> [   29.120551] system 00:04: ioport range 0xe78-0xe7b has been reserved
> [   29.120554] system 00:04: ioport range 0xbbc-0xbbf has been reserved
> [   29.120556] system 00:04: ioport range 0xfbc-0xfbf has been reserved
> [   29.120559] system 00:04: ioport range 0x4d0-0x4d1 has been reserved
> [   29.120562] system 00:04: ioport range 0x294-0x297 has been reserved
> [   29.151040] PCI: Bridge: 0000:00:08.0
> [   29.151044]   IO window: 9000-afff
> [   29.151049]   MEM window: e3000000-e6ffffff
> [   29.151053]   PREFETCH window: 50000000-500fffff
> [   29.151058] PCI: Bridge: 0000:00:1e.0
> [   29.151059]   IO window: disabled.
> [   29.151063]   MEM window: e0000000-e2ffffff
> [   29.151066]   PREFETCH window: d0000000-dfffffff
> [   29.151077] PCI: Setting latency timer of device 0000:00:08.0 to 64
> [   29.151093] NET: Registered protocol family 2
> [   29.160585] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
> [   29.160952] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
> [   29.162429] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
> [   29.163092] TCP: Hash tables configured (established 131072 bind 65536)
> [   29.163095] TCP reno registered
> [   29.165574] checking if image is initramfs... it is
> [   29.446295] Freeing initrd memory: 3628k freed
> [   29.446709] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
> [   29.446712] apm: overridden by ACPI.
> [   29.447133] audit: initializing netlink socket (disabled)
> [   29.447149] audit(1201524188.569:1): initialized
> [   29.447287] highmem bounce pool size: 64 pages
> [   29.447291] Total HugeTLB memory allocated, 0
> [   29.449941] SELinux:  Registering netfilter hooks
> [   29.450082] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
> [   29.450086] io scheduler noop registered
> [   29.450088] io scheduler anticipatory registered
> [   29.450090] io scheduler deadline registered
> [   29.450101] io scheduler cfq registered (default)
> [   29.472109] Boot video device is 0000:02:00.0
> [   29.477398] ACPI: Thermal Zone [THRM] (51 C)
> [   29.477413] isapnp: Scanning for PnP cards...
> [   29.650914] Switched to high resolution mode on CPU 0
> [   29.834322] isapnp: No Plug & Play device found
> [   29.837157] Real Time Clock Driver v1.12ac
> [   29.837309] Non-volatile memory driver v1.2
> [   29.837312] Linux agpgart interface v0.102
> [   29.837365] agpgart: Detected NVIDIA nForce2 chipset
> [   29.853228] agpgart: AGP aperture is 256M @ 0xc0000000
> [   29.853255] Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
> [   29.853403] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> [   29.853542] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> [   29.853854] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> [   29.854037] 00:0b: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> [   29.855000] RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
> [   29.855188] PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
> [   29.855191] PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
> [   29.855565] serio: i8042 KBD port at 0x60,0x64 irq 1
> [   29.855638] mice: PS/2 mouse device common for all mice
> [   29.876081] input: AT Translated Set 2 keyboard as /class/input/input0
> [   29.878901] cpuidle: using governor ladder
> [   29.878904] cpuidle: using governor menu
> [   29.878982] usbcore: registered new interface driver hiddev
> [   29.879024] usbcore: registered new interface driver usbhid
> [   29.879027] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
> [   29.879098] TCP cubic registered
> [   29.879100] Initializing XFRM netlink socket
> [   29.879180] NET: Registered protocol family 1
> [   29.879196] NET: Registered protocol family 17
> [   29.879204] Using IPI No-Shortcut mode
> [   29.879217] registered taskstats version 1
> [   29.879349]   Magic number: 8:30:735
> [   29.879657] Freeing unused kernel memory: 236k freed
> [   29.879695] Write protecting the kernel text: 1940k
> [   29.879708] Write protecting the kernel read-only data: 758k
> [   30.175117] ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
> [   30.175126] ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [APCL] -> GSI 22 (level, high) -> IRQ 16
> [   30.175139] PCI: Setting latency timer of device 0000:00:02.2 to 64
> [   30.175143] ehci_hcd 0000:00:02.2: EHCI Host Controller
> [   30.175235] ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
> [   30.175275] ehci_hcd 0000:00:02.2: debug port 1
> [   30.175280] PCI: cache line size of 64 is not supported by device 0000:00:02.2
> [   30.175291] ehci_hcd 0000:00:02.2: irq 16, io mem 0xe7005000
> [   30.180677] ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> [   30.180795] usb usb1: configuration #1 chosen from 1 choice
> [   30.180823] hub 1-0:1.0: USB hub found
> [   30.180834] hub 1-0:1.0: 6 ports detected
> [   30.287626] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
> [   30.288031] ACPI: PCI Interrupt Link [APCF] enabled at IRQ 21
> [   30.288038] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 21 (level, high) -> IRQ 17
> [   30.288052] PCI: Setting latency timer of device 0000:00:02.0 to 64
> [   30.288055] ohci_hcd 0000:00:02.0: OHCI Host Controller
> [   30.288129] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
> [   30.288148] ohci_hcd 0000:00:02.0: irq 17, io mem 0xe7003000
> [   30.340664] usb usb2: configuration #1 chosen from 1 choice
> [   30.340691] hub 2-0:1.0: USB hub found
> [   30.340704] hub 2-0:1.0: 3 ports detected
> [   30.441860] ACPI: PCI Interrupt Link [APCG] enabled at IRQ 20
> [   30.441865] ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCG] -> GSI 20 (level, high) -> IRQ 18
> [   30.441873] PCI: Setting latency timer of device 0000:00:02.1 to 64
> [   30.441876] ohci_hcd 0000:00:02.1: OHCI Host Controller
> [   30.441932] ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3
> [   30.441945] ohci_hcd 0000:00:02.1: irq 18, io mem 0xe7004000
> [   30.487468] usb 1-1: new high speed USB device using ehci_hcd and address 2
> [   30.494540] usb usb3: configuration #1 chosen from 1 choice
> [   30.494569] hub 3-0:1.0: USB hub found
> [   30.494579] hub 3-0:1.0: 3 ports detected
> [   30.601427] USB Universal Host Controller Interface driver v3.0
> [   30.601865] usb 1-1: configuration #1 chosen from 1 choice
> [   30.602052] hub 1-1:1.0: USB hub found
> [   30.602151] hub 1-1:1.0: 4 ports detected
> [   30.660576] SCSI subsystem initialized
> [   30.673851] Driver 'sd' needs updating - please use bus_type methods
> [   30.700319] libata version 3.00 loaded.
> [   30.702887] pata_amd 0000:00:09.0: version 0.3.10
> [   30.703052] PCI: Setting latency timer of device 0000:00:09.0 to 64
> [   30.703188] scsi0 : pata_amd
> [   30.709313] scsi1 : pata_amd
> [   30.710076] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
> [   30.710079] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
> [   30.864753] ata1.00: ATA-6: WDC WD2000JB-00EVA0, 15.05R15, max UDMA/100
> [   30.864756] ata1.00: 390721968 sectors, multi 16: LBA48 
> [   30.871629] ata1.00: configured for UDMA/100
> [   31.195305] ata2.00: ATAPI: LITE-ON DVDRW SHM-165H6S, HS06, max UDMA/66
> [   31.243813] ata2.01: ATA-7: MAXTOR STM3320620A, 3.AAE, max UDMA/100
> [   31.243816] ata2.01: 625142448 sectors, multi 16: LBA48 
> [   31.243825] ata2.00: limited to UDMA/33 due to 40-wire cable
> [   31.417074] ata2.00: configured for UDMA/33
> [   31.451769] ata2.01: configured for UDMA/100
> [   31.451873] scsi 0:0:0:0: Direct-Access     ATA      WDC WD2000JB-00E 15.0 PQ: 0 ANSI: 5
> [   31.451953] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
> [   31.451967] sd 0:0:0:0: [sda] Write Protect is off
> [   31.451970] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [   31.451989] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [   31.452040] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
> [   31.452051] sd 0:0:0:0: [sda] Write Protect is off
> [   31.452054] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [   31.452071] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [   31.452075]  sda: sda1 sda2
> [   31.467219] sd 0:0:0:0: [sda] Attached SCSI disk
> [   31.468093] scsi 1:0:0:0: CD-ROM            LITE-ON  DVDRW SHM-165H6S HS06 PQ: 0 ANSI: 5
> [   31.468208] scsi 1:0:1:0: Direct-Access     ATA      MAXTOR STM332062 3.AA PQ: 0 ANSI: 5
> [   31.468272] sd 1:0:1:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
> [   31.468283] sd 1:0:1:0: [sdb] Write Protect is off
> [   31.468286] sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
> [   31.468303] sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [   31.468338] sd 1:0:1:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
> [   31.468349] sd 1:0:1:0: [sdb] Write Protect is off
> [   31.468352] sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
> [   31.468370] sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [   31.468373]  sdb:<6>usb 2-2: new full speed USB device using ohci_hcd and address 2
> [   31.499690]  sdb1 sdb2 sdb3
> [   31.500119] sd 1:0:1:0: [sdb] Attached SCSI disk
> [   31.637428] usb 2-2: configuration #1 chosen from 1 choice
> [   31.856522] usb 2-3: new low speed USB device using ohci_hcd and address 3
> [   32.020045] usb 2-3: configuration #1 chosen from 1 choice
> [   32.035222] input: Chicony Saitek Eclipse II Keyboard as /class/input/input1
> [   32.038424] input,hidraw0: USB HID v1.11 Keyboard [Chicony Saitek Eclipse II Keyboard] on usb-0000:00:02.0-3
> [   32.067995] input: Chicony Saitek Eclipse II Keyboard as /class/input/input2
> [   32.070422] input,hiddev96,hidraw1: USB HID v1.11 Device [Chicony Saitek Eclipse II Keyboard] on usb-0000:00:02.0-3
> [   32.287225] usb 3-3: new full speed USB device using ohci_hcd and address 2
> [   32.422699] usb 3-3: configuration #1 chosen from 1 choice
> [   32.425658] hub 3-3:1.0: USB hub found
> [   32.428631] hub 3-3:1.0: 4 ports detected
> [   32.724000] usb 1-1.1: new low speed USB device using ehci_hcd and address 6
> [   32.919001] usb 1-1.1: configuration #1 chosen from 1 choice
> [   33.655893] hiddev97hidraw2: USB HID v1.11 Device [Belkin  Belkin UPS] on usb-0000:00:02.2-1.1
> [   33.833315] usb 1-1.2: new full speed USB device using ehci_hcd and address 7
> [   33.925926] usb 1-1.2: configuration #1 chosen from 1 choice
> [   34.018028] device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com
> [   34.043070] sata_sil 0000:01:0a.0: version 2.3
> [   34.043348] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
> [   34.043355] ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC1] -> GSI 16 (level, high) -> IRQ 19
> [   34.045029] scsi2 : sata_sil
> [   34.050031] scsi3 : sata_sil
> [   34.050064] ata3: SATA max UDMA/100 mmio m512@0xe6004000 tf 0xe6004080 irq 19
> [   34.050068] ata4: SATA max UDMA/100 mmio m512@0xe6004000 tf 0xe60040c0 irq 19
> [   34.107056] usb 1-1.4: new high speed USB device using ehci_hcd and address 8
> [   34.192310] usb 1-1.4: configuration #1 chosen from 1 choice
> [   34.192499] hub 1-1.4:1.0: USB hub found
> [   34.192597] hub 1-1.4:1.0: 4 ports detected
> [   34.352811] ata3: SATA link down (SStatus 0 SControl 310)
> [   34.481823] usb 1-1.4.3: new low speed USB device using ehci_hcd and address 9
> [   34.573676] usb 1-1.4.3: configuration #1 chosen from 1 choice
> [   34.577917] input: Logitech USB Receiver as /class/input/input3
> [   34.580691] input,hidraw3: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:02.2-1.4.3
> [   34.757557] usb 1-1.4.4: new full speed USB device using ehci_hcd and address 10
> [   34.806514] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> [   34.810071] ata4.00: ATA-7: Hitachi HDT725040VLA360, V5COA7EA, max UDMA/133
> [   34.810074] ata4.00: 781422768 sectors, multi 16: LBA48 NCQ (depth 0/32)
> [   34.816059] ata4.00: configured for UDMA/100
> [   34.816175] scsi 3:0:0:0: Direct-Access     ATA      Hitachi HDT72504 V5CO PQ: 0 ANSI: 5
> [   34.816257] sd 3:0:0:0: [sdc] 781422768 512-byte hardware sectors (400088 MB)
> [   34.816271] sd 3:0:0:0: [sdc] Write Protect is off
> [   34.816274] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> [   34.816293] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [   34.816344] sd 3:0:0:0: [sdc] 781422768 512-byte hardware sectors (400088 MB)
> [   34.816355] sd 3:0:0:0: [sdc] Write Protect is off
> [   34.816358] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> [   34.816375] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [   34.816379]  sdc: sdc1
> [   34.829837] sd 3:0:0:0: [sdc] Attached SCSI disk
> [   34.843933] usb 1-1.4.4: configuration #1 chosen from 1 choice
> [   37.852458] EXT3-fs: INFO: recovery required on readonly filesystem.
> [   37.852464] EXT3-fs: write access will be enabled during recovery.
> [   41.522866] kjournald starting.  Commit interval 5 seconds
> [   41.522885] EXT3-fs: recovery complete.
> [   41.524254] EXT3-fs: mounted filesystem with ordered data mode.
> [   41.972449] audit(1201524201.103:2): enforcing=1 old_enforcing=0 auid=4294967295
> [   42.187011] SELinux:8192 avtab hash slots allocated.Num of rules:213166
> [   42.260611] SELinux:8192 avtab hash slots allocated.Num of rules:213166
> [   42.314117] security:  8 users, 11 roles, 2363 types, 114 bools, 1 sens, 1024 cats
> [   42.314122] security:  67 classes, 213166 rules
> [   42.327287] SELinux:  Completing initialization.
> [   42.327290] SELinux:  Setting up existing superblocks.
> [   42.353550] SELinux: initialized (dev dm-0, type ext3), uses xattr
> [   42.515071] SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
> [   42.515088] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
> [   42.515193] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
> [   42.515205] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
> [   42.515235] SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
> [   42.515244] SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts
> [   42.515250] SELinux: initialized (dev devpts, type devpts), uses transition SIDs
> [   42.515262] SELinux: initialized (dev inotifyfs, type inotifyfs), uses genfs_contexts
> [   42.515266] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
> [   42.515274] SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
> [   42.515280] SELinux: initialized (dev anon_inodefs, type anon_inodefs), uses genfs_contexts
> [   42.515285] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
> [   42.515290] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
> [   42.515299] SELinux: initialized (dev proc, type proc), uses genfs_contexts
> [   42.515312] SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
> [   42.515318] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
> [   42.515341] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
> [   42.520002] SELinux: policy loaded with handle_unknown=allow
> [   42.520011] audit(1201524201.651:3): policy loaded auid=4294967295
> [   46.528101] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [   46.528126] scsi 1:0:0:0: Attached scsi generic sg1 type 5
> [   46.528149] sd 1:0:1:0: Attached scsi generic sg2 type 0
> [   46.528174] sd 3:0:0:0: Attached scsi generic sg3 type 0
> [   46.931288] input: Power Button (FF) as /class/input/input4
> [   46.938141] ACPI: Power Button (FF) [PWRF]
> [   46.938186] ACPI Error (evxfevnt-0186): Could not enable SleepButton event [20070126]
> [   46.938192] ACPI Warning (evxface-0145): Could not enable fixed event 3 [20070126]
> [   46.938283] input: Power Button (CM) as /class/input/input5
> [   46.941132] ACPI: Power Button (CM) [PWRB]
> [   46.941190] input: Sleep Button (CM) as /class/input/input6
> [   46.944347] ACPI: Sleep Button (CM) [SLPB]
> [   47.285717] usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x04B8 pid 0x0005
> [   47.285742] usbcore: registered new interface driver usblp
> [   47.308848] i2c-adapter i2c-0: nForce2 SMBus adapter at 0x5000
> [   47.308876] i2c-adapter i2c-1: nForce2 SMBus adapter at 0x5100
> [   47.352146] usbcore: registered new interface driver usbserial
> [   47.352152] drivers/usb/serial/usb-serial.c: USB Serial Driver core
> [   47.455275] drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
> [   47.455308] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
> [   47.455342] drivers/usb/serial/ftdi_sio.c: Detected FT232RL
> [   47.455381] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
> [   47.455398] usbcore: registered new interface driver ftdi_sio
> [   47.455401] drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
> [   47.530751] input: PC Speaker as /class/input/input7
> [   47.572764] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
> [   47.573147] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 22
> [   47.573151] ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCH] -> GSI 22 (level, high) -> IRQ 16
> [   47.573158] PCI: Setting latency timer of device 0000:00:04.0 to 64
> [   47.615492] Floppy drive(s): fd0 is 1.44M
> [   47.630509] FDC 0 is a post-1991 82077
> [   48.084769] forcedeth 0000:00:04.0: ifname eth0, PHY OUI 0x20 @ 1, addr 00:04:4b:5d:eb:7d
> [   48.084775] forcedeth 0000:00:04.0: timirq lnktim desc-v1
> [   48.085214] ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
> [   48.085222] ACPI: PCI Interrupt 0000:01:09.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 20
> [   48.141308] firewire_ohci: Added fw-ohci device 0000:01:09.0, OHCI version 1.10
> [   48.285456] nvidia: module license 'NVIDIA' taints kernel.
> [   48.549725] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 20
> [   48.550149] NVRM: loading NVIDIA UNIX x86 Kernel Module  169.07  Thu Dec 13 18:42:56 PST 2007
> [   48.641028] firewire_core: created new fw device fw0 (0 config rom retries, S400)
> [   48.848094] Linux video capture interface: v2.00
> [   49.104974] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
> [   49.105072] cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV [card=22,autodetected]
> [   49.105076] cx88[0]: TV tuner type 60, Radio tuner type -1
> [   49.151205] cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
> [   49.255507] cx88[0]/2: cx2388x 8802 Driver Manager
> [   49.257461] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
> [   49.257472] ACPI: PCI Interrupt 0000:01:07.2[A] -> Link [APC2] -> GSI 17 (level, high) -> IRQ 21
> [   49.257484] cx88[0]/2: found at 0000:01:07.2, rev: 5, irq: 21, latency: 32, mmio: 0xe4000000
> [   49.257561] ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC2] -> GSI 17 (level, high) -> IRQ 21
> [   49.257573] cx88[0]/0: found at 0000:01:07.0, rev: 5, irq: 21, latency: 32, mmio: 0xe3000000
> [   49.440179] tda8290_probe: not probed - driver disabled by Kconfig
> [   49.440185] tuner 2-0043: chip found @ 0x86 (cx88[0])
> [   49.440208] tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
> [   49.440211] tuner 2-0043: type set to tda9887
> [   49.442442] tuner 2-0061: chip found @ 0xc2 (cx88[0])
> [   49.442458] tuner-simple 2-0061: type set to 60 (Thomson DTT 761X (ATSC/NTSC))
> [   49.442461] tuner 2-0061: type set to Thomson DTT 761X (A
> [   49.442464] tuner-simple 2-0061: type set to 60 (Thomson DTT 761X (ATSC/NTSC))
> [   49.442466] tuner 2-0061: type set to Thomson DTT 761X (A
> [   49.451016] cx88[0]/0: registered device video0 [v4l2]
> [   49.451038] cx88[0]/0: registered device vbi0
> [   49.451064] cx88[0]/0: registered device radio0
> [   49.454722] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
> [   49.454731] ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC3] -> GSI 18 (level, high) -> IRQ 22
> [   49.459555] Audigy2 value: Special config.
> [   49.532042] cx88/2: cx2388x dvb driver version 0.0.6 loaded
> [   49.532047] cx88/2: registering cx8802 driver, type: dvb access: shared
> [   49.532052] cx88[0]/2: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV [card=22]
> [   49.532055] cx88[0]/2: cx2388x based DVB/ATSC card
> [   49.548119] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 21
> [   49.548125] ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 21 (level, high) -> IRQ 17
> [   49.548162] PCI: Setting latency timer of device 0000:00:06.0 to 64
> [   49.654575] DVB: registering new adapter (cx88[0])
> [   49.654582] DVB: registering frontend 0 (Oren OR51132 VSB/QAM Frontend)...
> [   49.859126] intel8x0_measure_ac97_clock: measured 50668 usecs
> [   49.859131] intel8x0: clocking to 47378
> [   52.910654] EXT3 FS on dm-0, internal journal
> [   53.162621] kjournald starting.  Commit interval 5 seconds
> [   53.170013] EXT3 FS on sda1, internal journal
> [   53.170019] EXT3-fs: mounted filesystem with ordered data mode.
> [   53.170144] SELinux: initialized (dev sda1, type ext3), uses xattr
> [   53.170540] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
> [   53.174936] kjournald starting.  Commit interval 5 seconds
> [   53.182987] EXT3 FS on sdc1, internal journal
> [   53.182992] EXT3-fs: mounted filesystem with ordered data mode.
> [   53.188827] SELinux: initialized (dev sdc1, type ext3), uses xattr
> [   54.005729] Adding 2031608k swap on /dev/mapper/VolGroup00-LogVol01.  Priority:-1 extents:1 across:2031608k
> [   54.009417] SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
>
>
>
>   

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Richard Heck wrote:
>I've recently seen this kind of error myself, under Fedora 8, using the
>
>Fedora 2.6.23 kernels: I'd see a train of the same sort of error:
>>  Jan 28 04:46:25 coyote kernel: [26550.290016] ata1.00: exception Emask
>> 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Jan 28 04:46:25 coyote kernel:
>> [26550.290028] ata1.00: cmd 35/00:58:c9:9c:0a/00:01:00:00:00/e0 tag 0 dma
>> 176128 out Jan 28 04:46:25 coyote kernel: [26550.290029]          res
>> 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
>
>usually associated with the optical drive, and then it seems as if the
>whole SATA subsystem would lock up, and the machine then becomes
>useless: I get journal commit errors if I'm lucky; if I'm not, it just
>locks up. My system is also using the pata_amd driver.
>
>I have not seen these sorts of errors with the 2.6.24 kernels.
>
>Richard Heck
>
Unforch, this is my only bootable drive, and its raising hell with things, 
about 6 hardware reset initiated reboots so far today since 6:15 am.  If it 
persists I'll go see if Circuit City still has any pata drives left as this 
mobo won't boot from a sata card.

>Gene Heskett wrote:
>> On Monday 28 January 2008, Peter Zijlstra wrote:
>>> On Mon, 2008-01-28 at 09:17 +0100, Mikael Pettersson wrote:
>>>> 1. Wrong mailing list; use linux-ide (@vger) instead.
>>>
>>> What, and keep all us other interested people in the dark?
>>
>> As a test, I tried rebooting to the latest fedora kernel and found it
>> kills X, so I'm back to the second to last fedora version ATM, and the
>> third 'smartctl -t lng /dev/sda' in 24 hours is running now.  The first
>> two completed with no errors.
>>
>> I've added the linux-ide list to refresh those people of the problem,
>> the logs are being spammed by this message stanza:
>>
>>  Jan 28 04:46:25 coyote kernel: [26550.290016] ata1.00: exception Emask
>> 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Jan 28 04:46:25 coyote kernel:
>> [26550.290028] ata1.00: cmd 35/00:58:c9:9c:0a/00:01:00:00:00/e0 tag 0 dma
>> 176128 out Jan 28 04:46:25 coyote kernel: [26550.290029]          res
>> 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 28 04:46:25
>> coyote kernel: [26550.290032] ata1.00: status: { DRDY } Jan 28 04:46:25
>> coyote kernel: [26550.290060] ata1: soft resetting link Jan 28 04:46:25
>> coyote kernel: [26550.452301] ata1.00: configured for UDMA/100 Jan 28
>> 04:46:25 coyote kernel: [26550.452318] ata1: EH complete
>> Jan 28 04:46:25 coyote kernel: [26550.455898] sd 0:0:0:0: [sda] 390721968
>> 512-byte hardware sectors (200050 MB) Jan 28 04:46:25 coyote kernel:
>> [26550.456151] sd 0:0:0:0: [sda] Write Protect is off Jan 28 04:46:25
>> coyote kernel: [26550.456403] sd 0:0:0:0: [sda] Write cache: enabled, read
>> cache: enabled, doesn't support DPO or FUA
>>
>>
>> And it just did it again, using the fedora kernel but without logging
>> anything at all when it froze.  In other words I had to reboot between
>> the word list and the word to above.  So now I'm booted to 2.6.24-rc7.
>>
>> Before it crashes again, here is the dmesg:
>> [    0.000000] Linux version 2.6.24-rc7 (root@coyote.coyote.den) (gcc
>> version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Mon Jan 14 10:00:40 EST
>> 2008
>> [    0.000000] BIOS-provided physical RAM map:
>> [    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
>> [    0.000000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
>> [    0.000000]  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
>> [    0.000000]  BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
>> [    0.000000]  BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
>> [    0.000000]  BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
>> [    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
>> [    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
>> [    0.000000]  BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
>> [    0.000000] 127MB HIGHMEM available.
>> [    0.000000] 896MB LOWMEM available.
>> [    0.000000] Entering add_active_range(0, 0, 262128) 0 entries of 256
>> used [    0.000000] Zone PFN ranges:
>> [    0.000000]   DMA             0 ->     4096
>> [    0.000000]   Normal       4096 ->   229376
>> [    0.000000]   HighMem    229376 ->   262128
>> [    0.000000] Movable zone start PFN for each node
>> [    0.000000] early_node_map[1] active PFN ranges
>> [    0.000000]     0:        0 ->   262128
>> [    0.000000] On node 0 totalpages: 262128
>> [    0.000000]   DMA zone: 32 pages used for memmap
>> [    0.000000]   DMA zone: 0 pages reserved
>> [    0.000000]   DMA zone: 4064 pages, LIFO batch:0
>> [    0.000000]   Normal zone: 1760 pages used for memmap
>> [    0.000000]   Normal zone: 223520 pages, LIFO batch:31
>> [    0.000000]   HighMem zone: 255 pages used for memmap
>> [    0.000000]   HighMem zone: 32497 pages, LIFO batch:7
>> [    0.000000]   Movable zone: 0 pages used for memmap
>> [    0.000000] DMI 2.2 present.
>> [    0.000000] ACPI: RSDP 000F7220, 0014 (r0 Nvidia)
>> [    0.000000] ACPI: RSDT 3FFF3000, 002C (r1 Nvidia AWRDACPI 42302E31 AWRD
>>        0) [    0.000000] ACPI: FACP 3FFF3040, 0074 (r1 Nvidia AWRDACPI
>> 42302E31 AWRD        0) [    0.000000] ACPI: DSDT 3FFF30C0, 4CC4 (r1
>> NVIDIA AWRDACPI     1000 MSFT  100000E) [    0.000000] ACPI: FACS
>> 3FFF0000, 0040
>> [    0.000000] ACPI: APIC 3FFF7DC0, 006E (r1 Nvidia AWRDACPI 42302E31 AWRD
>>        0) [    0.000000] Nvidia board detected. Ignoring ACPI timer
>> override. [    0.000000] If you got timer trouble try
>> acpi_use_timer_override [    0.000000] ACPI: PM-Timer IO Port: 0x4008
>> [    0.000000] ACPI: Local APIC address 0xfee00000
>> [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
>> [    0.000000] Processor #0 6:10 APIC version 16
>> [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
>> [    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
>> [    0.000000] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI
>> 0-23 [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl
>> dfl) [    0.000000] ACPI: BIOS IRQ0 pin2 override ignored.
>> [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
>> [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high
>> edge) [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15
>> high edge) [    0.000000] ACPI: IRQ9 used by override.
>> [    0.000000] ACPI: IRQ14 used by override.
>> [    0.000000] ACPI: IRQ15 used by override.
>> [    0.000000] Enabling APIC mode:  Flat.  Using 1 I/O APICs
>> [    0.000000] Using ACPI (MADT) for SMP configuration information
>> [    0.000000] Allocating PCI resources starting at 50000000 (gap:
>> 40000000:bec00000) [    0.000000] swsusp: Registered nosave memory region:
>> 000000000009f000 - 00000000000a0000 [    0.000000] swsusp: Registered
>> nosave memory region: 00000000000a0000 - 00000000000f0000 [    0.000000]
>> swsusp: Registered nosave memory region: 00000000000f0000 -
>> 0000000000100000 [    0.000000] Built 1 zonelists in Zone order, mobility
>> grouping on.  Total pages: 260081 [    0.000000] Kernel command line: ro
>> root=/dev/VolGroup00/LogVol00 rhgb quiet [    0.000000] mapped APIC to
>> ffffb000 (fee00000)
>> [    0.000000] mapped IOAPIC to ffffa000 (fec00000)
>> [    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] CPU 0 irqstacks, hard=c073a000 soft=c071a000
>> [    0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
>> [    0.000000] Detected 2079.551 MHz processor.
>> [   28.725256] Console: colour VGA+ 80x25
>> [   28.725259] console [tty0] enabled
>> [   28.725828] Dentry cache hash table entries: 131072 (order: 7, 524288
>> bytes) [   28.726361] Inode-cache hash table entries: 65536 (order: 6,
>> 262144 bytes) [   28.756701] Memory: 1031116k/1048512k available (1938k
>> kernel code, 16656k reserved, 967k data, 236k init, 131008k highmem)
>> [   28.756710] virtual kernel memory layout:
>> [   28.756711]     fixmap  : 0xffc55000 - 0xfffff000   (3752 kB)
>> [   28.756713]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
>> [   28.756714]     vmalloc : 0xf8800000 - 0xff7fe000   ( 111 MB)
>> [   28.756715]     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
>> [   28.756716]       .init : 0xc06dc000 - 0xc0717000   ( 236 kB)
>> [   28.756718]       .data : 0xc05e4944 - 0xc06d66e4   ( 967 kB)
>> [   28.756719]       .text : 0xc0400000 - 0xc05e4944   (1938 kB)
>> [   28.756722] Checking if this processor honours the WP bit even in
>> supervisor mode... Ok. [   28.756770] SLUB: Genslabs=11, HWalign=32,
>> Order=0-1, MinObjects=4, CPUs=1, Nodes=1 [   28.816731] Calibrating delay
>> using timer specific routine.. 4160.90 BogoMIPS (lpj=2080452) [  
>> 28.816763] Security Framework initialized
>> [   28.816770] SELinux:  Initializing.
>> [   28.816784] SELinux:  Starting in permissive mode
>> [   28.816797] selinux_register_security:  Registering secondary module
>> capability [   28.816800] Capability LSM initialized as secondary
>> [   28.816809] Mount-cache hash table entries: 512
>> [   28.816976] CPU: After generic identify, caps: 0383fbff c1c3fbff
>> 00000000 00000000 00000000 00000000 00000000 00000000
>> [   28.816985] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
>> bytes/line) [   28.816987] CPU: L2 Cache: 512K (64 bytes/line)
>> [   28.816990] CPU: After all inits, caps: 0383fbff c1c3fbff 00000000
>> 00000420 00000000 00000000 00000000 00000000 [   28.816996] Intel machine
>> check architecture supported.
>> [   28.816998] Intel machine check reporting enabled on CPU#0.
>> [   28.817003] Compat vDSO mapped to ffffe000.
>> [   28.817017] Checking 'hlt' instruction... OK.
>> [   28.820895] SMP alternatives: switching to UP code
>> [   28.821401] Freeing SMP alternatives: 12k freed
>> [   28.821404] ACPI: Core revision 20070126
>> [   28.824590] CPU0: AMD Athlon(tm) XP 2800+ stepping 00
>> [   28.824614] Total of 1 processors activated (4160.90 BogoMIPS).
>> [   28.824820] ENABLING IO-APIC IRQs
>> [   28.825012] ..TIMER: vector=0x31 apic1=0 pin1=0 apic2=-1 pin2=-1
>> [   28.936680] Brought up 1 CPUs
>> [   28.936708] CPU0 attaching sched-domain:
>> [   28.936711]  domain 0: span 00000001
>> [   28.936713]   groups: 00000001
>> [   28.936925] net_namespace: 64 bytes
>> [   28.937409] Time: 12:43:09  Date: 01/28/08
>> [   28.937442] NET: Registered protocol family 16
>> [   28.937683] ACPI: bus type pci registered
>> [   28.972986] PCI: PCI BIOS revision 2.10 entry at 0xfb4c0, last bus=2
>> [   28.972989] PCI: Using configuration type 1
>> [   28.972991] Setting up standard PCI resources
>> [   28.980763] ACPI: EC: Look up EC in DSDT
>> [   28.986590] ACPI: Interpreter enabled
>> [   28.986593] ACPI: (supports S0 S1 S4 S5)
>> [   28.986608] ACPI: Using IOAPIC for interrupt routing
>> [   28.997079] ACPI: PCI Root Bridge [PCI0] (0000:00)
>> [   28.997157] PCI: nForce2 C1 Halt Disconnect fixup
>> [   28.998175] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
>> [   28.998355] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
>> [   28.998631] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
>> [   29.054757] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 *11 12
>> 14 15) [   29.054952] ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10
>> *11 12 14 15) [   29.055144] ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 *5
>> 6 7 10 11 12 14 15) [   29.055334] ACPI: PCI Interrupt Link [LNK4] (IRQs 3
>> 4 *5 6 7 10 11 12 14 15) [   29.055529] ACPI: PCI Interrupt Link [LNK5]
>> (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. [   29.055724] ACPI: PCI
>> Interrupt Link [LUBA] (IRQs 3 4 *5 6 7 10 11 12 14 15) [   29.055918]
>> ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 10 11 *12 14 15) [  
>> 29.056109] ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 11 *12 14
>> 15) [   29.056298] ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 10 11
>> 12 14 15) *0, disabled. [   29.056489] ACPI: PCI Interrupt Link [LACI]
>> (IRQs 3 4 5 6 7 10 11 *12 14 15) [   29.056685] ACPI: PCI Interrupt Link
>> [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. [   29.056876] ACPI:
>> PCI Interrupt Link [LSMB] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. [ 
>>  29.057066] ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 6 7 10 *11 12 14
>> 15) [   29.057258] ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11
>> 12 14 15) *0, disabled. [   29.057448] ACPI: PCI Interrupt Link [L3CM]
>> (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. [   29.057642] ACPI: PCI
>> Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. [  
>> 29.057803] ACPI: PCI Interrupt Link [APC1] (IRQs *16)
>> [   29.057951] ACPI: PCI Interrupt Link [APC2] (IRQs *17)
>> [   29.058099] ACPI: PCI Interrupt Link [APC3] (IRQs *18)
>> [   29.058246] ACPI: PCI Interrupt Link [APC4] (IRQs *19)
>> [   29.058402] ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
>> [   29.058617] ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0
>> [   29.058827] ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22) *0
>> [   29.059036] ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0
>> [   29.059245] ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22) *0,
>> disabled. [   29.059454] ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22)
>> *0 [   29.059669] ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22) *0,
>> disabled. [   29.059819] ACPI: PCI Interrupt Link [APCS] (IRQs *23),
>> disabled. [   29.060028] ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22)
>> *0 [   29.060236] ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0,
>> disabled. [   29.060446] ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22)
>> *0, disabled. [   29.060661] ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21
>> 22) *0, disabled. [   29.060822] ACPI: Power Resource [ISAV] (on)
>> [   29.060880] Linux Plug and Play Support v0.97 (c) Adam Belay
>> [   29.060917] pnp: PnP ACPI init
>> [   29.060926] ACPI: bus type pnp registered
>> [   29.066989] pnp: PnP ACPI: found 16 devices
>> [   29.066992] ACPI: ACPI bus type pnp unregistered
>> [   29.067179] usbcore: registered new interface driver usbfs
>> [   29.067257] usbcore: registered new interface driver hub
>> [   29.067309] usbcore: registered new device driver usb
>> [   29.067395] PCI: Using ACPI for IRQ routing
>> [   29.067399] PCI: If a device doesn't work, try "pci=routeirq".  If it
>> helps, post a report [   29.117453] NetLabel: Initializing
>> [   29.117455] NetLabel:  domain hash size = 128
>> [   29.117457] NetLabel:  protocols = UNLABELED CIPSOv4
>> [   29.117471] NetLabel:  unlabeled traffic allowed by default
>> [   29.118443] Time: tsc clocksource has been installed.
>> [   29.120481] system 00:00: ioport range 0x4000-0x407f has been reserved
>> [   29.120484] system 00:00: ioport range 0x4080-0x40ff has been reserved
>> [   29.120487] system 00:00: ioport range 0x4400-0x447f has been reserved
>> [   29.120490] system 00:00: ioport range 0x4480-0x44ff has been reserved
>> [   29.120492] system 00:00: ioport range 0x4200-0x427f has been reserved
>> [   29.120495] system 00:00: ioport range 0x4280-0x42ff has been reserved
>> [   29.120502] system 00:01: ioport range 0x5000-0x503f has been reserved
>> [   29.120505] system 00:01: ioport range 0x5100-0x513f has been reserved
>> [   29.120511] system 00:02: iomem range 0xda800-0xdbfff has been reserved
>> [   29.120514] system 00:02: iomem range 0xf0000-0xf7fff could not be
>> reserved [   29.120516] system 00:02: iomem range 0xf8000-0xfbfff could
>> not be reserved [   29.120519] system 00:02: iomem range 0xfc000-0xfffff
>> could not be reserved [   29.120522] system 00:02: iomem range
>> 0x3fff0000-0x3fffffff could not be reserved [   29.120525] system 00:02:
>> iomem range 0xffff0000-0xffffffff could not be reserved [   29.120528]
>> system 00:02: iomem range 0x0-0x9ffff could not be reserved [   29.120531]
>> system 00:02: iomem range 0x100000-0x3ffeffff could not be reserved [  
>> 29.120534] system 00:02: iomem range 0xfec00000-0xfec00fff could not be
>> reserved [   29.120537] system 00:02: iomem range 0xfee00000-0xfee00fff
>> could not be reserved [   29.120543] system 00:04: ioport range
>> 0xb78-0xb7b has been reserved [   29.120546] system 00:04: ioport range
>> 0xf78-0xf7b has been reserved [   29.120548] system 00:04: ioport range
>> 0xa78-0xa7b has been reserved [   29.120551] system 00:04: ioport range
>> 0xe78-0xe7b has been reserved [   29.120554] system 00:04: ioport range
>> 0xbbc-0xbbf has been reserved [   29.120556] system 00:04: ioport range
>> 0xfbc-0xfbf has been reserved [   29.120559] system 00:04: ioport range
>> 0x4d0-0x4d1 has been reserved [   29.120562] system 00:04: ioport range
>> 0x294-0x297 has been reserved [   29.151040] PCI: Bridge: 0000:00:08.0
>> [   29.151044]   IO window: 9000-afff
>> [   29.151049]   MEM window: e3000000-e6ffffff
>> [   29.151053]   PREFETCH window: 50000000-500fffff
>> [   29.151058] PCI: Bridge: 0000:00:1e.0
>> [   29.151059]   IO window: disabled.
>> [   29.151063]   MEM window: e0000000-e2ffffff
>> [   29.151066]   PREFETCH window: d0000000-dfffffff
>> [   29.151077] PCI: Setting latency timer of device 0000:00:08.0 to 64
>> [   29.151093] NET: Registered protocol family 2
>> [   29.160585] IP route cache hash table entries: 32768 (order: 5, 131072
>> bytes) [   29.160952] TCP established hash table entries: 131072 (order:
>> 8, 1048576 bytes) [   29.162429] TCP bind hash table entries: 65536
>> (order: 7, 524288 bytes) [   29.163092] TCP: Hash tables configured
>> (established 131072 bind 65536) [   29.163095] TCP reno registered
>> [   29.165574] checking if image is initramfs... it is
>> [   29.446295] Freeing initrd memory: 3628k freed
>> [   29.446709] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
>> [   29.446712] apm: overridden by ACPI.
>> [   29.447133] audit: initializing netlink socket (disabled)
>> [   29.447149] audit(1201524188.569:1): initialized
>> [   29.447287] highmem bounce pool size: 64 pages
>> [   29.447291] Total HugeTLB memory allocated, 0
>> [   29.449941] SELinux:  Registering netfilter hooks
>> [   29.450082] Block layer SCSI generic (bsg) driver version 0.4 loaded
>> (major 254) [   29.450086] io scheduler noop registered
>> [   29.450088] io scheduler anticipatory registered
>> [   29.450090] io scheduler deadline registered
>> [   29.450101] io scheduler cfq registered (default)
>> [   29.472109] Boot video device is 0000:02:00.0
>> [   29.477398] ACPI: Thermal Zone [THRM] (51 C)
>> [   29.477413] isapnp: Scanning for PnP cards...
>> [   29.650914] Switched to high resolution mode on CPU 0
>> [   29.834322] isapnp: No Plug & Play device found
>> [   29.837157] Real Time Clock Driver v1.12ac
>> [   29.837309] Non-volatile memory driver v1.2
>> [   29.837312] Linux agpgart interface v0.102
>> [   29.837365] agpgart: Detected NVIDIA nForce2 chipset
>> [   29.853228] agpgart: AGP aperture is 256M @ 0xc0000000
>> [   29.853255] Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ
>> sharing disabled [   29.853403] serial8250: ttyS0 at I/O 0x3f8 (irq = 4)
>> is a 16550A [   29.853542] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a
>> 16550A [   29.853854] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>> [   29.854037] 00:0b: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
>> [   29.855000] RAMDISK driver initialized: 16 RAM disks of 16384K size
>> 4096 blocksize [   29.855188] PNP: PS/2 Controller [PNP0303:PS2K] at
>> 0x60,0x64 irq 1 [   29.855191] PNP: PS/2 appears to have AUX port
>> disabled, if this is incorrect please boot with i8042.nopnp [   29.855565]
>> serio: i8042 KBD port at 0x60,0x64 irq 1
>> [   29.855638] mice: PS/2 mouse device common for all mice
>> [   29.876081] input: AT Translated Set 2 keyboard as /class/input/input0
>> [   29.878901] cpuidle: using governor ladder
>> [   29.878904] cpuidle: using governor menu
>> [   29.878982] usbcore: registered new interface driver hiddev
>> [   29.879024] usbcore: registered new interface driver usbhid
>> [   29.879027] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
>> [   29.879098] TCP cubic registered
>> [   29.879100] Initializing XFRM netlink socket
>> [   29.879180] NET: Registered protocol family 1
>> [   29.879196] NET: Registered protocol family 17
>> [   29.879204] Using IPI No-Shortcut mode
>> [   29.879217] registered taskstats version 1
>> [   29.879349]   Magic number: 8:30:735
>> [   29.879657] Freeing unused kernel memory: 236k freed
>> [   29.879695] Write protecting the kernel text: 1940k
>> [   29.879708] Write protecting the kernel read-only data: 758k
>> [   30.175117] ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
>> [   30.175126] ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [APCL] -> GSI
>> 22 (level, high) -> IRQ 16 [   30.175139] PCI: Setting latency timer of
>> device 0000:00:02.2 to 64 [   30.175143] ehci_hcd 0000:00:02.2: EHCI Host
>> Controller
>> [   30.175235] ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus
>> number 1 [   30.175275] ehci_hcd 0000:00:02.2: debug port 1
>> [   30.175280] PCI: cache line size of 64 is not supported by device
>> 0000:00:02.2 [   30.175291] ehci_hcd 0000:00:02.2: irq 16, io mem
>> 0xe7005000
>> [   30.180677] ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver
>> 10 Dec 2004 [   30.180795] usb usb1: configuration #1 chosen from 1 choice
>> [   30.180823] hub 1-0:1.0: USB hub found
>> [   30.180834] hub 1-0:1.0: 6 ports detected
>> [   30.287626] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller
>> (OHCI) Driver [   30.288031] ACPI: PCI Interrupt Link [APCF] enabled at
>> IRQ 21
>> [   30.288038] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI
>> 21 (level, high) -> IRQ 17 [   30.288052] PCI: Setting latency timer of
>> device 0000:00:02.0 to 64 [   30.288055] ohci_hcd 0000:00:02.0: OHCI Host
>> Controller
>> [   30.288129] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus
>> number 2 [   30.288148] ohci_hcd 0000:00:02.0: irq 17, io mem 0xe7003000
>> [   30.340664] usb usb2: configuration #1 chosen from 1 choice
>> [   30.340691] hub 2-0:1.0: USB hub found
>> [   30.340704] hub 2-0:1.0: 3 ports detected
>> [   30.441860] ACPI: PCI Interrupt Link [APCG] enabled at IRQ 20
>> [   30.441865] ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCG] -> GSI
>> 20 (level, high) -> IRQ 18 [   30.441873] PCI: Setting latency timer of
>> device 0000:00:02.1 to 64 [   30.441876] ohci_hcd 0000:00:02.1: OHCI Host
>> Controller
>> [   30.441932] ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus
>> number 3 [   30.441945] ohci_hcd 0000:00:02.1: irq 18, io mem 0xe7004000
>> [   30.487468] usb 1-1: new high speed USB device using ehci_hcd and
>> address 2 [   30.494540] usb usb3: configuration #1 chosen from 1 choice
>> [   30.494569] hub 3-0:1.0: USB hub found
>> [   30.494579] hub 3-0:1.0: 3 ports detected
>> [   30.601427] USB Universal Host Controller Interface driver v3.0
>> [   30.601865] usb 1-1: configuration #1 chosen from 1 choice
>> [   30.602052] hub 1-1:1.0: USB hub found
>> [   30.602151] hub 1-1:1.0: 4 ports detected
>> [   30.660576] SCSI subsystem initialized
>> [   30.673851] Driver 'sd' needs updating - please use bus_type methods
>> [   30.700319] libata version 3.00 loaded.
>> [   30.702887] pata_amd 0000:00:09.0: version 0.3.10
>> [   30.703052] PCI: Setting latency timer of device 0000:00:09.0 to 64
>> [   30.703188] scsi0 : pata_amd
>> [   30.709313] scsi1 : pata_amd
>> [   30.710076] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000
>> irq 14 [   30.710079] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma
>> 0xf008 irq 15 [   30.864753] ata1.00: ATA-6: WDC WD2000JB-00EVA0,
>> 15.05R15, max UDMA/100 [   30.864756] ata1.00: 390721968 sectors, multi
>> 16: LBA48
>> [   30.871629] ata1.00: configured for UDMA/100
>> [   31.195305] ata2.00: ATAPI: LITE-ON DVDRW SHM-165H6S, HS06, max UDMA/66
>> [   31.243813] ata2.01: ATA-7: MAXTOR STM3320620A, 3.AAE, max UDMA/100
>> [   31.243816] ata2.01: 625142448 sectors, multi 16: LBA48
>> [   31.243825] ata2.00: limited to UDMA/33 due to 40-wire cable
>> [   31.417074] ata2.00: configured for UDMA/33
>> [   31.451769] ata2.01: configured for UDMA/100
>> [   31.451873] scsi 0:0:0:0: Direct-Access     ATA      WDC WD2000JB-00E
>> 15.0 PQ: 0 ANSI: 5 [   31.451953] sd 0:0:0:0: [sda] 390721968 512-byte
>> hardware sectors (200050 MB) [   31.451967] sd 0:0:0:0: [sda] Write
>> Protect is off
>> [   31.451970] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
>> [   31.451989] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
>> enabled, doesn't support DPO or FUA [   31.452040] sd 0:0:0:0: [sda]
>> 390721968 512-byte hardware sectors (200050 MB) [   31.452051] sd 0:0:0:0:
>> [sda] Write Protect is off
>> [   31.452054] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
>> [   31.452071] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
>> enabled, doesn't support DPO or FUA [   31.452075]  sda: sda1 sda2
>> [   31.467219] sd 0:0:0:0: [sda] Attached SCSI disk
>> [   31.468093] scsi 1:0:0:0: CD-ROM            LITE-ON  DVDRW SHM-165H6S
>> HS06 PQ: 0 ANSI: 5 [   31.468208] scsi 1:0:1:0: Direct-Access     ATA     
>> MAXTOR STM332062 3.AA PQ: 0 ANSI: 5 [   31.468272] sd 1:0:1:0: [sdb]
>> 625142448 512-byte hardware sectors (320073 MB) [   31.468283] sd 1:0:1:0:
>> [sdb] Write Protect is off
>> [   31.468286] sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
>> [   31.468303] sd 1:0:1:0: [sdb] Write cache: enabled, read cache:
>> enabled, doesn't support DPO or FUA [   31.468338] sd 1:0:1:0: [sdb]
>> 625142448 512-byte hardware sectors (320073 MB) [   31.468349] sd 1:0:1:0:
>> [sdb] Write Protect is off
>> [   31.468352] sd 1:0:1:0: [sdb] Mode Sense: 00 3a 00 00
>> [   31.468370] sd 1:0:1:0: [sdb] Write cache: enabled, read cache:
>> enabled, doesn't support DPO or FUA [   31.468373]  sdb:<6>usb 2-2: new
>> full speed USB device using ohci_hcd and address 2 [   31.499690]  sdb1
>> sdb2 sdb3
>> [   31.500119] sd 1:0:1:0: [sdb] Attached SCSI disk
>> [   31.637428] usb 2-2: configuration #1 chosen from 1 choice
>> [   31.856522] usb 2-3: new low speed USB device using ohci_hcd and
>> address 3 [   32.020045] usb 2-3: configuration #1 chosen from 1 choice
>> [   32.035222] input: Chicony Saitek Eclipse II Keyboard as
>> /class/input/input1 [   32.038424] input,hidraw0: USB HID v1.11 Keyboard
>> [Chicony Saitek Eclipse II Keyboard] on usb-0000:00:02.0-3 [   32.067995]
>> input: Chicony Saitek Eclipse II Keyboard as /class/input/input2 [  
>> 32.070422] input,hiddev96,hidraw1: USB HID v1.11 Device [Chicony Saitek
>> Eclipse II Keyboard] on usb-0000:00:02.0-3 [   32.287225] usb 3-3: new
>> full speed USB device using ohci_hcd and address 2 [   32.422699] usb 3-3:
>> configuration #1 chosen from 1 choice
>> [   32.425658] hub 3-3:1.0: USB hub found
>> [   32.428631] hub 3-3:1.0: 4 ports detected
>> [   32.724000] usb 1-1.1: new low speed USB device using ehci_hcd and
>> address 6 [   32.919001] usb 1-1.1: configuration #1 chosen from 1 choice
>> [   33.655893] hiddev97hidraw2: USB HID v1.11 Device [Belkin  Belkin UPS]
>> on usb-0000:00:02.2-1.1 [   33.833315] usb 1-1.2: new full speed USB
>> device using ehci_hcd and address 7 [   33.925926] usb 1-1.2:
>> configuration #1 chosen from 1 choice
>> [   34.018028] device-mapper: ioctl: 4.12.0-ioctl (2007-10-02)
>> initialised: dm-devel@redhat.com [   34.043070] sata_sil 0000:01:0a.0:
>> version 2.3
>> [   34.043348] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
>> [   34.043355] ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC1] -> GSI
>> 16 (level, high) -> IRQ 19 [   34.045029] scsi2 : sata_sil
>> [   34.050031] scsi3 : sata_sil
>> [   34.050064] ata3: SATA max UDMA/100 mmio m512@0xe6004000 tf 0xe6004080
>> irq 19 [   34.050068] ata4: SATA max UDMA/100 mmio m512@0xe6004000 tf
>> 0xe60040c0 irq 19 [   34.107056] usb 1-1.4: new high speed USB device
>> using ehci_hcd and address 8 [   34.192310] usb 1-1.4: configuration #1
>> chosen from 1 choice
>> [   34.192499] hub 1-1.4:1.0: USB hub found
>> [   34.192597] hub 1-1.4:1.0: 4 ports detected
>> [   34.352811] ata3: SATA link down (SStatus 0 SControl 310)
>> [   34.481823] usb 1-1.4.3: new low speed USB device using ehci_hcd and
>> address 9 [   34.573676] usb 1-1.4.3: configuration #1 chosen from 1
>> choice [   34.577917] input: Logitech USB Receiver as /class/input/input3
>> [   34.580691] input,hidraw3: USB HID v1.10 Mouse [Logitech USB Receiver]
>> on usb-0000:00:02.2-1.4.3 [   34.757557] usb 1-1.4.4: new full speed USB
>> device using ehci_hcd and address 10 [   34.806514] ata4: SATA link up 1.5
>> Gbps (SStatus 113 SControl 310) [   34.810071] ata4.00: ATA-7: Hitachi
>> HDT725040VLA360, V5COA7EA, max UDMA/133 [   34.810074] ata4.00: 781422768
>> sectors, multi 16: LBA48 NCQ (depth 0/32) [   34.816059] ata4.00:
>> configured for UDMA/100
>> [   34.816175] scsi 3:0:0:0: Direct-Access     ATA      Hitachi HDT72504
>> V5CO PQ: 0 ANSI: 5 [   34.816257] sd 3:0:0:0: [sdc] 781422768 512-byte
>> hardware sectors (400088 MB) [   34.816271] sd 3:0:0:0: [sdc] Write
>> Protect is off
>> [   34.816274] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
>> [   34.816293] sd 3:0:0:0: [sdc] Write cache: enabled, read cache:
>> enabled, doesn't support DPO or FUA [   34.816344] sd 3:0:0:0: [sdc]
>> 781422768 512-byte hardware sectors (400088 MB) [   34.816355] sd 3:0:0:0:
>> [sdc] Write Protect is off
>> [   34.816358] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
>> [   34.816375] sd 3:0:0:0: [sdc] Write cache: enabled, read cache:
>> enabled, doesn't support DPO or FUA [   34.816379]  sdc: sdc1
>> [   34.829837] sd 3:0:0:0: [sdc] Attached SCSI disk
>> [   34.843933] usb 1-1.4.4: configuration #1 chosen from 1 choice
>> [   37.852458] EXT3-fs: INFO: recovery required on readonly filesystem.
>> [   37.852464] EXT3-fs: write access will be enabled during recovery.
>> [   41.522866] kjournald starting.  Commit interval 5 seconds
>> [   41.522885] EXT3-fs: recovery complete.
>> [   41.524254] EXT3-fs: mounted filesystem with ordered data mode.
>> [   41.972449] audit(1201524201.103:2): enforcing=1 old_enforcing=0
>> auid=4294967295 [   42.187011] SELinux:8192 avtab hash slots allocated.Num
>> of rules:213166 [   42.260611] SELinux:8192 avtab hash slots allocated.Num
>> of rules:213166 [   42.314117] security:  8 users, 11 roles, 2363 types,
>> 114 bools, 1 sens, 1024 cats [   42.314122] security:  67 classes, 213166
>> rules
>> [   42.327287] SELinux:  Completing initialization.
>> [   42.327290] SELinux:  Setting up existing superblocks.
>> [   42.353550] SELinux: initialized (dev dm-0, type ext3), uses xattr
>> [   42.515071] SELinux: initialized (dev usbfs, type usbfs), uses
>> genfs_contexts [   42.515088] SELinux: initialized (dev tmpfs, type
>> tmpfs), uses transition SIDs [   42.515193] SELinux: initialized (dev
>> debugfs, type debugfs), uses genfs_contexts [   42.515205] SELinux:
>> initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts [  
>> 42.515235] SELinux: initialized (dev mqueue, type mqueue), uses transition
>> SIDs [   42.515244] SELinux: initialized (dev hugetlbfs, type hugetlbfs),
>> uses genfs_contexts [   42.515250] SELinux: initialized (dev devpts, type
>> devpts), uses transition SIDs [   42.515262] SELinux: initialized (dev
>> inotifyfs, type inotifyfs), uses genfs_contexts [   42.515266] SELinux:
>> initialized (dev tmpfs, type tmpfs), uses transition SIDs [   42.515274]
>> SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts [  
>> 42.515280] SELinux: initialized (dev anon_inodefs, type anon_inodefs),
>> uses genfs_contexts [   42.515285] SELinux: initialized (dev pipefs, type
>> pipefs), uses task SIDs [   42.515290] SELinux: initialized (dev sockfs,
>> type sockfs), uses task SIDs [   42.515299] SELinux: initialized (dev
>> proc, type proc), uses genfs_contexts [   42.515312] SELinux: initialized
>> (dev bdev, type bdev), uses genfs_contexts [   42.515318] SELinux:
>> initialized (dev rootfs, type rootfs), uses genfs_contexts [   42.515341]
>> SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts [  
>> 42.520002] SELinux: policy loaded with handle_unknown=allow
>> [   42.520011] audit(1201524201.651:3): policy loaded auid=4294967295
>> [   46.528101] sd 0:0:0:0: Attached scsi generic sg0 type 0
>> [   46.528126] scsi 1:0:0:0: Attached scsi generic sg1 type 5
>> [   46.528149] sd 1:0:1:0: Attached scsi generic sg2 type 0
>> [   46.528174] sd 3:0:0:0: Attached scsi generic sg3 type 0
>> [   46.931288] input: Power Button (FF) as /class/input/input4
>> [   46.938141] ACPI: Power Button (FF) [PWRF]
>> [   46.938186] ACPI Error (evxfevnt-0186): Could not enable SleepButton
>> event [20070126] [   46.938192] ACPI Warning (evxface-0145): Could not
>> enable fixed event 3 [20070126] [   46.938283] input: Power Button (CM) as
>> /class/input/input5
>> [   46.941132] ACPI: Power Button (CM) [PWRB]
>> [   46.941190] input: Sleep Button (CM) as /class/input/input6
>> [   46.944347] ACPI: Sleep Button (CM) [SLPB]
>> [   47.285717] usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2
>> vid 0x04B8 pid 0x0005 [   47.285742] usbcore: registered new interface
>> driver usblp
>> [   47.308848] i2c-adapter i2c-0: nForce2 SMBus adapter at 0x5000
>> [   47.308876] i2c-adapter i2c-1: nForce2 SMBus adapter at 0x5100
>> [   47.352146] usbcore: registered new interface driver usbserial
>> [   47.352152] drivers/usb/serial/usb-serial.c: USB Serial Driver core
>> [   47.455275] drivers/usb/serial/usb-serial.c: USB Serial support
>> registered for FTDI USB Serial Device [   47.455308] ftdi_sio 1-1.2:1.0:
>> FTDI USB Serial Device converter detected [   47.455342]
>> drivers/usb/serial/ftdi_sio.c: Detected FT232RL
>> [   47.455381] usb 1-1.2: FTDI USB Serial Device converter now attached to
>> ttyUSB0 [   47.455398] usbcore: registered new interface driver ftdi_sio
>> [   47.455401] drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial
>> Converters Driver [   47.530751] input: PC Speaker as /class/input/input7
>> [   47.572764] forcedeth: Reverse Engineered nForce ethernet driver.
>> Version 0.61. [   47.573147] ACPI: PCI Interrupt Link [APCH] enabled at
>> IRQ 22
>> [   47.573151] ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCH] -> GSI
>> 22 (level, high) -> IRQ 16 [   47.573158] PCI: Setting latency timer of
>> device 0000:00:04.0 to 64 [   47.615492] Floppy drive(s): fd0 is 1.44M
>> [   47.630509] FDC 0 is a post-1991 82077
>> [   48.084769] forcedeth 0000:00:04.0: ifname eth0, PHY OUI 0x20 @ 1, addr
>> 00:04:4b:5d:eb:7d [   48.084775] forcedeth 0000:00:04.0: timirq lnktim
>> desc-v1
>> [   48.085214] ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
>> [   48.085222] ACPI: PCI Interrupt 0000:01:09.0[A] -> Link [APC4] -> GSI
>> 19 (level, high) -> IRQ 20 [   48.141308] firewire_ohci: Added fw-ohci
>> device 0000:01:09.0, OHCI version 1.10 [   48.285456] nvidia: module
>> license 'NVIDIA' taints kernel.
>> [   48.549725] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI
>> 19 (level, high) -> IRQ 20 [   48.550149] NVRM: loading NVIDIA UNIX x86
>> Kernel Module  169.07  Thu Dec 13 18:42:56 PST 2007 [   48.641028]
>> firewire_core: created new fw device fw0 (0 config rom retries, S400) [  
>> 48.848094] Linux video capture interface: v2.00
>> [   49.104974] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
>> [   49.105072] cx88[0]: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV
>> [card=22,autodetected] [   49.105076] cx88[0]: TV tuner type 60, Radio
>> tuner type -1
>> [   49.151205] cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
>> [   49.255507] cx88[0]/2: cx2388x 8802 Driver Manager
>> [   49.257461] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
>> [   49.257472] ACPI: PCI Interrupt 0000:01:07.2[A] -> Link [APC2] -> GSI
>> 17 (level, high) -> IRQ 21 [   49.257484] cx88[0]/2: found at
>> 0000:01:07.2, rev: 5, irq: 21, latency: 32, mmio: 0xe4000000 [  
>> 49.257561] ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC2] -> GSI 17
>> (level, high) -> IRQ 21 [   49.257573] cx88[0]/0: found at 0000:01:07.0,
>> rev: 5, irq: 21, latency: 32, mmio: 0xe3000000 [   49.440179]
>> tda8290_probe: not probed - driver disabled by Kconfig [   49.440185]
>> tuner 2-0043: chip found @ 0x86 (cx88[0])
>> [   49.440208] tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
>> [   49.440211] tuner 2-0043: type set to tda9887
>> [   49.442442] tuner 2-0061: chip found @ 0xc2 (cx88[0])
>> [   49.442458] tuner-simple 2-0061: type set to 60 (Thomson DTT 761X
>> (ATSC/NTSC)) [   49.442461] tuner 2-0061: type set to Thomson DTT 761X (A
>> [   49.442464] tuner-simple 2-0061: type set to 60 (Thomson DTT 761X
>> (ATSC/NTSC)) [   49.442466] tuner 2-0061: type set to Thomson DTT 761X (A
>> [   49.451016] cx88[0]/0: registered device video0 [v4l2]
>> [   49.451038] cx88[0]/0: registered device vbi0
>> [   49.451064] cx88[0]/0: registered device radio0
>> [   49.454722] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
>> [   49.454731] ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC3] -> GSI
>> 18 (level, high) -> IRQ 22 [   49.459555] Audigy2 value: Special config.
>> [   49.532042] cx88/2: cx2388x dvb driver version 0.0.6 loaded
>> [   49.532047] cx88/2: registering cx8802 driver, type: dvb access: shared
>> [   49.532052] cx88[0]/2: subsystem: 7063:3000, board: pcHDTV HD3000 HDTV
>> [card=22] [   49.532055] cx88[0]/2: cx2388x based DVB/ATSC card
>> [   49.548119] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 21
>> [   49.548125] ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI
>> 21 (level, high) -> IRQ 17 [   49.548162] PCI: Setting latency timer of
>> device 0000:00:06.0 to 64 [   49.654575] DVB: registering new adapter
>> (cx88[0])
>> [   49.654582] DVB: registering frontend 0 (Oren OR51132 VSB/QAM
>> Frontend)... [   49.859126] intel8x0_measure_ac97_clock: measured 50668
>> usecs
>> [   49.859131] intel8x0: clocking to 47378
>> [   52.910654] EXT3 FS on dm-0, internal journal
>> [   53.162621] kjournald starting.  Commit interval 5 seconds
>> [   53.170013] EXT3 FS on sda1, internal journal
>> [   53.170019] EXT3-fs: mounted filesystem with ordered data mode.
>> [   53.170144] SELinux: initialized (dev sda1, type ext3), uses xattr
>> [   53.170540] SELinux: initialized (dev tmpfs, type tmpfs), uses
>> transition SIDs [   53.174936] kjournald starting.  Commit interval 5
>> seconds
>> [   53.182987] EXT3 FS on sdc1, internal journal
>> [   53.182992] EXT3-fs: mounted filesystem with ordered data mode.
>> [   53.188827] SELinux: initialized (dev sdc1, type ext3), uses xattr
>> [   54.005729] Adding 2031608k swap on /dev/mapper/VolGroup00-LogVol01. 
>> Priority:-1 extents:1 across:2031608k [   54.009417] SELinux: initialized
>> (dev binfmt_misc, type binfmt_misc), uses genfs_contexts



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"People should have access to the data which you have about them.  There 
should
 be a process for them to challenge any inaccuracies."
-- Arthur Miller

Re: Problem with ata layer in 2.6.24

[Mark Lord]

Gene Heskett wrote:
> Greeting;
> 
> I had to reboot early this morning due to a freezeup, and I had a 
> bunch of these in the messages log:
> ==============
> Jan 27 19:42:11 coyote kernel: [42461.915961] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Jan 27 19:42:11 coyote kernel: [42461.915973] ata1.00: cmd ca/00:08:b1:66:46/00:00:00:00:00/e8 tag 0 dma 4096 out
> Jan 27 19:42:11 coyote kernel: [42461.915974]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> Jan 27 19:42:11 coyote kernel: [42461.915978] ata1.00: status: { DRDY }
> Jan 27 19:42:11 coyote kernel: [42461.916005] ata1: soft resetting link
> Jan 27 19:42:12 coyote kernel: [42462.078216] ata1.00: configured for UDMA/100
> Jan 27 19:42:12 coyote kernel: [42462.078232] ata1: EH complete
> Jan 27 19:42:12 coyote kernel: [42462.090700] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
> Jan 27 19:42:12 coyote kernel: [42462.114230] sd 0:0:0:0: [sda] Write Protect is off
> Jan 27 19:42:12 coyote kernel: [42462.115079] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
> support DPO or FUA
> ===============
> That one showed up about 2 hours ago, so I expect I'll be locked 
> up again before I've managed a 24 hour uptime.  This drive passed
> a 'smartctl -t long /dev/sda' with flying colors after the reboot
> this morning.
> 
> Two instances were logged after I had rebooted to 2.6.24 from 2.6.24-rc8:
> 
> Jan 24 20:46:33 coyote kernel: [    0.000000] Linux version 2.6.24 (root@coyote.coyote.den) (gcc version 4.1.2 20070925 
> (Red Hat 4.1.2-33)) #1 SMP Thu Jan 24 20:17:55 EST 2008
> ----
> Jan 27 02:28:29 coyote kernel: [193207.445158] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Jan 27 02:28:29 coyote kernel: [193207.445170] ata1.00: cmd 35/00:08:f9:24:0a/00:00:17:00:00/e0 tag 0 dma 4096 out
> Jan 27 02:28:29 coyote kernel: [193207.445172]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> Jan 27 02:28:29 coyote kernel: [193207.445175] ata1.00: status: { DRDY }
> Jan 27 02:28:29 coyote kernel: [193207.445202] ata1: soft resetting link
> Jan 27 02:28:29 coyote kernel: [193207.607384] ata1.00: configured for UDMA/100
> Jan 27 02:28:29 coyote kernel: [193207.607399] ata1: EH complete
> Jan 27 02:28:29 coyote kernel: [193207.609681] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
> Jan 27 02:28:29 coyote kernel: [193207.619277] sd 0:0:0:0: [sda] Write Protect is off
> Jan 27 02:28:29 coyote kernel: [193207.649041] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
> support DPO or FUA
> Jan 27 02:30:06 coyote kernel: [193304.336929] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Jan 27 02:30:06 coyote kernel: [193304.336940] ata1.00: cmd ca/00:20:69:22:a6/00:00:00:00:00/e7 tag 0 dma 16384 out
> Jan 27 02:30:06 coyote kernel: [193304.336942]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> Jan 27 02:30:06 coyote kernel: [193304.336945] ata1.00: status: { DRDY }
> Jan 27 02:30:06 coyote kernel: [193304.336972] ata1: soft resetting link
> Jan 27 02:30:06 coyote kernel: [193304.499210] ata1.00: configured for UDMA/100
> Jan 27 02:30:06 coyote kernel: [193304.499226] ata1: EH complete
> Jan 27 02:30:06 coyote kernel: [193304.499714] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
> Jan 27 02:30:06 coyote kernel: [193304.499857] sd 0:0:0:0: [sda] Write Protect is off
> Jan 27 02:30:06 coyote kernel: [193304.502315] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
> support DPO or FUA
> 
> None were logged during the time I was running an -rc7 or -rc8.
> 
> The previous hits on this resulted in the udma speed being downgraded 
> till it was actually running in pio just before the freeze that 
> required the hardware reset button.
> 
> I'll reboot to -rc8 right now and resume.  If its the drive, I should see it.
> If not, then 2.6.24 is where I'll point the finger.
..

The only libata change I can see that could possibly affect your setup,
is this one here, which went in sometime between -rc7 and -final:

--- linux-2.6.24-rc7/drivers/ata/libata-eh.c    2008-01-06 16:45:38.000000000 -0500
+++ linux-2.6.24/drivers/ata/libata-eh.c        2008-01-24 17:58:37.000000000 -0500
@@ -1733,11 +1733,15 @@
                ehc->i.action &= ~ATA_EH_PERDEV_MASK;
        }

-       /* consider speeding down */
+       /* propagate timeout to host link */
+       if ((all_err_mask & AC_ERR_TIMEOUT) && !ata_is_host_link(link))
+               ap->link.eh_context.i.err_mask |= AC_ERR_TIMEOUT;
+

It looks pretty innocent to me, though.
If you want to try reverting just that change
(comment out the two lines and rebuild),
then that might provide useful information here.

If -final is still b0rked even with those two lines changed back,
then I suspect you're just "getting lucky" when switching between
the -rc7/-rc8 kernel and the -final kernel.

"Lucky" in a bad way, that is.

The real test would be to rebuild the kernel without libata,
and *with* the old IDE driver instead, and see if the problems persist.

If you need help with that, then perhaps someone familiar with Fedora
might be able to assist.

Cheers 

Re: Problem with ata layer in 2.6.24

[Mark Lord]

Gene Heskett wrote:
> Greeting;
>
> I had to reboot early this morning due to a freezeup, and I had a bunch of these in the messages log:
> ==============
> Jan 27 19:42:11 coyote kernel: [42461.915961] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Jan 27 19:42:11 coyote kernel: [42461.915973] ata1.00: cmd ca/00:08:b1:66:46/00:00:00:00:00/e8 tag 0 dma 4096 out
> Jan 27 19:42:11 coyote kernel: [42461.915974]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> Jan 27 19:42:11 coyote kernel: [42461.915978] ata1.00: status: { DRDY }
> Jan 27 19:42:11 coyote kernel: [42461.916005] ata1: soft resetting link
> Jan 27 19:42:12 coyote kernel: [42462.078216] ata1.00: configured for UDMA/100
> Jan 27 19:42:12 coyote kernel: [42462.078232] ata1: EH complete
> Jan 27 19:42:12 coyote kernel: [42462.090700] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
> Jan 27 19:42:12 coyote kernel: [42462.114230] sd 0:0:0:0: [sda] Write Protect is off
> Jan 27 19:42:12 coyote kernel: [42462.115079] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> ===============
> That one showed up about 2 hours ago, so I expect I'll be locked up again before I've managed a 24 hour uptime.  This drive passed
> a 'smartctl -t long /dev/sda' with flying colors after the reboot
> this morning.
>
> Two instances were logged after I had rebooted to 2.6.24 from 2.6.24-rc8:
>
> Jan 24 20:46:33 coyote kernel: [    0.000000] Linux version 2.6.24 (root@coyote.coyote.den) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Thu Jan 24 20:17:55 EST 2008
> ----
> Jan 27 02:28:29 coyote kernel: [193207.445158] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Jan 27 02:28:29 coyote kernel: [193207.445170] ata1.00: cmd 35/00:08:f9:24:0a/00:00:17:00:00/e0 tag 0 dma 4096 out
> Jan 27 02:28:29 coyote kernel: [193207.445172]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> Jan 27 02:28:29 coyote kernel: [193207.445175] ata1.00: status: { DRDY }
> Jan 27 02:28:29 coyote kernel: [193207.445202] ata1: soft resetting link
> Jan 27 02:28:29 coyote kernel: [193207.607384] ata1.00: configured for UDMA/100
> Jan 27 02:28:29 coyote kernel: [193207.607399] ata1: EH complete
> Jan 27 02:28:29 coyote kernel: [193207.609681] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
> Jan 27 02:28:29 coyote kernel: [193207.619277] sd 0:0:0:0: [sda] Write Protect is off
> Jan 27 02:28:29 coyote kernel: [193207.649041] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> Jan 27 02:30:06 coyote kernel: [193304.336929] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Jan 27 02:30:06 coyote kernel: [193304.336940] ata1.00: cmd ca/00:20:69:22:a6/00:00:00:00:00/e7 tag 0 dma 16384 out
> Jan 27 02:30:06 coyote kernel: [193304.336942]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> Jan 27 02:30:06 coyote kernel: [193304.336945] ata1.00: status: { DRDY }
> Jan 27 02:30:06 coyote kernel: [193304.336972] ata1: soft resetting link
> Jan 27 02:30:06 coyote kernel: [193304.499210] ata1.00: configured for UDMA/100
> Jan 27 02:30:06 coyote kernel: [193304.499226] ata1: EH complete
> Jan 27 02:30:06 coyote kernel: [193304.499714] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
> Jan 27 02:30:06 coyote kernel: [193304.499857] sd 0:0:0:0: [sda] Write Protect is off
> Jan 27 02:30:06 coyote kernel: [193304.502315] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
>
> None were logged during the time I was running an -rc7 or -rc8.
>
> The previous hits on this resulted in the udma speed being downgraded till it was actually running in pio just before the freeze that required the hardware reset button.
>
> I'll reboot to -rc8 right now and resume.  If its the drive, I should see it.
> If not, then 2.6.24 is where I'll point the finger.
..

The only libata change I can see that could possibly affect your setup,
is this one here, which went in sometime between -rc7 and -final:

--- linux-2.6.24-rc7/drivers/ata/libata-eh.c    2008-01-06 16:45:38.000000000 -0500
+++ linux-2.6.24/drivers/ata/libata-eh.c        2008-01-24 17:58:37.000000000 -0500
@@ -1733,11 +1733,15 @@
               ehc->i.action &= ~ATA_EH_PERDEV_MASK;
       }

-       /* consider speeding down */
+       /* propagate timeout to host link */
+       if ((all_err_mask & AC_ERR_TIMEOUT) && !ata_is_host_link(link))
+               ap->link.eh_context.i.err_mask |= AC_ERR_TIMEOUT;
+

It looks pretty innocent to me, though.
If you want to try reverting just that change
(comment out the two lines and rebuild),
then that might provide useful information here.

If -final is still b0rked even with those two lines changed back,
then I suspect you're just "getting lucky" when switching between
the -rc7/-rc8 kernel and the -final kernel.

"Lucky" in a bad way, that is.

The real test would be to rebuild the kernel without libata,
and *with* the old IDE driver instead, and see if the problems persist.

If you need help with that, then perhaps someone familiar with Fedora
might be able to assist.

Cheers

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Mark Lord wrote:
>Gene Heskett wrote:
>> Greeting;
>>
>> I had to reboot early this morning due to a freezeup, and I had a
>> bunch of these in the messages log:
>> ==============
>> Jan 27 19:42:11 coyote kernel: [42461.915961] ata1.00: exception Emask 0x0
>> SAct 0x0 SErr 0x0 action 0x2 frozen Jan 27 19:42:11 coyote kernel:
>> [42461.915973] ata1.00: cmd ca/00:08:b1:66:46/00:00:00:00:00/e8 tag 0 dma
>> 4096 out Jan 27 19:42:11 coyote kernel: [42461.915974]          res
>> 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 27 19:42:11
>> coyote kernel: [42461.915978] ata1.00: status: { DRDY } Jan 27 19:42:11
>> coyote kernel: [42461.916005] ata1: soft resetting link Jan 27 19:42:12
>> coyote kernel: [42462.078216] ata1.00: configured for UDMA/100 Jan 27
>> 19:42:12 coyote kernel: [42462.078232] ata1: EH complete
>> Jan 27 19:42:12 coyote kernel: [42462.090700] sd 0:0:0:0: [sda] 390721968
>> 512-byte hardware sectors (200050 MB) Jan 27 19:42:12 coyote kernel:
>> [42462.114230] sd 0:0:0:0: [sda] Write Protect is off Jan 27 19:42:12
>> coyote kernel: [42462.115079] sd 0:0:0:0: [sda] Write cache: enabled, read
>> cache: enabled, doesn't support DPO or FUA
>> ===============
>> That one showed up about 2 hours ago, so I expect I'll be locked
>> up again before I've managed a 24 hour uptime.  This drive passed
>> a 'smartctl -t long /dev/sda' with flying colors after the reboot
>> this morning.
>>
>> Two instances were logged after I had rebooted to 2.6.24 from 2.6.24-rc8:
>>
>> Jan 24 20:46:33 coyote kernel: [    0.000000] Linux version 2.6.24
>> (root@coyote.coyote.den) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33))
>> #1 SMP Thu Jan 24 20:17:55 EST 2008
>> ----
>> Jan 27 02:28:29 coyote kernel: [193207.445158] ata1.00: exception Emask
>> 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Jan 27 02:28:29 coyote kernel:
>> [193207.445170] ata1.00: cmd 35/00:08:f9:24:0a/00:00:17:00:00/e0 tag 0 dma
>> 4096 out Jan 27 02:28:29 coyote kernel: [193207.445172]          res
>> 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 27 02:28:29
>> coyote kernel: [193207.445175] ata1.00: status: { DRDY } Jan 27 02:28:29
>> coyote kernel: [193207.445202] ata1: soft resetting link Jan 27 02:28:29
>> coyote kernel: [193207.607384] ata1.00: configured for UDMA/100 Jan 27
>> 02:28:29 coyote kernel: [193207.607399] ata1: EH complete
>> Jan 27 02:28:29 coyote kernel: [193207.609681] sd 0:0:0:0: [sda] 390721968
>> 512-byte hardware sectors (200050 MB) Jan 27 02:28:29 coyote kernel:
>> [193207.619277] sd 0:0:0:0: [sda] Write Protect is off Jan 27 02:28:29
>> coyote kernel: [193207.649041] sd 0:0:0:0: [sda] Write cache: enabled,
>> read cache: enabled, doesn't support DPO or FUA
>> Jan 27 02:30:06 coyote kernel: [193304.336929] ata1.00: exception Emask
>> 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Jan 27 02:30:06 coyote kernel:
>> [193304.336940] ata1.00: cmd ca/00:20:69:22:a6/00:00:00:00:00/e7 tag 0 dma
>> 16384 out Jan 27 02:30:06 coyote kernel: [193304.336942]          res
>> 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 27 02:30:06
>> coyote kernel: [193304.336945] ata1.00: status: { DRDY } Jan 27 02:30:06
>> coyote kernel: [193304.336972] ata1: soft resetting link Jan 27 02:30:06
>> coyote kernel: [193304.499210] ata1.00: configured for UDMA/100 Jan 27
>> 02:30:06 coyote kernel: [193304.499226] ata1: EH complete
>> Jan 27 02:30:06 coyote kernel: [193304.499714] sd 0:0:0:0: [sda] 390721968
>> 512-byte hardware sectors (200050 MB) Jan 27 02:30:06 coyote kernel:
>> [193304.499857] sd 0:0:0:0: [sda] Write Protect is off Jan 27 02:30:06
>> coyote kernel: [193304.502315] sd 0:0:0:0: [sda] Write cache: enabled,
>> read cache: enabled, doesn't support DPO or FUA
>>
>> None were logged during the time I was running an -rc7 or -rc8.
>>
>> The previous hits on this resulted in the udma speed being downgraded
>> till it was actually running in pio just before the freeze that
>> required the hardware reset button.
>>
>> I'll reboot to -rc8 right now and resume.  If its the drive, I should see
>> it. If not, then 2.6.24 is where I'll point the finger.
>
>..
>
>The only libata change I can see that could possibly affect your setup,
>is this one here, which went in sometime between -rc7 and -final:
>
>--- linux-2.6.24-rc7/drivers/ata/libata-eh.c    2008-01-06
> 16:45:38.000000000 -0500 +++ linux-2.6.24/drivers/ata/libata-eh.c       
> 2008-01-24 17:58:37.000000000 -0500 @@ -1733,11 +1733,15 @@
>                ehc->i.action &= ~ATA_EH_PERDEV_MASK;
>        }
>
>-       /* consider speeding down */
>+       /* propagate timeout to host link */
>+       if ((all_err_mask & AC_ERR_TIMEOUT) && !ata_is_host_link(link))
>+               ap->link.eh_context.i.err_mask |= AC_ERR_TIMEOUT;
>+
>
>It looks pretty innocent to me, though.
>If you want to try reverting just that change
>(comment out the two lines and rebuild),
>then that might provide useful information here.
>
>If -final is still b0rked even with those two lines changed back,
>then I suspect you're just "getting lucky" when switching between
>the -rc7/-rc8 kernel and the -final kernel.
>
>"Lucky" in a bad way, that is.
>
>The real test would be to rebuild the kernel without libata,
>and *with* the old IDE driver instead, and see if the problems persist.

I can do that, but going to this was pretty painfull, probably 5 or 6 reboots 
to get it right.

And so far no one has tried to comment on those 2 dmesg lines I've quoted a 
couple of times now, here's another:
[    0.000000] Nvidia board detected. Ignoring ACPI timer override.
[    0.000000] If you got timer trouble try acpi_use_timer_override
what the heck is that trying to tell me to do, in some sort of broken english?


>If you need help with that, then perhaps someone familiar with Fedora
>might be able to assist.
>
>Cheers



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
I used to be disgusted, now I find I'm just amused.
		-- Elvis Costello

Re: Problem with ata layer in 2.6.24

[Mark Lord]

Gene Heskett wrote:
>..
> And so far no one has tried to comment on those 2 dmesg lines I've quoted a 
> couple of times now, here's another:
> [    0.000000] Nvidia board detected. Ignoring ACPI timer override.
> [    0.000000] If you got timer trouble try acpi_use_timer_override
> what the heck is that trying to tell me to do, in some sort of broken english?
..

I think it says this:

  "If your system is misbehaving, then try adding the acpi_use_timer_override
   keyword to your kernel command line (/boot/grub/menu.lst) and see if it helps."

So, you can either hardcode it in /boot/grub/menu.lst (just add it to the end
of the first line you see there that begins with the word "kernel".

Or you can just try it temporarily at boot time (safer, but tricker),
by catching GRUB (the bootloader) before it actually loads Linux.

Usually there's some key or something it says you have 3 seconds to hit for a "menu",
so do that, and then use the cursor keys to find the first "kernel" line in that menu
and hit "e" (edit) to go and add the acpi_use_timer_override keyword to the end of
that line (same as above).

Hit enter when done, and then the letter b (boot) to load Linux with that option.

Clear as mud, right?  :)

Re: Problem with ata layer in 2.6.24

[Mark Lord]

Mark Lord wrote:
> Gene Heskett wrote:
>> ..
>> And so far no one has tried to comment on those 2 dmesg lines I've quoted a couple of times now, here's another:
>> [    0.000000] Nvidia board detected. Ignoring ACPI timer override.
>> [    0.000000] If you got timer trouble try acpi_use_timer_override
>> what the heck is that trying to tell me to do, in some sort of broken english?
> ..
> 
> I think it says this:
> 
>  "If your system is misbehaving, then try adding the acpi_use_timer_override
>   keyword to your kernel command line (/boot/grub/menu.lst) and see if it helps."
> 
> So, you can either hardcode it in /boot/grub/menu.lst (just add it to the end
> of the first line you see there that begins with the word "kernel".
> 
> Or you can just try it temporarily at boot time (safer, but tricker),
> by catching GRUB (the bootloader) before it actually loads Linux.
> 
> Usually there's some key or something it says you have 3 seconds to hit for a "menu",
> so do that, and then use the cursor keys to find the first "kernel" line in that menu
> and hit "e" (edit) to go and add the acpi_use_timer_override keyword to the end of
> that line (same as above).
..

Minor correction (having just tried it here):  once you see the GRUB (boot) menu,
hit the letter e to edit the first entry, then scroll to the "kernel" line,
and hit the letter e again to edit that line.  It should put you at the end of the
line, where you can just type a space and then acpi_use_timer_override and then
hit enter to finish the (temporary) edit.  Then hit b for boot.

-ml

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Mark Lord wrote:
>Gene Heskett wrote:
>>..
>> And so far no one has tried to comment on those 2 dmesg lines I've quoted
>> a couple of times now, here's another:
>> [    0.000000] Nvidia board detected. Ignoring ACPI timer override.
>> [    0.000000] If you got timer trouble try acpi_use_timer_override
>> what the heck is that trying to tell me to do, in some sort of broken
>> english?
>
>..
>
>I think it says this:
>
>  "If your system is misbehaving, then try adding the
> acpi_use_timer_override keyword to your kernel command line
> (/boot/grub/menu.lst) and see if it helps."
>
>So, you can either hardcode it in /boot/grub/menu.lst (just add it to the
> end of the first line you see there that begins with the word "kernel".
>
>Or you can just try it temporarily at boot time (safer, but tricker),
>by catching GRUB (the bootloader) before it actually loads Linux.
>
>Usually there's some key or something it says you have 3 seconds to hit for
> a "menu", so do that, and then use the cursor keys to find the first
> "kernel" line in that menu and hit "e" (edit) to go and add the
> acpi_use_timer_override keyword to the end of that line (same as above).
>
>Hit enter when done, and then the letter b (boot) to load Linux with that
> option.
>
>Clear as mud, right?  :)

Precisely Mark.  Thanks, I'm building an ide-ata kernel 2.6.24 now, and I've 
added that to the argument line for 2.6.24-rc8.

Thanks mark.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Of all men's miseries, the bitterest is this:
to know so much and have control over nothing.
		-- Herodotus

Re: Problem with ata layer in 2.6.24

[Jeff Garzik]

Gene Heskett wrote:
> Greeting;
> 
> I had to reboot early this morning due to a freezeup, and I had a 
> bunch of these in the messages log:
> ==============
> Jan 27 19:42:11 coyote kernel: [42461.915961] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Jan 27 19:42:11 coyote kernel: [42461.915973] ata1.00: cmd ca/00:08:b1:66:46/00:00:00:00:00/e8 tag 0 dma 4096 out
> Jan 27 19:42:11 coyote kernel: [42461.915974]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> Jan 27 19:42:11 coyote kernel: [42461.915978] ata1.00: status: { DRDY }
> Jan 27 19:42:11 coyote kernel: [42461.916005] ata1: soft resetting link
> Jan 27 19:42:12 coyote kernel: [42462.078216] ata1.00: configured for UDMA/100
> Jan 27 19:42:12 coyote kernel: [42462.078232] ata1: EH complete
> Jan 27 19:42:12 coyote kernel: [42462.090700] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
> Jan 27 19:42:12 coyote kernel: [42462.114230] sd 0:0:0:0: [sda] Write Protect is off
> Jan 27 19:42:12 coyote kernel: [42462.115079] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
> support DPO or FUA
> ===============
> That one showed up about 2 hours ago, so I expect I'll be locked 
> up again before I've managed a 24 hour uptime.  This drive passed
> a 'smartctl -t long /dev/sda' with flying colors after the reboot
> this morning.
> 
> Two instances were logged after I had rebooted to 2.6.24 from 2.6.24-rc8:
> 
> Jan 24 20:46:33 coyote kernel: [    0.000000] Linux version 2.6.24 (root@coyote.coyote.den) (gcc version 4.1.2 20070925 
> (Red Hat 4.1.2-33)) #1 SMP Thu Jan 24 20:17:55 EST 2008
> ----
> Jan 27 02:28:29 coyote kernel: [193207.445158] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Jan 27 02:28:29 coyote kernel: [193207.445170] ata1.00: cmd 35/00:08:f9:24:0a/00:00:17:00:00/e0 tag 0 dma 4096 out
> Jan 27 02:28:29 coyote kernel: [193207.445172]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> Jan 27 02:28:29 coyote kernel: [193207.445175] ata1.00: status: { DRDY }
> Jan 27 02:28:29 coyote kernel: [193207.445202] ata1: soft resetting link
> Jan 27 02:28:29 coyote kernel: [193207.607384] ata1.00: configured for UDMA/100
> Jan 27 02:28:29 coyote kernel: [193207.607399] ata1: EH complete
> Jan 27 02:28:29 coyote kernel: [193207.609681] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
> Jan 27 02:28:29 coyote kernel: [193207.619277] sd 0:0:0:0: [sda] Write Protect is off
> Jan 27 02:28:29 coyote kernel: [193207.649041] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
> support DPO or FUA
> Jan 27 02:30:06 coyote kernel: [193304.336929] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> Jan 27 02:30:06 coyote kernel: [193304.336940] ata1.00: cmd ca/00:20:69:22:a6/00:00:00:00:00/e7 tag 0 dma 16384 out
> Jan 27 02:30:06 coyote kernel: [193304.336942]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> Jan 27 02:30:06 coyote kernel: [193304.336945] ata1.00: status: { DRDY }
> Jan 27 02:30:06 coyote kernel: [193304.336972] ata1: soft resetting link
> Jan 27 02:30:06 coyote kernel: [193304.499210] ata1.00: configured for UDMA/100
> Jan 27 02:30:06 coyote kernel: [193304.499226] ata1: EH complete
> Jan 27 02:30:06 coyote kernel: [193304.499714] sd 0:0:0:0: [sda] 390721968 512-byte hardware sectors (200050 MB)
> Jan 27 02:30:06 coyote kernel: [193304.499857] sd 0:0:0:0: [sda] Write Protect is off
> Jan 27 02:30:06 coyote kernel: [193304.502315] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't 
> support DPO or FUA
> 
> None were logged during the time I was running an -rc7 or -rc8.
> 
> The previous hits on this resulted in the udma speed being downgraded 
> till it was actually running in pio just before the freeze that 
> required the hardware reset button.

Unfortunately there are 1001 different causes for timeouts, so we need 
to drill down into the hardware, libata version, and ACPI version (most 
notably).


> I'll reboot to -rc8 right now and resume.  If its the drive, I should see it.
> If not, then 2.6.24 is where I'll point the finger.

There was also an ACPI update, which always affects interrupt handling 
(whose symptom can sometimes be a timeout).

Definitely interesting in test results from what you describe.

	Jeff

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Jeff Garzik wrote:
>Gene Heskett wrote:
>> Greeting;
>>
>> I had to reboot early this morning due to a freezeup, and I had a
>> bunch of these in the messages log:
>> ==============
>> Jan 27 19:42:11 coyote kernel: [42461.915961] ata1.00: exception Emask 0x0
>> SAct 0x0 SErr 0x0 action 0x2 frozen Jan 27 19:42:11 coyote kernel:
>> [42461.915973] ata1.00: cmd ca/00:08:b1:66:46/00:00:00:00:00/e8 tag 0 dma
>> 4096 out Jan 27 19:42:11 coyote kernel: [42461.915974]          res
>> 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 27 19:42:11
>> coyote kernel: [42461.915978] ata1.00: status: { DRDY } Jan 27 19:42:11
>> coyote kernel: [42461.916005] ata1: soft resetting link Jan 27 19:42:12
>> coyote kernel: [42462.078216] ata1.00: configured for UDMA/100 Jan 27
>> 19:42:12 coyote kernel: [42462.078232] ata1: EH complete
>> Jan 27 19:42:12 coyote kernel: [42462.090700] sd 0:0:0:0: [sda] 390721968
>> 512-byte hardware sectors (200050 MB) Jan 27 19:42:12 coyote kernel:
>> [42462.114230] sd 0:0:0:0: [sda] Write Protect is off Jan 27 19:42:12
>> coyote kernel: [42462.115079] sd 0:0:0:0: [sda] Write cache: enabled, read
>> cache: enabled, doesn't support DPO or FUA
>> ===============
>> That one showed up about 2 hours ago, so I expect I'll be locked
>> up again before I've managed a 24 hour uptime.  This drive passed
>> a 'smartctl -t long /dev/sda' with flying colors after the reboot
>> this morning.
>>
>> Two instances were logged after I had rebooted to 2.6.24 from 2.6.24-rc8:
>>
>> Jan 24 20:46:33 coyote kernel: [    0.000000] Linux version 2.6.24
>> (root@coyote.coyote.den) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33))
>> #1 SMP Thu Jan 24 20:17:55 EST 2008
>> ----
>> Jan 27 02:28:29 coyote kernel: [193207.445158] ata1.00: exception Emask
>> 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Jan 27 02:28:29 coyote kernel:
>> [193207.445170] ata1.00: cmd 35/00:08:f9:24:0a/00:00:17:00:00/e0 tag 0 dma
>> 4096 out Jan 27 02:28:29 coyote kernel: [193207.445172]          res
>> 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 27 02:28:29
>> coyote kernel: [193207.445175] ata1.00: status: { DRDY } Jan 27 02:28:29
>> coyote kernel: [193207.445202] ata1: soft resetting link Jan 27 02:28:29
>> coyote kernel: [193207.607384] ata1.00: configured for UDMA/100 Jan 27
>> 02:28:29 coyote kernel: [193207.607399] ata1: EH complete
>> Jan 27 02:28:29 coyote kernel: [193207.609681] sd 0:0:0:0: [sda] 390721968
>> 512-byte hardware sectors (200050 MB) Jan 27 02:28:29 coyote kernel:
>> [193207.619277] sd 0:0:0:0: [sda] Write Protect is off Jan 27 02:28:29
>> coyote kernel: [193207.649041] sd 0:0:0:0: [sda] Write cache: enabled,
>> read cache: enabled, doesn't support DPO or FUA
>> Jan 27 02:30:06 coyote kernel: [193304.336929] ata1.00: exception Emask
>> 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Jan 27 02:30:06 coyote kernel:
>> [193304.336940] ata1.00: cmd ca/00:20:69:22:a6/00:00:00:00:00/e7 tag 0 dma
>> 16384 out Jan 27 02:30:06 coyote kernel: [193304.336942]          res
>> 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 27 02:30:06
>> coyote kernel: [193304.336945] ata1.00: status: { DRDY } Jan 27 02:30:06
>> coyote kernel: [193304.336972] ata1: soft resetting link Jan 27 02:30:06
>> coyote kernel: [193304.499210] ata1.00: configured for UDMA/100 Jan 27
>> 02:30:06 coyote kernel: [193304.499226] ata1: EH complete
>> Jan 27 02:30:06 coyote kernel: [193304.499714] sd 0:0:0:0: [sda] 390721968
>> 512-byte hardware sectors (200050 MB) Jan 27 02:30:06 coyote kernel:
>> [193304.499857] sd 0:0:0:0: [sda] Write Protect is off Jan 27 02:30:06
>> coyote kernel: [193304.502315] sd 0:0:0:0: [sda] Write cache: enabled,
>> read cache: enabled, doesn't support DPO or FUA
>>
>> None were logged during the time I was running an -rc7 or -rc8.
>>
>> The previous hits on this resulted in the udma speed being downgraded
>> till it was actually running in pio just before the freeze that
>> required the hardware reset button.
>
>Unfortunately there are 1001 different causes for timeouts, so we need
>to drill down into the hardware, libata version, and ACPI version (most
>notably).
>
>> I'll reboot to -rc8 right now and resume.  If its the drive, I should see
>> it. If not, then 2.6.24 is where I'll point the finger.
Both rc8 and rc7 do it.  The fedora kernels do too, but without the error 
messages being logged, I assume they are an attempt to trace this?

>There was also an ACPI update, which always affects interrupt handling
>(whose symptom can sometimes be a timeout).

I'm thinking Bingo!, please pay the man. See my posts asking about a couple of 
lines very early in the dmesg, asking for an english explanation no one has 
proffered as yet.

>Definitely interesting in test results from what you describe.
>
>	Jeff



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
It's no wonder they call it WinNT; WNT = VMS++;

   -- Chris Abbey
%   
Peace, Love and Compile the kernel...

   -- Justin L. Herreman

Re: Problem with ata layer in 2.6.24

[Florian Attenberger]

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

On Mon, 28 Jan 2008 14:13:21 -0500
Gene Heskett <gene.heskett@gmail.com> wrote:


> >> I had to reboot early this morning due to a freezeup, and I had a
> >> bunch of these in the messages log:
> >> ==============
> >> Jan 27 19:42:11 coyote kernel: [42461.915961] ata1.00: exception Emask 0x0
> >> SAct 0x0 SErr 0x0 action 0x2 frozen Jan 27 19:42:11 coyote kernel:
> >> [42461.915973] ata1.00: cmd ca/00:08:b1:66:46/00:00:00:00:00/e8 tag 0 dma
> >> 4096 out Jan 27 19:42:11 coyote kernel: [42461.915974]          res
> >> 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 27 19:42:11
> >> coyote kernel: [42461.915978] ata1.00: status: { DRDY } Jan 27 19:42:11
> >> coyote kernel: [42461.916005] ata1: soft resetting link Jan 27 19:42:12
> >> coyote kernel: [42462.078216] ata1.00: configured for UDMA/100 Jan 27
> >> 19:42:12 coyote kernel: [42462.078232] ata1: EH complete
> >> Jan 27 19:42:12 coyote kernel: [42462.090700] sd 0:0:0:0: [sda] 390721968
> >> 512-byte hardware sectors (200050 MB) Jan 27 19:42:12 coyote kernel:
> >> [42462.114230] sd 0:0:0:0: [sda] Write Protect is off Jan 27 19:42:12
> >> coyote kernel: [42462.115079] sd 0:0:0:0: [sda] Write cache: enabled, read
> >> cache: enabled, doesn't support DPO or FUA
> >> ===============


I had this error too, or maybe only a similar one, and another, neither
of which of i still have the error output laying around, so I'm posting both
fixes, that i found here on lkml:
1) disabling ncq like that:
"echo 1 > /sys/block/sda/device/queue_depth" 
2) this patch: libata_drain_fifo_on_stuck_drq_hsm.patch 
( applies to 2.6.24 too )

Signed-off-by: Mark Lord <mlord@pobox.com>
---

--- old/drivers/ata/libata-sff.c	2007-09-28 09:29:22.000000000 -0400
+++ linux/drivers/ata/libata-sff.c	2007-09-28 09:39:44.000000000 -0400
@@ -420,6 +420,28 @@
 	ap->ops->irq_on(ap);
 }
 
+static void ata_drain_fifo(struct ata_port *ap, struct ata_queued_cmd *qc)
+{
+	u8 stat = ata_chk_status(ap);
+	/*
+	 * Try to clear stuck DRQ if necessary,
+	 * by reading/discarding up to two sectors worth of data.
+	 */
+	if ((stat & ATA_DRQ) && (!qc || qc->dma_dir != DMA_TO_DEVICE)) {
+		unsigned int i;
+		unsigned int limit = qc ? qc->sect_size : ATA_SECT_SIZE;
+
+		printk(KERN_WARNING "Draining up to %u words from data FIFO.\n",
+									limit);
+		for (i = 0; i < limit ; ++i) {
+			ioread16(ap->ioaddr.data_addr);
+			if (!(ata_chk_status(ap) & ATA_DRQ))
+				break;
+		}
+		printk(KERN_WARNING "Drained %u/%u words.\n", i, limit);
+	}
+}
+
 /**
  *	ata_bmdma_drive_eh - Perform EH with given methods for BMDMA controller
  *	@ap: port to handle error for
@@ -476,7 +498,7 @@
 	}
 
 	ata_altstatus(ap);
-	ata_chk_status(ap);
+	ata_drain_fifo(ap, qc);
 	ap->ops->irq_clear(ap);
 
 	spin_unlock_irqrestore(ap->lock, flags);
-





-- 
Florian Attenberger <valdyn@gmail.com>

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

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Tuesday 29 January 2008, Florian Attenberger wrote:
>On Mon, 28 Jan 2008 14:13:21 -0500
>
>Gene Heskett <gene.heskett@gmail.com> wrote:
>> >> I had to reboot early this morning due to a freezeup, and I had a
>> >> bunch of these in the messages log:
>> >> ==============
>> >> Jan 27 19:42:11 coyote kernel: [42461.915961] ata1.00: exception Emask
>> >> 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Jan 27 19:42:11 coyote kernel:
>> >> [42461.915973] ata1.00: cmd ca/00:08:b1:66:46/00:00:00:00:00/e8 tag 0
>> >> dma 4096 out Jan 27 19:42:11 coyote kernel: [42461.915974]          res
>> >> 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 27 19:42:11
>> >> coyote kernel: [42461.915978] ata1.00: status: { DRDY } Jan 27 19:42:11
>> >> coyote kernel: [42461.916005] ata1: soft resetting link Jan 27 19:42:12
>> >> coyote kernel: [42462.078216] ata1.00: configured for UDMA/100 Jan 27
>> >> 19:42:12 coyote kernel: [42462.078232] ata1: EH complete
>> >> Jan 27 19:42:12 coyote kernel: [42462.090700] sd 0:0:0:0: [sda]
>> >> 390721968 512-byte hardware sectors (200050 MB) Jan 27 19:42:12 coyote
>> >> kernel: [42462.114230] sd 0:0:0:0: [sda] Write Protect is off Jan 27
>> >> 19:42:12 coyote kernel: [42462.115079] sd 0:0:0:0: [sda] Write cache:
>> >> enabled, read cache: enabled, doesn't support DPO or FUA
>> >> ===============
>
>I had this error too, or maybe only a similar one, and another, neither
>of which of i still have the error output laying around, so I'm posting both
>fixes, that i found here on lkml:
>1) disabling ncq like that:
>"echo 1 > /sys/block/sda/device/queue_depth"

Interesting..

>2) this patch: libata_drain_fifo_on_stuck_drq_hsm.patch
>( applies to 2.6.24 too )
>
>Signed-off-by: Mark Lord <mlord@pobox.com>
>---
>
>--- old/drivers/ata/libata-sff.c	2007-09-28 09:29:22.000000000 -0400
>+++ linux/drivers/ata/libata-sff.c	2007-09-28 09:39:44.000000000 -0400
>@@ -420,6 +420,28 @@
> 	ap->ops->irq_on(ap);
> }
>
>+static void ata_drain_fifo(struct ata_port *ap, struct ata_queued_cmd *qc)
>+{
>+	u8 stat = ata_chk_status(ap);
>+	/*
>+	 * Try to clear stuck DRQ if necessary,
>+	 * by reading/discarding up to two sectors worth of data.
>+	 */
>+	if ((stat & ATA_DRQ) && (!qc || qc->dma_dir != DMA_TO_DEVICE)) {
>+		unsigned int i;
>+		unsigned int limit = qc ? qc->sect_size : ATA_SECT_SIZE;
>+
>+		printk(KERN_WARNING "Draining up to %u words from data FIFO.\n",
>+									limit);
>+		for (i = 0; i < limit ; ++i) {
>+			ioread16(ap->ioaddr.data_addr);
>+			if (!(ata_chk_status(ap) & ATA_DRQ))
>+				break;
>+		}
>+		printk(KERN_WARNING "Drained %u/%u words.\n", i, limit);
>+	}
>+}
>+
> /**
>  *	ata_bmdma_drive_eh - Perform EH with given methods for BMDMA controller
>  *	@ap: port to handle error for
>@@ -476,7 +498,7 @@
> 	}
>
> 	ata_altstatus(ap);
>-	ata_chk_status(ap);
>+	ata_drain_fifo(ap, qc);
> 	ap->ops->irq_clear(ap);
>
> 	spin_unlock_irqrestore(ap->lock, flags);
>-

This too.  Thanks Florian.  I'll keep these in mind as there may be more than 
one cat in need of skinning here.

See a couple of posts I made to lkml this morning for the investigation I'm 
doing re the kernel argument 'acpi_use_timer_override', experimental builds 
under way right now.

Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number 
when dmesg says its found ok at ata2.00?  I've turned on an option that says 
something about using the bios for device access this build, but I'll be 
surprised if that's it. :)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Ah, sweet Springtime, when a young man lightly turns his fancy over!

Re: Problem with ata layer in 2.6.24

[Mark Lord]

Gene Heskett wrote:
>..
> Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number 
> when dmesg says its found ok at ata2.00?  I've turned on an option that says 
> something about using the bios for device access this build, but I'll be 
> surprised if that's it. :)
..

It should show up as /dev/scd0 or something very similar.

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Tuesday 29 January 2008, Mark Lord wrote:
>Gene Heskett wrote:
>>..
>> Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
>> when dmesg says its found ok at ata2.00?  I've turned on an option that
>> says something about using the bios for device access this build, but I'll
>> be surprised if that's it. :)
>
>..
>
>It should show up as /dev/scd0 or something very similar.

Tisn't.  Darnit.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
clock speed

Re: Problem with ata layer in 2.6.24

[Mark Lord]

Gene Heskett wrote:
> On Tuesday 29 January 2008, Mark Lord wrote:
>> Gene Heskett wrote:
>>> ..
>>> Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
>>> when dmesg says its found ok at ata2.00?  I've turned on an option that
>>> says something about using the bios for device access this build, but I'll
>>> be surprised if that's it. :)
>> ..
>>
>> It should show up as /dev/scd0 or something very similar.
> 
> Tisn't.  Darnit.
..

It requires CONFIG_SCSI, CONFIG_BLK_DEV_SD, CONFIG_BLK_DEV_SR, in the kernel .config.

The _SR one ("SCSI Reader") is for CD/DVD support.

Cheers

Re: Problem with ata layer in 2.6.24

[rgheck]

Mark Lord wrote:
> Gene Heskett wrote:
>> ..
>> Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' 
>> number when dmesg says its found ok at ata2.00?  I've turned on an 
>> option that says something about using the bios for device access 
>> this build, but I'll be surprised if that's it. :)
> ..
>
> It should show up as /dev/scd0 or something very similar.
>
Does it appear as /dev/sr0? Try ll /dev/s* and see what you get.

Anyway, these /dev/ entries are produced by udev, not by libata.

rh

Re: Problem with ata layer in 2.6.24

[Jeff Garzik]

Gene Heskett wrote:
> Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number 
> when dmesg says its found ok at ata2.00?  I've turned on an option that says 
> something about using the bios for device access this build, but I'll be 
> surprised if that's it. :)

I think you mean /dev/scdx not /dev/sdx.  Make sure you have the 'sr' 
driver compiled and load (CONFIG_BLK_DEV_SR).

The bios-for-dev-access thing definitely won't help, and may hurt (by 
taking over the device you wanted to test).

	Jeff

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Tuesday 29 January 2008, Jeff Garzik wrote:
>Gene Heskett wrote:
>> Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
>> when dmesg says its found ok at ata2.00?  I've turned on an option that
>> says something about using the bios for device access this build, but I'll
>> be surprised if that's it. :)
>
>I think you mean /dev/scdx not /dev/sdx.  Make sure you have the 'sr'
>driver compiled and load (CONFIG_BLK_DEV_SR).
>
That menu item COULD be moved, I don't have any REAL scsi stuff, so I didn't 
look there.  My bad, with help from hiding it like that. :-)

>The bios-for-dev-access thing definitely won't help, and may hurt (by
>taking over the device you wanted to test).
>
Ok, if BLK_DEV_SR fails, I'll take that back out.  I'm heating the room making 
kernels here. :)

Thanks Jeff.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Life sucks, but death doesn't put out at all.
		-- Thomas J. Kopp

Re: Problem with ata layer in 2.6.24

[Jeff Garzik]

Gene Heskett wrote:
> On Tuesday 29 January 2008, Jeff Garzik wrote:
>> Gene Heskett wrote:
>>> Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
>>> when dmesg says its found ok at ata2.00?  I've turned on an option that
>>> says something about using the bios for device access this build, but I'll
>>> be surprised if that's it. :)
>> I think you mean /dev/scdx not /dev/sdx.  Make sure you have the 'sr'
>> driver compiled and load (CONFIG_BLK_DEV_SR).
>>
> That menu item COULD be moved, I don't have any REAL scsi stuff, so I didn't 
> look there.  My bad, with help from hiding it like that. :-)
> 
>> The bios-for-dev-access thing definitely won't help, and may hurt (by
>> taking over the device you wanted to test).
>>
> Ok, if BLK_DEV_SR fails, I'll take that back out.  I'm heating the room making 
> kernels here. :)

I can say with 100% certainty that 'sr' is required in order to use your 
dvd writer with libata.  :)

	Jeff

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Tuesday 29 January 2008, Jeff Garzik wrote:
>Gene Heskett wrote:
>> On Tuesday 29 January 2008, Jeff Garzik wrote:
>>> Gene Heskett wrote:
>>>> Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx'
>>>> number when dmesg says its found ok at ata2.00?  I've turned on an
>>>> option that says something about using the bios for device access this
>>>> build, but I'll be surprised if that's it. :)
>>>
>>> I think you mean /dev/scdx not /dev/sdx.  Make sure you have the 'sr'
>>> driver compiled and load (CONFIG_BLK_DEV_SR).
>>
>> That menu item COULD be moved, I don't have any REAL scsi stuff, so I
>> didn't look there.  My bad, with help from hiding it like that. :-)
>>
>>> The bios-for-dev-access thing definitely won't help, and may hurt (by
>>> taking over the device you wanted to test).
>>
>> Ok, if BLK_DEV_SR fails, I'll take that back out.  I'm heating the room
>> making kernels here. :)
>
>I can say with 100% certainty that 'sr' is required in order to use your
>dvd writer with libata.  :)
>
>	Jeff

And as usual, you are 100% correct, thanks.

And now back to our regularly scheduled testing for 'exception Emask' 
errors. :)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Main's Law:
	For every action there is an equal and opposite government program.

Re: Problem with ata layer in 2.6.24

[Robert Hancock]

Gene Heskett wrote:
> And so far no one has tried to comment on those 2 dmesg lines I've quoted a 
> couple of times now, here's another:
> [    0.000000] Nvidia board detected. Ignoring ACPI timer override.
> [    0.000000] If you got timer trouble try acpi_use_timer_override
> what the heck is that trying to tell me to do, in some sort of broken english?

A lot of NVIDIA-chipset motherboards have BIOS problems where they 
include an incorrect ACPI interrupt override for the timer interrupt, 
which tends to cause the system to fail to boot due to the timer 
interrupt not working. The kernel normally ignores ACPI interrupt 
overrides on the timer interrupt for NVIDIA chipsets for this reason. 
Unfortunately on some such boards the override is actually correct and 
needed, and so this actually causes problems. Hence the 
acpi_use_timer_override option.

In any case this is unlikely to have anything to do with your problem, 
since if that was messed up you likely would never have even booted.

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Robert Hancock wrote:
>Gene Heskett wrote:
>> And so far no one has tried to comment on those 2 dmesg lines I've quoted
>> a couple of times now, here's another:
>> [    0.000000] Nvidia board detected. Ignoring ACPI timer override.
>> [    0.000000] If you got timer trouble try acpi_use_timer_override
>> what the heck is that trying to tell me to do, in some sort of broken
>> english?
>
>A lot of NVIDIA-chipset motherboards have BIOS problems where they
>include an incorrect ACPI interrupt override for the timer interrupt,
>which tends to cause the system to fail to boot due to the timer
>interrupt not working. The kernel normally ignores ACPI interrupt
>overrides on the timer interrupt for NVIDIA chipsets for this reason.
>Unfortunately on some such boards the override is actually correct and
>needed, and so this actually causes problems. Hence the
>acpi_use_timer_override option.
>
>In any case this is unlikely to have anything to do with your problem,
>since if that was messed up you likely would never have even booted.
>--
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/

In this case, there seems to be a buglet.  I turned on the nvidia/amd drives 
under the ATA section of the menu, and turned off the pata_amd under the sata 
menu in xconfig.

But I've tried twice now and it fails to build the initrd because the pata_amd 
module is on the missing list.  Of course its missing, I didn't have it 
built...

Next?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Of course it's possible to love a human being if you don't know them too well.
		-- Charles Bukowski

Re: Problem with ata layer in 2.6.24

[Robert Hancock]

Gene Heskett wrote:
> On Monday 28 January 2008, Robert Hancock wrote:
>> Gene Heskett wrote:
>>> And so far no one has tried to comment on those 2 dmesg lines I've quoted
>>> a couple of times now, here's another:
>>> [    0.000000] Nvidia board detected. Ignoring ACPI timer override.
>>> [    0.000000] If you got timer trouble try acpi_use_timer_override
>>> what the heck is that trying to tell me to do, in some sort of broken
>>> english?
>> A lot of NVIDIA-chipset motherboards have BIOS problems where they
>> include an incorrect ACPI interrupt override for the timer interrupt,
>> which tends to cause the system to fail to boot due to the timer
>> interrupt not working. The kernel normally ignores ACPI interrupt
>> overrides on the timer interrupt for NVIDIA chipsets for this reason.
>> Unfortunately on some such boards the override is actually correct and
>> needed, and so this actually causes problems. Hence the
>> acpi_use_timer_override option.
>>
>> In any case this is unlikely to have anything to do with your problem,
>> since if that was messed up you likely would never have even booted.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at  http://www.tux.org/lkml/
> 
> In this case, there seems to be a buglet.  I turned on the nvidia/amd drives 
> under the ATA section of the menu, and turned off the pata_amd under the sata 
> menu in xconfig.
> 
> But I've tried twice now and it fails to build the initrd because the pata_amd 
> module is on the missing list.  Of course its missing, I didn't have it 
> built...
> 
> Next?

Check the /etc/modprobe.conf file, a lot of distributions use this to 
generate the initrd. If there's references to pata_amd it'll try and 
include it.

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Robert Hancock wrote:
[...]
>Check the /etc/modprobe.conf file, a lot of distributions use this to
>generate the initrd. If there's references to pata_amd it'll try and
>include it.

Bingo!  Thanks Robert, I'll try it again with that line commented.  I wasn't 
aware of that connection at all.  Yup, it worked, I feel a reboot coming 
on. :)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If everything seems to be going well, you have obviously overlooked something.

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Monday 28 January 2008, Gene Heskett wrote:
>On Monday 28 January 2008, Robert Hancock wrote:
>[...]
>
>>Check the /etc/modprobe.conf file, a lot of distributions use this to
>>generate the initrd. If there's references to pata_amd it'll try and
>>include it.
>
>Bingo!  Thanks Robert, I'll try it again with that line commented.  I wasn't
>aware of that connection at all.  Yup, it worked, I feel a reboot coming
>on. :)

But it didn't work, apparently commenting that line out needs to be balanced 
by adding another line telling it amd74xx is the 'hostadapter', not 
necessarily scsi.

Can this be made more universal so I don't have to edit /etc/modprobe.conf?

Thanks.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Because we don't think about future generations, they will never forget us.
		-- Henrik Tikkanen

Re: Problem with ata layer in 2.6.24

[Mark Lord]

Gene Heskett wrote:
> On Monday 28 January 2008, Gene Heskett wrote:
>> On Monday 28 January 2008, Robert Hancock wrote:
>> [...]
>>
>>> Check the /etc/modprobe.conf file, a lot of distributions use this to
>>> generate the initrd. If there's references to pata_amd it'll try and
>>> include it.
>> Bingo!  Thanks Robert, I'll try it again with that line commented.  I wasn't
>> aware of that connection at all.  Yup, it worked, I feel a reboot coming
>> on. :)
> 
> But it didn't work, apparently commenting that line out needs to be balanced 
> by adding another line telling it amd74xx is the 'hostadapter', not 
> necessarily scsi.
> 
> Can this be made more universal so I don't have to edit /etc/modprobe.conf?
>..

You could really do it like Linus (and me), and not bother with modules
for critical services like hard disks.

Just build them *into* the core kernel (select "y" or "checkmark" rather
than "m" or "dot" for modules).  This eliminates a ton of crap that can fail,
and may also make your kernel a micro-MIP faster (core memory is often mapped
without page table entries, whereas loaded modules use page tables.. slower, slightly).

Linus just edits the /boot/grub/menu.lst, and clones an existing boot entry
for the new kernel, editing the "kernel" line to match the name of the file
that got installed in /boot by "make install" (from the kernel directory).
He just leaves the ramdisk/initrd line as-was --> wrong version, but that's okay.

I totally get rid of them here, but that requires hardcoding the root=/dev/xxxx
part on the "kernel" line.  No big deal, it works just fine that way.

Cheers

Re: Problem with ata layer in 2.6.24

[Adam Turk]

I just found this thread and it looks like it will fix my problem too.  I have an IDE cd-rw drive and 2 SCSI hard drives.  My ide cd-rw drive hasn't been showing up.  I looked at setting scsi cdrom support (CONFIG_BLOCK_DEV_SR) but it doesn't mention anything about ide drives using libata.
I know the drive is being detecting by looking at dmesg:
ata_piix 0000:00:07.1: version 2.12
scsi1 : ata_piix
scsi2 : ata_piix
ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
ata1.00: ATAPI: Memorex 52MAXX 3252AJ1, 4WS2, max UDMA/33
ata1.00: configured for UDMA/33
ata2: port disabled. ignoring.
scsi 1:0:0:0: CD-ROM            Memorex  52MAXX 3252AJ1   4WS2 PQ: 0 ANSI: 5
if this works then it really needs to move and be renamed.  I am compiling with DEV_SR set.

Just my $0.02 but may be worth more or less,
Adam


_________________________________________________________________
Need to know the score, the latest news, or you need your Hotmail®-get your "fix".
http://www.msnmobilefix.com/Default.aspx

Re: Problem with ata layer in 2.6.24

[Gene Heskett]

On Tuesday 29 January 2008, Adam Turk wrote:
>I just found this thread and it looks like it will fix my problem too.  I
> have an IDE cd-rw drive and 2 SCSI hard drives.  My ide cd-rw drive hasn't
> been showing up.  I looked at setting scsi cdrom support
> (CONFIG_BLOCK_DEV_SR) but it doesn't mention anything about ide drives
> using libata. I know the drive is being detecting by looking at dmesg:
>ata_piix 0000:00:07.1: version 2.12
>scsi1 : ata_piix
>scsi2 : ata_piix
>ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
>ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
>ata1.00: ATAPI: Memorex 52MAXX 3252AJ1, 4WS2, max UDMA/33
>ata1.00: configured for UDMA/33
>ata2: port disabled. ignoring.
>scsi 1:0:0:0: CD-ROM            Memorex  52MAXX 3252AJ1   4WS2 PQ: 0 ANSI: 5
>if this works then it really needs to move and be renamed.  I am compiling
> with DEV_SR set.
>
>Just my $0.02 but may be worth more or less,
>Adam
>
That fixed me right up, Adam, & k3b is once again as happy as a clam.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Main's Law:
	For every action there is an equal and opposite government program.

RE: Problem with ata layer in 2.6.24

[Adam Turk]

> From: gene.heskett@gmail.com
>>if this works then it really needs to move and be renamed. I am compiling
>> with DEV_SR set.
>>
> That fixed me right up, Adam, & k3b is once again as happy as a clam.

Fixed it for me too.  I just realized the default config in 2.6.24 is way different than the default config in 2.6.23.  

If I remember correctly there was talk of separating the libata and scsi code.  This was awhile ago.  I am not a kernel programmer, only a user, but either the scsi and libata kconfig menus should be joined and made generic, or options like cdrom support should be in both kconfig menus.  Alan says libata is scsi with an accent so maybe merging the two isn't as bad as it sounds.  

Just my $0.02 cents, probably worth less in this case.
Adam
_________________________________________________________________
Connect and share in new ways with Windows Live.
http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008