FS#31658 - [linux] 3.4 - 3.6 rtl8712: tcp_recvmsg causes disk flood
Attached to Project:
Arch Linux
Opened by Ben Ruijl (revelation60) - Sunday, 23 September 2012, 13:18 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 23 January 2013, 15:04 GMT
Opened by Ben Ruijl (revelation60) - Sunday, 23 September 2012, 13:18 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 23 January 2013, 15:04 GMT
|
Details
Description:
When I am browsing (using Chrome), at a seemingly random time I notice my system slowing down. When I check the logs, I see the attached message getting posted over and over again. This causes a disk flood within 20 seconds, writing 15 gbs of this same error message. As you can see, when this error occurs, the system becomes unusable almost instantly. Removing the wireless network USB stick (RTL8191S) makes no difference when the flooding has started. Shutting down all network applications does not help either. I have had this problem for quite a while, but as of recently it happens every time and within 10 minutes from boot. Below I've linked to a thread that shows that I am not the only one. Additional info: * See attached kernel trace log * This thread: https://bbs.archlinux.org/viewtopic.php?pid=1165334#p1165334 Steps to reproduce: Use the internet. |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 23 January 2013, 15:04 GMT
Reason for closing: Fixed
Additional comments about closing: 3.7.x
Wednesday, 23 January 2013, 15:04 GMT
Reason for closing: Fixed
Additional comments about closing: 3.7.x
I'm not alone :D
(attached is what my trace says)
In my case I have a RTL8188SU
Edit: I recommend disabling logging of kernel messages in the meantime, you can just go to /etc/syslog-ng/syslog-ng.conf and comment out the line that says
file("/proc/kmsg");
then restart the service.
The other patch was submitted in two parts, neither of which have reached mainline. They are in staging-next and will be merged into 3.7. The corresponding hashes are 5ca136a0cb96aabcb3c2158fb958677d55915f93 and fa16e5ea25d7dd83f663f333e70713aa2fa5dffe.
Commit 5ca136a is unlikely to be responsible for the fix, but either or both of the other two commits could be fixing the problem.