From: Marcin Dalecki <dalecki@evision.ag>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: martin@dalecki.de, "Bill Huey (Hui)" <billh@gnuppy.monkey.org>,
linux-kernel@vger.kernel.org
Subject: Re: bad: schedule() with irqs disabled! (+ ksymoops)
Date: Thu, 08 Aug 2002 12:39:35 +0200 [thread overview]
Message-ID: <3D524A67.7030407@evision.ag> (raw)
In-Reply-To: Pine.LNX.4.44.0208081218160.24255-100000@linux-box.realnet.co.sz
Uz.ytkownik Zwane Mwaikambo napisa?:
> On Thu, 8 Aug 2002, Marcin Dalecki wrote:
>
>
>>I can report pretty the same:
>>
>>Trace; c0113f84 <try_to_wake_up+104/110>
>>Trace; c0113fa6 <wake_up_process+16/20>
>>Trace; c011d1f7 <do_softirq+a7/c0>
>
>
> What to do? Looks like do_softirq needs some work, also reading the
> comments at the beginning of kernel/softirq.c is it preempt safe? This is
> from looking at 'cpu = smp_processor_id' usage in do_softirq.
I think that you are right do_softirq is apparently in toruble.
Nowever the above only occurs when, I'm working on my notebook through
ssh X11 port forward login. So in this case there are likely
many overlapping IDE/eth0 IRQ comming through. And it's *really* the
eth part that matters. So it could simply be that the e8139too
driver deserves review in regards of proper lock protection.
next prev parent reply other threads:[~2002-08-08 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 9:33 bad: schedule() with irqs disabled! Bill Huey
2002-08-08 9:40 ` bad: schedule() with irqs disabled! (+ ksymoops) Bill Huey
2002-08-08 9:48 ` Marcin Dalecki
2002-08-08 10:25 ` Zwane Mwaikambo
2002-08-08 10:39 ` Marcin Dalecki [this message]
2002-08-08 15:18 ` Paul Larson
2002-08-08 13:56 ` Ingo Molnar
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=3D524A67.7030407@evision.ag \
--to=dalecki@evision.ag \
--cc=billh@gnuppy.monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
--cc=zwane@linuxpower.ca \
/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