mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yaroslav Halchenko <mutt@onerussian.com>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: crash of -bk17.  bad: scheduling while atomic!
Date: Sat, 11 Sep 2004 11:31:36 -0400	[thread overview]
Message-ID: <20040911153136.GG6735@washoe.rutgers.edu> (raw)

Dear Kernel people

I decided to give a try to recent rc1-bk17 moving from 2.6.8-rc3-bk3.

Computer boots but crashes not long after with

Sep 11 11:04:10 ravana kernel: bad: scheduling while atomic!
Sep 11 11:04:10 ravana kernel:  [schedule+1507/1520] schedule+0x5e3/0x5f0
Sep 11 11:04:10 ravana kernel:  [__do_softirq+186/208] __do_softirq+0xba/0xd0
Sep 11 11:04:10 ravana kernel:  [preempt_schedule+42/80] preempt_schedule+0x2a/0x50
Sep 11 11:04:10 ravana kernel:  [udp_sendmsg+753/1696] udp_sendmsg+0x2f1/0x6a0
Sep 11 11:04:10 ravana kernel:  [skb_copy_and_csum_bits+102/752] skb_copy_and_csum_bits+0x66/0x2f0
Sep 11 11:04:10 ravana kernel:  [__wake_up_common+65/112] __wake_up_common+0x41/0x70
Sep 11 11:04:10 ravana kernel:  [inet_sendmsg+77/96] inet_sendmsg+0x4d/0x60
Sep 11 11:04:10 ravana kernel:  [sock_sendmsg+229/256] sock_sendmsg+0xe5/0x100
....

full logs files for boot part of syslog and crash part (which seems to
be looping and producing huge log files) can be found at

http://www.onerussian.com/Linux/bugs/bug.bk17/

I'm going to try pure rc1 version...

-- 
                                  .-.
=------------------------------   /v\  ----------------------------=
Keep in touch                    // \\     (yoh@|www.)onerussian.com
Yaroslav Halchenko              /(   )\               ICQ#: 60653192
                   Linux User    ^^-^^    [175555]
             Key  http://www.onerussian.com/gpg-yoh.asc
GPG fingerprint   3BB6 E124 0643 A615 6F00  6854 8D11 4563 75C0 24C8


             reply	other threads:[~2004-09-11 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-11 15:31 Yaroslav Halchenko [this message]
2004-09-12  1:06 ` David S. Miller

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=20040911153136.GG6735@washoe.rutgers.edu \
    --to=mutt@onerussian.com \
    --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

all inboxes | Powered by JetHome®