From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: rpurdie@rpsys.net, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: -rc4: arm broken?
Date: Sat, 30 Jul 2005 17:13:08 +0100 [thread overview]
Message-ID: <20050730171308.A26592@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050730130406.GA4285@elf.ucw.cz>; from pavel@ucw.cz on Sat, Jul 30, 2005 at 03:04:06PM +0200
On Sat, Jul 30, 2005 at 03:04:06PM +0200, Pavel Machek wrote:
> I merged -rc4 into my zaurus tree, and now zaurus will not boot. I see
> oops-like display, and it seems to be __call_usermodehelper /
> do_execve / load_script related. Anyone seen it before?
I've run -rc4 on an ARM SMP system (with extra patches to sort out
the previously reported problem) and it seemed happy. I'll be
testing a SA1100 kernel later today (mainly for the UCB stuff.)
Stay tuned.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-07-30 16:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 13:04 -rc4: arm broken? Pavel Machek
2005-07-30 16:13 ` Russell King [this message]
2005-07-30 16:45 ` Richard Purdie
2005-07-30 19:02 ` Pavel Machek
2005-07-30 19:15 ` Russell King
2005-07-30 19:18 ` Pavel Machek
2005-07-30 21:36 ` Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?) Russell King
2005-07-30 21:41 ` Pavel Machek
2005-07-30 21:55 ` Russell King
2005-07-30 22:30 ` Pavel Machek
2005-07-30 22:43 ` Dominik Brodowski
2005-07-30 22:17 ` Grant Coady
2005-07-30 22:26 ` Russell King
2005-07-30 23:31 ` Richard Purdie
2005-08-01 1:01 ` Alan Cox
2005-08-01 6:48 ` Russell King
2005-08-01 12:16 ` [PATCH] pcmcia: defer ide-cs initialization after other IDE drivers started up [Was: Re: Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?)] Dominik Brodowski
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=20050730171308.A26592@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
/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