Re: 2.6.18-mm2

Re: 2.6.18-mm2

[Andrew Morton]

(please always do reply-to-all)

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.

Re: 2.6.18-mm2

[Stephen Hemminger]

On Thu, 28 Sep 2006 14:01:24 -0700
Andrew Morton <akpm@osdl.org> wrote:

> 
> (please always do reply-to-all)
> 
> 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.

That doesn't seem possible given:

static inline struct packet_sock *pkt_sk(struct sock *sk)
{
	return (struct packet_sock *)sk;
}

That means the packet socket list is corrupted??

Stephen Hemminger <shemminger@osdl.org>

Re: 2.6.18-mm2 boot failure on x86-64

[Steve Fox]

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.

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.

-- 

Steve Fox
IBM Linux Technology Center

Re: 2.6.18-mm2 boot failure on x86-64

[Andrew Morton]

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.

Re: 2.6.18-mm2 boot failure on x86-64

[Vivek Goyal]

On Wed, Oct 04, 2006 at 08:45:40AM -0700, Andrew Morton wrote:
> 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?
> 

I thought above patch was dropped because Keith ran into some boot issues
on one of the machines. Though there seems to be nothing wrong with the
patch as such but it might have triggered some existing bug. At that point
of time I looked into the issue but nothing was conclusive.

So looks like this patch has come back. I am not sure how.

Thanks
Vivek

Re: 2.6.18-mm2 boot failure on x86-64

[Andi Kleen]

On Wednesday 04 October 2006 17:45, Andrew Morton wrote:
> 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?

Yes we had this earlier already. But without this patch it doesn't 
compile for some people. So it was readded.

And nobody knows why the reposition-bss patch actually breaks things :/

In theory the reposition is ok, so it must be some marginal code
somewhere else that just ends up failing over.

-Andi

Re: 2.6.18-mm2 boot failure on x86-64

[Keith Mannthey]

On 10/4/06, Andi Kleen <ak@suse.de> wrote:
> On Wednesday 04 October 2006 17:45, Andrew Morton wrote:
> > 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?
>
> Yes we had this earlier already. But without this patch it doesn't
> compile for some people. So it was readded.
>
> And nobody knows why the reposition-bss patch actually breaks things :/

I just wanted to add a chaned up my config file and things went away.
It was not at all clear as to what was causing it.


Thanks,
  Keith

Re: 2.6.18-mm2 boot failure on x86-64

[Steve Fox]

On Wed, 2006-10-04 at 08:45 -0700, Andrew Morton wrote:
> On Wed, 04 Oct 2006 08:42:28 -0500
> Steve Fox <drfickle@us.ibm.com> wrote:
> > 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?

-git21 also fails with this same error.

-- 

Steve Fox
IBM Linux Technology Center

Re: 2.6.18-mm2 boot failure on x86-64

[Andrew Morton]

On Wed, 04 Oct 2006 11:41:59 -0500
Steve Fox <drfickle@us.ibm.com> wrote:

> On Wed, 2006-10-04 at 08:45 -0700, Andrew Morton wrote:
> > On Wed, 04 Oct 2006 08:42:28 -0500
> > Steve Fox <drfickle@us.ibm.com> wrote:
> > > 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?
> 
> -git21 also fails with this same error.
> 

OK, thanks.  And we know that
x86_64-mm-re-positioning-the-bss-segment.patch triggered this failure.  And
that patch is non-buggy, and the xfrm code is probably non-buggy.  So we don't
know squat, and we're going to need to debug this crash.

Well.  There is one trick we could use: apply
x86_64-mm-re-positioning-the-bss-segment.patch to 2.6.18 base and see if it
crashes.  If it doesn't, then we can theorise that the bug is some buggy
post 2.6.18 patch which is being exposed by
x86_64-mm-re-positioning-the-bss-segment.patch.  A technique I've used
before for identifying the buggy patch is to do a git-bisect, but apply
x86_64-mm-re-positioning-the-bss-segment.patch by hand at each bisection
step.  It's pretty straightforward as long as the patch roughly applies at
each step.  

Or we could debug it.  Can you send the .config?  Let's see if it happens
with my toolchain+machine first.

Thanks.

Re: 2.6.18-mm2 boot failure on x86-64

[Vivek Goyal]

On Wed, Oct 04, 2006 at 05:06:59PM -0700, Andrew Morton wrote:
> On Wed, 04 Oct 2006 11:41:59 -0500
> Steve Fox <drfickle@us.ibm.com> wrote:
> 
> > On Wed, 2006-10-04 at 08:45 -0700, Andrew Morton wrote:
> > > On Wed, 04 Oct 2006 08:42:28 -0500
> > > Steve Fox <drfickle@us.ibm.com> wrote:
> > > > 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?
> > 
> > -git21 also fails with this same error.
> > 
> 
> OK, thanks.  And we know that
> x86_64-mm-re-positioning-the-bss-segment.patch triggered this failure.  And
> that patch is non-buggy, and the xfrm code is probably non-buggy.  So we don't
> know squat, and we're going to need to debug this crash.
> 
> Well.  There is one trick we could use: apply
> x86_64-mm-re-positioning-the-bss-segment.patch to 2.6.18 base and see if it
> crashes.  If it doesn't, then we can theorise that the bug is some buggy
> post 2.6.18 patch which is being exposed by

I think most likely it would crash on 2.6.18. Keith mannthey had reported
a different crash on 2.6.18-rc4-mm2 when this patch was introduced first
time. Following is the link to the thread.

http://marc.theaimsgroup.com/?l=linux-kernel&m=115629369729911&w=2

Following is the backtrace he had reported.

 Unable to handle kernel NULL pointer dereference at 0000000000000007
 RIP:
  [<ffffffff803d45b0>] __unix_insert_socket+0x49/0x5a
 PGD 115c934067 PUD 115c935067 PMD 0
 Oops: 0002 [1] SMP
 last sysfs file:
 CPU 14
 Modules linked in:
 Pid: 1, comm: init Not tainted 2.6.18-rc4-mm2-smp #3
 RIP: 0010:[<ffffffff803d45b0>]  [<ffffffff803d45b0>]
 __unix_insert_socket+0x49/0x5a
 RSP: 0018:ffff810460605eb8  EFLAGS: 00010286
 RAX: ffffffffffffffff RBX: ffff81115c171c80 RCX: 0000000000000000
 RDX: ffff81115c171c88 RSI: ffff81115c171c80 RDI: ffffffff806656e0
 RBP: ffffffff806656e0 R08: ffff81115c069200 R09: ffff8110700b4000
 R10: 0000000000000000 R11: 0000000000000002 R12: ffff81115c170d00
 R13: 0000000000000001 R14: 0000000000000001 R15: 0000000000000000
 FS:  00002b793a4fd6d0(0000) GS:ffff81115c910e40(0000)
 knlGS:0000000000000000
 CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
 CR2: 0000000000000007 CR3: 000000115c92d000 CR4: 00000000000006e0
 Process init (pid: 1, threadinfo ffff810460604000, task
 ffff81115cb10040)
 Stack:  0000000100000001 00000000ffffffff ffff81115c171c80
 ffffffff803d58e9
  ffffffff8045bb30 0000000180298f61 ffffffff80498080 0000000000000001
  ffff81115c170d00 ffffffff803d595d 0000000000000004 ffffffff80376061
 Call Trace:
  [<ffffffff803d58e9>] unix_create1+0xf3/0x107
  [<ffffffff803d595d>] unix_create+0x60/0x6b
  [<ffffffff80376061>] __sock_create+0x12f/0x227
  [<ffffffff80376429>] sys_socket+0xf/0x37
  [<ffffffff8020968e>] system_call+0x7e/0x83


 Code: 48 89 50 08 48 89 55 00 48 89 6a 08 41 58 5b 5d c3 c7 47 08
 RIP  [<ffffffff803d45b0>] __unix_insert_socket+0x49/0x5a
  RSP <ffff810460605eb8>
 CR2: 0000000000000007
  <0>Kernel panic - not syncing: Attempted to kill init!

Thanks
Vivek

Re: 2.6.18-mm2 boot failure on x86-64

[Andi Kleen]

> I think most likely it would crash on 2.6.18. Keith mannthey had reported
> a different crash on 2.6.18-rc4-mm2 when this patch was introduced first
> time. Following is the link to the thread.

Then maybe trying 2.6.17 + the patch and then bisect between that and -rc4?

-Andi

Re: 2.6.18-mm2 boot failure on x86-64

[Martin Bligh]

Andi Kleen wrote:
>>I think most likely it would crash on 2.6.18. Keith mannthey had reported
>>a different crash on 2.6.18-rc4-mm2 when this patch was introduced first
>>time. Following is the link to the thread.
> 
> 
> Then maybe trying 2.6.17 + the patch and then bisect between that and -rc4?

I think it's fixed already in -git22, or at least it is for the IBM box
reporting to test.kernel.org. You might want to try that one ...

M.

Re: 2.6.18-mm2 boot failure on x86-64

[Keith Mannthey]

On 10/4/06, Martin Bligh <mbligh@mbligh.org> wrote:
> Andi Kleen wrote:
> >>I think most likely it would crash on 2.6.18. Keith mannthey had reported
> >>a different crash on 2.6.18-rc4-mm2 when this patch was introduced first
> >>time. Following is the link to the thread.
> >
> >
> > Then maybe trying 2.6.17 + the patch and then bisect between that and -rc4?
>
> I think it's fixed already in -git22, or at least it is for the IBM box
> reporting to test.kernel.org. You might want to try that one ...

Fixed or hidden... hard to say at this point.   I think it could be a
werid interaction between patches and or config options.  I will see
tommorrow if I can recreate again.

Thanks,
  Keith

Re: 2.6.18-mm2 boot failure on x86-64

[Steve Fox]

On Wed, 2006-10-04 at 18:08 -0700, Martin Bligh wrote:
> Andi Kleen wrote:
> >>I think most likely it would crash on 2.6.18. Keith mannthey had reported
> >>a different crash on 2.6.18-rc4-mm2 when this patch was introduced first
> >>time. Following is the link to the thread.
> > 
> > 
> > Then maybe trying 2.6.17 + the patch and then bisect between that and -rc4?
> 
> I think it's fixed already in -git22, or at least it is for the IBM box
> reporting to test.kernel.org. You might want to try that one ...

-git22 also panics for me.

-- 

Steve Fox
IBM Linux Technology Center

Re: 2.6.18-mm2 boot failure on x86-64

[Badari Pulavarty]

On Thu, 2006-10-05 at 09:53 -0500, Steve Fox wrote:
> On Wed, 2006-10-04 at 18:08 -0700, Martin Bligh wrote:
> > Andi Kleen wrote:
> > >>I think most likely it would crash on 2.6.18. Keith mannthey had reported
> > >>a different crash on 2.6.18-rc4-mm2 when this patch was introduced first
> > >>time. Following is the link to the thread.
> > > 
> > > 
> > > Then maybe trying 2.6.17 + the patch and then bisect between that and -rc4?
> > 
> > I think it's fixed already in -git22, or at least it is for the IBM box
> > reporting to test.kernel.org. You might want to try that one ...
> 
> -git22 also panics for me.
> 

Steve,

Can you post the latest panic stack again (with CONFIG_DEBUG_KERNEL) ? 
Last time I couldn't match your instruction dump to any code segment
in the routine. And also, can you post your .config file. I have
an amd64 and em64t machine and both work fine...

Thanks,
Badari

Re: 2.6.18-mm2 boot failure on x86-64

[Steve Fox]

On Thu, 2006-10-05 at 08:12 -0700, Badari Pulavarty wrote:

> Can you post the latest panic stack again (with CONFIG_DEBUG_KERNEL) ? 

CONFIG_DEBUG_KERNEL should be on

> Last time I couldn't match your instruction dump to any code segment
> in the routine. And also, can you post your .config file. I have
> an amd64 and em64t machine and both work fine...

Unable to handle kernel NULL pointer dereference at 0000000000000827 RIP:
 [<ffffffff804705e6>] xfrm_register_mode+0x36/0x60
