From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: jlmales@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Failure - 3.4.24
Date: Tue, 29 Jan 2013 22:32:53 +0100 [thread overview]
Message-ID: <51084005.2050506@linutronix.de> (raw)
In-Reply-To: <20130128145708.3c241dc8.jlmales@gmail.com>
On 01/28/2013 08:57 PM, John L. Males wrote:
> I was not suggesting you are responsible for the bug at all. On
Okay then :)
> I have no custom patches to the kernel.
okay.
> I looked at the RedHat bug 468794. The bug seems to indicate it
> was never fixed. The bug was reported against
> 2.6.27.4-47.rc3.fc10.i686 #1 on 2008-10-27 21:34:04 EDT and was
> closed 2009-12-18 01:40:33 EST. The differences are a bug of at
> least 5 years ago and a 2.6 kernel verses 5 years later and current
> at time stable kernel 3.4.24 from kernel.org with no patches I
> applied when this kernel failure I encountered occurred. If this
> is the same bug then there is a bug that may have been about for a
> while or perhaps a regression. The fact is the RedHat bug 468794
> was never fixed.
Lets see. According to the backtrace it seems that the kernel was not
able to write the buffer back to disk. The RH bug says that someone
unplugged the device without an unmount of the disk.
My question are:
- what were you doing by the time this happened?
- can you reproduce it (reliably)?
- Is this *new* meaning is there a kernel where did not happen?
Sebastian
next prev parent reply other threads:[~2013-01-29 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 23:42 Kernel Failure - 3.4.24 John L. Males
2013-01-27 16:14 ` Sebastian Andrzej Siewior
2013-01-28 19:57 ` Re[02]: " John L. Males
2013-01-29 21:32 ` Sebastian Andrzej Siewior [this message]
2013-01-30 18:58 ` Re[04]: " John L. Males
2014-05-16 21:30 ` Kernel Failure - 3.4.24 Similar USB MO To 3.4.89 Kernel Failure John L. Males
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=51084005.2050506@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jlmales@gmail.com \
--cc=linux-kernel@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