FC6 with yum updates - unstable

[Chris Jones]

> 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

looks like beagle might be going mad. Wouldn't be the first time.

Unless you really want it (and I wouldn't recommend it to my worst 
enemy) I suggest.

  > rpmquery -qa | grep beagle

and remove anything beagle related

  > yum remove beagle*

and see if that helps ?