Yes, we're working on it in a sub-group.
Since the panic message is a new one -- it's one I added that never existed
in -3.x, it is possible that the bug is not related to my VM stuff but
related to something else going on.
I've found a number of other bugs in the greater VM system which I am
comitting fixes for, *BUT* I don't think any of them are related to this
particular panic.
I am also comitting some very strict KASSERT checking to try to catch
the problem earlier. Everyone running 4.x kernels should add the following
options to your kernel config:
options INVARIANTS
options INVARIANT_SUPPORT
-Matt
Matthew Dillon
<dil...@backplane.com>
:On Sun, 24 Jan 1999, Peter Wemm wrote:
:
:[..]
:> Oh, one other thing that occurred to me.. Under 4.0-current, I regularly
:> (ie: within 30 seconds of boot) get if_de tranmitter underflows. My
:> console corruption was happening at the instant that de0 was being
:> configured with ifconfig. exmh is running to a remote display over that
:> de0 interface.
:
:Here too... pretty quickly after boot on a SMP machine (current as of Jan
:12) that pushes quite a bit of traffic, the following messages appear:
:
:de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256)
:de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512)
:de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024)
:
:The card is:
:
:de0: <Digital 21140A Fast Ethernet> rev 0x22 int a irq 16 on pci0.12.0
:de0: 21140A [10-100Mb/s] pass 2.2
:de0: address 00:c0:f0:1f:5d:0d
:de0: enabling Full Duplex 100baseTX port
:
:Actually a Kingston clone, not a real DEC (so 1/5th of the price - but the
:receiver doesn't go audibly *click* when it's autosensing).
:
:So far I've gotten this message once:
:
:de0: abnormal interrupt: transmit underflow (switching to store-and-forward
mode)
:
:Any harm in them, or can I safely ignore them? Would it be a good idea to
:raise the TX threshold by default, if only to avoid the messages?
:It's plugged into a Catalyst switch, if it makes any difference...
:
:
: -- Niels.
:
:
:To Unsubscribe: send mail to majord...@freebsd.org
:with "unsubscribe freebsd-current" in the body of the message
:
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