PGD 0
Oops: 0000 [1] SMP
CPU 0
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.18-git22 #1
RIP: 0010:[<ffffffff804705e6>]  [<ffffffff804705e6>] xfrm_register_mode+0x36/0x60
RSP: 0000:ffff810bffcbded0  EFLAGS: 00010286
RAX: 000000000000081f RBX: ffffffff805588a0 RCX: 0000000000000000
RDX: ffffffffffffffff RSI: 0000000000000002 RDI: ffffffff80559550
RBP: 00000000ffffffef R08: 000000003f924371 R09: 0000000000000000
R10: ffff810bffcbdcb0 R11: 0000000000000154 R12: 0000000000000000
R13: ffff810bffcbdef0 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffffffff805d2000(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000000827 CR3: 0000000000201000 CR4: 00000000000006e0
Process swapper (pid: 1, threadinfo ffff810bffcbc000, task ffff810bffcbb4e0)
Stack:  0000000000000000 ffffffff8061fb48 0000000000000000 ffffffff80207182
 0000000000000000 0000000000000000 0000000000000000 0000000000000000
 0000000000000000 0000000000000000 0000000000000000 0000000000090000

The base config file I'm using is at
http://flooterbu.net/kernel/elm3b239-2.6.17.config

-- 

Steve Fox
IBM Linux Technology Center

Re: 2.6.18-mm2 boot failure on x86-64

[Andi Kleen]

On Thursday 05 October 2006 17:32, Steve Fox wrote:
> On Thu, 2006-10-05 at 08:12 -0700, Badari Pulavarty wrote:
> 
> > Can you post the latest panic stack again (with CONFIG_DEBUG_KERNEL) ? 
> 
> CONFIG_DEBUG_KERNEL should be on
> 
> > Last time I couldn't match your instruction dump to any code segment
> > in the routine. And also, can you post your .config file. I have
> > an amd64 and em64t machine and both work fine...
> 
> Unable to handle kernel NULL pointer dereference at 0000000000000827 RIP:
>  [<ffffffff804705e6>] xfrm_register_mode+0x36/0x60
> PGD 0
> Oops: 0000 [1] SMP
> CPU 0
> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.18-git22 #1
> RIP: 0010:[<ffffffff804705e6>]  [<ffffffff804705e6>] xfrm_register_mode+0x36/0x60
> RSP: 0000:ffff810bffcbded0  EFLAGS: 00010286
> RAX: 000000000000081f RBX: ffffffff805588a0 RCX: 0000000000000000
> RDX: ffffffffffffffff RSI: 0000000000000002 RDI: ffffffff80559550
> RBP: 00000000ffffffef R08: 000000003f924371 R09: 0000000000000000
> R10: ffff810bffcbdcb0 R11: 0000000000000154 R12: 0000000000000000
> R13: ffff810bffcbdef0 R14: 0000000000000000 R15: 0000000000000000
> FS:  0000000000000000(0000) GS:ffffffff805d2000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> CR2: 0000000000000827 CR3: 0000000000201000 CR4: 00000000000006e0
> Process swapper (pid: 1, threadinfo ffff810bffcbc000, task ffff810bffcbb4e0)
> Stack:  0000000000000000 ffffffff8061fb48 0000000000000000 ffffffff80207182
>  0000000000000000 0000000000000000 0000000000000000 0000000000000000
>  0000000000000000 0000000000000000 0000000000000000 0000000000090000

Please don't snip the Code: line. It is fairly important.

> 
> The base config file I'm using is at
> http://flooterbu.net/kernel/elm3b239-2.6.17.config

My guess is that something is wrong with the global variable it is accessing.
Can you post the output of grep -5 xfrm_policy_afinfo ? 

I wonder if that variable overlaps something else.

And please add a 
printk("global %p\n",  xfrm_policy_afinfo[family]);
at the beginning of net/xfrm/xfrm_poliy.c:xfrm_policy_lock_afinfo
and post the output.

If not then it's possible
that some nearby variable is overflowing or similar. Adding some padding
around xfrm_policy_afinfo would show that. 

Another way if that global is proven to be corrupted will be to add
checks all over the boot process to track down where it gets corrupted.

-Andi

Re: 2.6.18-mm2 boot failure on x86-64

[Steve Fox]

On Thu, 2006-10-05 at 17:40 +0200, Andi Kleen wrote:

> Please don't snip the Code: line. It is fairly important.

Sorry about that. The remote console I was using appears to overwrite
some text after I force the reboot. Here's a clean one.

global ffffffffffffffff
Unable to handle kernel NULL pointer dereference at 0000000000000827 RIP:
 [<ffffffff80470766>] xfrm_register_mode+0x36/0x60
PGD 0
Oops: 0000 [1] SMP
CPU 0
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.18-git22 #3
RIP: 0010:[<ffffffff80470766>]  [<ffffffff80470766>] xfrm_register_mode+0x36/0x60
RSP: 0000:ffff810bffcbded0  EFLAGS: 00010286
RAX: 000000000000081f RBX: ffffffff805588a0 RCX: 0000000000000000
RDX: ffffffffffffffff RSI: 0000000000000046 RDI: ffffffff80559550
RBP: 00000000ffffffef R08: 0000000000007a02 R09: 000000000000000e
R10: 0000000000000006 R11: ffffffff80334660 R12: 0000000000000000
R13: ffff810bffcbdef0 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffffffff805d2000(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000000827 CR3: 0000000000201000 CR4: 00000000000006e0
Process swapper (pid: 1, threadinfo ffff810bffcbc000, task ffff810bffcbb4e0)
Stack:  0000000000000000 ffffffff8061fb48 0000000000000000 ffffffff80207182
 0000000000000000 0000000000000000 0000000000000000 0000000000000000
 0000000000000000 0000000000000000 0000000000000000 0000000000090000
Call Trace:
 [<ffffffff80207182>] init+0x162/0x330
 [<ffffffff8020a9a8>] child_rip+0xa/0x12
 [<ffffffff803394c2>] acpi_ds_init_one_object+0x0/0x82
 [<ffffffff80207020>] init+0x0/0x330
 [<ffffffff8020a99e>] child_rip+0x0/0x12


Code: 48 83 78 08 00 75 06 48 89 58 08 31 ed 48 89 d7 e8 65 fd ff
RIP  [<ffffffff80470766>] xfrm_register_mode+0x36/0x60
 RSP <ffff810bffcbded0>
CR2: 0000000000000827
 <0>Kernel panic - not syncing: Aiee, killing interrupt handler!

> My guess is that something is wrong with the global variable it is accessing.
> Can you post the output of grep -5 xfrm_policy_afinfo ? 

elm3b239:/boot # grep -5 xfrm_policy_afinfo System.map-2.6.18-git22
ffffffff805594c0 d xfrm4_state_afinfo
ffffffff80559500 D xfrm_cfg_mutex
ffffffff80559530 d xfrm_dev_notifier
ffffffff80559548 d xfrm_policy_lock
ffffffff8055954c d xfrm_policy_gc_lock
ffffffff80559550 d xfrm_policy_afinfo_lock
ffffffff80559560 d xfrm_hash_work
ffffffff805595c0 d hash_resize_mutex
ffffffff80559600 D sysctl_xfrm_aevent_etime
ffffffff80559604 D sysctl_xfrm_aevent_rseqth
ffffffff80559610 D km_waitq
--
ffffffff8075bfd8 b idiagnl
ffffffff8075bfe0 B xfrm_policy_count
ffffffff8075bff8 b xfrm_policy_gc_list
ffffffff8075c000 b dummy.28400
ffffffff8075c038 b idx_generator.27450
ffffffff8075c040 b xfrm_policy_afinfo
ffffffff8075c140 b xfrm_policy_gc_work
ffffffff8075c1a0 b xfrm_policy_inexact
ffffffff8075c1e0 B xfrm_nl
ffffffff8075c1e8 b xfrm_state_gc_list
ffffffff8075c1f0 b acqseq.27386

> And please add a 
> printk("global %p\n",  xfrm_policy_afinfo[family]);
> at the beginning of net/xfrm/xfrm_poliy.c:xfrm_policy_lock_afinfo
> and post the output.

Included above.

-- 

Steve Fox
IBM Linux Technology Center

Re: 2.6.18-mm2 boot failure on x86-64

[Andi Kleen]

On Thursday 05 October 2006 19:57, Steve Fox wrote:
> On Thu, 2006-10-05 at 17:40 +0200, Andi Kleen wrote:
> 
> > Please don't snip the Code: line. It is fairly important.
> 
> Sorry about that. The remote console I was using appears to overwrite
> some text after I force the reboot. Here's a clean one.
> 
> global ffffffffffffffff

Ok that definitely shouldn't be in there.

I guess we need to track when it gets corrupted. Can you send the full
boot log with this patch applied?


-Andi

Index: linux-2.6.19-rc1-hack/init/main.c
===================================================================
--- linux-2.6.19-rc1-hack.orig/init/main.c
+++ linux-2.6.19-rc1-hack/init/main.c
@@ -75,6 +75,9 @@
 
 static int init(void *);
 
+extern void bugcheck(char *, int);
+#define CHECK bugcheck(__FILE__, __LINE__)
+
 extern void init_IRQ(void);
 extern void fork_init(unsigned long);
 extern void mca_init(void);
@@ -480,6 +483,8 @@ asmlinkage void __init start_kernel(void
 	char * command_line;
 	extern struct kernel_param __start___param[], __stop___param[];
 
+	CHECK;
+
 	smp_setup_processor_id();
 
 	/*
@@ -502,7 +507,9 @@ asmlinkage void __init start_kernel(void
 	page_address_init();
 	printk(KERN_NOTICE);
 	printk(linux_banner);
+	CHECK;
 	setup_arch(&command_line);
+	CHECK;
 	setup_per_cpu_areas();
 	smp_prepare_boot_cpu();	/* arch-specific boot-cpu hooks */
 
@@ -517,6 +524,7 @@ asmlinkage void __init start_kernel(void
 	 * fragile until we cpu_idle() for the first time.
 	 */
 	preempt_disable();
+	CHECK;
 	build_all_zonelists();
 	page_alloc_init();
 	printk(KERN_NOTICE "Kernel command line: %s\n", saved_command_line);
@@ -525,6 +533,7 @@ asmlinkage void __init start_kernel(void
 		   __stop___param - __start___param,
 		   &unknown_bootoption);
 	sort_main_extable();
+	CHECK;
 	trap_init();
 	rcu_init();
 	init_IRQ();
@@ -533,8 +542,10 @@ asmlinkage void __init start_kernel(void
 	hrtimers_init();
 	softirq_init();
 	timekeeping_init();
+	CHECK;
 	time_init();
 	profile_init();
+	CHECK;
 	if (!irqs_disabled())
 		printk("start_kernel(): bug: interrupts were enabled early\n");
 	early_boot_irqs_on();
@@ -568,7 +579,9 @@ asmlinkage void __init start_kernel(void
 #endif
 	vfs_caches_init_early();
 	cpuset_init_early();
+	CHECK;
 	mem_init();
+	CHECK;
 	kmem_cache_init();
 	setup_per_cpu_pageset();
 	numa_policy_init();
@@ -577,6 +590,7 @@ asmlinkage void __init start_kernel(void
 	calibrate_delay();
 	pidmap_init();
 	pgtable_cache_init();
+	CHECK;
 	prio_tree_init();
 	anon_vma_init();
 #ifdef CONFIG_X86
@@ -586,12 +600,14 @@ asmlinkage void __init start_kernel(void
 	fork_init(num_physpages);
 	proc_caches_init();
 	buffer_init();
+	CHECK;
 	unnamed_dev_init();
 	key_init();
 	security_init();
 	vfs_caches_init(num_physpages);
 	radix_tree_init();
 	signals_init();
+	CHECK;
 	/* rootfs populating might need page-writeback */
 	page_writeback_init();
 #ifdef CONFIG_PROC_FS
@@ -599,6 +615,7 @@ asmlinkage void __init start_kernel(void
 #endif
 	cpuset_init();
 	taskstats_init_early();
+	CHECK;
 	delayacct_init();
 
 	check_bugs();
@@ -609,7 +626,7 @@ asmlinkage void __init start_kernel(void
 	rest_init();
 }
 
-static int __initdata initcall_debug;
+static int __initdata initcall_debug = 1;
 
 static int __init initcall_debug_setup(char *str)
 {
@@ -639,7 +656,11 @@ static void __init do_initcalls(void)
 			printk("\n");
 		}
 
+		CHECK;
+
 		result = (*call)();
+		
+		CHECK;
 
 		if (result && result != -ENODEV && initcall_debug) {
 			sprintf(msgbuf, "error code %d", result);
@@ -725,21 +746,32 @@ static int init(void * unused)
 
 	smp_prepare_cpus(max_cpus);
 
+	CHECK;
+
 	do_pre_smp_initcalls();
 
 	smp_init();
+
+	CHECK;
+
 	sched_init_smp();
 
 	cpuset_init_smp();
 
+	CHECK;
+
 	/*
 	 * Do this before initcalls, because some drivers want to access
 	 * firmware files.
 	 */
 	populate_rootfs();
 
+	CHECK;
+
 	do_basic_setup();
 
+	CHECK;
+
 	/*
 	 * check if there is an early userspace init.  If yes, let it do all
 	 * the work
Index: linux-2.6.19-rc1-hack/net/xfrm/xfrm_policy.c
===================================================================
--- linux-2.6.19-rc1-hack.orig/net/xfrm/xfrm_policy.c
+++ linux-2.6.19-rc1-hack/net/xfrm/xfrm_policy.c
@@ -39,6 +39,16 @@ EXPORT_SYMBOL(xfrm_policy_count);
 static DEFINE_RWLOCK(xfrm_policy_afinfo_lock);
 static struct xfrm_policy_afinfo *xfrm_policy_afinfo[NPROTO];
 
+void bugcheck(char *where, int line)
+{
+	int i;
+	for (i = 0; i < NPROTO; i++)
+		if (xfrm_policy_afinfo[i] == (void *)-1UL) {
+			printk("afinfo corrupted at %s:%d\n",where,line);
+			return;
+		}
+}
+
 static kmem_cache_t *xfrm_dst_cache __read_mostly;
 
 static struct work_struct xfrm_policy_gc_work;

Re: 2.6.18-mm2 boot failure on x86-64

[Steve Fox]

On Thu, 2006-10-05 at 20:27 +0200, Andi Kleen wrote:

> I guess we need to track when it gets corrupted. Can you send the full
> boot log with this patch applied?

Here she blows!

root (hd0,0)
 Filesystem type is reiserfs, partition type 0x83
kernel /boot/vmlinuz-autobench root=/dev/sda1 vga=791
ip=9.47.67.239:9.47.67.5
0:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts console=tty0
console=ttyS0,
57600 autobench_args: root=/dev/sda1 ABAT:1160073474
   [Linux-bzImage, setup=0x1400, size=0x1dd755]
initrd /boot/initrd-autobench.img
   [Linux-initrd @ 0x37ceb000, 0x304c57 bytes]

Linux version 2.6.18-git22 (root@elm3b239) (gcc version 4.1.0 (SUSE
Linux)) #4 SMP Thu Oct 5 11:36:21 PDT 2006
Command line: root=/dev/sda1 vga=791
ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1
showopts console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1
ABAT:1160073474
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009ac00 (usable)
 BIOS-e820: 000000000009ac00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000bff764c0 (usable)
 BIOS-e820: 00000000bff764c0 - 00000000bff98880 (ACPI data)
 BIOS-e820: 00000000bff98880 - 00000000c0000000 (reserved)
 BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
 BIOS-e820: 0000000100000000 - 0000000c00000000 (usable)
end_pfn_map = 12582912
DMI 2.3 present.
Zone PFN ranges:
  DMA             0 ->     4096
  DMA32        4096 ->  1048576
  Normal    1048576 -> 12582912
early_node_map[3] active PFN ranges
    0:        0 ->      154
    0:      256 ->   786294
    0:  1048576 -> 12582912
ACPI: PM-Timer IO Port: 0x9c
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
Processor #6
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
Processor #7
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x10] enabled)
Processor #16
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x11] enabled)
Processor #17
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x16] enabled)
Processor #22
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x17] enabled)
Processor #23
ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] enabled)
Processor #32
ACPI: LAPIC (acpi_id[0x11] lapic_id[0x21] enabled)
Processor #33
ACPI: LAPIC (acpi_id[0x12] lapic_id[0x26] enabled)
Processor #38
ACPI: LAPIC (acpi_id[0x13] lapic_id[0x27] enabled)
Processor #39
ACPI: LAPIC (acpi_id[0x14] lapic_id[0x30] enabled)
Processor #48
ACPI: LAPIC (acpi_id[0x15] lapic_id[0x31] enabled)
Processor #49
ACPI: LAPIC (acpi_id[0x16] lapic_id[0x36] enabled)
Processor #54
ACPI: LAPIC (acpi_id[0x17] lapic_id[0x37] enabled)
Processor #55
ACPI: LAPIC (acpi_id[0x20] lapic_id[0x40] enabled)
Processor #64
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x21] lapic_id[0x41] enabled)
Processor #65
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x22] lapic_id[0x46] enabled)
Processor #70
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x23] lapic_id[0x47] enabled)
Processor #71
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x24] lapic_id[0x50] enabled)
Processor #80
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x25] lapic_id[0x51] enabled)
Processor #81
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x26] lapic_id[0x56] enabled)
Processor #86
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x27] lapic_id[0x57] enabled)
Processor #87
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x30] lapic_id[0x60] enabled)
Processor #96
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x31] lapic_id[0x61] enabled)
Processor #97
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x32] lapic_id[0x66] enabled)
Processor #102
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x33] lapic_id[0x67] enabled)
Processor #103
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x34] lapic_id[0x70] enabled)
Processor #112
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x35] lapic_id[0x71] enabled)
Processor #113
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x36] lapic_id[0x76] enabled)
Processor #118
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x37] lapic_id[0x77] enabled)
Processor #119
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x10] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x11] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x12] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x13] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x14] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x15] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x16] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x17] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x20] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x21] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x22] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x23] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x24] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x25] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x26] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x27] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x30] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x31] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x32] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x33] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x34] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x35] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x36] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x37] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x0f] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 15, address 0xfec00000, GSI 0-35
ACPI: IOAPIC (id[0x0e] address[0xfec01000] gsi_base[36])
IOAPIC[1]: apic_id 14, address 0xfec01000, GSI 36-71
ACPI: IOAPIC (id[0x0d] address[0xfec02000] gsi_base[72])
IOAPIC[2]: apic_id 13, address 0xfec02000, GSI 72-107
ACPI: IOAPIC (id[0x0c] address[0xfec03000] gsi_base[108])
IOAPIC[3]: apic_id 12, address 0xfec03000, GSI 108-143
ACPI: IOAPIC (id[0x0b] address[0xfec04000] gsi_base[144])
IOAPIC[4]: apic_id 11, address 0xfec04000, GSI 144-179
ACPI: IOAPIC (id[0x0a] address[0xfec05000] gsi_base[180])
IOAPIC[5]: apic_id 10, address 0xfec05000, GSI 180-215
ACPI: IOAPIC (id[0x09] address[0xfec06000] gsi_base[216])
IOAPIC[6]: apic_id 9, address 0xfec06000, GSI 216-251
ACPI: IOAPIC (id[0x08] address[0xfec07000] gsi_base[252])
IOAPIC[7]: apic_id 8, address 0xfec07000, GSI 252-287
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 8 global_irq 8 low edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 low edge)
Setting APIC routing to clustered
ACPI: HPET id: 0x10142201 base: 0xfde84000
Using ACPI (MADT) for SMP configuration information
Nosave address range: 000000000009a000 - 000000000009b000
Nosave address range: 000000000009b000 - 00000000000a0000
Nosave address range: 00000000000a0000 - 00000000000e0000
Nosave address range: 00000000000e0000 - 0000000000100000
Nosave address range: 00000000bff76000 - 00000000bff77000
Nosave address range: 00000000bff77000 - 00000000bff98000
Nosave address range: 00000000bff98000 - 00000000bff99000
Nosave address range: 00000000bff99000 - 00000000c0000000
Nosave address range: 00000000c0000000 - 00000000fec00000
Nosave address range: 00000000fec00000 - 0000000100000000
Allocating PCI resources starting at c4000000 (gap: c0000000:3ec00000)
afinfo corrupted at init/main.c:512
SMP: Allowing 16 CPUs, 0 hotplug CPUs
PERCPU: Allocating 33920 bytes of per cpu data
afinfo corrupted at init/main.c:527
Built 1 zonelists.  Total pages: 12147064
Kernel command line: root=/dev/sda1 vga=791
ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1
showopts console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1
ABAT:1160073474
afinfo corrupted at init/main.c:536
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
afinfo corrupted at init/main.c:545
afinfo corrupted at init/main.c:548
Console: colour VGA+ 80x25
Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes)
Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes)
afinfo corrupted at init/main.c:582
Checking aperture...
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Placing software IO TLB between 0x310c2000 - 0x350c2000
Memory: 48422908k/50331648k available (2566k kernel code, 858868k
reserved, 1345k data, 184k init)
afinfo corrupted at init/main.c:584
Calibrating delay using timer specific routine.. 5677.94 BogoMIPS
(lpj=11355895)
afinfo corrupted at init/main.c:593
afinfo corrupted at init/main.c:603
Mount-cache hash table entries: 256
afinfo corrupted at init/main.c:610
afinfo corrupted at init/main.c:618
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
using mwait in idle threads.
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU0: Thermal monitoring enabled (TM1)
SMP alternatives: switching to UP code
ACPI: Core revision 20060707
..MP-BIOS bug: 8254 timer not connected to IO-APIC
Using local APIC timer interrupts.
result 10425802
Detected 10.425 MHz APIC timer.
afinfo corrupted at init/main.c:749
SMP alternatives: switching to SMP code
Booting processor 1/16 APIC 0x1
Initializing CPU#1
Calibrating delay using timer specific routine.. 5671.84 BogoMIPS
(lpj=11343680)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU1: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 1: Syncing TSC to CPU 0.
CPU 1: synchronized TSC with CPU 0 (last diff -4 cycles, maxerr 799
cycles)
SMP alternatives: switching to SMP code
Booting processor 2/16 APIC 0x6
Initializing CPU#2
Calibrating delay using timer specific routine.. 5671.99 BogoMIPS
(lpj=11343984)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 3
CPU: Processor Core ID: 0
CPU2: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 2: Syncing TSC to CPU 0.
CPU 2: synchronized TSC with CPU 0 (last diff -13 cycles, maxerr 3341
cycles)
SMP alternatives: switching to SMP code
Booting processor 3/16 APIC 0x7
Initializing CPU#3
Calibrating delay using timer specific routine.. 5672.06 BogoMIPS
(lpj=11344129)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 3
CPU: Processor Core ID: 0
CPU3: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 3: Syncing TSC to CPU 0.
CPU 3: synchronized TSC with CPU 0 (last diff 178 cycles, maxerr 3171
cycles)
SMP alternatives: switching to SMP code
Booting processor 4/16 APIC 0x10
Initializing CPU#4
Calibrating delay using timer specific routine.. 5672.04 BogoMIPS
(lpj=11344087)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 8
CPU: Processor Core ID: 0
CPU4: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 4: Syncing TSC to CPU 0.
CPU 4: synchronized TSC with CPU 0 (last diff -420 cycles, maxerr 3510
cycles)
SMP alternatives: switching to SMP code
Booting processor 5/16 APIC 0x11
Initializing CPU#5
Calibrating delay using timer specific routine.. 5672.04 BogoMIPS
(lpj=11344081)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 8
CPU: Processor Core ID: 0
CPU5: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 5: Syncing TSC to CPU 0.
CPU 5: synchronized TSC with CPU 0 (last diff -801 cycles, maxerr 3315
cycles)
SMP alternatives: switching to SMP code
Booting processor 6/16 APIC 0x16
Initializing CPU#6
Calibrating delay using timer specific routine.. 5672.02 BogoMIPS
(lpj=11344046)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 11
CPU: Processor Core ID: 0
CPU6: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 6: Syncing TSC to CPU 0.
CPU 6: synchronized TSC with CPU 0 (last diff -287 cycles, maxerr 3281
cycles)
SMP alternatives: switching to SMP code
Booting processor 7/16 APIC 0x17
Initializing CPU#7
Calibrating delay using timer specific routine.. 5672.01 BogoMIPS
(lpj=11344028)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 11
CPU: Processor Core ID: 0
CPU7: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 7: Syncing TSC to CPU 0.
CPU 7: synchronized TSC with CPU 0 (last diff 238 cycles, maxerr 3391
cycles)
SMP alternatives: switching to SMP code
Booting processor 8/16 APIC 0x20
Initializing CPU#8
Calibrating delay using timer specific routine.. 5672.42 BogoMIPS
(lpj=11344847)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 16
CPU: Processor Core ID: 0
CPU8: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 8: Syncing TSC to CPU 0.
CPU 8: synchronized TSC with CPU 0 (last diff 101 cycles, maxerr 8577
cycles)
SMP alternatives: switching to SMP code
Booting processor 9/16 APIC 0x21
Initializing CPU#9
Calibrating delay using timer specific routine.. 5672.28 BogoMIPS
(lpj=11344576)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 16
CPU: Processor Core ID: 0
CPU9: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 9: Syncing TSC to CPU 0.
CPU 9: synchronized TSC with CPU 0 (last diff 200 cycles, maxerr 8109
cycles)
SMP alternatives: switching to SMP code
Booting processor 10/16 APIC 0x26
Initializing CPU#10
Calibrating delay using timer specific routine.. 5672.50 BogoMIPS
(lpj=11345012)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 19
CPU: Processor Core ID: 0
CPU10: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 10: Syncing TSC to CPU 0.
CPU 10: synchronized TSC with CPU 0 (last diff 72 cycles, maxerr 8551
cycles)
SMP alternatives: switching to SMP code
Booting processor 11/16 APIC 0x27
Initializing CPU#11
Calibrating delay using timer specific routine.. 5672.90 BogoMIPS
(lpj=11345804)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 19
CPU: Processor Core ID: 0
CPU11: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 11: Syncing TSC to CPU 0.
CPU 11: synchronized TSC with CPU 0 (last diff -548 cycles, maxerr 8526
cycles)
SMP alternatives: switching to SMP code
Booting processor 12/16 APIC 0x30
Initializing CPU#12
Calibrating delay using timer specific routine.. 5672.75 BogoMIPS
(lpj=11345516)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 24
CPU: Processor Core ID: 0
CPU12: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 12: Syncing TSC to CPU 0.
CPU 12: synchronized TSC with CPU 0 (last diff 35 cycles, maxerr 8636
cycles)
SMP alternatives: switching to SMP code
Booting processor 13/16 APIC 0x31
Initializing CPU#13
Calibrating delay using timer specific routine.. 5672.55 BogoMIPS
(lpj=11345119)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 24
CPU: Processor Core ID: 0
CPU13: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 13: Syncing TSC to CPU 0.
CPU 13: synchronized TSC with CPU 0 (last diff -1125 cycles, maxerr 7829
cycles)
SMP alternatives: switching to SMP code
Booting processor 14/16 APIC 0x36
Initializing CPU#14
Calibrating delay using timer specific routine.. 5672.25 BogoMIPS
(lpj=11344507)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 27
CPU: Processor Core ID: 0
CPU14: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 14: Syncing TSC to CPU 0.
CPU 14: synchronized TSC with CPU 0 (last diff -796 cycles, maxerr 8568
cycles)
SMP alternatives: switching to SMP code
Booting processor 15/16 APIC 0x37
Initializing CPU#15
Calibrating delay using timer specific routine.. 5672.24 BogoMIPS
(lpj=11344495)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 27
CPU: Processor Core ID: 0
CPU15: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 15: Syncing TSC to CPU 0.
CPU 15: synchronized TSC with CPU 0 (last diff -3 cycles, maxerr 7531
cycles)
Brought up 16 CPUs
testing NMI watchdog ... OK.
time.c: Using 333.333333 MHz WALL PIT GTOD PIT/HPET timer.
time.c: Detected 2835.836 MHz processor.
afinfo corrupted at init/main.c:755
migration_cost=29,1007
afinfo corrupted at init/main.c:761
afinfo corrupted at init/main.c:769
Calling initcall 0xffffffff802166c0: init_smp_flush+0x0/0x60()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806077b0: helper_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607b40: pm_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607bc0: ksysfs_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060a490: filelock_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060afa0: init_script_binfmt+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060afb0: init_elf_binfmt+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80614400: sock_init+0x0/0x60()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80614ba0: netlink_proto_init+0x0/0x1a0()
afinfo corrupted at init/main.c:659
NET: Registered protocol family 16
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c080: kobject_uevent_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c210: pcibus_class_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c7e0: pci_driver_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060eca0: tty_class_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060f790: vtconsole_class_init+0x0/0xc0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c920: acpi_pci_init+0x0/0x40()
afinfo corrupted at init/main.c:659
ACPI: bus type pci registered
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060d65f: init_acpi_device_notify+0x0/0x4b()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80613810: pci_access_init+0x0/0x30()
afinfo corrupted at init/main.c:659
PCI: Using configuration type 1
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806054d0: topology_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806074e0: param_sysfs_init+0x0/0x200()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80249d00: pm_sysrq_init+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ac50: init_bio+0x0/0x110()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bf40: genhd_device_init+0x0/0x60()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060d472: acpi_init+0x0/0x1ed()
afinfo corrupted at init/main.c:659
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060d945: acpi_ec_init+0x0/0x62()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060dd5e: acpi_pci_root_init+0x0/0x28()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060dda6: acpi_pci_link_init+0x0/0x48()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060df2c: acpi_power_init+0x0/0x77()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060dfa3: acpi_system_init+0x0/0xc6()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e069: acpi_event_init+0x0/0x3f()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e0a8: acpi_scan_init+0x0/0x1ac()
afinfo corrupted at init/main.c:659
ACPI: PCI Root Bridge [VP00] (0000:00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:0f.1
ACPI: PCI Root Bridge [VP01] (0000:01)
ACPI: PCI Root Bridge [VP02] (0000:02)
ACPI: PCI Root Bridge [VP03] (0000:04)
ACPI: PCI Root Bridge [VP04] (0000:06)
ACPI: PCI Root Bridge [VP05] (0000:08)
ACPI: PCI Root Bridge [VP06] (0000:0a)
ACPI: PCI Root Bridge [VP07] (0000:0c)
ACPI: PCI Root Bridge [VP10] (0000:0e)
ACPI: PCI Root Bridge [VP11] (0000:0f)
ACPI: PCI Root Bridge [VP12] (0000:10)
ACPI: PCI Root Bridge [VP13] (0000:12)
ACPI: PCI Root Bridge [VP14] (0000:14)
ACPI: PCI Root Bridge [VP15] (0000:16)
ACPI: PCI Root Bridge [VP16] (0000:18)
ACPI: PCI Root Bridge [VP17] (0000:1a)
ACPI: PCI Root Bridge [VP20] (0000:1c)
ACPI: PCI Root Bridge [VP21] (0000:1d)
ACPI: PCI Root Bridge [VP22] (0000:1e)
ACPI: PCI Root Bridge [VP23] (0000:20)
ACPI: PCI Root Bridge [VP24] (0000:22)
ACPI: PCI Root Bridge [VP25] (0000:24)
ACPI: PCI Root Bridge [VP26] (0000:26)
ACPI: PCI Root Bridge [VP27] (0000:28)
ACPI: PCI Root Bridge [VP30] (0000:2a)
ACPI: PCI Root Bridge [VP31] (0000:2b)
ACPI: PCI Root Bridge [VP32] (0000:2c)
ACPI: PCI Root Bridge [VP33] (0000:2e)
ACPI: PCI Root Bridge [VP34] (0000:30)
ACPI: PCI Root Bridge [VP35] (0000:32)
ACPI: PCI Root Bridge [VP36] (0000:34)
ACPI: PCI Root Bridge [VP37] (0000:36)
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e3c4: acpi_cm_sbs_init+0x0/0xc()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e3d0: pnp_init+0x0/0x30()
afinfo corrupted at init/main.c:659
Linux Plug and Play Support v0.97 (c) Adam Belay
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e660: pnpacpi_init+0x0/0x70()
afinfo corrupted at init/main.c:659
pnp: PnP ACPI init
pnp: PnP ACPI: found 47 devices
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060f200: misc_init+0x0/0x90()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80375670: cn_init+0x0/0xe0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611560: init_scsi+0x0/0x90()
afinfo corrupted at init/main.c:659
SCSI subsystem initialized
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612240: serio_init+0x0/0xd0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612660: input_init+0x0/0x120()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612a70: rtc_init+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612ac0: rtc_sysfs_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612ad0: rtc_proc_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612ae0: rtc_dev_init+0x0/0xb0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80613840: pci_acpi_init+0x0/0xb0()
afinfo corrupted at init/main.c:659
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a
report
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806138f0: pci_legacy_init+0x0/0x120()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80613ea0: pcibios_irq_init+0x0/0x4f0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80614390: pcibios_init+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806144c0: proto_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80614660: net_dev_init+0x0/0x210()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80614d40: genl_init+0x0/0xb0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff805fdfc0: late_hpet_init+0x0/0xb0()
afinfo corrupted at init/main.c:659
hpet0: at MMIO 0xfde84000, IRQs 2, 8, 0
hpet0: 3 64-bit timers, 3707069 Hz
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff805ffe20: pci_iommu_init+0x0/0x20()
afinfo corrupted at init/main.c:659
PCI-GART: No AMD northbridge found.
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060a410: init_pipe_fs+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e294: acpi_motherboard_init+0x0/0x130()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e500: pnp_system_init+0x0/0x10()
afinfo corrupted at init/main.c:659
pnp: 00:0a: ioport range 0x400-0x47f has been reserved
pnp: 00:0a: ioport range 0x480-0x4ff could not be reserved
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e9e0: chr_dev_init+0x0/0x80()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806107b0: firmware_class_init+0x0/0x80()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80613220: pcibios_assign_resources+0x0/0x90()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80615750: inet_init+0x0/0x400()
afinfo corrupted at init/main.c:659
NET: Registered protocol family 2
IP route cache hash table entries: 524288 (order: 10, 4194304 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8020db10: time_init_device+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff805fe760: i8259A_init_sysfs+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff805fe730: init_timer_sysfs+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff805fed80: vsyscall_init+0x0/0xb0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff805ff010: sbf_init+0x0/0xe0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff805ffdf0: i8237A_init_sysfs+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80600270: periodic_mcheck_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806002a0: mce_init_device+0x0/0x80()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806003e0: thermal_throttle_init_device
+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80600450: threshold_init_device+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80601c50: init_lapic_sysfs+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806027f0: ioapic_init_sysfs+0x0/0xf0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8021d1f0: cache_sysfs_init+0x0/0x60()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806055e0: x8664_sysctl_init+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80606aa0: create_proc_profile+0x0/0x280()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80606ee0: ioresources_init+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607050: timekeeping_init_device+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607170: uid_cache_init+0x0/0x90()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806076e0: init_posix_timers+0x0/0xd0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806077f0: init_posix_cpu_timers+0x0/0xf0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607910: latency_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607a00: init_clocksource_sysfs+0x0/0x60()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607a60: init_jiffies_clocksource+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607a70: init+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607ae0: proc_dma_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80245840: percpu_modinit+0x0/0x80()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607b10: kallsyms_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607b80: ikconfig_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80608cd0: init_per_zone_pages_min+0x0/0x60()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80609c40: pdflush_init+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80609c90: kswapd_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80609cc0: setup_vmstat+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80609d30: procswaps_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80609da0: hugetlb_init+0x0/0x70()
afinfo corrupted at init/main.c:659
Total HugeTLB memory allocated, 0
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80609e10: init_tmpfs+0x0/0xe0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80609ef0: cpucache_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060a460: fasync_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ab70: aio_setup+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060adf0: inotify_setup+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ae00: inotify_user_setup+0x0/0xc0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060aec0: eventpoll_init+0x0/0xe0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060afc0: init_mbcache+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060aff0: dnotify_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b4b0: init_devpts_fs+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b4f0: init_reiserfs_fs+0x0/0x80()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b570: init_ext3_fs+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b6a0: journal_init+0x0/0xe0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b780: init_ext2_fs+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b840: init_ramfs_fs+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b850: init_hugetlbfs_fs+0x0/0x80()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b910: init_fat_fs+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b960: init_vfat_fs+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b970: init_nls_cp437+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b980: init_nls_iso8859_1+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b990: init_autofs_fs+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b9a0: init_autofs4_fs+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
initcall at 0xffffffff8060b9a0: init_autofs4_fs+0x0/0x10(): returned
with error code -16
Calling initcall 0xffffffff8060b9b0: ipc_init+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bc80: init_mqueue_fs+0x0/0xe0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bd60: crypto_algapi_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bda0: init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bdb0: init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bfa0: noop_init+0x0/0x10()
afinfo corrupted at init/main.c:659
io scheduler noop registered
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bfb0: as_init+0x0/0x10()
afinfo corrupted at init/main.c:659
io scheduler anticipatory registered (default)
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bfc0: deadline_init+0x0/0x10()
afinfo corrupted at init/main.c:659
io scheduler deadline registered
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bfd0: cfq_init+0x0/0xb0()
afinfo corrupted at init/main.c:659
io scheduler cfq registered
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8032c1d0: pci_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c7f0: pci_sysfs_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c830: pci_proc_init+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060d6aa: acpi_ac_init+0x0/0x45()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060d6ef: acpi_battery_init+0x0/0x45()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060dd00: acpi_video_init+0x0/0x5e()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ddee: irqrouter_init_sysfs+0x0/0x38()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ea80: rand_initialize+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060eab0: tty_init+0x0/0x1f0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ed10: pty_init+0x0/0x4f0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060f850: hpet_init+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060f8c0: agp_init+0x0/0x30()
afinfo corrupted at init/main.c:659
Linux agpgart interface v0.101 (c) Dave Jones
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060fa20: cn_proc_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060fe60: serial8250_init+0x0/0x150()
afinfo corrupted at init/main.c:659
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80610090: serial8250_pnp_init+0x0/0x10()
afinfo corrupted at init/main.c:659
00:03: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:04: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806100a0: serial8250_pci_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80384c90: topology_sysfs_init+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80610830: e1000_init_module+0x0/0x50()
afinfo corrupted at init/main.c:659
Intel(R) PRO/1000 Network Driver - version 7.2.9-k2
Copyright (c) 1999-2006 Intel Corporation.
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80610880: tg3_init+0x0/0x10()
afinfo corrupted at init/main.c:659
tg3.c:v3.66 (September 23, 2006)
ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 24 (level, low) -> IRQ 24
eth0: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit)
10/100/1000BaseT Ethernet 00:0d:60:98:63:54
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1]
TSOcap[0]
eth0: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:01:01.1[B] -> GSI 28 (level, low) -> IRQ 28
eth1: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit)
10/100/1000BaseT Ethernet 00:0d:60:98:63:55
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1]
TSOcap[1]
eth1: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:0f:01.0[A] -> GSI 96 (level, low) -> IRQ 96
eth2: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit)
10/100/1000BaseT Ethernet 00:14:5e:1c:45:0c
eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1]
TSOcap[0]
eth2: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:0f:01.1[B] -> GSI 100 (level, low) -> IRQ 100
eth3: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit)
10/100/1000BaseT Ethernet 00:14:5e:1c:45:0d
eth3: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1]
TSOcap[1]
eth3: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:1d:01.0[A] -> GSI 168 (level, low) -> IRQ 168
eth4: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit)
10/100/1000BaseT Ethernet 00:14:5e:1c:45:6c
eth4: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1]
TSOcap[0]
eth4: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:1d:01.1[B] -> GSI 172 (level, low) -> IRQ 172
eth5: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit)
10/100/1000BaseT Ethernet 00:14:5e:1c:45:6d
eth5: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1]
TSOcap[1]
eth5: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:2b:01.0[A] -> GSI 240 (level, low) -> IRQ 240
eth6: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit)
10/100/1000BaseT Ethernet 00:14:5e:1c:43:82
eth6: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1]
TSOcap[0]
eth6: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:2b:01.1[B] -> GSI 244 (level, low) -> IRQ 244
eth7: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit)
10/100/1000BaseT Ethernet 00:14:5e:1c:43:83
eth7: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1]
TSOcap[1]
eth7: dma_rwctrl[769f0000] dma_mask[64-bit]
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80610910: net_olddevs_init+0x0/0xc0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff803a8630: init_netconsole+0x0/0x80()
afinfo corrupted at init/main.c:659
netconsole: not configured, aborting
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff803a8710: cmd64x_ide_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806109e0: piix_ide_init+0x0/0xd0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff803aa810: svwks_ide_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff803ab480: generic_ide_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80610b20: ide_init+0x0/0x90()
afinfo corrupted at init/main.c:659
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
SvrWks CSB6: IDE controller at PCI slot 0000:00:0f.1
SvrWks CSB6: chipset revision 160
SvrWks CSB6: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x0700-0x0707, BIOS settings: hda:DMA, hdb:DMA
SvrWks CSB6: simplex device: DMA disabled
ide1: SvrWks CSB6 Bus-Master DMA disabled (BIOS)
hda: MATSHITADVD-ROM SR-8178, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806114f0: ide_generic_init+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611510: idedisk_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611520: ide_cdrom_init+0x0/0x10()
afinfo corrupted at init/main.c:659
hda: ATAPI 24X DVD-ROM drive, 256kB Cache, UDMA(66)
Uniform CD-ROM driver Revision: 3.20
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611530: idefloppy_init+0x0/0x30()
afinfo corrupted at init/main.c:659
ide-floppy driver 0.99.newide
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611800: raid_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611810: spi_transport_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611850: fc_transport_init+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806118a0: iscsi_transport_init+0x0/0x120()
afinfo corrupted at init/main.c:659
Loading iSCSI transport class v2.0-685.afinfo corrupted at
init/main.c:663
Calling initcall 0xffffffff806119c0: sas_transport_init+0x0/0xc0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611a80: iscsi_tcp_init+0x0/0x50()
afinfo corrupted at init/main.c:659
iscsi: registered transport (tcp)
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611ad0: aac_init+0x0/0x70()
afinfo corrupted at init/main.c:659
Adaptec aacraid driver (1.1-5[2409]-mh2)
ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 25 (level, low) -> IRQ 25
AAC0: kernel 5.0-2[8264]
AAC0: monitor 5.0-2[8264]
AAC0: bios 5.0-2[8264]
AAC0: serial 162348
AAC0: 64bit support enabled.
AAC0: 64 Bit DAC enabled
scsi0 : ServeRAID
scsi 0:0:0:0: Direct-Access     IBM      Drive 1          V1.0 PQ: 0
ANSI: 2
scsi 0:0:1:0: Direct-Access     IBM      Drive 2          V1.0 PQ: 0
ANSI: 2
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611b40: qla1280_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611d10: sym2_init+0x0/0x110()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611e20: init_sd+0x0/0x60()
afinfo corrupted at init/main.c:659
SCSI device sda: 143132672 512-byte hdwr sectors (73284 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
SCSI device sda: 143132672 512-byte hdwr sectors (73284 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
 sda: sda1 sda2 sda3
sd 0:0:0:0: Attached scsi removable disk sda
SCSI device sdb: 143132672 512-byte hdwr sectors (73284 MB)
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
SCSI device sdb: 143132672 512-byte hdwr sectors (73284 MB)
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
 sdb: sdb1 sdb2 sdb3
sd 0:0:1:0: Attached scsi removable disk sdb
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611e80: fusion_init+0x0/0x100()
afinfo corrupted at init/main.c:659
Fusion MPT base driver 3.04.01
Copyright (c) 1999-2005 LSI Logic Corporation
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611f80: mptspi_init+0x0/0xc0()
afinfo corrupted at init/main.c:659
Fusion MPT SPI Host driver 3.04.01
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612040: mptfc_init+0x0/0xf0()
afinfo corrupted at init/main.c:659
Fusion MPT FC Host driver 3.04.01
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612130: mptctl_init+0x0/0x100()
afinfo corrupted at init/main.c:659
Fusion MPT misc device (ioctl) driver 3.04.01
mptctl: Registered with Fusion MPT base driver
mptctl: /dev/mptctl @ (major,minor=10,220)
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612230: cdrom_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612310: i8042_init+0x0/0x350()
afinfo corrupted at init/main.c:659
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612780: mousedev_init+0x0/0x100()
afinfo corrupted at init/main.c:659
mice: PS/2 mouse device common for all mice
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612880: atkbd_init+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612b90: hwmon_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806149d0: flow_cache_init+0x0/0x1d0()
afinfo corrupted at init/main.c:659
input: AT Translated Set 2 keyboard as /class/input/input0
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80615e60: init_syncookies+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80615e80: xfrm4_beet_init+0x0/0x20()
afinfo corrupted at init/main.c:659
Unable to handle kernel NULL pointer dereference at 0000000000000827
RIP:
 [<ffffffff80470666>] xfrm_register_mode+0x36/0x60
PGD 0
Oops: 0000 [1] SMP
CPU 0
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.18-git22 #4
RIP: 0010:[<ffffffff80470666>]  [<ffffffff80470666>] xfrm_register_mode
+0x36/0x60
RSP: 0000:ffff810bffcbded0  EFLAGS: 00010286
RAX: 000000000000081f RBX: ffffffff805588a0 RCX: 0000000000100000
RDX: ffffffffffffffff RSI: 0000000000000002 RDI: ffffffff80559550
RBP: 00000000ffffffef R08: 0000000000000002 R09: fffffffffffffffd
R10: 0000000000000002 R11: 0000000000000000 R12: 0000000000000000
R13: ffff810bffcbdef0 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffffffff805d2000(0000)
knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000000827 CR3: 0000000000201000 CR4: 00000000000006e0
Process swapper (pid: 1, threadinfo ffff810bffcbc000, task
ffff810bffcbb4e0)
Stack:  0000000000000000 0000000000000000 ffffffff8061fc48
ffffffff802071d6
 6f6320726f727265 000036312d206564 0000000000000000 0000000000000000
 0000000000000000 0000000000000000 0000000000000000 0000000000090000
Call Trace:
 [<ffffffff802071d6>] init+0x1b6/0x3b0
 [<ffffffff8020aa28>] child_rip+0xa/0x12
 [<ffffffff80339542>] acpi_ds_init_one_object+0x0/0x82
 [<ffffffff80207020>] init+0x0/0x3b0
 [<ffffffff8020aa1e>] child_rip+0x0/0x12


Code: 48 83 78 08 00 75 06 48 89 58 08 31 ed 48 89 d7 e8 e5 fe ff
RIP  [<ffffffff80470666>] xfrm_register_mode+0x36/0x60
 RSP <ffff810bffcbded0>
CR2: 0000000000000827
 <0>Kernel panic - not syncing: Aiee, killing interrupt handler!

-- 

Steve Fox
IBM Linux Technology Center

Re: 2.6.18-mm2 boot failure on x86-64

[Andi Kleen]

On Thursday 05 October 2006 20:51, Steve Fox wrote:
> On Thu, 2006-10-05 at 20:27 +0200, Andi Kleen wrote:
> 
> > I guess we need to track when it gets corrupted. Can you send the full
> > boot log with this patch applied?
> 
> Here she blows!

Can you please try it again with this patch to narrow it down further?

-Andi

Index: linux-2.6.19-rc1-hack/init/main.c
===================================================================
--- linux-2.6.19-rc1-hack.orig/init/main.c
+++ linux-2.6.19-rc1-hack/init/main.c
@@ -75,6 +75,9 @@
 
 static int init(void *);
 
+extern void bugcheck(char *, int);
+#define CHECK bugcheck(__FILE__, __LINE__)
+
 extern void init_IRQ(void);
 extern void fork_init(unsigned long);
 extern void mca_init(void);
@@ -480,6 +483,8 @@ asmlinkage void __init start_kernel(void
 	char * command_line;
 	extern struct kernel_param __start___param[], __stop___param[];
 
+	CHECK;
+
 	smp_setup_processor_id();
 
 	/*
@@ -502,7 +507,9 @@ asmlinkage void __init start_kernel(void
 	page_address_init();
 	printk(KERN_NOTICE);
 	printk(linux_banner);
+	CHECK;
 	setup_arch(&command_line);
+	CHECK;
 	setup_per_cpu_areas();
 	smp_prepare_boot_cpu();	/* arch-specific boot-cpu hooks */
 
@@ -517,6 +524,7 @@ asmlinkage void __init start_kernel(void
 	 * fragile until we cpu_idle() for the first time.
 	 */
 	preempt_disable();
+	CHECK;
 	build_all_zonelists();
 	page_alloc_init();
 	printk(KERN_NOTICE "Kernel command line: %s\n", saved_command_line);
@@ -525,6 +533,7 @@ asmlinkage void __init start_kernel(void
 		   __stop___param - __start___param,
 		   &unknown_bootoption);
 	sort_main_extable();
+	CHECK;
 	trap_init();
 	rcu_init();
 	init_IRQ();
@@ -533,8 +542,10 @@ asmlinkage void __init start_kernel(void
 	hrtimers_init();
 	softirq_init();
 	timekeeping_init();
+	CHECK;
 	time_init();
 	profile_init();
+	CHECK;
 	if (!irqs_disabled())
 		printk("start_kernel(): bug: interrupts were enabled early\n");
 	early_boot_irqs_on();
@@ -568,7 +579,9 @@ asmlinkage void __init start_kernel(void
 #endif
 	vfs_caches_init_early();
 	cpuset_init_early();
+	CHECK;
 	mem_init();
+	CHECK;
 	kmem_cache_init();
 	setup_per_cpu_pageset();
 	numa_policy_init();
@@ -577,6 +590,7 @@ asmlinkage void __init start_kernel(void
 	calibrate_delay();
 	pidmap_init();
 	pgtable_cache_init();
+	CHECK;
 	prio_tree_init();
 	anon_vma_init();
 #ifdef CONFIG_X86
@@ -586,12 +600,14 @@ asmlinkage void __init start_kernel(void
 	fork_init(num_physpages);
 	proc_caches_init();
 	buffer_init();
+	CHECK;
 	unnamed_dev_init();
 	key_init();
 	security_init();
 	vfs_caches_init(num_physpages);
 	radix_tree_init();
 	signals_init();
+	CHECK;
 	/* rootfs populating might need page-writeback */
 	page_writeback_init();
 #ifdef CONFIG_PROC_FS
@@ -599,6 +615,7 @@ asmlinkage void __init start_kernel(void
 #endif
 	cpuset_init();
 	taskstats_init_early();
+	CHECK;
 	delayacct_init();
 
 	check_bugs();
@@ -609,7 +626,7 @@ asmlinkage void __init start_kernel(void
 	rest_init();
 }
 
-static int __initdata initcall_debug;
+static int __initdata initcall_debug = 1;
 
 static int __init initcall_debug_setup(char *str)
 {
@@ -639,7 +656,11 @@ static void __init do_initcalls(void)
 			printk("\n");
 		}
 
+		CHECK;
+
 		result = (*call)();
+		
+		CHECK;
 
 		if (result && result != -ENODEV && initcall_debug) {
 			sprintf(msgbuf, "error code %d", result);
@@ -725,21 +746,32 @@ static int init(void * unused)
 
 	smp_prepare_cpus(max_cpus);
 
+	CHECK;
+
 	do_pre_smp_initcalls();
 
 	smp_init();
+
+	CHECK;
+
 	sched_init_smp();
 
 	cpuset_init_smp();
 
+	CHECK;
+
 	/*
 	 * Do this before initcalls, because some drivers want to access
 	 * firmware files.
 	 */
 	populate_rootfs();
 
+	CHECK;
+
 	do_basic_setup();
 
+	CHECK;
+
 	/*
 	 * check if there is an early userspace init.  If yes, let it do all
 	 * the work
Index: linux-2.6.19-rc1-hack/net/xfrm/xfrm_policy.c
===================================================================
--- linux-2.6.19-rc1-hack.orig/net/xfrm/xfrm_policy.c
+++ linux-2.6.19-rc1-hack/net/xfrm/xfrm_policy.c
@@ -39,6 +39,16 @@ EXPORT_SYMBOL(xfrm_policy_count);
 static DEFINE_RWLOCK(xfrm_policy_afinfo_lock);
 static struct xfrm_policy_afinfo *xfrm_policy_afinfo[NPROTO];
 
+void bugcheck(char *where, int line)
+{
+	int i;
+	for (i = 0; i < NPROTO; i++)
+		if (xfrm_policy_afinfo[i] == (void *)-1UL) {
+			panic("afinfo corrupted at %s:%d\n",where,line);
+			return;
+		}
+}
+
 static kmem_cache_t *xfrm_dst_cache __read_mostly;
 
 static struct work_struct xfrm_policy_gc_work;
Index: linux-2.6.19-rc1-hack/arch/x86_64/kernel/setup.c
===================================================================
--- linux-2.6.19-rc1-hack.orig/arch/x86_64/kernel/setup.c
+++ linux-2.6.19-rc1-hack/arch/x86_64/kernel/setup.c
@@ -65,6 +65,12 @@
 #include <asm/sections.h>
 #include <asm/dmi.h>
 
+
+
+extern void bugcheck(char *, int);
+#define CHECK bugcheck(__FILE__, __LINE__)
+
+
 /*
  * Machine setup..
  */
@@ -351,14 +357,22 @@ void __init setup_arch(char **cmdline_p)
 	saved_video_mode = SAVED_VIDEO_MODE;
 	bootloader_type = LOADER_TYPE;
 
+	CHECK;
+
 #ifdef CONFIG_BLK_DEV_RAM
 	rd_image_start = RAMDISK_FLAGS & RAMDISK_IMAGE_START_MASK;
 	rd_prompt = ((RAMDISK_FLAGS & RAMDISK_PROMPT_FLAG) != 0);
 	rd_doload = ((RAMDISK_FLAGS & RAMDISK_LOAD_FLAG) != 0);
 #endif
+
+	CHECK;
+
 	setup_memory_region();
+	CHECK;
 	copy_edd();
 
+	CHECK;
+
 	if (!MOUNT_ROOT_RDONLY)
 		root_mountflags &= ~MS_RDONLY;
 	init_mm.start_code = (unsigned long) &_text;
@@ -373,14 +387,25 @@ void __init setup_arch(char **cmdline_p)
 
 	early_identify_cpu(&boot_cpu_data);
 
+	CHECK;
+
+
 	strlcpy(command_line, saved_command_line, COMMAND_LINE_SIZE);
 	*cmdline_p = command_line;
 
+	CHECK;
+
+
 	parse_early_param();
 
+	CHECK;
+
 	finish_e820_parsing();
+	CHECK;
 
 	e820_register_active_regions(0, 0, -1UL);
+	CHECK;
+
 	/*
 	 * partially used pages are not usable - thus
 	 * we are rounding upwards:
@@ -389,14 +414,19 @@ void __init setup_arch(char **cmdline_p)
 	num_physpages = end_pfn;
 
 	check_efer();
+	CHECK;
 
 	discover_ebda();
+	CHECK;
 
 	init_memory_mapping(0, (end_pfn_map << PAGE_SHIFT));
+	CHECK;
 
 	dmi_scan_machine();
+	CHECK;
 
 	zap_low_mappings(0);
+	CHECK;
 
 #ifdef CONFIG_ACPI
 	/*
@@ -405,6 +435,7 @@ void __init setup_arch(char **cmdline_p)
 	 */
 	acpi_boot_table_init();
 #endif
+	CHECK;
 
 	/* How many end-of-memory variables you have, grandma! */
 	max_low_pfn = end_pfn;
@@ -413,6 +444,7 @@ void __init setup_arch(char **cmdline_p)
 
 	/* Remove active ranges so rediscovery with NUMA-awareness happens */
 	remove_all_active_ranges();
+	CHECK;
 
 #ifdef CONFIG_ACPI_NUMA
 	/*
@@ -420,20 +452,24 @@ void __init setup_arch(char **cmdline_p)
 	 */
 	acpi_numa_init();
 #endif
+	CHECK;
 
 #ifdef CONFIG_NUMA
 	numa_initmem_init(0, end_pfn); 
 #else
 	contig_initmem_init(0, end_pfn);
 #endif
+	CHECK;
 
 	/* Reserve direct mapping */
 	reserve_bootmem_generic(table_start << PAGE_SHIFT, 
 				(table_end - table_start) << PAGE_SHIFT);
+	CHECK;
 
 	/* reserve kernel */
 	reserve_bootmem_generic(__pa_symbol(&_text),
 				__pa_symbol(&_end) - __pa_symbol(&_text));
+	CHECK;
 
 	/*
 	 * reserve physical page 0 - it's a special BIOS page on many boxes,
@@ -444,6 +480,7 @@ void __init setup_arch(char **cmdline_p)
 	/* reserve ebda region */
 	if (ebda_addr)
 		reserve_bootmem_generic(ebda_addr, ebda_size);
+	CHECK;
 
 #ifdef CONFIG_SMP
 	/*
@@ -456,6 +493,7 @@ void __init setup_arch(char **cmdline_p)
 	/* Reserve SMP trampoline */
 	reserve_bootmem_generic(SMP_TRAMPOLINE_BASE, PAGE_SIZE);
 #endif
+	CHECK;
 
 #ifdef CONFIG_ACPI_SLEEP
        /*
@@ -463,10 +501,14 @@ void __init setup_arch(char **cmdline_p)
         */
        acpi_reserve_bootmem();
 #endif
+	CHECK;
+
 	/*
 	 * Find and reserve possible boot-time SMP configuration:
 	 */
 	find_smp_config();
+	CHECK;
+
 #ifdef CONFIG_BLK_DEV_INITRD
 	if (LOADER_TYPE && INITRD_START) {
 		if (INITRD_START + INITRD_SIZE <= (end_pfn << PAGE_SHIFT)) {
@@ -484,18 +526,23 @@ void __init setup_arch(char **cmdline_p)
 		}
 	}
 #endif
+	CHECK;
+
 #ifdef CONFIG_KEXEC
 	if (crashk_res.start != crashk_res.end) {
 		reserve_bootmem_generic(crashk_res.start,
 			crashk_res.end - crashk_res.start + 1);
 	}
 #endif
+	CHECK;
 
 	paging_init();
+	CHECK;
 
 #ifdef CONFIG_PCI
 	early_quirks();
 #endif
+	CHECK;
 
 	/*
 	 * set this early, so we dont allocate cpu0
@@ -509,25 +556,36 @@ void __init setup_arch(char **cmdline_p)
 	 */
 	acpi_boot_init();
 #endif
+	CHECK;
 
 	init_cpu_to_node();
+	CHECK;
 
 	/*
 	 * get boot-time SMP configuration:
 	 */
 	if (smp_found_config)
 		get_smp_config();
+	CHECK;
+
 	init_apic_mappings();
+	CHECK;
 
 	/*
 	 * Request address space for all standard RAM and ROM resources
 	 * and also for regions reported as reserved by the e820.
 	 */
 	probe_roms();
+	CHECK;
+
 	e820_reserve_resources(); 
+	CHECK;
+
 	e820_mark_nosave_regions();
+	CHECK;
 
 	request_resource(&iomem_resource, &video_ram_resource);
+	CHECK;
 
 	{
 	unsigned i;
@@ -535,8 +593,10 @@ void __init setup_arch(char **cmdline_p)
 	for (i = 0; i < ARRAY_SIZE(standard_io_resources); i++)
 		request_resource(&ioport_resource, &standard_io_resources[i]);
 	}
+	CHECK;
 
 	e820_setup_gap();
+	CHECK;
 
 #ifdef CONFIG_VT
 #if defined(CONFIG_VGA_CONSOLE)

Re: 2.6.18-mm2 boot failure on x86-64

[Steve Fox]

On Thu, 2006-10-05 at 21:05 +0200, Andi Kleen wrote:

> Can you please try it again with this patch to narrow it down further?

Unfortunately this is as far as it got before it hung.

root (hd0,0)
 Filesystem type is reiserfs, partition type 0x83
kernel /boot/vmlinuz-autobench root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.5
0:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts console=tty0 console=ttyS0,
57600 autobench_args: root=/dev/sda1 ABAT:1160080320
   [Linux-bzImage, setup=0x1400, size=0x1dd871]
initrd /boot/initrd-autobench.img
   [Linux-initrd @ 0x37ceb000, 0x304c57 bytes]


-- 

Steve Fox
IBM Linux Technology Center

Re: 2.6.18-mm2 boot failure on x86-64

[Andi Kleen]

On Thursday 05 October 2006 22:42, Steve Fox wrote:
> On Thu, 2006-10-05 at 21:05 +0200, Andi Kleen wrote:
> 
> > Can you please try it again with this patch to narrow it down further?
> 
> Unfortunately this is as far as it got before it hung.

Boot with earlyprintk=serial,ttyS0,57600
(or change the panic in the checkfunction back to a printk) 

-Andi

Re: 2.6.18-mm2 boot failure on x86-64

[Steve Fox]

On Thu, 2006-10-05 at 22:50 +0200, Andi Kleen wrote:
> On Thursday 05 October 2006 22:42, Steve Fox wrote:
> > On Thu, 2006-10-05 at 21:05 +0200, Andi Kleen wrote:
> > 
> > > Can you please try it again with this patch to narrow it down further?
> > 
> > Unfortunately this is as far as it got before it hung.
> 
> Boot with earlyprintk=serial,ttyS0,57600
> (or change the panic in the checkfunction back to a printk) 

root (hd0,0)
 Filesystem type is reiserfs, partition type 0x83
kernel /boot/vmlinuz-autobench root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.5
0:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57
600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:116010
0417
   [Linux-bzImage, setup=0x1400, size=0x1dd855]
initrd /boot/initrd-autobench.img
   [Linux-initrd @ 0x37cec000, 0x303f80 bytes]

Linux version 2.6.18-git22 (root@elm3b239) (gcc version 4.1.0 (SUSE Linux)) #2 SMP Thu Oct 5 19:05:36 PDT 2006
Command line: root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:1160100417
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009ac00 (usable)
 BIOS-e820: 000000000009ac00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000bff764c0 (usable)
 BIOS-e820: 00000000bff764c0 - 00000000bff98880 (ACPI data)
 BIOS-e820: 00000000bff98880 - 00000000c0000000 (reserved)
 BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
 BIOS-e820: 0000000100000000 - 0000000c00000000 (usable)
end_pfn_map = 12582912
kernel direct mapping tables up to c00000000 @ 8000-39000
DMI 2.3 present.
afinfo corrupted at arch/x86_64/kernel/setup.c:462
afinfo corrupted at arch/x86_64/kernel/setup.c:467
afinfo corrupted at arch/x86_64/kernel/setup.c:472
afinfo corrupted at arch/x86_64/kernel/setup.c:483
afinfo corrupted at arch/x86_64/kernel/setup.c:496
afinfo corrupted at arch/x86_64/kernel/setup.c:504
afinfo corrupted at arch/x86_64/kernel/setup.c:510
afinfo corrupted at arch/x86_64/kernel/setup.c:529
afinfo corrupted at arch/x86_64/kernel/setup.c:537
Zone PFN ranges:
  DMA             0 ->     4096
  DMA32        4096 ->  1048576
  Normal    1048576 -> 12582912
early_node_map[3] active PFN ranges
    0:        0 ->      154
    0:      256 ->   786294
    0:  1048576 -> 12582912
afinfo corrupted at arch/x86_64/kernel/setup.c:540
afinfo corrupted at arch/x86_64/kernel/setup.c:545
ACPI: PM-Timer IO Port: 0x9c
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
Processor #6
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
Processor #7
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x10] enabled)
Processor #16
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x11] enabled)
Processor #17
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x16] enabled)
Processor #22
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x17] enabled)
Processor #23
ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] enabled)
Processor #32
ACPI: LAPIC (acpi_id[0x11] lapic_id[0x21] enabled)
Processor #33
ACPI: LAPIC (acpi_id[0x12] lapic_id[0x26] enabled)
Processor #38
ACPI: LAPIC (acpi_id[0x13] lapic_id[0x27] enabled)
Processor #39
ACPI: LAPIC (acpi_id[0x14] lapic_id[0x30] enabled)
Processor #48
ACPI: LAPIC (acpi_id[0x15] lapic_id[0x31] enabled)
Processor #49
ACPI: LAPIC (acpi_id[0x16] lapic_id[0x36] enabled)
Processor #54
ACPI: LAPIC (acpi_id[0x17] lapic_id[0x37] enabled)
Processor #55
ACPI: LAPIC (acpi_id[0x20] lapic_id[0x40] enabled)
Processor #64
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x21] lapic_id[0x41] enabled)
Processor #65
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x22] lapic_id[0x46] enabled)
Processor #70
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x23] lapic_id[0x47] enabled)
Processor #71
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x24] lapic_id[0x50] enabled)
Processor #80
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x25] lapic_id[0x51] enabled)
Processor #81
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x26] lapic_id[0x56] enabled)
Processor #86
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x27] lapic_id[0x57] enabled)
Processor #87
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x30] lapic_id[0x60] enabled)
Processor #96
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x31] lapic_id[0x61] enabled)
Processor #97
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x32] lapic_id[0x66] enabled)
Processor #102
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x33] lapic_id[0x67] enabled)
Processor #103
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x34] lapic_id[0x70] enabled)
Processor #112
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x35] lapic_id[0x71] enabled)
Processor #113
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x36] lapic_id[0x76] enabled)
Processor #118
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x37] lapic_id[0x77] enabled)
Processor #119
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x10] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x11] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x12] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x13] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x14] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x15] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x16] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x17] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x20] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x21] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x22] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x23] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x24] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x25] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x26] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x27] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x30] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x31] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x32] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x33] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x34] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x35] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x36] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x37] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x0f] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 15, address 0xfec00000, GSI 0-35
ACPI: IOAPIC (id[0x0e] address[0xfec01000] gsi_base[36])
IOAPIC[1]: apic_id 14, address 0xfec01000, GSI 36-71
ACPI: IOAPIC (id[0x0d] address[0xfec02000] gsi_base[72])
IOAPIC[2]: apic_id 13, address 0xfec02000, GSI 72-107
ACPI: IOAPIC (id[0x0c] address[0xfec03000] gsi_base[108])
IOAPIC[3]: apic_id 12, address 0xfec03000, GSI 108-143
ACPI: IOAPIC (id[0x0b] address[0xfec04000] gsi_base[144])
IOAPIC[4]: apic_id 11, address 0xfec04000, GSI 144-179
ACPI: IOAPIC (id[0x0a] address[0xfec05000] gsi_base[180])
IOAPIC[5]: apic_id 10, address 0xfec05000, GSI 180-215
ACPI: IOAPIC (id[0x09] address[0xfec06000] gsi_base[216])
IOAPIC[6]: apic_id 9, address 0xfec06000, GSI 216-251
ACPI: IOAPIC (id[0x08] address[0xfec07000] gsi_base[252])
IOAPIC[7]: apic_id 8, address 0xfec07000, GSI 252-287
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 8 global_irq 8 low edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 low edge)
Setting APIC routing to clustered
ACPI: HPET id: 0x10142201 base: 0xfde84000
afinfo corrupted at arch/x86_64/kernel/setup.c:559
afinfo corrupted at arch/x86_64/kernel/setup.c:562
Using ACPI (MADT) for SMP configuration information
afinfo corrupted at arch/x86_64/kernel/setup.c:569
afinfo corrupted at arch/x86_64/kernel/setup.c:572
afinfo corrupted at arch/x86_64/kernel/setup.c:579
afinfo corrupted at arch/x86_64/kernel/setup.c:582
Nosave address range: 000000000009a000 - 000000000009b000
Nosave address range: 000000000009b000 - 00000000000a0000
Nosave address range: 00000000000a0000 - 00000000000e0000
Nosave address range: 00000000000e0000 - 0000000000100000
Nosave address range: 00000000bff76000 - 00000000bff77000
Nosave address range: 00000000bff77000 - 00000000bff98000
Nosave address range: 00000000bff98000 - 00000000bff99000
Nosave address range: 00000000bff99000 - 00000000c0000000
Nosave address range: 00000000c0000000 - 00000000fec00000
Nosave address range: 00000000fec00000 - 0000000100000000
afinfo corrupted at arch/x86_64/kernel/setup.c:585
afinfo corrupted at arch/x86_64/kernel/setup.c:588
afinfo corrupted at arch/x86_64/kernel/setup.c:596
Allocating PCI resources starting at c4000000 (gap: c0000000:3ec00000)
afinfo corrupted at arch/x86_64/kernel/setup.c:599
afinfo corrupted at init/main.c:512
SMP: Allowing 16 CPUs, 0 hotplug CPUs
PERCPU: Allocating 33920 bytes of per cpu data
afinfo corrupted at init/main.c:527
Built 1 zonelists.  Total pages: 12147064
Kernel command line: root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:1160100417
afinfo corrupted at init/main.c:536
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
afinfo corrupted at init/main.c:545
afinfo corrupted at init/main.c:548
disabling early console
Linux version 2.6.18-git22 (root@elm3b239) (gcc version 4.1.0 (SUSE Linux)) #2 SMP Thu Oct 5 19:05:36 PDT 2006
Command line: root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:1160100417
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009ac00 (usable)
 BIOS-e820: 000000000009ac00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000bff764c0 (usable)
 BIOS-e820: 00000000bff764c0 - 00000000bff98880 (ACPI data)
 BIOS-e820: 00000000bff98880 - 00000000c0000000 (reserved)
 BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
 BIOS-e820: 0000000100000000 - 0000000c00000000 (usable)
