Messages in this thread | | | Date | Thu, 27 Jul 2000 19:36:27 -0400 (EDT) | From | clubneon <> | Subject | Re: oops' with the late 2.4.0-testX's |
| |
Well your bad config has the DRM code compiled in.
I've been getting Oops since 2.4.0-test5-pre4 when I've enabled the DRM code (with either tdfx or mga).
On Thu, 27 Jul 2000, safemode wrote:
> I'd just like to say first off i'm not subscribed to this list so anyone > with any answers as to why the problem is occurring should reply also to > me ...thanks. > the problem is this : > Unable to handle kernel NULL pointer dereference at virtual address > 00000008 > printing eip: > c0140d84 > *pde = 00000000 > Oops: 0000 > CPU: 0 > EIP: 0010:[<c0140d84>] > EFLAGS: 00010207 > eax: 00000000 ebx: c12b1f40 ecx: c7d4cc40 edx: c7ff8000 > esi: c120a3a0 edi: 00000000 ebp: c12b1f40 esp: c7ff9f00 > ds: 0018 es: 0018 ss: 0018 > Process start-stop-daem (pid: 147, stackpage=c7ff9000) > Stack: c7d4cc40 c7ff9fa4 c7c723c0 c7ff9fa4 00000000 00000000 00000000 > c014127b > c7d4cc40 00000001 c7ff9fa4 c7ff8000 c7d4cc40 c0134dd1 c7c723c0 > c7ff9fa4 > c7d4cc40 00000000 c7e8d000 c7ff9fa4 bffffbdc 00000001 bffffbdc > c7ff9fa8 > Call Trace: [<c014127b>] [<c0134dd1>] [<c013528c>] [<c0131eb6>] > [<c010a370>] > Code: 8b 50 08 39 d0 0f 84 81 00 00 00 8b 00 89 54 24 18 39 da 75 > > Now, the system is Debian Woody ... gcc version 2.95.2 20000220 > the start-stop-daemon does the obvious, it works on kernels 2.4.0-test3 > and previous, but none above > also, other problems like Kernel panic's on boot with INIT on the > Test5-pre kernels > this seems to be kernel config specific, since i compile under the same > system a different config and it worked fine.... under this current > kernel 2.4.0-test4, my ftp server wont connect to it's port, giving > this message : connect failed: Transport endpoint is not connected. > yet apache works (btw, this problem doesn't occur when accesing the ftp > server via another node on the network directly to this box. . only when > accessing locally and through the router, which worked before using > test3) with a pause between every access, but it works. keep in mind > it's commenicating over a masq box which forward requests to port 80 and > 21 to this box. This was working fine with Test3 > for the bad config > http://psuedomode.homeip.net/bad_config > > for the working config > http://psuedomode.homeip.net/good_config > > the good config was compiled for my firewall , it has a lot of > networking options set but i dont think this could be the problem, since > they're mostly modules and not very core to the kernel. but i could be > wrong :) > I guess if anyone can sort of point out what the evil option is that is > probably causing this i'd be really happy. > Oh, i just noticed, the bad config is a config file from > 2.4.0-test4 whereas the config file that's marked as good is from > 2.4.0-test5-pre5 ...this shouldn't be a problem since they're both > basically the same and the problem only occurred worse (i used the same > config found in the bad_config with -test5) with test5.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |