Network ( pppoE ) failed after resuming from hibernation by Tuxonice

[ddreamer]

I used ADSL to access the internet. After resuming, the connection wouldn't be re-established by running "pon".
By running "/etc/init.d/networking restart" it would still fail until the kernel message showed
"atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex".

Could the kernel be prompted to get ready the Ethernet card during resuming process? It is a little strange since atl1 always showed messages of
"PCI INT A -> GSI 16 (level, low) -> IRQ16"
"setting latency timer to 64"
before reading caches during resuming.

Before the kernel message of "atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex" is shown, ifconfig showed:
eth0 Link encap:Ethernet HWaddr 00:1f:c6:f3:33:a2
          inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:18393 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16839 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:1000
          RX bytes:17731562 (17.7 MB) TX bytes:2714475 (2.7 MB)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:80 errors:0 dropped:0 overruns:0 frame:0
          TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5224 (5.2 KB) TX bytes:5224 (5.2 KB)

After the kernel message appeared, ifconfig shows:
eth0 Link encap:Ethernet HWaddr 00:1f:c6:f3:33:a2
          inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:18448 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16894 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:1000
          RX bytes:17740156 (17.7 MB) TX bytes:2719846 (2.7 MB)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:88 errors:0 dropped:0 overruns:0 frame:0
          TX packets:88 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5740 (5.7 KB) TX bytes:5740 (5.7 KB)

ppp0 Link encap:Point-to-Point Protocol
          inet addr:114.39.190.159 P-t-P:114.39.160.254 Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
          RX packets:29 errors:0 dropped:0 overruns:0 frame:0
          TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:6308 (6.3 KB) TX bytes:1612 (1.6 KB)

I have contacted with the developer of Tuxonice, who said that Tuxonice didn't touch the kernel. I believed the problem is in the kernel module "atl1"

[Fabio Marconi (fabiomarconi)]

Hello
is this problem present with the latest updated Karmic's or Lucid's packages ?
Thanks in advance
Fabio

[ddreamer (ddreamer)]

>Hello

>is this problem present with the latest updated Karmic's or Lucid's packages ?

>Thanks in advance

>Fabio

After upgrading to Lucid Lynx, I don't install Tuxonice. Sorry about that.

After I have time, I may try installing in my Lucid machine. Is there any documentation for tuning
after installing PPA? I want to make the compression method LZMA so that the restoration rate will
be faster. By the way, how does Tuxonice work on Lucid? My machine is a productive one and
requires stability, which I can't be sure; however, it is a laptop for which a quick restoration
from suspend-to-disk will be helpful. I just don't know the balancing point.

--
http://card.url.com.tw
土地房屋租賃買賣, 超效果且免費的媒體

[Fabio Marconi (fabiomarconi)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!