From: Li Zefan <lizefan@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
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: Sun, 9 Jun 2013 09:39:52 +0800 [thread overview]
Message-ID: <51B3DCE8.90903@huawei.com> (raw)
In-Reply-To: <20130607151030.GB5264@kroah.com>
On 2013/6/7 23:10, Greg KH wrote:
> 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?
>
Now I remember occasionally the kernel failed to boot, and it's not specific
to 3.0... Sorry for the noise.
prev parent reply other threads:[~2013-06-09 1:39 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
2013-06-09 1:39 ` Li Zefan [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=51B3DCE8.90903@huawei.com \
--to=lizefan@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--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