On Tue, 27 Mar 2007, Keith G. Robertson-Turner wrote:
Verily I say unto thee, that Randy Vice spake thusly:
Since yesterday, my FC6 with all the updates has been very unstable with
the current kernel (and it's patches via yum). It's a bit more stable
using the original kernel (plus all the patches), but it's not perfect.
Well I'm fully up2date here too, and 100% rock solid.
And that's on an AMD64 system with a mix of 64 and 32 bit libraries,
packages from 25 different repos, fglrx (ATI) proprietary drivers, half
a dozen commercial Linux games, Cedga running half a dozen commercial
Windows games, proprietary software such as VMWare running Windows XP,
and my own collection of custom built packages.
If there was a b0rk vector in there somewhere, pure statistics would
suggest I'd have hit it.
It's x86_64 as well.
Machine runs stable under XP in harsh gaming environment so I don't
think ti's the hardware. Suggestions on which log I need to tail?
/var/log/messages would be a good start.
Thanks. This is where I lose the system:
Mar 27 04:15:25 bbs kernel: printk: 1014 messages suppressed.
Mar 27 04:15:25 bbs kernel: 4gb seg fixup, process beagled (pid 2972),
cs:ip 73:0811853f
Mar 27 04:15:30 bbs kernel: printk: 1941 messages suppressed.
Mar 27 04:15:30 bbs kernel: 4gb seg fixup, process beagled (pid 2972),
cs:ip 73:0811853f
Mar 27 04:15:35 bbs kernel: printk: 1745 messages suppressed.
Mar 27 04:15:35 bbs kernel: 4gb seg fixup, process beagled (pid 2972),
cs:ip 73:0811853f
Mar 27 04:15:41 bbs kernel: printk: 269747 messages suppressed.
Mar 27 04:15:41 bbs kernel: 4gb seg fixup, process beagled-helper (pid
3129), cs:ip 73:0811846aMar 27 04:15:25 bbs kernel: printk: 1014 messages
suppressed.
Mar 27 04:15:25 bbs kernel: 4gb seg fixup, process beagled (pid 2972),
cs:ip 73:0811853f
Mar 27 04:15:30 bbs kernel: printk: 1941 messages suppressed.
Mar 27 04:15:30 bbs kernel: 4gb seg fixup, process beagled (pid 2972),
cs:ip 73:0811853f
Mar 27 04:15:35 bbs kernel: printk: 1745 messages suppressed.
Mar 27 04:15:35 bbs kernel: 4gb seg fixup, process beagled (pid 2972),
cs:ip 73:0811853f
Mar 27 04:15:41 bbs kernel: printk: 269747 messages suppressed.
Mar 27 04:15:41 bbs kernel: 4gb seg fixup, process beagled-helper (pid
3129), cs:ip 73:0811846a
Given that you say downgrading the kernel doesn't help, it's unlikely to
be a driver issue (if, as you say, all was stable before).
Are you running anything weird on the system?
Oh, and like Ed already said ... define "unstable"
Current kernel may or may not survive bootup. I may get into X and a
chance to log on and lose it shortly afterwards. Going with the original
kernel, I lose it many hours later.
Thanks again!
Randy
--
: damocles@xxxxxxxxxxxxxxx : Bruce Morrow, a man before and after his time :
: "The tree of liberty must be refreshed from time to time with the blood :
: of patriots and tyrants." - Thomas Jefferson 11-13-1787 "Let's roll." :
: Todd Beamer, American Patriot onboard United Airlines Flight 93 9-11-01 :
: damocles@xxxxxxxxxxxxxxx http://www.thenostromo.com/ :
