System hangs when you run ifconfig usb0 up and ifconfig usb0 down

Bug #625108 reported by Ricardo Salveti
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-ti-omap4 (Ubuntu)
Fix Released
High
Lee Jones

Bug Description

If you try to bring up and then bring down the usb0 interface on Panda (ES1), the system will hang.

System:
 - Maverick
 - linux-image-2.6.35-903-omap4 (actually 2.6.34)
 - Panda ES1.0

The side effect of this problem is that Network Manager will cause the boot to hang, because it runs this sequence while starting and configuring the interfaces.

To get your system to boot again just avoid running network-manager from upstart.

Tags: armel
Revision history for this message
Ricardo Salveti (rsalveti) wrote :
Download full text (5.6 KiB)

root@panda-maverick:~# ifconfig usb0 up
root@panda-maverick:~# strace ifconfig usb0 down
execve("/sbin/ifconfig", ["ifconfig", "usb0", "down"], [/* 15 vars */]) = 0
brk(0) = 0x1e000
uname({sys="Linux", node="panda-maverick", ...}) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40017000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=16970, ...}) = 0
mmap2(NULL, 16970, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40019000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libgcc_s.so.1", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\320%\0\0004\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=38488, ...}) = 0
mmap2(NULL, 37140, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x40021000
mmap2(0x40029000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x8) = 0x40029000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\301V\1\0004\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=988620, ...}) = 0
mmap2(NULL, 1025308, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x4002b000
mprotect(0x40118000, 32768, PROT_NONE) = 0
mmap2(0x40120000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xed) = 0x40120000
mmap2(0x40123000, 9500, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40123000
close(3) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x4001e000
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40126000
set_tls(0x401264c0, 0x4002091c, 0x40126b98, 0x401264c0, 0x40020000) = 0
mprotect(0x40120000, 8192, PROT_READ) = 0
mprotect(0x40029000, 4096, PROT_READ) = 0
mprotect(0x1b000, 4096, PROT_READ) = 0
mprotect(0x4001f000, 4096, PROT_READ) = 0
munmap(0x40019000, 16970) = 0
brk(0) = 0x1e000
brk(0x3f000) = 0x3f000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=1539648, ...}) = 0
mmap2(NULL, 1539648, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40127000
close(3) = 0
uname({sys="Linux", node="panda-maverick", ...}) = 0
access("/proc/net", R_OK) = 0
access("/proc/net/unix", R_OK) = 0
socket(PF_FILE, SOCK_DGRAM, 0) = 3
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4
access("/proc/net/if_inet6", R_OK) = 0
socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 5
access("/proc/net/ax25", R_OK) = -1 ENOENT (No such file or directory)
access("/proc/net/nr", R_OK) = -1 ENOENT (No such file or directory)
access("/proc/net/rose", R_OK) ...

Read more...

Revision history for this message
Ricardo Salveti (rsalveti) wrote :
Revision history for this message
Ricardo Salveti (rsalveti) wrote :

Another way to workaround the Network Manager hang is to bring the interface up before calling the service.

Revision history for this message
Ricardo Salveti (rsalveti) wrote :

I know it's not the same thing, but I can confirm that this works with ES2 and the following kernel: http://people.canonical.com/~roc/kernel/omap4-2.6.35/linux-image-2.6.35-903-omap4_2.6.35-903.8_armel.deb

Changed in linux-ti-omap4 (Ubuntu):
status: New → Confirmed
Lee Jones (lag)
Changed in linux-ti-omap4 (Ubuntu):
assignee: nobody → Lee Jones (lag)
importance: Undecided → High
Revision history for this message
Ricardo Salveti (rsalveti) wrote :

I'm unable to reproduce this issue with 2.6.35-903.8 running on my ES2 (6 and 8 layers) boards.

Changed in linux-ti-omap4 (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Oliver Grawert (ogra) wrote :

fix is in the archive (apparently the bugnumber was not mentioned in the changelog)

Changed in linux-ti-omap4 (Ubuntu):
status: Fix Committed → Fix Released
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.