Pontus Gråskæg, in order to allow additional upstream developers to examine the
issue, at your earliest convenience, could you please test the latest upstream
kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ?
Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was
released upstream.
4) Install instructions are available at:
https://wiki.ubuntu.com/Kernel/MainlineBuilds
If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.
If the latest kernel did not allow you to test to the issue (ex. you couldn't
boot into the OS) please make a comment in your report about this, and continue
to test the next most recent kernel version until you can test to the issue.
Once you've tested the upstream kernel, please comment on which kernel version
specifically you tested. If this issue is fixed in the mainline kernel, please
add the following tags by clicking on the yellow circle with a black pencil
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ
Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.
If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ
Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.
Also, you don't need to apport-collect further unless specifically
requested to do so.
It is most helpful that after testing of the latest upstream kernel is
complete, you mark this report Status Confirmed.
Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.
Thank you for your help.
** Description changed:
- Issue on a newly installed Lubuntu 16.04.3 with 'apt upgrade' freshly
- applied.
-
-- /var/log/syslog and /var/log/kern.log grow to 100s of MiB in less
than a day. --
- Typical excessive syslog entry is attached (hostname redacted). I am not
- making hardware changes at the times these entries are made. Entires are
- of the form:
-
+ Typical excessive syslog entry is attached (hostname redacted). I am not
making hardware changes at the times these entries are made. Entires are of the
form:
Sep 7 20:05:55 <hostname> kernel: [14098.011547] r592: IRQ: card added
Sep 7 20:05:55 <hostname> kernel: [14098.011548] r592: IRQ: DMA error
followed by 38 lines of trace information
-
- Note that the kernel reports itself as tainted. This is due to a previous
kernel warning issued during the boot-up, which I believe to be unrelated -
kern.log extract (hostname redacted) of warning and taint also attached.
-
- The laptop reports itself as having the problematic Ricoh devices.
- Relevant hwinfo attached. grepped extract follows
-
+ The laptop reports itself as having the problematic Ricoh devices. Relevant
hwinfo attached. grepped extract follows
Model: "Ricoh R5C832 IEEE 1394 Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh xD-Picture Card Controller"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
Model: "Ricoh R5C592 Memory Stick Bus Host Adapter"
Vendor: pci 0x1180 "Ricoh Co Ltd"
- Workaround is blacklisting devices by adding the following lines at the
- end of /etc/modprobe.d/blacklist.conf
+ WORKAROUND: Blacklist devices by adding the following lines at the end
+ of /etc/modprobe.d/blacklist.conf
# Stop errors filling up log - see
# https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187
# Blacklist Ricoh card reader
blacklist r592
blacklist r852
This stops messages from appearing in /var/log/kern.log and
/var/log/syslog. The Ricoh cardreader built into the laptop still reads
SD cards after such blacklisting.
- (lsb_release -rd output is
- Description: Ubuntu 16.04.3 LTS
- Release: 16.04
-
-
- graaskaeg
-
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
- Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
- ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
- Uname: Linux 4.10.0-33-generic x86_64
- ApportVersion: 2.20.1-0ubuntu2.10
- Architecture: amd64
- Date: Fri Sep 8 13:30:06 2017
- InstallationDate: Installed on 2017-09-05 (3 days ago)
- InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
- SourcePackage: linux-hwe
- UpgradeStatus: No upgrade log present (probably fresh install)
- ---
+ ---
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: pgrb 2220 F.... pulseaudio
/dev/snd/controlC1: pgrb 2220 F.... pulseaudio
/dev/snd/controlC0: pgrb 2220 F.... pulseaudio
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=2b7792b7-4eda-4b10-b21c-ad775ff397b3
InstallationDate: Installed on 2017-09-05 (3 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
MachineType: LENOVO 0769BMG
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic
root=/dev/mapper/herd-root ro
cryptdevice=/dev/disk/by-uuid/081dc90a-6dbc-486a-8141-6635c99caca5:mithraeum
quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.10.0-33-generic N/A
linux-backports-modules-4.10.0-33-generic N/A
linux-firmware 1.157.12
RfKill:
0: phy0: Wireless LAN
- Soft blocked: no
- Hard blocked: yes
+ Soft blocked: no
+ Hard blocked: yes
Tags: xenial
Uname: Linux 4.10.0-33-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
-
+
_MarkForUpload: True
dmi.bios.date: 08/15/2007
dmi.bios.vendor: LENOVO
dmi.bios.version: 68ET24WW
dmi.board.name: IEL10
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnLENOVO:bvr68ET24WW:bd08/15/2007:svnLENOVO:pn0769BMG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: 0769BMG
dmi.product.version: 3000 N200
dmi.sys.vendor: LENOVO
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715861
Title:
r592 & r852 IRQ: DMA errors cause excessive log file entries
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715861/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
