> >> > > That's certainly correct. > > > Such issues > > could crash (all) user apps, but shouldn't prevent the machine from > > responding to sysrq sequences. > > You emphasized the differences of the effects. But there is one reason in > all cases which I know: int10 crashes X or even the whole kernel. > > I could debug the problem to the following point: > > > I could see, that X crashes in glibc 2.3.4 with kernel 2.4.x (not with > kernel 2.6.x, x <= 10, x > 10 not tested) during the first malloc syscall > after int10 to execute the function > xf86MsgVerb(X_INFO,3,"my comment\n"); > > The crashes depend on different versions of used software: > > glibc 2.3.3 or 2.3.4 with kernel 2.4.x > glibc 2.3.2 with kernel > 2.6.9rc2 >
Well if you can track down which patch in -rc2 causes it then we can annoy the person who created it, if you build some kernels from the bk snapshots it might help as -rc2 is quite large vs -rc1.. Dave. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
