Opened 7 years ago

Closed 4 years ago

#8474 closed bug (fixed)

[intel_extreme] crashes in init_overlay_registers

Reported by: Eddy Owned by: axeld
Priority: normal Milestone: R1
Component: Drivers/Graphics/intel_extreme Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description (last modified by diver)

Kernel Panic after the end of the boot sequence.
Configuration:
Motherboard: Shuttle SZ68R5
CPU: Core i7 2600K
RAM: 16GB
SSD: Corsair 240GB Force GT
Display: Dual 24" (1920x1200), one on DVI, the other on HDMI

Attachments (6)

IMG_0003.jpg (896.6 KB) - added by Eddy 7 years ago.
Kernel Panic
KDL.JPG (2.2 MB) - added by Eddy 7 years ago.
KDL trace
BootLog.txt (82.1 KB) - added by Eddy 7 years ago.
Debug trace
BootLogWithUserBuildConfig.txt (81.8 KB) - added by Eddy 7 years ago.
syslog_12_02_13 (159.1 KB) - added by Eddy 5 years ago.
syslog from December 2nd 2013
Syslog.txt (126.3 KB) - added by Eddy 5 years ago.
Serial debug, nothing is disabled.

Change History (38)

Changed 7 years ago by Eddy

Attachment: IMG_0003.jpg added

Kernel Panic

comment:1 Changed 7 years ago by diver

Blocked By: 5221 added
Description: modified (diff)
Resolution: duplicate
Status: newclosed
Summary: intel_extreme[intel_extreme] crashes in init_overlay_registers

Try to enable Use fail-safe video mode. DVI is not yet supported, see #5221 and I think the same is true for HDMI.

comment:2 Changed 7 years ago by axeld

Blocked By: 5221 removed
Resolution: duplicate
Status: closedreopened

The crash certainly has nothing to do with #5221, even if that one will probably finally prevent the driver to work as well.

comment:3 Changed 7 years ago by Eddy

I have removed the intel_extreme driver. The kernel panic arises with a white line (boot from usb key). I have disabled my USB3 controller. The same kernel panic arises (white lines).

I assume this is not an intel_extreme issue. I will try to get a syslog for this and I will publish it if I succeed.

comment:4 Changed 7 years ago by Eddy

I cannot get any syslog. The common/var/log directory is empty.

comment:5 Changed 7 years ago by diver

Could you take a photo of KDL. Without intel_extreme driver it should be different from the attached one.

Changed 7 years ago by Eddy

Attachment: KDL.JPG added

KDL trace

comment:6 Changed 7 years ago by Eddy

After compiling the latest version and removing the intel_extreme I finally get a KDL (before that I had a blue and white screen without text). So the file has been attached.

Last edited 7 years ago by anevilyak (previous) (diff)

comment:7 Changed 7 years ago by umccullough

Out of curiosity, does your machine complete a memtest86+ pass without issues?

comment:8 Changed 7 years ago by anevilyak

Another question: are you able to type in KDL? If so, if you type reboot from there, and then enter the boot loader options (by holding left shift before the splash screen comes up), is there an option to view the previous syslog? If there is, it can also optionally be saved to a a fat32 usb stick, which might help shed a bit more light on what's actually going on here.

comment:9 Changed 7 years ago by Eddy

I am unable to use my USB keyboard (no USB switch, directly connected on the back panel USB ports). The memtest86+ is in progress 46% and up to now everything is fine. As I cannot do anything whenever the KDL arise I have ordered an USB to RS32, a null modem cable and the RS232 extension of my shuttle. Hope to be able to solve those problems. I really want to see my computer running Haiku without emulation.

Last edited 6 years ago by mmadia (previous) (diff)

comment:10 Changed 7 years ago by diver

You should be able to type using PS/2 keyboard.

comment:11 in reply to:  9 ; Changed 7 years ago by umccullough

Replying to Eddy:

The memtest86+ is in progress 46% and up to now everything is fine.

Good, sounds like there's not likely a memory issue then (it will usually fail within the first couple tests)

As I cannot do anything whenever the KDL arise I have ordered an USB to RS32, a null modem cable and the RS232 extension of my shuttle. Hope to be able to solve those problems. I really want to see my computer running Haiku without emulation.

