I knew it I knew it I knew it! Posting that last comment guaranteed the problem would return. It's back to the original "no route to host" symptoms, so maybe I solved ONE problem, just not ALL problems. That's my way of looking at the bright side...
This time I happened to be listening to music exactly when it cut out, so I know an exact time to check for a logged event. Here it is, in /var/log/messages Apr 22 12:17:23 hostname kernel: ata2.00: exception Emask 0x0 Apr 22 12:24:55 hostname kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 22 12:24:55 hostname kernel: ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 in Apr 22 12:24:55 hostname kernel: res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) Apr 22 12:25:02 hostname kernel: ata2: port is slow to respond, please be patient (Status 0xd0) Apr 22 12:25:25 hostname kernel: ata2: port failed to respond (30 secs, Status 0xd0) Apr 22 12:25:25 hostname kernel: ata2: soft resetting port Apr 22 12:25:25 hostname kernel: ata2.00: configured for UDMA/33 Apr 22 12:25:25 hostname kernel: ata2: EH complete Ta-daa! The mystery death was at approximately 12:25. And there are also "no space left on device" messages in the slimserver.log (not timestamped) that could be from about the same time. So I'm thinking there's a problem in the kernel support for my SATA controller (some Intel thing). Some Googling seems to indicate this this particular event can happen when HAL periodically polls a SATA optical drive. So I shut down HAL because I don't need it on this server. Let's see how far we get this time...all suggestions welcome. -- CatBus ------------------------------------------------------------------------ CatBus's Profile: http://forums.slimdevices.com/member.php?userid=7461 View this thread: http://forums.slimdevices.com/showthread.php?t=34229 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
