glmtlc
Posts: 5
Joined: Sat Oct 13, 2012 7:23 am

Headless raspberryPi with eth0+USB issue Register 0x00000114

Sun Oct 14, 2012 1:00 pm

Hi,
I've read many post regarding this ethernet-USB issue of raspberry, the message is related to this one

Code: Select all

eth0: Failed to read register index 0x00000114
or
eth0: Failed to write register index 0x00000014
There is investigation running and huge posts on discussion but I've find no final solution; the problem of USB+ETH0 failure on an headless hardware is quite annoying because it stops everything, first ethernet then USB, and a power restart is necessary.
To mitigate the issue I've prepared a systemistic workaround that avoid physically remove power to the raspberry when the problem appears firstly with a graceful approach (restart eth0) and then a reboot if the previous is not working, the script is cron-ed every 10 minutes with adding this line to the general crontab file:

Code: Select all

sudo echo "*/10 * * * *    root    /opt/check_lan/lan.sh >/dev/null" >>/etc/crontab
For people is working on the issue, if interested in it, my configuration is an headless raspberry first version, with powered USB and one single 5,2V-2,5A power supply with a Y cable, many times checked voltage without issues. Here some details about system:

Code: Select all

[email protected] ~ $ uname -a
Linux raspberrypi 3.2.27+ #174 PREEMPT Wed Sep 26 14:09:47 BST 2012 armv6l GNU/Linux
[email protected] ~ $ /opt/vc/bin/vcgencmd version
Sep 25 2012 00:18:40
Copyright (c) 2012 Broadcom
version 339137 (release)
[email protected] ~ $ cat /boot/cmdline.txt
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
Two errors that generated the problem:

Code: Select all

Oct 13 08:12:32 raspberrypi kernel: [48351.659469] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Oct 13 08:12:36 raspberrypi kernel: [48355.949391] ------------[ cut here ]------------
Oct 13 08:12:36 raspberrypi kernel: [48355.949455] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x2a0/0x2c0()
Oct 13 08:12:36 raspberrypi kernel: [48355.949473] NETDEV WATCHDOG: eth0 (smsc95xx): transmit queue 0 timed out
Oct 13 08:12:36 raspberrypi kernel: [48355.949486] Modules linked in: ecb md4 nls_utf8 cifs rfcomm bnep i2c_dev snd_bcm2835 snd_pcm snd_page_alloc snd_seq snd_seq_device snd_timer snd btusb bluetooth i2c_bcm2708
Oct 13 08:12:36 raspberrypi kernel: [48355.949588] [<c0013e1c>] (unwind_backtrace+0x0/0xf0) from [<c0028ee8>] (warn_slowpath_common+0x4c/0x64)
Oct 13 08:12:36 raspberrypi kernel: [48355.949620] [<c0028ee8>] (warn_slowpath_common+0x4c/0x64) from [<c0028f94>] (warn_slowpath_fmt+0x30/0x40)
Oct 13 08:12:36 raspberrypi kernel: [48355.949654] [<c0028f94>] (warn_slowpath_fmt+0x30/0x40) from [<c02eb738>] (dev_watchdog+0x2a0/0x2c0)
Oct 13 08:12:36 raspberrypi kernel: [48355.949704] [<c02eb738>] (dev_watchdog+0x2a0/0x2c0) from [<c00343ac>] (run_timer_softirq+0x114/0x2a4)
Oct 13 08:12:36 raspberrypi kernel: [48355.949740] [<c00343ac>] (run_timer_softirq+0x114/0x2a4) from [<c002e9f0>] (__do_softirq+0x90/0x128)
Oct 13 08:12:36 raspberrypi kernel: [48355.949771] [<c002e9f0>] (__do_softirq+0x90/0x128) from [<c002eeb0>] (irq_exit+0x90/0x98)
Oct 13 08:12:36 raspberrypi kernel: [48355.949810] [<c002eeb0>] (irq_exit+0x90/0x98) from [<c000e880>] (handle_IRQ+0x34/0x84)
Oct 13 08:12:36 raspberrypi kernel: [48355.949848] [<c000e880>] (handle_IRQ+0x34/0x84) from [<c037cd14>] (__irq_svc+0x34/0xc8)
Oct 13 08:12:36 raspberrypi kernel: [48355.949880] [<c037cd14>] (__irq_svc+0x34/0xc8) from [<c000e990>] (default_idle+0x24/0x28)
Oct 13 08:12:36 raspberrypi kernel: [48355.949910] [<c000e990>] (default_idle+0x24/0x28) from [<c000eb78>] (cpu_idle+0x9c/0xc4)
Oct 13 08:12:36 raspberrypi kernel: [48355.949950] [<c000eb78>] (cpu_idle+0x9c/0xc4) from [<c04c2718>] (start_kernel+0x280/0x2c8)
Oct 13 08:12:36 raspberrypi kernel: [48355.949969] ---[ end trace 8326608cebc58b39 ]---
Oct 13 08:12:37 raspberrypi kernel: [48356.659495] smsc95xx 1-1.1:1.0: eth0: Failed to write register index 0x00000114
and

