From: Shan Wei <shanwei@cn.fujitsu.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, m.kloucek.m@gmail.com
Subject: Re: pandaboard brctl oops
Date: Tue, 02 Aug 2011 10:24:22 +0800 [thread overview]
Message-ID: <4E375FD6.4090404@cn.fujitsu.com> (raw)
In-Reply-To: <201108012325.17312.marek.vasut@gmail.com>
hi
Marek Vasut wrote, at 08/02/2011 05:25 AM:
> Hi,
>
> recently a friend of mine sent me this backtrace. I put him in CC so please any
> subsequent questions shall be forwarded to him.
>
> He claims this happens on pandaboard.
>
> Cheers
>
> root@box:~# brctl addbr br0
> root@box:~# brctl addif br0 eth0
> [ 77.795776] Unable to handle kernel NULL pointer dereference at virtual
> address 00000000
> [ 77.804321] pgd = ee8d4000
> [ 77.807312] [00000000] *pgd=af8e6831, *pte=00000000, *ppte=00000000
> [ 77.813995] Internal error: Oops: 80000007 [#1] SMP
> [ 77.819122] last sysfs file: /sys/devices/virtual/net/br0/uevent
> [ 77.825439] Modules linked in: bridge stp llc wl12xx_sdio wl12xx
> [ 77.831787] CPU: 0 Not tainted (2.6.39.2-omap4 #3)
> [ 77.837188] PC is at 0x0
> [ 77.839904] LR is at br_change_mtu+0x64/0x7c [bridge]
This one has been fixed in latest kernel.
commit 6407d74c5106bb362b4087693688afd34942b094
Author: Alexander Holler <holler@ahsoftware.de>
Date: Tue Jun 7 00:51:35 2011 -0700
bridge: provide a cow_metrics method for fake_ops
Like in commit 0972ddb237 (provide cow_metrics() methods to blackhole
dst_ops), we must provide a cow_metrics for bridges fake_dst_ops as
well.
This fixes a regression coming from commits 62fa8a846d7d (net: Implement
read-only protection and COW'ing of metrics.) and 33eb9873a28 (bridge:
initialize fake_rtable metrics)
ip link set mybridge mtu 1234
--
Best Regards
-----
Shan Wei
next prev parent reply other threads:[~2011-08-02 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 21:25 pandaboard brctl oops Marek Vasut
2011-08-02 2:24 ` Shan Wei [this message]
2011-08-02 21:18 ` Miloš GymRK
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=4E375FD6.4090404@cn.fujitsu.com \
--to=shanwei@cn.fujitsu.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=m.kloucek.m@gmail.com \
--cc=marek.vasut@gmail.com \
--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 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).