From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcus Better Subject: Re: [Bugme-new] [Bug 10327] New: keyboard stops responding after "ifdown eth0" Date: Wed, 26 Mar 2008 10:19:40 +0100 Message-ID: <47EA152C.6000008@better.se> References: <20080325143941.300d415f.akpm@linux-foundation.org> <47E9721C.2000306@better.se> <47E99258.3060005@s5r6.in-berlin.de> <20080325171608.509f4ca7.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Stefan Richter , bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org, linux-input@vger.kernel.org, netdev@vger.kernel.org To: Andrew Morton Return-path: In-Reply-To: <20080325171608.509f4ca7.akpm@linux-foundation.org> Sender: linux-input-owner@vger.kernel.org List-Id: netdev.vger.kernel.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