Opened 4 years ago

Closed 2 years ago

#15973 closed bug (duplicate)

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: #17349 Blocking:
Platform: x86

Description

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 (12)

comment:1 by diver, 4 years ago

How does it crash? Does it show any error?

in reply to:  1 comment:2 by stoltenberg, 4 years 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, 4 years ago

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

comment:4 by stoltenberg, 4 years ago

... give me a second ;-)

comment:5 by stoltenberg, 4 years ago

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

comment:6 by waddlesplash, 4 years ago

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

comment:7 by stoltenberg, 4 years ago

Sorry to ask this silly question, but where i can i find them inside the blacklist/directories?

Version 0, edited 4 years ago by stoltenberg (next)

comment:8 by stoltenberg, 4 years 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, 4 years 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, 4 years 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, 4 years ago

A syslog would probably help here.

comment:12 by waddlesplash, 2 years ago

Blocked By: 17349 added
Resolution: duplicate
Status: newclosed

If ipro100 was the issue, then this is almost certainly another instance of #17349. If it is not, well, hard to diagnose that without a syslog, which was never provided.

Note: See TracTickets for help on using tickets.