linux-kernel - Re: 2.6.23-rc1-mm1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <64bb37e0707261054j25691afnb1bbf3484af855f3@mail.gmail.com>
Date:	Thu, 26 Jul 2007 19:54:13 +0200
From:	"Torsten Kaiser" <just.for.lkml@...glemail.com>
To:	"Andrew Morton" <akpm@...ux-foundation.org>
Cc:	"Len Brown" <lenb@...nel.org>, "Cedric Le Goater" <clg@...ibm.com>,
	linux-kernel@...r.kernel.org, "Shaohua Li" <shaohua.li@...el.com>,
	linux-mm@...ck.org
Subject: Re: 2.6.23-rc1-mm1

On 7/26/07, Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Wed, 25 Jul 2007 23:52:47 +0200 "Torsten Kaiser" <just.for.lkml@...glemail.com> wrote:
>
> > On 7/25/07, Andrew Morton <akpm@...ux-foundation.org> wrote:
> > > On Wed, 25 Jul 2007 22:22:41 +0200
> > > "Torsten Kaiser" <just.for.lkml@...glemail.com> wrote:
> > > > [    0.000000] early_node_map[4] active PFN ranges
> > > > [    0.000000]     0:        0 ->      159
> > > > [    0.000000]     0:      256 ->   524288
> > > > [    0.000000]     1:   524288 ->   917488
> > > > [    0.000000]     1:  1048576 ->  1179648
> > > > PANIC: early exception rip ffffffff807caac5 error 2 cr2 ffffe20003000010
> > > > [    0.000000]
> > > > [    0.000000] Call Trace:
> > > >
> > > > ... but no Call Trace follows.
> > > >
> > > > (gdb) list *0xffffffff807caac5
> > > > 0xffffffff807caac5 is in memmap_init_zone (include/linux/list.h:32).
> > > > 27      #define LIST_HEAD(name) \
> > > > 28              struct list_head name = LIST_HEAD_INIT(name)
> > > > 29
> > > > 30      static inline void INIT_LIST_HEAD(struct list_head *list)
> > > > 31      {
> > > > 32              list->next = list;
> > > > 33              list->prev = list;
> > > > 34      }
> > > > 35
> > > > 36      /*
> > > >
> > > > Torsten
> > >
> > > Quite a few people have been playing in that area.  Can you please send the
> > > .config?
> >
> > #
> > # Automatically generated make config: don't edit
> > # Linux kernel version: 2.6.23-rc1-mm1
> > # Wed Jul 25 21:18:15 2007
>
> It boots OK on my test box, bummer.  Please test -mm2 and if it also fails,

I will test it...

> it'd be great if you could run through
> http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt - it
> doesn't take very long.

I did two major changes when upgrading from 22-rc6-mm1 to 23-rc1-mm1.
I switched from DISCONTIGMEM to SPARSEMEM and from SLAB to SLUB.

The other combinations:
SPARSEMEM+SLAB:
[    0.000000] early_node_map[4] active PFN ranges
[    0.000000]     0:        0 ->      159
[    0.000000]     0:      256 ->   524288
[    0.000000]     1:   524288 ->   917488
[    0.000000]     1:  1048576 ->  1179648
PANIC: early exception rip ffffffff807c4ac5 error 2 cr2 ffffe20003000010
[    0.000000]
[    0.000000] Call Trace:
DISCONTIGMEM+SLUB:
[   39.833272] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[   40.016659] Kernel panic - not syncing: IO-APIC + timer doesn't
work! Try using the 'noapic' kernel parameter
DISCONTIGMEM+SLAB:
Boots until it can't find / because I didn't append the correct initrd
It also hit the MP-BIOS bug, but was not bothered by it:
[   36.696965] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[   36.880537] Using local APIC timer interrupts.
[   36.932215] result 12500283
[   36.940581] Detected 12.500 MHz APIC timer.

So I think, I will postpone SPARSEMEM until -mm2, as there are seem to
be some problems in that area (Re: 2.6.23-rc1-mm1 sparsemem_vmemamp
fix)

But maybee I will get SLUB to work. ;)

Torsten
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/