Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#5703 closed bug (fixed)

KDL on boot on HP Pavilion dv5

Reported by: cssvb94 Owned by: bonefish
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Latest Haiku GCC4 revision build. After passing the last boot-loader icon boot process halts and jumps into KDL. First showing "Out of MTRRs" then graphic related errors. Images are attached to the ticket. Hardware trying to boot onto: Laptop HP Pavilion dv5. Graphic card: NVidia 9600M GT (vendor id: 10DE, dev id: 0649). Also ticket #5167 is related to the same hardware.

Attachments (3)

2010-04-09 boot_1.jpg (321.8 KB) - added by cssvb94 9 years ago.
2010-04-09 boot_2.jpg (433.6 KB) - added by cssvb94 9 years ago.
SYSLOG00.TXT (104.5 KB) - added by cssvb94 9 years ago.
Boot syslog

Download all attachments as: .zip

Change History (12)

Changed 9 years ago by cssvb94

Attachment: 2010-04-09 boot_1.jpg added

Changed 9 years ago by cssvb94

Attachment: 2010-04-09 boot_2.jpg added

comment:1 Changed 9 years ago by bonefish

Please attach syslog. If you can't get it from within Haiku itself, please have a look at the Syslog subsection in http://dev.haiku-os.org/wiki/ReportingBugs#KernelBugs.

comment:2 Changed 9 years ago by cssvb94

I still can't get the syslog, even with the latest release the same situation occurs. I'll be happy to try anything you propose.

comment:3 in reply to:  2 Changed 9 years ago by korli

Replying to cssvb94:

I still can't get the syslog, even with the latest release the same situation occurs. I'll be happy to try anything you propose.

Could you boot with on screen debug and take pictures of the pages on screen ?

comment:4 Changed 9 years ago by bonefish

Replying to cssvb94:

I still can't get the syslog, even with the latest release the same situation occurs. I'll be happy to try anything you propose.

Type reboot in the KDL , enter the boot loader menu (holding down shift), enter the debug options menu and save the syslog to disk. You need a FAT32 formatted partition or USB stick to save it (plug in before rebooting). Otherwise you could at least display the syslog in the boot loader and take pictures of the first and last few pages (Home/End to jump to the start/end of the file).

comment:5 Changed 9 years ago by bonefish

Component: - GeneralSystem/Kernel
Owner: changed from nobody to axeld
Version: R1/alpha1R1/Development

BTW, in principle the panic is continuable, i.e. you could type co and continue the boot process -- possibly multiple times. There's a good chance that you'll be able to fully boot, though most likely the graphics will be screwed. Anyway, if it looks like the system is not KDLing anymore, wait a short time (maybe a minute) and the syslog should have been saved to disk. If you have some Linux you can boot on the same machine, you can mount the BFS partition and access the saved syslog (common/var/log/syslog).

If you have a FAT32 partition/USB stick the boot loader option mentioned above is the more convenient way.

comment:6 Changed 9 years ago by cssvb94

Got it! Thank you guys. Boot syslog attached bellow.

Changed 9 years ago by cssvb94

Attachment: SYSLOG00.TXT added

Boot syslog

comment:7 Changed 9 years ago by bonefish

Owner: changed from axeld to bonefish
Status: newin-progress

Thanks! The memory ranges are quite fragmented, so it's not exactly surprising that the algorithm is running out of MTRRs. I'll have a closer look tomorrow whether the algorithm can be made a bit more intelligent -- relaxing the uncached ranges when it's out of registers -- so that the system can at least run, though maybe with performance penalty.

comment:8 Changed 9 years ago by bonefish

Resolution: fixed
Status: in-progressclosed

Should be fixed in hrev36591 (trunk).

comment:9 Changed 9 years ago by cssvb94

Great! Thanks, it's fixed.

Note: See TracTickets for help on using tickets.