end_pfn_map = 12582912
DMI 2.3 present.
afinfo corrupted at arch/x86_64/kernel/setup.c:462
afinfo corrupted at arch/x86_64/kernel/setup.c:467
afinfo corrupted at arch/x86_64/kernel/setup.c:472
afinfo corrupted at arch/x86_64/kernel/setup.c:483
afinfo corrupted at arch/x86_64/kernel/setup.c:496
afinfo corrupted at arch/x86_64/kernel/setup.c:504
afinfo corrupted at arch/x86_64/kernel/setup.c:510
afinfo corrupted at arch/x86_64/kernel/setup.c:529
afinfo corrupted at arch/x86_64/kernel/setup.c:537
Zone PFN ranges:
  DMA             0 ->     4096
  DMA32        4096 ->  1048576
  Normal    1048576 -> 12582912
early_node_map[3] active PFN ranges
    0:        0 ->      154
    0:      256 ->   786294
    0:  1048576 -> 12582912
afinfo corrupted at arch/x86_64/kernel/setup.c:540
afinfo corrupted at arch/x86_64/kernel/setup.c:545
ACPI: PM-Timer IO Port: 0x9c
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
Processor #6
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
Processor #7
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x10] enabled)
Processor #16
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x11] enabled)
Processor #17
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x16] enabled)
Processor #22
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x17] enabled)
Processor #23
ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] enabled)
Processor #32
ACPI: LAPIC (acpi_id[0x11] lapic_id[0x21] enabled)
Processor #33
ACPI: LAPIC (acpi_id[0x12] lapic_id[0x26] enabled)
Processor #38
ACPI: LAPIC (acpi_id[0x13] lapic_id[0x27] enabled)
Processor #39
ACPI: LAPIC (acpi_id[0x14] lapic_id[0x30] enabled)
Processor #48
ACPI: LAPIC (acpi_id[0x15] lapic_id[0x31] enabled)
Processor #49
ACPI: LAPIC (acpi_id[0x16] lapic_id[0x36] enabled)
Processor #54
ACPI: LAPIC (acpi_id[0x17] lapic_id[0x37] enabled)
Processor #55
ACPI: LAPIC (acpi_id[0x20] lapic_id[0x40] enabled)
Processor #64
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x21] lapic_id[0x41] enabled)
Processor #65
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x22] lapic_id[0x46] enabled)
Processor #70
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x23] lapic_id[0x47] enabled)
Processor #71
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x24] lapic_id[0x50] enabled)
Processor #80
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x25] lapic_id[0x51] enabled)
Processor #81
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x26] lapic_id[0x56] enabled)
Processor #86
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x27] lapic_id[0x57] enabled)
Processor #87
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x30] lapic_id[0x60] enabled)
Processor #96
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x31] lapic_id[0x61] enabled)
Processor #97
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x32] lapic_id[0x66] enabled)
Processor #102
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x33] lapic_id[0x67] enabled)
Processor #103
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x34] lapic_id[0x70] enabled)
Processor #112
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x35] lapic_id[0x71] enabled)
Processor #113
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x36] lapic_id[0x76] enabled)
Processor #118
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC (acpi_id[0x37] lapic_id[0x77] enabled)
Processor #119
WARNING: NR_CPUS limit of 16 reached. Processor ignored.
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x10] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x11] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x12] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x13] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x14] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x15] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x16] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x17] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x20] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x21] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x22] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x23] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x24] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x25] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x26] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x27] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x30] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x31] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x32] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x33] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x34] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x35] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x36] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x37] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x0f] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 15, address 0xfec00000, GSI 0-35
ACPI: IOAPIC (id[0x0e] address[0xfec01000] gsi_base[36])
IOAPIC[1]: apic_id 14, address 0xfec01000, GSI 36-71
ACPI: IOAPIC (id[0x0d] address[0xfec02000] gsi_base[72])
IOAPIC[2]: apic_id 13, address 0xfec02000, GSI 72-107
ACPI: IOAPIC (id[0x0c] address[0xfec03000] gsi_base[108])
IOAPIC[3]: apic_id 12, address 0xfec03000, GSI 108-143
ACPI: IOAPIC (id[0x0b] address[0xfec04000] gsi_base[144])
IOAPIC[4]: apic_id 11, address 0xfec04000, GSI 144-179
ACPI: IOAPIC (id[0x0a] address[0xfec05000] gsi_base[180])
IOAPIC[5]: apic_id 10, address 0xfec05000, GSI 180-215
ACPI: IOAPIC (id[0x09] address[0xfec06000] gsi_base[216])
IOAPIC[6]: apic_id 9, address 0xfec06000, GSI 216-251
ACPI: IOAPIC (id[0x08] address[0xfec07000] gsi_base[252])
IOAPIC[7]: apic_id 8, address 0xfec07000, GSI 252-287
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 8 global_irq 8 low edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 low edge)
Setting APIC routing to clustered
ACPI: HPET id: 0x10142201 base: 0xfde84000
afinfo corrupted at arch/x86_64/kernel/setup.c:559
afinfo corrupted at arch/x86_64/kernel/setup.c:562
Using ACPI (MADT) for SMP configuration information
afinfo corrupted at arch/x86_64/kernel/setup.c:569
afinfo corrupted at arch/x86_64/kernel/setup.c:572
afinfo corrupted at arch/x86_64/kernel/setup.c:579
afinfo corrupted at arch/x86_64/kernel/setup.c:582
Nosave address range: 000000000009a000 - 000000000009b000
Nosave address range: 000000000009b000 - 00000000000a0000
Nosave address range: 00000000000a0000 - 00000000000e0000
Nosave address range: 00000000000e0000 - 0000000000100000
Nosave address range: 00000000bff76000 - 00000000bff77000
Nosave address range: 00000000bff77000 - 00000000bff98000
Nosave address range: 00000000bff98000 - 00000000bff99000
Nosave address range: 00000000bff99000 - 00000000c0000000
Nosave address range: 00000000c0000000 - 00000000fec00000
Nosave address range: 00000000fec00000 - 0000000100000000
afinfo corrupted at arch/x86_64/kernel/setup.c:585
afinfo corrupted at arch/x86_64/kernel/setup.c:588
afinfo corrupted at arch/x86_64/kernel/setup.c:596
Allocating PCI resources starting at c4000000 (gap: c0000000:3ec00000)
afinfo corrupted at arch/x86_64/kernel/setup.c:599
afinfo corrupted at init/main.c:512
SMP: Allowing 16 CPUs, 0 hotplug CPUs
PERCPU: Allocating 33920 bytes of per cpu data
afinfo corrupted at init/main.c:527
Built 1 zonelists.  Total pages: 12147064
Kernel command line: root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:1160100417
afinfo corrupted at init/main.c:536
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
afinfo corrupted at init/main.c:545
afinfo corrupted at init/main.c:548
disabling early console
Console: colour VGA+ 80x25
Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes)
Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes)
afinfo corrupted at init/main.c:582
Checking aperture...
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Placing software IO TLB between 0x310c2000 - 0x350c2000
Memory: 48422908k/50331648k available (2566k kernel code, 858868k reserved, 1345k data, 184k init)
afinfo corrupted at init/main.c:584
Calibrating delay using timer specific routine.. 5678.09 BogoMIPS (lpj=11356196)
afinfo corrupted at init/main.c:593
afinfo corrupted at init/main.c:603
Mount-cache hash table entries: 256
afinfo corrupted at init/main.c:610
afinfo corrupted at init/main.c:618
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
using mwait in idle threads.
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU0: Thermal monitoring enabled (TM1)
SMP alternatives: switching to UP code
ACPI: Core revision 20060707
..MP-BIOS bug: 8254 timer not connected to IO-APIC
Using local APIC timer interrupts.
result 10425595
Detected 10.425 MHz APIC timer.
afinfo corrupted at init/main.c:749
SMP alternatives: switching to SMP code
Booting processor 1/16 APIC 0x1
Initializing CPU#1
Calibrating delay using timer specific routine.. 5671.84 BogoMIPS (lpj=11343696)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU1: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 1: Syncing TSC to CPU 0.
CPU 1: synchronized TSC with CPU 0 (last diff -2 cycles, maxerr 799 cycles)
SMP alternatives: switching to SMP code
Booting processor 2/16 APIC 0x6
Initializing CPU#2
Calibrating delay using timer specific routine.. 5671.98 BogoMIPS (lpj=11343971)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 3
CPU: Processor Core ID: 0
CPU2: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 2: Syncing TSC to CPU 0.
CPU 2: synchronized TSC with CPU 0 (last diff -184 cycles, maxerr 3349 cycles)
SMP alternatives: switching to SMP code
Booting processor 3/16 APIC 0x7
Initializing CPU#3
Calibrating delay using timer specific routine.. 5672.02 BogoMIPS (lpj=11344041)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 3
CPU: Processor Core ID: 0
CPU3: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 3: Syncing TSC to CPU 0.
CPU 3: synchronized TSC with CPU 0 (last diff -100 cycles, maxerr 1989 cycles)
SMP alternatives: switching to SMP code
Booting processor 4/16 APIC 0x10
Initializing CPU#4
Calibrating delay using timer specific routine.. 5672.07 BogoMIPS (lpj=11344144)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 8
CPU: Processor Core ID: 0
CPU4: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 4: Syncing TSC to CPU 0.
CPU 4: synchronized TSC with CPU 0 (last diff 43 cycles, maxerr 3247 cycles)
SMP alternatives: switching to SMP code
Booting processor 5/16 APIC 0x11
Initializing CPU#5
Calibrating delay using timer specific routine.. 5672.01 BogoMIPS (lpj=11344024)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 8
CPU: Processor Core ID: 0
CPU5: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 5: Syncing TSC to CPU 0.
CPU 5: synchronized TSC with CPU 0 (last diff 21 cycles, maxerr 3349 cycles)
SMP alternatives: switching to SMP code
Booting processor 6/16 APIC 0x16
Initializing CPU#6
Calibrating delay using timer specific routine.. 5672.02 BogoMIPS (lpj=11344042)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 11
CPU: Processor Core ID: 0
CPU6: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 6: Syncing TSC to CPU 0.
CPU 6: synchronized TSC with CPU 0 (last diff 257 cycles, maxerr 3383 cycles)
SMP alternatives: switching to SMP code
Booting processor 7/16 APIC 0x17
Initializing CPU#7
Calibrating delay using timer specific routine.. 5672.10 BogoMIPS (lpj=11344218)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 11
CPU: Processor Core ID: 0
CPU7: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 7: Syncing TSC to CPU 0.
CPU 7: synchronized TSC with CPU 0 (last diff 233 cycles, maxerr 3357 cycles)
SMP alternatives: switching to SMP code
Booting processor 8/16 APIC 0x20
Initializing CPU#8
Calibrating delay using timer specific routine.. 5672.35 BogoMIPS (lpj=11344712)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 16
CPU: Processor Core ID: 0
CPU8: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 8: Syncing TSC to CPU 0.
CPU 8: synchronized TSC with CPU 0 (last diff 140 cycles, maxerr 8509 cycles)
SMP alternatives: switching to SMP code
Booting processor 9/16 APIC 0x21
Initializing CPU#9
Calibrating delay using timer specific routine.. 5672.25 BogoMIPS (lpj=11344515)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 16
CPU: Processor Core ID: 0
CPU9: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 9: Syncing TSC to CPU 0.
CPU 9: synchronized TSC with CPU 0 (last diff -100 cycles, maxerr 7556 cycles)
SMP alternatives: switching to SMP code
Booting processor 10/16 APIC 0x26
Initializing CPU#10
Calibrating delay using timer specific routine.. 5672.33 BogoMIPS (lpj=11344676)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 19
CPU: Processor Core ID: 0
CPU10: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 10: Syncing TSC to CPU 0.
CPU 10: synchronized TSC with CPU 0 (last diff 405 cycles, maxerr 8126 cycles)
SMP alternatives: switching to SMP code
Booting processor 11/16 APIC 0x27
Initializing CPU#11
Calibrating delay using timer specific routine.. 5672.46 BogoMIPS (lpj=11344939)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 19
CPU: Processor Core ID: 0
CPU11: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 11: Syncing TSC to CPU 0.
CPU 11: synchronized TSC with CPU 0 (last diff -145 cycles, maxerr 8568 cycles)
SMP alternatives: switching to SMP code
Booting processor 12/16 APIC 0x30
Initializing CPU#12
Calibrating delay using timer specific routine.. 5672.23 BogoMIPS (lpj=11344472)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 24
CPU: Processor Core ID: 0
CPU12: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 12: Syncing TSC to CPU 0.
CPU 12: synchronized TSC with CPU 0 (last diff 419 cycles, maxerr 8602 cycles)
SMP alternatives: switching to SMP code
Booting processor 13/16 APIC 0x31
Initializing CPU#13
Calibrating delay using timer specific routine.. 5672.34 BogoMIPS (lpj=11344689)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 24
CPU: Processor Core ID: 0
CPU13: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 13: Syncing TSC to CPU 0.
CPU 13: synchronized TSC with CPU 0 (last diff 242 cycles, maxerr 8636 cycles)
SMP alternatives: switching to SMP code
Booting processor 14/16 APIC 0x36
Initializing CPU#14
Calibrating delay using timer specific routine.. 5672.32 BogoMIPS (lpj=11344644)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 27
CPU: Processor Core ID: 0
CPU14: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 14: Syncing TSC to CPU 0.
CPU 14: synchronized TSC with CPU 0 (last diff -272 cycles, maxerr 8109 cycles)
SMP alternatives: switching to SMP code
Booting processor 15/16 APIC 0x37
Initializing CPU#15
Calibrating delay using timer specific routine.. 5672.21 BogoMIPS (lpj=11344423)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: L3 cache: 4096K
CPU: Physical Processor ID: 27
CPU: Processor Core ID: 0
CPU15: Thermal monitoring enabled (TM1)
               Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
