From: Frank Overton <frank@discoverycenters.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 series kernels panic on boot at PCI probe with 450nx
Date: Mon, 07 Nov 2005 09:27:11 -0800 [thread overview]
Message-ID: <1131384430.26641.31.camel@coco.overtonshome.net> (raw)
In-Reply-To: <20051105043056.GA25501@kroah.com>
Greg,
I don't know any good way to save the oops message. I'd love a pointer
on that.
Here is a hand copy of the oops message I am seeing.
-- top of screen --
c316d000 c3126240 00000000 00000000 c01de368 00000000 c31262b8
c3126240
Call Trace:
[<co23e390>] class_device_create_file+0x11/0x16
[<co1ddcaf>] pci_alloc_child_bus+0x74/0xb8
[<co1ddda5>] pci_scan_bridge+0x90/0x1cd
[<co1de368>] pci_scan_child_bus+0x51/0x77
[<co1de4c2>] pci_scan_bus_parented+0x11d/0x133
[<co29d3ec>] pci_bios_scan_root+0x3d/0x40
[<co208e00>] acpi_pci_root_add+0x19a/0x1f0
[<co20d825>] acpi_bus_driver_init+0x2c/0x8c
[<co20e019>] acpi_bus_find_driver+0x110/0x21a
[<co20e561>] acpi_bus_add+0x12c/0x152
[<co20e68b>] acpi_bus_scan+0x104/0x156
[<co3b7c7a>] acpi_bus_scan_init+0x48/0x5e
[<co3a86fa>] do_initcalls+0x49/0x8e
[<co100454>] init+0x0/0x1d8
[<co1041d5>] kernel_thread_helper+0x5/0xb
Code:
00 00 0f 8e 37 02 00 00 83 c4 14 5b 5e 5f 5d c3 53 89 c1 89 c1 89 d3 85
c0 74 12 83 78 30 00 0f 94 c2 85 db 0f 94 c0 09 d0 a8 01 74 08 <0f> 0b
7d 01 1b 5b 31 c0 8b 41 30 89 da b9 04 00 00 00 5b e9 47
<0> Fatal Exception: panic in 5 seconds
On Fri, 2005-11-04 at 20:30, Greg KH wrote:
> On Fri, Nov 04, 2005 at 04:07:23PM -0800, Frank Overton wrote:
> > [1.] 2.6 series kernels panic on boot at PCI probe with 450nx (2.4.x
> > kernels boot without hitch) [2.] System: HP Netserver LH4s
>
> Can you post the oops message that you see?
>
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2005-11-07 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-05 0:07 Frank Overton
2005-11-05 4:30 ` Greg KH
2005-11-07 17:27 ` Frank Overton [this message]
2005-11-07 18:22 ` Greg KH
2005-11-07 19:07 ` Arjan van de Ven
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=1131384430.26641.31.camel@coco.overtonshome.net \
--to=frank@discoverycenters.org \
--cc=greg@kroah.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®