netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Simon Arlott <simon@fire.lp0.eu>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: Re: netconsole system freeze when cable unplugged
Date: 10 Mar 2007 14:38:23 +0100	[thread overview]
Message-ID: <p73r6rx9q28.fsf@bingen.suse.de> (raw)
In-Reply-To: <45F1EE12.2070605@simon.arlott.org.uk>

Simon Arlott <simon@fire.lp0.eu> writes:

> On 09/03/07 20:42, Francois Romieu wrote:
> > Simon Arlott <simon@fire.lp0.eu> :
> >> When I unplug the cable the system just stops responding to
> >> anything, at all. No message is printed to the console when the
> >> cable is plugged back in.
> > rtl8139_interrupt (spin_lock(&tp->lock))
> > -> rtl8139_weird_interrupt
> >    -> rtl_check_media
> >       -> mii_check_media (printk(KERN_INFO "%s: link down\n", ...))
> >          [netpoll stuff here]
> >          -> rtl8139_poll_controller
> >             -> rtl8139_interrupt
> >                *deadlock*
> > See below for my random stuff of the day. Feel free to open a PR at
> > bugzilla.kernel.org if the issue does not go away.
> 
> The patch doesn't fix it, nothing changes. I'm not sure how this can
> be debugged if printk won't work...

earlyprintk can be called directly (early_printk()) and should
work. It won't log over the network of course.

-Andi

  reply	other threads:[~2007-03-10 12:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09 19:35 netconsole system freeze when cable unplugged Simon Arlott
2007-03-09 20:42 ` Francois Romieu
2007-03-09 23:30   ` Simon Arlott
2007-03-10 13:38     ` Andi Kleen [this message]
2007-03-10 14:06       ` Simon Arlott
2007-03-11  7:50         ` Andi Kleen
2007-03-10 20:31   ` Matt Mackall

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=p73r6rx9q28.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    --cc=simon@fire.lp0.eu \
    /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).