> Thanks for this, I can now run 2.1.90
>
> I have run this up on 2.1.90 and it loads lp & slip ok.
>
> But I have had 5 different oopses. I don't know whether they are kmod
> related or something else in 2.1.90.
>
> Here is the last one:
>
> Mar 26 17:48:44 shawc kernel: Oops: 0002
> Mar 26 17:48:44 shawc kernel: CPU: 0
> Mar 26 17:48:44 shawc kernel: EIP: 0010:[<c012f113>]
> Mar 26 17:48:44 shawc kernel: EFLAGS: 00010246
> Mar 26 17:48:44 shawc kernel: eax: 00000000 ebx: c01b0bec ecx:
> c1786008 edx: c17cfecc
> Mar 26 17:48:44 shawc kernel: esi: c1786000 edi: 00000000 ebp:
> 00000005 esp: c17a3ed8
> Mar 26 17:48:44 shawc kernel: ds: 0018 es: 0018 ss: 0018
> Mar 26 17:48:44 shawc kernel: Process modprobe (pid: 166, process nr:
> 21, stackpage=c17a3000)
Hmmm - screwups in modprobe - I was having some of these, while I was
testing kmod - then I remembered to upgrade my modutils to 2.1.85, and the
problem with modprobe crashing the kernel seemed to stop. There are a
couple of places where I simply copy the pointers to strings instead of
bothering to strcpy them, but I that shouldn't be a problem. Which module
was it inserting at the time?
[rest snipped]
> --
> Shaw Carruthers - shaw@shawc.demon.co.uk
> London SW14 7JW UK
> This is not a sig( with homage to Magritte).
>
>
Greg Zornetzer - gaz+@andrew.cmu.edu
"Light shines brightest in the darkest night"
http://www.contrib.andrew.cmu.edu/~gaz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu