** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Assignee: Kamal Mostafa (kamalmostafa) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Hello all, please note that problem still exists in natty / modemmanager
0.5-0ubuntu1, although since the latest update it looks as the modem is
recognized automatically some minutes after resume. So workaround is
still required: have a script or resume rule killing modem-manager - it
will recover
I have constructed a new test kernel PPA:
https://launchpad.net/~kamalmostafa/+archive/linux-kamal-sierra
This is the latest Lucid kernel with the addition of:
- the Sierra driver backported from upstream 2.6.36-rc3
- the patch from Torsten's "lvm1" PPA kernel: [Chris Wilson] "drm/i915: Unset
I've been using the same sus-res.sh -- the script Torsten just posted in
comment #49.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Hans-Gerd, I do think that its possible that the BIOS version could
affect the problem here... The intermittent nature of the problem, the
theory that inserting a delay in the resume sequence helps, and the fact
that the newer T61's don't seem to ever exhibit the problem makes me
think that the r
Here's the sus-res.sh script used for the suspend/resume cycles.
** Attachment added: "sus-res.sh"
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/614274/+attachment/1577042/+files/sus-res.sh
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.n
One additional question:
what are the currently used suspend / resume scripts for the full
testcase? I think that some of you have local modified versions.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification
Gentlemen,
when you are talking about differences in bios versions let me put in
one mind:
All of our systems that are currently having these problems (and of
course many other modem based else) had run a different linux os in the
*past*. We did not seen such a problem with modem suspend / resume
Strike the words "disabling the" from my comment #45. I mean simply
that "rfkill block all" didn't help the LAN.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Side note: I can't make the 'e1000e' wired LAN connection work at all
on my T61 -- even on first boot (no suspend/resume involved) dmesg shows
"eth1: link is not ready" and ifconfig shows UP but no packets. None of
the following makes the LAN work: disabling the rfkill block all,
rmmod+modprobe
A few ideas...
1. Lets compare BIOS versions, and lets all upgrade to the latest.
"sudo dmidecode -s bios-version" on my T61 showed BIOS version "2.10".
I've just updated mine to BIOS version "2.27" a.k.a. "7LETC7WW (2.27-1.08)"
using the .iso image here:
http://www-307.ibm.com/pc/support/site
I had intermittent crashes as well, but I'm not overly concerned by
them. They are very infrequent, maybe once per thousand resumes, or even
less.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because yo
I don't know if it's good or bad news: after 405 cycles with our prod.
kernel (without 20_wwan script) the session crashed:
Sep 9 13:16:02 c383019 modem-manager: (ttyUSB1): probe requested by plugin
'Sierra'
Sep 9 13:16:03 c383019 kernel: [14325.621126] [drm:i915_hangcheck_elapsed]
*ERROR* Han
I just completed 500 sucessfull suspend-resume-cycles with our
productional kernel (Linux c383019 2.6.32-24-generic-pae #39+lvm1-Ubuntu
SMP Wed Jul 14 02:37:43 UTC 2010 i686 GNU/Linux) and the modified
20_wwan without loosing the device.
To verify the positive effect of the modified 20_wwan script
All in all, there seems to be an improvement. I tested the following
configurations:
i386-kernel from Kamal (unmodified 20_wwan script): 252 suspend-resume-
cycles, then the device was gone. For the fist 230 cycles the device id
increased by one per cycle (from 2 up to 231), during the subsequent
Todays testing was also only interrupted by unwritable timer problems. Overall
I did series of
123, 77, 196, 33
suspend/resume cycles with Kamals new kernel and the 20_wwan script. I believe
the combination of kernel and script or the script alone is worth to be tested
in a broader scope now.
Today I tested the 32bit kernel from Kamal together with the 20_wwan
script. Strangely all automatic suspend/resume cycles were stopped by an
unwritable timer. However, the modem never went away and I had these
amount of successful suspend/resume cycles: 69, 78, 69, 96.
--
modem-manager fails to
The wireless LAN driver is blacklisted on the production machines, there
is no WLAN access for the T61.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
@Torsten - I have been testing with a 32-bit system installed on the T61
-- primarily the 32-bit pae-lvm1 kernel from your PPA -- but now
switched to my 32-bit test kernel from comment #29, non-pae. FWIW, the
problem has still not occurred on my machine using any kernel in many
repeated sus-res.s
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification be
I briefly tested the 32bit kernel and I had a 100% failure rate after 4
suspends - the 3G device was gone after each single suspend. The device
could be brought back with the (sudo rfkill block 2; sudo rfkill unblock
2) commands.
@ Kamal: did you install a 32bit or 64bit system on the T61? It seem
Bas news from LVM: the device was lost after 196 cycles.
But I don't know how reliable my tests are.
1) Using the 32-bit-kernel from Kamal the modem was not switched on (LED in the
panel was off) if LAN cable was connected.
2) After the syspend/resume-cylces I was no longer able to use LAN (neith
A third run of the 64bit kernel was also a success. I believe the
problem is fixed with this updated sierra module. I'm waiting for
comments from LVM on the robustness of the 32bit kernel.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You
A second run of 250 suspend/resume cycles with the test kernel was also
successful!
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Good news: with your kernel the sierra 3g modem was present during 250
suspend/resume cycles. I will now run another 250 to validate this
finding.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because yo
The attached 20_wwan script placed in /etc/pm/sleep.d/ does seem to
decrease the likeliness of the error to happen. I had a run of 102
suspend/resume cycles (timer got unwritable), a run of 74 cycles (gdm
was shown instead of desktop) and a run of 150 cycles (modem disappeared
and could not get bac
@Torsten & DSHR-
I've constructed a kernel for you to try. This is the latest Lucid kernel, but
with the Sierra driver from upstream 2.6.36-rc3. Lets see if this has any
effect on the suspend/resume behavior. (I realize that I forgot to build the
-pae kernel, but I don't think that will mat
When moving the rfkill block to a 'case "$1" in resume)' block, the
suspend resume script failed after 20, 25 and 27 times.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubunt
When I reproduced the problem again with the above 20_wwan script, I
could get the modem back by restarting network manager. I'm testing a
modified 20_wwan script now, where the rfkill is only sent on suspend.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpa
With the rfkill script running on suspend/resume, once the modem is gone
I also need to restart network-manager to bring it back.
E.g. modem disappeared
1) sudo /etc/pm/power.d/20_wwan
2) sudo restart network-manager
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.
Unfortunately the results are mixed when killing the modem upon
suspend/resume:
150 suspend/resumes, modem there
200 suspend/resumes, modem gone
86 suspend/resumes, modem gone
Here's the modified script /etc/pm/power.d/20_wwan:
#!/bin/sh
WWANSTATE=$(cat /proc/acpi/ibm/wan|awk '/status:/ {print
As per comment #18 I tested what happens when using rfkill to kill the non
existing modem. After the followin sequence the modem appeared again in
network-manager:
$ sudo rfkill block 2
$ sudo rfkill unblock 2
I will check now if killing the modem upon resume will always lead to a
working modem.
With both options set it failed to detect the modem after 33 cycles.
$ echo Y | sudo tee /sys/module/usbcore/parameters/old_scheme_first
$ echo -1 | sudo tee /sys/module/usbcore/parameters/autosuspend
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bu
Very unfortunately the next test run with old_scheme_first Y did stop
after 15 suspend/resumes.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I did a test series with the usb option changes as in comment #12 by
Kamal. Here are the results:
=
'normal'
42 cycles, modem gone
=
echo -1 | sudo tee /s
@DSHR - Thanks for that information.
For what it's worth, I cannot reproduce the problem on my T61,
regardless of the position of the wireless slide switch.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification
@ Kamal: I can reproduce the problem without USB stick.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On a Thinkpad X61 I saw the following behaviour:
Returning from suspend lsusb does not show the modem - so no modem
available in nw-manager.
After switching off wireless with the slide on the front the modem was
shown in lsusb. After switching on networking it is avalable in nm-
applet.
Maybe it
Attached is my lsusb -v output (lsusb-kamal-cannotreproduce).
The only interesting differences from yours are that (1) I have my
BlueTooth enabled but you don't, and (2) you have a SanDisk "Cruzer
Contour" USB stick plugged in. Torsten, can you verify that you can
still reproduce the problem with
The laptop with Uli that passed 500 suspend/resumes (comment #9) is also
a 6463Y3W.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A quick glance at the lshw output reveals that the motherboard product id
differs:
Kamals: 6463Y3W
Torstens: 6463WFX
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs
lsusb -v output for the laptop where the problem occurred infrequently.
** Attachment added: "lsusb-v.torstenT61"
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/614274/+attachment/1502835/+files/lsusb-v.torstenT61
--
modem-manager fails to recognize 3G modem after suspend/resume
h
lshw from the laptop where the problem occured infrequently.
** Attachment added: "lshw-torstenT61"
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/614274/+attachment/1502829/+files/lshw-torstenT61
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launc
@Torsten-
This thread references "device descriptor read/64, error -71":
http://ubuntuforums.org/archive/index.php/t-797789.html
>From that thread ... these have no apparent effect on my T61 (sus-res
>continues to work reliably), but you might try it on yours:
echo -1 | sudo tee /sys/module/us
** Attachment added: "lshw-kamal-cannotreproduce"
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/614274/+attachment/1501442/+files/lshw-kamal-cannotreproduce
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this
@Torsten-
I cannot reproduce the problem on the similar T61 that was sent to me.
I've tried your the pae-lvm1 kernel from your PPA, as well as the
standard Lucid amd64 kernel. For each, I ran 750 cycles of the sus-
res.sh test script without seeing the problem. Lets compare 'sudo lshw'
output on
A test of suspend/resume cycles gave the following results:
Laptop 1:
250 cycles, no problem
250 cycles, no problem
Laptop 2:
151 cycles, modem gone, after next suspend/resume modem was back
36 cycles, same as above
43 cycles, same as above
28 cycles, same as above
250 cycles, no problem
--
modem
** Tags added: kernel-suspend
** Tags added: kj-triage
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
After an additional suspend/resume cycle the device was back and
working.
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
Removing the driver via modprobe -r sierra and then inserting it again
does not cure the problem, the modem is still gone.
** Description changed:
Binary package hint: network-manager
A 3G modem is no longer recognized by modem-manager when the system
- resumes. It seems the USB identifica
The problem is not always present. While I could reproduce it last week
with ease, in a test run of 10 suspend/resume cycles today the problem
fails to manifest. I do not believe the usb_modeswitch is a solution, as
the sierra module takes care of this, at least according to the upstream
bug 594085
Torsten,
Possibly related to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/259028
( upstream https://bugzilla.gnome.org/show_bug.cgi?id=594085 )
Seems we might need the usb_modeswitch udev helper to run on wake up
from suspend.
Hope this helps,
** Bug watch added: GNOME B
** Attachment added: "mm.log"
http://launchpadlibrarian.net/53157340/mm.log
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "mm.log"
http://launchpadlibrarian.net/53157338/mm.log
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "find"
http://launchpadlibrarian.net/53157295/find
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
** Attachment added: "dmesg"
http://launchpadlibrarian.net/53157289/dmesg
--
modem-manager fails to recognize 3G modem after suspend/resume
https://bugs.launchpad.net/bugs/614274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
56 matches
Mail list logo
