On Wed, Jul 13, 2011 at 10:31 PM, Dale <rdalek1...@gmail.com> wrote: > I'm baaaaaacccckkkkkk. Anybody want to guess why? Come on, guess. First > one doesn't count. > > OK. This thing ran for a while with no problems. I'm downloading a video > while I am watching TV. I use Firefox for that because it has that download > helper tool and I like it. I couldn't find it for Seamonkey. Anyway, I'm > watching TV when I here my puter beep like it does when it is booting up the > BIOS. I look over and sure enough, it was rebooting. This is what I am > using at the moment: > > root@fireball / # equery list *xorg* firefox nvidia* > * Searching for *xorg* ... > [IP-] [ ] x11-base/xorg-drivers-1.10:0 > [IP-] [ ] x11-base/xorg-server-1.10.3:0 > > * Searching for firefox ... > [IP-] [ ] www-client/firefox-3.6.17:0 > > * Searching for nvidia* ... > [IP-] [ ] media-video/nvidia-settings-260.19.29:0 > [IP-] [ ] x11-drivers/nvidia-drivers-275.09.07:0 > root@fireball / # > > > There was a bump in xorg-server so I let it upgrade. I also noticed the > nvidia and updated it as well. I don't recall seeing that the last time I > looked. Anyway, Could this be xorg, Nvidia, Firefox or something else or a > combination of a couple of them? I'm on the latest of everything that is in > the tree. I'm thinking about going back to the older xorg, just to test. > > While I am at it, it ran fine before I let it upgrade xorg. Maybe I didn't > let it run long enough or something but it never crashed on me. > > Any more thoughts on this mess? > > Dale
A complete reboot like that might be software jumping to the wrong address but, if so, it seems to me that it's more likely caused by how you've built the machine and not the software itself having a bug. KDE & Firefox are very widely used. Why should you hit this bug and not everyone else? None the less publish everything required for people to hep, emerge --info, contents of all /etc/portage/package.* files, /var/lib/portage/world, rc-update show results, etc. Maybe someone will see it when you haven't. I don't think it's the nvidia-settings stuff if you haven't run nvidia settings. On the other hand, it's new hardware which is where I'd put my bet. A flaky power supply. A funky motherboard. Bad CPU cooling causing overheating. Memory problems that are as of yet uncovered by memtest86. Bummer... - Mark
