Comment 11 for bug 24238

Message-Id: <email address hidden>
Date: Tue, 11 Oct 2005 05:46:13 +1000
From: Rusty Russell <email address hidden>
To: Kay Sievers <email address hidden>
Cc: Marco d'Itri <email address hidden>
Subject: Re: insmod race?

On Sun, 2005-10-09 at 16:26 +0200, Kay Sievers wrote:
> On Sun, Oct 09, 2005 at 10:56:15AM +0200, Marco d'Itri wrote:
> > What do you think about this? It happens when udevd tries to load a
> > dozen of modules at boot time. Is there a race in modules loading?
> > It happens less frequently with other modules too (which as far as I can
> > see are always loaded by one of the other instances).
> >
> > Oct 9 10:36:51 wonderland kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
> > Oct 9 10:36:51 wonderland kernel: 8250_pnp: Unknown symbol serial8250_unregister_port
> > Oct 9 10:36:51 wonderland kernel: 8250_pnp: Unknown symbol serial8250_register_port
> > Oct 9 10:36:51 wonderland kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> > Oct 9 10:36:51 wonderland kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
>
> I'm seeing this too for all sort of modules when using heavy parallel
> modprobe calls like the experimental udev coldplug is doing now...

Weird. Be interesting to replace modprobe with a script that logged who
its parent was and what the args were. The above can happen, of course,
if someone is *removing* modules. It should not really happen with mere
module insertion.

If log doesn't show anything interesting, try adding -v and logging
that...

Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman