[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3209444.Rv0zN2ZK8h@calvin>
Date: Mon, 26 Aug 2013 13:15:41 +0200
From: Fabio Coatti <fabio.coatti@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: 3.10.9 Crash
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists