On Monday 13 June 2005 02:09, Ingo Molnar wrote:
>* Gene Heskett <[email protected]> wrote:
>> but had to interrupt the boot & go back to 48-13 as I was drowning
>> in a near DOS caused by:
>>
>> Jun 12 21:54:16 coyote kernel: BUG: scheduling while atomic:
>> softirq-timer/0/0x10000100/3 Jun 12 21:54:16 coyote kernel: caller
>> is __cond_resched+0x3d/0x50
>
>ok, fixed this one - does -48-19 work for you? (PREEMPT_DESKTOP was
>broken by the new split-softirqs code)
>
> Ingo
Its running apparently ok Ingo, but it fussed during the boot because
CONFIG_LATENCY_TRACE was still on, so my ./makeit script is running
again after turning that off. I'd turned its parent in the xconfig
display off mistakenly figureing that got the child. kconfig
miss-cue?
Rebooted to it, no warnings. Glitch reports as they are found. :-)
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.35% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]