-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WARNING: CPU: 0 PID: 0 at net/core/skbuff.c:3995 #837
Comments
Some similar reports: suggest it may be an issue with skb->truesize in the network driver. |
Are you able to rebuild kernel? I have a patch from Steve that may help: |
popcornmix, thank-you very much for this. Patch applied and kernel rebuilt overnight. Streaming without any stuttering or warnings all day today. Cheers! |
I've got the same problem with my raspberry pi 2. Will this patch be merged into master or do i have to start building my own kernel? Thanks. |
@steveglen thought the linked patch might have some performance impact and he'd think about an alternative. Hopefully he can suggest something. |
Getting the same thing on the XBian kernel. I'm going to test the patch as this bug is a showstopper. |
Hi There!
on
regards, |
Does |
Thanks popcornmix. I'm away from home so can't test smsc95xx.turbo_mode=N fix for a few weeks. As I'm only streaming audio (1411kbs) so probably not notice any performance problems, unless severe. regards, Simon. |
Hello! I'm using raspberry 2 with raspbian as file server with syncthing and sometimes got this nasty error in my logs.
The error:
And yes, I'm using smsc95xx.turbo_mode=N in cmdline.txt, otherwise I get thousands of other errors.
I did not tried the patch afore mentioned patch yet. Regards, |
Also happens using On a Raspberry Pi 2 B using latest firmware from rpi-update. Here is the dmsg dump:
|
Hi, This is my settings:
and /etc/samba/smb.conf
Thanks, |
Any difference in performance with "smsc95xx.turbo_mode=N"? |
Well, I've no concrete evidences or measurement about performances, but I can't feel sensible degradation of the performance. Probably depends also on the load of the raspberry net interfaces. So, i think you can consider it as a confirmation of your belief. |
I had to put |
kernel: smsc95xx: Disable turbo mode by default See: raspberrypi/linux#837 kernel: SPI: merge upstream patches for spi-bcm2835 See: raspberrypi/linux#930 firmware: jpegdec: Fix memory corruption issue caused by repeated exif tags See: OpenELEC/OpenELEC.tv#4089 firmware: lcd: Updated pi lcd support firmware: arm_display: Avoid overscan for lcd displays
kernel: smsc95xx: Disable turbo mode by default See: raspberrypi/linux#837 kernel: SPI: merge upstream patches for spi-bcm2835 See: raspberrypi/linux#930 firmware: jpegdec: Fix memory corruption issue caused by repeated exif tags See: OpenELEC/OpenELEC.tv#4089 firmware: lcd: Updated pi lcd support firmware: arm_display: Avoid overscan for lcd displays
Latest firmware includes the patch from Steve and disables smsc95xx.turbo_mode by default (can be enabled with smsc95xx.turbo_mode=Y on command line). Please rpi-update and report if you have any errors in dmesg log, and if performance seems okay. |
I cannot tell about performance (I currently have issues with #777), but this error has disappeared from dmesg. |
@simonhiggs can you test? |
I've updated to kernel with rpi-update: And my raspberry 2 model b, running syncthing, is now up: And so far I did not get this error. This bug seems to be fixed till now. |
kernel: smsc95xx: Disable turbo mode by default See: raspberrypi/linux#837 kernel: SPI: merge upstream patches for spi-bcm2835 See: raspberrypi/linux#930 firmware: jpegdec: Fix memory corruption issue caused by repeated exif tags See: OpenELEC/OpenELEC.tv#4089 firmware: lcd: Updated pi lcd support firmware: arm_display: Avoid overscan for lcd displays
Sync with v5.19-rc8
Hello. It's been suggested on the Arch Linux ARM forums that I post here.
I'm using a Pi 2 with a HiFiBerry Digi+ SPDIF interface. Occasionally I have a loud stuttering whilst streaming from a NAS, and have the following in the logs
I've no idea about what this means, let alone how to fix. Any help most welcome.
Simon.
Linux raspi 3.18.7-4-ARCH #1 SMP PREEMPT Mon Feb 16 11:39:41 MST 2015 armv7l GNU/Linux
The text was updated successfully, but these errors were encountered: