Messages in this thread | | | Date | Sun, 2 Mar 2008 21:08:05 +0100 | From | Marcin Slusarz <> | Subject | Re: 2.6.25-rc: complete lockup on boot/start of X (bisected) |
| |
On Sun, Mar 02, 2008 at 12:00:10PM -0800, Arjan van de Ven wrote: > On Sun, 2 Mar 2008 20:00:05 +0100 > Marcin Slusarz <marcin.slusarz@gmail.com> wrote: > > > Hi > > Since early 2.6.25 days I'm having strange lockup on boot. As it > > happens rarely (in ~10% of boots), I couldn't bisect it. No kernel > > panic, SysRq didn't work, so I couldn't provide any useful > > informations to LK community. I hoped someone else would fix it... :) > > > > It's rc3 so I decided to narrow it down myself. I enabled netconsole > > to see whether some other informations are printed before lockup. > > It didn't help, but I noticed that lockup happens much more > > frequenly! (~50%) So I bisected it down to: > > > > 8f4d37ec073c17e2d4aa8851df5837d798606d6f is first bad commit > > commit 8f4d37ec073c17e2d4aa8851df5837d798606d6f > > Author: Peter Zijlstra <a.p.zijlstra@chello.nl> > > Date: Fri Jan 25 21:08:29 2008 +0100 > > > > sched: high-res preemption tick > > > > Use HR-timers (when available) to deliver an accurate preemption > > tick. > > > the only unusual/suspect thing you have is nvidiafb driver; that's not very commonly used. > Can you do a quick try with that thing disabled? Maybe it has some races that are more likely > to trigger after this patch... I switched from vesa to nvidiafb few days ago. Lockup started to happen earlier.
Marcin
| |