All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe@profihost.ag>
To: Greg KH <gregkh@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Stable Tree <stable@kernel.org>
Subject: Re: Kernel hard LOCKUP with v3.0.7
Date: Mon, 24 Oct 2011 21:01:12 +0200	[thread overview]
Message-ID: <4EA5B5F8.5090802@profihost.ag> (raw)
In-Reply-To: <20111024183820.GA9397@suse.de>

Hi,

> On Mon, Oct 24, 2011 at 08:15:28PM +0200, Stefan Priebe wrote:
>> Am 22.10.2011 18:55, schrieb Greg KH:
>>>> this seems to fix it. Perhaps you should release v3.0.8 as the
>>>> stable tree isn't stable right now? I mean this bug seems to be
>>>> triggered on every SMP machine.
>>> I will work to get it out soon.
>> Fine. Any idea if this will happen this week or in a month or ...
>> I'm scheduling an update for all our systems and if this will happen
>> really soon i will probably schedule it a bit later.
>
> The 3.0.8-rc1 went out two days ago, so hopefully, if my gpg usb stick
> still works, I can get it out tomorrow, or the day after, as tomorrow,
> the Kernel Summit is still going on.

how to get 3.0.8-rc1? linux-stable.git does not have a tag named 
v3.0.8-rc1 - will 3.0.8 be the same as 3.0.8-rc1?

Thanks!

Stefan

  reply	other threads:[~2011-10-24 19:01 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
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 [this message]
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=4EA5B5F8.5090802@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.