On Fri, Jan 21, 2005 at 09:05:12PM +0100, Andreas Hartmann wrote: > Hello Helge, > > Helge Hafting schrieb: > > On Sun, Jan 16, 2005 at 10:41:23PM +1100, Dave Airlie wrote: > >> > > >> > I'm fine with adding this code, but we still don't know if this is the > >> > cause of his problem. The debug output can determine if this really is > >> > the source of the problem or if it is somewhere else. > >> > > >> > >> I actually doubt it is this stuff.. my guess is that it is something > >> nasty like ACPI breaking int10 for X or something like that... it > >> seems a lot more subtle than the usually things that break when we > >> mess with the DRM :-) > > Which glibc do you use? I have problems with glibc 2.3.4, kernel 2.4.x and > X / Xorg while executing the int10-code of X. glibc 2.3.3 works fine for > me. But I could find another posting, which describes, that there are even > problems with glibc 2.3.3 and kernel 2.4.x. > > It's new for me, that there could be problems with kernelversions of 2.6, too. > > Therefore, it would be really interessting to know, which glibc version > you are using. > I use glibc 2.3.2 from debian testing (or unstable). This is not the problem though, because a reboot into 2.6.8.1 makes X work without crashing. The crash only happens with 2.6.9-rc2 or later kernels.
So the only way glibc could be the culprit, is if the newer kernel exports some new interface that this glibc manages to mess up. Still, even a buggy glibc shouldn't hang the kernel anyway. Such issues could crash (all) user apps, but shouldn't prevent the machine from responding to sysrq sequences. Helge Hafting - 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/
