* Re: udev causes kernel oops when migrating from 2.6.30.4 to 2.6.31.2
2009-10-07 13:57 udev causes kernel oops when migrating from 2.6.30.4 to 2.6.31.2 hoefle marco
@ 2009-10-07 14:32 ` Kay Sievers
2009-10-07 14:59 ` udev causes kernel oops when migrating from 2.6.30.4 to hoefle marco
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Kay Sievers @ 2009-10-07 14:32 UTC (permalink / raw)
To: linux-hotplug
On Wed, Oct 7, 2009 at 15:57, hoefle marco <marco.hoefle@nanotronic.ch> 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?
Kay
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: udev causes kernel oops when migrating from 2.6.30.4 to
2009-10-07 13:57 udev causes kernel oops when migrating from 2.6.30.4 to 2.6.31.2 hoefle marco
2009-10-07 14:32 ` Kay Sievers
@ 2009-10-07 14:59 ` hoefle marco
2009-10-07 15:05 ` udev causes kernel oops when migrating from 2.6.30.4 to 2.6.31.2 Kay Sievers
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: hoefle marco @ 2009-10-07 14:59 UTC (permalink / raw)
To: linux-hotplug
On Wed, 2009-10-07 at 16:32 +0200, Kay Sievers wrote:
> On Wed, Oct 7, 2009 at 15:57, hoefle marco
> <marco.hoefle@nanotronic.ch> 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?
>
> Kay
Hi Kay,
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.
Marco
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: udev causes kernel oops when migrating from 2.6.30.4 to 2.6.31.2
2009-10-07 13:57 udev causes kernel oops when migrating from 2.6.30.4 to 2.6.31.2 hoefle marco
2009-10-07 14:32 ` Kay Sievers
2009-10-07 14:59 ` udev causes kernel oops when migrating from 2.6.30.4 to hoefle marco
@ 2009-10-07 15:05 ` Kay Sievers
2009-10-07 15:25 ` udev causes kernel oops when migrating from 2.6.30.4 to Greg KH
2009-10-15 8:07 ` hoefle marco
4 siblings, 0 replies; 6+ messages in thread
From: Kay Sievers @ 2009-10-07 15:05 UTC (permalink / raw)
To: linux-hotplug
On Wed, Oct 7, 2009 at 16:59, hoefle marco <marco.hoefle@nanotronic.ch> 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@nanotronic.ch> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: udev causes kernel oops when migrating from 2.6.30.4 to
2009-10-07 13:57 udev causes kernel oops when migrating from 2.6.30.4 to 2.6.31.2 hoefle marco
` (2 preceding siblings ...)
2009-10-07 15:05 ` udev causes kernel oops when migrating from 2.6.30.4 to 2.6.31.2 Kay Sievers
@ 2009-10-07 15:25 ` Greg KH
2009-10-15 8:07 ` hoefle marco
4 siblings, 0 replies; 6+ messages in thread
From: Greg KH @ 2009-10-07 15:25 UTC (permalink / raw)
To: linux-hotplug
On Wed, Oct 07, 2009 at 04:32:38PM +0200, Kay Sievers wrote:
> On Wed, Oct 7, 2009 at 15:57, hoefle marco <marco.hoefle@nanotronic.ch> 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?
It's a huge diff, will not fit on this list I think :(
Anyway, I just looked at it again. Marco, there are numerous bugs in
that driver code. NEVER have an empty release function for a device,
that is completly wrong, and is one reason why this is now failing.
Your driver also has devices in the __initdata section, which is being
thrown away by the kernel. That's probably the biggest problem and I'm
amazed it even worked at all here.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: udev causes kernel oops when migrating from 2.6.30.4 to
2009-10-07 13:57 udev causes kernel oops when migrating from 2.6.30.4 to 2.6.31.2 hoefle marco
` (3 preceding siblings ...)
2009-10-07 15:25 ` udev causes kernel oops when migrating from 2.6.30.4 to Greg KH
@ 2009-10-15 8:07 ` hoefle marco
4 siblings, 0 replies; 6+ messages in thread
From: hoefle marco @ 2009-10-15 8:07 UTC (permalink / raw)
To: linux-hotplug
On Wed, 2009-10-07 at 17:05 +0200, Kay Sievers wrote:
> On Wed, Oct 7, 2009 at 16:59, hoefle marco <marco.hoefle@nanotronic.ch> 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@nanotronic.ch> 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
^ permalink raw reply [flat|nested] 6+ messages in thread