Holy COW!
Glad I found this bug report. This has just started happening to me.
Will try the workaround and let you know. Using Hardy Heron 8.04.3 and
an HP6910p laptop with docking station. Will not resume from suspend
when USB mouse was plugged in, but will if unplugged before waking
Nope. The options libata noacpi=1 solution posted by Daniel Gnoutcheff
doesn't work for me.
- Andor
--
[regression] Dock with USB devices + suspend == resume fails
https://bugs.launchpad.net/bugs/218760
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for testing and the update Dave. I'm marking this Fix Released
against Intrepid.
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Released
--
[regression] Dock with USB devices + suspend == resume fails
https://bugs.launchpad.net/bugs/218760
You received this bug notification
@Leann
Happy New Year!
I'm pleased to report that Intrepid, at least with 2.6.27-10-generic
(which I think may be from the backports repo?) does not show any signs
of dock-related suspend problems. Now I hope someone will be able to
backport the fix to Hardy for those poor souls who stuck with
@Leann
Now that I've worked around https://bugs.launchpad.net/bugs/197209
(again!) I am getting reliable suspend/resume when I'm not docked When
I get back from vacation on Jan 1st I will be able to test suspend in
the dock again.
--
[regression] Dock with USB devices + suspend == resume fails
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Status: Incomplete = Triaged
--
[regression] Dock with USB devices + suspend == resume fails
https://bugs.launchpad.net/bugs/218760
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Dave, have you tried disabling bluetooth? Intrepid works great for me in
terms of this issue, but with Hardy bluetooth seemed to have been a variable
with a definite effect on my suspend/resume issues.
On Mon, Dec 15, 2008 at 6:52 AM, DaveAbrahams d...@boostpro.com wrote:
@Leann,
I can't
@Leann,
I can't really tell whether I'm seeing the same bug or a different one,
but I cannot get my screen to come back upon resume in Intrepid. I am
able to ctrl-alt-del to restart the system, but clearly the screen isn't
the only thing that hasn't come back correctly, since I can't ssh in
from
on Mon Dec 15 2008, David Alexis dave.alexis-AT-gmail.com wrote:
Dave, have you tried disabling bluetooth?
No; not really a viable option for me as I use a BT mouse when at my
desktop.
Intrepid works great for me in terms of this issue, but with Hardy
bluetooth seemed to have been a
on Mon Dec 15 2008, David Alexis dave.alexis-AT-gmail.com wrote:
Dave, have you tried disabling bluetooth? Intrepid works great for me in
terms of this issue, but with Hardy bluetooth seemed to have been a variable
with a definite effect on my suspend/resume issues.
Results: first
My initial experiments with the stock intrepid configuration files (but
with fglrx installed) have shown a failure to bring back the screen on
resume, although ctrl-alt-del does cause a reboot thereafter.
Will try with my .conf file edits next.
--
[regression] Dock with USB devices + suspend ==
@Leann,
I've upgraded to intrepid and am now trying to sort out all the
changes I had to make to work around suspend problems in Hardy. I'll
let you know how this goes.
Thanks
--
[regression] Dock with USB devices + suspend == resume fails
https://bugs.launchpad.net/bugs/218760
You received
on Fri Nov 07 2008, Leann Ogasawara leann-AT-ubuntu.com wrote:
Hi Guys,
Thanks for testing and the feedback. Glad to hear it's resolved for you
with Intrepid.
@DaveAbrahams, care to test the final Intrepid release and verify if it
is fixed for you? We can then try to narrow down which
Hi Guys,
Thanks for testing and the feedback. Glad to hear it's resolved for you
with Intrepid.
@DaveAbrahams, care to test the final Intrepid release and verify if it
is fixed for you? We can then try to narrow down which patch to
backport for Hardy - although we'll need your help with that
Guys, you can't believe how happy I am with Intrepid. It feels very solid
and the display looks sharper too. But best of all, I'm now able to fully
trust the suspend/resume! I've tried all the previously failing scenarios
and more, and it works every time. Battery like is much better also.
I second that. I tested upgrading to the beta release when it first came
out, and the suspend/resume scenarios that previously failed were working
beautifully.
On Fri, Oct 24, 2008 at 8:20 PM, Seth Randall [EMAIL PROTECTED] wrote:
I've been running the Intrepid beta for a few weeks and
Hi Dave,
Thanks for your comment and concern. According to the Stable Release
Update policy - https://wiki.ubuntu.com/StableReleaseUpdates - we need
to verify this bug is first fixed in the current development release
before we can consider backporting a fix to Hardy. Since you are the
original
I've been running the Intrepid beta for a few weeks and suspending on
the dock seems to be working okay for me with my Thinkpad T61
--
[regression] Dock with USB devices + suspend == resume fails
https://bugs.launchpad.net/bugs/218760
You received this bug notification because you are a member
I'm wondering if Ubuntu is simply ignoring this bug for Hardy. Given
that Hardy is an LTS release and that the bug is not present in any
vanilla kernel, it seems to me somebody should be doing more than asking
us whether it's broken on intrepid.
--
[regression] Dock with USB devices + suspend
** Tags added: linux-2.6.27
--
[regression] Dock with USB devices + suspend == resume fails
https://bugs.launchpad.net/bugs/218760
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I installed the 2.6.27.2-generic kernel on Linux Mint 5 I my results are
similar to Daniel's. This is with OR without the USB hub and devices
plugged in. On resume, the screen is blank and it looks like the machine
locked up. But in fact, the OS is active. I had to fly blind, but I did a
Leann,
First of all, thank you so much for you attention to this issue.
Not sure if this is what you wanted, but ...
I manually downloaded and installed (via dpkg -i) the package
linux-image-2.6.27-1-generic_2.6.27-1.2_amd64.deb onto my Hardy system and
rebooted.
Frankly, I can't tell if this
** Description changed:
+ A summary of the discussion so far (as of 2008/08/29):
+
+ Steps to reproduce:
+ 1) Boot up Ubuntu while the laptop is attached to the dock.
+ 2) Connect a USB device to a port *on the dock*.
+ 3) Suspend-to-Ram.
+ 4) Resume.
+
+ Result:
+ On resume, the hardware
Daniel,
* you are correct that I am experiencing the same thing as you: total
lockup.
* I'm a bit confused about your report regarding 2.6.26.3. It sounds
like you're saying the problem is fixed, and the old workaround
doesn't break the fix. Is that right? If so, that would indeed be
Daniel, it's possible that what I'm seeing could be a different bug, but
based on my experience I would say its the same bug but that a dock triggers
slightly different/extra symptoms. The issue I'm seeing is reported by
others in the same threads as your total lockup issue.
I did experience the
I have compiled and installed a vanilla 2.6.24 kernel. I have not been
able to reproduce the hard lockup problem with this kernel either.
~~
DaveAbrahams: your interpretation of my report is correct. So far, our
problem does not appear to exist in 2.6.26.3 or vanilla 2.6.24, and it
does not seem
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Another pattern I've noticed, at least with the current kernel:
If I start up my laptop disconnected from the dock, I find that even if
I later connect it to the dock, I don't get the lockups. Just something
that might be worth noting in terms of trying to reproduce the crash.
Note that I am
I got riled up about Dave Abrahams saying that the linux-usb developers
wanted console debug info and pointed to a thread where the bug triage guy
was saying that nobody is reporting this issue. I was told to take a chill
pill, and that I can't expect the kernel devs to test Ubuntu-specific
Well, with the help of instructions at
https://help.ubuntu.com/community/forum/software/CustomKernel, I have
compiled and installed a vanilla 2.6.26.3 kernel.
I have *not* been able to reproduce this behavior with this kernel.
Suspend/resume always works even when using libata noacpi=0 (i.e. when
David, please take a chill pill. I agree the situation is a little
ridiculous, but it's not Alan Stern's fault. These people (almost
certainly volunteers) are responsible for what goes into the mainline
linux kernel, not what ubuntu ships, and it's understandable that they
don't want to debug
You're right, of course. I owe my apologies to Alan Stern and the
developers. Sorry guys. Chill pill taken, Dave. :)
On Tue, Jul 29, 2008 at 7:47 AM, DaveAbrahams [EMAIL PROTECTED]
consulting.comwrote:
David, please take a chill pill. I agree the situation is a little
ridiculous, but it's
Is there any news on this?
Last week I ran some standard update in hardy on my Thinkpad T60 which among
other things installed kernel 2.6.24-20. Now I have the above problem.
Suspend/resume works fine if undocked. If docked and usb-devices are attached
the machine hangs on resume. However,
Changing package again; hoping somone will notice.
** Changed in: linux (Ubuntu)
Sourcepackagename: usbutils = linux
--
[regression] Dock with USB devices + suspend == resume fails
https://bugs.launchpad.net/bugs/218760
You received this bug notification because you are a member of Ubuntu
Bugs,
I don't know if any of the other subscribers have the resources for
this, but in the thread at
http://thread.gmane.org/gmane.linux.usb.general/7889, the linux-usb
developers are asking for console debug info from a newer kernel. I may
be able to do that myself eventually, but am a bit too pressed
I'm sorry, but this is a little ridiculous. I read that thread, and this
guy, Alan Stern, is saying that nobody else is reporting this problem?? Has
he done the slightest bit of research into the issue?
I've been a developer for 19 years and I've seen this too many times. I'm
sorry, but its
I'm using a Dell m1330 (4GB ram, nvidia graphics, Dell wireless module)
and I'm seen this problem initially with 64-bit Hardy. After trying
everything suggested on the net, I installed 32-bit Hardy, and I'm
having the exact same symptoms. I don't have a dock, but I'm using a
USB hub that I have
The linux-usb developers think there may be a relationship to a kernel
regression: http://news.gmane.org/find-
root.php?message_id=%3cloom.20080514T050845%2d477%40post.gmane.org%3e
** Changed in: usbutils (Ubuntu)
Sourcepackagename: hal = usbutils
--
[regression] Dock with USB devices + suspend
Changing the package assignment in the hopes this will attract a glance
from the devs.
--
[regression] Dock with USB devices + suspend == resume fails
https://bugs.launchpad.net/bugs/218760
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hmm, changing the assignment to linux-source-2.6.24 didn't work; it got
automatically reset to linux. Let's see if the HAL devs have anything
to say.
** Changed in: hal (Ubuntu)
Sourcepackagename: linux = hal
--
[regression] Dock with USB devices + suspend == resume fails
The workaround was working quite nicely with 2.6.24-18-generic. But now,
2.6.24-19-generic has broken it for me too. (And I've verified via
/sys/module/libata/parameters/noacpi that the workaround is still
enabled).
It is becoming increasingly difficult to prevent myself from flaming the
Well, it's free software, so go easy on the kerosene. That said, I wish
one of the developers would at least show up (with or without flameproof
suit) and acknowledge that this ticket exists!
--
[regression] Dock with USB devices + suspend == resume fails
https://bugs.launchpad.net/bugs/218760
I'm sorry to report that, at least with 2.6.24-19-generic, turning off
libata's acpi in /etc/modprobe.d/options doesn't seem to be enough. If
I eject the laptop from the dock once before suspending, all seems to be
well (so far), but if I just boot up in the dock and suspend, I get the
same old
** Summary changed:
- Dock with USB devices + suspend == resume fails
+ [regression] Dock with USB devices + suspend == resume fails
--
[regression] Dock with USB devices + suspend == resume fails
https://bugs.launchpad.net/bugs/218760
You received this bug notification because you are a member
Daniel, the first time I tried this it didn't appear to work, but I've
now suspended and resumed many times without a hitch. So far, this is
great! Thanks so much.
--
[regression] Dock with USB devices + suspend == resume fails
https://bugs.launchpad.net/bugs/218760
You received this bug
From
https://wiki.ubuntu.com/KernelTeamBugPolicies#head-af13b59be9b1642d8c1d2462c3711b597383bbbf:
It also should be noted that Confirmed state should only be set by a person
triaging the bug report. The bug submitter or other person experiencing the bug
should not arbitrarily set Confirmed
46 matches
Mail list logo
