From: Andrew Morton <akpm@osdl•org>
To: Steve Fox <drfickle@us•ibm.com>
Cc: linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
Andi Kleen <ak@suse•de>, Vivek Goyal <vgoyal@in•ibm.com>
Subject: Re: 2.6.18-mm2 boot failure on x86-64
Date: Wed, 4 Oct 2006 08:45:40 -0700 [thread overview]
Message-ID: <20061004084540.af17fee5.akpm@osdl.org> (raw)
In-Reply-To: <1159969349.28106.64.camel@flooterbu>
On Wed, 04 Oct 2006 08:42:28 -0500
Steve Fox <drfickle@us•ibm.com> wrote:
> On Thu, 2006-09-28 at 14:01 -0700, Andrew Morton wrote:
> > On Thu, 28 Sep 2006 17:50:31 +0000 (UTC)
> > "Steve Fox" <drfickle@us•ibm.com> wrote:
> >
> > > On Thu, 28 Sep 2006 01:46:23 -0700, Andrew Morton wrote:
> > >
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18/2.6.18-mm2/
> > >
> > > Panic on boot. This machine booted 2.6.18-mm1 fine. em64t machine.
> > >
> > > TCP bic registered
> > > TCP westwood registered
> > > TCP htcp registered
> > > NET: Registered protocol family 1
> > > NET: Registered protocol family 17
> > > Unable to handle kernel paging request at ffffffffffffffff RIP:
> > > [<ffffffff8047ef93>] packet_notifier+0x163/0x1a0
> > > PGD 203027 PUD 2b031067 PMD 0
> > > Oops: 0000 [1] SMP
> > > last sysfs file:
> > > CPU 0
> > > Modules linked in:
> > > Pid: 1, comm: swapper Not tainted 2.6.18-mm2-autokern1 #1
> > > RIP: 0010:[<ffffffff8047ef93>] [<ffffffff8047ef93>] packet_notifier+0x163/0x1a0
> > > RSP: 0000:ffff810bffcbde90 EFLAGS: 00010286
> > > RAX: 0000000000000000 RBX: ffff810bff4a1000 RCX: 2222222222222222
> > > RDX: ffff810bff4a1000 RSI: 0000000000000005 RDI: ffffffff8055f5e0
> > > RBP: ffffffffffffffff R08: 0000000000007616 R09: 000000000000000e
> > > R10: 0000000000000006 R11: ffffffff803373f0 R12: 0000000000000000
> > > R13: 0000000000000005 R14: ffff810bff4a1000 R15: 0000000000000000
> > > FS: 0000000000000000(0000) GS:ffffffff805d8000(0000) knlGS:0000000000000000
> > > CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> > > CR2: ffffffffffffffff CR3: 0000000000201000 CR4: 00000000000006e0
> > > Process swapper (pid: 1, threadinfo ffff810bffcbc000, task ffff810bffcbb510)
> > > Stack: ffff810bff4a1000 ffffffff8055f4c0 0000000000000000 ffff810bffcbdef0
> > > 0000000000000000 ffffffff8042736e 0000000000000000 0000000000000000
> > > 0000000000000000 ffffffff8061c68d ffffffff806260f0 ffffffff80207182
> > > Call Trace:
> > > [<ffffffff8042736e>] register_netdevice_notifier+0x3e/0x70
> > > [<ffffffff8061c68d>] packet_init+0x2d/0x53
> > > [<ffffffff80207182>] init+0x162/0x330
> > > [<ffffffff8020a9d8>] child_rip+0xa/0x12
> > > [<ffffffff8033c2a2>] acpi_ds_init_one_object+0x0/0x82
> > > [<ffffffff80207020>] init+0x0/0x330
> > > [<ffffffff8020a9ce>] child_rip+0x0/0x12
> > >
> > >
> > > Code: 48 8b 45 00 0f 18 08 49 83 fd 02 4c 8d 65 f8 0f 84 f8 fe ff
> > > RIP [<ffffffff8047ef93>] packet_notifier+0x163/0x1a0
> > > RSP <ffff810bffcbde90>
> > > CR2: ffffffffffffffff
> > > <0>Kernel panic - not syncing: Attempted to kill init!
> > >
> >
> > I'm really struggling to work out what went wrong there. Comparing your
> > miserable 20 bytes of code to my object code makes me think that this:
> >
> > struct packet_sock *po = pkt_sk(sk);
> >
> > returned -1, perhaps in %ebp. But it's all very crude.
> >
> > Perhaps you could compile that kernel with CONFIG_DEBUG_INFO, rerun it (the
> > addresses might change) then have a poke around with `gdb vmlinux' (or
> > maybe just addr2line) to work out where it's really oopsing?
> >
> > I don't see much which has changed in that area recently.
>
> Sorry for the delay. I was finally able to perform a bisect on this. It
> turns out the patch that causes this is
> x86_64-mm-re-positioning-the-bss-segment.patch, which seems like a
> strange candidate, but sure enough I can boot to login: right up until
> that patch is applied.
hm, that patch was merged into mainline September 29. Does mainline work?
> P.S. I had to comment usb-hubc-build-fix.patch out of the series file
> because it would not apply cleanly and caused quilt (0.45) to simply
> abort its 'push' operation.
Sorry about that.
If mainline _does_ work then perhaps it's an interaction between that patch
and something else in the -mm2 lineup (and at that point in the bisection,
it'll be one of the git trees or something else in the x86_64 tree). Could
be that the problem remains in -mm3.
next prev parent reply other threads:[~2006-10-04 15:45 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060928014623.ccc9b885.akpm@osdl.org>
[not found] ` <efh217$8au$1@sea.gmane.org>
2006-09-28 21:01 ` 2.6.18-mm2 Andrew Morton
2006-09-28 22:45 ` 2.6.18-mm2 Stephen Hemminger
2006-10-04 13:42 ` 2.6.18-mm2 boot failure on x86-64 Steve Fox
2006-10-04 15:45 ` Andrew Morton [this message]
2006-10-04 15:55 ` Vivek Goyal
2006-10-04 15:56 ` Andi Kleen
2006-10-05 1:57 ` Keith Mannthey
2006-10-04 16:41 ` Steve Fox
2006-10-05 0:06 ` Andrew Morton
2006-10-05 0:51 ` Vivek Goyal
2006-10-05 0:57 ` Andi Kleen
2006-10-05 1:08 ` Martin Bligh
2006-10-05 2:05 ` Keith Mannthey
2006-10-05 14:53 ` Steve Fox
2006-10-05 15:12 ` Badari Pulavarty
2006-10-05 15:32 ` Steve Fox
2006-10-05 15:40 ` Andi Kleen
2006-10-05 17:57 ` Steve Fox
2006-10-05 18:27 ` Andi Kleen
2006-10-05 18:51 ` Steve Fox
2006-10-05 19:05 ` Andi Kleen
2006-10-05 20:42 ` Steve Fox
2006-10-05 20:50 ` Andi Kleen
2006-10-06 2:23 ` Steve Fox
2006-10-06 14:33 ` Mel Gorman
2006-10-06 15:36 ` Vivek Goyal
2006-10-06 17:11 ` Mel Gorman
2006-10-06 17:34 ` Vivek Goyal
2006-10-06 17:59 ` Vivek Goyal
2006-10-06 18:03 ` Steve Fox
2006-10-06 20:04 ` Vivek Goyal
2006-10-09 9:53 ` Mel Gorman
2006-10-16 18:16 ` Vivek Goyal
2006-10-16 23:58 ` Andrew Morton
2006-10-17 12:18 ` Adrian Bunk
2006-10-17 17:32 ` Mel Gorman
2006-10-05 18:52 ` Vivek Goyal
2006-10-05 19:08 ` Andi Kleen
2006-10-05 20:25 ` Steve Fox
2006-10-05 20:39 ` Mel Gorman
2006-10-05 20:51 ` Andi Kleen
2006-10-05 23:14 ` 2.6.18-mm2 boot failure on x86-64 II Andi Kleen
2006-10-05 23:32 ` keith mannthey
2006-10-05 23:35 ` Andi Kleen
2006-10-05 23:58 ` keith mannthey
2006-10-06 0:02 ` Badari Pulavarty
2006-10-06 0:12 ` Andrew Morton
[not found] ` <200609290319.k8T3JOwS005455@turing-police.cc.vt.edu>
[not found] ` <20060928202931.dc324339.akpm@osdl.org>
[not found] ` <200609291519.k8TFJfvw004256@turing-police.cc.vt.edu>
[not found] ` <20060929124558.33ef6c75.akpm@osdl.org>
2006-09-30 0:01 ` 2.6.18-mm2 - oops in cache_alloc_refill() Valdis.Kletnieks
2006-09-30 1:20 ` Andrew Morton
2006-09-30 1:33 ` Jean Tourrilhes
2006-09-30 3:31 ` Valdis.Kletnieks
2006-09-30 7:50 ` Valdis.Kletnieks
2006-09-30 8:33 ` Andrew Morton
2006-09-30 1:40 ` Jean Tourrilhes
2006-09-30 3:31 ` Valdis.Kletnieks
2006-09-30 1:57 ` Makefile for linux modules x z
2006-09-30 8:55 ` Sam Ravnborg
2006-09-30 1:59 ` x z
2006-10-02 17:52 ` 2.6.18-mm2 - oops in cache_alloc_refill() Jean Tourrilhes
2006-10-02 19:57 ` Valdis.Kletnieks
2006-10-03 15:58 ` Samuel Tardieu
2006-10-03 16:34 ` Jean Tourrilhes
2006-10-03 16:45 ` Samuel Tardieu
2006-10-03 17:07 ` Jean Tourrilhes
2006-10-05 22:37 ` Pavel Roskin
2006-10-05 22:42 ` Jean Tourrilhes
[not found] ` <20060930133706.GA3291@melchior.yamamaya.is-a-geek.org>
2006-09-30 19:53 ` 2.6.18-mm2 Andrew Morton
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=20061004084540.af17fee5.akpm@osdl.org \
--to=akpm@osdl$(echo .)org \
--cc=ak@suse$(echo .)de \
--cc=drfickle@us$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=vgoyal@in$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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