Description of problem: i810 driver causes kernel panic. It sometimes loads, only if first vesa is loaded, and then one exits the server, and loads i810, but even in this case shutdown, or reboot, causes kernel panic. The chipset is intel i965. Version-Release number of selected component (if applicable): Linux homayoun 2.6.18-8.1.1.el5 #1 SMP Mon Feb 26 20:37:57 EST 2007 x86_64 x86_64 x86_64 GNU/Linux How reproducible: Always, load i810 driver Steps to Reproduce: 1. Boot the machine 2. Panic after the initial graphica boot, before login screen 3. Panic during reboot, if first started in init 1, and then doing init 5 Actual results: The xorg.conf that is auto generated during installation is not valid, and is missing the Modes line in the Screen section. Vesa driver is the only one that works, any attemp to change the xorg.conf to load i810 causes kernel panic. The Expected results: i810 to load normally and does not cause crash. Additional info: relevant portion of lspci is: 00:00.0 Host bridge: Intel Corporation 82Q963/Q965 Memory Controller Hub (rev 02) 00:01.0 PCI bridge: Intel Corporation 82Q963/Q965 PCI Express Root Port (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) 00:02.1 Display controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) The machine is a Dell Optiplex 745 with 2 gig of memory, and the above intel chipset.
Created attachment 152948 [details] xorg.conf
One more comment: The installation never succeeded completely, as I could never reboot properly with i810 driver loaded. I just built kernel 2.6.20, with proper SATA option, and now everything is working properly. I can load i810 without any issues. Seems like the problem was the kernel i810 driver, and not the xorg i810_drv! I wonder if this is a kernel 2.6.18 issue, or redhat's modifications of it.
Kernel panic means kernel bug.
Can the reporter provide us a backtrace of the kernel panic message?
This problem might have been addressed by the agpgart fixes made during RHEL5.1 for bug 227391. Please report whether the RHEL5.1 beta kernel addresses this problem.
I just upgraded to this version of the kernel, i.e 2.6.18-53, but the issue still persists. I get a blank screen, after RHGB is done, and keyboard and mouse do not respond (frozen). I did not try to rsh from a different machine to see if I can get in though.
I had a Q963 on hand and had a try under RHEL5.1 GA (2.6.18-53), this issue can not be reproduced in my side. The installation process is OK with i810 driver (Although this is some errors info in log but it is just related with 3D.) and after installation, the booting/reboot/shutdown are all OK with i810 driver. In your last feedback, I'd like to know if you can get X log file (/var/log/X.0.log) and post it here after you updated the kernel (rsh?)? Or you still see the kernal panic after you updated your kernel? (Ps. Do you have a try of whole RHEL5.1 GA in this machine? Or you just update the kernel to 2.6.18-53 and still use the original system?)
I did install the latest kernel 2.6.18-53.1.14, but the result is still the same! If I boot with this kernel, the machine freezes after the graphical boot, at the point that login prompt get displayed. Kernel 2.6.20 works perfectly. Since the machine freezes completely (no mouse/keyboard, and no remote access) with black screen and then kernel panic shortly after, I can not get the X.0.log, nor can I get the kernel panic messages, unless I manually write the whole page. Is there just some particular info that you need? Or could you suggest a way that I can to this info? Thanks.
I just upgrade to RHEL 5.2, kernel version 2.6.18-92.1.6.el5, and the problem is resolved, machine no longer freezes with kernel panic following. Thanks, Homayoun
Marking closed based on Comment 9