CPU 15: Syncing TSC to CPU 0.
CPU 15: synchronized TSC with CPU 0 (last diff -21 cycles, maxerr 8560 cycles)
Brought up 16 CPUs
testing NMI watchdog ... OK.
time.c: Using 333.333333 MHz WALL PIT GTOD PIT/HPET timer.
time.c: Detected 2835.773 MHz processor.
afinfo corrupted at init/main.c:755
migration_cost=19,988
afinfo corrupted at init/main.c:761
afinfo corrupted at init/main.c:769
Calling initcall 0xffffffff802166c0: init_smp_flush+0x0/0x60()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607a40: helper_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607dd0: pm_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607e50: ksysfs_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060a720: filelock_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b230: init_script_binfmt+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b240: init_elf_binfmt+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80614690: sock_init+0x0/0x60()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80614e30: netlink_proto_init+0x0/0x1a0()
afinfo corrupted at init/main.c:659
NET: Registered protocol family 16
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c310: kobject_uevent_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c4a0: pcibus_class_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ca70: pci_driver_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ef30: tty_class_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060fa20: vtconsole_class_init+0x0/0xc0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060cbb0: acpi_pci_init+0x0/0x40()
afinfo corrupted at init/main.c:659
ACPI: bus type pci registered
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060d8ef: init_acpi_device_notify+0x0/0x4b()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80613aa0: pci_access_init+0x0/0x30()
afinfo corrupted at init/main.c:659
PCI: Using configuration type 1
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80605760: topology_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607770: param_sysfs_init+0x0/0x200()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80249d00: pm_sysrq_init+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060aee0: init_bio+0x0/0x110()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c1d0: genhd_device_init+0x0/0x60()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060d702: acpi_init+0x0/0x1ed()
afinfo corrupted at init/main.c:659
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060dbd5: acpi_ec_init+0x0/0x62()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060dfee: acpi_pci_root_init+0x0/0x28()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e036: acpi_pci_link_init+0x0/0x48()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e1bc: acpi_power_init+0x0/0x77()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e233: acpi_system_init+0x0/0xc6()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e2f9: acpi_event_init+0x0/0x3f()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e338: acpi_scan_init+0x0/0x1ac()
afinfo corrupted at init/main.c:659
ACPI: PCI Root Bridge [VP00] (0000:00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:0f.1
ACPI: PCI Root Bridge [VP01] (0000:01)
ACPI: PCI Root Bridge [VP02] (0000:02)
ACPI: PCI Root Bridge [VP03] (0000:04)
ACPI: PCI Root Bridge [VP04] (0000:06)
ACPI: PCI Root Bridge [VP05] (0000:08)
ACPI: PCI Root Bridge [VP06] (0000:0a)
ACPI: PCI Root Bridge [VP07] (0000:0c)
ACPI: PCI Root Bridge [VP10] (0000:0e)
ACPI: PCI Root Bridge [VP11] (0000:0f)
ACPI: PCI Root Bridge [VP12] (0000:10)
ACPI: PCI Root Bridge [VP13] (0000:12)
ACPI: PCI Root Bridge [VP14] (0000:14)
ACPI: PCI Root Bridge [VP15] (0000:16)
ACPI: PCI Root Bridge [VP16] (0000:18)
ACPI: PCI Root Bridge [VP17] (0000:1a)
ACPI: PCI Root Bridge [VP20] (0000:1c)
ACPI: PCI Root Bridge [VP21] (0000:1d)
ACPI: PCI Root Bridge [VP22] (0000:1e)
ACPI: PCI Root Bridge [VP23] (0000:20)
ACPI: PCI Root Bridge [VP24] (0000:22)
ACPI: PCI Root Bridge [VP25] (0000:24)
ACPI: PCI Root Bridge [VP26] (0000:26)
ACPI: PCI Root Bridge [VP27] (0000:28)
ACPI: PCI Root Bridge [VP30] (0000:2a)
ACPI: PCI Root Bridge [VP31] (0000:2b)
ACPI: PCI Root Bridge [VP32] (0000:2c)
ACPI: PCI Root Bridge [VP33] (0000:2e)
ACPI: PCI Root Bridge [VP34] (0000:30)
ACPI: PCI Root Bridge [VP35] (0000:32)
ACPI: PCI Root Bridge [VP36] (0000:34)
ACPI: PCI Root Bridge [VP37] (0000:36)
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e654: acpi_cm_sbs_init+0x0/0xc()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e660: pnp_init+0x0/0x30()
afinfo corrupted at init/main.c:659
Linux Plug and Play Support v0.97 (c) Adam Belay
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e8f0: pnpacpi_init+0x0/0x70()
afinfo corrupted at init/main.c:659
pnp: PnP ACPI init
pnp: PnP ACPI: found 47 devices
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060f490: misc_init+0x0/0x90()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80375670: cn_init+0x0/0xe0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806117f0: init_scsi+0x0/0x90()
afinfo corrupted at init/main.c:659
SCSI subsystem initialized
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806124d0: serio_init+0x0/0xd0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806128f0: input_init+0x0/0x120()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612d00: rtc_init+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612d50: rtc_sysfs_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612d60: rtc_proc_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612d70: rtc_dev_init+0x0/0xb0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80613ad0: pci_acpi_init+0x0/0xb0()
afinfo corrupted at init/main.c:659
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80613b80: pci_legacy_init+0x0/0x120()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80614130: pcibios_irq_init+0x0/0x4f0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80614620: pcibios_init+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80614750: proto_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806148f0: net_dev_init+0x0/0x210()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80614fd0: genl_init+0x0/0xb0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff805fdfc0: late_hpet_init+0x0/0xb0()
afinfo corrupted at init/main.c:659
hpet0: at MMIO 0xfde84000, IRQs 2, 8, 0
hpet0: 3 64-bit timers, 3707069 Hz
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806000b0: pci_iommu_init+0x0/0x20()
afinfo corrupted at init/main.c:659
PCI-GART: No AMD northbridge found.
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060a6a0: init_pipe_fs+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e524: acpi_motherboard_init+0x0/0x130()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e790: pnp_system_init+0x0/0x10()
afinfo corrupted at init/main.c:659
pnp: 00:0a: ioport range 0x400-0x47f has been reserved
pnp: 00:0a: ioport range 0x480-0x4ff could not be reserved
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ec70: chr_dev_init+0x0/0x80()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80610a40: firmware_class_init+0x0/0x80()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806134b0: pcibios_assign_resources+0x0/0x90()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806159e0: inet_init+0x0/0x400()
afinfo corrupted at init/main.c:659
NET: Registered protocol family 2
IP route cache hash table entries: 524288 (order: 10, 4194304 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8020db10: time_init_device+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff805fe9f0: i8259A_init_sysfs+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff805fe9c0: init_timer_sysfs+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff805ff010: vsyscall_init+0x0/0xb0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff805ff2a0: sbf_init+0x0/0xe0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80600080: i8237A_init_sysfs+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80600500: periodic_mcheck_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80600530: mce_init_device+0x0/0x80()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80600670: thermal_throttle_init_device+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806006e0: threshold_init_device+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80601ee0: init_lapic_sysfs+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80602a80: ioapic_init_sysfs+0x0/0xf0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8021d1f0: cache_sysfs_init+0x0/0x60()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80605870: x8664_sysctl_init+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80606d30: create_proc_profile+0x0/0x280()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607170: ioresources_init+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806072e0: timekeeping_init_device+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607400: uid_cache_init+0x0/0x90()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607970: init_posix_timers+0x0/0xd0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607a80: init_posix_cpu_timers+0x0/0xf0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607ba0: latency_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607c90: init_clocksource_sysfs+0x0/0x60()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607cf0: init_jiffies_clocksource+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607d00: init+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607d70: proc_dma_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80245840: percpu_modinit+0x0/0x80()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607da0: kallsyms_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80607e10: ikconfig_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80608f60: init_per_zone_pages_min+0x0/0x60()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80609ed0: pdflush_init+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80609f20: kswapd_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80609f50: setup_vmstat+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80609fc0: procswaps_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060a030: hugetlb_init+0x0/0x70()
afinfo corrupted at init/main.c:659
Total HugeTLB memory allocated, 0
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060a0a0: init_tmpfs+0x0/0xe0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060a180: cpucache_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060a6f0: fasync_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ae00: aio_setup+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b080: inotify_setup+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b090: inotify_user_setup+0x0/0xc0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b150: eventpoll_init+0x0/0xe0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b250: init_mbcache+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b280: dnotify_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b740: init_devpts_fs+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b780: init_reiserfs_fs+0x0/0x80()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b800: init_ext3_fs+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060b930: journal_init+0x0/0xe0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ba10: init_ext2_fs+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bad0: init_ramfs_fs+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bae0: init_hugetlbfs_fs+0x0/0x80()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bba0: init_fat_fs+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bbf0: init_vfat_fs+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bc00: init_nls_cp437+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bc10: init_nls_iso8859_1+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bc20: init_autofs_fs+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bc30: init_autofs4_fs+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
initcall at 0xffffffff8060bc30: init_autofs4_fs+0x0/0x10(): returned with error code -16
Calling initcall 0xffffffff8060bc40: ipc_init+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bf10: init_mqueue_fs+0x0/0xe0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060bff0: crypto_algapi_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c030: init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c040: init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c230: noop_init+0x0/0x10()
afinfo corrupted at init/main.c:659
io scheduler noop registered
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c240: as_init+0x0/0x10()
afinfo corrupted at init/main.c:659
io scheduler anticipatory registered (default)
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c250: deadline_init+0x0/0x10()
afinfo corrupted at init/main.c:659
io scheduler deadline registered
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060c260: cfq_init+0x0/0xb0()
afinfo corrupted at init/main.c:659
io scheduler cfq registered
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8032c1d0: pci_init+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ca80: pci_sysfs_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060cac0: pci_proc_init+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060d93a: acpi_ac_init+0x0/0x45()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060d97f: acpi_battery_init+0x0/0x45()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060df90: acpi_video_init+0x0/0x5e()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060e07e: irqrouter_init_sysfs+0x0/0x38()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ed10: rand_initialize+0x0/0x30()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060ed40: tty_init+0x0/0x1f0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060efa0: pty_init+0x0/0x4f0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060fae0: hpet_init+0x0/0x70()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060fb50: agp_init+0x0/0x30()
afinfo corrupted at init/main.c:659
Linux agpgart interface v0.101 (c) Dave Jones
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff8060fcb0: cn_proc_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806100f0: serial8250_init+0x0/0x150()
afinfo corrupted at init/main.c:659
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80610320: serial8250_pnp_init+0x0/0x10()
afinfo corrupted at init/main.c:659
00:03: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:04: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80610330: serial8250_pci_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80384c90: topology_sysfs_init+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80610ac0: e1000_init_module+0x0/0x50()
afinfo corrupted at init/main.c:659
Intel(R) PRO/1000 Network Driver - version 7.2.9-k2
Copyright (c) 1999-2006 Intel Corporation.
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80610b10: tg3_init+0x0/0x10()
afinfo corrupted at init/main.c:659
tg3.c:v3.66 (September 23, 2006)
ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 24 (level, low) -> IRQ 24
eth0: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:60:98:63:54
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
eth0: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:01:01.1[B] -> GSI 28 (level, low) -> IRQ 28
eth1: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:60:98:63:55
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth1: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:0f:01.0[A] -> GSI 96 (level, low) -> IRQ 96
eth2: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:1c:45:0c
eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
eth2: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:0f:01.1[B] -> GSI 100 (level, low) -> IRQ 100
eth3: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:1c:45:0d
eth3: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth3: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:1d:01.0[A] -> GSI 168 (level, low) -> IRQ 168
eth4: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:1c:45:6c
eth4: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
eth4: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:1d:01.1[B] -> GSI 172 (level, low) -> IRQ 172
eth5: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:1c:45:6d
eth5: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth5: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:2b:01.0[A] -> GSI 240 (level, low) -> IRQ 240
eth6: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:1c:43:82
eth6: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
eth6: dma_rwctrl[769f0000] dma_mask[64-bit]
ACPI: PCI Interrupt 0000:2b:01.1[B] -> GSI 244 (level, low) -> IRQ 244
eth7: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:1c:43:83
eth7: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth7: dma_rwctrl[769f0000] dma_mask[64-bit]
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80610ba0: net_olddevs_init+0x0/0xc0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff803a8630: init_netconsole+0x0/0x80()
afinfo corrupted at init/main.c:659
netconsole: not configured, aborting
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff803a8710: cmd64x_ide_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80610c70: piix_ide_init+0x0/0xd0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff803aa810: svwks_ide_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff803ab480: generic_ide_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80610db0: ide_init+0x0/0x90()
afinfo corrupted at init/main.c:659
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SvrWks CSB6: IDE controller at PCI slot 0000:00:0f.1
SvrWks CSB6: chipset revision 160
SvrWks CSB6: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x0700-0x0707, BIOS settings: hda:DMA, hdb:DMA
SvrWks CSB6: simplex device: DMA disabled
ide1: SvrWks CSB6 Bus-Master DMA disabled (BIOS)
hda: MATSHITADVD-ROM SR-8178, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611780: ide_generic_init+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806117a0: idedisk_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806117b0: ide_cdrom_init+0x0/0x10()
afinfo corrupted at init/main.c:659
hda: ATAPI 24X DVD-ROM drive, 256kB Cache, UDMA(66)
Uniform CD-ROM driver Revision: 3.20
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806117c0: idefloppy_init+0x0/0x30()
afinfo corrupted at init/main.c:659
ide-floppy driver 0.99.newide
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611a90: raid_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611aa0: spi_transport_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611ae0: fc_transport_init+0x0/0x50()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611b30: iscsi_transport_init+0x0/0x120()
afinfo corrupted at init/main.c:659
Loading iSCSI transport class v2.0-685.afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611c50: sas_transport_init+0x0/0xc0()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611d10: iscsi_tcp_init+0x0/0x50()
afinfo corrupted at init/main.c:659
iscsi: registered transport (tcp)
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611d60: aac_init+0x0/0x70()
afinfo corrupted at init/main.c:659
Adaptec aacraid driver (1.1-5[2409]-mh2)
ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 25 (level, low) -> IRQ 25
AAC0: kernel 5.0-2[8264]
AAC0: monitor 5.0-2[8264]
AAC0: bios 5.0-2[8264]
AAC0: serial 162348
AAC0: 64bit support enabled.
AAC0: 64 Bit DAC enabled
scsi0 : ServeRAID
scsi 0:0:0:0: Direct-Access     IBM      Drive 1          V1.0 PQ: 0 ANSI: 2
scsi 0:0:1:0: Direct-Access     IBM      Drive 2          V1.0 PQ: 0 ANSI: 2
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611dd0: qla1280_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80611fa0: sym2_init+0x0/0x110()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806120b0: init_sd+0x0/0x60()
afinfo corrupted at init/main.c:659
SCSI device sda: 143132672 512-byte hdwr sectors (73284 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
SCSI device sda: 143132672 512-byte hdwr sectors (73284 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
 sda: sda1 sda2 sda3
sd 0:0:0:0: Attached scsi removable disk sda
SCSI device sdb: 143132672 512-byte hdwr sectors (73284 MB)
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
SCSI device sdb: 143132672 512-byte hdwr sectors (73284 MB)
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
 sdb: sdb1 sdb2 sdb3
sd 0:0:1:0: Attached scsi removable disk sdb
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612110: fusion_init+0x0/0x100()
afinfo corrupted at init/main.c:659
Fusion MPT base driver 3.04.01
Copyright (c) 1999-2005 LSI Logic Corporation
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612210: mptspi_init+0x0/0xc0()
afinfo corrupted at init/main.c:659
Fusion MPT SPI Host driver 3.04.01
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806122d0: mptfc_init+0x0/0xf0()
afinfo corrupted at init/main.c:659
Fusion MPT FC Host driver 3.04.01
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806123c0: mptctl_init+0x0/0x100()
afinfo corrupted at init/main.c:659
Fusion MPT misc device (ioctl) driver 3.04.01
mptctl: Registered with Fusion MPT base driver
mptctl: /dev/mptctl @ (major,minor=10,220)
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806124c0: cdrom_init+0x0/0x10()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806125a0: i8042_init+0x0/0x350()
afinfo corrupted at init/main.c:659
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612a10: mousedev_init+0x0/0x100()
afinfo corrupted at init/main.c:659
mice: PS/2 mouse device common for all mice
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612b10: atkbd_init+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80612e20: hwmon_init+0x0/0x40()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80614c60: flow_cache_init+0x0/0x1d0()
afinfo corrupted at init/main.c:659
input: AT Translated Set 2 keyboard as /class/input/input0
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff806160f0: init_syncookies+0x0/0x20()
afinfo corrupted at init/main.c:659
afinfo corrupted at init/main.c:663
Calling initcall 0xffffffff80616110: xfrm4_beet_init+0x0/0x20()
afinfo corrupted at init/main.c:659
Unable to handle kernel NULL pointer dereference at 0000000000000827 RIP:
 [<ffffffff80470666>] xfrm_register_mode+0x36/0x60
PGD 0
Oops: 0000 [1] SMP
CPU 0
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.18-git22 #2
RIP: 0010:[<ffffffff80470666>]  [<ffffffff80470666>] xfrm_register_mode+0x36/0x60
RSP: 0000:ffff810bffcbded0  EFLAGS: 00010286
RAX: 000000000000081f RBX: ffffffff805588a0 RCX: 0000000000100000
RDX: ffffffffffffffff RSI: 0000000000000002 RDI: ffffffff80559550
RBP: 00000000ffffffef R08: 0000000000000002 R09: fffffffffffffffd
R10: 0000000000000002 R11: 0000000000000000 R12: 0000000000000000
R13: ffff810bffcbdef0 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffffffff805d2000(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000000827 CR3: 0000000000201000 CR4: 00000000000006e0
Process swapper (pid: 1, threadinfo ffff810bffcbc000, task ffff810bffcbb4e0)
Stack:  0000000000000000 0000000000000000 ffffffff8061fee8 ffffffff802071d6
 6f6320726f727265 000036312d206564 0000000000000000 0000000000000000
 0000000000000000 0000000000000000 0000000000000000 0000000000090000
Call Trace:
 [<ffffffff802071d6>] init+0x1b6/0x3b0
 [<ffffffff8020aa28>] child_rip+0xa/0x12
 [<ffffffff80339542>] acpi_ds_init_one_object+0x0/0x82
 [<ffffffff80207020>] init+0x0/0x3b0
 [<ffffffff8020aa1e>] child_rip+0x0/0x12


Code: 48 83 78 08 00 75 06 48 89 58 08 31 ed 48 89 d7 e8 e5 fe ff
RIP  [<ffffffff80470666>] xfrm_register_mode+0x36/0x60
 RSP <ffff810bffcbded0>
CR2: 0000000000000827
 <0>Kernel panic - not syncing: Aiee, killing interrupt handler!


-- 

Steve Fox
IBM Linux Technology Center

Re: 2.6.18-mm2 boot failure on x86-64

[Mel Gorman]

On (05/10/06 21:23), Steve Fox didst pronounce:
> On Thu, 2006-10-05 at 22:50 +0200, Andi Kleen wrote:
> > On Thursday 05 October 2006 22:42, Steve Fox wrote:
> > > On Thu, 2006-10-05 at 21:05 +0200, Andi Kleen wrote:
> > > 
> > > > Can you please try it again with this patch to narrow it down further?
> > > 
> > > Unfortunately this is as far as it got before it hung.
> > 
> > Boot with earlyprintk=serial,ttyS0,57600
> > (or change the panic in the checkfunction back to a printk) 
> 
> root (hd0,0)
>  Filesystem type is reiserfs, partition type 0x83
> kernel /boot/vmlinuz-autobench root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.5
> 0:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57
> 600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:116010
> 0417
>    [Linux-bzImage, setup=0x1400, size=0x1dd855]
> initrd /boot/initrd-autobench.img
>    [Linux-initrd @ 0x37cec000, 0x303f80 bytes]
> 
> Linux version 2.6.18-git22 (root@elm3b239) (gcc version 4.1.0 (SUSE Linux)) #2 SMP Thu Oct 5 19:05:36 PDT 2006
> Command line: root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:1160100417
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 000000000009ac00 (usable)
>  BIOS-e820: 000000000009ac00 - 00000000000a0000 (reserved)
>  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 00000000bff764c0 (usable)
>  BIOS-e820: 00000000bff764c0 - 00000000bff98880 (ACPI data)
>  BIOS-e820: 00000000bff98880 - 00000000c0000000 (reserved)
>  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
>  BIOS-e820: 0000000100000000 - 0000000c00000000 (usable)

I continued what Steve was doing this morning to see could this be
pinned down. After placing 'CHECK;' in a few places as suggested by
Andi's check, the problem code was identified as that following in
mm/bootmem.c#init_bootmem_core()

        mapsize = get_mapsize(bdata);
        memset(bdata->node_bootmem_map, 0xff, mapsize);

That explains the value in the array at least. A few more printfs around
this point printed out the following in the boot log

init_bootmem_core(0, 1909, 0, 12582912)
init_bootmem_core: Calling memset(0xFFFF810000775000, 1572864)
AAGH: afinfo corrupted at mm/bootmem.c:121

where;

1909 == mapstart
0 == start
12582912 == end
1572864 == mapsize

mapstart, start and end being the parameters being passed to
init_bootmem_core(). This means we are calling memset for the physical
range 0x775000 -> 0x8F5000 which is in a usable range according to the
BIOS-e820 map it appears.

However with 2.6.18-git22, a backout of the patch
x86_64-mm-re-positioning-the-bss-segment.patch from 2.6.18-mm2 allowed the
machine to boot. As this patch moves the BSS past the end of the init section,
it seems that an unintentional side-effect of the patch that BSS ends up in
a place that init_bootmem clobbers it.

> end_pfn_map = 12582912
> kernel direct mapping tables up to c00000000 @ 8000-39000
> DMI 2.3 present.
> afinfo corrupted at arch/x86_64/kernel/setup.c:462
> afinfo corrupted at arch/x86_64/kernel/setup.c:467
> afinfo corrupted at arch/x86_64/kernel/setup.c:472
> afinfo corrupted at arch/x86_64/kernel/setup.c:483
> afinfo corrupted at arch/x86_64/kernel/setup.c:496
> afinfo corrupted at arch/x86_64/kernel/setup.c:504
> afinfo corrupted at arch/x86_64/kernel/setup.c:510
> afinfo corrupted at arch/x86_64/kernel/setup.c:529
> afinfo corrupted at arch/x86_64/kernel/setup.c:537
> Zone PFN ranges:
>   DMA             0 ->     4096
>   DMA32        4096 ->  1048576
>   Normal    1048576 -> 12582912
> early_node_map[3] active PFN ranges
>     0:        0 ->      154
>     0:      256 ->   786294
>     0:  1048576 -> 12582912
> afinfo corrupted at arch/x86_64/kernel/setup.c:540
> afinfo corrupted at arch/x86_64/kernel/setup.c:545
> ACPI: PM-Timer IO Port: 0x9c
> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> Processor #0 (Bootup-CPU)
> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> Processor #1
> ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
> Processor #6
> ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
> Processor #7
> ACPI: LAPIC (acpi_id[0x04] lapic_id[0x10] enabled)
> Processor #16
> ACPI: LAPIC (acpi_id[0x05] lapic_id[0x11] enabled)
> Processor #17
> ACPI: LAPIC (acpi_id[0x06] lapic_id[0x16] enabled)
> Processor #22
> ACPI: LAPIC (acpi_id[0x07] lapic_id[0x17] enabled)
> Processor #23
> ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] enabled)
> Processor #32
> ACPI: LAPIC (acpi_id[0x11] lapic_id[0x21] enabled)
> Processor #33
> ACPI: LAPIC (acpi_id[0x12] lapic_id[0x26] enabled)
> Processor #38
> ACPI: LAPIC (acpi_id[0x13] lapic_id[0x27] enabled)
> Processor #39
> ACPI: LAPIC (acpi_id[0x14] lapic_id[0x30] enabled)
> Processor #48
> ACPI: LAPIC (acpi_id[0x15] lapic_id[0x31] enabled)
> Processor #49
> ACPI: LAPIC (acpi_id[0x16] lapic_id[0x36] enabled)
> Processor #54
> ACPI: LAPIC (acpi_id[0x17] lapic_id[0x37] enabled)
> Processor #55
> ACPI: LAPIC (acpi_id[0x20] lapic_id[0x40] enabled)
> Processor #64
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x21] lapic_id[0x41] enabled)
> Processor #65
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x22] lapic_id[0x46] enabled)
> Processor #70
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x23] lapic_id[0x47] enabled)
> Processor #71
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x24] lapic_id[0x50] enabled)
> Processor #80
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x25] lapic_id[0x51] enabled)
> Processor #81
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x26] lapic_id[0x56] enabled)
> Processor #86
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x27] lapic_id[0x57] enabled)
> Processor #87
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x30] lapic_id[0x60] enabled)
> Processor #96
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x31] lapic_id[0x61] enabled)
> Processor #97
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x32] lapic_id[0x66] enabled)
> Processor #102
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x33] lapic_id[0x67] enabled)
> Processor #103
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x34] lapic_id[0x70] enabled)
> Processor #112
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x35] lapic_id[0x71] enabled)
> Processor #113
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x36] lapic_id[0x76] enabled)
> Processor #118
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x37] lapic_id[0x77] enabled)
> Processor #119
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x10] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x11] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x12] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x13] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x14] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x15] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x16] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x17] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x20] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x21] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x22] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x23] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x24] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x25] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x26] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x27] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x30] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x31] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x32] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x33] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x34] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x35] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x36] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x37] dfl dfl lint[0x1])
> ACPI: IOAPIC (id[0x0f] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: apic_id 15, address 0xfec00000, GSI 0-35
> ACPI: IOAPIC (id[0x0e] address[0xfec01000] gsi_base[36])
> IOAPIC[1]: apic_id 14, address 0xfec01000, GSI 36-71
> ACPI: IOAPIC (id[0x0d] address[0xfec02000] gsi_base[72])
> IOAPIC[2]: apic_id 13, address 0xfec02000, GSI 72-107
> ACPI: IOAPIC (id[0x0c] address[0xfec03000] gsi_base[108])
> IOAPIC[3]: apic_id 12, address 0xfec03000, GSI 108-143
> ACPI: IOAPIC (id[0x0b] address[0xfec04000] gsi_base[144])
> IOAPIC[4]: apic_id 11, address 0xfec04000, GSI 144-179
> ACPI: IOAPIC (id[0x0a] address[0xfec05000] gsi_base[180])
> IOAPIC[5]: apic_id 10, address 0xfec05000, GSI 180-215
> ACPI: IOAPIC (id[0x09] address[0xfec06000] gsi_base[216])
> IOAPIC[6]: apic_id 9, address 0xfec06000, GSI 216-251
> ACPI: IOAPIC (id[0x08] address[0xfec07000] gsi_base[252])
> IOAPIC[7]: apic_id 8, address 0xfec07000, GSI 252-287
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 8 global_irq 8 low edge)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 low edge)
> Setting APIC routing to clustered
> ACPI: HPET id: 0x10142201 base: 0xfde84000
> afinfo corrupted at arch/x86_64/kernel/setup.c:559
> afinfo corrupted at arch/x86_64/kernel/setup.c:562
> Using ACPI (MADT) for SMP configuration information
> afinfo corrupted at arch/x86_64/kernel/setup.c:569
> afinfo corrupted at arch/x86_64/kernel/setup.c:572
> afinfo corrupted at arch/x86_64/kernel/setup.c:579
> afinfo corrupted at arch/x86_64/kernel/setup.c:582
> Nosave address range: 000000000009a000 - 000000000009b000
> Nosave address range: 000000000009b000 - 00000000000a0000
> Nosave address range: 00000000000a0000 - 00000000000e0000
> Nosave address range: 00000000000e0000 - 0000000000100000
> Nosave address range: 00000000bff76000 - 00000000bff77000
> Nosave address range: 00000000bff77000 - 00000000bff98000
> Nosave address range: 00000000bff98000 - 00000000bff99000
> Nosave address range: 00000000bff99000 - 00000000c0000000
> Nosave address range: 00000000c0000000 - 00000000fec00000
> Nosave address range: 00000000fec00000 - 0000000100000000
> afinfo corrupted at arch/x86_64/kernel/setup.c:585
> afinfo corrupted at arch/x86_64/kernel/setup.c:588
> afinfo corrupted at arch/x86_64/kernel/setup.c:596
> Allocating PCI resources starting at c4000000 (gap: c0000000:3ec00000)
> afinfo corrupted at arch/x86_64/kernel/setup.c:599
> afinfo corrupted at init/main.c:512
> SMP: Allowing 16 CPUs, 0 hotplug CPUs
> PERCPU: Allocating 33920 bytes of per cpu data
> afinfo corrupted at init/main.c:527
> Built 1 zonelists.  Total pages: 12147064
> Kernel command line: root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:1160100417
> afinfo corrupted at init/main.c:536
> Initializing CPU#0
> PID hash table entries: 4096 (order: 12, 32768 bytes)
> afinfo corrupted at init/main.c:545
> afinfo corrupted at init/main.c:548
> disabling early console
> Linux version 2.6.18-git22 (root@elm3b239) (gcc version 4.1.0 (SUSE Linux)) #2 SMP Thu Oct 5 19:05:36 PDT 2006
> Command line: root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:1160100417
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 000000000009ac00 (usable)
>  BIOS-e820: 000000000009ac00 - 00000000000a0000 (reserved)
>  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 00000000bff764c0 (usable)
>  BIOS-e820: 00000000bff764c0 - 00000000bff98880 (ACPI data)
>  BIOS-e820: 00000000bff98880 - 00000000c0000000 (reserved)
>  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
>  BIOS-e820: 0000000100000000 - 0000000c00000000 (usable)
> end_pfn_map = 12582912
> DMI 2.3 present.
> afinfo corrupted at arch/x86_64/kernel/setup.c:462
> afinfo corrupted at arch/x86_64/kernel/setup.c:467
> afinfo corrupted at arch/x86_64/kernel/setup.c:472
> afinfo corrupted at arch/x86_64/kernel/setup.c:483
> afinfo corrupted at arch/x86_64/kernel/setup.c:496
> afinfo corrupted at arch/x86_64/kernel/setup.c:504
> afinfo corrupted at arch/x86_64/kernel/setup.c:510
> afinfo corrupted at arch/x86_64/kernel/setup.c:529
> afinfo corrupted at arch/x86_64/kernel/setup.c:537
> Zone PFN ranges:
>   DMA             0 ->     4096
>   DMA32        4096 ->  1048576
>   Normal    1048576 -> 12582912
> early_node_map[3] active PFN ranges
>     0:        0 ->      154
>     0:      256 ->   786294
>     0:  1048576 -> 12582912
> afinfo corrupted at arch/x86_64/kernel/setup.c:540
> afinfo corrupted at arch/x86_64/kernel/setup.c:545
> ACPI: PM-Timer IO Port: 0x9c
> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> Processor #0 (Bootup-CPU)
> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
> Processor #1
> ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
> Processor #6
> ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled)
> Processor #7
> ACPI: LAPIC (acpi_id[0x04] lapic_id[0x10] enabled)
> Processor #16
> ACPI: LAPIC (acpi_id[0x05] lapic_id[0x11] enabled)
> Processor #17
> ACPI: LAPIC (acpi_id[0x06] lapic_id[0x16] enabled)
> Processor #22
> ACPI: LAPIC (acpi_id[0x07] lapic_id[0x17] enabled)
> Processor #23
> ACPI: LAPIC (acpi_id[0x10] lapic_id[0x20] enabled)
> Processor #32
> ACPI: LAPIC (acpi_id[0x11] lapic_id[0x21] enabled)
> Processor #33
> ACPI: LAPIC (acpi_id[0x12] lapic_id[0x26] enabled)
> Processor #38
> ACPI: LAPIC (acpi_id[0x13] lapic_id[0x27] enabled)
> Processor #39
> ACPI: LAPIC (acpi_id[0x14] lapic_id[0x30] enabled)
> Processor #48
> ACPI: LAPIC (acpi_id[0x15] lapic_id[0x31] enabled)
> Processor #49
> ACPI: LAPIC (acpi_id[0x16] lapic_id[0x36] enabled)
> Processor #54
> ACPI: LAPIC (acpi_id[0x17] lapic_id[0x37] enabled)
> Processor #55
> ACPI: LAPIC (acpi_id[0x20] lapic_id[0x40] enabled)
> Processor #64
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x21] lapic_id[0x41] enabled)
> Processor #65
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x22] lapic_id[0x46] enabled)
> Processor #70
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x23] lapic_id[0x47] enabled)
> Processor #71
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x24] lapic_id[0x50] enabled)
> Processor #80
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x25] lapic_id[0x51] enabled)
> Processor #81
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x26] lapic_id[0x56] enabled)
> Processor #86
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x27] lapic_id[0x57] enabled)
> Processor #87
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x30] lapic_id[0x60] enabled)
> Processor #96
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x31] lapic_id[0x61] enabled)
> Processor #97
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x32] lapic_id[0x66] enabled)
> Processor #102
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x33] lapic_id[0x67] enabled)
> Processor #103
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x34] lapic_id[0x70] enabled)
> Processor #112
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x35] lapic_id[0x71] enabled)
> Processor #113
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x36] lapic_id[0x76] enabled)
> Processor #118
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC (acpi_id[0x37] lapic_id[0x77] enabled)
> Processor #119
> WARNING: NR_CPUS limit of 16 reached. Processor ignored.
> ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x10] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x11] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x12] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x13] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x14] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x15] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x16] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x17] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x20] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x21] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x22] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x23] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x24] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x25] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x26] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x27] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x30] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x31] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x32] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x33] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x34] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x35] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x36] dfl dfl lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x37] dfl dfl lint[0x1])
> ACPI: IOAPIC (id[0x0f] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: apic_id 15, address 0xfec00000, GSI 0-35
> ACPI: IOAPIC (id[0x0e] address[0xfec01000] gsi_base[36])
> IOAPIC[1]: apic_id 14, address 0xfec01000, GSI 36-71
> ACPI: IOAPIC (id[0x0d] address[0xfec02000] gsi_base[72])
> IOAPIC[2]: apic_id 13, address 0xfec02000, GSI 72-107
> ACPI: IOAPIC (id[0x0c] address[0xfec03000] gsi_base[108])
> IOAPIC[3]: apic_id 12, address 0xfec03000, GSI 108-143
> ACPI: IOAPIC (id[0x0b] address[0xfec04000] gsi_base[144])
> IOAPIC[4]: apic_id 11, address 0xfec04000, GSI 144-179
> ACPI: IOAPIC (id[0x0a] address[0xfec05000] gsi_base[180])
> IOAPIC[5]: apic_id 10, address 0xfec05000, GSI 180-215
> ACPI: IOAPIC (id[0x09] address[0xfec06000] gsi_base[216])
> IOAPIC[6]: apic_id 9, address 0xfec06000, GSI 216-251
> ACPI: IOAPIC (id[0x08] address[0xfec07000] gsi_base[252])
> IOAPIC[7]: apic_id 8, address 0xfec07000, GSI 252-287
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 8 global_irq 8 low edge)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 low edge)
> Setting APIC routing to clustered
> ACPI: HPET id: 0x10142201 base: 0xfde84000
> afinfo corrupted at arch/x86_64/kernel/setup.c:559
> afinfo corrupted at arch/x86_64/kernel/setup.c:562
> Using ACPI (MADT) for SMP configuration information
> afinfo corrupted at arch/x86_64/kernel/setup.c:569
> afinfo corrupted at arch/x86_64/kernel/setup.c:572
> afinfo corrupted at arch/x86_64/kernel/setup.c:579
> afinfo corrupted at arch/x86_64/kernel/setup.c:582
> Nosave address range: 000000000009a000 - 000000000009b000
> Nosave address range: 000000000009b000 - 00000000000a0000
> Nosave address range: 00000000000a0000 - 00000000000e0000
> Nosave address range: 00000000000e0000 - 0000000000100000
> Nosave address range: 00000000bff76000 - 00000000bff77000
> Nosave address range: 00000000bff77000 - 00000000bff98000
> Nosave address range: 00000000bff98000 - 00000000bff99000
> Nosave address range: 00000000bff99000 - 00000000c0000000
> Nosave address range: 00000000c0000000 - 00000000fec00000
> Nosave address range: 00000000fec00000 - 0000000100000000
> afinfo corrupted at arch/x86_64/kernel/setup.c:585
> afinfo corrupted at arch/x86_64/kernel/setup.c:588
> afinfo corrupted at arch/x86_64/kernel/setup.c:596
> Allocating PCI resources starting at c4000000 (gap: c0000000:3ec00000)
> afinfo corrupted at arch/x86_64/kernel/setup.c:599
> afinfo corrupted at init/main.c:512
> SMP: Allowing 16 CPUs, 0 hotplug CPUs
> PERCPU: Allocating 33920 bytes of per cpu data
> afinfo corrupted at init/main.c:527
> Built 1 zonelists.  Total pages: 12147064
> Kernel command line: root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:1160100417
> afinfo corrupted at init/main.c:536
> Initializing CPU#0
> PID hash table entries: 4096 (order: 12, 32768 bytes)
> afinfo corrupted at init/main.c:545
> afinfo corrupted at init/main.c:548
> disabling early console
> Console: colour VGA+ 80x25
> Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes)
> Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes)
> afinfo corrupted at init/main.c:582
> Checking aperture...
> PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
> Placing software IO TLB between 0x310c2000 - 0x350c2000
> Memory: 48422908k/50331648k available (2566k kernel code, 858868k reserved, 1345k data, 184k init)
> afinfo corrupted at init/main.c:584
> Calibrating delay using timer specific routine.. 5678.09 BogoMIPS (lpj=11356196)
> afinfo corrupted at init/main.c:593
> afinfo corrupted at init/main.c:603
> Mount-cache hash table entries: 256
> afinfo corrupted at init/main.c:610
> afinfo corrupted at init/main.c:618
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> using mwait in idle threads.
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> CPU0: Thermal monitoring enabled (TM1)
> SMP alternatives: switching to UP code
> ACPI: Core revision 20060707
> ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> Using local APIC timer interrupts.
> result 10425595
> Detected 10.425 MHz APIC timer.
> afinfo corrupted at init/main.c:749
> SMP alternatives: switching to SMP code
> Booting processor 1/16 APIC 0x1
> Initializing CPU#1
> Calibrating delay using timer specific routine.. 5671.84 BogoMIPS (lpj=11343696)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 0
> CPU1: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 1: Syncing TSC to CPU 0.
> CPU 1: synchronized TSC with CPU 0 (last diff -2 cycles, maxerr 799 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 2/16 APIC 0x6
> Initializing CPU#2
> Calibrating delay using timer specific routine.. 5671.98 BogoMIPS (lpj=11343971)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 3
> CPU: Processor Core ID: 0
> CPU2: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 2: Syncing TSC to CPU 0.
> CPU 2: synchronized TSC with CPU 0 (last diff -184 cycles, maxerr 3349 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 3/16 APIC 0x7
> Initializing CPU#3
> Calibrating delay using timer specific routine.. 5672.02 BogoMIPS (lpj=11344041)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 3
> CPU: Processor Core ID: 0
> CPU3: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 3: Syncing TSC to CPU 0.
> CPU 3: synchronized TSC with CPU 0 (last diff -100 cycles, maxerr 1989 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 4/16 APIC 0x10
> Initializing CPU#4
> Calibrating delay using timer specific routine.. 5672.07 BogoMIPS (lpj=11344144)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 8
> CPU: Processor Core ID: 0
> CPU4: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 4: Syncing TSC to CPU 0.
> CPU 4: synchronized TSC with CPU 0 (last diff 43 cycles, maxerr 3247 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 5/16 APIC 0x11
> Initializing CPU#5
> Calibrating delay using timer specific routine.. 5672.01 BogoMIPS (lpj=11344024)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 8
> CPU: Processor Core ID: 0
> CPU5: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 5: Syncing TSC to CPU 0.
> CPU 5: synchronized TSC with CPU 0 (last diff 21 cycles, maxerr 3349 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 6/16 APIC 0x16
> Initializing CPU#6
> Calibrating delay using timer specific routine.. 5672.02 BogoMIPS (lpj=11344042)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 11
> CPU: Processor Core ID: 0
> CPU6: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 6: Syncing TSC to CPU 0.
> CPU 6: synchronized TSC with CPU 0 (last diff 257 cycles, maxerr 3383 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 7/16 APIC 0x17
> Initializing CPU#7
> Calibrating delay using timer specific routine.. 5672.10 BogoMIPS (lpj=11344218)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 11
> CPU: Processor Core ID: 0
> CPU7: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 7: Syncing TSC to CPU 0.
> CPU 7: synchronized TSC with CPU 0 (last diff 233 cycles, maxerr 3357 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 8/16 APIC 0x20
> Initializing CPU#8
> Calibrating delay using timer specific routine.. 5672.35 BogoMIPS (lpj=11344712)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 16
> CPU: Processor Core ID: 0
> CPU8: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 8: Syncing TSC to CPU 0.
> CPU 8: synchronized TSC with CPU 0 (last diff 140 cycles, maxerr 8509 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 9/16 APIC 0x21
> Initializing CPU#9
> Calibrating delay using timer specific routine.. 5672.25 BogoMIPS (lpj=11344515)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 16
> CPU: Processor Core ID: 0
> CPU9: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 9: Syncing TSC to CPU 0.
> CPU 9: synchronized TSC with CPU 0 (last diff -100 cycles, maxerr 7556 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 10/16 APIC 0x26
> Initializing CPU#10
> Calibrating delay using timer specific routine.. 5672.33 BogoMIPS (lpj=11344676)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 19
> CPU: Processor Core ID: 0
> CPU10: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 10: Syncing TSC to CPU 0.
> CPU 10: synchronized TSC with CPU 0 (last diff 405 cycles, maxerr 8126 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 11/16 APIC 0x27
> Initializing CPU#11
> Calibrating delay using timer specific routine.. 5672.46 BogoMIPS (lpj=11344939)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 19
> CPU: Processor Core ID: 0
> CPU11: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 11: Syncing TSC to CPU 0.
> CPU 11: synchronized TSC with CPU 0 (last diff -145 cycles, maxerr 8568 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 12/16 APIC 0x30
> Initializing CPU#12
> Calibrating delay using timer specific routine.. 5672.23 BogoMIPS (lpj=11344472)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 24
> CPU: Processor Core ID: 0
> CPU12: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 12: Syncing TSC to CPU 0.
> CPU 12: synchronized TSC with CPU 0 (last diff 419 cycles, maxerr 8602 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 13/16 APIC 0x31
> Initializing CPU#13
> Calibrating delay using timer specific routine.. 5672.34 BogoMIPS (lpj=11344689)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 24
> CPU: Processor Core ID: 0
> CPU13: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 13: Syncing TSC to CPU 0.
> CPU 13: synchronized TSC with CPU 0 (last diff 242 cycles, maxerr 8636 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 14/16 APIC 0x36
> Initializing CPU#14
> Calibrating delay using timer specific routine.. 5672.32 BogoMIPS (lpj=11344644)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 27
> CPU: Processor Core ID: 0
> CPU14: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 14: Syncing TSC to CPU 0.
> CPU 14: synchronized TSC with CPU 0 (last diff -272 cycles, maxerr 8109 cycles)
> SMP alternatives: switching to SMP code
> Booting processor 15/16 APIC 0x37
> Initializing CPU#15
> Calibrating delay using timer specific routine.. 5672.21 BogoMIPS (lpj=11344423)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: L3 cache: 4096K
> CPU: Physical Processor ID: 27
> CPU: Processor Core ID: 0
> CPU15: Thermal monitoring enabled (TM1)
>                Intel(R) Xeon(TM) MP CPU 2.83GHz stepping 01
> CPU 15: Syncing TSC to CPU 0.
> CPU 15: synchronized TSC with CPU 0 (last diff -21 cycles, maxerr 8560 cycles)
> Brought up 16 CPUs
> testing NMI watchdog ... OK.
> time.c: Using 333.333333 MHz WALL PIT GTOD PIT/HPET timer.
> time.c: Detected 2835.773 MHz processor.
> afinfo corrupted at init/main.c:755
> migration_cost=19,988
> afinfo corrupted at init/main.c:761
> afinfo corrupted at init/main.c:769
> Calling initcall 0xffffffff802166c0: init_smp_flush+0x0/0x60()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607a40: helper_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607dd0: pm_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607e50: ksysfs_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060a720: filelock_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060b230: init_script_binfmt+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060b240: init_elf_binfmt+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80614690: sock_init+0x0/0x60()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80614e30: netlink_proto_init+0x0/0x1a0()
> afinfo corrupted at init/main.c:659
> NET: Registered protocol family 16
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060c310: kobject_uevent_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060c4a0: pcibus_class_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060ca70: pci_driver_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060ef30: tty_class_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060fa20: vtconsole_class_init+0x0/0xc0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060cbb0: acpi_pci_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> ACPI: bus type pci registered
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060d8ef: init_acpi_device_notify+0x0/0x4b()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80613aa0: pci_access_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> PCI: Using configuration type 1
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80605760: topology_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607770: param_sysfs_init+0x0/0x200()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80249d00: pm_sysrq_init+0x0/0x20()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060aee0: init_bio+0x0/0x110()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060c1d0: genhd_device_init+0x0/0x60()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060d702: acpi_init+0x0/0x1ed()
> afinfo corrupted at init/main.c:659
> ACPI: Interpreter enabled
> ACPI: Using IOAPIC for interrupt routing
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060dbd5: acpi_ec_init+0x0/0x62()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060dfee: acpi_pci_root_init+0x0/0x28()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060e036: acpi_pci_link_init+0x0/0x48()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060e1bc: acpi_power_init+0x0/0x77()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060e233: acpi_system_init+0x0/0xc6()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060e2f9: acpi_event_init+0x0/0x3f()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060e338: acpi_scan_init+0x0/0x1ac()
> afinfo corrupted at init/main.c:659
> ACPI: PCI Root Bridge [VP00] (0000:00)
> PCI: Ignoring BAR0-3 of IDE controller 0000:00:0f.1
> ACPI: PCI Root Bridge [VP01] (0000:01)
> ACPI: PCI Root Bridge [VP02] (0000:02)
> ACPI: PCI Root Bridge [VP03] (0000:04)
> ACPI: PCI Root Bridge [VP04] (0000:06)
> ACPI: PCI Root Bridge [VP05] (0000:08)
> ACPI: PCI Root Bridge [VP06] (0000:0a)
> ACPI: PCI Root Bridge [VP07] (0000:0c)
> ACPI: PCI Root Bridge [VP10] (0000:0e)
> ACPI: PCI Root Bridge [VP11] (0000:0f)
> ACPI: PCI Root Bridge [VP12] (0000:10)
> ACPI: PCI Root Bridge [VP13] (0000:12)
> ACPI: PCI Root Bridge [VP14] (0000:14)
> ACPI: PCI Root Bridge [VP15] (0000:16)
> ACPI: PCI Root Bridge [VP16] (0000:18)
> ACPI: PCI Root Bridge [VP17] (0000:1a)
> ACPI: PCI Root Bridge [VP20] (0000:1c)
> ACPI: PCI Root Bridge [VP21] (0000:1d)
> ACPI: PCI Root Bridge [VP22] (0000:1e)
> ACPI: PCI Root Bridge [VP23] (0000:20)
> ACPI: PCI Root Bridge [VP24] (0000:22)
> ACPI: PCI Root Bridge [VP25] (0000:24)
> ACPI: PCI Root Bridge [VP26] (0000:26)
> ACPI: PCI Root Bridge [VP27] (0000:28)
> ACPI: PCI Root Bridge [VP30] (0000:2a)
> ACPI: PCI Root Bridge [VP31] (0000:2b)
> ACPI: PCI Root Bridge [VP32] (0000:2c)
> ACPI: PCI Root Bridge [VP33] (0000:2e)
> ACPI: PCI Root Bridge [VP34] (0000:30)
> ACPI: PCI Root Bridge [VP35] (0000:32)
> ACPI: PCI Root Bridge [VP36] (0000:34)
> ACPI: PCI Root Bridge [VP37] (0000:36)
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060e654: acpi_cm_sbs_init+0x0/0xc()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060e660: pnp_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> Linux Plug and Play Support v0.97 (c) Adam Belay
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060e8f0: pnpacpi_init+0x0/0x70()
> afinfo corrupted at init/main.c:659
> pnp: PnP ACPI init
> pnp: PnP ACPI: found 47 devices
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060f490: misc_init+0x0/0x90()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80375670: cn_init+0x0/0xe0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806117f0: init_scsi+0x0/0x90()
> afinfo corrupted at init/main.c:659
> SCSI subsystem initialized
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806124d0: serio_init+0x0/0xd0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806128f0: input_init+0x0/0x120()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80612d00: rtc_init+0x0/0x50()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80612d50: rtc_sysfs_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80612d60: rtc_proc_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80612d70: rtc_dev_init+0x0/0xb0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80613ad0: pci_acpi_init+0x0/0xb0()
> afinfo corrupted at init/main.c:659
> PCI: Using ACPI for IRQ routing
> PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80613b80: pci_legacy_init+0x0/0x120()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80614130: pcibios_irq_init+0x0/0x4f0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80614620: pcibios_init+0x0/0x70()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80614750: proto_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806148f0: net_dev_init+0x0/0x210()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80614fd0: genl_init+0x0/0xb0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff805fdfc0: late_hpet_init+0x0/0xb0()
> afinfo corrupted at init/main.c:659
> hpet0: at MMIO 0xfde84000, IRQs 2, 8, 0
> hpet0: 3 64-bit timers, 3707069 Hz
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806000b0: pci_iommu_init+0x0/0x20()
> afinfo corrupted at init/main.c:659
> PCI-GART: No AMD northbridge found.
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060a6a0: init_pipe_fs+0x0/0x50()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060e524: acpi_motherboard_init+0x0/0x130()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060e790: pnp_system_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> pnp: 00:0a: ioport range 0x400-0x47f has been reserved
> pnp: 00:0a: ioport range 0x480-0x4ff could not be reserved
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060ec70: chr_dev_init+0x0/0x80()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80610a40: firmware_class_init+0x0/0x80()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806134b0: pcibios_assign_resources+0x0/0x90()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806159e0: inet_init+0x0/0x400()
> afinfo corrupted at init/main.c:659
> NET: Registered protocol family 2
> IP route cache hash table entries: 524288 (order: 10, 4194304 bytes)
> TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
> TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
> TCP: Hash tables configured (established 262144 bind 65536)
> TCP reno registered
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8020db10: time_init_device+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff805fe9f0: i8259A_init_sysfs+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff805fe9c0: init_timer_sysfs+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff805ff010: vsyscall_init+0x0/0xb0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff805ff2a0: sbf_init+0x0/0xe0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80600080: i8237A_init_sysfs+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80600500: periodic_mcheck_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80600530: mce_init_device+0x0/0x80()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80600670: thermal_throttle_init_device+0x0/0x70()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806006e0: threshold_init_device+0x0/0x50()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80601ee0: init_lapic_sysfs+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80602a80: ioapic_init_sysfs+0x0/0xf0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8021d1f0: cache_sysfs_init+0x0/0x60()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80605870: x8664_sysctl_init+0x0/0x20()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80606d30: create_proc_profile+0x0/0x280()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607170: ioresources_init+0x0/0x50()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806072e0: timekeeping_init_device+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607400: uid_cache_init+0x0/0x90()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607970: init_posix_timers+0x0/0xd0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607a80: init_posix_cpu_timers+0x0/0xf0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607ba0: latency_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607c90: init_clocksource_sysfs+0x0/0x60()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607cf0: init_jiffies_clocksource+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607d00: init+0x0/0x70()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607d70: proc_dma_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80245840: percpu_modinit+0x0/0x80()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607da0: kallsyms_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80607e10: ikconfig_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80608f60: init_per_zone_pages_min+0x0/0x60()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80609ed0: pdflush_init+0x0/0x20()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80609f20: kswapd_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80609f50: setup_vmstat+0x0/0x20()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80609fc0: procswaps_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060a030: hugetlb_init+0x0/0x70()
> afinfo corrupted at init/main.c:659
> Total HugeTLB memory allocated, 0
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060a0a0: init_tmpfs+0x0/0xe0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060a180: cpucache_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060a6f0: fasync_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060ae00: aio_setup+0x0/0x70()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060b080: inotify_setup+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060b090: inotify_user_setup+0x0/0xc0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060b150: eventpoll_init+0x0/0xe0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060b250: init_mbcache+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060b280: dnotify_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060b740: init_devpts_fs+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060b780: init_reiserfs_fs+0x0/0x80()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060b800: init_ext3_fs+0x0/0x70()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060b930: journal_init+0x0/0xe0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060ba10: init_ext2_fs+0x0/0x70()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060bad0: init_ramfs_fs+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060bae0: init_hugetlbfs_fs+0x0/0x80()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060bba0: init_fat_fs+0x0/0x50()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060bbf0: init_vfat_fs+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060bc00: init_nls_cp437+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060bc10: init_nls_iso8859_1+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060bc20: init_autofs_fs+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060bc30: init_autofs4_fs+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> initcall at 0xffffffff8060bc30: init_autofs4_fs+0x0/0x10(): returned with error code -16
> Calling initcall 0xffffffff8060bc40: ipc_init+0x0/0x20()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060bf10: init_mqueue_fs+0x0/0xe0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060bff0: crypto_algapi_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060c030: init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060c040: init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060c230: noop_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> io scheduler noop registered
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060c240: as_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> io scheduler anticipatory registered (default)
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060c250: deadline_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> io scheduler deadline registered
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060c260: cfq_init+0x0/0xb0()
> afinfo corrupted at init/main.c:659
> io scheduler cfq registered
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8032c1d0: pci_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060ca80: pci_sysfs_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060cac0: pci_proc_init+0x0/0x70()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060d93a: acpi_ac_init+0x0/0x45()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060d97f: acpi_battery_init+0x0/0x45()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060df90: acpi_video_init+0x0/0x5e()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060e07e: irqrouter_init_sysfs+0x0/0x38()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060ed10: rand_initialize+0x0/0x30()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060ed40: tty_init+0x0/0x1f0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060efa0: pty_init+0x0/0x4f0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060fae0: hpet_init+0x0/0x70()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060fb50: agp_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> Linux agpgart interface v0.101 (c) Dave Jones
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff8060fcb0: cn_proc_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806100f0: serial8250_init+0x0/0x150()
> afinfo corrupted at init/main.c:659
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
> serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80610320: serial8250_pnp_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> 00:03: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> 00:04: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80610330: serial8250_pci_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80384c90: topology_sysfs_init+0x0/0x50()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80610ac0: e1000_init_module+0x0/0x50()
> afinfo corrupted at init/main.c:659
> Intel(R) PRO/1000 Network Driver - version 7.2.9-k2
> Copyright (c) 1999-2006 Intel Corporation.
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80610b10: tg3_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> tg3.c:v3.66 (September 23, 2006)
> ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 24 (level, low) -> IRQ 24
> eth0: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:60:98:63:54
> eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
> eth0: dma_rwctrl[769f0000] dma_mask[64-bit]
> ACPI: PCI Interrupt 0000:01:01.1[B] -> GSI 28 (level, low) -> IRQ 28
> eth1: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:0d:60:98:63:55
> eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
> eth1: dma_rwctrl[769f0000] dma_mask[64-bit]
> ACPI: PCI Interrupt 0000:0f:01.0[A] -> GSI 96 (level, low) -> IRQ 96
> eth2: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:1c:45:0c
> eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
> eth2: dma_rwctrl[769f0000] dma_mask[64-bit]
> ACPI: PCI Interrupt 0000:0f:01.1[B] -> GSI 100 (level, low) -> IRQ 100
> eth3: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:1c:45:0d
> eth3: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
> eth3: dma_rwctrl[769f0000] dma_mask[64-bit]
> ACPI: PCI Interrupt 0000:1d:01.0[A] -> GSI 168 (level, low) -> IRQ 168
> eth4: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:1c:45:6c
> eth4: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
> eth4: dma_rwctrl[769f0000] dma_mask[64-bit]
> ACPI: PCI Interrupt 0000:1d:01.1[B] -> GSI 172 (level, low) -> IRQ 172
> eth5: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:1c:45:6d
> eth5: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
> eth5: dma_rwctrl[769f0000] dma_mask[64-bit]
> ACPI: PCI Interrupt 0000:2b:01.0[A] -> GSI 240 (level, low) -> IRQ 240
> eth6: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:1c:43:82
> eth6: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
> eth6: dma_rwctrl[769f0000] dma_mask[64-bit]
> ACPI: PCI Interrupt 0000:2b:01.1[B] -> GSI 244 (level, low) -> IRQ 244
> eth7: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:66MHz:64-bit) 10/100/1000BaseT Ethernet 00:14:5e:1c:43:83
> eth7: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
> eth7: dma_rwctrl[769f0000] dma_mask[64-bit]
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80610ba0: net_olddevs_init+0x0/0xc0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff803a8630: init_netconsole+0x0/0x80()
> afinfo corrupted at init/main.c:659
> netconsole: not configured, aborting
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff803a8710: cmd64x_ide_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80610c70: piix_ide_init+0x0/0xd0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff803aa810: svwks_ide_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff803ab480: generic_ide_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80610db0: ide_init+0x0/0x90()
> afinfo corrupted at init/main.c:659
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> SvrWks CSB6: IDE controller at PCI slot 0000:00:0f.1
> SvrWks CSB6: chipset revision 160
> SvrWks CSB6: not 100% native mode: will probe irqs later
>     ide0: BM-DMA at 0x0700-0x0707, BIOS settings: hda:DMA, hdb:DMA
> SvrWks CSB6: simplex device: DMA disabled
> ide1: SvrWks CSB6 Bus-Master DMA disabled (BIOS)
> hda: MATSHITADVD-ROM SR-8178, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80611780: ide_generic_init+0x0/0x20()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806117a0: idedisk_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806117b0: ide_cdrom_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> hda: ATAPI 24X DVD-ROM drive, 256kB Cache, UDMA(66)
> Uniform CD-ROM driver Revision: 3.20
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806117c0: idefloppy_init+0x0/0x30()
> afinfo corrupted at init/main.c:659
> ide-floppy driver 0.99.newide
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80611a90: raid_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80611aa0: spi_transport_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80611ae0: fc_transport_init+0x0/0x50()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80611b30: iscsi_transport_init+0x0/0x120()
> afinfo corrupted at init/main.c:659
> Loading iSCSI transport class v2.0-685.afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80611c50: sas_transport_init+0x0/0xc0()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80611d10: iscsi_tcp_init+0x0/0x50()
> afinfo corrupted at init/main.c:659
> iscsi: registered transport (tcp)
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80611d60: aac_init+0x0/0x70()
> afinfo corrupted at init/main.c:659
> Adaptec aacraid driver (1.1-5[2409]-mh2)
> ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 25 (level, low) -> IRQ 25
> AAC0: kernel 5.0-2[8264]
> AAC0: monitor 5.0-2[8264]
> AAC0: bios 5.0-2[8264]
> AAC0: serial 162348
> AAC0: 64bit support enabled.
> AAC0: 64 Bit DAC enabled
> scsi0 : ServeRAID
> scsi 0:0:0:0: Direct-Access     IBM      Drive 1          V1.0 PQ: 0 ANSI: 2
> scsi 0:0:1:0: Direct-Access     IBM      Drive 2          V1.0 PQ: 0 ANSI: 2
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80611dd0: qla1280_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80611fa0: sym2_init+0x0/0x110()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806120b0: init_sd+0x0/0x60()
> afinfo corrupted at init/main.c:659
> SCSI device sda: 143132672 512-byte hdwr sectors (73284 MB)
> sda: assuming Write Enabled
> sda: assuming drive cache: write through
> SCSI device sda: 143132672 512-byte hdwr sectors (73284 MB)
> sda: assuming Write Enabled
> sda: assuming drive cache: write through
>  sda: sda1 sda2 sda3
> sd 0:0:0:0: Attached scsi removable disk sda
> SCSI device sdb: 143132672 512-byte hdwr sectors (73284 MB)
> sdb: assuming Write Enabled
> sdb: assuming drive cache: write through
> SCSI device sdb: 143132672 512-byte hdwr sectors (73284 MB)
> sdb: assuming Write Enabled
> sdb: assuming drive cache: write through
>  sdb: sdb1 sdb2 sdb3
> sd 0:0:1:0: Attached scsi removable disk sdb
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80612110: fusion_init+0x0/0x100()
> afinfo corrupted at init/main.c:659
> Fusion MPT base driver 3.04.01
> Copyright (c) 1999-2005 LSI Logic Corporation
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80612210: mptspi_init+0x0/0xc0()
> afinfo corrupted at init/main.c:659
> Fusion MPT SPI Host driver 3.04.01
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806122d0: mptfc_init+0x0/0xf0()
> afinfo corrupted at init/main.c:659
> Fusion MPT FC Host driver 3.04.01
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806123c0: mptctl_init+0x0/0x100()
> afinfo corrupted at init/main.c:659
> Fusion MPT misc device (ioctl) driver 3.04.01
> mptctl: Registered with Fusion MPT base driver
> mptctl: /dev/mptctl @ (major,minor=10,220)
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806124c0: cdrom_init+0x0/0x10()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806125a0: i8042_init+0x0/0x350()
> afinfo corrupted at init/main.c:659
> PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
> serio: i8042 KBD port at 0x60,0x64 irq 1
> serio: i8042 AUX port at 0x60,0x64 irq 12
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80612a10: mousedev_init+0x0/0x100()
> afinfo corrupted at init/main.c:659
> mice: PS/2 mouse device common for all mice
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80612b10: atkbd_init+0x0/0x20()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80612e20: hwmon_init+0x0/0x40()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80614c60: flow_cache_init+0x0/0x1d0()
> afinfo corrupted at init/main.c:659
> input: AT Translated Set 2 keyboard as /class/input/input0
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff806160f0: init_syncookies+0x0/0x20()
> afinfo corrupted at init/main.c:659
> afinfo corrupted at init/main.c:663
> Calling initcall 0xffffffff80616110: xfrm4_beet_init+0x0/0x20()
> afinfo corrupted at init/main.c:659
> Unable to handle kernel NULL pointer dereference at 0000000000000827 RIP:
>  [<ffffffff80470666>] xfrm_register_mode+0x36/0x60
> PGD 0
> Oops: 0000 [1] SMP
> CPU 0
> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.18-git22 #2
> RIP: 0010:[<ffffffff80470666>]  [<ffffffff80470666>] xfrm_register_mode+0x36/0x60
> RSP: 0000:ffff810bffcbded0  EFLAGS: 00010286
> RAX: 000000000000081f RBX: ffffffff805588a0 RCX: 0000000000100000
> RDX: ffffffffffffffff RSI: 0000000000000002 RDI: ffffffff80559550
> RBP: 00000000ffffffef R08: 0000000000000002 R09: fffffffffffffffd
> R10: 0000000000000002 R11: 0000000000000000 R12: 0000000000000000
> R13: ffff810bffcbdef0 R14: 0000000000000000 R15: 0000000000000000
> FS:  0000000000000000(0000) GS:ffffffff805d2000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> CR2: 0000000000000827 CR3: 0000000000201000 CR4: 00000000000006e0
> Process swapper (pid: 1, threadinfo ffff810bffcbc000, task ffff810bffcbb4e0)
> Stack:  0000000000000000 0000000000000000 ffffffff8061fee8 ffffffff802071d6
>  6f6320726f727265 000036312d206564 0000000000000000 0000000000000000
>  0000000000000000 0000000000000000 0000000000000000 0000000000090000
> Call Trace:
>  [<ffffffff802071d6>] init+0x1b6/0x3b0
>  [<ffffffff8020aa28>] child_rip+0xa/0x12
>  [<ffffffff80339542>] acpi_ds_init_one_object+0x0/0x82
>  [<ffffffff80207020>] init+0x0/0x3b0
>  [<ffffffff8020aa1e>] child_rip+0x0/0x12
> 
> 
> Code: 48 83 78 08 00 75 06 48 89 58 08 31 ed 48 89 d7 e8 e5 fe ff
> RIP  [<ffffffff80470666>] xfrm_register_mode+0x36/0x60
>  RSP <ffff810bffcbded0>
> CR2: 0000000000000827
>  <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
> 
> 
> -- 
> 
> Steve Fox
> IBM Linux Technology Center
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

Re: 2.6.18-mm2 boot failure on x86-64

[Vivek Goyal]

On Fri, Oct 06, 2006 at 03:33:12PM +0100, Mel Gorman wrote:
> > Linux version 2.6.18-git22 (root@elm3b239) (gcc version 4.1.0 (SUSE Linux)) #2 SMP Thu Oct 5 19:05:36 PDT 2006
> > Command line: root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:1160100417
> > BIOS-provided physical RAM map:
> >  BIOS-e820: 0000000000000000 - 000000000009ac00 (usable)
> >  BIOS-e820: 000000000009ac00 - 00000000000a0000 (reserved)
> >  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
> >  BIOS-e820: 0000000000100000 - 00000000bff764c0 (usable)
> >  BIOS-e820: 00000000bff764c0 - 00000000bff98880 (ACPI data)
> >  BIOS-e820: 00000000bff98880 - 00000000c0000000 (reserved)
> >  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
> >  BIOS-e820: 0000000100000000 - 0000000c00000000 (usable)
> 
> I continued what Steve was doing this morning to see could this be
> pinned down. After placing 'CHECK;' in a few places as suggested by
> Andi's check, the problem code was identified as that following in
> mm/bootmem.c#init_bootmem_core()
> 
>         mapsize = get_mapsize(bdata);
>         memset(bdata->node_bootmem_map, 0xff, mapsize);
> 
> That explains the value in the array at least. A few more printfs around
> this point printed out the following in the boot log
> 
> init_bootmem_core(0, 1909, 0, 12582912)
> init_bootmem_core: Calling memset(0xFFFF810000775000, 1572864)
> AAGH: afinfo corrupted at mm/bootmem.c:121
> 
> where;
> 
> 1909 == mapstart
> 0 == start
> 12582912 == end
> 1572864 == mapsize
> 
> mapstart, start and end being the parameters being passed to
> init_bootmem_core(). This means we are calling memset for the physical
> range 0x775000 -> 0x8F5000 which is in a usable range according to the
> BIOS-e820 map it appears.
> 

Hi Mel,

Where is bss placed in physical memory? I guess bss_start and bss_stop
from System.map will tell us. That will confirm that above memset step is
stomping over bss. Then we have to just find that somewhere probably
we allocated wrong physical memory area for bootmem allocator map.

Thanks
Vivek

Re: 2.6.18-mm2 boot failure on x86-64

[Mel Gorman]

On (06/10/06 11:36), Vivek Goyal didst pronounce:
> On Fri, Oct 06, 2006 at 03:33:12PM +0100, Mel Gorman wrote:
> > > Linux version 2.6.18-git22 (root@elm3b239) (gcc version 4.1.0 (SUSE Linux)) #2 SMP Thu Oct 5 19:05:36 PDT 2006
> > > Command line: root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:1160100417
> > > BIOS-provided physical RAM map:
> > >  BIOS-e820: 0000000000000000 - 000000000009ac00 (usable)
> > >  BIOS-e820: 000000000009ac00 - 00000000000a0000 (reserved)
> > >  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
> > >  BIOS-e820: 0000000000100000 - 00000000bff764c0 (usable)
> > >  BIOS-e820: 00000000bff764c0 - 00000000bff98880 (ACPI data)
> > >  BIOS-e820: 00000000bff98880 - 00000000c0000000 (reserved)
> > >  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
> > >  BIOS-e820: 0000000100000000 - 0000000c00000000 (usable)
> > 
> > I continued what Steve was doing this morning to see could this be
> > pinned down. After placing 'CHECK;' in a few places as suggested by
> > Andi's check, the problem code was identified as that following in
> > mm/bootmem.c#init_bootmem_core()
> > 
> >         mapsize = get_mapsize(bdata);
> >         memset(bdata->node_bootmem_map, 0xff, mapsize);
> > 
> > That explains the value in the array at least. A few more printfs around
> > this point printed out the following in the boot log
> > 
> > init_bootmem_core(0, 1909, 0, 12582912)
> > init_bootmem_core: Calling memset(0xFFFF810000775000, 1572864)
> > AAGH: afinfo corrupted at mm/bootmem.c:121
> > 
> > where;
> > 
> > 1909 == mapstart
> > 0 == start
> > 12582912 == end
> > 1572864 == mapsize
> > 
> > mapstart, start and end being the parameters being passed to
> > init_bootmem_core(). This means we are calling memset for the physical
> > range 0x775000 -> 0x8F5000 which is in a usable range according to the
> > BIOS-e820 map it appears.
> > 
> 
> Hi Mel,
> 

Hi.

> Where is bss placed in physical memory? I guess bss_start and bss_stop
> from System.map will tell us. That will confirm that above memset step is
> stomping over bss. Then we have to just find that somewhere probably
> we allocated wrong physical memory area for bootmem allocator map.
> 

BSS is at 0x643000 -> 0x777BC4
init_bootmem wipes from 0x777000 -> 0x8F7000

So the BSS bytes from 0x777000 ->0x777BC4 (which looks very suspiciously
pile a page alignment of addr & PAGE_MASK) gets set to 0xFF. One possible
fix is below. It adds a check in bad_addr() to see if the BSS section is
about to be used for bootmap. It Seems To Work For Me (tm) and illustrates
the source of the problem even if it's not the 100% correct fix.

diff -rup -X /usr/src/patchset-0.6/bin//dontdiff linux-2.6.18-git22-clean/arch/x86_64/kernel/e820.c linux-2.6.18-git22-bss_relocate_fix/arch/x86_64/kernel/e820.c
--- linux-2.6.18-git22-clean/arch/x86_64/kernel/e820.c	2006-10-05 20:42:07.000000000 +0100
+++ linux-2.6.18-git22-bss_relocate_fix/arch/x86_64/kernel/e820.c	2006-10-06 17:39:51.000000000 +0100
@@ -51,6 +51,7 @@ extern struct resource code_resource, da
 static inline int bad_addr(unsigned long *addrp, unsigned long size)
 { 
 	unsigned long addr = *addrp, last = addr + size; 
+	unsigned long bss_start, bss_end;
 
 	/* various gunk below that needed for SMP startup */
 	if (addr < 0x8000) { 
@@ -77,6 +78,14 @@ static inline int bad_addr(unsigned long
 		*addrp = __pa_symbol(&_end);
 		return 1;
 	}
+	
+	/* bss section */
+	bss_start = __pa_symbol(&__bss_start);
+	bss_end = PAGE_ALIGN(__pa_symbol(&__bss_stop));
+	if (addr >= bss_start && addr < bss_end) {
+		*addrp = bss_end;
+		return 1;
+	}
 
 	if (last >= ebda_addr && addr < ebda_addr + ebda_size) {
 		*addrp = ebda_addr + ebda_size;

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

Re: 2.6.18-mm2 boot failure on x86-64

[Vivek Goyal]

On Fri, Oct 06, 2006 at 06:11:05PM +0100, Mel Gorman wrote:
> On (06/10/06 11:36), Vivek Goyal didst pronounce:
> > On Fri, Oct 06, 2006 at 03:33:12PM +0100, Mel Gorman wrote:
> > > > Linux version 2.6.18-git22 (root@elm3b239) (gcc version 4.1.0 (SUSE Linux)) #2 SMP Thu Oct 5 19:05:36 PDT 2006
> > > > Command line: root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:1160100417
> > > > BIOS-provided physical RAM map:
> > > >  BIOS-e820: 0000000000000000 - 000000000009ac00 (usable)
> > > >  BIOS-e820: 000000000009ac00 - 00000000000a0000 (reserved)
> > > >  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
> > > >  BIOS-e820: 0000000000100000 - 00000000bff764c0 (usable)
> > > >  BIOS-e820: 00000000bff764c0 - 00000000bff98880 (ACPI data)
> > > >  BIOS-e820: 00000000bff98880 - 00000000c0000000 (reserved)
> > > >  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
> > > >  BIOS-e820: 0000000100000000 - 0000000c00000000 (usable)
> > > 
> > > I continued what Steve was doing this morning to see could this be
> > > pinned down. After placing 'CHECK;' in a few places as suggested by
> > > Andi's check, the problem code was identified as that following in
> > > mm/bootmem.c#init_bootmem_core()
> > > 
> > >         mapsize = get_mapsize(bdata);
> > >         memset(bdata->node_bootmem_map, 0xff, mapsize);
> > > 
> > > That explains the value in the array at least. A few more printfs around
> > > this point printed out the following in the boot log
> > > 
> > > init_bootmem_core(0, 1909, 0, 12582912)
> > > init_bootmem_core: Calling memset(0xFFFF810000775000, 1572864)
> > > AAGH: afinfo corrupted at mm/bootmem.c:121
> > > 
> > > where;
> > > 
> > > 1909 == mapstart
> > > 0 == start
> > > 12582912 == end
> > > 1572864 == mapsize
> > > 
> > > mapstart, start and end being the parameters being passed to
> > > init_bootmem_core(). This means we are calling memset for the physical
> > > range 0x775000 -> 0x8F5000 which is in a usable range according to the
> > > BIOS-e820 map it appears.
> > > 
> > 
> > Hi Mel,
> > 
> 
> Hi.
> 
> > Where is bss placed in physical memory? I guess bss_start and bss_stop
> > from System.map will tell us. That will confirm that above memset step is
> > stomping over bss. Then we have to just find that somewhere probably
> > we allocated wrong physical memory area for bootmem allocator map.
> > 
> 
> BSS is at 0x643000 -> 0x777BC4
> init_bootmem wipes from 0x777000 -> 0x8F7000
> 
> So the BSS bytes from 0x777000 ->0x777BC4 (which looks very suspiciously
> pile a page alignment of addr & PAGE_MASK) gets set to 0xFF. One possible
> fix is below. It adds a check in bad_addr() to see if the BSS section is
> about to be used for bootmap. It Seems To Work For Me (tm) and illustrates
> the source of the problem even if it's not the 100% correct fix.
> 
> diff -rup -X /usr/src/patchset-0.6/bin//dontdiff linux-2.6.18-git22-clean/arch/x86_64/kernel/e820.c linux-2.6.18-git22-bss_relocate_fix/arch/x86_64/kernel/e820.c
> --- linux-2.6.18-git22-clean/arch/x86_64/kernel/e820.c	2006-10-05 20:42:07.000000000 +0100
> +++ linux-2.6.18-git22-bss_relocate_fix/arch/x86_64/kernel/e820.c	2006-10-06 17:39:51.000000000 +0100
> @@ -51,6 +51,7 @@ extern struct resource code_resource, da
>  static inline int bad_addr(unsigned long *addrp, unsigned long size)
>  { 
>  	unsigned long addr = *addrp, last = addr + size; 
> +	unsigned long bss_start, bss_end;
>  
>  	/* various gunk below that needed for SMP startup */
>  	if (addr < 0x8000) { 
> @@ -77,6 +78,14 @@ static inline int bad_addr(unsigned long
>  		*addrp = __pa_symbol(&_end);
>  		return 1;
>  	}
> +	
> +	/* bss section */
> +	bss_start = __pa_symbol(&__bss_start);
> +	bss_end = PAGE_ALIGN(__pa_symbol(&__bss_stop));
> +	if (addr >= bss_start && addr < bss_end) {
> +		*addrp = bss_end;
> +		return 1;
> +	}
>  

Surprising, the kernel code check just before this should have taken care
of it.

 /* kernel code */
	if (last >= __pa_symbol(&_text) && last < __pa_symbol(&_end)) {
		*addrp = __pa_symbol(&_end);
		return 1;
	}
May be it can be changed to 
	if (last >= __pa_symbol(&_text) && last < PAGE_ALIGN(__pa_symbol(&_end))) {

But all this seem to be a stopgap fix. Still the real puzzle is exactly
where did it slip out and should be fixed there.

May be some more printks will help us.

Thanks
Vivek

Re: 2.6.18-mm2 boot failure on x86-64

[Vivek Goyal]

On Fri, Oct 06, 2006 at 06:11:05PM +0100, Mel Gorman wrote:
> On (06/10/06 11:36), Vivek Goyal didst pronounce:
> > On Fri, Oct 06, 2006 at 03:33:12PM +0100, Mel Gorman wrote:
> > > > Linux version 2.6.18-git22 (root@elm3b239) (gcc version 4.1.0 (SUSE Linux)) #2 SMP Thu Oct 5 19:05:36 PDT 2006
> > > > Command line: root=/dev/sda1 vga=791  ip=9.47.67.239:9.47.67.50:9.47.67.1:255.255.255.0 resume=/dev/sdb1 showopts earlyprintk=serial,ttyS0,57600 console=tty0 console=ttyS0,57600 autobench_args: root=/dev/sda1 ABAT:1160100417
> > > > BIOS-provided physical RAM map:
> > > >  BIOS-e820: 0000000000000000 - 000000000009ac00 (usable)
> > > >  BIOS-e820: 000000000009ac00 - 00000000000a0000 (reserved)
> > > >  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
> > > >  BIOS-e820: 0000000000100000 - 00000000bff764c0 (usable)
> > > >  BIOS-e820: 00000000bff764c0 - 00000000bff98880 (ACPI data)
> > > >  BIOS-e820: 00000000bff98880 - 00000000c0000000 (reserved)
> > > >  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
> > > >  BIOS-e820: 0000000100000000 - 0000000c00000000 (usable)
> > > 
> > > I continued what Steve was doing this morning to see could this be
> > > pinned down. After placing 'CHECK;' in a few places as suggested by
> > > Andi's check, the problem code was identified as that following in
> > > mm/bootmem.c#init_bootmem_core()
> > > 
> > >         mapsize = get_mapsize(bdata);
> > >         memset(bdata->node_bootmem_map, 0xff, mapsize);
> > > 
> > > That explains the value in the array at least. A few more printfs around
> > > this point printed out the following in the boot log
> > > 
> > > init_bootmem_core(0, 1909, 0, 12582912)
> > > init_bootmem_core: Calling memset(0xFFFF810000775000, 1572864)
> > > AAGH: afinfo corrupted at mm/bootmem.c:121
> > > 
> > > where;
> > > 
> > > 1909 == mapstart
> > > 0 == start
> > > 12582912 == end
> > > 1572864 == mapsize
> > > 
> > > mapstart, start and end being the parameters being passed to
> > > init_bootmem_core(). This means we are calling memset for the physical
> > > range 0x775000 -> 0x8F5000 which is in a usable range according to the
> > > BIOS-e820 map it appears.
> > > 
> > 
> > Hi Mel,
> > 
> 
> Hi.
> 
> > Where is bss placed in physical memory? I guess bss_start and bss_stop
> > from System.map will tell us. That will confirm that above memset step is
> > stomping over bss. Then we have to just find that somewhere probably
> > we allocated wrong physical memory area for bootmem allocator map.
> > 
> 
> BSS is at 0x643000 -> 0x777BC4
> init_bootmem wipes from 0x777000 -> 0x8F7000
> 
> So the BSS bytes from 0x777000 ->0x777BC4 (which looks very suspiciously
> pile a page alignment of addr & PAGE_MASK) gets set to 0xFF. One possible
> fix is below. It adds a check in bad_addr() to see if the BSS section is
> about to be used for bootmap. It Seems To Work For Me (tm) and illustrates
> the source of the problem even if it's not the 100% correct fix.
> 

Ok, it looks like that code is assuming that memory area returned by
find_e820_area() is page aligned. I found two such instances and that's
what is leading to problem.

        bootmap_size = init_bootmem_node(NODE_DATA(nodeid),
                                         bootmap_start >> PAGE_SHIFT,
                                         start_pfn, end_pfn);

Here bootmap_start is not page aligned and I guess  currently should
contain the value 0x777BC4 (just beyond _end). But the moement I do
bootmap_start>>PAGE_SHIFT, I start stomping bss.

Similar is the case here.

        bootmap = find_e820_area(0, end_pfn<<PAGE_SHIFT, bootmap_size);
        if (bootmap == -1L)
                panic("Cannot find bootmem map of size %ld\n",bootmap_size);
        bootmap_size = init_bootmem(bootmap >> PAGE_SHIFT, end_pfn);

So may be we should return a page aligned address from find_e820_area(). 
May be we can change bad_addr() to set *addrp to next page aligned 
boundary for every check?

 	*addrp = PAGE_ALIGN(__pa_symbol(&_end));

Thanks
Vivek

Re: 2.6.18-mm2 boot failure on x86-64

[Steve Fox]

On Fri, 2006-10-06 at 18:11 +0100, Mel Gorman wrote:
> On (06/10/06 11:36), Vivek Goyal didst pronounce:
> > Where is bss placed in physical memory? I guess bss_start and bss_stop
> > from System.map will tell us. That will confirm that above memset step is
> > stomping over bss. Then we have to just find that somewhere probably
> > we allocated wrong physical memory area for bootmem allocator map.
> > 
> 
> BSS is at 0x643000 -> 0x777BC4
> init_bootmem wipes from 0x777000 -> 0x8F7000
> 
> So the BSS bytes from 0x777000 ->0x777BC4 (which looks very suspiciously
> pile a page alignment of addr & PAGE_MASK) gets set to 0xFF. One possible
> fix is below. It adds a check in bad_addr() to see if the BSS section is
> about to be used for bootmap. It Seems To Work For Me (tm) and illustrates
> the source of the problem even if it's not the 100% correct fix.

I was able to boot the machine with Mel's patch applied on top of
-git22.

-- 

Steve Fox
IBM Linux Technology Center

Re: 2.6.18-mm2 boot failure on x86-64

[Vivek Goyal]

On Fri, Oct 06, 2006 at 01:03:50PM -0500, Steve Fox wrote:
> On Fri, 2006-10-06 at 18:11 +0100, Mel Gorman wrote:
> > On (06/10/06 11:36), Vivek Goyal didst pronounce:
> > > Where is bss placed in physical memory? I guess bss_start and bss_stop
> > > from System.map will tell us. That will confirm that above memset step is
> > > stomping over bss. Then we have to just find that somewhere probably
> > > we allocated wrong physical memory area for bootmem allocator map.
> > > 
> > 
> > BSS is at 0x643000 -> 0x777BC4
> > init_bootmem wipes from 0x777000 -> 0x8F7000
> > 
> > So the BSS bytes from 0x777000 ->0x777BC4 (which looks very suspiciously
> > pile a page alignment of addr & PAGE_MASK) gets set to 0xFF. One possible
> > fix is below. It adds a check in bad_addr() to see if the BSS section is
> > about to be used for bootmap. It Seems To Work For Me (tm) and illustrates
> > the source of the problem even if it's not the 100% correct fix.
> 
> I was able to boot the machine with Mel's patch applied on top of
> -git22.


Please have a look at the attached patch. Does it make some sense. 

Steve, can you please give this patch a try if it fixes the problem?

Thanks
Vivek




o Currently some code pieces assume that address returned by find_e820_area()
  are page aligned. But looks like find_e820_area() had no such intention
  and hence one might end up stomping over some of the data. One such
  case is bootmem allocator initialization code stomped over bss.

o This patch modified find_e820_area() to return page aligned address. This
  might be little wasteful of memory but at the same time probably it is
  easier to handle page aligned memory. 

Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com>
---

 arch/x86_64/kernel/e820.c |   14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff -puN arch/x86_64/kernel/e820.c~x86_64-return-page-aligned-phy-addr-from-find-e820-area arch/x86_64/kernel/e820.c
--- linux-2.6.19-rc1-1M/arch/x86_64/kernel/e820.c~x86_64-return-page-aligned-phy-addr-from-find-e820-area	2006-10-06 15:28:13.000000000 -0400
+++ linux-2.6.19-rc1-1M-root/arch/x86_64/kernel/e820.c	2006-10-06 15:44:45.000000000 -0400
@@ -54,13 +54,13 @@ static inline int bad_addr(unsigned long
 
 	/* various gunk below that needed for SMP startup */
 	if (addr < 0x8000) { 
-		*addrp = 0x8000;
+		*addrp = PAGE_ALIGN(0x8000);
 		return 1; 
 	}
 
 	/* direct mapping tables of the kernel */
 	if (last >= table_start<<PAGE_SHIFT && addr < table_end<<PAGE_SHIFT) { 
-		*addrp = table_end << PAGE_SHIFT; 
+		*addrp = PAGE_ALIGN(table_end << PAGE_SHIFT);
 		return 1;
 	} 
 
@@ -68,18 +68,18 @@ static inline int bad_addr(unsigned long
 #ifdef CONFIG_BLK_DEV_INITRD
 	if (LOADER_TYPE && INITRD_START && last >= INITRD_START && 
 	    addr < INITRD_START+INITRD_SIZE) { 
-		*addrp = INITRD_START + INITRD_SIZE; 
+		*addrp = PAGE_ALIGN(INITRD_START + INITRD_SIZE);
 		return 1;
 	} 
 #endif
 	/* kernel code */
-	if (last >= __pa_symbol(&_text) && last < __pa_symbol(&_end)) {
-		*addrp = __pa_symbol(&_end);
+	if (last >= __pa_symbol(&_text) && addr < __pa_symbol(&_end)) {
+		*addrp = PAGE_ALIGN(__pa_symbol(&_end));
 		return 1;
 	}
 
 	if (last >= ebda_addr && addr < ebda_addr + ebda_size) {
-		*addrp = ebda_addr + ebda_size;
+		*addrp = PAGE_ALIGN(ebda_addr + ebda_size);
 		return 1;
 	}
 
@@ -152,7 +152,7 @@ unsigned long __init find_e820_area(unsi
 			continue; 
 		while (bad_addr(&addr, size) && addr+size <= ei->addr+ei->size)
 			;
-		last = addr + size;
+		last = PAGE_ALIGN(addr) + size;
 		if (last > ei->addr + ei->size)
 			continue;
 		if (last > end) 
_

Re: 2.6.18-mm2 boot failure on x86-64

[Mel Gorman]

On Fri, 6 Oct 2006, Vivek Goyal wrote:

> On Fri, Oct 06, 2006 at 01:03:50PM -0500, Steve Fox wrote:
>> On Fri, 2006-10-06 at 18:11 +0100, Mel Gorman wrote:
>>> On (06/10/06 11:36), Vivek Goyal didst pronounce:
>>>> Where is bss placed in physical memory? I guess bss_start and bss_stop
>>>> from System.map will tell us. That will confirm that above memset step is
>>>> stomping over bss. Then we have to just find that somewhere probably
>>>> we allocated wrong physical memory area for bootmem allocator map.
>>>>
>>>
>>> BSS is at 0x643000 -> 0x777BC4
>>> init_bootmem wipes from 0x777000 -> 0x8F7000
>>>
>>> So the BSS bytes from 0x777000 ->0x777BC4 (which looks very suspiciously
>>> pile a page alignment of addr & PAGE_MASK) gets set to 0xFF. One possible
>>> fix is below. It adds a check in bad_addr() to see if the BSS section is
>>> about to be used for bootmap. It Seems To Work For Me (tm) and illustrates
>>> the source of the problem even if it's not the 100% correct fix.
>>
>> I was able to boot the machine with Mel's patch applied on top of
>> -git22.
>
>
> Please have a look at the attached patch. Does it make some sense.
>

It makes some sense. As you state, it wastes memory but that is better 
than breaking.

> Steve, can you please give this patch a try if it fixes the problem?
>

I boottested the patch on the same machine as Steve was using and it 
completed successfully.

> Thanks
> Vivek
>
>
>
>
> o Currently some code pieces assume that address returned by find_e820_area()
>  are page aligned. But looks like find_e820_area() had no such intention
>  and hence one might end up stomping over some of the data. One such
>  case is bootmem allocator initialization code stomped over bss.
>
> o This patch modified find_e820_area() to return page aligned address. This
>  might be little wasteful of memory but at the same time probably it is
>  easier to handle page aligned memory.
>
> Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com>
> ---
>
> arch/x86_64/kernel/e820.c |   14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff -puN arch/x86_64/kernel/e820.c~x86_64-return-page-aligned-phy-addr-from-find-e820-area arch/x86_64/kernel/e820.c
> --- linux-2.6.19-rc1-1M/arch/x86_64/kernel/e820.c~x86_64-return-page-aligned-phy-addr-from-find-e820-area	2006-10-06 15:28:13.000000000 -0400
> +++ linux-2.6.19-rc1-1M-root/arch/x86_64/kernel/e820.c	2006-10-06 15:44:45.000000000 -0400
> @@ -54,13 +54,13 @@ static inline int bad_addr(unsigned long
>
> 	/* various gunk below that needed for SMP startup */
> 	if (addr < 0x8000) {
> -		*addrp = 0x8000;
> +		*addrp = PAGE_ALIGN(0x8000);
> 		return 1;
> 	}
>
> 	/* direct mapping tables of the kernel */
> 	if (last >= table_start<<PAGE_SHIFT && addr < table_end<<PAGE_SHIFT) {
> -		*addrp = table_end << PAGE_SHIFT;
> +		*addrp = PAGE_ALIGN(table_end << PAGE_SHIFT);
> 		return 1;
> 	}
>
> @@ -68,18 +68,18 @@ static inline int bad_addr(unsigned long
> #ifdef CONFIG_BLK_DEV_INITRD
> 	if (LOADER_TYPE && INITRD_START && last >= INITRD_START &&
> 	    addr < INITRD_START+INITRD_SIZE) {
> -		*addrp = INITRD_START + INITRD_SIZE;
> +		*addrp = PAGE_ALIGN(INITRD_START + INITRD_SIZE);
> 		return 1;
> 	}
> #endif
> 	/* kernel code */
> -	if (last >= __pa_symbol(&_text) && last < __pa_symbol(&_end)) {
> -		*addrp = __pa_symbol(&_end);
> +	if (last >= __pa_symbol(&_text) && addr < __pa_symbol(&_end)) {
> +		*addrp = PAGE_ALIGN(__pa_symbol(&_end));
> 		return 1;
> 	}
>
> 	if (last >= ebda_addr && addr < ebda_addr + ebda_size) {
> -		*addrp = ebda_addr + ebda_size;
> +		*addrp = PAGE_ALIGN(ebda_addr + ebda_size);
> 		return 1;
> 	}
>
> @@ -152,7 +152,7 @@ unsigned long __init find_e820_area(unsi
> 			continue;
> 		while (bad_addr(&addr, size) && addr+size <= ei->addr+ei->size)
> 			;
> -		last = addr + size;
> +		last = PAGE_ALIGN(addr) + size;
> 		if (last > ei->addr + ei->size)
> 			continue;
> 		if (last > end)
> _
>

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

Re: 2.6.18-mm2 boot failure on x86-64

[Vivek Goyal]

On Mon, Oct 09, 2006 at 10:53:58AM +0100, Mel Gorman wrote:
> On Fri, 6 Oct 2006, Vivek Goyal wrote:
> 
> >On Fri, Oct 06, 2006 at 01:03:50PM -0500, Steve Fox wrote:
> >>On Fri, 2006-10-06 at 18:11 +0100, Mel Gorman wrote:
> >>>On (06/10/06 11:36), Vivek Goyal didst pronounce:
> >>>>Where is bss placed in physical memory? I guess bss_start and bss_stop
> >>>>from System.map will tell us. That will confirm that above memset step 
> >>>>is
> >>>>stomping over bss. Then we have to just find that somewhere probably
> >>>>we allocated wrong physical memory area for bootmem allocator map.
> >>>>
> >>>
> >>>BSS is at 0x643000 -> 0x777BC4
> >>>init_bootmem wipes from 0x777000 -> 0x8F7000
> >>>
> >>>So the BSS bytes from 0x777000 ->0x777BC4 (which looks very suspiciously
> >>>pile a page alignment of addr & PAGE_MASK) gets set to 0xFF. One possible
> >>>fix is below. It adds a check in bad_addr() to see if the BSS section is
> >>>about to be used for bootmap. It Seems To Work For Me (tm) and 
> >>>illustrates
> >>>the source of the problem even if it's not the 100% correct fix.
> >>
> >>I was able to boot the machine with Mel's patch applied on top of
> >>-git22.
> >
> >
> >Please have a look at the attached patch. Does it make some sense.
> >
> 
> It makes some sense. As you state, it wastes memory but that is better 
> than breaking.
> 
> >Steve, can you please give this patch a try if it fixes the problem?
> >
> 
> I boottested the patch on the same machine as Steve was using and it 
> completed successfully.
>

Hi Andrew,

Can you please have a look at the attached patch and include it in -mm.
This fixes the issue for steve. It also figures in the list of Adrian Bunk
of known regressions.

Subject    : oops in xfrm_register_mode
References : http://lkml.org/lkml/2006/10/4/170
Submitter  : Steve Fox <drfickle@us.ibm.com>
Handled-By : Vivek Goyal <vgoyal@in.ibm.com>
Status     : patch available



o Currently some code pieces assume that address returned by find_e820_area()
  are page aligned. But looks like find_e820_area() had no such intention
  and hence one might end up stomping over some of the data. One such
  case is bootmem allocator initialization code stomped over bss.

o This patch modified find_e820_area() to return page aligned address. This
  might be little wasteful of memory but at the same time probably it is
  easier to handle page aligned memory. 

Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com>
---

 arch/x86_64/kernel/e820.c |   14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff -puN arch/x86_64/kernel/e820.c~x86_64-return-page-aligned-phy-addr-from-find-e820-area arch/x86_64/kernel/e820.c
--- linux-2.6.19-rc1-1M/arch/x86_64/kernel/e820.c~x86_64-return-page-aligned-phy-addr-from-find-e820-area	2006-10-06 15:28:13.000000000 -0400
+++ linux-2.6.19-rc1-1M-root/arch/x86_64/kernel/e820.c	2006-10-06 15:44:45.000000000 -0400
@@ -54,13 +54,13 @@ static inline int bad_addr(unsigned long
 
 	/* various gunk below that needed for SMP startup */
 	if (addr < 0x8000) { 
-		*addrp = 0x8000;
+		*addrp = PAGE_ALIGN(0x8000);
 		return 1; 
 	}
 
 	/* direct mapping tables of the kernel */
 	if (last >= table_start<<PAGE_SHIFT && addr < table_end<<PAGE_SHIFT) { 
-		*addrp = table_end << PAGE_SHIFT; 
+		*addrp = PAGE_ALIGN(table_end << PAGE_SHIFT);
 		return 1;
 	} 
 
@@ -68,18 +68,18 @@ static inline int bad_addr(unsigned long
 #ifdef CONFIG_BLK_DEV_INITRD
 	if (LOADER_TYPE && INITRD_START && last >= INITRD_START && 
 	    addr < INITRD_START+INITRD_SIZE) { 
-		*addrp = INITRD_START + INITRD_SIZE; 
+		*addrp = PAGE_ALIGN(INITRD_START + INITRD_SIZE);
 		return 1;
 	} 
 #endif
 	/* kernel code */
-	if (last >= __pa_symbol(&_text) && last < __pa_symbol(&_end)) {
-		*addrp = __pa_symbol(&_end);
+	if (last >= __pa_symbol(&_text) && addr < __pa_symbol(&_end)) {
+		*addrp = PAGE_ALIGN(__pa_symbol(&_end));
 		return 1;
 	}
 
 	if (last >= ebda_addr && addr < ebda_addr + ebda_size) {
-		*addrp = ebda_addr + ebda_size;
+		*addrp = PAGE_ALIGN(ebda_addr + ebda_size);
 		return 1;
 	}
 
@@ -152,7 +152,7 @@ unsigned long __init find_e820_area(unsi
 			continue; 
 		while (bad_addr(&addr, size) && addr+size <= ei->addr+ei->size)
 			;
-		last = addr + size;
+		last = PAGE_ALIGN(addr) + size;
 		if (last > ei->addr + ei->size)
 			continue;
 		if (last > end) 
_

Re: 2.6.18-mm2 boot failure on x86-64

[Andrew Morton]

On Mon, 16 Oct 2006 14:16:13 -0400
Vivek Goyal <vgoyal@in.ibm.com> wrote:

> 
> Can you please have a look at the attached patch

Looks like a fine patch to me, although it could benefit from a comment
explaining why all those PAGE_ALIGN()s are in there.

> and include it in -mm.

Does it fix a patch in -mm or is it needed in mainline?

Re: 2.6.18-mm2 boot failure on x86-64

[Adrian Bunk]

On Mon, Oct 16, 2006 at 04:58:14PM -0700, Andrew Morton wrote:
> On Mon, 16 Oct 2006 14:16:13 -0400
> Vivek Goyal <vgoyal@in.ibm.com> wrote:
> 
> > 
> > Can you please have a look at the attached patch
> 
> Looks like a fine patch to me, although it could benefit from a comment
> explaining why all those PAGE_ALIGN()s are in there.
> 
> > and include it in -mm.
> 
> Does it fix a patch in -mm or is it needed in mainline?

The bug in my list was reported to be present in mainline [1].

cu
Adrian

[1] http://lkml.org/lkml/2006/10/4/394

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: 2.6.18-mm2 boot failure on x86-64

[Mel Gorman]

On Tue, 17 Oct 2006, Adrian Bunk wrote:

> On Mon, Oct 16, 2006 at 04:58:14PM -0700, Andrew Morton wrote:
>> On Mon, 16 Oct 2006 14:16:13 -0400
>> Vivek Goyal <vgoyal@in.ibm.com> wrote:
>>
>>>
>>> Can you please have a look at the attached patch
>>
>> Looks like a fine patch to me, although it could benefit from a comment
>> explaining why all those PAGE_ALIGN()s are in there.
>>
>>> and include it in -mm.
>>
>> Does it fix a patch in -mm or is it needed in mainline?
>
> The bug in my list was reported to be present in mainline [1].
>

Confirmed. This bug is present in 2.6.19-rc2

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

Re: 2.6.18-mm2 boot failure on x86-64

[Vivek Goyal]

On Thu, Oct 05, 2006 at 08:27:02PM +0200, Andi Kleen wrote:
> On Thursday 05 October 2006 19:57, Steve Fox wrote:
> > On Thu, 2006-10-05 at 17:40 +0200, Andi Kleen wrote:
> > 
> > > Please don't snip the Code: line. It is fairly important.
> > 
> > Sorry about that. The remote console I was using appears to overwrite
> > some text after I force the reboot. Here's a clean one.
> > 
> > global ffffffffffffffff
> 
> Ok that definitely shouldn't be in there.
> 
> I guess we need to track when it gets corrupted. Can you send the full
> boot log with this patch applied?
> 

Just recalled one more observation about the problem when keith had
reported it last. If I just move .bss before .data_nosave instead
of it being at the end, keith's problem had disappeared.

Thanks
Vivek

Re: 2.6.18-mm2 boot failure on x86-64

[Andi Kleen]

On Thursday 05 October 2006 20:52, Vivek Goyal wrote:
> On Thu, Oct 05, 2006 at 08:27:02PM +0200, Andi Kleen wrote:
> > On Thursday 05 October 2006 19:57, Steve Fox wrote:
> > > On Thu, 2006-10-05 at 17:40 +0200, Andi Kleen wrote:
> > > 
> > > > Please don't snip the Code: line. It is fairly important.
> > > 
> > > Sorry about that. The remote console I was using appears to overwrite
> > > some text after I force the reboot. Here's a clean one.
> > > 
> > > global ffffffffffffffff
> > 
> > Ok that definitely shouldn't be in there.
> > 
> > I guess we need to track when it gets corrupted. Can you send the full
> > boot log with this patch applied?
> > 
> 
> Just recalled one more observation about the problem when keith had
> reported it last. If I just move .bss before .data_nosave instead
> of it being at the end, keith's problem had disappeared.

Yes, that could well be that it's something in the new bootmap 
management.  Steve's box failed at

Using ACPI (MADT) for SMP configuration information
Nosave address range: 000000000009a000 - 000000000009b000
Nosave address range: 000000000009b000 - 00000000000a0000
Nosave address range: 00000000000a0000 - 00000000000e0000
Nosave address range: 00000000000e0000 - 0000000000100000
Nosave address range: 00000000bff76000 - 00000000bff77000
Nosave address range: 00000000bff77000 - 00000000bff98000
Nosave address range: 00000000bff98000 - 00000000bff99000
Nosave address range: 00000000bff99000 - 00000000c0000000
Nosave address range: 00000000c0000000 - 00000000fec00000
Nosave address range: 00000000fec00000 - 0000000100000000
Allocating PCI resources starting at c4000000 (gap: c0000000:3ec00000)
afinfo corrupted at init/main.c:512

which is directly after that code does lots of stuff.

Mel might want to take a look (and perhaps
also cut down a little on the ugly printks ...) 

BTW I found one of my test systems too now which does a lot of:
I'm about to leave for vacation so i won't have time to track it down
any time soon. But here is it for reference.

-Andi

Please enable the IOMMU option in the BIOS setup
This costs you 64 MB of RAM
Mapping aperture over 65536 KB of RAM @ 8000000
Bad page state in process 'swapper'
page:ffff810003ee5480 flags:0x0000000000000000 mapping:0000000000000000 mapcount:1 count:0
Trying to fix it up, but a reboot is needed
Backtrace:   

Call Trace:  
 [<ffffffff8020ac84>] show_trace+0x34/0x47
 [<ffffffff8020aca9>] dump_stack+0x12/0x17
 [<ffffffff802586a7>] bad_page+0x57/0x81
 [<ffffffff80258791>] __free_pages_ok+0x64/0x247
 [<ffffffff807cca72>] free_all_bootmem_core+0xcc/0x1a9
 [<ffffffff807ca08b>] numa_free_all_bootmem+0x3b/0x77
 [<ffffffff807c915e>] mem_init+0x44/0x186
 [<ffffffff807bc5f0>] start_kernel+0x17b/0x207
 [<ffffffff807bc168>] _sinittext+0x168/0x16c

Bad page state in process 'swapper'
page:ffff810003ee54b8 flags:0x0000000000000000 mapping:0000000000000000 mapcount:1 count:0
Trying to fix it up, but a reboot is needed
Backtrace:   

Call Trace:  
 [<ffffffff8020ac84>] show_trace+0x34/0x47
 [<ffffffff8020aca9>] dump_stack+0x12/0x17
 [<ffffffff802586a7>] bad_page+0x57/0x81
 [<ffffffff80258791>] __free_pages_ok+0x64/0x247
 [<ffffffff807cca72>] free_all_bootmem_core+0xcc/0x1a9
 [<ffffffff807ca08b>] numa_free_all_bootmem+0x3b/0x77
 [<ffffffff807c915e>] mem_init+0x44/0x186
 [<ffffffff807bc5f0>] start_kernel+0x17b/0x207
 [<ffffffff807bc168>] _sinittext+0x168/0x16c


... lots more of those ...

Re: 2.6.18-mm2 boot failure on x86-64

[Steve Fox]

On Thu, 2006-10-05 at 21:08 +0200, Andi Kleen wrote:

> Mel might want to take a look (and perhaps
> also cut down a little on the ugly printks ...) 

I tested a patch from Mel which backs out the arch independent zone
sizing and got the same results (to my inexperienced eye). I've sent him
the boot log to verify they really are the same as without this
back-out.

-- 

Steve Fox
IBM Linux Technology Center

Re: 2.6.18-mm2 boot failure on x86-64

[Mel Gorman]

On Thu, 5 Oct 2006, Andi Kleen wrote:

> On Thursday 05 October 2006 20:52, Vivek Goyal wrote:
>> On Thu, Oct 05, 2006 at 08:27:02PM +0200, Andi Kleen wrote:
>>> On Thursday 05 October 2006 19:57, Steve Fox wrote:
>>>> On Thu, 2006-10-05 at 17:40 +0200, Andi Kleen wrote:
>>>>
>>>>> Please don't snip the Code: line. It is fairly important.
>>>>
>>>> Sorry about that. The remote console I was using appears to overwrite
>>>> some text after I force the reboot. Here's a clean one.
>>>>
>>>> global ffffffffffffffff
>>>
>>> Ok that definitely shouldn't be in there.
>>>
>>> I guess we need to track when it gets corrupted. Can you send the full
>>> boot log with this patch applied?
>>>
>>
>> Just recalled one more observation about the problem when keith had
>> reported it last. If I just move .bss before .data_nosave instead
>> of it being at the end, keith's problem had disappeared.
>
> Yes, that could well be that it's something in the new bootmap
> management.  Steve's box failed at
>
> Using ACPI (MADT) for SMP configuration information
> Nosave address range: 000000000009a000 - 000000000009b000
> Nosave address range: 000000000009b000 - 00000000000a0000
> Nosave address range: 00000000000a0000 - 00000000000e0000
> Nosave address range: 00000000000e0000 - 0000000000100000
> Nosave address range: 00000000bff76000 - 00000000bff77000
> Nosave address range: 00000000bff77000 - 00000000bff98000
> Nosave address range: 00000000bff98000 - 00000000bff99000
> Nosave address range: 00000000bff99000 - 00000000c0000000
> Nosave address range: 00000000c0000000 - 00000000fec00000
> Nosave address range: 00000000fec00000 - 0000000100000000
> Allocating PCI resources starting at c4000000 (gap: c0000000:3ec00000)
> afinfo corrupted at init/main.c:512
>
> which is directly after that code does lots of stuff.
>
> Mel might want to take a look (and perhaps
> also cut down a little on the ugly printks ...)
>

Steve tested a patch with arch-independent zone-sizing backed out for 
x86_64 and things looked ok but that is no guarantee it is not a 
contributary factor. The "Nosave address range:" printks are related to a 
suspend problem that was reported .... end of June I believe.

I'll pick this up in the morning because I should have access to the same 
machine Steve does and see what I can come up with.

> BTW I found one of my test systems too now which does a lot of:
> I'm about to leave for vacation so i won't have time to track it down
> any time soon. But here is it for reference.
>

hmm, rather than bugging you with patches now, I'll see what I can find 
with the x86_64 machines I have access to and see can I reproduce it.

> -Andi
>
> Please enable the IOMMU option in the BIOS setup
> This costs you 64 MB of RAM
> Mapping aperture over 65536 KB of RAM @ 8000000
> Bad page state in process 'swapper'
> page:ffff810003ee5480 flags:0x0000000000000000 mapping:0000000000000000 mapcount:1 count:0
> Trying to fix it up, but a reboot is needed
> Backtrace:
>
> Call Trace:
> [<ffffffff8020ac84>] show_trace+0x34/0x47
> [<ffffffff8020aca9>] dump_stack+0x12/0x17
> [<ffffffff802586a7>] bad_page+0x57/0x81
> [<ffffffff80258791>] __free_pages_ok+0x64/0x247
> [<ffffffff807cca72>] free_all_bootmem_core+0xcc/0x1a9
> [<ffffffff807ca08b>] numa_free_all_bootmem+0x3b/0x77
> [<ffffffff807c915e>] mem_init+0x44/0x186
> [<ffffffff807bc5f0>] start_kernel+0x17b/0x207
> [<ffffffff807bc168>] _sinittext+0x168/0x16c
>
> Bad page state in process 'swapper'
> page:ffff810003ee54b8 flags:0x0000000000000000 mapping:0000000000000000 mapcount:1 count:0
> Trying to fix it up, but a reboot is needed
> Backtrace:
>
> Call Trace:
> [<ffffffff8020ac84>] show_trace+0x34/0x47
> [<ffffffff8020aca9>] dump_stack+0x12/0x17
> [<ffffffff802586a7>] bad_page+0x57/0x81
> [<ffffffff80258791>] __free_pages_ok+0x64/0x247
> [<ffffffff807cca72>] free_all_bootmem_core+0xcc/0x1a9
> [<ffffffff807ca08b>] numa_free_all_bootmem+0x3b/0x77
> [<ffffffff807c915e>] mem_init+0x44/0x186
> [<ffffffff807bc5f0>] start_kernel+0x17b/0x207
> [<ffffffff807bc168>] _sinittext+0x168/0x16c
>
>
> ... lots more of those ...
>

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

Re: 2.6.18-mm2 boot failure on x86-64

[Andi Kleen]

> hmm, rather than bugging you with patches now, I'll see what I can find 
> with the x86_64 machines I have access to and see can I reproduce it.

I started the bisect, should finish soon.

-Andi

Re: 2.6.18-mm2 boot failure on x86-64 II

[Andi Kleen]

On Thursday 05 October 2006 22:51, Andi Kleen wrote:
> 
> > hmm, rather than bugging you with patches now, I'll see what I can find 
> > with the x86_64 machines I have access to and see can I reproduce it.
> 
> I started the bisect, should finish soon.

It ended at 

diff-tree d5cdb67236dba94496de052c9f9f431e1fc658f4 (from 0dad3510ee82bcf8a380b81
a2184a664a911ef9c)
Author: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Date:   Tue Sep 12 10:19:00 2006 -0700

    acpiphp: disable bridges
    
    Currently acpiphp calls pci_enable_device() against all
    hot-added bridges, but acpiphp does not call pci_disable_device()
    against them in hot-remove. So ioapic hot-remove would fail.
    This patch fixes this issue.

Not sure that is it really, it is possible i made a mistake during bisect
(the symptoms changed from bad page to just networking doesn't work
somewhere at 4cfee88ad30acc47f02b8b7ba3db8556262dce1e) 

I don't have time to rerun unfortunately
for some time. Anyone else looking would be useful.

-Andi

Re: 2.6.18-mm2 boot failure on x86-64 II

[keith mannthey]

On Fri, 2006-10-06 at 01:14 +0200, Andi Kleen wrote:
> On Thursday 05 October 2006 22:51, Andi Kleen wrote:
> > 
> > > hmm, rather than bugging you with patches now, I'll see what I can find 
> > > with the x86_64 machines I have access to and see can I reproduce it.
> > 
> > I started the bisect, should finish soon.
> 
> It ended at 
> 
> diff-tree d5cdb67236dba94496de052c9f9f431e1fc658f4 (from 0dad3510ee82bcf8a380b81
> a2184a664a911ef9c)
> Author: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
> Date:   Tue Sep 12 10:19:00 2006 -0700
> 
>     acpiphp: disable bridges
>     
>     Currently acpiphp calls pci_enable_device() against all
>     hot-added bridges, but acpiphp does not call pci_disable_device()
>     against them in hot-remove. So ioapic hot-remove would fail.
>     This patch fixes this issue.
> 
> Not sure that is it really, it is possible i made a mistake during bisect
> (the symptoms changed from bad page to just networking doesn't work
> somewhere at 4cfee88ad30acc47f02b8b7ba3db8556262dce1e) 
> 
> I don't have time to rerun unfortunately
> for some time. Anyone else looking would be useful.

As of yet I haven't been able to recreate the hang.  I am running
similar HW to Steve. 

Thanks,
  Keith 

Re: 2.6.18-mm2 boot failure on x86-64 II

[Andi Kleen]

> As of yet I haven't been able to recreate the hang.  I am running
> similar HW to Steve. 

That was on a 4 core Opteron with Tyan board  (S2881) and AMD-8111 
chipset.

-Andi

Re: 2.6.18-mm2 boot failure on x86-64 II

[keith mannthey]

On Fri, 2006-10-06 at 01:35 +0200, Andi Kleen wrote:
> > As of yet I haven't been able to recreate the hang.  I am running
> > similar HW to Steve. 

I ran into this with -mm3

Memory: 24150368k/26738688k available (1933k kernel code, 490260k
reserved, 978k data, 308k init)
------------[ cut here ]------------
kernel BUG in init_list at mm/slab.c:1334!
invalid opcode: 0000 [1] SMP
last sysfs file:
CPU 0
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.18-mm3-smp #1
RIP: 0010:[<ffffffff8027f8fa>]  [<ffffffff8027f8fa>] init_list+0x1d/0xfd
RSP: 0018:ffffffff80577f48  EFLAGS: 00010212
RAX: 0000000000000040 RBX: 0000000000000001 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff805ba848 RDI: ffff810460700040
RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000003
R10: 0000000000000000 R11: ffffffff805bc268 R12: ffff810460700040
R13: ffffffff805ba848 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffffffff804d8000(0000)
knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 0000000000201000 CR4: 00000000000006a0
Process swapper (pid: 0, threadinfo ffffffff80576000, task
ffffffff80455840)
Stack:  0000000000000000 0000000000000000 0000000100000000
0000000000000001
 ffffffff805ba848 0000000000000000 0000000000000000 ffffffff80593aa8
 00000000000002c0 0000000100000001 000000000008ef00 000000000008c000
Call Trace:
 [<ffffffff80593aa8>] kmem_cache_init+0x344/0x406
 [<ffffffff805805ef>] start_kernel+0x180/0x21b
 [<ffffffff8058016a>] _sinittext+0x16a/0x16e


Code: 0f 0b 48 8b 3d 15 ab 1e 00 be d0 00 00 00 e8 c0 f5 ff ff 48
RIP  [<ffffffff8027f8fa>] init_list+0x1d/0xfd
 RSP <ffffffff80577f48>
 <0>Kernel panic - not syncing: Attempted to kill the idle task!


I am going to revert the patch and see if it works.  I ran -git22 just
fine. 

Thanks,
  Keith 

Re: 2.6.18-mm2 boot failure on x86-64 II

[Badari Pulavarty]

keith mannthey wrote:
> On Fri, 2006-10-06 at 01:35 +0200, Andi Kleen wrote:
>   
>>> As of yet I haven't been able to recreate the hang.  I am running
>>> similar HW to Steve. 
>>>       
>
> I ran into this with -mm3
>
> Memory: 24150368k/26738688k available (1933k kernel code, 490260k
> reserved, 978k data, 308k init)
> ------------[ cut here ]------------
> kernel BUG in init_list at mm/slab.c:1334!
> invalid opcode: 0000 [1] SMP
> last sysfs file:
> CPU 0
> Modules linked in:
> Pid: 0, comm: swapper Not tainted 2.6.18-mm3-smp #1
> RIP: 0010:[<ffffffff8027f8fa>]  [<ffffffff8027f8fa>] init_list+0x1d/0xfd
> RSP: 0018:ffffffff80577f48  EFLAGS: 00010212
> RAX: 0000000000000040 RBX: 0000000000000001 RCX: 0000000000000000
> RDX: 0000000000000001 RSI: ffffffff805ba848 RDI: ffff810460700040
> RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000003
> R10: 0000000000000000 R11: ffffffff805bc268 R12: ffff810460700040
> R13: ffffffff805ba848 R14: 0000000000000000 R15: 0000000000000000
> FS:  0000000000000000(0000) GS:ffffffff804d8000(0000)
> knlGS:0000000000000000
> CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> CR2: 0000000000000000 CR3: 0000000000201000 CR4: 00000000000006a0
> Process swapper (pid: 0, threadinfo ffffffff80576000, task
> ffffffff80455840)
> Stack:  0000000000000000 0000000000000000 0000000100000000
> 0000000000000001
>  ffffffff805ba848 0000000000000000 0000000000000000 ffffffff80593aa8
>  00000000000002c0 0000000100000001 000000000008ef00 000000000008c000
> Call Trace:
>  [<ffffffff80593aa8>] kmem_cache_init+0x344/0x406
>  [<ffffffff805805ef>] start_kernel+0x180/0x21b
>  [<ffffffff8058016a>] _sinittext+0x16a/0x16e
>
>
> Code: 0f 0b 48 8b 3d 15 ab 1e 00 be d0 00 00 00 e8 c0 f5 ff ff 48
> RIP  [<ffffffff8027f8fa>] init_list+0x1d/0xfd
>  RSP <ffffffff80577f48>
>  <0>Kernel panic - not syncing: Attempted to kill the idle task!
>
>
> I am going to revert the patch and see if it works.  I ran -git22 just
> fine. 
>
> Thanks,
>   Keith 
>
>   
Keith,

I fixed this already. Can you look for it on lkml (look for 2.6.18-mm3 
in the subject line).
one typo in mm/slab.c

Thanks,
Badari

Re: 2.6.18-mm2 boot failure on x86-64 II

[Andrew Morton]

On Thu, 05 Oct 2006 17:02:54 -0700
Badari Pulavarty <pbadari@us.ibm.com> wrote:

> > Code: 0f 0b 48 8b 3d 15 ab 1e 00 be d0 00 00 00 e8 c0 f5 ff ff 48
> > RIP  [<ffffffff8027f8fa>] init_list+0x1d/0xfd
> >  RSP <ffffffff80577f48>
> >  <0>Kernel panic - not syncing: Attempted to kill the idle task!
> >
> >
> > I am going to revert the patch and see if it works.  I ran -git22 just
> > fine. 
> >
> > Thanks,
> >   Keith 
> >
> >   
> Keith,
> 
> I fixed this already. Can you look for it on lkml (look for 2.6.18-mm3 
> in the subject line).
> one typo in mm/slab.c

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18/2.6.18-mm3/hot-fixes

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 3192 bytes --]

On Fri, 29 Sep 2006 12:45:58 PDT, Andrew Morton said:

(Adding a bunch of people to the cc: list now that I have a clue what is
going on....)

> I'd expect it's the same bug - slab data structures have gone bad.

*bing*! We have a winner.  A quick check showed the kernel wasn't built with
slab debugging enabled, so I turned on the more obvious options, and got
rewarded with a traceback..

> Again: how come nobody else is hitting this?  Something's different.

gkrellm and wireless (specifically, gkrellm-wifi-0.9.12-3.fc6 from Fedora
Core extras-development).  Kernel is still a 2.6.18 with *only* the
origin.patch from -mm2 applied. Note that the gkrellm plugin hasn't had
a change in the code since 01/03/2004 - hopefully there's been no unintentional
API change on the kernel side since then...

Here's the traceback I got:

slab error in verify_redzone_free(): cache `size-32': memory outside object was overwritten
[<c0103ad2>] dump_trace+0x64/0x1cd
[<c0103c4d>] show_trace_log_lvl+0x12/0x25
[<c010415f>] show_trace+0xd/0x10
[<c01041fc>] dump_stack+0x19/0x1b
[<c014c796>] __slab_error+0x17/0x1c
[<c014cdac>] cache_free_debugcheck+0xaf/0x230
[<c014d43e>] kfree+0x59/0x8c
[<c02dc04a>] ioctl_standard_call+0x1da/0x218
[<c02dc275>] wireless_process_ioctl+0x55/0x312
[<c02d3750>] dev_ioctl+0x45f/0x49a
[<c02c92aa>] sock_ioctl+0x1b3/0x1c6
[<c0160322>] do_ioctl+0x22/0x67
[<c01605a5>] vfs_ioctl+0x23e/0x251
[<c01605ff>] sys_ioctl+0x47/0x64
[<c0102cd3>] syscall_call+0x7/0xb
DWARF2 unwinder stuck at syscall_call+0x7/0xb

Leftover inexact backtrace:

=======================
de57e16c: redzone 1:0x170fc2a5, redzone 2:0x170fc200.

Repeated, over and over, just about once a second.

A quick strace of gkrellm finds these likely ioctl's causing the problem:

% grep ioctl /tmp/foo2 | sort -u | more
ioctl(13, SIOCGIWESSID, 0xbfbcdb9c)     = 0
ioctl(13, SIOCGIWRANGE, 0xbfbcdbdc)     = 0
ioctl(13, SIOCGIWRATE, 0xbfbcdbbc)      = 0

Since I'm using an orinoco-based card, these 2 look like the most likely
candidates.  WE-21 was merged between -mm1 and -mm2, which is why -mm1 was
stable for me. I'll let somebody else argue over what path these took that
I never tripped over them in an earlier -mm before they hit Linus's tree...

commit baef186519c69b11cf7e48c26e75feb1e6173baa
Author: John W. Linville <linville@tuxdriver.com>
Date:   Fri Sep 8 16:04:05 2006 -0400

    [PATCH] WE-21 support (core API)

    This is version 21 of the Wireless Extensions. Changelog :
        o finishes migrating the ESSID API (remove the +1)
        o netdev->get_wireless_stats is no more
        o long/short retry

    This is a redacted version of a patch originally submitted by Jean
    Tourrilhes.  I removed most of the additions, in order to minimize
    future support requirements for nl80211 (or other WE successor).

    CC: Jean Tourrilhes <jt@hpl.hp.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

commit eeec9f1a931262d69811135092c8447d6dccc3e6
Author: Jean Tourrilhes <jt@hpl.hp.com>
Date:   Tue Aug 29 18:02:31 2006 -0700

    [PATCH] WE-21 for orinoco

    Signed-off-by: Jean Tourrilhes <jt@hpl.hp.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>




[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Andrew Morton]

On Fri, 29 Sep 2006 20:01:54 -0400
Valdis.Kletnieks@vt.edu wrote:

> On Fri, 29 Sep 2006 12:45:58 PDT, Andrew Morton said:
> 
> (Adding a bunch of people to the cc: list now that I have a clue what is
> going on....)
> 
> > I'd expect it's the same bug - slab data structures have gone bad.
> 
> *bing*! We have a winner.  A quick check showed the kernel wasn't built with
> slab debugging enabled, so I turned on the more obvious options, and got
> rewarded with a traceback..

doh.  I'd assumed that CONFIG_DEBUG_SLAB was enabled :(

> > Again: how come nobody else is hitting this?  Something's different.
> 
> gkrellm and wireless (specifically, gkrellm-wifi-0.9.12-3.fc6 from Fedora
> Core extras-development).  Kernel is still a 2.6.18 with *only* the
> origin.patch from -mm2 applied. Note that the gkrellm plugin hasn't had
> a change in the code since 01/03/2004 - hopefully there's been no unintentional
> API change on the kernel side since then...
> 
> Here's the traceback I got:
> 
> slab error in verify_redzone_free(): cache `size-32': memory outside object was overwritten
> [<c0103ad2>] dump_trace+0x64/0x1cd
> [<c0103c4d>] show_trace_log_lvl+0x12/0x25
> [<c010415f>] show_trace+0xd/0x10
> [<c01041fc>] dump_stack+0x19/0x1b
> [<c014c796>] __slab_error+0x17/0x1c
> [<c014cdac>] cache_free_debugcheck+0xaf/0x230
> [<c014d43e>] kfree+0x59/0x8c
> [<c02dc04a>] ioctl_standard_call+0x1da/0x218
> [<c02dc275>] wireless_process_ioctl+0x55/0x312
> [<c02d3750>] dev_ioctl+0x45f/0x49a
> [<c02c92aa>] sock_ioctl+0x1b3/0x1c6
> [<c0160322>] do_ioctl+0x22/0x67
> [<c01605a5>] vfs_ioctl+0x23e/0x251
> [<c01605ff>] sys_ioctl+0x47/0x64
> [<c0102cd3>] syscall_call+0x7/0xb
> DWARF2 unwinder stuck at syscall_call+0x7/0xb
> 
> Leftover inexact backtrace:
> 
> =======================
> de57e16c: redzone 1:0x170fc2a5, redzone 2:0x170fc200.
> 
> Repeated, over and over, just about once a second.
> 
> A quick strace of gkrellm finds these likely ioctl's causing the problem:
> 
> % grep ioctl /tmp/foo2 | sort -u | more
> ioctl(13, SIOCGIWESSID, 0xbfbcdb9c)     = 0
> ioctl(13, SIOCGIWRANGE, 0xbfbcdbdc)     = 0
> ioctl(13, SIOCGIWRATE, 0xbfbcdbbc)      = 0

Yes.  The main thing which those WE-21 patches do is to shorten the size of
various buffers which are used in wireless ioctls.

> Since I'm using an orinoco-based card, these 2 look like the most likely
> candidates.  WE-21 was merged between -mm1 and -mm2, which is why -mm1 was
> stable for me.

The WE-21 patches weren't in Jeff's tree for -mm1 or for -mm2.  They
appeared there transiently then quickly went mainline.  They _might_ have
been in the wireless git tree, although I often drop that due to git woes. 
But that hasn't happened recently....

> I'll let somebody else argue over what path these took that
> I never tripped over them in an earlier -mm before they hit Linus's tree...
> 
> commit baef186519c69b11cf7e48c26e75feb1e6173baa
> Author: John W. Linville <linville@tuxdriver.com>
> Date:   Fri Sep 8 16:04:05 2006 -0400
> 
>     [PATCH] WE-21 support (core API)
> 
>     This is version 21 of the Wireless Extensions. Changelog :
>         o finishes migrating the ESSID API (remove the +1)
>         o netdev->get_wireless_stats is no more
>         o long/short retry
> 
>     This is a redacted version of a patch originally submitted by Jean
>     Tourrilhes.  I removed most of the additions, in order to minimize
>     future support requirements for nl80211 (or other WE successor).
> 
>     CC: Jean Tourrilhes <jt@hpl.hp.com>
>     Signed-off-by: John W. Linville <linville@tuxdriver.com>
> 
> commit eeec9f1a931262d69811135092c8447d6dccc3e6
> Author: Jean Tourrilhes <jt@hpl.hp.com>
> Date:   Tue Aug 29 18:02:31 2006 -0700
> 
>     [PATCH] WE-21 for orinoco
> 
>     Signed-off-by: Jean Tourrilhes <jt@hpl.hp.com>
>     Signed-off-by: John W. Linville <linville@tuxdriver.com>
> 

Try reverting those?

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Jean Tourrilhes]

On Fri, Sep 29, 2006 at 06:20:08PM -0700, Andrew Morton wrote:
> On Fri, 29 Sep 2006 20:01:54 -0400
> > 
> > Here's the traceback I got:
> > 
> > slab error in verify_redzone_free(): cache `size-32': memory outside object was overwritten
> > [<c0103ad2>] dump_trace+0x64/0x1cd
> > [<c0103c4d>] show_trace_log_lvl+0x12/0x25
> > [<c010415f>] show_trace+0xd/0x10
> > [<c01041fc>] dump_stack+0x19/0x1b
> > [<c014c796>] __slab_error+0x17/0x1c
> > [<c014cdac>] cache_free_debugcheck+0xaf/0x230
> > [<c014d43e>] kfree+0x59/0x8c
> > [<c02dc04a>] ioctl_standard_call+0x1da/0x218
> > [<c02dc275>] wireless_process_ioctl+0x55/0x312
> > [<c02d3750>] dev_ioctl+0x45f/0x49a
> > [<c02c92aa>] sock_ioctl+0x1b3/0x1c6
> > [<c0160322>] do_ioctl+0x22/0x67
> > [<c01605a5>] vfs_ioctl+0x23e/0x251
> > [<c01605ff>] sys_ioctl+0x47/0x64
> > [<c0102cd3>] syscall_call+0x7/0xb
> > DWARF2 unwinder stuck at syscall_call+0x7/0xb

	Hum... Not clear what's happening. I'll look more into it on
monday.

> > A quick strace of gkrellm finds these likely ioctl's causing the problem:
> > 
> > % grep ioctl /tmp/foo2 | sort -u | more
> > ioctl(13, SIOCGIWESSID, 0xbfbcdb9c)     = 0

	That's most likely the one. I need to check the source code.

> Yes.  The main thing which those WE-21 patches do is to shorten the size of
> various buffers which are used in wireless ioctls.

	Only for ESSID, it reduce it by one char, and remove the final
'\0'. But, kernel wise, it should not matter.

> > Since I'm using an orinoco-based card, these 2 look like the most likely
> > candidates.  WE-21 was merged between -mm1 and -mm2, which is why -mm1 was
> > stable for me.

	I'm using Orinoco, I've not seen that with iwconfig.
	I'll look into that...

	Jean

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

On Fri, 29 Sep 2006 18:33:48 PDT, Jean Tourrilhes said:
> On Fri, Sep 29, 2006 at 06:20:08PM -0700, Andrew Morton wrote:
> > On Fri, 29 Sep 2006 20:01:54 -0400
> > > 
> > > Here's the traceback I got:
> > > 
> > > slab error in verify_redzone_free(): cache `size-32': memory outside object was overwritten

> 	Hum... Not clear what's happening. I'll look more into it on
> monday.

Fair enough,  I'm going to try reverting the 2 commits and see if things
behave better.

> 	I'm using Orinoco, I've not seen that with iwconfig.
> 	I'll look into that...

I'll bet it's the difference between a modern iwconfig and a 3-year-old
stone-age gkrellm plugin :)

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]

On Fri, 29 Sep 2006 23:31:07 EDT, Valdis.Kletnieks@vt.edu said:
> Fair enough,  I'm going to try reverting the 2 commits and see if things
> behave better.

OK, it's definitely something in those 2 commits - I reverted them and the
resulting 2.6.18-mm2 kernel has been up and stable for 4 hours, even with
the problem gkrellm updating once a second the whole time.

I'm not *seeing* how those changes can cause trouble - unless it's this:

diff --git a/drivers/net/wireless/orinoco.c b/drivers/net/wireless/orinoco.c
index 1840b69..9e19a96 100644
--- a/drivers/net/wireless/orinoco.c
+++ b/drivers/net/wireless/orinoco.c
@@ -3037,7 +3037,7 @@ static int orinoco_ioctl_getessid(struct
        }
 
        erq->flags = 1;
-       erq->length = strlen(essidbuf) + 1;
+       erq->length = strlen(essidbuf);

Does some other code go batshit if length ==0?  My current config doesn't
try to actually ifup the wireless if I also have connectivity via copper (in
order to avoid chewing up a DHCP lease in crowded address space if not needed).

% iwconfig eth5
eth5      IEEE 802.11b  ESSID:""  Nickname:"HERMES I"
          Mode:Managed  Frequency:2.457 GHz  Access Point: Not-Associated   
          Bit Rate:11 Mb/s   Sensitivity:1/3  
          Retry limit:4   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=0/92  Signal level=134/153  Noise level=134/153
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

That ESSID the source of the trouble?


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Andrew Morton]

On Sat, 30 Sep 2006 03:50:43 -0400
Valdis.Kletnieks@vt.edu wrote:

> On Fri, 29 Sep 2006 23:31:07 EDT, Valdis.Kletnieks@vt.edu said:
> > Fair enough,  I'm going to try reverting the 2 commits and see if things
> > behave better.
> 
> OK, it's definitely something in those 2 commits - I reverted them and the
> resulting 2.6.18-mm2 kernel has been up and stable for 4 hours, even with
> the problem gkrellm updating once a second the whole time.
> 
> I'm not *seeing* how those changes can cause trouble - unless it's this:
> 
> diff --git a/drivers/net/wireless/orinoco.c b/drivers/net/wireless/orinoco.c
> index 1840b69..9e19a96 100644
> --- a/drivers/net/wireless/orinoco.c
> +++ b/drivers/net/wireless/orinoco.c
> @@ -3037,7 +3037,7 @@ static int orinoco_ioctl_getessid(struct
>         }
>  
>         erq->flags = 1;
> -       erq->length = strlen(essidbuf) + 1;
> +       erq->length = strlen(essidbuf);

You know what the next question is ;)

Did reverting just that line fix it?

> Does some other code go batshit if length ==0? My current config doesn't
> try to actually ifup the wireless if I also have connectivity via copper (in
> order to avoid chewing up a DHCP lease in crowded address space if not needed).
> 
> % iwconfig eth5
> eth5      IEEE 802.11b  ESSID:""  Nickname:"HERMES I"
>           Mode:Managed  Frequency:2.457 GHz  Access Point: Not-Associated   
>           Bit Rate:11 Mb/s   Sensitivity:1/3  
>           Retry limit:4   RTS thr:off   Fragment thr:off
>           Power Management:off
>           Link Quality=0/92  Signal level=134/153  Noise level=134/153
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> 
> That ESSID the source of the trouble?
> 

Might be.  I can't immediately spot a problem with it, but perhaps
length==0 causes the driver to not allocate a buffer and to then write to
the not-allocated buffer.  Not sure..

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Jean Tourrilhes]

On Fri, Sep 29, 2006 at 06:20:08PM -0700, Andrew Morton wrote:
> On Fri, 29 Sep 2006 20:01:54 -0400
> > 
> > A quick strace of gkrellm finds these likely ioctl's causing the problem:
> > 
> > % grep ioctl /tmp/foo2 | sort -u | more
> > ioctl(13, SIOCGIWESSID, 0xbfbcdb9c)     = 0
> > ioctl(13, SIOCGIWRANGE, 0xbfbcdbdc)     = 0
> > ioctl(13, SIOCGIWRATE, 0xbfbcdbbc)      = 0

	Excuse me, can you point out wich version of gkrellm you use
and where to find it, the only version that is listed on my page does
not use the ESSID ioctl. I want to be sure I'm looking at the same
thing as you are...

	Jean

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

On Fri, 29 Sep 2006 18:40:43 PDT, Jean Tourrilhes said:
> On Fri, Sep 29, 2006 at 06:20:08PM -0700, Andrew Morton wrote:
> > On Fri, 29 Sep 2006 20:01:54 -0400
> > > 
> > > A quick strace of gkrellm finds these likely ioctl's causing the problem:
> > > 
> > > % grep ioctl /tmp/foo2 | sort -u | more
> > > ioctl(13, SIOCGIWESSID, 0xbfbcdb9c)     = 0
> > > ioctl(13, SIOCGIWRANGE, 0xbfbcdbdc)     = 0
> > > ioctl(13, SIOCGIWRATE, 0xbfbcdbbc)      = 0
> 
> 	Excuse me, can you point out wich version of gkrellm you use
> and where to find it, the only version that is listed on my page does
> not use the ESSID ioctl. I want to be sure I'm looking at the same
> thing as you are...

All the pieces:
http://download.fedora.redhat.com/pub/fedora/linux/extras/development/SRPMS/

The particular plugin causing the trouble:
http://download.fedora.redhat.com/pub/fedora/linux/extras/development/SRPMS/gkrellm-wifi-0.9.12-3.fc6.src.rpm

If you're not on a box that has rpm2cpio or similar, yell and I'll
break that .src.rpm up for you - there's basically just an 18K .tar.gz and
a 14K patch in there.

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Makefile for linux modules

[x z]

Hi
   I have a makefielt to make several driver modules:
obj-$(CONFIG_FUSION_SPI)	+= mptbase.o mptscsih.o
mptspi.o
obj-$(CONFIG_FUSION_FC)		+= mptbase.o mptscsih.o
mptfc.o
obj-m				+= mptbase.o mptscsih.o mptsas.o
obj-$(CONFIG_FUSION_LAN)	+= mptlan.o
obj-m				+= mptctl.o
obj-m                           += mptcfg.o
obj-m                       +=mptstm.o


this will compile and modules can be installed
successfully.

I need to have a comfunc.c file, which contains all
common functions, which could be used by these module
files.
I added the line below to the content just below
mptstm.o (I tried adding just above mptlan). All
modules are compiled successfully. I can install
mptbase.ko. However, when I try to install mptctl.ko
(or other modules), I got errors like mptctl: Unknown
symbol mpt_register; mpt_deregister. These functions
are implemented in mptbase.c.

How do I fix this problem?

thanks
Robert
mptbase-objs             := comfunc.o

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Makefile for linux modules

[Sam Ravnborg]

Hi Robert.

>    I have a makefielt to make several driver modules:
> obj-$(CONFIG_FUSION_SPI)	+= mptbase.o mptscsih.o
> mptspi.o
> obj-$(CONFIG_FUSION_FC)		+= mptbase.o mptscsih.o
> mptfc.o
> obj-m				+= mptbase.o mptscsih.o mptsas.o
> obj-$(CONFIG_FUSION_LAN)	+= mptlan.o
> obj-m				+= mptctl.o
> obj-m                           += mptcfg.o
> obj-m                       +=mptstm.o

The above kbuild file snippet tells us that you are creating
a number of modules:
mptbase.ko mptscsih.ko mptsas.ko mptlan.ko mptctl.ko mtpcfg.ko and mptstm.ko
They are each build from a single .c file.

> mptbase-objs             := comfunc.o

Now you try to include confunc.o in every module.
To do so you need to tell kbuild that you are dealing with a module
based on composite .o files.
That would look like:
obj-$(CONFIG_FUSION_PCI) += mptbase-foo.o
mtpbase-foo-y := comfunc.o mptbase.o

This will result in a module named mtpbase-foo.ko which is hardly what
you try to achive. Likewise you will have duplicate symbols in the
modules due to comfunc.o being included more than once.

The only sane approce here is to compile comfunc.o as an independent
module and let the modutils pull in the comfunc (deservers a more
specific name) module as needed.

So what you need to do is simply:
obj-m += comfunc.o

And accept this is a module so all symbols that you needs must be properly
exported using EXPORT_SYMBOL*

	Sam

Makefile for linux modules

[x z]

Hi
   I have a makefile to make several driver modules:
obj-$(CONFIG_FUSION_SPI)	+= mptbase.o mptscsih.o
mptspi.o
obj-$(CONFIG_FUSION_FC)		+= mptbase.o mptscsih.o
mptfc.o
obj-m				+= mptbase.o mptscsih.o mptsas.o
obj-$(CONFIG_FUSION_LAN)	+= mptlan.o
obj-m				+= mptctl.o
obj-m                           += mptcfg.o
obj-m                       +=mptstm.o


this will compile all modules and the modules can be
installed successfully.

I need to have a comfunc.c file, which contains all
common functions, which could be used by these module
files.
I added the line below to the content just below
mptstm.o (I tried adding just above mptlan). 
mptbase-objs             := comfunc.o

All modules are compiled successfully. I can install
mptbase.ko. However, when I try to install mptctl.ko
(or other modules), I got errors like mptctl: Unknown
symbol mpt_register; mpt_deregister. These functions
are implemented in mptbase.c.

How do I fix this problem?

thanks
Robert


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Jean Tourrilhes]

On Fri, Sep 29, 2006 at 06:20:08PM -0700, Andrew Morton wrote:
> On Fri, 29 Sep 2006 20:01:54 -0400
> > 
> > % grep ioctl /tmp/foo2 | sort -u | more
> > ioctl(13, SIOCGIWESSID, 0xbfbcdb9c)     = 0
> > ioctl(13, SIOCGIWRANGE, 0xbfbcdbdc)     = 0
> > ioctl(13, SIOCGIWRATE, 0xbfbcdbbc)      = 0
> 
> Yes.  The main thing which those WE-21 patches do is to shorten the size of
> various buffers which are used in wireless ioctls.

	Ok, I've found it. Actually, I feel ashamed, as it is a fairly
classical buffer overflow, we put one extra char in a buffer. Now, I
don't understand why it did not blow up on my box ;-)
	New patch. I think it is right, but I would not mind Pavel to
have a look at it. On my box it does not make thing worse.
	Valdis : would you mind trying if this patch fix the problem
you are seeing with WE-21 ? If it fixes it, I'll send it to John...
	Have fun...

	Jean

P.S. : I'll audit the other wireless drivers for the same thing.

-------------------------------------------------

diff -u -p linux/drivers/net/wireless/orinoco.j1.c linux/drivers/net/wireless/orinoco.c
--- linux/drivers/net/wireless/orinoco.j1.c	2006-10-02 10:15:41.000000000 -0700
+++ linux/drivers/net/wireless/orinoco.c	2006-10-02 10:39:20.000000000 -0700
@@ -2456,6 +2456,7 @@ void free_orinocodev(struct net_device *
 /* Wireless extensions                                              */
 /********************************************************************/
 
+/* Return : < 0 -> error code ; >= 0 -> length */
 static int orinoco_hw_get_essid(struct orinoco_private *priv, int *active,
 				char buf[IW_ESSID_MAX_SIZE+1])
 {
@@ -2500,9 +2501,9 @@ static int orinoco_hw_get_essid(struct o
 	len = le16_to_cpu(essidbuf.len);
 	BUG_ON(len > IW_ESSID_MAX_SIZE);
 
-	memset(buf, 0, IW_ESSID_MAX_SIZE+1);
+	memset(buf, 0, IW_ESSID_MAX_SIZE);
 	memcpy(buf, p, len);
-	buf[len] = '\0';
+	err = len;
 
  fail_unlock:
 	orinoco_unlock(priv, &flags);
@@ -3026,17 +3027,18 @@ static int orinoco_ioctl_getessid(struct
 
 	if (netif_running(dev)) {
 		err = orinoco_hw_get_essid(priv, &active, essidbuf);
-		if (err)
+		if (err < 0)
 			return err;
+		erq->length = err;
 	} else {
 		if (orinoco_lock(priv, &flags) != 0)
 			return -EBUSY;
-		memcpy(essidbuf, priv->desired_essid, IW_ESSID_MAX_SIZE + 1);
+		memcpy(essidbuf, priv->desired_essid, IW_ESSID_MAX_SIZE);
+		erq->length = strlen(priv->desired_essid);
 		orinoco_unlock(priv, &flags);
 	}
 
 	erq->flags = 1;
-	erq->length = strlen(essidbuf);
 
 	return 0;
 }
@@ -3074,10 +3076,10 @@ static int orinoco_ioctl_getnick(struct 
 	if (orinoco_lock(priv, &flags) != 0)
 		return -EBUSY;
 
-	memcpy(nickbuf, priv->nick, IW_ESSID_MAX_SIZE+1);
+	memcpy(nickbuf, priv->nick, IW_ESSID_MAX_SIZE);
 	orinoco_unlock(priv, &flags);
 
-	nrq->length = strlen(nickbuf);
+	nrq->length = strlen(priv->nick);
 
 	return 0;
 }

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

On Mon, 02 Oct 2006 10:52:45 PDT, Jean Tourrilhes said:
> On Fri, Sep 29, 2006 at 06:20:08PM -0700, Andrew Morton wrote:
> > On Fri, 29 Sep 2006 20:01:54 -0400
> > > 
> > > % grep ioctl /tmp/foo2 | sort -u | more
> > > ioctl(13, SIOCGIWESSID, 0xbfbcdb9c)     = 0
> > > ioctl(13, SIOCGIWRANGE, 0xbfbcdbdc)     = 0
> > > ioctl(13, SIOCGIWRATE, 0xbfbcdbbc)      = 0
> > 
> > Yes.  The main thing which those WE-21 patches do is to shorten the size of
> > various buffers which are used in wireless ioctls.
> 
> 	Ok, I've found it. Actually, I feel ashamed, as it is a fairly
> classical buffer overflow, we put one extra char in a buffer. Now, I
> don't understand why it did not blow up on my box ;-)
> 	New patch. I think it is right, but I would not mind Pavel to
> have a look at it. On my box it does not make thing worse.
> 	Valdis : would you mind trying if this patch fix the problem
> you are seeing with WE-21 ? If it fixes it, I'll send it to John...

Been up and running with we-21 configured in, and gkrellm doing the monitoring
that gave it indigestion.  It was dying in 1-2 minutes, now been up for 30 mins
with no issues....

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Samuel Tardieu]

>>>>> "Jean" == Jean Tourrilhes <jt@hpl.hp.com> writes:

Jean> @@ -2500,9 +2501,9 @@ static int orinoco_hw_get_essid(struct o
Jean>  	len = le16_to_cpu(essidbuf.len);
Jean>  	BUG_ON(len > IW_ESSID_MAX_SIZE);
Jean>  
Jean> -	memset(buf, 0, IW_ESSID_MAX_SIZE+1);
Jean> +	memset(buf, 0, IW_ESSID_MAX_SIZE);
Jean>  	memcpy(buf, p, len);
Jean> -	buf[len] = '\0';
Jean> +	err = len;

Jean,

something bugs me here:

  - either buf is supposed to be a nul-terminated string, in which
    case if p is IW_ESSID_MAX_SIZE long there may be a bug (no '\0' at
    the end of buf)

  - either buf is not-supposed to be nul-terminated and the length
    value will always be used, in which case the memset() looks
    useless

I suggest that you revert the memset() to IW_ESSID_MAX_SIZE+1 so that
the last byte is cleared as well. Or am I missing something?

 Sam
-- 
Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Jean Tourrilhes]

On Tue, Oct 03, 2006 at 05:58:31PM +0200, Samuel Tardieu wrote:
> >>>>> "Jean" == Jean Tourrilhes <jt@hpl.hp.com> writes:
> 
> Jean> @@ -2500,9 +2501,9 @@ static int orinoco_hw_get_essid(struct o
> Jean>  	len = le16_to_cpu(essidbuf.len);
> Jean>  	BUG_ON(len > IW_ESSID_MAX_SIZE);
> Jean>  
> Jean> -	memset(buf, 0, IW_ESSID_MAX_SIZE+1);
> Jean> +	memset(buf, 0, IW_ESSID_MAX_SIZE);
> Jean>  	memcpy(buf, p, len);
> Jean> -	buf[len] = '\0';
> Jean> +	err = len;
> 
> Jean,
> 
> something bugs me here:
> 
>   - either buf is supposed to be a nul-terminated string, in which
>     case if p is IW_ESSID_MAX_SIZE long there may be a bug (no '\0' at
>     the end of buf)

	ESSID is supposed to be up to 32 char, so we need to full
buffer size.

>   - either buf is not-supposed to be nul-terminated and the length
>     value will always be used, in which case the memset() looks
>     useless

	Yes, it is entirely useless, but not incorrect. Note that the
code was not very efficient to start with, the last char of the string
was set to NUL twice.
	I don't really want to overstep my authority there, my goal
was to minimise the changes. Pavel will have to clean up my mess, so I
don't want change things too much.

> I suggest that you revert the memset() to IW_ESSID_MAX_SIZE+1 so that
> the last byte is cleared as well. Or am I missing something?

	No, that would bring back the slab/memory overflow we are
trying to get rid of.

>  Sam
> -- 
> Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/

	Strange, this name remind me someone. Must be a previous life ;-)

	A+

	Jean

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Samuel Tardieu]

On  3/10, Jean Tourrilhes wrote:

| > I suggest that you revert the memset() to IW_ESSID_MAX_SIZE+1 so that
| > the last byte is cleared as well. Or am I missing something?
| 
| No, that would bring back the slab/memory overflow we are
| trying to get rid of.

Then I am puzzled by the function declaration:

static int orinoco_hw_get_essid(struct orinoco_private *priv, int *active,
                                char buf[IW_ESSID_MAX_SIZE+1])

Do you mean that this function is called with a buf parameter which
doesn't have the expected size? (as far as the function declaration is
concerned) Shouldn't the declaration be changed to

static int orinoco_hw_get_essid(struct orinoco_private *priv, int *active,
                                char buf[IW_ESSID_MAX_SIZE])

then to reflect the reality? (it won't change the code but would be
clearer from a documentation point of view)

 Sam

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Jean Tourrilhes]

On Tue, Oct 03, 2006 at 06:45:35PM +0200, Samuel Tardieu wrote:
> On  3/10, Jean Tourrilhes wrote:
> 
> | > I suggest that you revert the memset() to IW_ESSID_MAX_SIZE+1 so that
> | > the last byte is cleared as well. Or am I missing something?
> | 
> | No, that would bring back the slab/memory overflow we are
> | trying to get rid of.
> 
> Then I am puzzled by the function declaration:
> 
> static int orinoco_hw_get_essid(struct orinoco_private *priv, int *active,
>                                 char buf[IW_ESSID_MAX_SIZE+1])
> 
> Do you mean that this function is called with a buf parameter which
> doesn't have the expected size? (as far as the function declaration is
> concerned) Shouldn't the declaration be changed to
> 
> static int orinoco_hw_get_essid(struct orinoco_private *priv, int *active,
>                                 char buf[IW_ESSID_MAX_SIZE])
> 
> then to reflect the reality? (it won't change the code but would be
> clearer from a documentation point of view)

	Yep, that one is a bug.
	Thanks !

>  Sam

	Jean

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Pavel Roskin]

Hello!

On Tue, 2006-10-03 at 09:34 -0700, Jean Tourrilhes wrote:
> 	I don't really want to overstep my authority there, my goal
> was to minimise the changes. Pavel will have to clean up my mess, so I
> don't want change things too much.

Sorry for a long delay.

I'm actually not very interested in the Wireless Extension interface of
the driver.  The less I touch that code, the better I feel.  I won't add
to the criticism for the latest changes; enough has been said.

Its fine with me that your are changing the orinoco driver to update
Wireless Extensions compatibility.

I'm trying to maintain a Subversion repository with the driver modified
to be compatible with a few latest kernels.  But it looks like it's an
uphill battle that I'm not going to win.

-- 
Regards,
Pavel Roskin

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

[Jean Tourrilhes]

On Thu, Oct 05, 2006 at 06:37:53PM -0400, Pavel Roskin wrote:
> Hello!
> 
> On Tue, 2006-10-03 at 09:34 -0700, Jean Tourrilhes wrote:
> > 	I don't really want to overstep my authority there, my goal
> > was to minimise the changes. Pavel will have to clean up my mess, so I
> > don't want change things too much.
> 
> Sorry for a long delay.

	That's ok, we all have a real life ;-)

> I'm actually not very interested in the Wireless Extension interface of
> the driver.  The less I touch that code, the better I feel.  I won't add
> to the criticism for the latest changes; enough has been said.
> 
> Its fine with me that your are changing the orinoco driver to update
> Wireless Extensions compatibility.
> 
> I'm trying to maintain a Subversion repository with the driver modified
> to be compatible with a few latest kernels.  But it looks like it's an
> uphill battle that I'm not going to win.

	I'll try to come up with a patch for you. It's not as bad as
it looks like. It will look like the patch for the external ipw
drivers I sent on the list.

> Pavel Roskin

	Have fun...

	Jean

Re: 2.6.18-mm2

[Andrew Morton]

On Sat, 30 Sep 2006 15:37:06 +0200
Tobias Diedrich <ranma@tdiedrich.de> wrote:

> Andrew Morton wrote:
> 
> > - More updates to the MSI code.  If your machine has Message Signalled
> >   Interrupts, please enable it and give it a try.
> 
> I'm happy to report, that with 2.6.18-mm2 suspend to disk works for
> me without additional patches, tested both with MSI interrupts
> disabled and enabled (forcedeth driver).

Thanks.

Which kernel version(s) didn't work?  -mm1?  Mainline?