Messages in this thread |  | | Date | Mon, 3 Feb 1997 07:01:25 -0500 (EST) | From | "Steven N. Hirsch" <> | Subject | Re: depmod Oops in 2.1.25 |
| |
On Mon, 3 Feb 1997, Charlie Ross wrote:
> > spiff# depmod -a > Unable to handle kernel paging request at virtual address 1c392cc0 > current->tss.cr3 = 01011000, %cr3 = 01011000 > *pde = 00000000 > Oops: 0000 > CPU: 0 > EIP: 0010:[<c01169d1>] > EFLAGS: 00010203 > eax: 1dfb2000 ebx: c01e3b48 ecx: 0000003b edx: 1c392cc0 > esi: 1c392cc0 edi: c0728f84 ebp: c01c62d7 esp: c0728f5c > ds: 0018 es: 0018 ss: 0018 > Process depmod (pid: 199, process nr: 20, stackpage=c0728000) > Stack: c10cd018 bffffb40 00000002 bfffabbc c0728f80 c0728f84 c0728f85 > 00000000 > 00000001 1dfb2000 00000023 00000000 00000000 00000000 00000000 > 00000000 > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > 00000000 > Call Trace: [<c010a3f6>] > Code: ac aa 84 c0 75 f7 f3 aa c6 44 24 63 00 ba 40 00 00 00 a1 8c > Segmentation fault > spiff#
Exactly the same results here when using modules.. Broken again, I guess <sigh>.
> I get very similar Oopses when modprobe runs on bootup... > BTW I've been getting these since 2.1.21 ish...
Odd. Modules actually worked properly here with 2.1.24!
Steve
|  |