From: "John W. Linville" <linville@tuxdriver.com>
To: "news.gmane.org" <francois.valenduc@tvcablenet.be>
Cc: netdev@vger.kernel.org
Subject: Re: Kernel panic with the b44 driver in 2.6.35-rc1
Date: Tue, 1 Jun 2010 09:33:19 -0400 [thread overview]
Message-ID: <20100601133318.GA26701@tuxdriver.com> (raw)
In-Reply-To: <4C0414F3.8030409@tvcablenet.be>
On Mon, May 31, 2010 at 09:58:43PM +0200, news.gmane.org wrote:
> I have a kernel panic at startup with the b44 driver with the 2.6.35-rc1
> kernel. I have submitted a bug report (see
> https://bugzilla.kernel.org/show_bug.cgi?id=16074) but until know, I
> din't get any answer yet. Does anybody knows what's happening. I have
> tried several git-bisect run but I didn't find any conclusive result.
> The first bad-commit was different each time and if I revert it, the
> problem still occurs anyway.
This patch is already on its way to Linus -- it should fix the problem
you are seeing:
commit da1fdb02d9200ff28b6f3a380d21930335fe5429
Author: Christoph Fritz <chf.fritz@googlemail.com>
Date: Fri May 28 10:45:59 2010 +0200
ssb: fix NULL ptr deref when pcihost_wrapper is used
Ethernet driver b44 does register ssb by it's pcihost_wrapper
and doesn't set ssb_chipcommon. A check on this value
introduced with commit d53cdbb94a52a920d5420ed64d986c3523a56743
and ea2db495f92ad2cf3301623e60cb95b4062bc484 triggers:
BUG: unable to handle kernel NULL pointer dereference at 00000010
IP: [<c1266c36>] ssb_is_sprom_available+0x16/0x30
Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-06-01 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 19:58 Kernel panic with the b44 driver in 2.6.35-rc1 news.gmane.org
2010-06-01 13:33 ` John W. Linville [this message]
2010-06-01 18:06 ` François Valenduc
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=20100601133318.GA26701@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=francois.valenduc@tvcablenet.be \
--cc=netdev@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.