below is the oops of the other guy for your reference.
----------------------------------------------------------------------------
Hi, guys!
This piss me off! I don't know how can I do!
2.2.[6789] all give me an oops of this kind:
Options used: -V (default)
-o /lib/modules/2.2.9 (specified)
-k /proc/ksyms (default)
-l /proc/modules (default)
-m /boot/System.map-2.2.9 (specified)
-c 1 (default)
Unable to handle kernel NULL pointer dereference at virtual address 00000070
current->tss.cr3=00101000, %cr3=00101000
OOPS: 0002
CPU: 1
EIP: 0010:[<cc8511cd>]
EFLAGS: 00010282
eax: 00000070 ebx: 00000047 ecx: 00000007 edx: 00000000
esi: c2983a46 edi: 00000013 ebp: c2983800 esp: c009df04
ds: 0018 es: 0018 ss: 0018
Process swapper (pid:0, process nr. 1, stackpage=c009d001
Stack: c843c000 00000000 00000000 c8909d80 c2983b2b 00000013 ffff472a
cc850f0c c2983800 22983800 c843c000 00000001 c009df7c cc850623 c2983800
cc833d84 c843c000 cc92c15a c843c000 00000000 c0224c74 cc82c0c6 cc833d84
00000001
Call trace: [<cc850f0c>] [<cc850b23>] [<cc833d84>] [<cc82c15a>] [<cc82c0c6>]
[<cc833d84>] [<c011a93d>] [<c010b749>] [<c0109260>] [<c01078c7>] [<c0106000>]
[<c0100018>] [<c0107b2e>]
Code: f0 ff 4a 70 0f 94 c0 84 c0 74 09 52 e8 f6 b1 8f f3 83 c4 04
>>EIP: cc8511cd <ppp_tty_receive+5cd/660>
Trace: cc850f0c <ppp_tty_receive+30c/660>
Trace: cc850b23 <ppp_async_encode+27b/288>
Trace: cc833d84 <cleanup_module+f3c/1a204>
Trace: cc82c15a <do_softint+8a/c0>
Trace: cc82c0c6 <do_cyclades_bh+56/60>
Trace: cc833d84 <cleanup_module+f3c/1a204>
Trace: c0100018 <startup_32+18/a4>
Code: cc8511cd <ppp_tty_receive+5cd/660> 00000000 <_EIP>: <===
Code: cc8511cd <ppp_tty_receive+5cd/660> 0: f0 ff 4a 70 lock decl 0x70(%edx) <===
Code: cc8511d1 <ppp_tty_receive+5d1/660> 4: 0f 94 c0 sete %al
Code: cc8511d4 <ppp_tty_receive+5d4/660> 7: 84 c0 testb %al,%al
Code: cc8511d6 <ppp_tty_receive+5d6/660> 9: 74 09 je cc8511e1 <ppp_tty_receive+5e1/660>
Code: cc8511d8 <ppp_tty_receive+5d8/660> b: 52 pushl %edx
Code: cc8511d9 <ppp_tty_receive+5d9/660> c: e8 f6 b1 8f f3 call c014c3d4 <__kfree_skb+0/ac>
Code: cc8511de <ppp_tty_receive+5de/660> 11: 83 c4 04 addl $0x4,%esp
Aiee, kiling interrupt handler.
Kernel panic: attempted to kill the idle task!
733 warnings issued. Results may not be reliable.
I have a:
- dual Pentium II AGP/PCI/333 MHz
- mo Intel i82440LX
- 196 MB Ram
- 1 x AIC-7880
- 2 x 3C905b
- 1 x Cyclom YeP
- 1 ESS1869 Sound Card
Thanks!
************************************
Catalin(ux) BOIE
System Administrator at Deuroconsult
catab@deuroconsult.ro
http://www2.deuroconsult.ro/~catab
----------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
On Tue, 25 May 1999, Tim Waugh wrote:
> On Tue, 25 May 1999, Rodel T. Viado wrote:
>
> > Tim
> > Attached herewith are the files you requested compiles from a
> > pristine 2.2.9+Tim_Waugh_cyclades_patch
>
> Okay. What's going on is that info->close_wait is non-zero and 'active',
> but (*info->close_wait)->task is 0x1! __wake_up then trips over it when
> we say 'wake_up_interruptible(&info->close_wait)'.
>
> I can't see any way that can ever happen. (*info->close_wait)->task must
> always be 8k-aligned, since it's always set to current whenever it's set.
>
> Tim.
> */
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/