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

Re: how can i see the result of my "kerneloops"?






--- On Thu, 4/23/09, Robert P. J. Day <rpjday crashcourse ca> wrote:

> From: Robert P. J. Day <rpjday crashcourse ca>
> Subject: how can i see the result of my "kerneloops"?
> To: "Fedora Test List" <fedora-test-list redhat com>
> Date: Thursday, April 23, 2009, 4:13 PM
> still fighting with a radeon driver issue, and apparently,
> it caused
> a kernel oops, which i sent on.  but how can i take a look
> at the
> contents of that kerneloops report once it's out of my
> hands?  is
> there some record of it?
> 
> rday
> --

Try dmesg.  ALso you could have clicked on view right before you sent it.  For instance I have one recurring and I see it almost every time I boot up, on Fedora 10 though with 2.6.29 testing kernel:

BUG: sleeping function called from invalid context at include/linux/kernel.h:155
in_atomic(): 0, irqs_disabled(): 1, pid: 7655, name: slmodemd
Pid: 7655, comm: slmodemd Tainted: P           2.6.29.1-30.fc10.i686.PAE #1
Call Trace:
 [<c042fd9c>] __might_sleep+0xdf/0xe4
 [<c053bf81>] might_fault+0x12/0x19
 [<c053c0c6>] copy_to_user+0x2c/0xfc
 [<fae32286>] amrmo_read+0x49/0x5f [slamr]
 [<fae3223d>] ? amrmo_read+0x0/0x5f [slamr]
 [<c04a5f86>] vfs_read+0x81/0xdc
 [<c04a607a>] sys_read+0x3b/0x60
 [<c040915f>] sysenter_do_call+0x12/0x34


It says that it is a bug, but I have been up four days and still going :)

[olivares localhost ~]$ uptime
 18:41:51 up 4 days,  2:20,  3 users,  load average: 0.16, 0.13, 0.09
[olivares localhost ~]$ 


Regards,

Antonio 


      


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