https://bugzilla.novell.com/show_bug.cgi?id=892249 https://bugzilla.novell.com/show_bug.cgi?id=892249#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |tiwai@suse.com InfoProvider| |gordon@dickens.com --- Comment #1 from Takashi Iwai 2014-08-22 16:02:20 UTC --- Since it's endless irq wakeups, here is a blind shot: could you check whether the patch below works? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=892249 https://bugzilla.novell.com/show_bug.cgi?id=892249#c3 --- Comment #3 from Gordon Dickens 2014-08-27 17:19:05 UTC --- I am not a kernel developer and so I'm not sure how to build r592.c with the patch, however, I would be happy to test it if somebody else would build it for me. Alternatively, if its simple to do, then please provide some instructions and I will attempt to build it. Also, the following is from a post at: https://forums.opensuse.org/showthread.php/494706-openSUSE-13-1-KDE-inconsis... Quoting Romanator: "The most recent openSUSE kernel (3.11.10-21-desktop) Makefile for the r592.c from Maxim Levitsky is from 2010. His final patch wasn't submitted until Jan. 8, 2011. <snip> Ask the openSUSE kernel devs to look at and backport patch #5b945a6 from this link: https://gitorious.org/ricoh-kernel/ricoh-kernel.git ". So, it doesn't look like the OpenSUSE kernel has the most recent r592 driver... Also, there is a good bit of recent activity by the r592 developer, Maxim Levitsky, on this exact same bug at Red Hat's Bugzilla site here: https://bugzilla.redhat.com/show_bug.cgi?id=1119361 The bottom line is that someone needs to make sure that OpenSUSE is using the most recent version of r592.c. FYI, Gordon -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=892249 https://bugzilla.novell.com/show_bug.cgi?id=892249#c5 --- Comment #5 from Takashi Iwai 2014-08-28 07:02:09 UTC --- (In reply to comment #3)

I am not a kernel developer and so I'm not sure how to build r592.c with the patch, however, I would be happy to test it if somebody else would build it for me. Alternatively, if its simple to do, then please provide some instructions and I will attempt to build it.

Yes, you should learn how to build a kernel and a patched module. There are a few good ways. I'll give some brief instructions later.

Also, the following is from a post at:

https://forums.opensuse.org/showthread.php/494706-openSUSE-13-1-KDE-inconsis...

Quoting Romanator: "The most recent openSUSE kernel (3.11.10-21-desktop) Makefile for the r592.c from Maxim Levitsky is from 2010. His final patch wasn't submitted until Jan. 8, 2011. <snip> Ask the openSUSE kernel devs to look at and backport patch #5b945a6 from this link: https://gitorious.org/ricoh-kernel/ricoh-kernel.git ".

So, it doesn't look like the OpenSUSE kernel has the most recent r592 driver...

You're testing 3.15 and 3.16, so the above statement doesn't fit at all.

Also, there is a good bit of recent activity by the r592 developer, Maxim Levitsky, on this exact same bug at Red Hat's Bugzilla site here:

https://bugzilla.redhat.com/show_bug.cgi?id=1119361

The bottom line is that someone needs to make sure that OpenSUSE is using the most recent version of r592.c.

No, r592 developer has to submit the fix to the upstream at first. This is the golden rule. In general, we take *only* the upstream fix (or the patch that is promised to upstream) to openSUSE kernels. If there is a problem of upstreaming, put me in Cc in chain, so that I can assist for it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=892249 --- Comment #14 from Gordon Dickens --- The massive logging started up again after about 7 hours.... Ugh... Thanks for your repo for me to try! Its installed: gordon@rhino:~> uname -a Linux rhino 3.16.7-1.g632515b-desktop #1 SMP PREEMPT Tue Nov 25 07:11:35 UTC 2014 (632515b) x86_64 x86_64 x86_64 GNU/Linux Lets see how it goes for a day or so. Thanks again for your efforts! Gordon -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=892249 --- Comment #16 from Gordon Dickens --- Well, your kernel-desktop version 3.16.7-1.g632515b-desktop did not help. Like before, after installing your new kernel, everything was fine through a few hours or operation and 3 to 4 suspends/resumes. Then, following the most recent resume from suspend, the massive logging started back up again. I have attached a 12 second snippet of the log output that I hope helps you figure this out. To review what is happening, everything is fine for a few hours of operation. Then the kernel logger goes crazy with huge massive logging. I believe that the massive logging has always begun following a resume from suspend, however, I cannot say that with 100% certainty. Then, following a reboot, everything is fine again for a little while. Please review the attached log and reply with your advice. This is an unmanageable situation. If it cannot be fixed soon then I need to revert back to an earlier kernel version and, if necessary, an earlier OS version such as OpenSUSE 13.1. As another test, I am going to blacklist r852 since it has been showing up in these logs too. Thanks again for your help. Gordon -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=892249 --- Comment #18 from Gordon Dickens --- I have recently run kernels 3.11, 3.15, 3.16. The problem did not exist with kernel 3.11 and I first saw issues in kernels 3.15 and 3.16. I did not test kernels 3.12, 3.13 or 3.14. So the problem started between kernel 3.12 and 3.15. Yes, the card reader works without the r592 module. I have now blacklisted both r592 and r852 and there are no mention of either in the kernel logs at startup or when I plug the card in. Also, the hwinfo command indicates that both modules are not active even when the card is inserted during which I am able to browse the card. I am adding another hwinfo output file with r592 and r852 blacklisted. This file was generated with the SD card inserted and working. The hwinfo output says that both R592 and r852 are not active. However, there are two other Ricoh devices: Device 32: PCI 301.0: 0c00 FireWire (IEEE 1394) (OHCI) Model: Model: "Ricoh R5C832 IEEE 1394 Controller" Driver: "firewire_ohci" Device 33: PCI 301.1: 0805 SD Host controller Model: "Ricoh R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter" Driver: "sdhci-pci" So, should I also blacklist both firewire_ohci and sdhci-pci? Thanks, Gordon PS: As an FYI, I am now running OpenSUSE 13.2. Previous to three days ago, I was runing OpenSUSE 13.1. I don't know if it matters but I thought that I should mention this. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=892249 --- Comment #20 from Takashi Iwai --- Ah, I have looked somehow at the wrong places. Yes, you can keep using the SD-card, etc, without r592 and r852 modules. r592 module is only for the legacy memory stick device, and r852 is for xD. Unless you need these rare media, you can safely blacklist them. Did you have to blacklist both modules, not only one of them? I wonder now whether disabling DMA in r592 and r852 modules make things calm down. Put the following in /etc/modprobe.d/*.conf: options r592 enable_dma=0 options r852 r852_enable_dma=0 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=892249 --- Comment #22 from Gordon Dickens --- Hi Takashi, I believe that we have achieved success! Blacklisting both the r592 and r852 modules appears to have fixed the problem. I have now been running your 3.16.7-1.g632515b-desktop kernel for 3 days with these two modules blacklisted and I have not seen any unusual or excessive logging at all. With this configuration, everything seems to be back to normal. As an FYI, I have not disabled DMA for the r592 and r852 modules; only blacklisted them. I noticed that you posted an updated kernel on November 27 which I did install. Did that update contain anything special or significant regarding this problem? Also, do you recommend that I stay on your kernel/repo or should I revert back to the stock kernel at some point? Please advise. Thank you very much for your help and assistance. Gordon -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=892249 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |jslaby@suse.com Resolution|--- |FIXED --- Comment #23 from Jiri Slaby --- I hope this is fixed in later kernels, so we can close it now. If not, please reopen. -- You are receiving this mail because: You are on the CC list for the bug.