The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Fabio Coatti <fabio.coatti@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3.10.9 Crash
Date: Mon, 26 Aug 2013 13:15:41 +0200	[thread overview]
Message-ID: <3209444.Rv0zN2ZK8h@calvin> (raw)
In-Reply-To: <20130826105930.GA25331@kroah.com>

In data lunedì 26 agosto 2013 03:59:30, Greg Kroah-Hartman ha scritto:
> On Mon, Aug 26, 2013 at 10:36:30AM +0200, Fabio Coatti wrote:
> > Hi all,
> > I'm remotely managing a 3.10.9 server and this morning I found it locked.
> > The only data I could gather is a screenshot (thru AMT interface).
> > I've ran it thru gocr and this is the result (some char got garbled but
> > the
> > bulk is ok).
> > The machine is pretty new and stable, nothin like this happened with
> > previous 3.10.X
> 
> Can you reproduce this easily?  If so, can you use 'git bisect' to track
> down the offending patch?


I wish I could :). I thinked of it, but looking at logs I spotted no clues 
about reproducing the issue. The server is pretty unused, the only thing that 
I can imagine happening at more or less the time of crash is a logrotation. I 
launched it again with no problems, but of course things can be different.
Right now I'm using that server with no problems,  (emerging packages and so 
on) but of course is not a proof of anything.
The only thing a bit weird on that system (if it can be considered as such) is 
a raid+lvm+btrfs stack (not a important production server )
--
Fabio

      reply	other threads:[~2013-08-26 11:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26  8:36 3.10.9 Crash Fabio Coatti
2013-08-26 10:59 ` Greg Kroah-Hartman
2013-08-26 11:15   ` Fabio Coatti [this message]

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=3209444.Rv0zN2ZK8h@calvin \
    --to=fabio.coatti@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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