Opened 12 years ago

Closed 11 years ago

#1637 closed bug (fixed)

Frozen empty desktop with an inert cursor on startup.

Reported by: meanwhile Owned by: axeld
Priority: normal Milestone: R1
Component: - General Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Today's Haiku build (don't know which revision#) mostly doesn't get beyond a blue background and frozen cursor. When wildly moving the mouse around during startup, the cursor sometimes moves a bit, but freezes up. Only once doing this, did I get a Tracker to show up, which then crashed soon after use. (First time trying Haiku on this particular PC)

Attachments (1)

debug231107.txt (60.2 KB ) - added by meanwhile 12 years ago.

Download all attachments as: .zip

Change History (15)

by meanwhile, 12 years ago

Attachment: debug231107.txt added

comment:1 by meanwhile, 12 years ago

Some background info: This PC doesn't run plain BeOS very well; it has a known issue with keyboards that occurs in some IBM desktops (keyboards just don't do anything on them). Recently I found that BeOS Dano runs on it without problems, and then Haiku was tried on it as well. The mouse is supposed to be recognized as standard mouse (and didn't come with a driver) and connects to PS/2 through an USB adapter. Keyboard is PS/2 and should also just run without drivers.

comment:2 by hunnia, 12 years ago

This may be related to the above ticket. I have an amd64 computer with sata drives and usb mouse. Installed on sda the newest snapshot. If I boot I get the screen, mouse pointer but no tracker. In the save mode I do get into the haiku shell, in which lot of commands work, but more complicated commands give: "Cannot initialize global fonts." If I disable USB in the BIOS the problem still exist. When I am in the empty screen with the mouse pointer, Ctrl-Alt-Enter does NOT open the Team Monitor. F12 enters kernel debug. Executing teams display (Here I write only the last word of each line) : syslo, waitfor, sh, regis, debug, net_s and app_s. a back trace indicate that I am in an idle tread. Vector 0x21 error code 0x0

comment:3 by meanwhile, 12 years ago

Forgot about this bug, sorry. Don't know if what hunnia describes is related, but my bug is no more; Haiku runs on said PC, and all peripherals do so too.

comment:4 by mmlr, 12 years ago

I think hunnia meant bug #1723 seems related. If this specific bug is fixed I suggest closing it and tracking the other issues with #1723.

in reply to:  4 comment:5 by hunnia, 12 years ago

Replying to mmlr:

I think hunnia meant bug #1723 seems related. If this specific bug is fixed I suggest closing it and tracking the other issues with #1723.

Yes. It is also similar to bug #1723, except for me F12 works as I indicated in the writeup. Should I relax or copy my report under #1723, or open a new bug number.

Meanwhile wrote: "my bug is no more." What happened. A newer version of haiku downloaded. Which version? Would be nice to know. :-)

comment:6 by meanwhile, 12 years ago

@hunnia: In retrospect, I guess it's because Haiku didn't have USB mouse support at the time the bug showed up. That would make sense if a USB mouse connected through a PS/2 adapter is still seen by the OS as a USB mouse. Anyways, the Haiku revision that's now used (hrev23705) boots with standard settings.

in reply to:  6 ; comment:7 by hunnia, 12 years ago

Replying to meanwhile:

@hunnia: In retrospect, I guess it's because Haiku didn't have USB mouse support at the time the bug showed up. That would make sense if a USB mouse connected through a PS/2 adapter is still seen by the OS as a USB mouse. Anyways, the Haiku revision that's now used (hrev23705) boots with standard settings.

Just to be safe, I disconnected all USB devices. Connected a standard PS2 mouse and the problem still exist for me. So except that F12 works for me, it is more like #1723. So should I relax or copy my report under #1723, or open a new bug number?

in reply to:  7 comment:8 by meanwhile, 12 years ago

Replying to hunnia:

Replying to meanwhile:

@hunnia: In retrospect, I guess it's because Haiku didn't have USB mouse support at the time the bug showed up. That would make sense if a USB mouse connected through a PS/2 adapter is still seen by the OS as a USB mouse. Anyways, the Haiku revision that's now used (hrev23705) boots with standard settings.

Just to be safe, I disconnected all USB devices. Connected a standard PS2 mouse and the problem still exist for me. So except that F12 works for me, it is more like #1723. So should I relax or copy my report under #1723, or open a new bug number?

Not sure, someone with a better view on teh technicalities can answer that one...mmlr perhaps?

comment:9 by mmlr, 12 years ago

The F12 panic was only introduced in usb_hid this weekend. So it's easily possible that F12 works for you because you have a PS2 keyboard or tested with a newer revision and a USB keyboard. It's really not technically possible for the OS to recognize your PS2 connected mouse as a USB device ;-). It is possible that there was some error in the PS2 drivers that was fixed in the meantime. Hunnia I think you should append your report to bug #1723 and then this bug can be closed.

in reply to:  9 comment:10 by hunnia, 12 years ago

Replying to mmlr:

The F12 panic was only introduced in usb_hid this weekend. So it's easily possible that F12 works for you because you have a PS2 keyboard or tested with a newer revision and a USB keyboard. It's really not technically possible for the OS to recognize your PS2 connected mouse as a USB device ;-). It is possible that there was some error in the PS2 drivers that was fixed in the meantime. Hunnia I think you should append your report to bug #1723 and then this bug can be closed.

I will do that. You can close this.

comment:11 by scottmc, 11 years ago

This one looks like it can be closed.

comment:12 by sdeken, 11 years ago

FWIW, even with more recent Haiku builds I am occasionally seeing this bug. I'm running Haiku in a VM. The next time I see it I'll panic and see if I can determine where it's getting held up.

in reply to:  4 comment:13 by scottmc, 11 years ago

Replying to mmlr:

I think hunnia meant bug #1723 seems related. If this specific bug is fixed I suggest closing it and tracking the other issues with #1723.

Seems this one should be closed as it's either been fixed, or it's the same as 1723.

comment:14 by anevilyak, 11 years ago

Resolution: fixed
Status: newclosed

Closing.

Note: See TracTickets for help on using tickets.