-rc4: arm broken?

-rc4: arm broken?

[Pavel Machek]

Hi!

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?

								Pavel
-- 
teflon -- maybe it is a trademark, but it should not be.

Re: -rc4: arm broken?

[Russell King]

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

Re: -rc4: arm broken?

[Richard Purdie]

On Sat, 2005-07-30 at 15:04 +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?

For the record -rc4 works fine on my Zaurus c760 (which is pxa255 based
rather than sa1100).

Does there problem look like http://lkml.org/lkml/2005/7/30/46 ? That
shouldn't be in -rc4 but it in current git. I've sent a fix for this to
Linus/Andrew and LKML but it hasn't appeared for some reason. A link to
the fix is:
http://www.rpsys.net/openzaurus/patches/2.6.13-rc3-mm3_fix-r0.patch

Richard

Re: -rc4: arm broken?

[Pavel Machek]

Hi!

> > 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?
> 
> For the record -rc4 works fine on my Zaurus c760 (which is pxa255 based
> rather than sa1100).
> 
> Does there problem look like http://lkml.org/lkml/2005/7/30/46 ?
> That
> shouldn't be in -rc4 but it in current git. I've sent a fix for this
> to

Yes, I was running -rc4-git, and yes, the problem looks really similar.

> Linus/Andrew and LKML but it hasn't appeared for some reason. A link to
> the fix is:
> http://www.rpsys.net/openzaurus/patches/2.6.13-rc3-mm3_fix-r0.patch

Hmm, I guess I really should not be running -preempt on zaurus. Thanks!

									Pavel

-- 
if you have sharp zaurus hardware you don't need... you know my address

Re: -rc4: arm broken?

[Russell King]

On Sat, Jul 30, 2005 at 05:45:37PM +0100, Richard Purdie wrote:
> On Sat, 2005-07-30 at 15:04 +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?
> 
> For the record -rc4 works fine on my Zaurus c760 (which is pxa255 based
> rather than sa1100).

It appears to work fine on Intel Assabet.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

Re: -rc4: arm broken?

[Pavel Machek]

Hi!

> > > 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?
> > 
> > For the record -rc4 works fine on my Zaurus c760 (which is pxa255 based
> > rather than sa1100).
> 
> It appears to work fine on Intel Assabet.

I had preempt enabled, and that's apparently broken in -rc4-git. I
turned off preempt and now it boots.
								Pavel
-- 
if you have sharp zaurus hardware you don't need... you know my address

Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?)

[Russell King]

On Sat, Jul 30, 2005 at 08:15:08PM +0100, Russell King wrote:
> On Sat, Jul 30, 2005 at 05:45:37PM +0100, Richard Purdie wrote:
> > On Sat, 2005-07-30 at 15:04 +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?
> > 
> > For the record -rc4 works fine on my Zaurus c760 (which is pxa255 based
> > rather than sa1100).
> 
> It appears to work fine on Intel Assabet.

Let me qualify that, because it's not 100% fine due to the changes in
PCMCIA land.

Since PCMCIA cards are detected and drivers bound at boot time, we no
longer get hotplug events to setup networking for PCMCIA network cards
already inserted.  Consequently, if you are relying on /sbin/hotplug to
setup your PCMCIA network card at boot time, triggered by the cardmgr
startup binding the driver, it won't happen.

This may affect distributions, and distro folks need to check what will
happen when they upgrade to a 2.6 kernel with this updated PCMCIA
support.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

Re: Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?)

[Pavel Machek]

Hi!

> > > > 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?
> > > 
> > > For the record -rc4 works fine on my Zaurus c760 (which is pxa255 based
> > > rather than sa1100).
> > 
> > It appears to work fine on Intel Assabet.
> 
> Let me qualify that, because it's not 100% fine due to the changes in
> PCMCIA land.
> 
> Since PCMCIA cards are detected and drivers bound at boot time, we no
> longer get hotplug events to setup networking for PCMCIA network cards
> already inserted.  Consequently, if you are relying on /sbin/hotplug to
> setup your PCMCIA network card at boot time, triggered by the cardmgr
> startup binding the driver, it won't happen.

Does that mean that if CF is inserted during bootup, it will simply
appear as /dev/hda after bootup, without need to run cardmgr?

								Pavel
-- 
if you have sharp zaurus hardware you don't need... you know my address

Re: Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?)

[Russell King]

On Sat, Jul 30, 2005 at 11:41:52PM +0200, Pavel Machek wrote:
> Hi!
> 
> > > > > 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?
> > > > 
> > > > For the record -rc4 works fine on my Zaurus c760 (which is pxa255 based
> > > > rather than sa1100).
> > > 
> > > It appears to work fine on Intel Assabet.
> > 
> > Let me qualify that, because it's not 100% fine due to the changes in
> > PCMCIA land.
> > 
> > Since PCMCIA cards are detected and drivers bound at boot time, we no
> > longer get hotplug events to setup networking for PCMCIA network cards
> > already inserted.  Consequently, if you are relying on /sbin/hotplug to
> > setup your PCMCIA network card at boot time, triggered by the cardmgr
> > startup binding the driver, it won't happen.
> 
> Does that mean that if CF is inserted during bootup, it will simply
> appear as /dev/hda after bootup, without need to run cardmgr?

