From: Jarek Poplawski <jarkao2@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Denys Fedoryshchenko <denys@visp.net.lb>,
Bart Van Assche <bart.vanassche@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: BUG/ spinlock lockup, 2.6.24
Date: Fri, 15 Feb 2008 22:03:26 +0100 [thread overview]
Message-ID: <47B5FE1E.5080804@gmail.com> (raw)
In-Reply-To: <47B5F462.40603@gmail.com>
Jarek Poplawski wrote, On 02/15/2008 09:21 PM:
> Denys Fedoryshchenko wrote, On 02/15/2008 08:42 PM:
> ...
>
>> I have similar crashes on completely different hardware with same job (QOS),
>> so i think it is actually some nasty bug in networking.
>
> Maybe you could try with some other debugging options? E.g. since lockdep
> doesn't help - turn this off. Instead try some others, like these:
...On the other hand this:
> Feb 15 15:50:17 217.151.X.X [1521315.068984] BUG: spinlock lockup on CPU#1,
> ksoftirqd/1/7, f0551180
seems to point just at spinlock lockup, so it's more about the full report.
I wonder if this patch to prink could help here:
author Ingo Molnar <mingo at elte.hu>
Fri, 25 Jan 2008 20:07:58 +0000 (21:07 +0100)
printk: make printk more robust by not allowing recursion
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=32a76006683f7b28ae3cc491da37716e002f198e
Jarek P.
next prev parent reply other threads:[~2008-02-15 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 15:19 BUG/ spinlock lockup, 2.6.24 Denys Fedoryshchenko
2008-02-15 15:24 ` Bart Van Assche
2008-02-15 19:42 ` Denys Fedoryshchenko
2008-02-15 20:21 ` Jarek Poplawski
2008-02-15 21:03 ` Jarek Poplawski [this message]
2008-02-15 22:49 ` Jarek Poplawski
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=47B5FE1E.5080804@gmail.com \
--to=jarkao2@gmail.com \
--cc=bart.vanassche@gmail.com \
--cc=denys@visp.net.lb \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.