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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
