Re: kern/56793 (Xen DOM0 device timeouts/interrupt issues (wd, mpii))

[Frank Kardel <kardel%netbsd.org@localhost>]

The following reply was made to PR kern/56793; it has been noted by GNATS.

From: Frank Kardel <kardel%netbsd.org@localhost>
To: gnats-bugs%netbsd.org@localhost, kern-bug-people%netbsd.org@localhost,
 netbsd-bugs%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, bouyer%NetBSD.org@localhost
Cc: 
Subject: Re: kern/56793 (Xen DOM0 device timeouts/interrupt issues (wd, mpii))
Date: Wed, 25 May 2022 12:42:52 +0200

 Better:
      - boots
      - xl list works
      - mpii works with tape/disk devices
 But
      - ahd experiences two timeout during boot
      - ahd recovers later on and the tape on that device can be accessed
 
 ahd attaches like this:
 [     1.345132] pci5 at ppb4 bus 5
 [     1.345444] acpi0: MCFG: 005:00:0: Ok (cfg[0x100]=0xfb410003 extconf=Y)
 [     1.345527] acpi0: MCFG: bus 5: valid devices
 [     1.345538] acpi0: MCFG: 005:00:0
 [     1.345547] acpi0: acpimcfg_map_bus done
 [     1.345562] pci5: i/o space, memory space enabled
 [     1.346092] ppb5 at pci5 dev 0 function 0: PLX Technology PEX 8114 
 PCIe-to-PCI/PCI-X Bridge (rev. 0xbd)
 [     1.346193] ppb5: PCI Express capability version 1 <PCI-E to 
 PCI/PCI-X Bridge>
 [     1.346303] pci6 at ppb5 bus 6
 [     1.346672] acpi0: MCFG: 006:04:0: invalid config space 
 (cfg[0x100]=0xffffffff, alias=false)
 [     1.346692] acpi0: MCFG: 006:04:0: Ok (cfg[0x100]=0xffffffff extconf=N)
 [     1.346907] acpi0: MCFG: bus 6: valid devices
 [     1.346919] acpi0: MCFG: 006:00:0
 [     1.346927] acpi0: MCFG: 006:04:0
 [     1.346936] acpi0: acpimcfg_map_bus done
 [     1.346951] pci6: i/o space, memory space enabled
 [     1.347562] ahd0 at pci6 dev 4 function 0
 [     1.347759] ahd0: Enabling 39Bit Addressing
 [     1.348827] xen_pic_to_gsi ioapic pin 6 gsi 30 allocated 30
 [     1.348872] ahd0: interrupting at ioapic1 pin 6
 [     1.353220] ahd0: Manual Primary Termination
 [     1.353231] ahd0: Manual Secondary Termination
 [     1.353283] ahd0: Primary High byte termination Disabled
 [     1.353296] ahd0: Primary Low byte termination Enabled
 [     1.353309] ahd0: Secondary High byte termination Disabled
 [     1.353322] ahd0: Secondary Low byte termination Disabled
 [     1.513805] ahd0: Downloading Sequencer Program... 651 instructions 
 downloaded
 [     1.520827] ahd0: Features 0x1c001, Bugs 0x500080, Flags 0x103f1
 [     1.521015] ahd0: aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 
 101-133 MHz, 512 SCBs
 [     1.521047] scsibus0 at ahd0: 16 targets, 8 luns per target
 
 So, it looks usable/tolerable but not perfect yet
 
 Frank
 
 On 05/24/22 18:20, bouyer%NetBSD.org@localhost wrote:
 > Synopsis: Xen DOM0 device timeouts/interrupt issues (wd, mpii)
 >
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bouyer%NetBSD.org@localhost
 > State-Changed-When: Tue, 24 May 2022 16:20:40 +0000
 > State-Changed-Why:
 > Please try again with sources newer than XEN3_DOM0 1.195
 >
 >
 >