Opened 11 years ago

Closed 8 years ago

#2050 closed bug (invalid)

Bootscreen stops at 4th icon on Abit IP35

Reported by: biffuz Owned by: marcusoverhagen
Priority: normal Milestone: R1
Component: Drivers/Disk Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Hi,

I replaced my ASRock with an Abit IP35, and when I try to boot Haiku (hrev24870 downloaded from Build Factory), it stops at the fourth icon. However, I can go into KDL and get a stack crawl. This board has not a serial port, so I had to get a "screenshot" :-)

Attachments (2)

IMG_2259.JPG (339.4 KB ) - added by biffuz 11 years ago.
sc on KDL
syslog (392.2 KB ) - added by biffuz 11 years ago.
syslog after detaching SATA DVD-RW

Download all attachments as: .zip

Change History (16)

comment:1 by axeld, 11 years ago

And where is that? Does it end up in KDL by itself, or do you have to press F12 in order to get there? In the former case, a stack crawl would be very helpful, in the latter it would be useless.

If it's in fact the latter, please enable "on screen debug output" in the safe boot menu, and make a shot of the last screen you see (you'll have to press a key after each screen to continue).

Do you have a SATA disk, BTW?

by biffuz, 11 years ago

Attachment: IMG_2259.JPG added

sc on KDL

in reply to:  1 comment:2 by biffuz, 11 years ago

Replying to axeld:

And where is that? Does it end up in KDL by itself, or do you have to press F12 in order to get there? In the former case, a stack crawl would be very helpful, in the latter it would be useless.

I can press F12. Well, I attached it anyway :-)

If it's in fact the latter, please enable "on screen debug output" in the safe boot menu, and make a shot of the last screen you see (you'll have to press a key after each screen to continue).

Why didn't I thought of that? I'll do asap.

Do you have a SATA disk, BTW?

The disk is IDE, connected to (of course) the one and only IDE port of this board. There's a DVD-ROM as slave. I also coonected an IDE DVD-RW to the first SATA port with an adapter, do you think I should try to detach it?

comment:3 by biffuz, 11 years ago

I tried with on screen debug output, and I get several pages of an error, you can see it in the syslog I'm going to attach. At last page, it says:

IDE: scan_device_int: waiting 100ms... More than 99% interrupts of vector 10 are hunandled Last message repeated 378 times. ide: ide_timeout() bus 90d5e700 More than 99% interrupts of vector 10 are hunandled

and here it stops.

Both errors are relative to the SATA controllers, so I tried to detach the DVD-RW on the SATA port, and booting went fine! I picked the syslog, so you can see at least the first of the errors.

by biffuz, 11 years ago

Attachment: syslog added

syslog after detaching SATA DVD-RW

comment:4 by umccullough, 11 years ago

Disclaimer: I have different hardware, but also experiencing the same problems now as well.

I recently started running into the same thing on my Dell Optiplex GX270 machine (which previously worked perfectly).

I started having the problem when I changed from using a 40gb IDE (UDMA PATA) disk for Haiku to using a 80gb SATA disk instead. (no SATA disks were in use on this machine previously).

In my case, the CDROM is still connected to the PATA controller.

My on-screen debug output looks very similar referencing the "99% interrupts unhandled".

I haven't tried the newer ata driver vs the ide driver yet - so I haven't logged a ticket. Is there a proper way to debug this otherwise?

comment:5 by stippi, 11 years ago

Component: - GeneralDrivers/Disk
Owner: changed from axeld to marcusoverhagen

Based on this info, I am reassigning to Marcus. Could be wrong though.

comment:6 by umccullough, 11 years ago

FWIW, I replaced the ide bus_manager with the newer ata version and that seemed to clear it up. Of course, I also update to the latest rev, so I will switch back and make sure it still fails with the older "ide" version.

Also, I thought it was still broken as it hangs on the 4th icon for 10-15 seconds before continuing - and definitely seems slower than it was with the PATA disk.

Anyhow, probably going to switch back to the PATA disk in the next couple days until the situation improves, unless there is anything further I can test and provide now.

comment:7 by marcusoverhagen, 11 years ago

Status: newassigned

The screenshot shows that ide bus_manager gets stuck in scan_device_int. The ide bus_manager triggers an interrupt but never acknowledges it.

This bug is fixed in the ata bus_manager, but as it's still unfinished, is has a few other bugs, for example a timeout problem when accessing ATAPI devices. I plan to fix those pretty soon and switch Haiku to the ata bus_manager.

comment:8 by scottmc, 11 years ago

This sounds a lot like #1444.

comment:9 by richienyhus, 10 years ago

With Haiku now using the ata bus_manager, shouldn't this ticket be fixed?

comment:10 by biffuz, 10 years ago

I still own that board, so I can give it a try.

comment:11 by biffuz, 9 years ago

Tested the board with R1A2, dd'ed to a IDE disk.

Works fine without any SATA device, or with a SATA disk and SATA controller set to AHCI mode in BIOS.

Things go bad when set the controller is set as IDE. So bad, actually, that the on-screen debug output changes every time :-( Sometimes it lands into KDL, sometimes it doesn't. Even worse, sometimes the screens is messed up and unreadable - well, not really unreadable, but the printed strings are messed up and misaligned, right now I read one line "rermeomvoev_em_emmeomroyr_yt_ytyep_er_arnagneg(e9(69,6 ,0 x07xf7efee3030000,0 ,0 x01x010000,0 ,0 )0". Hardly of any help.

I was worried, so I tried MemTest and it runs ok.

Lastly, disabling IDE DMA in the boot menu works, but of course the system becomes very slow.

comment:12 by scottmc, 8 years ago

Can you recheck this with a recent Haiku build? Let us know if there's any changes since the last time you checked this.

comment:13 by biffuz, 8 years ago

Unfortunately, I no longer have that board, sorry.

comment:14 by korli, 8 years ago

Resolution: invalid
Status: in-progressclosed
Note: See TracTickets for help on using tickets.