A Corrected Error Received Is =0038

Assigned to Milestone linux (Ubuntu) Edit Expired Medium Unassigned Edit You need to log in pcie bus error severity=corrected type=data link layer to change this bug's status. Affecting: linux (Ubuntu) Filed here pcie bus error severity=corrected type=physical layer by: Dan Kegel When: 2014-04-09 Completed: 2014-06-19 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu

Pcie Bus Error Severity Corrected Type Physical Layer Id

Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Expired Medium Assigned

Pcie Bus Error Severity=corrected Type=physical Layer Ubuntu

to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description I installed Trusty beta 2, and since then have had maximum uptime of about 12 hours. System hangs frequently, sometimes with mouse still aer: multiple corrected error received: id=0018 active, sometimes not. The clock in the upper right of the screen shows the time of the hang. I have not yet established whether the machine can be pinged when it is in this state. Nothing obvious in the logs except an increasingly frequent PCIe bus error similar to the one in bug 1279699, e.g. Apr 7 17:13:52 dank kernel: [ 810.166278] pcieport 0000:00:07.0: AER: Multiple Corrected error received: id=0038 Apr 7 17:13:52 dank kernel: [ 810.166292] pcieport 0000:00:07.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0038(Receiver ID) Apr 7 17:13:52 dank kernel: [ 810.166297] pcieport 0000:00:07.0: device [8086:340e] error status/mask=00000081/00002000 Apr 7 17:13:52 dank kernel: [ 810.166300] pcieport 0000:00:07.0: [ 0] Receiver Error Apr 7 17:13:52 dank kernel: [ 810.166303] pcieport 0000:00:07.0: [ 7] Bad DLLP Apr 7 17:15:55 dank kernel: [ 933.083876] pcieport 0000:00:07.0: AER: Multiple Corrected error received: id=0038 Apr 7 17:15:55 dank kernel: [ 933.083890] pcieport 0000:00:07.0: PCI

-Clone This Bug -Last Comment First Last Prev

Aer Multiple Corrected Error Received Id 0000

Next This bug is not in your last search pci=nommconf results. Bug681017 - 82576 stuck after PCI AER error Summary: 82576 stuck after PCI AER error pci=noaer Status: CLOSED ERRATA Aliases: None Product: Red Hat Enterprise Linux 6 Classification: Red Hat Component: kernel (Show other bugs) Sub Component: --- kabi-whitelists Storage Multiple https://bugs.launchpad.net/bugs/1305172 Devices (MD) Device Mapper Core Crypt Multipath RAID Snapshots Thin Provisioning Other Storage Drivers Other File Systems GFS/GFS2 XFS ext* Btrfs NFS CIFS AutoFS Other Networking Protocol sctp igmp/mld tcp udp arp/icmp IPv6 NIC Drivers Vlan Bonding Team Bridge OVS Tunnel IPSec/Crypto Netfilter PTP Misc Memory Management Scheduler Process management Power Management https://bugzilla.redhat.com/show_bug.cgi?id=681017 Desktop Graphics Audio V4L fbdev USB Other Virtualization Xen ESX Hyper-V KVM Other Debugging/Tracing Kexec/kdump Utrace/Uprobe/Ptrace Ftrace Perf EDAC/HERM Oprofile Systemtap Locking/lockdep Other Platform Enablement RFEs Wireless Infiniband Resource Management Control Groups Namespace Crypto Security SELinux Audit TPM Key Management Other Other Version: 6.2 Hardware: x86_64 Linux Priority urgent Severity urgent TargetMilestone: rc TargetRelease: --- Assigned To: Alex Williamson QA Contact: Red Hat Kernel QE team Docs Contact: URL: Whiteboard: Keywords: ZStream Duplicates: 619806 647077 689015 (view as bug list) Depends On: Blocks: 689015 694073 Show dependency tree /graph Reported: 2011-02-28 14:50 EST by Alex Williamson Modified: 2013-01-10 03:17 EST (History) CC List: 13 users (show) agospoda ddugger ddutile dhoward dts jburke jfeeney jwest kzhang mishu prarit sassmann syeghiay See Also: Fixed In Version: kernel-2.6.32-128.el6 Doc Type: Bug Fix Doc Text: Under some circumstances, faulty logic in the system BIOS could report that ASPM (Active State Power Management) was no

communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about http://askubuntu.com/questions/663828/syslog-and-kern-log-multiple-gb-in-size-filled-with-pcieport-error-messages Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top syslog and pcie bus kern.log multiple GB in size filled with pcieport error messages up vote 1 down vote favorite After getting a disk usage warning, I noticed my syslog and kern.log were multiple GBs in size (20GB each). I then used this askubuntu post to clear the log files but today I find that they have again grown to around 2GB in size. This is a normal computer which is shutdown at the end of pcie bus error the day so these files have literally grown that much in a day or two. The last 10,000 lines of both log files can be downloaded; syslog and kern.log. I then examined the contents of my log files and noticed a repeating message Aug 20 10:47:41 macallan3 kernel: [ 382.119288] pcieport 0000:00:07.0: can't find device of ID0038 Aug 20 10:47:41 macallan3 kernel: [ 382.119290] pcieport 0000:00:07.0: AER: Corrected error received: id=0038 Aug 20 10:47:41 macallan3 kernel: [ 382.119297] pcieport 0000:00:07.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0038(Receiver ID) Aug 20 10:47:41 macallan3 kernel: [ 382.119298] pcieport 0000:00:07.0: device [8086:340e] error status/mask=00000001/00002000 Aug 20 10:47:41 macallan3 kernel: [ 382.119299] pcieport 0000:00:07.0: [ 0] Receiver Error (First) Aug 20 10:47:41 macallan3 kernel: [ 382.119303] pcieport 0000:00:07.0: AER: Corrected error received: id=0038 Aug 20 10:47:41 macallan3 kernel: [ 382.119307] pcieport 0000:00:07.0: can't find device of ID0038 Aug 20 10:47:41 macallan3 kernel: [ 382.119313] pcieport 0000:00:07.0: AER: Corrected error received: id=0038 Aug 20 10:47:41 macallan3 kernel: [ 382.119322] pcieport 0000:00:07.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0038(Receiver ID) Aug 20 10:47:41 macallan3 kernel: [ 382.119324] pcieport 0000:00:07.0: device [8086:340e] error status/mask=00000001/00002000 Aug 20 10:47:41 macallan3 kernel: [ 382.119329] pcieport 0000:00:07.0: [ 0] Receiver Error (First) Aug 20 10:47:41 macallan3 kernel: [ 382.119333] pcieport 0000:00:07.0: AER: Corrected error rec