From: Greg KH <greg@kroah.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc1 kernel init oops
Date: Sun, 29 Jan 2006 12:19:23 -0800 [thread overview]
Message-ID: <20060129201923.GB6972@kroah.com> (raw)
In-Reply-To: <20060129111934.53710b03.rdunlap@xenotime.net>
On Sun, Jan 29, 2006 at 11:19:34AM -0800, Randy.Dunlap wrote:
> On Sun, 29 Jan 2006 11:00:29 -0800 Greg KH wrote:
>
> > On Sat, Jan 28, 2006 at 05:55:11PM -0800, Randy.Dunlap wrote:
> > > On Sat, 28 Jan 2006 17:18:41 -0800 Randy.Dunlap wrote:
> > >
> > > > Hi,
> > > >
> > > > I'm trying to boot 2.6.16-rc1 on a T42 Thinkpad notebook.
> > > > No serial port for serial console. I don't think that networking
> > > > is alive yet (for network console ?).
> > > >
> > > > Anyone recognize this? got patch?
> > > >
> > > > This is just typed in, so could contain a few errors.
> > > >
> > > > Unable to handle kernel NULL pointer dereference at virtual address 00000001
> > > > printing eip:
> > > > 00000001
> > > > *pde = 00000000
> > > > Oops: 0000 [#1]
> > > > SMP DEBUG_PAGEALLOC
> > > > Modules linked in:
> > > > CPU: 0
> > > > EIP: 0060:[<00000001>] Not tainted VLI
> > > > EFLAGS: 00010202 (2.6.16-rc1)
> > > > EIP is at 0x1
> > > > <skip reg. dump>
> > > > <skip stack dump>
> > > > Call trace:
> > > > show_stack_log_lvl+0xa5/0xad
> > > > show_registers+0xf9/0x162
> > > > die+0xfe/0x179
> > > > do_page_fault+0x399/0x4d8
> > > > error_code+0x4f/0x54
> > > > device_register+0x13/0x18
> > > > platform_bus_init+0xd/0x19
> > > > driver_init+0x1c/0x2d
> > > > do_basic_setup+0x12/0x1e
> > > > init+0x95/0x195
> > > > kernel_thread_helper+0x5/0xb
> > > > Code: Bad EIP value.
> > >
> > > Both 2.6.15 and 2.6.15.1 boot OK for me.
> > > .config for 2.6.16-rc1 is at
> > > http://www.xenotime.net/linux/doc/config-2616rc1
> >
> > If you disable CONFIG_PNP and CONFIG_ISAPNP options does that help?
>
> Nope, no change. Any other suggestions?
>
> I just booted with a KOBJECT_DEBUG
> built kernel and it's failing after:
>
> kobject platform: registering, parent: <NULL>, set: devices
Can you enable CONFIG_DEBUG_DRIVER and see if that helps?
thanks,
greg k-h
next prev parent reply other threads:[~2006-01-29 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 1:18 2.6.16-rc1 kernel init oops Randy.Dunlap
2006-01-29 1:55 ` Randy.Dunlap
2006-01-29 19:00 ` Greg KH
2006-01-29 19:19 ` Randy.Dunlap
2006-01-29 20:19 ` Greg KH [this message]
2006-01-29 21:08 ` Randy.Dunlap
2006-01-29 23:07 ` Randy.Dunlap
2006-01-30 0:57 ` Randy.Dunlap
2006-01-30 4:44 ` Greg KH
2006-02-02 5:31 ` 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=20060129201923.GB6972@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.