From: Reg Clemens <reg@dwf.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.18 will not boot on Intel D954nt motherboard.
Date: Tue, 17 Oct 2006 11:32:35 -0600 [thread overview]
Message-ID: <200610171732.k9HHWZdF020439@deneb.dwf.com> (raw)
Linux 2.6.11 is the last release that will boot on my Intel D945Gnt
motherboard (Pentium 4) with a Nvidia Video Card and a generic ethernet
card.
Up thru 2.6.16 The boot completed (with errors) but you could not get
to the ethernet card.
With 2.6.18 the boot totally fails (see below)
HOPEFULLY this more serious failure mode will lead to a fix to this problem.
As noted, everything is fine up thru 2.6.11 ...
---
Boot output with Intel's most recent BIOS for the D945Gnt, NT3996.iso, dated
11sep2006
and 2.6.18 with NO CHANGES the boot output (hand copied) is:
---
Booting 'Fedora Core (2.6.18)'
root(hd1,5)
File system type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-2.6.18 ro root=/dev/sda6 rhgb quiet
[Linux-bzImage, setup=0x1e00, size=0x196a84]
initrd /boot/initrd-2.6.18.img
[linux-initrd @ 0x37eba000, 0x135a1c bytes]
Uncompressing Linux... OK, booting the kernel.
PCI: BIOS Bug: MCFG area at f0000000 is not e820-reserved
PCI: Not using MMCONFIG.
PCI: Cannot allocate resource region 1 of device 0000:05:01.0
PCI: Cannot allocate resource region 2 of device 0000:05:01.0
PCI: Failed to allocate mem resource #6:20000@48000000 for 0000:01:00.0
APCI: getting cpu index for apciid 0x3
APCI: getting cpu index for apciid 0x4
RedHat nash version 4.2.15 starting
Bug: soft lockup detected on CPU#0!
<hang>
---
This is in bugzilla as Bug 6209 with more details.
--
Reg.Clemens
reg@dwf.com
reply other threads:[~2006-10-17 17:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200610171732.k9HHWZdF020439@deneb.dwf.com \
--to=reg@dwf.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 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®