All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Michael Joy <mdj00b@acu.edu>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.3 Boot Failure on Nforce2 Board
Date: Wed, 25 Feb 2004 11:17:38 -0500	[thread overview]
Message-ID: <403CCAA2.5070800@pobox.com> (raw)
In-Reply-To: <1077723571.9844.22.camel@physx01.acu.edu>

Michael Joy wrote:
> Hello,
> We're having an interesting problem with the latest kernel release. On
> an Albatron KM18G, latest bios, 1024MB system with athlon xp proc, 2.6.3
> refuses to boot. It hangs on initializing the ide devices.
> 
> [2.] Full description of the problem/report: The problem is most
> definately related to the ide controller changes made in 2.6.3 as in
> 2.4.22 we did not have this issue. We haven't tried any of the previous
> kernels as this is a production system.
> 
> When booting the 2.6.3 kernel, either compiled by Mandrake (cooker) or
> using the straight up source, the kernel hangs without any error on hda:
> max request size : 128KiB.
> 
> I don't have a log of this as it won't initialize the HD (wd1200jb on an
> 80pin cable) to log the dmesg dump. Anyways we have two identical
> machines that do this. Both are nforce2 integrated gpu's, using onboard
> networking and sound. They have 2x512 Kingston HyperX memory modules
> which have been thouroughly tested in these machines with memtest and no
> errors are found.
> 
> Of note is that these machines exhibit the random freezes (blank screen,
> hard lock, normally associated with heavy disk thrashing) many other
> nforce2 boards seem to be experiencing. To fix this, we boot them with
> the noapic and nolapic option and the problem does not reappear. 

> i2c-nforce2             4392   0 (unused)

> nvnet                  30880   1 (autoclean)


You appear to have a binary-only module, nvnet, loaded...  we cannot 
debug problems with closed source code in your kernel.  Try "forcedeth" 
NIC driver instead.

	Jeff




  reply	other threads:[~2004-02-25 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25 15:39 2.6.3 Boot Failure on Nforce2 Board Michael Joy
2004-02-25 16:17 ` Jeff Garzik [this message]
2004-02-25 17:06   ` Michael Joy
  -- strict thread matches above, loose matches on Subject: below --
2004-02-26  0:48 Ross Dickson

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=403CCAA2.5070800@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdj00b@acu.edu \
    /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.