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

Re: Experimental 2.6.18rc FC5 kernels.



On 18/09/06, Dave Jones <davej redhat com> wrote:
To get some extra testing for the upcoming 2.6.18 release,
I've made some kernels based on 2.6.18rc7git2
You can find them at http://people.redhat.com/davej/kernels/Fedora/FC5/

Please file bugs in bugzilla against FC5, even though these
kernels are somewhat similar to whats in rawhide right now.

Known 'problems':

- For the time being, there aren't any Xen kernels, this will
  be fixed up when time comes for a real update.
- They currently have a bunch of extra debugging options turned
  on so may 'feel' a little slower than the current FC5 kernels.
  This too, will be fixed.
- They'll output a lot more text to the console during boot
  than FC5. Like rawhide, the 'quiet' option has been disabled
  in order to ease debugging. (It's a lot easier to ask someone
  what the last thing on the screen is than to walk people through
  removing the quiet option a hundred times)

These caveats aside, it seems to have survived my tests for the last
day, so it's time for some wider testing.

Thanks,

        Dave

This is what I get for an HP Compaq nx 8220:

Hibernate did not work at all for 2.6.17.* kernels, with this kernel
it shows the report of what is doing but then it complains that it
does not now how to unload the ipw2200 module.

Another issue  analysing /var/log/messages for other output I got in
the first reboot with the new kernel:

=============================================
[ INFO: possible recursive locking detected ]
2.6.17-1.3001.fc5 #1
---------------------------------------------
kseriod/168 is trying to acquire lock:
 (&ps2dev->cmd_mutex#2){--..}, at: [<c05fa8f2>] mutex_lock+0x21/0x24

but task is already holding lock:
 (&ps2dev->cmd_mutex#2){--..}, at: [<c05fa8f2>] mutex_lock+0x21/0x24

other info that might help us debug this:
4 locks held by kseriod/168:
 #0:  (serio_mutex){--..}, at: [<c05fa8f2>] mutex_lock+0x21/0x24
 #1:  (&serio->drv_mutex){--..}, at: [<c05fa8f2>] mutex_lock+0x21/0x24
 #2:  (psmouse_mutex){--..}, at: [<c05fa8f2>] mutex_lock+0x21/0x24
 #3:  (&ps2dev->cmd_mutex#2){--..}, at: [<c05fa8f2>] mutex_lock+0x21/0x24

stack backtrace:
 [<c0403f8e>] show_trace_log_lvl+0x58/0x171
 [<c040456d>] show_trace+0xd/0x10
 [<c040460a>] dump_stack+0x19/0x1b
 [<c0431410>] __lock_acquire+0x75f/0x986
 [<c0431ba8>] lock_acquire+0x4b/0x6b
 [<c05fa788>] __mutex_lock_slowpath+0xb3/0x1fc
 [<c05fa8f2>] mutex_lock+0x21/0x24
 [<c0583f26>] ps2_command+0x82/0x2ff
 [<c0589434>] psmouse_sliced_command+0x1c/0x5a
 [<c058c984>] synaptics_pt_write+0x21/0x45
 [<c0583e00>] ps2_sendbyte+0x48/0xec
 [<c0583fab>] ps2_command+0x107/0x2ff
 [<c0589072>] psmouse_probe+0x1d/0x68
 [<c0589fed>] psmouse_connect+0x100/0x227
 [<c05817e1>] serio_connect_driver+0x1e/0x2e
 [<c0581807>] serio_driver_probe+0x16/0x18
 [<c0542606>] driver_probe_device+0x45/0x92
 [<c054265b>] __device_attach+0x8/0xa
 [<c0541f9f>] bus_for_each_drv+0x3a/0x65
 [<c05426b5>] device_attach+0x58/0x6c
 [<c0541cdd>] bus_attach_device+0x16/0x2b
 [<c054113b>] device_add+0x1f8/0x2de
 [<c058225d>] serio_thread+0xcf/0x28e
 [<c042c2bf>] kthread+0xb0/0xdd
 [<c0401005>] kernel_thread_helper+0x5/0xb
DWARF2 unwinder stuck at kernel_thread_helper+0x5/0xb
Leftover inexact backtrace:
 [<c040456d>] show_trace+0xd/0x10
 [<c040460a>] dump_stack+0x19/0x1b
 [<c0431410>] __lock_acquire+0x75f/0x986
 [<c0431ba8>] lock_acquire+0x4b/0x6b
 [<c05fa788>] __mutex_lock_slowpath+0xb3/0x1fc
 [<c05fa8f2>] mutex_lock+0x21/0x24
 [<c0583f26>] ps2_command+0x82/0x2ff
 [<c0589434>] psmouse_sliced_command+0x1c/0x5a
 [<c058c984>] synaptics_pt_write+0x21/0x45
 [<c0583e00>] ps2_sendbyte+0x48/0xec
 [<c0583fab>] ps2_command+0x107/0x2ff
 [<c0589072>] psmouse_probe+0x1d/0x68
 [<c0589fed>] psmouse_connect+0x100/0x227
 [<c05817e1>] serio_connect_driver+0x1e/0x2e
 [<c0581807>] serio_driver_probe+0x16/0x18
 [<c0542606>] driver_probe_device+0x45/0x92
 [<c054265b>] __device_attach+0x8/0xa
 [<c0541f9f>] bus_for_each_drv+0x3a/0x65
 [<c05426b5>] device_attach+0x58/0x6c
 [<c0541cdd>] bus_attach_device+0x16/0x2b
 [<c054113b>] device_add+0x1f8/0x2de
 [<c058225d>] serio_thread+0xcf/0x28e
 [<c042c2bf>] kthread+0xb0/0xdd
 [<c0401005>] kernel_thread_helper+0x5/0xb


 Do you need further details? Should I add this to bugzilla?
--
José Abílio


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