From: Bob Gill <gillb4@telusplanet.net>
To: Bongani Hlope <bonganilinux@mweb.co.za>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: test3 responsible for atomic blast!
Date: 11 Aug 2003 11:14:41 -0600 [thread overview]
Message-ID: <1060622081.4200.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20030810224853.4a291e6e.bonganilinux@mweb.co.za>
CONFIG_DEBUG_SPINLOCK_SLEEP is not set:
(but thank you for replying anyway).
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_SLAB=y
# CONFIG_DEBUG_IOVIRT is not set
# CONFIG_MAGIC_SYSRQ is not set
CONFIG_DEBUG_SPINLOCK=y
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_DEBUG_HIGHMEM=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
CONFIG_FRAME_POINTER=y
CONFIG_X86_EXTRA_IRQS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
>On Sun, 2003-08-10 at 14:48, Bongani Hlope wrote:
> On Sun, 10 Aug 2003 14:28:01 -0600
> Bob Gill <gillb4@telusplanet.net> wrote:
>
> > The really good news is 2.6.0-test3 is *much* more efficient at
> > delivering error messages than earlier versions!
> > The following is from /var/log/messages:
>
> 8<
>
> > unknown_bootoption+0x0/0xfa
> > Aug 10 14:07:38 localhost kernel:
> > Aug 10 14:07:38 localhost kernel: bad: scheduling while atomic!
> > Aug 10 14:07:38 localhost kernel: Call Trace:
> > Aug 10 14:07:38 localhost kernel: [<c0105000>] rest_init+0x0/0xf5
> > Aug 10 14:07:38 localhost kernel: [<c011d729>] schedule+0x6e4/0x6e9
> > Aug 10 14:07:38 localhost kernel: [<c0107269>] default_idle+0x0/0x2c
> > Aug 10 14:07:38 localhost kernel: [<c0105000>] rest_init+0x0/0xf5
> > Aug 10 14:07:38 localhost kernel: [<c0107269>] default_idle+0x0/0x2c
> > Aug 10 14:07:38 localhost kernel: [<c0105000>] rest_init+0x0/0xf5
> > Aug 10 14:07:38 localhost kernel: [<c0107308>] cpu_idle+0x38/0x3a
> > Aug 10 14:07:38 localhost kernel: [<c039672a>] start_kernel+0x1bd/0x215
> > Aug 10 14:07:38 localhost kernel: [<c039643f>]
> > unknown_bootoption+0x0/0xfa
> >
> > ... the bad: scheduling while atomic! keeps blasting away at my screen
> > until I shutdown. I *do* shutdown right away before the system decides
> > to really hang (and take out my root partition on next startup like it
> > has done when I get these atomic crashes). Long before any real testing
> > begins, nasty bugs like this have to go!
> >
> >
> > --
> > Bob Gill <gillb4@telusplanet.net>
>
> The system wont really hang (and take out you root partition) disable CONFIG_DEBUG_SPINLOCK_SLEEP (kernel hacking -> Sleep-inside-spinlock checking) on you .config if you want them to go away.
--
Bob Gill <gillb4@telusplanet.net>
next prev parent reply other threads:[~2003-08-11 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-10 20:28 test3 responsible for atomic blast! Bob Gill
2003-08-10 20:48 ` Bongani Hlope
2003-08-11 17:14 ` Bob Gill [this message]
2003-08-10 21:04 ` Rahul Karnik
2003-08-11 17:07 ` Bob Gill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1060622081.4200.7.camel@localhost.localdomain \
--to=gillb4@telusplanet.net \
--cc=bonganilinux@mweb.co.za \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox