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

Re: Had this oops while using nfs on F11



On Fri, Apr 03, 2009 at 07:23:38PM -0400, Louis E Garcia II wrote:
 > Is this enough for a bug report?
 > 
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel:Oops: 0000 [#1] SMP 
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel:last sysfs
 > file: /sys/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/rfkill/rfkill0/state
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel:Stack:
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: 0000000000000001 ffffffff815f4040 ffff88001f9efc90
 > 0000000000000246
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: ffff88001f9c6000 ffff88002ed3d180 ffff88001f9efc90
 > ffffffff811894f8
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel:Call Trace:
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffff811894f8>] selinux_dentry_open+0xe7/0xf0
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffff81181be1>] security_dentry_open+0x16/0x18
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffff810d69de>] __dentry_open+0x11b/0x273
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffff810d6bbd>] dentry_open+0x87/0x8e
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffff813a9f97>] ? trace_hardirqs_on_thunk+0x3a/0x3c
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffffa03390cc>] nfsd_open+0x12d/0x156 [nfsd]
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffff81050686>] ? _local_bh_enable_ip+0xde/0xeb
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffffa0339451>] nfsd_read+0x85/0xc4 [nfsd]
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffffa033f6f8>] nfsd3_proc_read+0xe7/0x126 [nfsd]
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffffa033426f>] nfsd_dispatch+0xf1/0x1cc [nfsd]
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffffa02921b5>] svc_process+0x426/0x642 [sunrpc]
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffffa033486e>] nfsd+0x14c/0x1aa [nfsd]
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffffa0334722>] ? nfsd+0x0/0x1aa [nfsd]
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffff8105edd5>] kthread+0x4d/0x78
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffff810126ca>] child_rip+0xa/0x20
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffff81011fe7>] ? restore_args+0x0/0x30
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffff8105ed88>] ? kthread+0x0/0x78
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel: [<ffffffff810126c0>] ? child_rip+0x0/0x20
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel:Code: 83 ec 50 0f 1f 44 00 00 44 8b 9e 18 02 00 00 31 c0 49 89
 > c8 41 81 e3 00 02 00 00 75 42 48 8b 47 68 48 85 c9 4c 8b 96 20 02 00 00
 > <44> 8b 48 04 75 19 4c 8d 45 b0 b9 12 00 00 00 44 89 d8 4c 89 c7 
 > 
 > Message from syslogd localhost at Apr  3 19:08:35 ...
 >  kernel:CR2: 0000000000000004

Yes. bz it please.

If the box is still up, you'll get a cleaner output 
(without all those syslogd lines) by running dmesg

	Dave
 


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