From: Yan Seiner <yan@seiner.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Kenrel oops
Date: Sun, 27 Apr 2008 13:03:06 -0700 [thread overview]
Message-ID: <4814DBFA.2070901@seiner.com> (raw)
I just had this kernel oops. Approximately 5 mintes later, the machine
hard-locked. Can anyone give me some guidance on where to look?
Apr 27 12:05:19 selene kernel: Unable to handle kernel paging request at
ffff81007e3d1300 RIP:
Apr 27 12:05:19 selene kernel: [<ffff81007e3d1300>]
Apr 27 12:05:19 selene kernel: PGD 8063 PUD a063 PMD 800000007e2001e3
Apr 27 12:05:19 selene kernel: Oops: 0011 [1] SMP
Apr 27 12:05:19 selene kernel: CPU 1
Apr 27 12:05:19 selene kernel: Modules linked in: nls_iso8859_1
nls_cp437 vfat fat usb_storage tcp_diag inet_diag nvidia(P) xt_m
ultiport iptable_filter ip_tables x_tables nfsd auth_rpcgss exportfs
ppdev lp ac battery autofs4 tun cpufreq_ondemand cpufreq_us
erspace cpufreq_conservative cpufreq_powersave cpufreq_stats freq_table
nfs lockd nfs_acl sunrpc bonding fuse loop firewire_sbp2
dvb_pll or51132 firmware_class cx88_dvb cx88_vp3054_i2c videobuf_dvb
dvb_core tuner tea5767 tda8290 tuner_simple mt20xx tea5761
cx88_alsa cx8802 snd_usb_audio cx8800 cx88xx snd_usb_lib ir_common
i2c_algo_bit snd_seq_dummy tveeprom snd_hda_intel serio_raw
snd_seq_oss videodev parport_pc parport snd_seq_midi snd_seq_midi_event
psmouse pcspkr v4l1_compat compat_ioctl32 v4l2_common sn
d_pcm_oss snd_mixer_oss snd_seq k8temp videobuf_dma_sg videobuf_core
btcx_risc snd_pcm usblp snd_timer snd_page_alloc snd_rawmid
i snd_seq_device shpchp snd_hwdep pci_hotplug snd soundcore i2c_nforce2
i2c_core button joydev evdev ext3 jbd mbcache raid456 as
yn
Apr 27 12:05:19 selene kernel: _xor async_memcpy async_tx xor raid1
raid0 md_mod osst st sd_mod sata_nv usbhid hid ata_generic l
ibata floppy firewire_ohci firewire_core crc_itu_t aic79xx
scsi_transport_spi scsi_mod forcedeth generic amd74xx ide_core ehci_h
cd ohci_hcd thermal processor fan
Apr 27 12:05:19 selene kernel: Pid: 32309, comm: configure_head.
Tainted: P 2.6.24-1-amd64 #1
Apr 27 12:05:19 selene kernel: RIP: 0010:[<ffff81007e3d1300>]
[<ffff81007e3d1300>]
Apr 27 12:05:19 selene kernel: RSP: 0018:ffff81007ada3ec0 EFLAGS: 00010286
Apr 27 12:05:19 selene kernel: RAX: ffff81007e3d1300 RBX:
ffff810026ec0050 RCX: ffff81007df37980
Apr 27 12:05:19 selene kernel: RDX: 0000000000000008 RSI:
ffff81007195ac80 RDI: ffff810026ec0050
Apr 27 12:05:19 selene kernel: RBP: ffff81007195ac80 R08:
ffff81003b4403f0 R09: ffff810001018700
Apr 27 12:05:19 selene kernel: R10: ffff810076d9c858 R11:
ffffffff802ea95d R12: 0000000000001018
Apr 27 12:05:19 selene kernel: R13: ffff8100049344c0 R14:
0000000000000200 R15: 0000000000000008
Apr 27 12:05:19 selene kernel: FS: 00002b9d5dd5fdc0(0000)
GS:ffff81007df98ac0(0000) knlGS:00000000f7e4d6b0
Apr 27 12:05:19 selene kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
000000008005003b
Apr 27 12:05:19 selene kernel: CR2: ffff81007e3d1300 CR3:
0000000000201000 CR4: 00000000000006e0
Apr 27 12:05:19 selene kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Apr 27 12:05:19 selene kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400
Apr 27 12:05:19 selene kernel: Process configure_head. (pid: 32309,
threadinfo ffff81007ada2000, task ffff81007706c000)
Apr 27 12:05:19 selene kernel: Stack: ffffffff8029680d ffff81007195ac80
1ffff020056f3c8f 0000000000001018
Apr 27 12:05:19 selene kernel: ffffffff802377a0 ffff810074155140
0000000000000001 ffff81007706c000
Apr 27 12:05:19 selene kernel: 0000000000000000 0000000000000000
00000000006dae08 0000000000000000
Apr 27 12:05:19 selene kernel: Call Trace:
Apr 27 12:05:19 selene kernel: [<ffffffff8029680d>] filp_close+0x37/0x65
Apr 27 12:05:19 selene kernel: [<ffffffff802377a0>]
put_files_struct+0x66/0xc4
Apr 27 12:05:19 selene kernel: [<ffffffff80238a6a>] do_exit+0x278/0x789
Apr 27 12:05:19 selene kernel: [<ffffffff80238ffa>] sys_exit_group+0x0/0xe
Apr 27 12:05:19 selene kernel: [<ffffffff8020be2e>] system_call+0x7e/0x83
Apr 27 12:05:19 selene kernel:
Apr 27 12:05:19 selene kernel:
Apr 27 12:05:19 selene kernel: Code: b8 75 ac 7e 00 81 ff ff a8 74 69 7e
00 81 ff ff 60 00 00 00
Apr 27 12:05:19 selene kernel: RIP [<ffff81007e3d1300>]
Apr 27 12:05:19 selene kernel: RSP <ffff81007ada3ec0>
Apr 27 12:05:19 selene kernel: CR2: ffff81007e3d1300
Apr 27 12:05:19 selene kernel: ---[ end trace d1960b80aa7bb270 ]---
Apr 27 12:05:19 selene kernel: Fixing recursive fault but reboot is needed!
--
o__
,>/'_ o__
(_)\(_) ,>/'_ o__
Yan Seiner (_)\(_) ,>/'_ o__
Certified Personal Trainer (_)\(_) ,>/'_ o__
Licensed Professional Engineer (_)\(_) ,>/'_
Who says engineers have to be pencil necked geeks? (_)\(_)
Help out my kids' school: http://www.seiner.com/blog/Travels/
next reply other threads:[~2008-04-27 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 20:03 Yan Seiner [this message]
2008-05-08 18:52 ` Kenrel oops Jan Kara
2008-05-08 19:00 ` Yan Seiner
2008-05-08 19:05 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4814DBFA.2070901@seiner.com \
--to=yan@seiner.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.