r592 & r852 IRQ: DMA errors cause excessive log file entries

Bug #1715861 reported by Pontus Gråskæg
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

 -- /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:
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

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: 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.

---
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
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

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Pontus Gråskæg, thank you for taking the time to report this bug and helping to make Ubuntu better.

Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1715861

affects: linux-hwe (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
tags: added: regression-potential
removed: dma error irq r592
Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : CRDA.txt

apport information

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : IwConfig.txt

apport information

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : JournalErrors.txt

apport information

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : Lspci.txt

apport information

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : Lsusb.txt

apport information

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : ProcEnviron.txt

apport information

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : ProcModules.txt

apport information

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : UdevDb.txt

apport information

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote : WifiSyslog.txt

apport information

Revision history for this message
penalvch (penalvch) wrote :

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: updated
Revision history for this message
Pontus Gråskæg (graaskaeg) wrote :

Currently having problems consistently reproducing the error using kernel 4.13.0-041300-generic, despite trying.

Laptop generally runs without generating the error - I thought it might be related to recovery after hibernating, but that does not trigger the behaviour reliably. I have had one instance of the log filling, but without a reliable means of generating the problem, a bug report isn't very helpful.

However, using this kernel gives me a separate issue - hibernate works, but suspend does not. This is entirely reproducible, so I might have to file a bug for that. Suspend worked reliably in the previous kernel I was using.

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote :

OK, trying newest kernel: 4.14.0-041400rc1-generic

So far, no recurrence of kern.log and syslog filling up, and suspend seems to work again.

Revision history for this message
Pontus Gråskæg (graaskaeg) wrote :
Download full text (5.6 KiB)

Issue has recurred on 4.14.0-041400rc1-generic.

I have not worked out how to generate the problem reliably. Between 0700 this morning and 2000, syslog is 2.8G and kern.log is also 2.8G

Log events are:

Sep 18 21:31:15 muddlehead kernel: [70317.777977] ------------[ cut here ]------------
Sep 18 21:31:15 muddlehead kernel: [70317.777982] WARNING: CPU: 1 PID: 0 at /home/kernel/COD/linux/drivers/mtd/nand/r852.c:746 r852_irq+0x180/0x1d0 [r852]
Sep 18 21:31:15 muddlehead kernel: [70317.777983] Modules linked in: mmc_block nls_iso8859_1 binfmt_misc coretemp joydev input_leds wmi_bmof serio_raw snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic arc4 snd_hda_intel snd_hda_codec snd_hda_core snd_seq_midi snd_seq_midi_event iwl3945 snd_usb_audio snd_usbmidi_lib snd_hwdep snd_rawmidi iwlegacy r852 sm_common snd_pcm nand nand_ecc snd_seq nand_bch uvcvideo usblp bch mac80211 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core mtd snd_seq_device r592 memstick videodev cfg80211 snd_timer media lpc_ich snd mac_hid soundcore shpchp parport_pc ppdev lp parport autofs4 crypto_simd glue_helper cryptd aes_x86_64 algif_skcipher af_alg dm_crypt nilfs2 uas usb_storage hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops
Sep 18 21:31:15 muddlehead kernel: [70317.778043] tg3 ahci libahci pata_acpi drm psmouse ptp sdhci_pci firewire_ohci sdhci firewire_core crc_itu_t pps_core wmi video
Sep 18 21:31:15 muddlehead kernel: [70317.778057] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G W 4.14.0-041400rc1-generic #201709162031
Sep 18 21:31:15 muddlehead kernel: [70317.778059] Hardware name: LENOVO 0769BMG/IEL10, BIOS 68ET24WW 08/15/2007
Sep 18 21:31:15 muddlehead kernel: [70317.778060] task: ffff9cb17a4015c0 task.stack: ffffb2ab40694000
Sep 18 21:31:15 muddlehead kernel: [70317.778064] RIP: 0010:r852_irq+0x180/0x1d0 [r852]
Sep 18 21:31:15 muddlehead kernel: [70317.778065] RSP: 0018:ffff9cb17fd03eb8 EFLAGS: 00010002
Sep 18 21:31:15 muddlehead kernel: [70317.778068] RAX: ffffb2ab406d1000 RBX: ffff9cb175902b00 RCX: 0000000000000086
Sep 18 21:31:15 muddlehead kernel: [70317.778070] RDX: 0000000000000001 RSI: ffff9cb175902b00 RDI: 0000000000000001
Sep 18 21:31:15 muddlehead kernel: [70317.778072] RBP: ffff9cb17fd03ed8 R08: 0000000000000000 R09: 000000000000c020
Sep 18 21:31:15 muddlehead kernel: [70317.778073] R10: ffff9cb17fd03f28 R11: 0000000000000484 R12: 0000000000000001
Sep 18 21:31:15 muddlehead kernel: [70317.778075] R13: ffff9cb175902be4 R14: 0000000000000082 R15: ffff9cb170f86580
Sep 18 21:31:15 muddlehead kernel: [70317.778077] FS: 0000000000000000(0000) GS:ffff9cb17fd00000(0000) knlGS:0000000000000000
Sep 18 21:31:15 muddlehead kernel: [70317.778079] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 18 21:31:15 muddlehead kernel: [70317.778081] CR2: 00007fe1eca5d019 CR3: 0000000137339000 CR4: 00000000000006e0
Sep 18 21:31:15 muddlehead kernel: [70317.778083] Call Trace:
Sep 18 21:31:15 muddlehead kernel: [70317.778084] <IRQ>
Sep 18 21:31:15 muddlehead kernel: [70317.778088] __handle_irq_event_percpu+0x3f/0x190
Sep 18 21:31:15 muddlehead kernel: [70317.778091] handle_irq_event_pe...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

Pontus Gråskæg, to rule out a regression, could you please test http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/ and advise to the results? If you have tested a kernel version earlier to this, please advise to the results of this also.

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.14-rc1
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Ryan C. Underwood (nemesis-icequake) wrote :

Still happens in kernel 5.8.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.