Bug#681161: [squeeze] General Protection Fault or Invalid Opcode in mm/slub.c:2969
On Wed, Jul 11, 2012 at 11:52 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Can we have a few (10, maybe) lines before that, too? Sorry for the
> lack of clarity.
Sure, doesn't look very interesting but this is what precedes "cut
here" in /var/log/syslog:
Jul 11 09:58:06 archibald wpa_supplicant[1290]: Failed to initiate AP scan.
Jul 11 09:59:06 archibald wpa_supplicant[1290]: Failed to initiate AP scan.
Jul 11 10:00:06 archibald wpa_supplicant[1290]: Failed to initiate AP scan.
Jul 11 10:01:06 archibald wpa_supplicant[1290]: Failed to initiate AP scan.
Jul 11 10:02:06 archibald wpa_supplicant[1290]: Failed to initiate AP scan.
Jul 11 10:03:06 archibald wpa_supplicant[1290]: Failed to initiate AP scan.
Jul 11 10:04:06 archibald wpa_supplicant[1290]: Failed to initiate AP scan.
Jul 11 10:05:06 archibald wpa_supplicant[1290]: Failed to initiate AP scan.
Jul 11 10:06:06 archibald wpa_supplicant[1290]: Failed to initiate AP scan.
Jul 11 10:07:06 archibald wpa_supplicant[1290]: Failed to initiate AP scan.
I should probably look at disabling wifi on there as we don't use it.
The ten lines preceding "cut here" in dmesg show:
[ 24.433927] Bridge firewalling registered
[ 24.460461] Bluetooth: SCO (Voice Link) ver 0.6
[ 24.460465] Bluetooth: SCO socket layer initialized
[ 25.721535] lp: driver loaded but no devices found
[ 25.856612] powernow-k8: Found 1 AMD Turion(tm) 64 X2 Mobile
Technology TL-50 processors (2 cpu cores) (version 2.20.00)
[ 25.857138] powernow-k8: 0 : fid 0x8 (1600 MHz), vid 0x12
[ 25.857142] powernow-k8: 1 : fid 0x0 (800 MHz), vid 0x1e
[ 26.071107] ppdev: user-space parallel port driver
[ 26.512042] Clocksource tsc unstable (delta = -251968230 ns)
[ 31.273036] eth0: no IPv6 routers present
> In the current configuration, does memtest86+ report the memory to be
> ok?
Currently running Memtest86+ v4.20 off a Clonezilla CD. It hasn't
finished a pass but it's onto test #6 (30% through the pass) with no
problems.
> Have there been any other weird symptoms recently, or is this the
> first time?
There were some weird issues with Clonezilla. We tried to set up a
basic Debian plus a few, then clone it so I could try a new version of
Upstart, with ability to rapidly reset (this is a dedicated testbox).
Weird stuff happened with the restore process, so I formatted and
started over, fresh install. Subsequently backed it up again, haven't
restored. There was a weird glitch on reboot after Clonezilla, but
that's not unusual; cold boot worked. There was also an unusual screed
on bootup once, but it disappeared before I took good note of it. If
it happens again I'll try to track it down in syslog.
Nothing seems noteworthy to me, but I'll let you be the judge.
ChrisA
Reply to: