I got a few more oopses like the one in the original message (see below)
and one with a different call trace but that happened while creating a
snapshot too.
After that I rebuilt the kernel with SLAB instead of SLUB. The system
is running fine for a week now.
BUG: unable to handle kernel NULL p
Arjan van de Ven wrote:
> On Sun, 2007-08-05 at 21:03 +0200, Juergen Kreileder wrote:
>> I've upgraded devmapper to 1.02.20 and lvm2 to 2.02.26. Didn't help much,
>> I just got a the same BUG again:
>>
>> kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
>> BUG: unable to handl
On Sun, 2007-08-05 at 21:03 +0200, Juergen Kreileder wrote:
> I've upgraded devmapper to 1.02.20 and lvm2 to 2.02.26. Didn't help much,
> I just got a the same BUG again:
>
> kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
> BUG: unable to handle kernel paging request at vir
I've upgraded devmapper to 1.02.20 and lvm2 to 2.02.26. Didn't help much,
I just got a the same BUG again:
kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
BUG: unable to handle kernel paging request at virtual address f492c1f8
printing eip:
f492c1f8
*pdpt = 100
Hi,
I got the appended BUG from a 32-bit 2.6.22.1 kernel (with exec-shield
patch and PAE enabled) on an Athlon64 with dmsetup 1.02.03 and lvm2
v2.02.02.
(Note, the message comes from the vanilla kernel, not from the
exec-shiled patch.)
I wasn't able to reproduce the problem so far. The machine c
5 matches
Mail list logo