Messages in this thread | | | Date | Sat, 13 Oct 2007 14:03:19 +0200 | From | Rok Markovic <> | Subject | Re: 2.6.23-rt1 lockup after loading HAL deamon |
| |
Hi
Good news (I hope). With kernel option maxcpus=1, I can not get a lock, so the system is stable and running. Where could be a problem?
Best regards, Rok
Ingo Molnar wrote: >> Hi >> >> I have recompiled kernel with OPROFILE disabled. I am sending in >> attachment /proc/interrupts (i ran it 3 times with 2 sec delay) and >> netconsole log. Lockup in the lock is software made with ./lockup. The >> kernel still locks 4-5minutes after boot without any further messages >> (waited more than 2 minutes). Any ideas? > > no good ideas :-( I suspect this one: > > [ 185.600900] hdc: lost interrupt > > was a side-effect of lockup.c too? > > does the lockup go away if you boot with maxcpus=1? > > Ingo > >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |