Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d
- To: martin-eric.racine@iki.fi
- Cc: 677655@bugs.debian.org, control@bugs.debian.org
- Subject: Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d
- From: Moritz Muehlenhoff <jmm@inutil.org>
- Date: Fri, 12 Jul 2013 09:46:54 +0200
- Message-id: <[🔎] 20130712074654.GA3865@inutil.org>
- Reply-to: Moritz Muehlenhoff <jmm@inutil.org>, 677655@bugs.debian.org
- In-reply-to: <20120616084815.GA24896@burratino>
- References: <20120615184119.2754.26157.reportbug@geode.lan> <20120615185243.GA11941@burratino> <CAPZXPQc1FtSzz_j9ZwrbCULdnO-aqShdfR7uWUoG1wCxZ=C-tg@mail.gmail.com> <1339807723.4942.134.camel@deadeye.wl.decadent.org.uk> <20120616010042.GD3547@burratino> <20120616022318.GC3201@burratino> <CAPZXPQcsOE=E_KNsbfu_0Vfm4Q00+7xD=U+bP_3H941gJs=f9Q@mail.gmail.com> <20120616084815.GA24896@burratino>
reassign 677655 src:linux
thanks
On Sat, Jun 16, 2012 at 03:48:45AM -0500, Jonathan Nieder wrote:
> Martin-Éric Racine wrote:
>
> > Yup, this issue returns every now and then on the exact same host
> > (which was recently migrated from Ubuntu to Debian, now that Ubuntu
> > stopped supporting anything older than non-PAE 686 hardware), whenever
> > someone touches the inode code again. The nice thing, this time, is
> > that it has become non-fatal; the kernel simply reports the oops and
> > continues operating.
>
> Thanks for the background. That would have indeed been useful context
> in the original report (though perhaps it had been long enough since
> the last appearance that you had forgotten).
>
> If I have any more questions, I'll ask them upstream.
Does this still occur with current kernels?
Cheers,
Moritz
Reply to: