Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
pcieport: Multiple Corrected error received and can't find device
619 views
Skip to first unread message
Damian Montaldo
Aug 27, 2012, 12:50:02 PM8/27/12
to
Hi, I'm experiencing a lot of strange errors in the logs about a pci
port device.
Aug 27 13:36:42 n2 kernel: [ 2350.344677] pcieport 0000:00:03.0: AER:
Multiple Corrected error received: id=0018
Aug 27 13:36:42 n2 kernel: [ 2350.344683] pcieport 0000:00:03.0: can't
find device of ID0018
Aug 27 13:36:42 n2 kernel: [ 2350.344684] pcieport 0000:00:03.0: AER:
Multiple Corrected error received: id=0018
Aug 27 13:36:42 n2 kernel: [ 2350.344689] pcieport 0000:00:03.0: can't
find device of ID0018
Aug 27 13:36:42 n2 kernel: [ 2350.344696] pcieport 0000:00:03.0: AER:
Multiple Corrected error received: id=0018
Aug 27 13:36:42 n2 kernel: [ 2350.344702] pcieport 0000:00:03.0: PCIe
Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver
ID)
Aug 27 13:36:42 n2 kernel: [ 2350.344707] pcieport 0000:00:03.0:
device [8086:340a] error status/mask=00000001/00002000
Aug 27 13:36:42 n2 kernel: [ 2350.344708] pcieport 0000:00:03.0: [
0] Receiver Error
Aug 27 13:36:42 n2 kernel: [ 2350.344712] pcieport 0000:00:03.0: AER:
Multiple Corrected error received: id=0018
Aug 27 13:36:42 n2 kernel: [ 2350.344722] pcieport 0000:00:03.0: PCIe
Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver
ID)
Aug 27 13:36:42 n2 kernel: [ 2350.344724] pcieport 0000:00:03.0:
device [8086:340a] error status/mask=00000001/00002000
Aug 27 13:36:42 n2 kernel: [ 2350.344725] pcieport 0000:00:03.0: [
0] Receiver Error
Aug 27 13:36:42 n2 kernel: [ 2350.344729] pcieport 0000:00:03.0: AER:
Corrected error received: id=0018
Aug 27 13:36:42 n2 kernel: [ 2350.344734] pcieport 0000:00:03.0: can't
find device of ID0018
Aug 27 13:43:20 n2 kernel: [ 2746.757385] pcieport 0000:00:03.0: AER:
Multiple Corrected error received: id=0018
Aug 27 13:43:20 n2 kernel: [ 2746.757395] pcieport 0000:00:03.0: PCIe
Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver
ID)
Aug 27 13:43:20 n2 kernel: [ 2746.757397] pcieport 0000:00:03.0:
device [8086:340a] error status/mask=00000001/00002000
Aug 27 13:43:20 n2 kernel: [ 2746.757399] pcieport 0000:00:03.0: [
0] Receiver Error
I'm using the kernel 3.2.0-3-amd64 of debian wheezy (less than 1 month
up-to-date).
I have 4 pc like that and some of them have this errors in the logs
but one of these have a *lot* of them.
How could I know if it's a hardware error (related to a board in the
pci bus?) or may be for example a bug in the nouveau nvidia drivers?
I was looking for a related bug but I'm not using a X server at all so
I need some help here.
Here is the list of pci devices
root@n2:~# lspci
00:00.0 Host bridge: Intel Corporation 5520/5500/X58 I/O Hub to ESI
Port (rev 13)
00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI
Express Root Port 1 (rev 13)
00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI
Express Root Port 3 (rev 13)
00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI
Express Root Port 7 (rev 13)
00:10.0 PIC: Intel Corporation 5520/5500/X58 Physical and Link Layer
Registers Port 0 (rev 13)
00:10.1 PIC: Intel Corporation 5520/5500/X58 Routing and Protocol
Layer Registers Port 0 (rev 13)
00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management
Registers (rev 13)
00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch
Pad Registers (rev 13)
00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status
and RAS Registers (rev 13)
00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 13)
00:19.0 Ethernet controller: Intel Corporation 82567LM-2 Gigabit
Network Connection
00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #4
00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #5
00:1a.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #6
00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2
EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD
Audio Controller
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI
Express Root Port 1
00:1c.1 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 2
00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI
Express Root Port 5
00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #1
00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #2
00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #3
00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2
EHCI Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port
SATA IDE Controller #1
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2 port
SATA IDE Controller #2
02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce
210] (rev a2)
02:00.1 Audio device: NVIDIA Corporation High Definition Audio
Controller (rev a1)
03:00.0 3D controller: NVIDIA Corporation GT200 [Tesla C1060] (rev a1)
07:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A
IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx]
3f:00.0 Host bridge: Intel Corporation Xeon 5500/Core i7 QuickPath
Architecture Generic Non-Core Registers (rev 05)
3f:00.1 Host bridge: Intel Corporation Xeon 5500/Core i7 QuickPath
Architecture System Address Decoder (rev 05)
3f:02.0 Host bridge: Intel Corporation Xeon 5500/Core i7 QPI Link 0 (rev 05)
3f:02.1 Host bridge: Intel Corporation Xeon 5500/Core i7 QPI Physical 0 (rev 05)
3f:03.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller (rev 05)
3f:03.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Target Address Decoder (rev 05)
3f:03.4 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Test Registers (rev 05)
3f:04.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 0 Control Registers (rev 05)
3f:04.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 0 Address Registers (rev 05)
3f:04.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 0 Rank Registers (rev 05)
3f:04.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 0 Thermal Control Registers (rev 05)
3f:05.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 1 Control Registers (rev 05)
3f:05.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 1 Address Registers (rev 05)
3f:05.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 1 Rank Registers (rev 05)
3f:05.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 1 Thermal Control Registers (rev 05)
3f:06.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 2 Control Registers (rev 05)
3f:06.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 2 Address Registers (rev 05)
3f:06.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 2 Rank Registers (rev 05)
3f:06.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 2 Thermal Control Registers (rev 05)
root@n2:~#
Does anybody need more info?
Thanks!
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/CAFb4Da+_MnHdVZJ4kkBjJtvS...@mail.gmail.com
port device.
Aug 27 13:36:42 n2 kernel: [ 2350.344677] pcieport 0000:00:03.0: AER:
Multiple Corrected error received: id=0018
Aug 27 13:36:42 n2 kernel: [ 2350.344683] pcieport 0000:00:03.0: can't
find device of ID0018
Aug 27 13:36:42 n2 kernel: [ 2350.344684] pcieport 0000:00:03.0: AER:
Multiple Corrected error received: id=0018
Aug 27 13:36:42 n2 kernel: [ 2350.344689] pcieport 0000:00:03.0: can't
find device of ID0018
Aug 27 13:36:42 n2 kernel: [ 2350.344696] pcieport 0000:00:03.0: AER:
Multiple Corrected error received: id=0018
Aug 27 13:36:42 n2 kernel: [ 2350.344702] pcieport 0000:00:03.0: PCIe
Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver
ID)
Aug 27 13:36:42 n2 kernel: [ 2350.344707] pcieport 0000:00:03.0:
device [8086:340a] error status/mask=00000001/00002000
Aug 27 13:36:42 n2 kernel: [ 2350.344708] pcieport 0000:00:03.0: [
0] Receiver Error
Aug 27 13:36:42 n2 kernel: [ 2350.344712] pcieport 0000:00:03.0: AER:
Multiple Corrected error received: id=0018
Aug 27 13:36:42 n2 kernel: [ 2350.344722] pcieport 0000:00:03.0: PCIe
Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver
ID)
Aug 27 13:36:42 n2 kernel: [ 2350.344724] pcieport 0000:00:03.0:
device [8086:340a] error status/mask=00000001/00002000
Aug 27 13:36:42 n2 kernel: [ 2350.344725] pcieport 0000:00:03.0: [
0] Receiver Error
Aug 27 13:36:42 n2 kernel: [ 2350.344729] pcieport 0000:00:03.0: AER:
Corrected error received: id=0018
Aug 27 13:36:42 n2 kernel: [ 2350.344734] pcieport 0000:00:03.0: can't
find device of ID0018
Aug 27 13:43:20 n2 kernel: [ 2746.757385] pcieport 0000:00:03.0: AER:
Multiple Corrected error received: id=0018
Aug 27 13:43:20 n2 kernel: [ 2746.757395] pcieport 0000:00:03.0: PCIe
Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver
ID)
Aug 27 13:43:20 n2 kernel: [ 2746.757397] pcieport 0000:00:03.0:
device [8086:340a] error status/mask=00000001/00002000
Aug 27 13:43:20 n2 kernel: [ 2746.757399] pcieport 0000:00:03.0: [
0] Receiver Error
I'm using the kernel 3.2.0-3-amd64 of debian wheezy (less than 1 month
up-to-date).
I have 4 pc like that and some of them have this errors in the logs
but one of these have a *lot* of them.
How could I know if it's a hardware error (related to a board in the
pci bus?) or may be for example a bug in the nouveau nvidia drivers?
I was looking for a related bug but I'm not using a X server at all so
I need some help here.
Here is the list of pci devices
root@n2:~# lspci
00:00.0 Host bridge: Intel Corporation 5520/5500/X58 I/O Hub to ESI
Port (rev 13)
00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI
Express Root Port 1 (rev 13)
00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI
Express Root Port 3 (rev 13)
00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI
Express Root Port 7 (rev 13)
00:10.0 PIC: Intel Corporation 5520/5500/X58 Physical and Link Layer
Registers Port 0 (rev 13)
00:10.1 PIC: Intel Corporation 5520/5500/X58 Routing and Protocol
Layer Registers Port 0 (rev 13)
00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management
Registers (rev 13)
00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch
Pad Registers (rev 13)
00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status
and RAS Registers (rev 13)
00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 13)
00:19.0 Ethernet controller: Intel Corporation 82567LM-2 Gigabit
Network Connection
00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #4
00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #5
00:1a.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #6
00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2
EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD
Audio Controller
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI
Express Root Port 1
00:1c.1 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 2
00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI
Express Root Port 5
00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #1
00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #2
00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #3
00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2
EHCI Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port
SATA IDE Controller #1
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2 port
SATA IDE Controller #2
02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce
210] (rev a2)
02:00.1 Audio device: NVIDIA Corporation High Definition Audio
Controller (rev a1)
03:00.0 3D controller: NVIDIA Corporation GT200 [Tesla C1060] (rev a1)
07:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A
IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx]
3f:00.0 Host bridge: Intel Corporation Xeon 5500/Core i7 QuickPath
Architecture Generic Non-Core Registers (rev 05)
3f:00.1 Host bridge: Intel Corporation Xeon 5500/Core i7 QuickPath
Architecture System Address Decoder (rev 05)
3f:02.0 Host bridge: Intel Corporation Xeon 5500/Core i7 QPI Link 0 (rev 05)
3f:02.1 Host bridge: Intel Corporation Xeon 5500/Core i7 QPI Physical 0 (rev 05)
3f:03.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller (rev 05)
3f:03.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Target Address Decoder (rev 05)
3f:03.4 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Test Registers (rev 05)
3f:04.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 0 Control Registers (rev 05)
3f:04.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 0 Address Registers (rev 05)
3f:04.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 0 Rank Registers (rev 05)
3f:04.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 0 Thermal Control Registers (rev 05)
3f:05.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 1 Control Registers (rev 05)
3f:05.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 1 Address Registers (rev 05)
3f:05.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 1 Rank Registers (rev 05)
3f:05.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 1 Thermal Control Registers (rev 05)
3f:06.0 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 2 Control Registers (rev 05)
3f:06.1 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 2 Address Registers (rev 05)
3f:06.2 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 2 Rank Registers (rev 05)
3f:06.3 Host bridge: Intel Corporation Xeon 5500/Core i7 Integrated
Memory Controller Channel 2 Thermal Control Registers (rev 05)
root@n2:~#
Does anybody need more info?
Thanks!
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/CAFb4Da+_MnHdVZJ4kkBjJtvS...@mail.gmail.com
Camaleón
Aug 27, 2012, 2:00:03 PM8/27/12
to
On Mon, 27 Aug 2012 13:47:39 -0300, Damian Montaldo wrote:
> Hi, I'm experiencing a lot of strange errors in the logs about a pci
> port device.
>
> Aug 27 13:36:42 n2 kernel: [ 2350.344677] pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
> Aug 27 13:36:42 n2 kernel: [ 2350.344683] pcieport 0000:00:03.0: can't find device of ID0018
> Aug 27 13:36:42 n2 kernel: [ 2350.344684] pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
> Aug 27 13:36:42 n2 kernel: [ 2350.344689] pcieport 0000:00:03.0: can't find device of ID0018
> Aug 27 13:36:42 n2 kernel: [ 2350.344696] pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
> Aug 27 13:36:42 n2 kernel: [ 2350.344702] pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver ID)
> Aug 27 13:36:42 n2 kernel: [ 2350.344707] pcieport 0000:00:03.0: device [8086:340a] error status/mask=00000001/00002000
> Aug 27 13:36:42 n2 kernel: [ 2350.344708] pcieport 0000:00:03.0: [ 0] Receiver Error
(...)
> Hi, I'm experiencing a lot of strange errors in the logs about a pci
> port device.
>
> Aug 27 13:36:42 n2 kernel: [ 2350.344677] pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
> Aug 27 13:36:42 n2 kernel: [ 2350.344683] pcieport 0000:00:03.0: can't find device of ID0018
> Aug 27 13:36:42 n2 kernel: [ 2350.344684] pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
> Aug 27 13:36:42 n2 kernel: [ 2350.344689] pcieport 0000:00:03.0: can't find device of ID0018
> Aug 27 13:36:42 n2 kernel: [ 2350.344696] pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
> Aug 27 13:36:42 n2 kernel: [ 2350.344702] pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver ID)
> Aug 27 13:36:42 n2 kernel: [ 2350.344707] pcieport 0000:00:03.0: device [8086:340a] error status/mask=00000001/00002000
> Aug 27 13:36:42 n2 kernel: [ 2350.344708] pcieport 0000:00:03.0: [ 0] Receiver Error
> I'm using the kernel 3.2.0-3-amd64 of debian wheezy (less than 1 month
> up-to-date).
>
> I have 4 pc like that and some of them have this errors in the logs but
> one of these have a *lot* of them. How could I know if it's a hardware
> error (related to a board in the pci bus?) or may be for example a bug
> in the nouveau nvidia drivers?
There's more information about those message in this bug report for Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/671979
Specifically comments #8 and #9.
It looks related to the nvidia card but the solution/bypass is not clear,
maybe worth reporting at Debian BTS (kernel component).
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Damian Montaldo
Aug 27, 2012, 2:20:02 PM8/27/12
to
On Mon, Aug 27, 2012 at 2:50 PM, Camaleón <noel...@gmail.com> wrote:
> On Mon, 27 Aug 2012 13:47:39 -0300, Damian Montaldo wrote:
>
>> Hi, I'm experiencing a lot of strange errors in the logs about a pci
>> port device.
>
> On Mon, 27 Aug 2012 13:47:39 -0300, Damian Montaldo wrote:
>
>> Hi, I'm experiencing a lot of strange errors in the logs about a pci
>> port device.
>
> (...)
>
> There's more information about those message in this bug report for Ubuntu:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/671979
>
> Specifically comments #8 and #9.
Thanks Camaleón, I read that bug before ask here but the #9 solution
>
> There's more information about those message in this bug report for Ubuntu:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/671979
>
> Specifically comments #8 and #9.
in the opensuse forum talks about X server and kde and, like I said
before, I'm not using a X server.
The ubuntu nvidia-current-updates packages doesn't exists in debian.
The similar package in debian is nvidia-support?
Anyway that is the non-free driver binaries and I'm currently using nouveau.
> It looks related to the nvidia card but the solution/bypass is not clear,
> maybe worth reporting at Debian BTS (kernel component).
Thanks again.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Camaleón
Aug 28, 2012, 9:40:02 AM8/28/12
to
On Mon, 27 Aug 2012 15:10:09 -0300, Damian Montaldo wrote:
> On Mon, Aug 27, 2012 at 2:50 PM, Camaleón <noel...@gmail.com> wrote:
>> On Mon, 27 Aug 2012 13:47:39 -0300, Damian Montaldo wrote:
>>
>>> Hi, I'm experiencing a lot of strange errors in the logs about a pci
>>> port device.
>>
>> (...)
>>
>> There's more information about those message in this bug report for
>> Ubuntu:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/671979
>>
>> Specifically comments #8 and #9.
>
> Thanks Camaleón, I read that bug before ask here but the #9 solution in
> the opensuse forum talks about X server and kde and, like I said before,
> I'm not using a X server.
Not exactly.
> On Mon, Aug 27, 2012 at 2:50 PM, Camaleón <noel...@gmail.com> wrote:
>> On Mon, 27 Aug 2012 13:47:39 -0300, Damian Montaldo wrote:
>>
>>> Hi, I'm experiencing a lot of strange errors in the logs about a pci
>>> port device.
>>
>> (...)
>>
>> There's more information about those message in this bug report for
>> Ubuntu:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/671979
>>
>> Specifically comments #8 and #9.
>
> Thanks Camaleón, I read that bug before ask here but the #9 solution in
> the opensuse forum talks about X server and kde and, like I said before,
> I'm not using a X server.
The openSUSE forum post is about moving the VGA card into a different
PCIe slot but this was of no help for the Ubuntu user. I guess the
success of the suggested bypass depends on the motherboard (on some
models you can find slots which share MB resources which could be
triggering this warning).
> The ubuntu nvidia-current-updates packages doesn't exists in debian. The
> similar package in debian is nvidia-support? Anyway that is the non-free
> driver binaries and I'm currently using nouveau.
not find it) that's why I suggested that you open a report in Debian :-)
>> It looks related to the nvidia card but the solution/bypass is not
>> clear, maybe worth reporting at Debian BTS (kernel component).
> OK so I'm going to try to report it as a bug.
another users affected by this. Most sure they already know about this
and can give you some hints to overcome it.
> Thanks again.
You're welcome.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
0 new messages