Actually, I don't think that will work. In order to do serial log capture, you will need a real COM port on the motherboard in order to connect to a second computer. Using a USB adapter requires a driver that uses the USB stack to communicate with the device. The USB stack cannot actually run while in KDL (because KDL halts all execution of the OS, drivers, etc.), which is also basically why you're having issues with your keyboard.

If your computer has PS2 ports, then you should attempt to use a keyboard attached to that - if it does not, there are some options for having the BIOS take control back of the keyboard, but I think that only works when it is connected to a USB1.1 hub or something?

Last edited 6 years ago by mmadia (previous) (diff)

comment:12 in reply to:  11 Changed 7 years ago by umccullough

Replying to umccullough:

As I cannot do anything whenever the KDL arise I have ordered an USB to RS32, a null modem cable and the RS232 extension of my shuttle. Hope to be able to solve those problems. I really want to see my computer running Haiku without emulation.

Actually, I don't think that will work. In order to do serial log capture, you will need a real COM port on the motherboard in order to connect to a second computer. Using a USB

Unless I misunderstood - and you're just getting the USB->RS232 adapter for your second computer?

Last edited 6 years ago by mmadia (previous) (diff)

comment:13 in reply to:  11 ; Changed 7 years ago by Eddy

Replying to umccullough:

Replying to Eddy:

The memtest86+ is in progress 46% and up to now everything is fine.

Good, sounds like there's not likely a memory issue then (it will usually fail within the first couple tests)

As I cannot do anything whenever the KDL arise I have ordered an USB to RS32, a null modem cable and the RS232 extension of my shuttle. Hope to be able to solve those problems. I really want to see my computer running Haiku without emulation.

Actually, I don't think that will work. In order to do serial log capture, you will need a real COM port on the motherboard in order to connect to a second computer. Using a USB adapter requires a driver that uses the USB stack to communicate with the device. The USB stack cannot actually run while in KDL (because KDL halts all execution of the OS, drivers, etc.), which is also basically why you're having issues with your keyboard.

I now have a serial port on my computer (direct COM port extension)

If your computer has PS2 ports, then you should attempt to use a keyboard attached to that - if it does not, there are some options for having the BIOS take control back of the keyboard, but I think that only works when it is connected to a USB1.1 hub or something?

Unfortunately, no PS2 port. i hope that the serial debug will be successful. Anyway do you know how to set it ? Is it part of the userbootscript? I know that there is a keyboard emulation via usb as long as the usb controller has not been initialized. But I did not deeply dig into the data sheet to check this.

Last edited 6 years ago by mmadia (previous) (diff)

comment:14 in reply to:  9 Changed 7 years ago by Eddy

Replying to Eddy:

I am unable to use my USB keyboard (no USB switch, directly connected on the back panel USB ports). The memtest86+ is in progress 46% and up to now everything is fine. As I cannot do anything whenever the KDL arise I have ordered an USB to RS32, a null modem cable and the RS232 extension of my shuttle. Hope to be able to solve those problems. I really want to see my computer running Haiku without emulation.

The memtest86+ was successful.

Last edited 6 years ago by mmadia (previous) (diff)

comment:15 in reply to:  13 Changed 7 years ago by anevilyak

Replying to Eddy:

Unfortunately, no PS2 port. i hope that the serial debug will be successful. Anyway do you know how to set it ? Is it part of the userbootscript?

On a nightly build, serial debug is enabled by default.

comment:16 Changed 7 years ago by Eddy

I have finally received everything, so now a complete debug trace has been done. Hope this helps.

comment:17 Changed 7 years ago by diver

BootLog.txt indicates that you still have intel_extreme driver. Could you get another bootlog without it?

Changed 7 years ago by Eddy

Attachment: BootLog.txt added

Debug trace

comment:18 in reply to:  17 ; Changed 7 years ago by Eddy

Replying to diver:

BootLog.txt indicates that you still have intel_extreme driver. Could you get another bootlog without it?

Sorry for the mistake. I have removed the intel_extreme driver, but then I connect launch any command. The BootLog file has been updated.

Last edited 7 years ago by Eddy (previous) (diff)

comment:19 in reply to:  18 ; Changed 7 years ago by anevilyak

Replying to Eddy:

