The officially official Devuan Forum!

You are not logged in.

#1 2020-04-12 06:09:18

toru
Member
Registered: 2020-04-12
Posts: 15  

Strange thing appearing during boot

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]

Last edited by toru (2020-04-12 06:09:53)

Offline

#2 2020-04-12 07:42:10

aus9
Member
Registered: 2020-03-24
Posts: 37  

Re: Strange thing appearing during boot

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

Last edited by aus9 (2020-04-12 07:44:55)

Offline

#3 2020-04-12 08:15:19

Magnus
Member
Registered: 2020-03-14
Posts: 8  

Re: Strange thing appearing during boot

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

Offline

#4 2020-04-12 08:38:20

toru
Member
Registered: 2020-04-12
Posts: 15  

Re: Strange thing appearing during boot

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 41
	Region 0: Memory at f0800000 (64-bit, non-prefetchable) [size=2M]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
		Address: fee00000  Data: 0000
		Masking: 000000fe  Pending: 00000000
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 0.000W
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, OBFF Via message
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr+ BadTLP- BadDLLP+ Rollover- Timeout- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
	Capabilities: [148 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [168 v1] Device Serial Number 00-00-00-00-00-00-00-00
	Capabilities: [178 v1] Latency Tolerance Reporting
		Max snoop latency: 0ns
		Max no snoop latency: 0ns
	Capabilities: [180 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=50us PortTPowerOnTime=10us
		L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-
			   T_CommonMode=0us LTR1.2_Threshold=0ns
		L1SubCtl2: T_PwrOn=10us
	Kernel driver in use: ath10k_pci
	Kernel modules: ath10k_pci

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.

Last edited by toru (2020-04-12 08:38:45)

Offline

#5 2020-04-12 08:52:00

toru
Member
Registered: 2020-04-12
Posts: 15  

Re: Strange thing appearing during boot

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.

Last edited by toru (2020-04-12 08:52:33)

Offline

#6 2020-04-12 09:23:19

Head_on_a_Stick
Member
From: London
Registered: 2019-03-24
Posts: 669  
Website

Re: Strange thing appearing during boot

Try the iommu=soft kernel command line parameter.

And for outdated PCI IDs use

# update-pciids

"Il semble que la perfection soit atteinte non quand il n'y a plus rien à ajouter, mais quand il n'y a plus rien à retrancher." — Antoine de Saint-Exupéry

Offline

#7 2020-04-12 13:29:24

aus9
Member
Registered: 2020-03-24
Posts: 37  

Re: Strange thing appearing during boot

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

Offline

#8 2020-04-12 16:05:52

fsmithred
Administrator
Registered: 2016-11-25
Posts: 1,503  

Re: Strange thing appearing during boot

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.

Offline

#9 2020-04-12 23:00:50

aus9
Member
Registered: 2020-03-24
Posts: 37  

Re: Strange thing appearing during boot

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

Last edited by aus9 (2020-04-12 23:02:14)

Offline

#10 2020-04-17 10:03:57

toru
Member
Registered: 2020-04-12
Posts: 15  

Re: Strange thing appearing during boot

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.

Last edited by toru (2020-04-17 10:04:25)

Offline

#11 2020-04-17 10:10:17

fsmithred
Administrator
Registered: 2016-11-25
Posts: 1,503  

Re: Strange thing appearing during boot

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.

Offline

Board footer