Yes, which is almost a plus side.  Whether you can use it to boot from
or not may depend on the timing of the boot up - it looks like it may
suffer the same problems as trying to boot off your USB hard drive.
Try it and see.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

Re: Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?)

[Pavel Machek]

Hi!

> > > > > > 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?
> > > > > 
> > > > > For the record -rc4 works fine on my Zaurus c760 (which is pxa255 based
> > > > > rather than sa1100).
> > > > 
> > > > It appears to work fine on Intel Assabet.
> > > 
> > > Let me qualify that, because it's not 100% fine due to the changes in
> > > PCMCIA land.
> > > 
> > > Since PCMCIA cards are detected and drivers bound at boot time, we no
> > > longer get hotplug events to setup networking for PCMCIA network cards
> > > already inserted.  Consequently, if you are relying on /sbin/hotplug to
> > > setup your PCMCIA network card at boot time, triggered by the cardmgr
> > > startup binding the driver, it won't happen.
> > 
> > Does that mean that if CF is inserted during bootup, it will simply
> > appear as /dev/hda after bootup, without need to run cardmgr?
> 
> Yes, which is almost a plus side.  Whether you can use it to boot

That's certainly a plus side, because I should be able to use pcmcia
cards without setting much userland.
								Pavel
-- 
if you have sharp zaurus hardware you don't need... you know my address

Re: Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?)

[Dominik Brodowski]

Hi,

On Sun, Jul 31, 2005 at 12:30:30AM +0200, Pavel Machek wrote:
> > > > Let me qualify that, because it's not 100% fine due to the changes in
> > > > PCMCIA land.
> > > > 
> > > > Since PCMCIA cards are detected and drivers bound at boot time, we no
> > > > longer get hotplug events to setup networking for PCMCIA network cards
> > > > already inserted.  Consequently, if you are relying on /sbin/hotplug to
> > > > setup your PCMCIA network card at boot time, triggered by the cardmgr
> > > > startup binding the driver, it won't happen.
> > > 
> > > Does that mean that if CF is inserted during bootup, it will simply
> > > appear as /dev/hda after bootup, without need to run cardmgr?
> > 
> > Yes, which is almost a plus side.  Whether you can use it to boot
> 
> That's certainly a plus side, because I should be able to use pcmcia
> cards without setting much userland.

Let me clarify this a bit, and point all interested parties to
http://kernel.org/pub/linux/utils/kernel/pcmcia/howto.html

PCMCIA can work without userspace on 2.6.13 if you compile all necessary
things into the kernel and:

a) the socket is smart enough.This is the case for
	- all sockets which statically map resources 
	  (hd64465, Au1x00, SA1100, SA1111, PXA2xx, M32R_PCC, M32R_CFC, 
	   VRC4171, VRC4173)
	- yenta-socket, pd6729 or i82092 if it 
		1) resides behind a PCI-PCI bridge [oh, I need to update
			the howto regarding this point...] or
		2) resides behind some other bridge limiting the resource
			space (PPC, PPC64)

and

b) a Manufactor/Device or Product ID match is known for the device. Matching
for "Function ID" (quite common for CF cards, unfortunately) is fuzzy and
therefore can only be enabled if we are sure no (other) driver matches. And
that's currently done by waiting for userspace telling the kernel that it
already modprobed all available modules. In the long term, we should try to
get rid of all "Function ID" matches, and use the more specific Manufactor,
Device and Product ID matches. So patches adding more IDs are welcome.

Thanks,
	Dominik

Re: Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?)

[Grant Coady]

On Sat, 30 Jul 2005 22:36:28 +0100, Russell King <rmk+lkml@arm.linux.org.uk> wrote:
>
>Let me qualify that, because it's not 100% fine due to the changes in
>PCMCIA land.
>
>Since PCMCIA cards are detected and drivers bound at boot time, we no

Without an unbind/eject option?  Implies reboot to remove a device...

Grant.

Re: Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?)

[Russell King]

On Sun, Jul 31, 2005 at 08:17:29AM +1000, Grant Coady wrote:
> On Sat, 30 Jul 2005 22:36:28 +0100, Russell King <rmk+lkml@arm.linux.org.uk> wrote:
> >
> >Let me qualify that, because it's not 100% fine due to the changes in
> >PCMCIA land.
> >
> >Since PCMCIA cards are detected and drivers bound at boot time, we no
> 
> Without an unbind/eject option?  Implies reboot to remove a device...

