Re: 2.4.4 del_timer_sync oops in schedule_timeout

2001-05-21 Thread Jacob Luna Lundberg
On Mon, 21 May 2001, Andrew Morton wrote: > It could be timer-list corruption. Someone released some memory > which had a live timer in it. The memory got recycled and then > the timer list traversal fell over it. Well I do have another oops now (artsd this time). Once again it's in del_timer

Re: 2.4.4 del_timer_sync oops in schedule_timeout

2001-05-20 Thread Andrew Morton
Ingo Molnar wrote: > > On Sat, 19 May 2001, Jacob Luna Lundberg wrote: > > > This is 2.4.4 with the aic7xxx driver version 6.1.13 dropped in. > > > Unable to handle kernel paging request at virtual address 78626970 > > this appears to be some sort of DMA-corruption or other memory scribble > p

Re: 2.4.4 del_timer_sync oops in schedule_timeout

2001-05-20 Thread Ingo Molnar
On Sun, 20 May 2001, Jacob Luna Lundberg wrote: > > > Unable to handle kernel paging request at virtual address 78626970 > > this appears to be some sort of DMA-corruption or other memory scribble > > problem. hexa 78626970 is ASCII "pibx", which shows in the direction of > > some sort of disk-r

Re: 2.4.4 del_timer_sync oops in schedule_timeout

2001-05-20 Thread Jacob Luna Lundberg
On Sun, 20 May 2001, Ingo Molnar wrote: > > Unable to handle kernel paging request at virtual address 78626970 > this appears to be some sort of DMA-corruption or other memory scribble > problem. hexa 78626970 is ASCII "pibx", which shows in the direction of > some sort of disk-related DMA corrup

Re: 2.4.4 del_timer_sync oops in schedule_timeout

2001-05-20 Thread Ingo Molnar
On Sat, 19 May 2001, Jacob Luna Lundberg wrote: > This is 2.4.4 with the aic7xxx driver version 6.1.13 dropped in. > Unable to handle kernel paging request at virtual address 78626970 this appears to be some sort of DMA-corruption or other memory scribble problem. hexa 78626970 is ASCII "pibx"