Sorry for the mistake. I have removed the intel_extreme driver, but then I connect launch any command. The BootLog file has been updated.

As you appear to be building your own images, try the following:

In your UserBuildConfig, add the line:

AddFilesToHaikuImage system add-ons kernel debugger <kdebug>auto_stack_trace ;

Rebuild, then try again (with intel_extreme removed). With any luck that will at least get us a backtrace. In any event going off the tail end of the boot log, something appears to go wrong while initializing the PS2 subsystem.

comment:20 in reply to:  19 Changed 7 years ago by Eddy

Replying to anevilyak:

Replying to Eddy:

Sorry for the mistake. I have removed the intel_extreme driver, but then I connect launch any command. The BootLog file has been updated.

As you appear to be building your own images, try the following:

In your UserBuildConfig, add the line:

AddFilesToHaikuImage system add-ons kernel debugger <kdebug>auto_stack_trace ;

Rebuild, then try again (with intel_extreme removed). With any luck that will at least get us a backtrace. In any event going off the tail end of the boot log, something appears to go wrong while initializing the PS2 subsystem.

I did it but there is no change in the trace. Just slight values. Check the second trace.

Changed 7 years ago by Eddy

comment:21 Changed 7 years ago by anevilyak

If both your keyboard and mouse are USB, you could hypothetically try removing /system/add-ons/kernel/bus_managers/ps2 and see if that gets you further or if that simply results in a panic elsewhere.

comment:22 in reply to:  21 Changed 7 years ago by Eddy

Replying to anevilyak:

If both your keyboard and mouse are USB, you could hypothetically try removing /system/add-ons/kernel/bus_managers/ps2 and see if that gets you further or if that simply results in a panic elsewhere.

What I did was removing my keyboard and replacing it with another one. And it is working now. I have a Unicomp USB keyboard with the French keycap. I now changed for a playstation 2 American keyboard. Maybe later I will try to understand the reason this keyboard is not working.

comment:23 Changed 7 years ago by Eddy

Thanks everybody for your help.

comment:24 Changed 7 years ago by Eddy

Ok, so it worked once but after a reboot the same issue occurs again. So the keyboard is not the only cause. KDL arises after plugging/unplugging USB peripherals (hub from my monitors, mouse not being recognized).

comment:25 Changed 6 years ago by korli

Could you please check with a current revision and provide a syslog? Thanks!

Changed 5 years ago by Eddy

Attachment: syslog_12_02_13 added

syslog from December 2nd 2013

comment:26 Changed 5 years ago by Eddy

Sorry for taking so long login/password issues. I have just uploaded the latest syslog.

comment:27 in reply to:  26 ; Changed 5 years ago by korli

Replying to Eddy:

Sorry for taking so long login/password issues. I have just uploaded the latest syslog.

No crash in this syslog. Did you force vesa or anything?

comment:28 in reply to:  27 ; Changed 5 years ago by Eddy

Replying to korli:

Replying to Eddy:

Sorry for taking so long login/password issues. I have just uploaded the latest syslog.

No crash in this syslog. Did you force vesa or anything?

Yes, I have to force Vesa because of a sandybridge desktop computer. But before, even the keyboard was leading to a system crash which is not the case anymore (usb drivers might have improved).

comment:29 in reply to:  28 Changed 5 years ago by korli

Replying to Eddy:

Yes, I have to force Vesa because of a sandybridge desktop computer. But before, even the keyboard was leading to a system crash which is not the case anymore (usb drivers might have improved).

Can you attach a syslog without force vesa? or the result is the same as IMG_0003.jpg​?

comment:30 Changed 5 years ago by Eddy

I have just saved the serial debug. The fact is I no more have a KDL, instead both my monitors loses the synchro as the intel driver only support integrated display (notebook compatibility only.

Changed 5 years ago by Eddy

Attachment: Syslog.txt added

Serial debug, nothing is disabled.

comment:31 in reply to:  30 Changed 5 years ago by korli

Replying to Eddy:

I have just saved the serial debug. The fact is I no more have a KDL, instead both my monitors loses the synchro as the intel driver only support integrated display (notebook compatibility only.

I'd suggest to close this bug report then.

comment:32 Changed 4 years ago by luroh

Resolution: fixed
Status: reopenedclosed
Note: See TracTickets for help on using tickets.