Reproducable oops in 2.1.3[0-6]

Matthew Harrell (
Wed, 23 Apr 1997 10:06:25 -0400 (EDT)

I sent in a bug report earlier this week, but I probably didn't
qualify it enough. It seems that 90% of the time when I unsuspend my
laptop I get an oops. It almost seems like it the first process which
runs that causes the oops, but there always seems to be one. It's not
fatal, but it could be a sign of something else. I've attached the oops
stuff below (not much to it). This particular one happened when the first
thing I did was try to open an xterm under fvwm.

  Matthew Harrell                          Behind every great computer sits
  Simulation Technology Division, SAIC      a skinny little geek.

Using `/boot/' to map addresses to symbols. >>EIP: c011f272 <kfree+1e/12c> Code: c011f272 <kfree+1e/12c>

Unable to handle kernel NULL pointer dereference at virtual address 00000000 current->tss.cr3 = 009aa000, ^Tr3 = 009aa000 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[<c011f272>] EFLAGS: 00010257 eax: 00000008 ebx: c143d3e0 ecx: 00000000 edx: 00000000 esi: c143d3e0 edi: c143d3e0 ebp: c192a3e0 esp: c11c9ef0 ds: 0018 es: 0018 ss: 0018 Process sh (pid: 691, process nr: 54, stackpage=c11c9000) Stack: c143d3e0 c143d3e0 c143d3e0 c192a3e0 c0124ded c0145efa 00000008 c192a3e0 c143d3e0 c143d3e0 c11c9f7c 00000000 bffff790 fffffffb 00000000 00000000 00000008 c012be97 c192a3e0 c143d3e0 00000000 00000000 c11c9f7c 00000000 Call Trace: Code: f7 02 ff 0f 00 00 0f 85 ca 00 00 00 8b 42 08 83 f8 0d 0f 87