On Tue, Jan 14, 2003 at 06:55:28PM +0100, Marek Habersack wrote: > Hello, > > The kernel 2.5.56 seems to have changed something that affected the XFS > code as I'm getting hit by one (and possibly two) bugs related to it now. > What happens is that the machine suddenly freezes (running Debian/Sid - > XFree 4.2.1, glibc 2.3.1, gnome2 - nothing out of ordinary) so that SysRq > keys don't have any effect (but Numlock still toggles the led on the > keyboard), machine is inaccessible from the net and the only cure is hard > reboot. Nothing gets logged on the freeze and on reboot when XFS attempts to > check the first filesystem the kernel oopses with Oops code 0002, in the > interrupt handler. Nothing gets logged, of course, so I can't provide the > full backtrace right now - I'll try to get it logged through the serial console > if it happens again with 2.5.58. I have copied some values by hand from the > screen (until I lost patience... :)): > > Unable to handle kernel paging request at virtual address 000500074 > printing EIP Hmm, that's really no much info. And there weren't any XFS changes from 2.5.52 to 2.5.58.. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups: References:
- Prev by Date: Re: Nvidia and its choice to read the GPL "differently"
- Next by Date: Re: 2.4.x, can't ptrace a task created with clone() ?
- Previous by thread: XFS problems (hard lockup and oops on startup) with 2.5.5{6,7}
- Next by thread: Re: XFS problems (hard lockup and oops on startup) with 2.5.5{6,7}
- Indexes:[Main][Thread]