From: "Andreas Unterkircher" <unki@netshadow.at>
To: "Herve Fache" <herve.fache@europemail.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: Linux hangs on nVidia nForce2 400 Ultra
Date: Sun, 4 Jan 2004 19:00:20 +0100 [thread overview]
Message-ID: <003701c3d2ec$a066c3b0$02bfa8c0@kuecken> (raw)
In-Reply-To: 20040104173624.19046.qmail@iname.com
According your .config you have compiled all ide-chipsets.
Have you tried only compile in the
AMD74XX (CONFIG_BLK_DEV_AMD74XX=y) AMD and nVidia IDE support?
This is the only necessary IDE-Chipset on my Nforce Board.... Perhaps this
would help.
Can you supply a dmesg output?
Andreas
----- Original Message -----
From: "Herve Fache" <herve.fache@europemail.com>
To: <linux-kernel@vger.kernel.org>
Sent: Sunday, January 04, 2004 6:36 PM
Subject: Linux hangs on nVidia nForce2 400 Ultra
> Hi chaps!
>
> My system hangs (no oops, nothing) on disk access using either 2.4.23 or
2.6.0. A rather reliable way for me to
> crash it is to, for example, copy the sources of the Linux kernel.
>
> It hanged once on CD-ROM access, which could lead to a more IDE-level
problem. Also, the only time it did it in
> another operating system (humm...) was after it crashed in Linux and I
pressed reset (no shut down), which
> makes me think it could the IDE controller [driver]'s fault...
>
> It seems I'm the only one on Earth to have this problem (according to
Google), but if there was a way to track it
> down I'd be happy to try.
>
> I have attached my 2.6.0 kernel config for info.
>
> Thanks!
> Hervé.
> --
> ___________________________________________________________
> Sign-up for Ads Free at Mail.com
> http://promo.mail.com/adsfreejump.htm
>
>
next prev parent reply other threads:[~2004-01-04 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 17:36 Linux hangs on nVidia nForce2 400 Ultra Herve Fache
2004-01-04 18:00 ` Andreas Unterkircher [this message]
2004-01-04 18:03 ` Daniel Drake
2004-01-06 6:12 ` Bob
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='003701c3d2ec$a066c3b0$02bfa8c0@kuecken' \
--to=unki@netshadow.at \
--cc=herve.fache@europemail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.