From: Greg KH <gregkh@linuxfoundation.org>
To: Li Zefan <lizefan@huawei.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 3.0.80
Date: Fri, 7 Jun 2013 08:10:30 -0700 [thread overview]
Message-ID: <20130607151030.GB5264@kroah.com> (raw)
In-Reply-To: <51B1A33C.1020708@huawei.com>
On Fri, Jun 07, 2013 at 05:09:16PM +0800, Li Zefan wrote:
> On 2013/5/25 2:23, Greg KH wrote:
> > I'm announcing the release of the 3.0.80 kernel.
> >
> > All users of the 3.0 kernel series must upgrade.
> >
> > The updated 3.0.y git tree can be found at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.0.y
> > and can be browsed at the normal kernel.org git web browser:
> > http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
> >
> > thanks,
> >
> > greg k-h
> >
> > ------------
> >
> > Makefile | 2 +-
> > drivers/hwmon/abituguru.c | 16 ++++++++++------
> > drivers/media/dvb/mantis/mantis_dvb.c | 6 ++++--
> > fs/btrfs/ioctl.c | 10 +++++-----
> > 4 files changed, 20 insertions(+), 14 deletions(-)
> >
>
> 3.0.80 failed to boot, and looks like the culprit is blkcg, so I disabled
> CONFIG_CGROUP and it boot successfully.
Did 3.0.79 boot properly with this same hardware / kernel configuration?
If so, can you bisect it down to the problem commit please?
> I haven't tried 3.0.81, as it's not released yet.
Give me a few hours, but odds are, it's not fixed, as I have not heard
of this problem before.
thanks,
greg k-h
next prev parent reply other threads:[~2013-06-07 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 18:23 Linux 3.0.80 Greg KH
2013-05-24 18:23 ` Greg KH
2013-06-07 9:09 ` Li Zefan
2013-06-07 15:10 ` Greg KH [this message]
2013-06-09 1:39 ` Li Zefan
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=20130607151030.GB5264@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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