Code: Select all

Oct 14 11:49:37 raspberrypi kernel: [98837.167828] smsc95xx 1-1.1:1.0: eth0: Failed to read register
 index 0x00000114
Oct 14 11:49:41 raspberrypi kernel: [98841.337808] ------------[ cut here ]------------
Oct 14 11:49:41 raspberrypi kernel: [98841.337872] WARNING: at net/sched/sch_generic.c:255 dev_watch
dog+0x2a0/0x2c0()
Oct 14 11:49:41 raspberrypi kernel: [98841.337890] NETDEV WATCHDOG: eth0 (smsc95xx): transmit queue
0 timed out
Oct 14 11:49:41 raspberrypi kernel: [98841.337902] Modules linked in: ecb md4 nls_utf8 cifs rfcomm b
nep i2c_dev snd_bcm2835 snd_pcm snd_page_alloc snd_seq snd_seq_device snd_timer snd btusb bluetooth
i2c_bcm2708
Oct 14 11:49:41 raspberrypi kernel: [98841.338004] [<c0013e1c>] (unwind_backtrace+0x0/0xf0) from [<c
0028ee8>] (warn_slowpath_common+0x4c/0x64)
Oct 14 11:49:41 raspberrypi kernel: [98841.338034] [<c0028ee8>] (warn_slowpath_common+0x4c/0x64) fro
m [<c0028f94>] (warn_slowpath_fmt+0x30/0x40)
Oct 14 11:49:41 raspberrypi kernel: [98841.338067] [<c0028f94>] (warn_slowpath_fmt+0x30/0x40) from [
<c02eb738>] (dev_watchdog+0x2a0/0x2c0)
Oct 14 11:49:41 raspberrypi kernel: [98841.338117] [<c02eb738>] (dev_watchdog+0x2a0/0x2c0) from [<c0
0343ac>] (run_timer_softirq+0x114/0x2a4)
Oct 14 11:49:41 raspberrypi kernel: [98841.338152] [<c00343ac>] (run_timer_softirq+0x114/0x2a4) from
 [<c002e9f0>] (__do_softirq+0x90/0x128)
Oct 14 11:49:41 raspberrypi kernel: [98841.338183] [<c002e9f0>] (__do_softirq+0x90/0x128) from [<c002eeb0>] (irq_exit+0x90/0x98)
Oct 14 11:49:41 raspberrypi kernel: [98841.338222] [<c002eeb0>] (irq_exit+0x90/0x98) from [<c000e880>] (handle_IRQ+0x34/0x84)
Oct 14 11:49:41 raspberrypi kernel: [98841.338259] [<c000e880>] (handle_IRQ+0x34/0x84) from [<c037cd14>] (__irq_svc+0x34/0xc8)
Oct 14 11:49:41 raspberrypi kernel: [98841.338292] [<c037cd14>] (__irq_svc+0x34/0xc8) from [<c000e990>] (default_idle+0x24/0x28)
Oct 14 11:49:41 raspberrypi kernel: [98841.338322] [<c000e990>] (default_idle+0x24/0x28) from [<c000eb78>] (cpu_idle+0x9c/0xc4)
Oct 14 11:49:41 raspberrypi kernel: [98841.338362] [<c000eb78>] (cpu_idle+0x9c/0xc4) from [<c04c2718>] (start_kernel+0x280/0x2c8)
Oct 14 11:49:41 raspberrypi kernel: [98841.338382] ---[ end trace dfbc30edf6fae379 ]---
Here the script that I've put into /opt/check_lan folder:

