From: Greg KH <gregkh@suse.de>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: LKML <linux-kernel@vger.kernel.org>, Stable Tree <stable@kernel.org>
Subject: Re: Kernel hard LOCKUP with v3.0.7
Date: Fri, 21 Oct 2011 22:02:57 +0200 [thread overview]
Message-ID: <20111021200257.GA31198@suse.de> (raw)
In-Reply-To: <AA4CF3E1-3D52-418E-BED9-F34BD22168C3@profihost.ag>
On Fri, Oct 21, 2011 at 09:59:30PM +0200, Stefan Priebe wrote:
> > On Fri, Oct 21, 2011 at 01:11:42PM +0200, Stefan Priebe - Profihost AG wrote:
> >> Hello list,
> >>
> >> today i've seen the following crash using v3.0.7 (renamed to 2.6.40.7).
> >>
> >> http://pastebin.com/raw.php?i=sRq7T4Y0
> >>
> >> I haven't seen this with 3.0.6 but i also changed some kernel config
> >> options (activated ipv6, changed from SLAB to SLUB).
> >
> > Any way to reproduce it?
> >
> > greg k-h
> No idea the systrm is just crashing every 2-6 hours. I've now also
> tried to use slab. No difference. So i will revert to 3.0.6 which is
> running fine.
Can you run 'git bisect' to try to find the problem patch? Oh, there is
one bugfix that I know of, bcd5cff7216f9b2de0a148cc355eac199dc6f1cf in
Linus's tree, can you try that to see if it solves the problem for you?
thanks,
greg k-h
next prev parent reply other threads:[~2011-10-21 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 11:11 Kernel hard LOCKUP with v3.0.7 Stefan Priebe - Profihost AG
2011-10-21 13:07 ` Greg KH
2011-10-21 19:59 ` Stefan Priebe
2011-10-21 20:02 ` Greg KH [this message]
2011-10-22 16:44 ` Stefan Priebe
2011-10-22 16:55 ` Greg KH
2011-10-24 18:15 ` Stefan Priebe
2011-10-24 18:38 ` Greg KH
2011-10-24 19:01 ` Stefan Priebe
2011-10-24 19:13 ` Josh Boyer
2011-10-24 20:33 ` Greg KH
2011-10-25 6:24 ` Stefan Priebe
2011-10-25 7:02 ` Greg KH
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=20111021200257.GA31198@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).