by TonF » Wed, 28 Jul 1999 04:00:00
Since a couple of days I get lots of messages like
got a messages (-1, 0x2018)
readfs=0x2018
on the console.
Seems to ignore syslog: in the syslog are no messages.
We've killed nearly all processes that could be the cause, but still
they come.
Anyone have an idea as to where these messages come from?
Ton
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
1. 2.2.18+ adaptec 29160 (scsi0:-1:-1:-1) Referenced SCB 0 not valid
I saw this in earlier kernels but wonder if anyone has a clue.
Dec 31 15:47:47 salsablanca kernel: SCSISEQ = 0x5a SEQADDR =
0x9 SSTAT0
= 0x10 SSTAT1 = 0x8a
Dec 31 15:47:47 salsablanca kernel: (scsi0:-1:-1:-1) Referenced SCB 0
not valid
during SELTO.
Dec 31 15:47:47 salsablanca kernel: SCSISEQ = 0x5a SEQADDR =
0x8 SSTAT0
= 0x10 SSTAT1 = 0x8a
Dec 31 15:47:47 salsablanca kernel: scsi : aborting command due to
timeout : pid
15169, scsi0, channel 0, id 0, lun 0 Write (10) 00 02 14 34 86 00 00
08 00
Dec 31 15:47:47 salsablanca kernel: scsi : aborting command due to
timeout : pid
15170, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 00 00 4d 00 00
02 00
I am hoping it is not a hardware issue.
I see this also on a 2.2.17 kernel.
The 2.2.18 is monolithic and the 2.2.17 is modular for scsi.
This is a SEAGATE LVD 18gig drive.
2. watchdog - multiple instances
5. We are getting this error message /var/log/messages
7. Problems with Samba and SCO Openserver 5.0.2
8. Getting console messages in X
9. getting pppd/chat messages -> /dev/console
10. Why do I keep getting this console message in RH72?
11. CONSOLE window in X gets no messages - HELP!
12. iptables log messages getting spewed to console