Code: Select all

#!/bin/sh

# cron script for checking wlan connectivity
IP_FOR_TEST="192.168.1.1"
PING_COUNT=1

PING="/bin/ping"
IFUP="/sbin/ifup"
IFDOWN="/sbin/ifdown --force"

INTERFACE="eth0"

FFLAG="/opt/check_lan/stuck.fflg"

# ping test
$PING -c $PING_COUNT $IP_FOR_TEST > /dev/null 2> /dev/null
if [ $? -ge 1 ]
then
    logger "$INTERFACE seems to be down, trying to bring it up..."
        if [ -e $FFLAG ]
        then
                logger "$INTERFACE is still down, REBOOT to recover ..."
                rm -f $FFLAG 2>/dev/null
                sudo reboot
        else
                touch $FFLAG
                logger $(sudo $IFDOWN $INTERFACE)
                sleep 10
                logger $(sudo $IFUP $INTERFACE)
        fi
else
#    logger "$INTERFACE is up"
    rm -f $FFLAG 2>/dev/null
fi
The effect is that the system is automatically rebooted when unrecoverable problems.
Hope this can help someone to better wait final solution

rpifreeze
Posts: 76
Joined: Tue Jul 24, 2012 10:03 pm

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Sun Oct 14, 2012 5:32 pm

One question - does you NIC stop working or drops IP address assigned to it ?
Why I'm asking is because I've just observed such problem on my Pi, no matter if using integrated NIC or separate on USB port (in fact, they are connected the same way - through usb hub).
usb and broadcom issues will never be solved...Too much time passed, too much to be done...

rpifreeze
Posts: 76
Joined: Tue Jul 24, 2012 10:03 pm

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Sun Oct 14, 2012 8:47 pm

I made a second test - powering Pi from power bank. This gives me 4,8V between TP1 and TP2. USB has 4,89V so everything seems to be ok.
What happened ?
I was downloading DVD image and after one hour, my ethernet adapter vanished!
No eth0 interface and some message in dmesg like "transmit queue 0 timed out"
I use mos7830 chip/driver, but same would happen if I used integrated NIC.
IF my voltages listed above are valid, then don't try anyone to tell you this is a bad power adapter issue. If not, then we have a poor port from SW side or faulty HW. Period.

