Race condition in module load causing undefined symbols
in [Kernel]
|
Next: Am1771 wireless driver?
From: Steve Lord on 11 Jun 2005 09:30 Pozsýr Balýzs wrote: > On Fri, Jun 10, 2005 at 11:25:15AM -0700, Andrew Morton wrote: > >>I wonder if rather than the intermittency being time-based, it is >>load-address-based? For example, suppose there's a bug in the symbol >>lookup code? > > > Just a data point: I met the same problem with 2.6.12-rc5, using > gcc 3.3.4. > I think it's time-based issue, because I was playing around with the > initscripts, and the bug shows up when there are lots of modprobes in a > short time. > > I think this is not actually module loading itself, but a problem between the fork/exec/wait code in nash and the kernel. The commands which have problems are the ones which are not built into nash. So this looks more like a problem with wait. This would explain sleep fixing it and the fact that I have device issues after module load. Steve - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Andrew Morton on 11 Jun 2005 15:10 Stephen Lord <lord(a)xfs.org> wrote: > > Pozsýr Balýzs wrote: > > On Sat, Jun 11, 2005 at 08:23:20AM -0500, Steve Lord wrote: > > > >>I think this is not actually module loading itself, but a problem > >>between the fork/exec/wait code in nash and the kernel. > > > > > > I do not use nash, only bash, so this is not a nash-specific issue. > > > > > > I disabled hyperthreading and things started working, so are there any > HT related scheduling bugs right now? There haven't been any scheduler changes for some time. There have been a few low-level SMT changes I think. Are you able to identify which kernel version broke it? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Pozsár Balázs on 11 Jun 2005 15:20 On Sat, Jun 11, 2005 at 12:00:40PM -0700, Andrew Morton wrote: > > I disabled hyperthreading and things started working, so are there any > > HT related scheduling bugs right now? > > There haven't been any scheduler changes for some time. There have been a > few low-level SMT changes I think. > > Are you able to identify which kernel version broke it? I do not have HT or SMP, though the kernel is smp. 2.6.9 works for me. That's all I can tell now. -- pozsy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Steve Lord on 11 Jun 2005 16:20 Well, the bizarre part is that I think this has been around for a while, but it does not exhibit itself in redhat kernels which postdate the earliest recolloction of me seeing it. 2.6.11-rc1 is the earliest I remember, but I am not religious about updating the kernel on this box so my samples are spotty. The difference between the two may be that I recompile for a P4 while redhat uses a lowest common denominator cpu type. If I get a chance this weekend I will try some other kernels and report back. Maybe just start out by dumbing down my cpu type. Steve > Stephen Lord <lord(a)xfs.org> wrote: >> >> I disabled hyperthreading and things started working, so are there any >> HT related scheduling bugs right now? > > There haven't been any scheduler changes for some time. There have been a > few low-level SMT changes I think. > > Are you able to identify which kernel version broke it? > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Pozsár Balázs on 11 Jun 2005 16:30
On Sat, Jun 11, 2005 at 03:09:08PM -0500, Steve Lord wrote: > Well, the bizarre part is that I think this has been around for a while, > but it > does not exhibit itself in redhat kernels which postdate the earliest > recolloction of me seeing it. 2.6.11-rc1 is the earliest I remember, > but I am not religious about updating the kernel on this box so > my samples are spotty. > > The difference between the two may be that I recompile for a P4 > while redhat uses a lowest common denominator cpu type. > > If I get a chance this weekend I will try some other kernels and > report back. Maybe just start out by dumbing down my cpu > type. I always used CONFIG_M586=y. Did you turn preempt on? I did with the 2.6.12-rc, but not with the (working) 2.6.9, so this migth be the difference. Sorry, I do not have currently for testing. -- pozsy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |