From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: two NICs -> kernel crash ?
Date: Tue, 06 Mar 2012 17:00:34 -0800 [thread overview]
Message-ID: <jj6bvi$oca$1@dough.gmane.org> (raw)
In-Reply-To: <1331028495.4662.0@numa-i>
On 03/06/2012 02:08 AM, Helmut Jarausch wrote:
> Hi,
>
> on my HP625 I run a bleeding edge Gentoo (kernel 3.3-rc6).
>
> If the notebook is connected by an ethernet cable, the net comes up
> just fine.
>
> If I disconnect it from ethernet and start net.wlan0, the WLAN comes
> up just fine.
>
> BUT, if it's connect to ethernet, and net.eth0 has been started, the
> kernel crashes badly (i.e. no SysRq anymore) if I start net.wlan0 in
> addition.
>
> Is this a configuration error by me or a kernel bug. The WLAN card is
> a Broadcom BCM4313 with the BRCMSMAC driver.
Well, this is just my non-expert opinion, but I feel that any knob
that can be twiddled by a user should never crash the kernel, ever.
However, the kernel devs might agree with my wife about my opinions ;)
Do kernels from the stable branch also crash?
next prev parent reply other threads:[~2012-03-07 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 10:08 [gentoo-user] two NICs -> kernel crash ? Helmut Jarausch
2012-03-07 1:00 ` walt [this message]
2012-03-07 14:08 ` Mark Knecht
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='jj6bvi$oca$1@dough.gmane.org' \
--to=w41ter@gmail.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox