On Wed, 2009-10-07 at 17:05 +0200, Kay Sievers wrote:
> On Wed, Oct 7, 2009 at 16:59, hoefle marco <marco.hoefle@xxxxxxxxxxxxx> wrote:
> > On Wed, 2009-10-07 at 16:32 +0200, Kay Sievers wrote:
> >> On Wed, Oct 7, 2009 at 15:57, hoefle marco
> >> <marco.hoefle@xxxxxxxxxxxxx> wrote:
> >> > on your arm board (pxa270) we need to migrate to Kernel 2.6.31.x due
> >> to
> >> > block device driver api changes.
> >> > When compiling the new kernel with the same .config as with 2.6.30.4
> >> we
> >> > get a kernel oops (attached later).
> >> > The udevd version is 125 which is that one used in debian. This
> >> version
> >> > works well for kernel 2.6.30.1, 2.6.30.4 but not for 2.6.31.0,
> >> 2.6.31.1
> >> > and 2.6.31.2.
> >> > Do we need to change something in the kernel config?
> >> > Has the according userspace API changed?
> >> > Any ideas on how to debug this?
> >>
> >> No, there was no change. It should work fine.
> >>
> >> I would expect a kernel device driver problem. You use any drivers
> >> which are not in the upstream git repo? If yes, any pointers to it?
>
> > thanks for your quick response. I disabled all non upstream drivers (USB
> > Host controller driver, usb device controller, disk-on-chip).
> > So only drivers in the upstream kernel are used.
>
> Does the box allow you to boot with init=/bin/sh, or something
> similar, mount /sys and run binaries?
>
> Kay
>
The failure was caused by:
static struct isp1760_platform_data isp1760_platform_data __initdata = {
__initdata causes a section mismatch and finally a kernel oops. So it
was driver related not as I thought an udev issue. Strange that this
behavior didn't show up in 2.6.30.4.
Cheers,
Marco
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
