Dev1 Galaxy Forum / Strange thing appearing during boot

Re: Strange thing appearing during boot

dummy@example.com (fsmithred) — Fri, 17 Apr 2020 10:10:17 +0000

GRUB_CMDLINE_LINUX_DEFAULT="quiet iommu=soft"
might work? I am not very knowledgeable in how to handle this.

Yes, that will work. Run update-grub to generate a new boot menu after you edit the file.

Re: Strange thing appearing during boot

dummy@example.com (toru) — Fri, 17 Apr 2020 10:03:57 +0000

I already have firmware-atheros. Thank you for the attempts at helping. My WLAN device appears to work.

I used update-pciids now and upon looking it up, it appears that iommu=soft can be placed in /etc/default/grub. Is that correct?

If it is, I'll give it a try. I guess editing:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet iommu=soft"
might work? I am not very knowledgeable in how to handle this.

Apologies for my late reply.

Re: Strange thing appearing during boot

dummy@example.com (aus9) — Sun, 12 Apr 2020 23:00:50 +0000

fsmithred wrote

You need to enable the non-free repository to get it with apt

Yeah well I did not even an entry for it. Just made one now in /etc/apt/sources.list

deb http://deb.devuan.org/merged beowulf non-free

Maybe....add that line with it commented out for members to easily spot....
In the next test release?

either in above file or a file under /etc/apt/sources.list.d/

cheers

Re: Strange thing appearing during boot

dummy@example.com (fsmithred) — Sun, 12 Apr 2020 16:05:52 +0000

firmware-atheros is "in" the devuan repository:

$ apt-cache policy firmware-atheros
firmware-atheros:
  Installed: (none)
  Candidate: 20190114-2
  Version table:
     20190114-2 500
        500 http://deb.devuan.org/merged beowulf/non-free amd64 Packages

Like most of the packages in devuan, it gets pulled from debian and merged with our repo of forked packages. We don't actually host the un-forked packages on devuan servers.

You need to enable the non-free repository to get it with apt.

Re: Strange thing appearing during boot

dummy@example.com (aus9) — Sun, 12 Apr 2020 13:29:24 +0000

We know you have the 9377 WLAN device, so if you do wish to pursue that it will need a firmware file and
I can not find it in Devuan at the moment.

I did find
https://packages.debian.org/buster/firmware-atheros
which contains those fw files

Re: Strange thing appearing during boot

dummy@example.com (Head_on_a_Stick) — Sun, 12 Apr 2020 09:23:19 +0000

Try the iommu=soft kernel command line parameter.

And for outdated PCI IDs use

# update-pciids

Re: Strange thing appearing during boot

dummy@example.com (toru) — Sun, 12 Apr 2020 08:52:00 +0000

Magnus wrote:

Iommu has with virtualisation to do. To run virtual system like Gnome Boxes or Virtualbox. Is virtualisation on in your BIOS?
https://en.wikipedia.org/wiki/Input–out … ement_unit

Yes, it is enabled in the BIOS.

It is maybe worthy of note that the iommu lines often don't appear with these other lines, when these other lines show up. Also, since it seems that none of these lines showed up during this boot, it seems like perhaps all of them don't always show up. The non-iommu lines are common, though.

Re: Strange thing appearing during boot

dummy@example.com (toru) — Sun, 12 Apr 2020 08:38:20 +0000

The atheros device is a wireless LAN device that I installed a driver for but am not using for internet presently.

Here's the output for modinfo ath10k_pci:

