Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: giacobbe@pilot.njin.net (Jeff Giacobbe)
Newsgroups: comp.sys.sun
Subject: Ethernet panic/reboot !!
Keywords: Miscellaneous
Message-ID: <1110@brchh104.bnr.ca>
Date: 7 Jan 91 18:01:25 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 21
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 10, Issue 11, message 6
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

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@