Re: Problem with ata layer in 2.6.24

[Dave Neuer]

On Jan 28, 2008 11:35 AM, Gene Heskett <gene.heskett@xxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/