From: Milan Broz <mbroz@redhat.com>
To: Andy Whitcroft <apw@canonical.com>
Cc: Ray Lee <ray-lk@madrabbit.org>,
Arnaud Lacombe <lacombar@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Michal Marek <mmarek@suse.cz>,
pefoley2@verizon.net, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT] kbuild fixes for 3.0
Date: Fri, 10 Jun 2011 17:26:09 +0200 [thread overview]
Message-ID: <4DF23791.7060607@redhat.com> (raw)
In-Reply-To: <BANLkTikb0=CvTbN_njhq7JyJwOigEa0eLA@mail.gmail.com>
On 06/10/2011 05:06 PM, Andy Whitcroft wrote:
> As an experiment I have uploaded a 3.0 reporting kernel into Ubuntu
> Oneiric. So far we have had issues with:
>
> - depmod -- (as above)
> - procps (ps/top) -- reporting errors on startup
> - glibc version checks are preventing upgrade of that package
>
> I am sure there will be others
All tools based on libdevmapper (lvm, cryptsetup, kpartx, ...)
fails in initialization. (fixed already in devel tree)
mdadm is broken with 3.0 as well (it fails to auto assemble devices)
because of misparsing kernel version.
Fedora was quite proactive and added uts name patch "3.0-rc1",
so you can see what it caused... (unbootable system in short)
https://bugzilla.redhat.com/show_bug.cgi?id=710646
Milan
next prev parent reply other threads:[~2011-06-10 15:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 21:42 [GIT] kbuild fixes for 3.0 Michal Marek
2011-06-10 0:10 ` Linus Torvalds
2011-06-10 3:14 ` Arnaud Lacombe
2011-06-10 3:37 ` Linus Torvalds
2011-06-10 3:41 ` Arnaud Lacombe
2011-06-10 3:45 ` Arnaud Lacombe
2011-06-10 3:57 ` Linus Torvalds
2011-06-10 5:16 ` Arnaud Lacombe
2011-06-10 5:53 ` Ray Lee
2011-06-10 10:03 ` maximilian attems
2011-06-10 15:22 ` Linus Torvalds
2011-06-10 20:45 ` Michal Marek
2011-06-10 20:56 ` Linus Torvalds
2011-06-10 15:06 ` Andy Whitcroft
2011-06-10 15:26 ` Milan Broz [this message]
2011-06-10 16:30 ` Arnaud Lacombe
2011-06-10 19:31 ` [lm-sensors] " Jean Delvare
2011-06-10 12:13 ` Michal Marek
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=4DF23791.7060607@redhat.com \
--to=mbroz@redhat.com \
--cc=apw@canonical.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=pefoley2@verizon.net \
--cc=ray-lk@madrabbit.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