From: Reg Clemens <reg@dwf.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Reg Clemens <reg@dwf.com>,
rlrevell@joe-job.com, linux-kernel@vger.kernel.org
Subject: Re: vmlinuz-2.6.16-rc5-git8 still nogo with Intel D945 Motherboard
Date: Tue, 07 Mar 2006 12:32:00 -0700 [thread overview]
Message-ID: <200603071932.k27JW0UH003735@deneb.dwf.com> (raw)
In-Reply-To: <20060307104646.9b2e193d.rdunlap@xenotime.net>
>
> Both boot logs contains the Cannot messages.
Hadn't noticed that, since it worked, I hadnt looked that carefully, sorry.
> The "bad" log also contains:
> Mar 7 10:58:41 deneb kernel: PCI: Failed to allocate mem resource #6:20000@48000000 for 0000:01:00.0
>
Yep.
> Is device 0:01:00.0 your Nvidia video card?
> Is there an updated NVRM driver for it (guessing from your OK boot log)
> for 2.6.15 or later?
Yes, I am running with the NVIDIA
NVIDIA-Linux-x86-1.0-6629-pkg1.run
driver, tho the 'nv' in the system works.
>
> I suppose an lspci might help. I dunno.
---
Here is the lspci, run from 2.6.11, but I dont think that should matter...
[root@deneb reg]# /sbin/lspci
00:00.0 Host bridge: Intel Corporation 945G/P Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 945G/P PCI Express Graphics Port (rev 02)
00:1b.0 Class 0403: Intel Corporation 82801G (ICH7 Family) High Definition
Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1
(rev 01)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3
(rev 01)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4
(rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1
(rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2
(rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3
(rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4
(rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI
Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface
Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller
(rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) Serial
ATA Storage Controllers cc=IDE (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev
a2)
05:01.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 04)
05:02.0 Multimedia audio controller: Creative Labs SB Audigy LS
05:03.0 Ethernet controller: D-Link System Inc Gigabit Ethernet Adapter (rev
11)
---
Did you notice that the following three pnp messages talk about the same
memory ranges, but different devices (5 vs 6),
Mar 7 11:02:21 deneb kernel: PCI: Cannot allocate resource region 1 of device
0000:05:01.0
Mar 7 11:02:21 deneb kernel: PCI: Cannot allocate resource region 2 of device
0000:05:01.0
Mar 7 11:02:21 deneb kernel: pnp: 00:05: ioport range 0x500-0x53f has been
reserved
Mar 7 11:02:21 deneb kernel: pnp: 00:05: ioport range 0x400-0x47f could not
be reserved
Mar 7 11:02:21 deneb kernel: pnp: 00:05: ioport range 0x680-0x6ff has been
reserved
---
Mar 7 10:58:41 deneb kernel: PCI: Cannot allocate resource region 1 of device
0000:05:01.0
Mar 7 10:58:41 deneb kernel: PCI: Cannot allocate resource region 2 of device
0000:05:01.0
Mar 7 10:58:41 deneb kernel: pnp: 00:06: ioport range 0x500-0x53f has been
reserved
Mar 7 10:58:41 deneb kernel: pnp: 00:06: ioport range 0x400-0x47f could not
be reserved
Mar 7 10:58:41 deneb kernel: pnp: 00:06: ioport range 0x680-0x6ff has been
reserved
Mar 7 10:58:41 deneb kernel: PCI: Failed to allocate mem resource
#6:20000@48000000 for 0000:01:00.0
--
Im not sure what the significance of that is, just noticed the difference.
Reg.Clemens
reg@dwf.com
next prev parent reply other threads:[~2006-03-07 19:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 3:40 Reg Clemens
2006-03-07 3:48 ` Lee Revell
2006-03-07 8:23 ` Reg Clemens
2006-03-07 16:13 ` Lee Revell
2006-03-07 16:18 ` Randy.Dunlap
2006-03-07 18:20 ` Reg Clemens
2006-03-07 18:46 ` Randy.Dunlap
2006-03-07 19:32 ` Reg Clemens [this message]
2006-03-07 20:00 ` Randy.Dunlap
2006-03-07 20:22 ` Reg Clemens
2006-03-07 21:55 ` Randy.Dunlap
2006-03-07 18:38 ` Reg Clemens
2006-03-07 18:50 ` Lee Revell
2006-03-07 4:01 ` Randy.Dunlap
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=200603071932.k27JW0UH003735@deneb.dwf.com \
--to=reg@dwf.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rlrevell@joe-job.com \
/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®