Re: Question about use of PMAD-AA ethernet adapter on Decstation

[Len Sorensen <lsorense@opengraphics.com>]

On Tue, Oct 07, 2003 at 10:24:22AM -0400, Len Sorensen wrote:
> Wel the code as it is in the pmadaa.c driver must be working now, since
> the card is now working for me in a 5000/133, and the onboard is working
> too at the same time.  It helped once I put the card IN the machine I
> was playing with. :)

Well I have had it running a few hours and then got this while doing
ping 192.168.8.255 from the decstation:

Not starting NFS kernel daemon: No exports.
Starting OpenBSD Secure Shell server: sshd.
Starting NFS common utilities: statd.
Starting deferred execution scheduler: atd.
Starting periodic command scheduler: cron.
Stopping Bootlog daemon: bootlogd.

Debian GNU/Linux testing/unstable dec ttyS2

dec login: Instruction bus error, epc == 80045ae0, ra == 8005d8a8
Oops in traps.c::do_be, line 491:
$0 : 00000000 80280000 80280000 000f48b0 8027ef94 000f48b0 8027ef94 00000000
$8 : 8023e108 bc040000 00000020 874d227c 86b857e4 86b857e8 86b857e0 00000008
$16: 00000000 00000000 00000000 8027ebc0 80259820 fffffffe 00000000 04102060
$24: 00000000 2b107a90                   8023e000 8023fde0 8043ff80 8005d8a8
Hi : 00000000
Lo : 00000600
epc  : 80045ae0    Not tainted
Status: 1000e400
Cause : 00000018
Process swapper (pid: 0, stackpage=8023e000)
Stack:    00000000 8005da74 00000000 04102060 00000001 8005dd18 8027ebe0
 20000001 8027ebe0 8005de64 8027ebe0 800598e4 00000000 811b2940 8023fea8
 801263bc 800596a0 00000000 80158898 80158888 000000c0 80259848 00000000
 80259838 fffffffe 1000e400 8023fea8 00000000 80059170 30000400 fffffffb
 00000011 8004a6e8 8667c000 802590d0 8026c97c fffffffb 0000000d 8004a728
 8044e2d0 ...
Call Trace:   [<8005da74>] [<8005dd18>] [<8005de64>] [<800598e4>] [<801263bc>]
 [<800596a0>] [<80158898>] [<80158888>] [<80059170>] [<8004a6e8>] [<8004a728>]
 [<80125574>] [<80125574>] [<800432dc>] [<800432c0>] [<8020a37c>] [<8004042c>]
 [<8020959c>]

Code: 03a02021  080115e0  00000000 <401a6000> 00000000  001ad0c0  07400003  03a0d821  3c1b802b
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing

Anyone know what that means?  Running the 2.4.19 kernel from Debian
testing.

Is this a hardware failure or a bug?  It has done it twice now, once
while I didn't have a console up, and then I decided to put up a console
since it had crashed, and abuse hte network card with ping and gt that
within about 5 minutes.

Len Sorensen