Re: arcnet/com90xx still breaks 2.1.93

Christoph Lorenz (ChLorenz@csi.com)
17 Apr 1998 07:56:07 +0200


Hi,

I've finally made it - here's the ksymoops output for the arcnet Oops,
this time in 2.1.96:

Using `Oops.map' to map addresses to symbols.

>>EIP: c1819ef6 <arcnet_interrupt+f6/160>
Trace: c0107f68 <this_must_match_init_task+1f68/2000>
Trace: c010aa61 <handle_IRQ_event+31/60>
Trace: c1820854 <thiscard>
Trace: c0107f69 <this_must_match_init_task+1f69/2000>
Trace: c0106000 <init_task_union>
Trace: c0107f60 <this_must_match_init_task+1f60/2000>
Trace: c010ac02 <do_8259A_IRQ+72/d0>
Trace: c0107f68 <this_must_match_init_task+1f68/2000>
Trace: c0107f60 <this_must_match_init_task+1f60/2000>
Trace: c0118529 <do_bottom_half+49/70>
Trace: c010ac80 <do_IRQ+20/40>
Trace: c0107f68 <this_must_match_init_task+1f68/2000>
Trace: c0109b20 <ret_from_intr>
Trace: c0106000 <init_task_union>
Trace: c0106000 <init_task_union>
Trace: c010831c <sys_idle+6c/c0>
Trace: c0106000 <init_task_union>
Trace: c0107fe4 <this_must_match_init_task+1fe4/2000>
Trace: c0109a38 <system_call+38/40>
Trace: c01080a0 <init>
Trace: c0107fe4 <this_must_match_init_task+1fe4/2000>
Trace: c0106000 <init_task_union>
Trace: c0108087 <cpu_idle+7/20>
Trace: c010025b <L6>
Code: c1819ef6 <arcnet_interrupt+f6/160>
Code: c1819ef6 <arcnet_interrupt+f6/160> c6 40 1d 01 movb $0x1,0x1d(%eax)
Code: c1819efa <arcnet_interrupt+fa/160> 8b 83 dc 08 00 movl 0x8dc(%ebx),%eax
Code: c1819f06 <arcnet_interrupt+106/160> c6 40 1d 01 movb $0x1,0x1d(%eax)
Code: c1819f0a <arcnet_interrupt+10a/160> 55 pushl %ebp
Code: c1819f0b <arcnet_interrupt+10b/160> 8b 83 b8 08 00 movl 0x8b8(%ebx),%eax
Code: c1819f17 <arcnet_interrupt+117/160> 90 nop
Code: c1819f18 <arcnet_interrupt+118/160> 90 nop
Code: c1819f19 <arcnet_interrupt+119/160> 90 nop

I must admit, that I cannot get much information out of this trace,
but I hope, it helps you.

If not, I can provide you

- the oops message (which I copied from the screen - manually)
- System.map
- arcnet.map (generated from insmod -m arcnet)
- com90xx.map (generated from insmod -m com90xx.map)

By the way - the last mail, where we were talking about the com90io driver,
I mixed up things. Of course, I meant the com90xx driver. The com90io
driver is not working for my card (as far as I remember, I get sth. like
"device busy" when I insert the kernel module).

Ciao
Christoph

-- 
** http://ourworld.compuserve.com/homepages/ChLorenz/ ** ChLorenz@csi.com **
 ** No Spam ! ** No Adverts ! ** No Junk-Mails ! ** No unwanted Mails ! **

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu