From: Amit Shah <amitshah@gmx.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RT-preempt-2.6.10-rc1-mm2-V0.7.11 hang
Date: Sat, 6 Nov 2004 20:54:39 +0530 [thread overview]
Message-ID: <200411062054.40384.amitshah@gmx.net> (raw)
In-Reply-To: <20041106120525.GA15363@elte.hu>
On Saturday 06 Nov 2004 17:35, Ingo Molnar wrote:
> found the bug(s), the e1000 driver disabled interrupts on
> PREEMPT_REALTIME too, and the debug-message printout had a bug as well.
> Found a similar problem in the tg3 driver too. Could you check out
> -V0.7.15 that i've just uploaded to:
>
> http://redhat.com/~mingo/realtime-preempt/
>
> does this work any better? [you'll still get the e100 message but that
> is harmless.]
Yes; solved. (I'm using -18). Thanks.
However, I get this:
IRQ#18 thread RT prio: 46.
ifconfig/4106: BUG in enable_irq at kernel/irq/manage.c:112
[<c0107fc0>] dump_stack+0x1e/0x22 (20)
[<c0142a9b>] enable_irq+0xeb/0xf0 (52)
[<f892b290>] e100_up+0x111/0x20c [e100] (48)
[<f892c4d7>] e100_open+0x2c/0x71 [e100] (32)
[<c027747d>] dev_open+0x78/0x86 (28)
[<c0278aed>] dev_change_flags+0x56/0x127 (36)
[<c02b4538>] devinet_ioctl+0x242/0x5bc (104)
[<c02b66aa>] inet_ioctl+0x5a/0x9a (28)
[<c026e2a4>] sock_ioctl+0xbb/0x21f (32)
[<c01777bf>] sys_ioctl+0xdc/0x241 (44)
[<c0107153>] syscall_call+0x7/0xb (-8124)
---------------------------
| preempt count: 00000002 ]
| 2-level deep critical section nesting:
----------------------------------------
.. [<c02c81b8>] .... _raw_spin_lock_irqsave+0x1d/0x7a
.....[<c01429d8>] .. ( <= enable_irq+0x28/0xf0)
.. [<c013b8c8>] .... print_traces+0x18/0x4c
.....[<c0107fc0>] .. ( <= dump_stack+0x1e/0x22)
IRQ#17 thread RT prio: 45.
IRQ#4 thread RT prio: 44.
IRQ#3 thread RT prio: 43.
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
IRQ#8 thread RT prio: 42.
But as you say, this should be harmless.
>
> Ingo
Amit.
--
Amit Shah
http://amitshah.nav.to/
next prev parent reply other threads:[~2004-11-06 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 13:07 Amit Shah
2004-11-05 13:46 ` Ingo Molnar
2004-11-05 14:42 ` Norberto Bensa
2004-11-05 14:58 ` K.R. Foley
2004-11-05 14:59 ` Amit Shah
2004-11-05 15:24 ` Amit Shah
2004-11-05 18:13 ` Adam Heath
2004-11-05 19:17 ` Adam Heath
2004-11-06 7:24 ` Ingo Molnar
2004-11-06 8:44 ` Amit Shah
2004-11-06 12:05 ` Ingo Molnar
2004-11-06 15:24 ` Amit Shah [this message]
2004-11-06 16:30 ` 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=200411062054.40384.amitshah@gmx.net \
--to=amitshah@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®