Bug#438736: intel driver produces kernel crash in a variety of situations
Robert Millan wrote: Well, since X is a userland process, I wouldn't expect it to be able to crash the kernel, even if it plays with /dev/agpgart in a bad way. It can even be a security issue. I'm not a X expert but the server contains many drivers that interact with the graphics hardware, i don't know if directly (bypassing the kernel) or by using some kernel interface (DRI?). But if something goes wrong in this area, a crash could happen. Do you know if Linux had improvements in this area from 2.6.18 to 2.6.22 ? Since the upgrade from i810 to intel driver, every kernel upgrade hasn't make any improvement for me (i'm using Sid). In my system is clearly a problem with the X driver. Now i'm still using the vesa driver, but i haven't tested the latest intel driver well (may be most problems are solved?), because the changelogs make me think that some crash problems still exists. Happy to hear that vesa driver seems to have temporarily bypassed your crash problems. Regards. Cesare. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#438736: intel driver produces kernel crash in a variety of situations
On Mon, Aug 20, 2007 at 08:24:18AM +0200, Robert Millan wrote: > > In the meanwhile try to use the generic vesa driver to see if the > > crashes still happens. If they will not occur anymore, you can try with > > the intel driver from unstable or experimental. Btw, tried the vesa driver as you suggested, and now everything works fine. It would still be nice if I could get 3D acceleration, though. -- Robert Millan I know my rights; I want my phone call! What use is a phone call, if you are unable to speak? (as seen on /.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#438736: intel driver produces kernel crash in a variety of situations
On Mon, Aug 20, 2007 at 12:21:12AM +0200, Cesare Leonardi wrote: > Robert Millan wrote: > >I've recently upgraded my hardware (motherboard + cpu + ram) and am now > >getting Linux crashes in a variety of situations. I've detected them > >when any of the following conditions are met: > > > > - When starting a second X session. > > - When time goes backwards (e.g. due to ntpdate) while X is running (but > >NOT when X isn't running) > > - When stopping X. > > [...] > > > - X driver is xserver-xorg-video-i810. Card model: > > Are you sure this is a kernel bug? Well, since X is a userland process, I wouldn't expect it to be able to crash the kernel, even if it plays with /dev/agpgart in a bad way. It can even be a security issue. > I see that the constant is that crashes happen when X is running (or > when is finishing running). > You are using xserver-xorg-video-i810, but since some months this is a > transitional package that points to the newer (and less stable) > xserver-xorg-video-intel. > Since this transition i had noticed numerous crash (and various problems > using video applications, but these seems to be resolved), and reading > some bug reports seems that this driver still has different problems on > which Intel is working on. > I suggest you to look at: > http://bugs.debian.org/xserver-xorg-video-intel Yes, I've seen those reports. That's why I holded on backporting the driver from testing/sid to my etch system. > In the meanwhile try to use the generic vesa driver to see if the > crashes still happens. If they will not occur anymore, you can try with > the intel driver from unstable or experimental. > If they'll persists... this could be a kernel bug. ;-) Do you know if Linux had improvements in this area from 2.6.18 to 2.6.22 ? -- Robert Millan I know my rights; I want my phone call! What use is a phone call, if you are unable to speak? (as seen on /.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#438736: intel driver produces kernel crash in a variety of situations
Robert Millan wrote: I've recently upgraded my hardware (motherboard + cpu + ram) and am now getting Linux crashes in a variety of situations. I've detected them when any of the following conditions are met: - When starting a second X session. - When time goes backwards (e.g. due to ntpdate) while X is running (but NOT when X isn't running) - When stopping X. [...] - X driver is xserver-xorg-video-i810. Card model: Are you sure this is a kernel bug? I see that the constant is that crashes happen when X is running (or when is finishing running). You are using xserver-xorg-video-i810, but since some months this is a transitional package that points to the newer (and less stable) xserver-xorg-video-intel. Since this transition i had noticed numerous crash (and various problems using video applications, but these seems to be resolved), and reading some bug reports seems that this driver still has different problems on which Intel is working on. I suggest you to look at: http://bugs.debian.org/xserver-xorg-video-intel In the meanwhile try to use the generic vesa driver to see if the crashes still happens. If they will not occur anymore, you can try with the intel driver from unstable or experimental. If they'll persists... this could be a kernel bug. ;-) Regards. Cesare. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#438736: intel driver produces kernel crash in a variety of situations
Package: linux-image-2.6.18-5-amd64 Version: 2.6.18.dfsg.1-13etch1 Severity: important I've recently upgraded my hardware (motherboard + cpu + ram) and am now getting Linux crashes in a variety of situations. I've detected them when any of the following conditions are met: - When starting a second X session. - When time goes backwards (e.g. due to ntpdate) while X is running (but NOT when X isn't running) - When stopping X. When this happens, terminal is switched to console, and a kernel backtrace is displayed. As for the backtrace, I've seen it at least once hitting functions related to intel driver, but it seems to be completely different every time. I can get it captured if that's of any use. Also, sometimes the crash is complete, and sometimes SysReq key responds allowing for a cleaner reboot. Some notes on my system: - Two cpu cores (Could parallelism be an issue? If it's possible to disable SMP without recompile I could give that a quick try) - X driver is xserver-xorg-video-i810. Card model: $ sudo lspci -v [...] 00:02.0 VGA compatible controller: Intel Corporation 945G/GZ Express Integrated Graphics Controller (rev 02) (prog-if 00 [VGA]) Subsystem: ASRock Incorporation Unknown device 2772 Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at fea8 (32-bit, non-prefetchable) [size=512K] I/O ports at cc00 [size=8] Memory at d000 (32-bit, prefetchable) [size=256M] Memory at fea4 (32-bit, non-prefetchable) [size=256K] Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Capabilities: [d0] Power Management version 2 [...] -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-amd64 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-5-amd64 depends on: ii coreutil 5.97-5.3The GNU core utilities ii debconf 1.5.11 Debian configuration management sy ii e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib ii initramf 0.85h tools for generating an initramfs ii module-i 3.3-pre4-2 tools for managing Linux kernel mo linux-image-2.6.18-5-amd64 recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
