Skip to contentSkip to conversation

-rc4: arm broken?

PATCH New Pavel Machek 6 participants 17 messages Jul 30, 2005 – Aug 1, 2005

lore
Share & tools
lore
#0 lore raw

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

Signature · 1 line
teflon -- maybe it is a trademark, but it should not be.
#1 lore raw
Quoted 3 lines · Pavel Machek

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.

Signature · 3 lines
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core
#2 lore raw
In reply to Pavel Machek
Quoted 3 lines · Pavel Machek

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

#3 lore raw

Hi!

Quoted 11 lines
Quoted 3 lines

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.

Quoted 3 lines

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

Signature · 1 line
if you have sharp zaurus hardware you don't need... you know my address
#4 lore raw
In reply to Richard Purdie
Quoted 7 lines · Richard Purdie
Quoted 3 lines · Pavel Machek

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.

Signature · 3 lines
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core
#5 lore raw

Hi!

Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

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

Signature · 1 line
if you have sharp zaurus hardware you don't need... you know my address
#6 lore raw

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

In reply to Russell King
Quoted 10 lines · Russell King
Quoted 7 lines · Richard Purdie
Quoted 3 lines · Pavel Machek

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.

Signature · 3 lines
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core
#7 lore raw

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

Hi!

Quoted 9 lines
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

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.

Quoted 8 lines

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

Signature · 1 line
if you have sharp zaurus hardware you don't need... you know my address
#8 lore raw

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

Quoted 14 lines · Pavel Machek

Hi!

Quoted 12 lines
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

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.

Quoted 8 lines
Quoted 5 lines

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.

Signature · 3 lines
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core
#9 lore raw

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

Hi!

Quoted 18 lines
Quoted 18 lines
Quoted 17 lines
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

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.

Quoted 4 lines
Quoted 2 lines

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

Signature · 1 line
if you have sharp zaurus hardware you don't need... you know my address
#10 lore raw

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

Hi,

Quoted 9 lines · Pavel Machek
Quoted 9 lines
Quoted 9 lines
Quoted 8 lines

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.

Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

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

#11 lore raw

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

In reply to Russell King
Quoted 5 lines · Russell King

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.

#12 lore raw

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

Quoted 8 lines · Grant Coady
Quoted 5 lines · Russell King

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.

Signature · 3 lines
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core
#13 lore raw

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

Quoted 3 lines · Russell King

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

#14 lore raw

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

In reply to Russell King
Quoted 5 lines · Russell King

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.

#15 lore raw

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

Quoted 7 lines · Alan Cox
Quoted 5 lines · Russell King

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.

Quoted 8 lines

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.

Signature · 3 lines
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core
#16 lore raw

PATCH 1/1 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?)]

Quoted 14 lines · Russell King
Quoted 13 lines · Alan Cox
Quoted 5 lines · Russell King

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.

Quoted 7 lines
Quoted 2 lines

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.

drivers/ide/legacy/ide-cs.c +1 -1
Index: 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);