| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
Can anyone tell me what this message means: "vmunix: We have an empty buffer error - intr path" It was logged in kern.log Any help appreciated. Regards, Greg Carmody. CSS Sydney.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 9665.1 | some additional info might be helpful | NNTPD::"[email protected]" | Farrell Woods | Wed Apr 30 1997 17:40 | 19 |
Perhaps you could tell us which version of the OS you're referring to,
and what hardware it's running on...
I groped around for a few moments looking for that string. Couldn't
find it. I'm suspecting that there's a custom or third-party driver
built into the kernel, and that this is generating the message.
If it's a driver for which the customer doesn't have source, they can
figure out if the message is coming from it by running the "strings"
program on it's .o or .mod files, looking (grep) for the whole string or
pieces of it (to catch the case of things like:
printf("We have an %s error - %s path", errlist[whatever], func_name);
-- Farrell
[Posted by WWW Notes gateway]
| |||||
| 9665.2 | AUSSIE::CARMODY | Thu May 01 1997 01:20 | 7 | ||
Thanks Farrell. This gives me some place to start looking. The customer is running DU3.2g on Alpha Server 1000A. I suspect the message may be coming from the driver for the PTI V.35 card used by DECss7. Regards, Greg. | |||||