Re: 2.6.6-xx locks up hard (nforce 2)
From: Craig Bradney
Date: Mon May 17 2004 - 17:57:52 EST
On Tue, 2004-05-18 at 00:35, Tim Krieglstein wrote:
> I have a serious problem with the newer kernel versions. Every Version
> of 2.6.6((-mm)*) locks up hard, no network no pinging no input.
> Just plain noting :(. The systems seems to boot up fine but after a few
> seconds after X has started everything locks up. Currently i am running
> the 2.6.5 version which has been running stable for days. I didn't tried
> the the mm versions of the 2.6.5 flavour (or probably i tested them but
> i forgot...). I know that there are broken out patches available, but
> before starting binary search on the single patches i hope i get an
> educated guess? I have already taken out an rtl8169 network card. But
> still lockups (the cards drivers seemed to be very bogus in earlier
> versions till 2.6.4 or so). Attached there will be the lspci output and
> my kernel config.
> Appendix: Ok, i glanced over the list-archives (i am not subscribed) and
> under the topic "IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 +
> [PATCH]for idle=C1halt, 2.6.5 " seem to be some fixes, i haven't tried
> yet. The thread was spread over different directorys and i didn't get
> the point. However lspci -xxx -vvv gives me the following error:
> pcilib: sysfs_read: tried to read 256 bytes at 0, but got only 64
> lspci: Unable to read 256 bytes of configuration space. Do these fixes
> help me in my problem?
> System is Debian sid.
The IO APIC idle c1 halt patches should work fine on 2.6.5 and stop
nforce related hanging. 2.6.6 is supposed to have the "correct" fix for
the BIOS issues. Perhaps there is something else wrong with the system?
Others will have more input.. Im yet to try 2.6.6 on the nforce system
here due to the IDE caching issues.
Description: This is a digitally signed message part