Sporadic failure to connect to network

Asked by John Blythe Reid

Since I upgraded to Lucid Lynx, it occasionally fails to connect to the network. It's a wired connection using an ADSL router. Rebooting fixes it each time. I upgraded from Karmic to Lucid using the update manager. I never had this problem with Karmic. Anyone got any ideas ?

Bye for now,
John.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnome-nettool Edit question
Assignee:
No assignee Edit question
Solved by:
John Blythe Reid
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

when the connection drops run:

dmesg | tail -n 20 > ~/Desktop/dmesg.txt

You can then reboot as normal and give the output

Thanks

You may not have to reboot, you could try this:

sudo /etc/init.d/networking restart

See if it makes it nice.

Revision history for this message
John Blythe Reid (jbreid-deactivatedaccount) said :
#2

Here's the output from dmesg | tail -n 20 > ~/Desktop/dmesg.txt:

[ 20.518428] CPU3 attaching NULL sched-domain.
[ 20.585422] CPU0 attaching sched-domain:
[ 20.585425] domain 0: span 0-3 level MC
[ 20.585426] groups: 0 1 2 3
[ 20.585431] CPU1 attaching sched-domain:
[ 20.585432] domain 0: span 0-3 level MC
[ 20.585434] groups: 1 2 3 0
[ 20.585437] CPU2 attaching sched-domain:
[ 20.585438] domain 0: span 0-3 level MC
[ 20.585439] groups: 2 3 0 1
[ 20.585442] CPU3 attaching sched-domain:
[ 20.585443] domain 0: span 0-3 level MC
[ 20.585445] groups: 3 0 1 2
[ 31.791883] CIFS VFS: Error connecting to socket. Aborting operation
[ 31.791887] CIFS VFS: cifs_mount failed w/return code = -101
[ 46.069728] __ratelimit: 12 callbacks suppressed
[ 46.069735] operapluginwrap[1729]: segfault at 0 ip (null) sp 00007ffff38fafd8 error 14 in operapluginwrapper-native[400000+2e000]
[ 46.399605] operapluginwrap[1777]: segfault at 0 ip (null) sp 00007fffcdb2b308 error 14 in operapluginwrapper-native[400000+2e000]
[ 46.592016] operapluginwrap[1826]: segfault at 0 ip (null) sp 00007fffcc6b0648 error 14 in operapluginwrapper-native[400000+2e000]
[ 46.673539] operapluginwrap[1869]: segfault at 0 ip (null) sp 00007fff82384e98 error 14 in operapluginwrapper-native[400000+2e000]

Revision history for this message
John Blythe Reid (jbreid-deactivatedaccount) said :
#3

I have a modified fstab to map a shared folder on a WinXp machine to a folder in my home directory. Here's the fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=d4323cde-3ab7-498c-874f-f6e58cb23a98 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=687af511-198d-4ccf-830e-261b0af55d7a none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
******* Here's the change I made ********************
//192.168.1.66/Documentos /home/john/sambaVianiP4 smbfs credentials=/etc/samba/user,rw,uid=john
0 0
*************************************************************

I notice the network drop problem happens when on the previous Ubuntu boot the WinXP machine was active. If the WinXP is switched off and Ubuntu re-booted I get the network drop problem.

By the way, the only reason that I had added that line to fstab was to get write-access to the shared folder on the WinXP machine. Even though it was defined as a shared folder with write-access on WinXP from Ubuntu I was only getting read access. Somebody on one of the forums that I could use fstab to get write-access so that's what I did.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#4

I'd log a bug

Revision history for this message
John Blythe Reid (jbreid-deactivatedaccount) said :
#5

OK, thanks.

Revision history for this message
John Blythe Reid (jbreid-deactivatedaccount) said :
#6

This has changed from a soft error to a hard error. Now, even rebooting doesn't cure it. I've tried this command:

sudo /etc/init.d/networking restart

but it makes no difference even though it responds as OK.

Is there anything else I can do to force the network connection ? At the moment I can't use the Ubuntu machine because of this problem. I'm doing this update on a WinXP machine which is connected to the same ADSL router as the Ubuntu machine.

Revision history for this message
John Blythe Reid (jbreid-deactivatedaccount) said :
#7

I tested the cable by plugging it into a WinXP laptop and it worked fine. Crawling behind the Ubuntu computer I noticed that there were two ethernet ports. It's an ASUS P7P55D EVO motherboard. I tried plugging the cable into the other port and it worked !! I had being using the other one since November so I don't know why it's given up the ghost now. Maybe it really was a hardware problem after all. The port I had been using was eth1. It's now eth0.

Thanks for you help. It's nice when things work.

Bye for now,
John.