[ 8.831642] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 9.290241] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 26.307689] Adding 102396k swap on /var/swap. Priority:-1 extents:8 across:2726112k SS
[ 6946.351880] ------------[ cut here ]------------
[ 6946.351937] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x240/0x260()
[ 6946.351954] NETDEV WATCHDOG: eth0 (MOSCHIP usb-ethernet driver): transmit queue 0 timed out
[ 6946.351968] Modules linked in: mcs7830 usbnet
[ 6946.352027] [<c0012bd4>] (unwind_backtrace+0x0/0xf4) from [<c0024be8>] (warn_slowpath_common+0x4c/0x64)
[ 6946.352062] [<c0024be8>] (warn_slowpath_common+0x4c/0x64) from [<c0024c94>] (warn_slowpath_fmt+0x30/0x40)
[ 6946.352095] [<c0024c94>] (warn_slowpath_fmt+0x30/0x40) from [<c02574b8>] (dev_watchdog+0x240/0x260)
[ 6946.352139] [<c02574b8>] (dev_watchdog+0x240/0x260) from [<c002f130>] (run_timer_softirq+0x118/0x26c)
[ 6946.352171] [<c002f130>] (run_timer_softirq+0x118/0x26c) from [<c002a0b0>] (__do_softirq+0x88/0x118)
[ 6946.352198] [<c002a0b0>] (__do_softirq+0x88/0x118) from [<c002a2c8>] (irq_exit+0x7c/0x98)
[ 6946.352233] [<c002a2c8>] (irq_exit+0x7c/0x98) from [<c000e580>] (handle_IRQ+0x34/0x84)
[ 6946.352274] [<c000e580>] (handle_IRQ+0x34/0x84) from [<c02b95d4>] (__irq_svc+0x34/0xa8)
[ 6946.352306] [<c02b95d4>] (__irq_svc+0x34/0xa8) from [<c000e720>] (default_idle+0x24/0x28)
[ 6946.352334] [<c000e720>] (default_idle+0x24/0x28) from [<c000ea4c>] (cpu_idle+0x64/0x98)
[ 6946.352373] [<c000ea4c>] (cpu_idle+0x64/0x98) from [<c03bb748>] (start_kernel+0x234/0x274)
[ 6946.352392] ---[ end trace 62fa80b157b97a28 ]---
[ 8818.054861] usb 1-1.2: USB disconnect, device number 4
[ 8818.055070] MOSCHIP usb-ethernet driver 1-1.2:1.0: eth0: unregister 'MOSCHIP usb-ethernet driver' usb-bcm2708_usb-1.2, MOSCHIP 7830/7832/7730 usb-NET adapter
[ 8818.534753] usb 1-1.2: new high-speed USB device number 5 using dwc_otg
[ 8818.639552] usb 1-1.2: New USB device found, idVendor=9710, idProduct=7830
[ 8818.639603] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8818.639620] usb 1-1.2: Product: USB-MAC Controller
[ 8818.639633] usb 1-1.2: Manufacturer: Moschip Semiconductor
[ 8818.639646] usb 1-1.2: SerialNumber: 6e000069
[ 8818.712252] usb 1-1.2: applying rev.C fixup
[ 8818.724698] usb 1-1.2: applying rev.C fixup
[ 8818.746652] MOSCHIP usb-ethernet driver 1-1.2:1.0: eth0: register 'MOSCHIP usb-ethernet driver' at usb-bcm2708_usb-1.2, MOSCHIP 7830/7832/7730 usb-NET adapter, 00:60:6e:00:00:69
[ 8819.079413] usb 1-1.2: USB disconnect, device number 5
[ 8819.079615] MOSCHIP usb-ethernet driver 1-1.2:1.0: eth0: unregister 'MOSCHIP usb-ethernet driver' usb-bcm2708_usb-1.2, MOSCHIP 7830/7832/7730 usb-NET adapter
usb and broadcom issues will never be solved...Too much time passed, too much to be done...

glmtlc
Posts: 5
Joined: Sat Oct 13, 2012 7:23 am

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Mon Oct 15, 2012 9:31 pm

The NIC is disappeared, also the USB is affected, in fact, in my log:

Code: Select all

Oct 13 08:13:23 raspberrypi kernel: [48402.770206] smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
Oct 13 08:13:26 raspberrypi kernel: [48406.020447] sd 1:0:0:0: Device offlined - not ready after error recovery
Oct 13 08:13:26 raspberrypi kernel: [48406.020495] sd 1:0:0:0: [sdb] Unhandled error code
Oct 13 08:13:26 raspberrypi kernel: [48406.020509] sd 1:0:0:0: [sdb]  Result: hostbyte=0x05 driverbyte=0x00
Oct 13 08:13:26 raspberrypi kernel: [48406.020529] sd 1:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 46 76 60 00 00 20 00
Oct 13 08:13:26 raspberrypi kernel: [48406.020661] sd 1:0:0:0: [sdb] killing request
Oct 13 08:13:26 raspberrypi kernel: [48406.021242] EXT4-fs warning (device sdb1): ext4_end_bio:251: I/O error writing to inode 1441817 (offset 3300917248 size 126976 starting block 3290398)
(sdb is the drive used for writing downloaded data from internet)
I have no need to use external eth usb adapter because of integrated eth furthermore the fault will affect both types (integrated and or external).
So, as I've understood from other post the problem is more related to USB because eth relies on it.
Let's wait for a fix


rmistero
Posts: 27
Joined: Mon Feb 20, 2012 9:14 pm

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Tue Oct 16, 2012 11:12 pm

Hello,

Same issue here. The raspberry which developed the issue had been running for almost 2 months without any problem as a home DNS server.
Problem started with 3.1.9 and continue on latest kernel.
The problem happened intermittently and hieratically. but seems to happen faster if it is busy.
I created a script to collect some data ( top, lsof, ...) : when the problem occurs and clearly the raspberry was idle almost every time.
During tests. there was no USB device connected to it, only power plug and network cable.
Voltage is stable at 4.89-4.90V every time.
Now, I noticed that when the problem happens it tend to happen on the next reboot too and on the next reboot..
However, if I switch off and swap the SD card to another raspi ( I got it from a friend which don t have this issue at all), then it works fine straight away.
If I leave the raspberry pi to rest then, it starts again fine and works for hours or minutes..

