[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

help interpreting dmesg output



Hi,

I was using dvd::rip to scan the volume level of a set of vob files
on a hard disc.  The following dmesg is from the second time I tried
it.  Progress got to about 20% (very quickly, I assume the file had
been cached), then finished.  This turned up on the console:
Message from syslogd atlas at Tue Sep  5 15:23:55 2006 ...
atlas kernel: Oops: 0000 [#4]

followed by registers and a call trace.  Something very similar
happened when I tried to cat the file to /dev/null.  After
repeating this a couple of times I cleared the cache by copying
another large file to /dev/null which seemed to eliminate the
problem.

The dmesg output is below.  What I'd like to know is whether this
looks like a hardware problem, a filesystem problem or simply a
bug somewhere.  Thanks for your time.

BUG: unable to handle kernel paging request at virtual address 00160000
 printing eip:
c043f7a0
*pde = 00000000
Oops: 0000 [#3]
last sysfs file: /block/hda/hda1/size
Modules linked in: autofs4 hidp rfcomm l2cap bluetooth sunrpc ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables acpi_cpufreq vfat fat video button battery ac ipv6 lp floppy ehci_hcd ohci_hcd nvidia(U) uhci_hcd snd_ice1724 snd_ice17xx_ak4xxx snd_ac97_codec snd_ac97_bus snd_ak4114 serio_raw snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_ak4xxx_adda snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore i2c_viapro parport_pc 8139cp via686a hwmon i2c_isa i2c_core amd76x_edac 8139too mii edac_mc parport dm_snapshot dm_zero dm_mirror dm_mod ext3 jbd
CPU:    0
EIP:    0060:[<c043f7a0>]    Tainted: P      VLI
EFLAGS: 00010006   (2.6.17-1.2174_FC5 #1)
EIP is at find_get_page+0x23/0x3f
eax: 00160000   ebx: 00160000   ecx: 00023700   edx: 00000000
esi: 000237e4   edi: c6574834   ebp: 000237e4   esp: c530ae00
ds: 007b   es: 007b   ss: 0068
Process cat (pid: 5954, threadinfo=c530a000 task=e1fabaa0)
Stack: 00001000 c1687680 000237e4 c043fe49 000237e4 00000004 000237e0 00000000 e5f72d20 e5f72d70 c6574824 c657473c 0003ffff 00000000 000237e8 000237e5 000237e3 40000000 00000000 00000000 00001000 00000000 00000000 00000002
Call Trace:
<c043fe49> do_generic_mapping_read+0x13a/0x465 <c044098d> __generic_file_aio_read+0x167/0x1ac <c043f625> file_read_actor+0x0/0xe0 <c0440a12> generic_file_aio_read+0x40/0x47 <c045bd3a> do_sync_read+0xc3/0xfd <c04204e4> current_fs_time+0x45/0x51 <c042c17c> autoremove_wake_function+0x0/0x35 <c045bc77> do_sync_read+0x0/0xfd
 <c045c671> vfs_read+0xa6/0x14e  <c045c9f0> sys_read+0x41/0x67
 <c0402cb3> syscall_call+0x7/0xb
Code: 83 c4 0c 5b 5e 5f 5d c3 57 56 89 d6 8d 78 10 53 89 c3 89 f8 83 c3 04 e8 9f 33 1c 00 89 d8 89 f2 e8 5e 66 09 00 85 c0 89 c3 74 0f <8b> 00 89 da f6 c4 40 74 03 8b 53 0c ff 42 04 89 f8 e8 10 33 1c
EIP: [<c043f7a0>] find_get_page+0x23/0x3f SS:ESP 0068:c530ae00
<3>BUG: sleeping function called from invalid context at include/linux/rwsem.h:43
in_atomic():0, irqs_disabled():1
<c0426d91> blocking_notifier_call_chain+0x18/0x49 <c041e800> do_exit+0x19/0x768
 <c0529103> do_unblank_screen+0x2a/0x127  <c04042c0> die+0x27b/0x2a0
 <c0603b4e> do_page_fault+0x443/0x5ad  <c060370b> do_page_fault+0x0/0x5ad
 <c04037df> error_code+0x4f/0x54  <c043f7a0> find_get_page+0x23/0x3f
<c043fe49> do_generic_mapping_read+0x13a/0x465 <c044098d> __generic_file_aio_read+0x167/0x1ac <c043f625> file_read_actor+0x0/0xe0 <c0440a12> generic_file_aio_read+0x40/0x47 <c045bd3a> do_sync_read+0xc3/0xfd <c04204e4> current_fs_time+0x45/0x51 <c042c17c> autoremove_wake_function+0x0/0x35 <c045bc77> do_sync_read+0x0/0xfd
 <c045c671> vfs_read+0xa6/0x14e  <c045c9f0> sys_read+0x41/0x67
 <c0402cb3> syscall_call+0x7/0xb


--
imalone


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]