mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Reg Clemens <reg@dwf.com>
Cc: 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, 7 Mar 2006 13:55:50 -0800	[thread overview]
Message-ID: <20060307135550.79fb90ff.rdunlap@xenotime.net> (raw)
In-Reply-To: <200603071932.k27JW0UH003735@deneb.dwf.com>

On Tue, 07 Mar 2006 12:32:00 -0700 Reg Clemens wrote:

> 
> > 
> > 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.
> ---
> 
> 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.

Hi Reg,
I think you'll need to file a bug at bugzilla.kernel.org for this,
including the boot logs (good + bad), lspci -v, etc.

---
~Randy

  parent reply	other threads:[~2006-03-07 21:54 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
2006-03-07 20:00             ` Randy.Dunlap
2006-03-07 20:22               ` Reg Clemens
2006-03-07 21:55             ` Randy.Dunlap [this message]
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=20060307135550.79fb90ff.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reg@dwf.com \
    --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®