mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Craig Bradney <cbradney@zip.com.au>
To: Tim Krieglstein <tstone@fachschaft.informatik.tu-darmstadt.de>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.6-xx locks up hard (nforce 2)
Date: Tue, 18 May 2004 00:55:09 +0200	[thread overview]
Message-ID: <1084834509.14114.7.camel@amilo.bradney.info> (raw)
In-Reply-To: <20040517223550.GA7631@host02.fachschaft.informatik.tu-darmstadt.de>

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

On Tue, 2004-05-18 at 00:35, Tim Krieglstein wrote:
> Hi 
> 
> I have a serious problem with the newer kernel versions. Every Version
> of 2.6.6((-mm[123])*) 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.

Craig

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

  reply	other threads:[~2004-05-17 22:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 22:35 Tim Krieglstein
2004-05-17 22:55 ` Craig Bradney [this message]
2004-05-21 16:37 ` Francois Romieu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1084834509.14114.7.camel@amilo.bradney.info \
    --to=cbradney@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tstone@fachschaft.informatik.tu-darmstadt.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®