DragonFly BSD
DragonFly users List (threaded) for 2005-02
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: interrupt routing problem?

From: Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
Date: Wed, 9 Feb 2005 13:39:39 -0800 (PST)

:>    We currently have some issues with gdb'ing kernel cores that may make
:>    it more difficult to track the problem down.  Joerg has been working on
:>    them.
:I can do that, but I'm not sure you understood properly. When I said "lock up"
:I didnt mean that the system locked up, but just the controller. I can run
:ifconfigs to revive the port, so I can add trace code or whatever is necessary
:to look at things.
:Since my last post I fired up linux and linux runs fine with no problems. The
:interrrupt that both ports on the PCI-X slot is using is 9.
:Also, why does dragonfly put stray interrupts into the vmstat output? Is 
:that useful for something?

    If you get a dump I can look at the EM driver's management structures
    to try to figure out what state the EM driver is in.

    keeping track of stray interrupts is a good debugging tool.

					Matthew Dillon 

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]