Bug#462424: further oops info (2.6.22-3-686)

2008-01-30 Thread Bastian Blank
On Wed, Jan 30, 2008 at 12:47:12AM +0100, Michael Prokop wrote: > * Bastian Blank <[EMAIL PROTECTED]> [20080129 23:47]: > > But behaves like a rootkit, or did they kill the syscall table > > modifications? > Nope, you're right - sys_call_table seems to be still > around. *hmpf* And the code is so

Bug#462424: further oops info (2.6.22-3-686)

2008-01-29 Thread Brendan Cully
On Tuesday, 29 January 2008 at 19:05, maximilian attems wrote: > On Sat, 26 Jan 2008, Brendan Cully wrote: > > > Rolling back to the previous kernel, I got a very similar oops but with a > > little more > > detail in kern.log: > > > > Jan 26 03:35:29 peyresourde kernel: BUG: unable to handle ker

Bug#462424: further oops info (2.6.22-3-686)

2008-01-29 Thread Michael Prokop
* Bastian Blank <[EMAIL PROTECTED]> [20080129 23:47]: > On Tue, Jan 29, 2008 at 11:36:18PM +0100, Michael Prokop wrote: > > That's openafs, which is open source but just lacking MODULE_LICENSE > > what's tainting the kernel. Irrelevant IMHO. > But behaves like a rootkit, or did they kill the sysc

Bug#462424: further oops info (2.6.22-3-686)

2008-01-29 Thread Bastian Blank
On Tue, Jan 29, 2008 at 11:36:18PM +0100, Michael Prokop wrote: > That's openafs, which is open source but just lacking MODULE_LICENSE > what's tainting the kernel. Irrelevant IMHO. But behaves like a rootkit, or did they kill the syscall table modifications? Bastian -- Landru! Guide us!

Bug#462424: further oops info (2.6.22-3-686)

2008-01-29 Thread Michael Prokop
* maximilian attems <[EMAIL PROTECTED]> wrote: > On Sat, 26 Jan 2008, Brendan Cully wrote: [...] > your kernel is tainted can you reproduce aboves trouble > without openafs? That's openafs, which is open source but just lacking MODULE_LICENSE what's tainting the kernel. Irrelevant IMHO. Brendan

Bug#462424: further oops info (2.6.22-3-686)

2008-01-29 Thread maximilian attems
On Sat, 26 Jan 2008, Brendan Cully wrote: > Rolling back to the previous kernel, I got a very similar oops but with a > little more > detail in kern.log: > > Jan 26 03:35:29 peyresourde kernel: BUG: unable to handle kernel paging > request at virtual address ffef > Jan 26 03:35:29 peyresour

Bug#462424: further oops info (2.6.22-3-686)

2008-01-26 Thread Brendan Cully
Rolling back to the previous kernel, I got a very similar oops but with a little more detail in kern.log: Jan 26 03:35:29 peyresourde kernel: BUG: unable to handle kernel paging request at virtual address ffef Jan 26 03:35:29 peyresourde kernel: printing eip: Jan 26 03:35:29 peyresourde ker