filename:       /lib/modules/4.19.0-0.bpo.6-amd64/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
firmware:       ath10k/QCA9377/hw1.0/board.bin
firmware:       ath10k/QCA9377/hw1.0/firmware-5.bin
firmware:       ath10k/QCA9377/hw1.0/firmware-6.bin
firmware:       ath10k/QCA6174/hw3.0/board-2.bin
firmware:       ath10k/QCA6174/hw3.0/board.bin
firmware:       ath10k/QCA6174/hw3.0/firmware-6.bin
firmware:       ath10k/QCA6174/hw3.0/firmware-5.bin
firmware:       ath10k/QCA6174/hw3.0/firmware-4.bin
firmware:       ath10k/QCA6174/hw2.1/board-2.bin
firmware:       ath10k/QCA6174/hw2.1/board.bin
firmware:       ath10k/QCA6174/hw2.1/firmware-5.bin
firmware:       ath10k/QCA6174/hw2.1/firmware-4.bin
firmware:       ath10k/QCA9887/hw1.0/board-2.bin
firmware:       ath10k/QCA9887/hw1.0/board.bin
firmware:       ath10k/QCA9887/hw1.0/firmware-5.bin
firmware:       ath10k/QCA988X/hw2.0/board-2.bin
firmware:       ath10k/QCA988X/hw2.0/board.bin
firmware:       ath10k/QCA988X/hw2.0/firmware-5.bin
firmware:       ath10k/QCA988X/hw2.0/firmware-4.bin
firmware:       ath10k/QCA988X/hw2.0/firmware-3.bin
firmware:       ath10k/QCA988X/hw2.0/firmware-2.bin
license:        Dual BSD/GPL
description:    Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices
author:         Qualcomm Atheros
alias:          pci:v0000168Cd00000050sv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000042sv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000046sv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000056sv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000040sv*sd*bc*sc*i*
alias:          pci:v0000168Cd0000003Esv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000041sv*sd*bc*sc*i*
alias:          pci:v0000168Cd0000003Csv*sd*bc*sc*i*
alias:          pci:v00000777d000011ACsv*sd*bc*sc*i*
depends:        ath10k_core
retpoline:      Y
intree:         Y
name:           ath10k_pci
vermagic:       4.19.0-0.bpo.6-amd64 SMP mod_unload modversions 
signat:         PKCS#7
signer:         
sig_key:        
sig_hashalgo:   md4
parm:           irq_mode:0: auto, 1: legacy, 2: msi (default: 0) (uint)
parm:           reset_mode:0: auto, 1: warm only (default: 0) (uint)

I haven't yet figured out what to do with that link.

lspci:

03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)
	Subsystem: Lite-On Communications Inc QCA9377 802.11ac Wireless Network Adapter
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-

inxi:

Graphics:  Card: Advanced Micro Devices [AMD/ATI] Device 98e4
           bus-ID: 00:01.0 chip-ID: 1002:98e4
           Display Server: X.org 1.19.2 drivers: ati,vesa (unloaded: modesetting,fbdev,radeon)
           tty size: 80x24 Advanced Data: N/A for root

I'll check the virtualization.



Re: Strange thing appearing during boot
dummy@example.com (Magnus) — Sun, 12 Apr 2020 08:15:19 +0000
Iommu has with virtualisation to do. To run virtual system like Gnome Boxes or Virtualbox. Is virtualisation on in your BIOS?
https://en.wikipedia.org/wiki/Input–out … ement_unit


Re: Strange thing appearing during boot
dummy@example.com (aus9) — Sun, 12 Apr 2020 07:42:10 +0000
Hi
until you get a better reply.....are you using that Atheros device for your internet?
if so you may like to run with root powers
modinfo ath10k_pci
you will see some firmware files may be required.
but the list of PCI IDS in that command are misleading. Instead
https://pci-ids.ucw.cz/v2.2/pci.ids might be easier to search for your device.
also as a non-root user....but do not post full output please....just your network device if you have any concerns
lspci -vvv
should show you the details of your device.
2) I assume you are using AMD graphics? if so post
inxi -Gxxx


Strange thing appearing during boot
dummy@example.com (toru) — Sun, 12 Apr 2020 06:09:18 +0000
This only appears to happen during boot, it doesn't seem to get recorded in the syslog after boot.  I am not even sure if this is really a problem, or not.  But it doesn't look like the kind of thing that is best ignored without even looking into it.  Please, shed some light on it.
I value your time, I know you have things to do, and I am grateful for any assistance I may get.
Apr 11 02:09:49  kernel: [   49.332395] amd_iommu_report_page_fault: 101 callbacks suppressed
Apr 11 02:09:49  kernel: [   49.332401] ath10k_pci 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff826a0 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.332469] ath10k_pci 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff826d0 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.332528] ath10k_pci 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff82650 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.332580] ath10k_pci 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff82660 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.332632] ath10k_pci 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff82650 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.332683] ath10k_pci 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff826c0 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.332734] ath10k_pci 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff826b0 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.332786] ath10k_pci 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff826a0 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.332837] ath10k_pci 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff82680 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.332888] ath10k_pci 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000fff82670 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.332939] amd_iommu_report_page_fault: 91 callbacks suppressed
Apr 11 02:09:49  kernel: [   49.332941] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.0 domain=0x0000 address=0x00000000fff826d0 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.332992] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.0 domain=0x0000 address=0x00000000fff82700 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.333043] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.0 domain=0x0000 address=0x00000000fff82720 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.333093] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.0 domain=0x0000 address=0x00000000fff82640 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.333143] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.0 domain=0x0000 address=0x00000000fff82640 flags=0x0020]
Apr 11 02:09:49  kernel: [   49.333193] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.0 domain=0x0000 address=0x00000000fff826e0 flags=0x0020]