Testing - kernel-2.6.9-1.715_FC3 panics on GUI Exit
Davide Rossetti
davide.rossetti at roma1.infn.it
Wed Dec 29 09:14:45 UTC 2004
Dan Williams wrote:
>On Wed, 2004-12-15 at 07:01 -0500, Jim Cornette wrote:
>
>
>>The problem seems to be triggered when exiting the GUI. When booting in
>>runlevel 5 and logging out of X, the hourglass stays in the center of
>>the screen and the caplocks light flashes.
>>When booted into runlevel 3 and closing down, the text on the screen
>>displays a series of numbers and states that it has a panic condition
>>and the cap-locks light is flashing.
>>
>>
>
>Known issue and has been fixed already in later kernels than FC3 (.906
>and later I believe), and at some point I assume it will be pushed down
>to FC3.
>
>Do you happen to have a ThinkPad T31, or a Radeon graphics card?
>
>Does your panic backtrace look anything like this?
>------------------
>Nov 7 22:22:30 localhost kernel: Call Trace:
>Nov 7 22:22:30 localhost kernel: [<c0156447>] handle_mm_fault+0xe5/0x233
>Nov 7 22:22:30 localhost kernel: [<c01783c3>] path_lookup+0xff/0x12f
>Nov 7 22:22:30 localhost kernel: [<c0178aa2>] open_namei+0x99/0x581
>Nov 7 22:22:30 localhost kernel: [<c01662be>] filp_open+0x23/0x3c
>Nov 7 22:22:30 localhost kernel: [<c0309b32>] __cond_resched+0x14/0x3b
>Nov 7 22:22:30 localhost kernel: [<c01e132e>] direct_strncpy_from_user+0x3e/0x5d
>Nov 7 22:22:30 localhost kernel: [<c01667e7>] sys_open+0x31/0x7d
>Nov 7 22:22:30 localhost kernel: [<c030b3c3>] syscall_call+0x7/0xb
>------------------
>
>
>
I have an Intel 830 ASUS laptop... and keep on having problems with
1.715 kernels... better that previous kernels (as in
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=142240). before it
oops'd at gdm restart. now it locks down at shutdown time with spin_lock
msgs in console... sysrq- is not active so at next boot I loose the
dump. let me know if I can be of any help
More information about the test
mailing list