From: Tim Chen <tim.c.chen@linux.intel.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.19-rt14 e1000 shutdown problem
Date: Tue, 19 Dec 2006 08:54:39 -0800 [thread overview]
Message-ID: <1166547279.28359.23.camel@localhost.localdomain> (raw)
Ingo,
While trying out the 2.6.19.1-rt14 kernel with a
x86_64 system with Clovertown processor, it hung when it
was shutting down e1000 ethernet interface running the command:
/sbin/ip link set dev eth0 down
Same problem was also seen for 2.6.19.1-rt15. The default
kernel from your RPM was used. Sysreq was still working and
call trace of the ip command using Sysreq-prtscr-t is listed below:
ip D [ffff810139201040] ffff81013fe47840 0 3526 3433
(NOTLB)
ffff81012ce75ba8 0000000000000086 0000000000000007 0000000000000297
00000000000c4994 ffff810139201278 ffff810139201040 ffff81013fe47800
0000005681bed269 0000000400000080 ffff81013fe47800 00000004802df143
Call Trace:
[<ffffffff80265da0>] schedule+0xd8/0xfc
[<ffffffff802a0bab>] flush_cpu_workqueue+0x72/0xa7
[<ffffffff802a0e13>] flush_workqueue+0x59/0x81
[<ffffffff802a0f79>] schedule_on_each_cpu+0xe6/0xfd
[<ffffffff802e33ca>] filevec_add_drain_all+0x12/0x14
[<ffffffff8030bb38>] remove_proc_entry+0xaf/0x25a
[<ffffffff802c720d>] unregister_handler_proc+0x43/0x48
[<ffffffff802c56c4>] free_irq+0xdd/0x117
[<ffffffff88133101>] :e1000:e1000_free_irq+0x22/0x3b
[<ffffffff88135c88>] :e1000:e1000_close+0x4d/0xb9
[<ffffffff80429735>] dev_close+0x5b/0x7c
[<ffffffff80429ab9>] dev_change_flags+0x64/0x139
[<ffffffff8046048b>] devinet_ioctl+0x252/0x5e1
[<ffffffff80460ac1>] inet_ioctl+0x71/0x8f
[<ffffffff80422042>] sock_ioctl+0x1d7/0x1ff
[<ffffffff802433b8>] do_ioctl+0x27/0x74
[<ffffffff80231339>] vfs_ioctl+0x263/0x280
[<ffffffff8024dfb7>] sys_ioctl+0x5f/0x82
[<ffffffff8026042c>] tracesys+0x151/0x1c5
[<0000003055ac6267>]
Tim
next reply other threads:[~2006-12-19 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 16:54 Tim Chen [this message]
2006-12-21 20:13 ` 2.6.19-rt14 e1000 shutdown problem Ingo Molnar
2006-12-21 20:49 ` Tim Chen
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=1166547279.28359.23.camel@localhost.localdomain \
--to=tim.c.chen@linux.intel.com \
--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