Subject: kern/6767: fxp driver seems to lock machine
To: None <gnats-bugs@gnats.netbsd.org>
From: Michael Graff <explorer@flame.org>
List: netbsd-bugs
Date: 01/07/1999 20:52:12
>Number: 6767
>Category: kern
>Synopsis: fxp driver seems to lock my machine
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: kern-bug-people (Kernel Bug People)
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Jan 7 21:05:01 1999
>Last-Modified:
>Originator: Michael Graff
>Organization:
flame.org
>Release: Thu Jan 7 20:48:39 PST 1999 (current)
>Environment:
System: NetBSD 1.3I i386
>Description:
When booting a kernel built from CVS-checked out 1999/01/07 sources,
the FXP driver seems to lock up.
The call stack is:
hardclock
softclock
fxp_tick()
fxp_mc_setup at _fxp_mc_setup + 0x2e2
This machine has two fxp cards installed, along with raidframe. I have not
yet traced things down enough to determine more.
>How-To-Repeat:
Boot a machine built from latest sources on a machine with a
fxp card.
>Fix:
Unknown.
>Audit-Trail:
>Unformatted: