From: Tim Chen <tim.c.chen@linux.intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
suresh.b.siddha@intel.com
Subject: Re: 2.6.19-rt14 e1000 shutdown problem
Date: Thu, 21 Dec 2006 12:49:30 -0800 [thread overview]
Message-ID: <1166734170.28359.36.camel@localhost.localdomain> (raw)
In-Reply-To: <20061221201351.GA11625@elte.hu>
On Thu, 2006-12-21 at 21:13 +0100, Ingo Molnar wrote:
> * Tim Chen <tim.c.chen@linux.intel.com> wrote:
>
> > 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
>
> does the patch below solve it for you?
>
> Ingo
>
Yes, the patch took care of the problem. Thanks.
Tim
prev parent reply other threads:[~2006-12-21 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 16:54 2.6.19-rt14 e1000 shutdown problem Tim Chen
2006-12-21 20:13 ` Ingo Molnar
2006-12-21 20:49 ` Tim Chen [this message]
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=1166734170.28359.36.camel@localhost.localdomain \
--to=tim.c.chen@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
/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