giacobbe@pilot.njin.net (Jeff Giacobbe) (01/08/91)
Last Friday morning, I noticed that our server had mysteriously rebooted
during the night. The following messages were on the screen (and also in
/etc/adm/messages, of course :-) ) -- server's name is logos
Jan 3 23:33:46 logos vmunix: le0: panic: RINT with buffer owned by chip
Jan 3 23:33:46 logos vmunix: syncing file systems... done
Jan 3 23:33:46 logos vmunix: dumping to vp ff005f9c, offset 32522
Jan 3 23:33:46 logos vmunix: 4093 total pages, dump succeeded
Jan 3 23:33:46 logos vmunix: rebooting...
[ remainder of reboot messages ]
What the heck happened? It seems that there was some kind of error with
the Lance Ethernet board (le0) that cause a panic, core dump, and reboot.
Anyone know what le0: panic: RINT with buffer owned by chip means? Who
is this Chip character and why does he own my RINT with buffer!? :) :)
Any help would be appreciated.
Jeff
@xxxxx{==============- giacobbe@pilot.njin.net -==============}xxxxx@dupuy@cs.columbia.edu (01/10/91)
There's a patch for the "RINT with buffer owned by chip", which you can
get via anonymous ftp from princeton.edu, in
~ftp/pub/sun-fixes/if_le.patch.shar.
Here's the README file:
This tape contains new versions of the Unix kernel object file if_le.o for
SunOS 4.0.3.
This patch contains a slightly modified 4.0.3[c] lance ethernet driver
(if_le.c) and object files for sun3x (hydra), sun4 (stingray), and sun4c
(SPARCstation1) as an effective patch for 4.0.3[c] lance xmit memory
underflow ("transmission stopped").
1. Increase LANCE_MIN_TU from 100 to 102, this effectively
eliminates UFLO (!)
2. Minimize leintr lance slave register accesses -
this is also a factor in UFLO.
3. Never print "Transmission stopped" or "memory underflow"
error messages.
This patch also fixes the panic: le0: RINT: Buffer owned by chip problem.
Architecture:
Sun-3x, Sun-4, Sun-4c
Release:
4.0.3
Bug Report Id:
1029247, 1019513, 1029316 and 1021518dvandeer@oracle.com (Danny Vanderryn) (01/19/91)
In article <1202@brchh104.bnr.ca> dupuy@cs.columbia.edu writes: > >There's a patch for the "RINT with buffer owned by chip", which you can >get via anonymous ftp from princeton.edu, in >~ftp/pub/sun-fixes/if_le.patch.shar. Does this solve spurious "le0: No carrier - transceiver cable problem?" messages as well? Our network people have been reinstalling ethernet boards left and right, etc., but I keep thinking maybe it's a software prob. [[Ed's Note: These messages (No carrier) were discussed in some detail a while back (v8n80 v8n88 v8n98 v8n121 among others), and then general consensus seemed to be that this was usually a hardware problem with loose connections being the #1 cited cause. -bdg]]