It looks more to me like a hardware issue rather than a software one. A hot failure or something like that.

rmistero

glmtlc
Posts: 5
Joined: Sat Oct 13, 2012 7:23 am

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Wed Oct 17, 2012 5:56 pm

It can be a mystery or both software + certain hardware in certain conditions.
I've thought it is mainly related to high network traffic because the network traffic is handle by the same USB controller (if I've understood well the architecture) and the data is sent through USB to and USB disk
But sometimes happens also with low traffic.

Happily it is three days since I've no reboot, previously it was daily, sometimes twice a day.

But in this period I've also low traffic on my net so low probability of "collisions"

rpifreeze
Posts: 76
Joined: Tue Jul 24, 2012 10:03 pm

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Wed Oct 17, 2012 9:21 pm

rmistero wrote:Hello,
Problem started with 3.1.9 and continue on latest kernel.
It looks more to me like a hardware issue rather than a software one. A hot failure or something like that.
rmistero
Hmm, I might be wrong but something is worng with the code i think and all issues gathered together might releal some problem.
Why?
You're saying that 3.1.9 worked properly. solet's assume 3.2.x is buggy.
You're saying this is a hardware issue. Well connecting some "bad loop" than consumes some resources, we might be receiving also the well known bug "process X hung for 120 seconds bla bla bla".
It's not about processes consuming all available CPU time, but some process blocking other things, so....you get such messages than "something hung".
I'm not a developer, nor debug expert, but see the internet for problems like:
"INFO: task nfsd:1188 blocked for more than 120 seconds" (remove nfsd and PID when googling)
and see there was lot of problem with kernels (CentOS, RHEL), despite HW platform used (x86_64) in those cases, but also virtual machines.
So...let's wait a month or two until fix or new kernel arrives ;)
Just FYI - I tried to skin my own kernel from all unneeded modules, also not compiling them into kernel, but....seems the problem is with memory management. That's my observation.
usb and broadcom issues will never be solved...Too much time passed, too much to be done...

rmistero
Posts: 27
Joined: Mon Feb 20, 2012 9:14 pm

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Thu Oct 18, 2012 9:28 am

rpifreeze wrote:
rmistero wrote:Hello,
Problem started with 3.1.9 and continue on latest kernel.
It looks more to me like a hardware issue rather than a software one. A hot failure or something like that.
rmistero
Hmm, I might be wrong but something is worng with the code i think and all issues gathered together might releal some problem.
Why?
You're saying that 3.1.9 worked properly. solet's assume 3.2.x is buggy.
You're saying this is a hardware issue. Well connecting some "bad loop" than consumes some resources.
Hello,

As you quoted, the problem was already present on 3.1.9+

...but with a different error :

kernel: DEBUG:handle_hc_chhltd_intr_dma:: XactErr with NYET/NAK/ACK

...The consequences were exactly the same towards the NIC.

Since I installed 3.2.27+ I got the errors :
smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
smsc95xx 1-1.1:1.0: eth0: Failed to write register index 0x00000114

There are no kernel stacks, no segvs, no oom (out ot memory ) issues, no other error in syslog and messages.
Again I lose network access ( the eth0 is still present in ifconfig and link is up) but now, if i connect a keyboard, it doesn t work either( I could do that using 3.1.9+)

NOTE: Initially I thought it was due to a broadcast storm or some broadcast that was hammering the Pi because the network led on the pi was flashing quite rapidly althought I had lost network access already. I took a packet capture on the router to which the Pi connects to and traffic was normal/idle.

Since I got a second Pi it was easy to compare.

1. I installed a fresh raspbian build 180912 (3.2.27+) and configured it on the "faulty" pi. I also took the PSU of the known good Pi
2. I took the SD card and the PSU of the "faulty" Pi onto the known good Pi.

If the issue was related hardware or firmware ( program inside the chip), I would think that it should occur again on a vanilla install without X server running and no USB devices connected, only ethernet cable and PSU. If it was software related however, it should follow the SD card.

Result : the second is still running after 22 hours. On the "faulty" Pi the problem occurred again after 16mins. Same errors in the logs :

smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
smsc95xx 1-1.1:1.0: eth0: Failed to write register index 0x00000114

And no access via keyboard..

Even thought, the voltage was stable at 4.90V when issue occurred, I measured the F3 polyfuse tension few hours later and it was 0.01V.. no problem there either..

Finally, and more importantly, I didn't say it was a hardware issue, I assumed it could be one and I have arguments to defend my assumptions.
NOTE: The day I start making statments about technologies I don't know (like this NIC running on USB hub), I quit the IT industry, I promise ! :)

Also you may want to have a look at the following :

This is the source code the smsc95x driver :

https://android.googlesource.com/kernel ... smsc95xx.c

The error message is displayed if ret <0

if (unlikely(ret < 0))
netdev_warn(dev->net, "Failed to read register index 0x%08x\n", index);
(same for write)

ret is
ret = usb_control_msg(dev->udev, usb_rcvctrlpipe(dev->udev, 0),
USB_VENDOR_REQUEST_READ_REGISTER,
USB_DIR_IN | USB_TYPE_VENDOR | USB_RECIP_DEVICE,
00, index, buf, 4, USB_CTRL_GET_TIMEOUT);

ret variable is a call of the command usb_control_msg

http://libusb.sourceforge.net/doc/funct ... olmsg.html

"usb_control_msg performs a control request to the default control pipe on a device. The parameters mirror the types of the same name in the USB specification. Returns number of bytes written/read or < 0 on error."

I hope it is more clear.

Cheers,

Nicolas

rmistero
Posts: 27
Joined: Mon Feb 20, 2012 9:14 pm

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Fri Oct 19, 2012 8:17 pm

Hello,

Because I'm stubborn and I really can't be bothered with RMAing things in general, I have been trying again.
I reinstalled raspbian build 1809 with 3.2.27+ from scratch ( Same SD card, same PSU) and run another test with no keyboard connected just ethernet connected to laptop.
The problem didn't occur straight away ( I expected that following my assumptions, since the pi hadn't resting for 2 days), but it did happen at the end..
Now, the symptoms changed slightly. First of all, there wasn't any error in the logs like before.
Also, I could plug a keyboard and use it. eth0 was up and configured correctly; no error on ifconfig counters but no ping in or out..
Again, I noticed that the link led was blinking at the pace of external pings ! yet taking a packet capture on the side of the pi and laptop : nothing went in or out.
I tried to unbind/bind the smsc95xx driver but still nothing...
Also, connecting/disconnecting the ethernet cable would raise an event in the logs as normal ( link up/down).

So it was like the ethernet card worked but like if signals would not reached the upper layers of the OS.

Just for the sake of it, I connected another USB ethernet card ( a Belkin fastethernet) and it worked fine with same ethernet cable...
I unplugged the keyboard and everything finally hung like I used to see before.. but still no errors in logs when I checked on reboot...

Then I had an idea, it is really unusual to me to see USB drivers compiled into the kernel, I'm not saying it is bad but just unusual because of the nature of USB devices themselves ( detachable).
Anyway, just for troubleshooting purpose if a driver seems to behave badly you would agree that compiling it in hard into the kernel is a bad idea
So I recompile the kernel with the driver as module :

This is the diff between raspbian kernel config and mine :

> # Linux/arm 3.2.27+ Kernel Configuration
> CONFIG_USB_NET_SMSC95XX=m
> CONFIG_I2C_BCM2708_BAUDRATE=100000
> CONFIG_USB_DEBUG=y

NOTE: I enabled USB debugging also.

Anyway, I still don't understand why but since I have done that, the pi behave like a charm ! :)
It has been running for several hours now. I have unplugged and re-plugged keyboard, second ethernet adapter many times and still no hanging..
Because of the second ethernet adapter the voltage is now 4.82V but still nae bother !

I would be good to see if the people in this thread and others having issues with ethernet and USB could try.

my 2 cents.

rmistero
Posts: 27
Joined: Mon Feb 20, 2012 9:14 pm

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Fri Oct 19, 2012 10:29 pm

right problem came back ... at least the law of physics are safe :)

Reading the thread below Farnells knows about the issue it seems..

http://www.raspberrypi.org/phpBB3/viewt ... 98#p197198

