Bug 239068 - emulators/qemu: interrupt storm on "vec2016:" when booting FreeBSD/sparc64
Summary: emulators/qemu: interrupt storm on "vec2016:" when booting FreeBSD/sparc64
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Muhammad Moinur Rahman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-09 17:36 UTC by Alexey Dokuchaev
Modified: 2019-08-05 17:46 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (bofh)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Dokuchaev freebsd_committer 2019-07-09 17:36:29 UTC
Last year, I've been happily booting into my FreeBSD/sparc64 installation, to run occasional tests for some ports, using emulators/qemu and qemu-system-sparc64 program it provides.  It was rather slow, of course, but worked just fine.

Today I've tried to boot the same disk image on another machine, and thus had to freshly install emulators/qemu port, which is now at version 3.0.1, but VM went into endless interrupt storm during kernel boot process, after detecting the disk(s):

> interrupt storm detected on "vec2016:"; throttling interrupt source
> interrupt storm detected on "vec2016:"; throttling interrupt source
> interrupt storm detected on "vec2016:"; throttling interrupt source
> interrupt storm detected on "vec2016:"; throttling interrupt source
> ... and it never stops ...
Since I've been pretty positive that I could boot the very same VM file under FreeBSD before, I've downgraded to the previous version 2.12.1, but it behaved similarly.  Only after I've downgraded to version 2.9.0, I could finally boot into my VM successfully.

It would be nice if this regression could be identified and fixed.
Comment 1 Muhammad Moinur Rahman freebsd_committer 2019-07-09 18:20:51 UTC
If you are trying to boot from ISO can you please try to rebuild qemu turning off CDROM_DMA and retrying the installation? If you are running from a VM image please try to disable DMA of the HDD detected mostly for ATA or ATAPI.
Comment 2 Alexey Dokuchaev freebsd_committer 2019-07-15 12:05:00 UTC
(In reply to Muhammad Moinur Rahman from comment #1)

> If you are running from a VM image
Yes, I'm running from the VM disk image (not CD-ROM).

> please try to disable DMA of the HDD detected mostly for ATA or ATAPI.
I've tried to google how to do this and failed.  Gentoo and Ubuntu wikis also do not tell how to disable DMA.  Do do I do it?  Do I have to patch QEMU source code and rebuild it?
Comment 3 Muhammad Moinur Rahman freebsd_committer 2019-08-05 17:46:19 UTC
(In reply to Alexey Dokuchaev from comment #2)
Hi danfe,
I am sorry but I might have missed this reply. My first try would be to disable the option CDROM_DMA of qemu and rebuild it. Then retry.

Second option would be adding the hdd as SCSI rather than ATA. This is definitely a problem attached with either ATA or ATAPI.

In the earlier days we could do hw.ata.ata*_dma=0 which is no longer available.

dmesg would be highly helpful.