From: Marcus Better <marcus@better.se>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 10327] New: keyboard stops responding after "ifdown eth0"
Date: Wed, 26 Mar 2008 10:19:40 +0100 [thread overview]
Message-ID: <47EA152C.6000008@better.se> (raw)
In-Reply-To: <20080325171608.509f4ca7.akpm@linux-foundation.org>
Andrew Morton wrote:
> ( sleep 10 ; echo t > /proc/sysrq-trigger ) &
> ifdown eth0
>
>
> - See if the sysrq-t output made it to /var/log/messages
No, not a word. It hung after printing this:
...
DHCPRELEASE ...
send_packet: Network is unreachable
send_packet: please consult README ...
sky2 eth0: disabling interface
~# sky2 eth0: enabling interface
I'm running ifplugd, but this time there was no network cable connected.
Also ran from virtual console this time, the keyboard locked up like before.
SysRq keys work, so I could do sysrq-s, sysrq-b. Also pressed sysrq-t
before rebooting.
Any use trying netconsole? Can I run it over the wireless interface?
Marcus
next prev parent reply other threads:[~2008-03-26 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10327-10286@http.bugzilla.kernel.org/>
2008-03-25 21:39 ` [Bugme-new] [Bug 10327] New: keyboard stops responding after "ifdown eth0" Andrew Morton
2008-03-25 21:43 ` Marcus Better
2008-03-26 0:01 ` Stefan Richter
2008-03-26 0:16 ` Andrew Morton
2008-03-26 9:19 ` Marcus Better [this message]
2008-03-26 17:29 ` Andrew Morton
2008-04-11 11:12 ` Marcus Better
2008-03-26 8:47 ` [Bugme-new] " Marcus Better
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=47EA152C.6000008@better.se \
--to=marcus@better.se \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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;
as well as URLs for NNTP newsgroup(s).