it appears the issue stemmed from some faulty RAM modules.. I'll be returning those...
On Sat, Dec 3, 2011 at 8:35 PM, Glenn Phillips <gl...@coriolis-storm.com>wrote: > And it happened again, also firefox randomly seg faulting in general... no > other applications affected...' > is this possibly another gcc issue? > > dmesg: > [440280.814698] firefox[11819] trap stack segment ip:7eff3d39a6c8 > sp:7fff83606180 error:0 > [440775.509228] equo[13242] general protection ip:7ff5d197ab20 > sp:7fff0ec3e528 error:0 in libpython2.7.so.1.0[7ff5d1868000+175000] > > > /var/log/messages > Dec 3 20:10:01 kralizec cron[12533]: (root) CMD (test -x > /usr/sbin/run-crons && /usr/sbin/run-crons ) > Dec 3 20:18:56 kralizec kernel: [440280.814698] firefox[11819] trap stack > segment ip:7eff3d39a6c8 sp:7fff83606180 error:0 > Dec 3 20:20:01 kralizec cron[12580]: (root) CMD (test -x > /usr/sbin/run-crons && /usr/sbin/run-crons ) > Dec 3 20:25:35 kralizec dbus[6355]: [system] Reloaded configuration > Dec 3 20:25:35 kralizec dbus[6355]: [system] Reloaded configuration > Dec 3 20:27:11 kralizec kernel: [440775.509228] equo[13242] general > protection ip:7ff5d197ab20 sp:7fff0ec3e528 error:0 in > libpython2.7.so.1.0[7ff5d1868000+175000] > > > > > On Tue, Nov 29, 2011 at 9:33 AM, Glenn Phillips > <gl...@coriolis-storm.com>wrote: > >> You're right, it appears to have some funny kernel/mismatch from a prior >> update, it eventually forced me to reboot. also Dmesg appeared to be fine. >> >> >> On Mon, Nov 28, 2011 at 2:04 PM, Fabio Erculiani <lx...@sabayon.org>wrote: >> >>> That looks like completely random or hardware/system-related (unstable?). >>> What did dmesg say about it? >>> I guess you didn't have the core-dump enabled (ulimit -S). >>> >>> -- >>> Fabio Erculiani >>> >>> >> >