So RMA it will be for me... But it seems it is not going to solve all problems at all ..

http://www.raspberrypi.org/phpBB3/viewt ... 95#p130095

mcgyver83
Posts: 358
Joined: Fri Oct 05, 2012 11:49 am

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Sat Oct 20, 2012 7:52 am

I still have these lines in kernel log as I wrote in this post http://www.raspberrypi.org/phpBB3/viewt ... 28&t=20491:
smsc95xx 1-1.1:1.0: eth0: Failed to read register index 0x00000114
ERROR::dwc_otg_hcd_urb_enqueue:477: Not connected

Until now all worked fine.I have the same issue as you have? I have to RMA my raspberry to Farnell?

rmistero
Posts: 27
Joined: Mon Feb 20, 2012 9:14 pm

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Sat Oct 20, 2012 8:41 am

Hello,

Cutting the power during an apt-get could have corrupted the system depending at which stage it occurred. It is unlikely that it would damage the Pi ( although it depends..). Since you have reinstalled a new image, and based on the error it could be that.

You may want to read this : http://elinux.org/R-Pi_Troubleshooting

Triple check your PSU..

Hope it helps.

chrism69
Posts: 1
Joined: Sat Oct 20, 2012 9:30 pm

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Sat Oct 20, 2012 9:53 pm

I've had the same problem for weeks now with my Pi running Raspbian wheezy and have tried various options to resolve this. My latest is working so far. Previously I would often have to reboot after between 1 and 4 hours, sometimes longer but the most I got was about 7 or 8 hours from memory. I only have an RFXtrx433 and an Aeon Z-Stick 2 attached via usb. I previously had other devices attached via a powered usb hub but removed them in case they were causing the issues, that made no difference. I have not been game to re-attach the usb hub yet.

Here are the details of my Pi after my latest changes:

Code: Select all

[email protected] /var/log $ uname -a
Linux raspberrypi 3.2.27+ #247 PREEMPT Tue Oct 16 01:49:18 BST 2012 armv6l GNU/Linux

[email protected] /var/log $ cat /boot/cmdline.txt
dwc_otg.fiq_fix_enable=0 sdhci-bcm2708.sync_after_dma=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait

from /var/log/debug:
Oct 20 00:03:53 raspberrypi kernel: [    1.812872] dwc_otg: Microframe scheduler enabled
Oct 20 00:03:53 raspberrypi kernel: [    1.902757] dwc_otg: FIQ disabled
The key change that worked for me was to disable FIQ. I had previously removed other options that I had found in various forums and they made no difference for me. My last change was to disable FIQ and my Pi has now been up for 1 day 8 hours and 40 mins. I noticed there was an increase in interrupts when I disabled FIQ (from around 12k to 13k) but I can live with that.

mcgyver83
Posts: 358
Joined: Fri Oct 05, 2012 11:49 am

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Sat Oct 20, 2012 11:18 pm

it's not related to power.before my parents unplugged the power networking worked fine so if it worked before it should work now...

rmistero
Posts: 27
Joined: Mon Feb 20, 2012 9:14 pm

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Sun Oct 21, 2012 12:24 am

mcgyver83 wrote:it's not related to power.before my parents unplugged the power networking worked fine so if it worked before it should work now...
Have you measured the TP1- TP2, F3 polyfuse ?

With defects, whatever they are, there is always a before and an after. It does usually work fine before ! :)

mcgyver83
Posts: 358
Joined: Fri Oct 05, 2012 11:49 am

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Sun Oct 21, 2012 8:14 am

I always have a 5,01V on TP1-TP2 also during a command I found to test overclock (now is default speed) .
What I have to check about polyfuse F3?

mcgyver83
Posts: 358
Joined: Fri Oct 05, 2012 11:49 am

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Sun Oct 21, 2012 9:15 am

My parents unplugged the power to switch the old power supply with a new powered usb hub...
I tried many times also with the old power supply but didn't work...

Now, at after 100 tentative it works fine with the old power supply...
I don't know why..maybe the usual solution "check the power supply" again worked.
To spread knowledge the power usb hub (output 1.0A) provide 4,32V during the boot so isn't acceptable for the rasp.

glmtlc
Posts: 5
Joined: Sat Oct 13, 2012 7:23 am

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Mon Oct 22, 2012 10:40 pm

Since the beginning of the post, no NIC fault, up to now more than 6 days.
The traffic on my net was very various but always generated by transmission-daemon or USB writes (for the USB).

Continue to update ... waiting for a fix (if there will be one), RMA to me is not an option

godFather89
Posts: 150
Joined: Fri May 18, 2012 9:40 am
Location: Timisoara, RO

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Tue Oct 23, 2012 6:54 am

I also have the same problem http://raspberrypi.org/phpBB3/viewtopic ... 36&t=20727.

I don't have the integrated NIC and I used the RPi with a lapdock (so using the lapdock's USB hub).

I also tried using the above cmdline.txt but had the same results. I have the RPi from may this year (if that makes any difference).

So, it works for a few mins, after that, nothing. Ethernet seems up, has the proper configuration (ip, netmask, etc.) but doesn't work anymore. No ping, no nothing. Wireless, on the other hand, works fine (from RPI) but doesn't get shared over ethernet...

Same error message in dmesg. But sometimes it does not apear but still hangs.

I also tried using just ethernet and it works fine (more than 10 GB transferred).
Could this be a problem with iptables? Or with the USB->ETH adapter driver (I currently use the one integrated in the distribution)?

rpifreeze
Posts: 76
Joined: Tue Jul 24, 2012 10:03 pm

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Tue Oct 23, 2012 6:54 pm

godFather89 wrote:Could this be a problem with iptables? Or with the USB->ETH adapter driver (I currently use the one integrated in the distribution)?
Yes.
Moreover, I also had the same issue with USB ETH as you did. Mine was of moschip 7830 (?) chipset, but connecting to Pi via com port, I noticed it blew up. I'm not an expert but driver along with iptables modules crashed. Maybe in reverse order, but no expert at all, so in my opinion, it was related to either buggy driver for NIC or iptables or....power on usb ports.
I've hacked my RPi, removed F1 F2 polyfuses and drain power from main line to USB ports.
I with I could send you photos, but I'm poor and don't have camera :(
As you see, I've got stable voltage on usb (~4,98) so in your case, it could be one of those three things.
usb and broadcom issues will never be solved...Too much time passed, too much to be done...

glmtlc
Posts: 5
Joined: Sat Oct 13, 2012 7:23 am

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Wed Oct 24, 2012 5:43 am

Rebooting via power cycling is potentially risky because you can catch a write on the SD card during restarting and corrupt the SD card making it non bootable (I've verifyed myself), if you implement the script above (or similar, maybe using a monit program) it restart more gracefully and without care from you.
This is true provided that your kernel don't go in panic (but this is not the typical case), if so power cycling is needed.
The driver is buggy for sure but not so many people are working on finding solution so it could be far in time.

7 1/2 days no fault ...

ski522
Posts: 394
Joined: Sun Sep 30, 2012 2:22 pm

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Wed Oct 24, 2012 11:38 am

Hhhhmmmm...just had this problem for the first time last night after adding a USB sound card (at least coincidentally). I will have to keep an eye on it to see if the problem continues. I have a 700mA supply and the USB sound card supposedly only draws 50mA. The other change I made was to the /boot/cmdline.txt file and added in the "dwc_otg.speed=1" to fix sound problems with my USB sound card.

godFather89
Posts: 150
Joined: Fri May 18, 2012 9:40 am
Location: Timisoara, RO

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Wed Oct 24, 2012 12:12 pm

On my setup this is not a power problem. I don't have the fuses either!
So this is either an USB, NIC driver (wireless or ethernet) or iptables problem.
Curios is that individually, they work. Is there any other way to share internet connection, other than iptables?

ski522
Posts: 394
Joined: Sun Sep 30, 2012 2:22 pm

Re: Headless raspberryPi with eth0+USB issue Register 0x0000

Wed Oct 24, 2012 12:22 pm

godFather89 wrote:On my setup this is not a power problem. I don't have the fuses either!
So this is either an USB, NIC driver (wireless or ethernet) or iptables problem.
Curios is that individually, they work. Is there any other way to share internet connection, other than iptables?
Well that's good to know....I think ;)!

I also had a Logitech wireless keyboard and pulled the USB adapter for now to see what happens. My PI had been rock solid since I bought it.

Return to “Troubleshooting”