--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: MSI errors after linux-image-2.6.26-2-xen-amd64 update
- From: Bartek <bart@sitenet.pl>
- Date: Thu, 26 Aug 2010 09:27:36 +0200
- Message-id: <20100826072736.10521.8380.reportbug@gserwer2.gserwer2>
Package: linux-image-2.6.26-2-xen-amd64
Version: 2.6.26-24lenny1
Severity: important
Hello!
I am running Xen with pciback. This is my kernel command line
root=/dev/mapper/vg1-root ro console=tty0 pciback.permissive noirqdebug pciback.hide=(00:0a.0)(01:06.0)
After last kernel package upgrade, the following errors appeared.
Aug 25 19:30:39 debian kernel: [ 0.655321] PCI: Setting latency timer of device 0000:00:10.0 to 64
Aug 25 19:30:39 debian kernel: [ 0.655582] assign_interrupt_mode Found MSI capability
Aug 25 19:30:39 debian kernel: [ 0.655772] no ownder
Aug 25 19:30:39 debian kernel: [ 0.655849] map irq failed
Aug 25 19:30:39 debian kernel: [ 0.655928] Allocate Port Service[0000:00:10.0:pcie00]
Aug 25 19:30:39 debian kernel: [ 0.659308] PCI: Setting latency timer of device 0000:00:12.0 to 64
Aug 25 19:30:39 debian kernel: [ 0.659308] assign_interrupt_mode Found MSI capability
Aug 25 19:30:39 debian kernel: [ 0.659308] no ownder
Aug 25 19:30:39 debian kernel: [ 0.659308] map irq failed
The system is unstable, resets especially when I load uvesafb. When uvesafb is loaded and I run DRBD the screen goes black. The same with pciback.hide enabled and without pciback at all.
After starting Xen DomU with binded devices following errors appeared
Aug 25 20:17:54 debian kernel: [ 87.927850] error enable msi for guest 1 status ffffffea
Add pci=nomsi to kernel command line solves problem with msi errors, but still there is MSI error when booting DomU and I can not use uvesafb (system unstable, black screen after loading DRBD)
Kernel without Xen support seems to work properly with uvesafb and DRBD.
# lspci
00:00.0 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a2)
00:01.0 ISA bridge: nVidia Corporation MCP78S [GeForce 8200] LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP78S [GeForce 8200] SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a1)
00:01.3 Co-processor: nVidia Corporation MCP78S [GeForce 8200] Co-Processor (rev a2)
00:01.4 RAM memory: nVidia Corporation MCP78S [GeForce 8200] Memory Controller (rev a1)
00:06.0 IDE interface: nVidia Corporation MCP78S [GeForce 8200] IDE (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1)
00:09.0 SATA controller: nVidia Corporation MCP78S [GeForce 8200] AHCI Controller (rev a2)
00:0a.0 Ethernet controller: nVidia Corporation MCP78S [GeForce 8200] Ethernet (rev a2)
00:0b.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:12.0 PCI bridge: nVidia Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Link Control
01:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:00.0 VGA compatible controller: nVidia Corporation GeForce 8200 (rev a2)
Greetings
Bartek
-- System Information:
Debian Release: 5.0.5
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.26-2-xen-amd64 depends on:
ii initramfs-tools 0.92o tools for generating an initramfs
ii linux-modules-2.6.26-2-x 2.6.26-24lenny1 Linux 2.6.26 modules on AMD64
linux-image-2.6.26-2-xen-amd64 recommends no packages.
Versions of packages linux-image-2.6.26-2-xen-amd64 suggests:
ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn linux-doc-2.6.26 <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: 594462-done@bugs.debian.org
- Cc: Bartek <bart@sitenet.pl>
- Subject: Re: MSI errors after linux-image-2.6.26-2-xen-amd64 update
- From: Moritz Muehlenhoff <jmm@inutil.org>
- Date: Thu, 18 Jul 2013 18:49:45 +0200
- Message-id: <20130718164945.GA24907@inutil.org>
- In-reply-to: <20120208022706.GA7014@burratino>
- References: <20100826072736.10521.8380.reportbug@gserwer2.gserwer2> <20120208022706.GA7014@burratino>
On Tue, Feb 07, 2012 at 08:27:06PM -0600, Jonathan Nieder wrote:
> Hi Bartek,
>
> Bartek wrote:
>
> > I am running Xen with pciback. This is my kernel command line
> >
> > root=/dev/mapper/vg1-root ro console=tty0 pciback.permissive noirqdebug pciback.hide=(00:0a.0)(01:06.0)
> >
> > After last kernel package upgrade, the following errors appeared.
> >
> > Aug 25 19:30:39 debian kernel: [ 0.655321] PCI: Setting latency timer of device 0000:00:10.0 to 64
> > Aug 25 19:30:39 debian kernel: [ 0.655582] assign_interrupt_mode Found MSI capability
> > Aug 25 19:30:39 debian kernel: [ 0.655772] no ownder
> > Aug 25 19:30:39 debian kernel: [ 0.655849] map irq failed
> > Aug 25 19:30:39 debian kernel: [ 0.655928] Allocate Port Service[0000:00:10.0:pcie00]
> > Aug 25 19:30:39 debian kernel: [ 0.659308] PCI: Setting latency timer of device 0000:00:12.0 to 64
> > Aug 25 19:30:39 debian kernel: [ 0.659308] assign_interrupt_mode Found MSI capability
> > Aug 25 19:30:39 debian kernel: [ 0.659308] no ownder
> > Aug 25 19:30:39 debian kernel: [ 0.659308] map irq failed
> >
> > The system is unstable, resets especially when I load uvesafb. When
> > uvesafb is loaded and I run DRBD the screen goes black. The same
> > with pciback.hide enabled and without pciback at all.
>
> Thanks for a clear report, and sorry for the very long silence. Some
> basic questions, since it's been a long time: did you end up solving
> this? Do you still have access to the affected system? What kernel
> do you use these days?
No further feedback, closing.
Cheers,
Moritz
--- End Message ---