On Fri, May 18, 2007 at 09:16:45PM +0200, Luca Tettamanti wrote:
>
> Output from serial console is enlightening (sort of...):
>
> Loading IPsec SA/SP database from /etc/ipsec-tools.conf: BUG: unable to
> handle kernel paging request at virtual address 6b6b6ceb printing eip:
> b0141aef
> [oops]
T
Luca Tettamanti wrote:
> Il Fri, May 18, 2007 at 11:14:55PM +1000, Herbert Xu ha scritto:
>> On Fri, May 18, 2007 at 02:09:54PM +0200, Luca wrote:
>>> Well, pretty sure. The OOPS says 2.6.22-rc1-libata-g705962cc-dirty,
>>> git agrees and I've done a full rebuild. The .config is generated
>>> using
Il Fri, May 18, 2007 at 11:14:55PM +1000, Herbert Xu ha scritto:
> On Fri, May 18, 2007 at 02:09:54PM +0200, Luca wrote:
> >
> > Well, pretty sure. The OOPS says 2.6.22-rc1-libata-g705962cc-dirty,
> > git agrees and I've done a full rebuild. The .config is generated
> > using 'make oldconfig' usi
On Fri, May 18, 2007 at 02:09:54PM +0200, Luca wrote:
>
> Well, pretty sure. The OOPS says 2.6.22-rc1-libata-g705962cc-dirty,
> git agrees and I've done a full rebuild. The .config is generated
> using 'make oldconfig' using the 2.6.21 as baseline, maybe ALGAPI is
> coming from there?
Sorry, my m
On 5/18/07, Herbert Xu <[EMAIL PROTECTED]> wrote:
On Tue, May 15, 2007 at 08:52:12PM +0200, Luca Tettamanti wrote:
>
> CONFIG_CRYPTO_ALGAPI=m
Are you sure you're actually running 2.6.22-rc1? Due to a bug
in the padlock patch present in 2.6.22-rc1 it shouldn't be
possible to select ALGAPI as a mo
On Tue, May 15, 2007 at 08:52:12PM +0200, Luca Tettamanti wrote:
>
> CONFIG_CRYPTO_ALGAPI=m
Are you sure you're actually running 2.6.22-rc1? Due to a bug
in the padlock patch present in 2.6.22-rc1 it shouldn't be
possible to select ALGAPI as a module.
Cheers,
--
Visit Openswan at http://www.open
On 5/17/07, Luca Tettamanti <[EMAIL PROTECTED]> wrote:
Il Tue, May 15, 2007 at 11:43:44AM +1000, Herbert Xu ha scritto:
> On Mon, May 14, 2007 at 07:38:23PM +0200, Luca Tettamanti wrote:
> > I'm running git 705962cc (which is a commit after -rc1) and I still see
> > the OOPS on boot. The patch ab
Il Tue, May 15, 2007 at 11:43:44AM +1000, Herbert Xu ha scritto:
> On Mon, May 14, 2007 at 07:38:23PM +0200, Luca Tettamanti wrote:
> > I'm running git 705962cc (which is a commit after -rc1) and I still see
> > the OOPS on boot. The patch above is already applied though. Note that
> > I'm using t
Il Tue, May 15, 2007 at 11:43:44AM +1000, Herbert Xu ha scritto:
> On Mon, May 14, 2007 at 07:38:23PM +0200, Luca Tettamanti wrote:
> > I'm running git 705962cc (which is a commit after -rc1) and I still see
> > the OOPS on boot. The patch above is already applied though. Note that
> > I'm using t
On Mon, May 14, 2007 at 07:38:23PM +0200, Luca Tettamanti wrote:
> I'm running git 705962cc (which is a commit after -rc1) and I still see
> the OOPS on boot. The patch above is already applied though. Note that
> I'm using the SLAB allocator:
>
> CONFIG_SLAB=y
> # CONFIG_SLUB is not set
> # CONFI
Kevin Winchester <[EMAIL PROTECTED]> ha scritto:
> On 5/9/07, Herbert Xu <[EMAIL PROTECTED]> wrote:
>> On Tue, May 08, 2007 at 09:58:09PM -0300, Kevin Winchester wrote:
>> >
>> > Not having any idea what I'm doing, I looked at cryptomgr_probe and
>> > cryptomgr_notify, and can't seem to see much, e
On 5/9/07, Herbert Xu <[EMAIL PROTECTED]> wrote:
On Tue, May 08, 2007 at 09:58:09PM -0300, Kevin Winchester wrote:
>
> Not having any idea what I'm doing, I looked at cryptomgr_probe and
> cryptomgr_notify, and can't seem to see much, except for the following
> odd lines.
>
> From cryptomgr_sched
On Tue, May 08, 2007 at 09:58:09PM -0300, Kevin Winchester wrote:
>
> Not having any idea what I'm doing, I looked at cryptomgr_probe and
> cryptomgr_notify, and can't seem to see much, except for the following
> odd lines.
>
> From cryptomgr_schedule_probe, which is almost certainly inlined int
Christoph Lameter wrote:
On Tue, 8 May 2007, Kevin Winchester wrote:
Here's the dmesg of the slub_debug run, I'll try the patch next:
Ok someone wrote to an object after it was freed. Not slubs problem.
[1.367129] Object 0x810001bdecd0: 80 b7 b1 01 00 81 ff ff 6b 6b
On Tue, 8 May 2007, Kevin Winchester wrote:
> [1.376783] [] kernel_init+0xc4/0x2a0
> [1.376857] [] __switch_to+0x2a/0x2d0
> [1.376932] [] child_rip+0xa/0x12
> [1.377006] [] kernel_init+0x0/0x2a0
> [1.377080] [] child_rip+0x0/0x12
> [1.377151]
> [1.377221] @@@ SLUB
On Tue, 8 May 2007, Kevin Winchester wrote:
> Here's the dmesg of the slub_debug run, I'll try the patch next:
Ok someone wrote to an object after it was freed. Not slubs problem.
> [1.367129] Object 0x810001bdecd0: 80 b7 b1 01 00 81 ff ff 6b 6b
> 6b 6b 6b 6b 6b 6b .·±...
T
Christoph Lameter wrote:
On Tue, 8 May 2007, Kevin Winchester wrote:
x86_64 UP Athlon64 I get a crash on boot using SLUB. Switching to SLAB makes
it go away. I don't have a serial console, so the best I have is a digital
photo of as many lines as my VGA console was able to get (60 or so).
It seems that a uevent notification fails.
Does this patch fix it?
---
mm/slub.c |1 -
1 file changed, 1 deletion(-)
Index: linux-2.6/mm/slub.c
===
--- linux-2.6.orig/mm/slub.c2007-05-08 16:06:54.0 -0700
+++ linux-2
On Tue, 8 May 2007, Kevin Winchester wrote:
> x86_64 UP Athlon64 I get a crash on boot using SLUB. Switching to SLAB makes
> it go away. I don't have a serial console, so the best I have is a digital
> photo of as many lines as my VGA console was able to get (60 or so). Is there
> a better way
19 matches
Mail list logo
