From: Patrick McHardy <kaber@trash.net>
To: Andy Whitcroft <apw@shadowen.org>
Cc: linux390@de.ibm.com, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: Re: s390x: getting ipv6 bugs on mainline since 2.6.23-git3
Date: Thu, 18 Oct 2007 11:43:49 +0200 [thread overview]
Message-ID: <47172AD5.2030009@trash.net> (raw)
In-Reply-To: <20071018093556.GT21136@shadowen.org>
Andy Whitcroft wrote:
> Seems we are getting some kind of bug out of our s390x partition (lnxabat1)
> when booting latest mainline releases, specifically since 2.6.23-git3.
>
> Kernel BUG at 0000000000000002 Ýverbose debug info unavailable?
> illegal operation: 0001 Ý#1?
> Modules linked in: dm_mod sit tunnel4 ipv6 qeth ccwgroup qdio dasd_fba_mod dasd_
> eckd_mod dasd_mod
> CPU: 0 Not tainted
> Process ip (pid: 2614, task: 000000003f42f680, ksp: 000000003cf2feb8)
> Krnl PSW : 0704200180000000 0000000000000002 (0x2)
> R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:0 CC:2 PM:0 EA:3
> Krnl GPRS: 0000000000000000 0000000000000000 000000003e6d5d00 000000003e01f000
> 00000000000086dd 000000003cdac144 0000000000000000 0000000000000010
> 000000003e01f000 000000003d97e3c0 0000000100eaaa00 000000003cdac100
> 000000003e6d5d00 00000001018fb1d0 0000000000286da8 000000003cf2f5e8
> Krnl Code:>0000000000000002: 0000 unknown
> 0000000000000004: 0000 unknown
> 0000000000000006: 0000 unknown
> 0000000000000008: 0000 unknown
> 000000000000000a: 0000 unknown
> 000000000000000c: 0000 unknown
> 000000000000000e: 0000 unknown
> 0000000000000010: 0000 unknown
> Call Trace:
> (Ý<0000000000286d60>? neigh_connected_output+0x68/0xfc)
Which network driver are you using? Please post the output of
"ip link list <dev>".
next prev parent reply other threads:[~2007-10-18 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 9:35 s390x: getting ipv6 bugs on mainline since 2.6.23-git3 Andy Whitcroft
2007-10-18 9:43 ` Patrick McHardy [this message]
2007-10-18 10:37 ` Martin Schwidefsky
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=47172AD5.2030009@trash.net \
--to=kaber@trash.net \
--cc=apw@shadowen.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.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).