On Sat Feb 23, 2002 at 11:18:23AM -0500, Stew Benedict wrote: > > I just came back in from watching a movie and found my machine sitting > > at gdm... definately not in fluxbox with xchat and gkrellm running > > (only apps running at the time). > > > > > Feb 22 22:08:32 imac kernel: Loaded 136 symbols from 6 modules. > > Feb 22 22:08:32 imac kernel: Memory BAT mapping: BAT2=256Mb, BAT3=256Mb, residual: >0Mb > > > > Nothing spectacular at all... shows a few hours of it running, a few > > cronjobs, and then nothing until syslogd restarts (from the reboot, I > > imagine). > > > > Any ideas on where I else I might look to find some info on this? > > It's extremely wierd... I've never had this happen on my imac before > > (regular imac indigo with a larger (40GB instead of 20GB) drive and a > > little extra RAM. > > Hmm, not good. I've occasionally had spontaneous reboots here, but my > machine is being beat on pretty heavily, running rpm-rebuild and updating > itself almost constantly. I had one like you describe, when the cron > stuff ran on top of a big build of glibc or something and triggered a > panic, and recently pcmcia_cs built/updated itself and stopped/restart > card services with my 4 firewire partitions mounted which just hung things > in limbo until I manually rebooted.
Definately no heavy load here.. it was basically idling and doing nothing. > It's possible a power event triggered it too. My Powerbook, even though > it has batteries, seems sensitive to line dips etc. My wife has kicked on > the dryer before, which will sag that line and the PC, which is on a UPS > is fine, although the UPS gripes, and the Powerbook, which isn't on the > UPS will occasionally reboot. This seems more likely. Nothing else did a dip, but most of the machines are on UPS systems and the AMD machines aren't really susceptible to little spikes or drops to do a reboot. I've no idea how sensitive the imac is... it could be like my P3 which, even though it's connected to a UPS, will reboot given the slightest variation in current (very odd, that). I haven't noticed it since, however, which is a good sign. > Unfortunately, since the logs didn't show anything, all we can do is guess > what happened. If you can catch in action and get oops info maybe we can > diagnose. Will do. I'll assume it's a fluke... the only other machine in here that seems to be pretty sensitive is the SparcStation2 and it wasn't powered on at the time. -- MandrakeSoft Security; http://www.mandrakesecure.net/ "lynx -source http://www.freezer-burn.org/bios/vdanen.gpg | gpg --import" 1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD Current Linux kernel 2.4.8-34.1mdk uptime: 33 days 18 hours 43 minutes.
msg01820/pgp00000.pgp
Description: PGP signature
