How to analyze a kernel oops on FC2

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

 



I have heard of kernel oops before but have not seen one until now. 
This is from an FC2 system.  I believe the kernel is up to date
(2.6.8-1.521 #1 Mon Aug 16 09:01:18 EDT 2004 i686 athlon i386
GNU/Linux).

System appeared to be operating normally until this occurred.  

How does one determine what caused this problem?


Nov 18 23:03:45 ws4 kernel: Unable to handle kernel paging request at
virtual address 6c696171
Nov 18 23:03:45 ws4 kernel:  printing eip:
Nov 18 23:03:45 ws4 kernel: 208559bc
Nov 18 23:03:45 ws4 kernel: *pde = 00000000
Nov 18 23:03:45 ws4 kernel: Oops: 0002 [#1]
Nov 18 23:03:45 ws4 kernel: Modules linked in: snd_mixer_oss snd_via82xx
snd_ac97_codec snd_pcm snd_timer snd_page_alloc gameport snd_mpu401_uart
snd_rawmidi snd_seq_device snd soundcore parport_pc lp parport autofs4
sunrpc 8139too mii ipt_REJECT ipt_state ip_conntrack iptable_filter
ip_tables floppy sg scsi_mod dm_mod uhci_hcd ehci_hcd button battery
asus_acpi ac md5 ipv6 ext3 jbd
Nov 18 23:03:45 ws4 kernel: CPU:    0
Nov 18 23:03:45 ws4 kernel: EIP:    0060:[<208559bc>]    Not tainted
Nov 18 23:03:45 ws4 kernel: EFLAGS: 00010206   (2.6.8-1.521)
Nov 18 23:03:45 ws4 kernel: EIP is at
journal_commit_transaction+0xb5a/0x1d72 [jbd]
Nov 18 23:03:45 ws4 kernel: eax: 0eb7b59c   ebx: 6c69616d   ecx:
1ff90140   edx: 1ff90140
Nov 18 23:03:45 ws4 kernel: esi: 0d391e6c   edi: 1ff90140   ebp:
1fee6400   esp: 1e6a9de4
Nov 18 23:03:45 ws4 kernel: ds: 007b   es: 007b   ss: 0068
Nov 18 23:03:45 ws4 kernel: Process kjournald (pid: 1265,
threadinfo=1e6a9000 task=1e7b6700)
Nov 18 23:03:45 ws4 kernel: Stack: 00000000 00000000 00000000 00000000
00000000 12d435fc 1ff90140 1f851c5c
Nov 18 23:03:45 ws4 kernel:        00001ed4 00000000 1e7b6700 0211be05
1e6a9e34 1e6a9e34 00000000 00000000
Nov 18 23:03:45 ws4 kernel:        00000000 00000000 1e7b6700 0211be05
1e6a9e34 1e6a9e34 00000000 00000000
Nov 18 23:03:45 ws4 kernel: Call Trace:
Nov 18 23:03:45 ws4 kernel:  [<0211be05>]
autoremove_wake_function+0x0/0x2d
Nov 18 23:03:45 ws4 kernel:  [<0211be05>]
autoremove_wake_function+0x0/0x2d
Nov 18 23:03:45 ws4 kernel:  [<208592c3>] kjournald+0x1ad/0x548 [jbd]
Nov 18 23:03:45 ws4 kernel:  [<0211be05>]
autoremove_wake_function+0x0/0x2d
Nov 18 23:03:45 ws4 kernel:  [<0211be05>]
autoremove_wake_function+0x0/0x2d
Nov 18 23:03:45 ws4 kernel:  [<20859110>] commit_timeout+0x0/0x5 [jbd]
Nov 18 23:03:45 ws4 kernel:  [<20859116>] kjournald+0x0/0x548 [jbd]
Nov 18 23:03:45 ws4 kernel:  [<021041d9>] kernel_thread_helper+0x5/0xb
Nov 18 23:03:45 ws4 kernel: Code: ff 43 04 8b 03 a8 04 0f 84 4e 01 00 00
81 bd 74 01 00 00 3c
Nov 18 23:03:45 ws4 kernel:  fs/jbd/transaction.c:980:
spin_lock(fs/jbd/journal.c:1fee6574) already locked by
fs/jbd/commit.c/320
Nov 19 06:32:38 ws4 syslogd 1.4.1: restart.

-- 
Scot L. Harris
webid@xxxxxxxxxx

Who does not trust enough will not be trusted.
		-- Lao Tsu 


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux