And I'm beginning to wonder about my hardware, gkrellms displayed
temps are fubar after the reboot, one is 32F, the other about
261.6F, and the heat sinks feel plumb normal. Displayed temps a
few minutes prior to the crash were both normal and in the low
130F range, its nice & warm in the coyotes den tonight. AC is off,
and I just opened the window about a foot.
Anyway, from /var/log/messages:
Aug 6 01:23:08 coyote kernel: BUG: unable to handle kernel NULL pointer
dereference at virtual address 0000002e
Aug 6 01:23:08 coyote kernel: printing eip:
Aug 6 01:23:08 coyote kernel: c01543b3
Aug 6 01:23:08 coyote kernel: *pde = 00000000
Aug 6 01:23:08 coyote kernel: Oops: 0002 [#1]
Aug 6 01:23:08 coyote kernel: PREEMPT
Aug 6 01:23:08 coyote kernel: Modules linked in: snd_rtctimer cx88_dvb
cx88_vp3054_i2c mt352 or51132 video_buf_dvb
dvb_core nxt200x zl10353 cx24123 lgdt330x cx22702 dvb_pll cx8802 tda9887
cx8800 compat_ioctl32 v4l1_compat cx88xx
ir_common i2c_algo_bit video_buf btcx_risc tuner v4l2_common tveeprom videodev
radeon drm nvidia_agp agpgart w83627
hf hwmon_vid i2c_isa i2c_nforce2 i2c_core snd_seq_oss snd_pcm_oss snd_mixer_oss
snd_bt87x pl2303 usbserial snd_seq_
midi snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_event
snd_seq_midi_emul snd_seq snd_intel8x0 snd
_emu10k1 snd_rawmidi snd_ac97_codec snd_ac97_bus snd_pcm snd_seq_device
snd_timer snd_page_alloc snd_util_mem snd_h
wdep snd soundcore nfsd exportfs lockd nfs_acl smbfs sunrpc ohci1394 ieee1394
Aug 6 01:23:08 coyote kernel: CPU: 0
Aug 6 01:23:08 coyote kernel: EIP: 0060:[<c01543b3>] Not tainted VLI
Aug 6 01:23:08 coyote kernel: EFLAGS: 00010202 (2.6.17.7 #1)
Aug 6 01:23:08 coyote kernel: EIP is at __pollwait+0x25/0x4b
Aug 6 01:23:08 coyote kernel: eax: fffff000 ebx: ee87d700 ecx: 0000002e
edx: 00000032
Aug 6 01:23:08 coyote kernel: esi: c08da398 edi: 00000145 ebp: 00000040
esp: c8910b44
Aug 6 01:23:08 coyote kernel: ds: 007b es: 007b ss: 0068
Aug 6 01:23:08 coyote kernel: Process dumper (pid: 18807, threadinfo=c8910000
task=efef5090)
Aug 6 01:23:08 coyote kernel: Stack: c0f965e0 00000000 c029fba0 ee87d700
c08da398 c8910bd4 ee87d700 ee87d700
Aug 6 01:23:08 coyote kernel: ee87d700 00000000 00000145 00000040
c027d05b ee87d700 c08da380 c8910bd4
Aug 6 01:23:08 coyote kernel: c0154642 ee87d700 c8910bd4 000000e0
00000000 000000e0 00000000 00000000
Aug 6 01:23:08 coyote kernel: Call Trace:
Aug 6 01:23:08 coyote kernel: <c029fba0> tcp_poll+0x24/0x146 <c027d05b>
sock_poll+0x13/0x17
Aug 6 01:23:08 coyote kernel: <c0154642> do_select+0x1a4/0x33c <c015438e>
__pollwait+0x0/0x4b
Aug 6 01:42:30 coyote syslogd 1.4.1: restart.
The delay was the e2fsck of all disks. Kernel is 2.6.17.7, amanda was
2.5.0p2-20060424.
kmail was running on another screen, and I was also playing
patience (solitaire) when everything went black.
I've performed an amcleanup, and restarted the amanda wrapper script
that I use.
The amstatus output looks fairly normal for this time of the night.
Is there enough here to allow some finger pointing?
--
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules. I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
|
