lockup with parport_pc on 2.4.0-test10-pre1

2000-10-11 Thread John Cavan

I managed to follow, with a number of debug statements, a problem that
appears to be in parport_pc that causes the following lockup on a dual
P3 500 with modprobe:

NMI Watchdog detected LOCKUP on CPU0, registers:
CPU:0
EIP:0010:[]
EFLAGS: 0086
eax: 0301   ebx: 0216   ecx: 0001   edx: 000816a1
esi: 0301   edi: 000c   ebp: 00034a4e   esp: df91fe98
ds: 0018   es: 0018   ss: 0018
Process modprobe (pid: 79, stackpage=df91f000)
Stack: df8f3f20 0001 c0162cea 0301 df8f3f20  
df91ff0c 
   c0162ea1  df8f3f20 df8f3f20 0004 000a 0400
c0134492 
    0004 df91ff0c c196ea04 c18620e0 df9b385c 
1000 
Call Trace: [] [] [] []
[] [] [] 
   [] [] [] [] [] 
Code: 80 3d 64 4d 22 c0 00 f3 90 7e f5 e9 e6 31 f8 ff 80 3d ac f6 
console shuts up ...

I don't if this is specifically a problem in the module or with modprobe
(2.3.17), but it doesn't happen with any other module. Unfortunately
parport_pc.c was as far as I traced before my work life sucked me back
in.

If more information is needed, please tell me what you need and I'll try
to provide it.

John
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: lockup with parport_pc on 2.4.0-test10-pre1

2000-10-14 Thread Tim Waugh

On Wed, Oct 11, 2000 at 11:01:20PM -0400, John Cavan wrote:

> I don't if this is specifically a problem in the module or with modprobe
> (2.3.17), but it doesn't happen with any other module. Unfortunately
> parport_pc.c was as far as I traced before my work life sucked me back
> in.

I think it's a parport problem.  I haven't had time to look at this
yet, sorry.

Tim.
*/

 PGP signature


Re: lockup with parport_pc on 2.4.0-test10-pre1

2000-10-14 Thread John Cavan

Tim Waugh wrote:
> 
> On Wed, Oct 11, 2000 at 11:01:20PM -0400, John Cavan wrote:
> 
> > I don't if this is specifically a problem in the module or with modprobe
> > (2.3.17), but it doesn't happen with any other module. Unfortunately
> > parport_pc.c was as far as I traced before my work life sucked me back
> > in.
> 
> I think it's a parport problem.  I haven't had time to look at this
> yet, sorry.

Actually, I got further. It's the Zip ppa.o driver that's causing it.
I'll keep digging.

John
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: lockup with parport_pc on 2.4.0-test10-pre1]

2000-10-14 Thread James M

Kernel test10-pre2, Dual Xeon PII(400 mhz), Mandrake 7.1, microde
updates enabled

Mounting my zipdrive(IMM) will result in something like this:
Sysrq does not work, machine is completely dead after 20-40 seconds.The
usual progession is CPU's lockup, modprobe dies, kflushed and syslogd
follow shortly afterwards.

NMI Watchdog detected LOCKUP on CPU0, registers:
CPU:0
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00200086
eax: 2101   ebx: 00200202   ecx: 0001   edx: 001f8f79
esi: 2101   edi: 0084   ebp: 00089e60   esp: c60e7e98
ds: 0018   es: 0018   ss: 0018
Process modprobe (pid: 1207, stackpage=c60e7000)
Stack: c7eb4cc0 0001 c0163bfa 2101 c7eb4cc0  
c60e7f0c
   c0163db1  c7eb4cc0 c7eb4cc0 0001 000c 1000
c01342a2
    0001 c60e7f0c c7fa5a64 c1197a7c c7c7da1c 
1000
Call Trace: [] [] [] []
[] [>EIP; c01d7243<=
Trace; c0163bfa 
Trace; c0163db1 
Trace; c01342a2 
Trace; c0153773 
Trace; c01530a8 
Code;  c01d7243 
 <_EIP>:
Code;  c01d7243<=
   0:   80 3d c4 67 21 c0 00  cmpb   $0x0,0xc02167c4   <=
Code;  c01d724a 
   7:   f3 90 repz nop 
Code;  c01d724c 
   9:   7e f5 jle0 <_EIP>
Code;  c01d724e 
   b:   e9 76 bd f8 ffjmpfff8bd86 <_EIP+0xfff8bd86>
c0162fc9 
Code;  c01d7253 
  10:   80 3d 34 2a 00 00 00  cmpb   $0x0,0x2a34

NMI Watchdog detected LOCKUP on CPU0, registers:
CPU:0
EIP:0010:[]
EFLAGS: 00200086
eax: 2105   ebx: 00200206   ecx: 0005   edx: 00bc1f49
esi: 2105   edi: 0084   ebp: 0010   esp: c1263f7c
ds: 0018   es: 0018   ss: 0018
Process kflushd (pid: 4, stackpage=c1263000)
Stack: c4f042c0 0001 c0163bfa 2105 c4f042c0  0001
c1263fd8
   c0163db1 0001 c4f042c0 0029 c7a9b380 0001 c1262000
c013560a
Warning (Oops_read): Code line not seen, dumping what data is available

>>EIP; c01d7243<=

If anyone has a patch to test let me knowI'll try anything once,
twice if I like it...:=)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/