Ticket #1925 (new bug)

Opened 10 months ago

Last modified 2 months ago

Reboot during startup on Toshiba Satellite 2615DVD/6.0

Reported by: umccullough Owned by: axeld
Priority: normal Milestone: R1
Component: System/Kernel Version: R1 development
Cc: Blocked By:
Platform: x86 Blocking:

Description

Booting Haiku natively on this laptop causes it to reboot shortly after showing the HAIKU logo at the bottom of the screen. Tried disabling all options in boot menu, and it won't boot into Safe Mode either.

Possibly something I've done wrong, or possible the funky hardware on this laptop (some Linux LiveCDs hang at boot on this machine also - but usually after the X server is started).

Laptop is an older Toshiba Satellite 2615DVD/6.0:

PII Celeron running at ~430mhz 192MB RAM 6GB disk with Linux on it (first partition on the drive is ~256mb for Haiku)

Attaching serial debug log. lspci output will be attached shortly.

Note: this was built and installed directly to the partition from within Xubuntu 7.10 which generally doesn't give me any problems on other machines.

Attachments

tosh_sat_r24408.txt (10.6 KB) - added by umccullough 10 months ago.
Toshiba Satellite boot failure log
lspci.txt (1.1 KB) - added by umccullough 10 months ago.
lspci -nn output
tosh_sat_r24494_with_trace.txt (11.5 KB) - added by umccullough 10 months ago.
New serial log with TRACE_VM and TRACE_FAULTS enabled
tosh_sat_r24636_trace_vm_and_trace_mmu.txt (171.9 KB) - added by umccullough 9 months ago.
New trace with TRACE_MMU and TRACE_VM enabled
Haiku_r27641_tosh_sat.txt (5.3 KB) - added by umccullough 4 months ago.
new failure during boot with r27641
ubuntu_dmesg_toshiba.txt (20.4 KB) - added by umccullough 2 months ago.
dmesg output from ubuntu

Change History

Changed 10 months ago by umccullough

Toshiba Satellite boot failure log

Changed 10 months ago by umccullough

lspci -nn output

Changed 10 months ago by umccullough

Should also add that it was r24408 built with gcc2.95.3 and configured with --include-gpl-addons and --include-3rdparty

Changed 10 months ago by jackburton

I have seen a similar issue on an HP DC 7600 (Pentium 4), booting from CD. I haven't filed a bug yet because I don't have the pc at hand to do tests (it's not my pc). I was able to boot further (it then panics by not finding a boot volume) by disabling the "use APIC I/O" (or something similar) option in the bios.

Changed 10 months ago by umccullough

Good idea. I will try messing with some of the more obscure BIOS settings and see if that changes my results.

Will update in a day or two with any results I find.

Changed 10 months ago by umccullough

I was unable to find any BIOS options that would change the behavior. (The Toshiba BIOS on this laptop is amazingly stupid).

I suppose it's time for me to start adding some trace code to find where it fails - any recommendations on where to start based on the attached serial log?

Changed 10 months ago by umccullough

New serial log with TRACE_VM and TRACE_FAULTS enabled

Changed 10 months ago by umccullough

I attached a new serial log from Haiku r24494 and I enabled TRACE_VM and TRACE_FAULTS in vm.cpp (had to comment out a trace line that didn't compile, btw).

Looks like it maybe fails in find_and_insert_area_slot()

Anything I can try or provide to further identify the cause here?

Changed 10 months ago by axeld

The line "PANIC: looking up page failed for pa 0x41433000" can only be caused by vm_create_anonymous_area() when it tries to create areas for already bound memory. There seems to be something seriously wrong there, which is also underpinned by the fact that it doesn't find its way into the debugger.

Could you also provide the output of TRACE_MMU in boot/platform/bios_ia32/mmu.cpp?

Would it be possible that the memory is corrupt on this machine? Does it work flawlessly with other operating systems?

Changed 10 months ago by umccullough

It does work fine with Xubuntu on it (in fact, I used Xubuntu on this very machine to build Haiku onto the other partition) and previously had Windows XP on it with no issues that I ever recall.

I believe I ran memtest86+ the other day to verify that very notion - but I only let it run through the first couple tests (as these usually find bad ram quickly in my experience). However, if it's a subtle memory issue I can let memtest86+ run through an ENTIRE pass of tests one night and see what it throws out.

I will also turn on the TRACE_MMU and rebuild soon and report back my results.

Changed 10 months ago by axeld

Don't worry about that; if other systems run that stable, there is something wrong with Haiku, I'd guess. It will probably corrupt some memory at some point of the boot process.

Changed 9 months ago by umccullough

New trace with TRACE_MMU and TRACE_VM enabled

Changed 9 months ago by umccullough

Added another serial log with TRACE_MMU and TRACE_VM enabled.

LOTS of info in this one :/

Changed 7 months ago by powelly

I have the exact same problem with booting Haiku r25852 on a Toshiba Satellite Pro 4270. The boot process fails at the same place with the same PANIC messages.

I've had Win98, Ubuntu 8.04 and BeOS R5 running fine on the laptop.

Feel free to contact me if you'd like me to do any testing on this machine.

Changed 4 months ago by umccullough

I've been testing revisions every few weeks on this same laptop with no change in result until recently.

I just finally got around to testing r27470 and noticed that instead of an immediate reboot, it now hangs at the boot screen with *no* icons lit.

Unfortunately I haven't had a chance to dig any deeper yet, I'll try to get a serial log and try going back some revs to find out what changed.

I will do so shortly.

Changed 4 months ago by umccullough

new failure during boot with r27641

Changed 2 months ago by umccullough

dmesg output from ubuntu

Changed 2 months ago by umccullough

I attached dmesg output from ubuntu (currently gOS 3.0 beta) in hopes that it might yield something of interest that is specific to this machine in the early boot process.

Note: See TracTickets for help on using tickets.