Messages in this thread | | | Date | Wed, 12 Nov 1997 12:09:19 +0100 (MET) | From | Rik van Riel <> | Subject | Re: Lockup 2.1.6* => kmalloc/slab |
| |
On Wed, 12 Nov 1997, Mark Hemment wrote:
> There could be a bug in the SLAB which is causing the lock-up, but > it is also possible the the networking stack doesn't handle a failure > correctly somehwere...or it doesn't handle multi-failures correctly...or > doesn't use GFP_ATOMIC when it should... (The stack is a black-hole for > me...). > What can you do after your box locks? Switch multi-screens? Turn the > Num-lock on/off?
On my box (generic P5) nothing works anymore, except the <sysrq> things. But <sysrq> can't wake up kflushd anymore. Task-switching seems to have stopped too. I can't kill the tasks because they don't get the CPU to handle the signals :-( Screen-switching doesn't work either.
> Of course, the lock-up may not be in the networking code. The allocations > the code performs triggers a page-reaping (race) bug somewhere else. This > does sounds v. plausable - I'll walk some code paths this evening. Your > not SMP are you?
You don't need SMP for these.
Rik.
---------- Send Linux memory-management wishes to me: I'm currently looking for something to hack...
| |