No.  You can still use cardctl (or whatever the pcmciautils version
of that is) to eject cards, and you can of course still pull them
from the socket.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

Re: Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?)

[Richard Purdie]

On Sat, 2005-07-30 at 23:26 +0100, Russell King wrote:
> No.  You can still use cardctl (or whatever the pcmciautils version
> of that is) to eject cards, and you can of course still pull them
> from the socket.

If you pull CF memory cards from the socket, you'll see some interesting
oops. I've been waiting for things to stabilise a bit before trying to
investigate and hopefully fix this. Any assistance welcome.

Richard

Re: Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?)

[Alan Cox]

On Sad, 2005-07-30 at 22:36 +0100, Russell King wrote:
> Since PCMCIA cards are detected and drivers bound at boot time, we no
> longer get hotplug events to setup networking for PCMCIA network cards
> already inserted.  Consequently, if you are relying on /sbin/hotplug to
> setup your PCMCIA network card at boot time, triggered by the cardmgr
> startup binding the driver, it won't happen.

So eth0 now randomly changes between on board and PCMCIA depending upon
whether the PCMCIA card was inserted or not, and your disks re-order
themselves in the same situation. That'll be funny if anyone does a
mkswap to share their swap between Linux and Windows. Gosh look there
goes the root partition.

I'm hoping thats not what you are implying. Especially for disks,
network is much much less of an issue.

Re: Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?)

[Russell King]

On Mon, Aug 01, 2005 at 02:01:07AM +0100, Alan Cox wrote:
> On Sad, 2005-07-30 at 22:36 +0100, Russell King wrote:
> > Since PCMCIA cards are detected and drivers bound at boot time, we no
> > longer get hotplug events to setup networking for PCMCIA network cards
> > already inserted.  Consequently, if you are relying on /sbin/hotplug to
> > setup your PCMCIA network card at boot time, triggered by the cardmgr
> > startup binding the driver, it won't happen.
> 
> So eth0 now randomly changes between on board and PCMCIA depending upon
> whether the PCMCIA card was inserted or not, and your disks re-order
> themselves in the same situation. That'll be funny if anyone does a
> mkswap to share their swap between Linux and Windows. Gosh look there
> goes the root partition.
> 
> I'm hoping thats not what you are implying. Especially for disks,
> network is much much less of an issue.

If you have the socket driver as a module, as some (most?) distros do,
then of course such cards won't be detected at boot time.  If PCMCIA
and the socket driver are built-in, along with the card driver, then
I guess this possibility may well exist - it does for NE2K cards.

Since I don't use CF cards with PCMCIA here, I can't say what the ide-cs
behaviour actually is.  This is why I'm trying to encourage folk to
explore the kernels new behaviour.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

[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]

On Mon, Aug 01, 2005 at 07:48:31AM +0100, Russell King wrote:
> On Mon, Aug 01, 2005 at 02:01:07AM +0100, Alan Cox wrote:
> > On Sad, 2005-07-30 at 22:36 +0100, Russell King wrote:
> > > Since PCMCIA cards are detected and drivers bound at boot time, we no
> > > longer get hotplug events to setup networking for PCMCIA network cards
> > > already inserted.  Consequently, if you are relying on /sbin/hotplug to
> > > setup your PCMCIA network card at boot time, triggered by the cardmgr
> > > startup binding the driver, it won't happen.
> > 
> > So eth0 now randomly changes between on board and PCMCIA depending upon
> > whether the PCMCIA card was inserted or not, and your disks re-order
> > themselves in the same situation. That'll be funny if anyone does a
> > mkswap to share their swap between Linux and Windows. Gosh look there
> > goes the root partition.
> > 
> > I'm hoping thats not what you are implying. Especially for disks,
> > network is much much less of an issue.
> 
> If you have the socket driver as a module, as some (most?) distros do,
> then of course such cards won't be detected at boot time.  If PCMCIA
> and the socket driver are built-in, along with the card driver, then
> I guess this possibility may well exist - it does for NE2K cards.

Linus, Andrew,

Please apply this for 2.6.13 - Thanks,

	Dominik


Avoid registering PCMCIA CF cards before other IDE stuff. This means the risk
of /dev/hd* being re-ordered is lessened. The _sane_ thing to assert any
ordering is to use udev, nameif and so on, of course.

Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>

Index: 2.6.13-rc4-git1/drivers/ide/legacy/ide-cs.c
===================================================================
--- 2.6.13-rc4-git1.orig/drivers/ide/legacy/ide-cs.c
+++ 2.6.13-rc4-git1/drivers/ide/legacy/ide-cs.c
@@ -508,5 +508,5 @@ static void __exit exit_ide_cs(void)
 	BUG_ON(dev_list != NULL);
 }
 
-module_init(init_ide_cs);
+late_initcall(init_ide_cs);
 module_exit(exit_ide_cs);