[ Date Index ][
Thread Index ]
[ <= Previous by date / thread ] [ Next by date / thread => ]
On Sunday 19 October 2003 10:32, Robin Cornelius wrote: > Hi Lee, > > sounds nasty!. The first place to look would always be the syslog /var/log/ > syslog maybe /var/log/messages on some distros. You should be able to look > towards the end of it and itentify where you rebooted from and look back > before there before the crash to see if there is any naughtyness at all. > Thanks to all for the advice will monitor CPU, and next time it occurs will look at the logs at the precise time of the hiccup to see if any clues are given, like you were saying there are a lot of possibles. One thing that i did notice in the logs is a warning about the conexant winmodem driver which as it happens is very much beta,and uses a module called hfsoss spec which results in a few kernel warnings it could be the combination of sound and and internal modem causing a linux equivalent of a corenary heart attack! -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.