Re: Oops with 2.6.15

Re: Oops with 2.6.15

[Lee Revell]

On Fri, 2006-01-06 at 00:10 +0100, Jacek Luczak wrote:
> Jan  5 19:25:04 slawek kernel: EIP:    0060:[<c0138603>]    Tainted:
> P 
>      VLI 

It's impossible to debug this unless you can reproduce it with a clean
kernel.  If you can't then it's likely that the binary kernel module is
the problem.

Lee

Oops with 2.6.15

[Jacek Luczak]

HI all

I receive this Oops (see below) with kernels from 2.6.15-rc5 to 2.6.15 
(I haven't using earlier versions of 2.6.15-rc). I'm using sk98lin 
driver (version 8.28.1.3) from Syskonnect and ndiswrapper-1.7. Is this 
error caused by sk98lin driver?

--------
CPU: Intel Pentium4 3GHz HT
GCC: 3.4.5
Binutils: 2.16.1
--------

Regards

	Jacek Luczak

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

Jan  5 19:25:04 slawek kernel: Unable to handle kernel NULL pointer 
dereference at virtual address 00000003
Jan  5 19:25:04 slawek kernel:  printing eip:
Jan  5 19:25:04 slawek kernel: c0138603
Jan  5 19:25:04 slawek kernel: *pde = 00000000
Jan  5 19:25:04 slawek kernel: Oops: 0002 [#1]
Jan  5 19:25:04 slawek kernel: SMP
Jan  5 19:25:04 slawek kernel: Modules linked in: sk98lin ndiswrapper 
usbhid uhci_hcd i915
Jan  5 19:25:04 slawek kernel: CPU:    0
Jan  5 19:25:04 slawek kernel: EIP:    0060:[<c0138603>]    Tainted: P 
     VLI
Jan  5 19:25:05 slawek kernel: EFLAGS: 00010086   (2.6.15)
Jan  5 19:25:05 slawek kernel: EIP is at free_block+0x45/0xd1
Jan  5 19:25:05 slawek kernel: eax: ffffffff   ebx: df0388c0   ecx: 
de9fbbc0   edx: 00000000
Jan  5 19:25:05 slawek kernel: esi: df7ad340   edi: 00000005   ebp: 
df7af600   esp: df731ef0
Jan  5 19:25:05 slawek kernel: ds: 007b   es: 007b   ss: 0068
Jan  5 19:25:05 slawek kernel: Process events/0 (pid: 6, 
threadinfo=df730000 task=df70ea30)
Jan  5 19:25:05 slawek kernel: Stack: df7ad350 00000002 deabd800 
df7aa194 0000000b df7aa180 00000000 c0138e15
Jan  5 19:25:05 slawek kernel:        df7af600 df7aa194 0000000b 
00000000 df7af600 df7ad340 df7af600 df7af654
Jan  5 19:25:05 slawek kernel:        00000003 c0138ea9 df7af600 
df7aa180 00000000 00000000 c146e418 c13f71a0
Jan  5 19:25:05 slawek kernel: Call Trace:
Jan  5 19:25:05 slawek kernel:  [<c0138e15>] drain_array_locked+0x6a/0x95
Jan  5 19:25:05 slawek kernel:  [<c0138ea9>] cache_reap+0x69/0x155
Jan  5 19:25:05 slawek kernel:  [<c012533e>] worker_thread+0x170/0x1de
Jan  5 19:25:05 slawek kernel:  [<c0138e40>] cache_reap+0x0/0x155
Jan  5 19:25:05 slawek kernel:  [<c01148e2>] default_wake_function+0x0/0x12
Jan  5 19:25:05 slawek kernel:  [<c01148e2>] default_wake_function+0x0/0x12
Jan  5 19:25:05 slawek kernel:  [<c01251ce>] worker_thread+0x0/0x1de
Jan  5 19:25:05 slawek kernel:  [<c01288df>] kthread+0x7c/0xa6
Jan  5 19:25:05 slawek kernel:  [<c0128863>] kthread+0x0/0xa6
Jan  5 19:25:05 slawek kernel:  [<c0100eb5>] kernel_thread_helper+0x5/0xb
Jan  5 19:25:05 slawek kernel: Code: 24 8b 54 24 2c 8b 04 b8 89 44 24 08 
05 00 00 00 40 c1 e8 0c 8b 74 95 18 31 d2 c1 e0 05 03 05 d0 e4 35 c0 8b 
58 1c 8b 03 8b 4b 04 <89> 48 04 89 01 c7 43 04 00 02 20 00 c7 03 00 01 
10 00 8b 43 0c

Re: Oops with 2.6.15

[Jesper Juhl]

On 1/6/06, Jacek Luczak <difrost@pin.if.uz.zgora.pl> wrote:
> HI all
>
> I receive this Oops (see below) with kernels from 2.6.15-rc5 to 2.6.15
> (I haven't using earlier versions of 2.6.15-rc). I'm using sk98lin
> driver (version 8.28.1.3) from Syskonnect and ndiswrapper-1.7. Is this
> error caused by sk98lin driver?
>
It might be.
As long as you are running a tainted kernel, getting people to look
seriously at an oops is going to be hard - no way to debug the
binary-only code that tainted the kernel, so it's pretty impossible to
know what's going on.

[snip]
> Jan  5 19:25:04 slawek kernel: Modules linked in: sk98lin ndiswrapper
> usbhid uhci_hcd i915
> Jan  5 19:25:04 slawek kernel: CPU:    0
> Jan  5 19:25:04 slawek kernel: EIP:    0060:[<c0138603>]    Tainted: P

Try and reproduce with a non-tainted kernel.

--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

Re: Oops with 2.6.15

[Jacek Luczak]

Jesper Juhl napisał(a):
> On 1/6/06, Jacek Luczak <difrost@pin.if.uz.zgora.pl> wrote:
> 
>>HI all
>>
>>I receive this Oops (see below) with kernels from 2.6.15-rc5 to 2.6.15
>>(I haven't using earlier versions of 2.6.15-rc). I'm using sk98lin
>>driver (version 8.28.1.3) from Syskonnect and ndiswrapper-1.7. Is this
>>error caused by sk98lin driver?
>>
> 
> It might be.
> As long as you are running a tainted kernel, getting people to look
> seriously at an oops is going to be hard - no way to debug the
> binary-only code that tainted the kernel, so it's pretty impossible to
> know what's going on.
> 
> [snip]
> 
>>Jan  5 19:25:04 slawek kernel: Modules linked in: sk98lin ndiswrapper
>>usbhid uhci_hcd i915
>>Jan  5 19:25:04 slawek kernel: CPU:    0
>>Jan  5 19:25:04 slawek kernel: EIP:    0060:[<c0138603>]    Tainted: P
> 
> 
> Try and reproduce with a non-tainted kernel.

I will try and send more info.

Big Thank
	J. L.

Re: Oops with 2.6.15

[Jacek Luczak]

Jesper Juhl napisał(a):

> 
> Try and reproduce with a non-tainted kernel.
> 

Non-tained kernel works great. There is no oops with that. The real 
problem is with ndiswrapper + sk98lin conflict. I will try to find 
solution and fix this conflict.

Thank you for your reply.

	J. L.

Re: Oops with 2.6.15

[Bill Davidsen]

Jacek Luczak wrote:
> Jesper Juhl napisał(a):
> 
>>
>> Try and reproduce with a non-tainted kernel.
>>
> 
> Non-tained kernel works great. There is no oops with that. The real 
> problem is with ndiswrapper + sk98lin conflict. I will try to find 
> solution and fix this conflict.

Are you running 4k stacks? I wouldn't expect ndiswrapper to works at all 
in that case, but...

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

Re: Oops with 2.6.15

[Jacek Luczak]

Bill Davidsen napisał(a):
> Jacek Luczak wrote:
> 
>> Jesper Juhl napisał(a):
>>
>>>
>>> Try and reproduce with a non-tainted kernel.
>>>
>>
>> Non-tained kernel works great. There is no oops with that. The real 
>> problem is with ndiswrapper + sk98lin conflict. I will try to find 
>> solution and fix this conflict.
> 
> 
> Are you running 4k stacks? I wouldn't expect ndiswrapper to works at all 
> in that case, but...
> 

No! I'm using 8K stacks.