From: Johannes Berg <johannes@sipsolutions.net>
To: linux-kernel@vger.kernel.org
Cc: "David S. Miller" <davem@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Eric Lemoine <eric.lemoine@gmail.com>
Subject: sungem hangs in atomic if netconsole enabled but no carrier
Date: Tue, 20 Dec 2005 13:08:58 +0100 [thread overview]
Message-ID: <1135080538.3937.3.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
I've been debugging some issues and wondered why I got hangs in random
places in the code. It turns out that the problem is that I still had
netconsole enabled even though I have no network at the moment. So what
I had was:
* sungem compiled in
* netconsole=.... as command line
* no network cable plugged in
sungem does recognise this situation and says that waiting for carrier
timed out. However, later, when I printk() in with interrupts disabled,
the system hangs after printing out a few lines to the console (I think
it's more than one, not sure though, might be just a single one).
Turns out that if I remove the netconsole=... option to my kernel, all
works fine and the system no longer hangs. Obviously not plugging in a
network cable is pretty useless when netconsole is turned on, but I
think it should not hang the system completely. So far I haven't been
able to figure out where it actually hangs and don't even know how to do
so -- I'm open for suggestions on how to find out why/where it hangs or
even fixes.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2005-12-20 12:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 12:08 Johannes Berg [this message]
2005-12-20 21:18 ` sungem hangs in atomic if netconsole enabled but no carrier Benjamin Herrenschmidt
2005-12-20 21:23 ` David S. Miller
2005-12-20 22:19 ` Francois Romieu
2005-12-20 22:59 ` Benjamin Herrenschmidt
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=1135080538.3937.3.camel@localhost \
--to=johannes@sipsolutions.net \
--cc=benh@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=eric.lemoine@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.