From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hannes Frederic Sowa Subject: Re: [BUG] 3.12.0-rcX IPv6 panic Date: Mon, 21 Oct 2013 17:52:52 +0200 Message-ID: <20131021155252.GA24158@order.stressinduktion.org> References: <20131021131846.GA5769@gherkin.frus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org To: Bob Tracy Return-path: Content-Disposition: inline In-Reply-To: <20131021131846.GA5769@gherkin.frus.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Hi! On Mon, Oct 21, 2013 at 08:18:46AM -0500, Bob Tracy wrote: > Actually, a regression: the 3.11 kernel is rock-solid stable on my > Alpha. > > Beginning with 3.12.0-rc1, I can reliably trigger a kernel panic by > executing the gogo6.net "gw6c" IPv6 client program. If the networking > layer is active, an "Oops" will eventually (within a day) occur regardless > of whether I attempt to run "gw6c". 3.12.0-rcX is stable as long as I > leave networking completely disabled. The error has persisted up through > -rc6. Apologies for not mentioning this earlier, but the state of my > PWS-433au has been questionable, and I wanted to make sure I had a > legitimate bug sighting. > > I'll have to transcribe the panic backtrace by hand: nothing makes it > into any of the system logs :-(. I *can* recall that every backtrace > I've seen thus far has included one of the skb_copy() variants near the > top of the list (first or second function). Try to capture the panic via serial console. Otherwise a picture would give us a first hint. Please watch out for lines like skb_(over|under)_panic. gw6c is a tunnel client? Can you post ip -6 tunnel ls? (Also please send networking bugs to netdev@). Greetings, Hannes