Opened 11 months ago

Last modified 11 months ago

#15973 new bug

Nightly hrev54134-x86 crashes after boot process

Reported by: stoltenberg Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: - General Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: x86


Just wanted to try the hrev54134 on my vintage ThinkPad, but it crashes after the boot process and the (complete) array of icons. Safe mode runs fine.

Change History (11)

comment:1 by diver, 11 months ago

How does it crash? Does it show any error?

in reply to:  1 comment:2 by stoltenberg, 11 months ago

No error messages, it just freezes. Sometimes the "boot floater with the icons" moves to the right in front of the black screen, sometimes it shows the blue desktop with centered pointer and freezes there.

comment:3 by waddlesplash, 11 months ago

Try enabling "Fail-safe video mode" without Safe mode.

comment:4 by stoltenberg, 11 months ago

... give me a second ;-)

comment:5 by stoltenberg, 11 months ago

Yes, some progress: It boots until complete desktop including menubar, icons and wallpaper, but freezes right here.

comment:6 by waddlesplash, 11 months ago

Try blacklisting all network drivers and see if that changes anything.

comment:7 by stoltenberg, 11 months ago

Don't know how, but i've found a set of more or less network-related drivers and was able to boot with success. Any idea how to isolate the relevant driver(s)?

Last edited 11 months ago by stoltenberg (previous) (diff)

comment:8 by stoltenberg, 11 months ago

I'm not 100% sure at this point, but especially the ipro100, which is essential for my machine, seems to be part of the trouble.

comment:9 by pulkomandy, 11 months ago

I think I have an ipro100 machine somewhere here if closer inspection/debugging of that is needed. Booted fine last week but I had no ethernet cable connected to it.

in reply to:  9 comment:10 by stoltenberg, 11 months ago

Good point. Tested without LAN-cable right now. Fascinating effect of a blue desktop with a black area at the bottom ;-)

comment:11 by pulkomandy, 11 months ago

A syslog would probably help here.

Note: See TracTickets for help on using tickets.