** Changed in: ubuntu
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed error (-110)
To manage notifications about this bug go
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed error (-110)
To manage notifications about
** Project changed: linux = ubuntu
** Changed in: ubuntu
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed error (-110)
To
** Changed in: ubuntu
Status: Invalid = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed error (-110)
To manage notifications about this bug go
** Changed in: linux
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed error (-110)
To manage notifications about this bug go
This error is gone with kernel 3.4.01 generic-pae
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed error (-110)
To manage notifications about this bug go to:
About comment #14 above:
i've found this report :
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106
and it seems related to the problem reported here :
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/comments/6
--
You received this bug notification
Giving the real message done into #13 above :
mount / is busy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed error (-110)
To manage notifications about this
More comments:
i'm seeing previously (2 lines prior hub_port_status failed error
(-110) error) :
a line saying something like : root / is busy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
fwts : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/740857
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed error (-110)
To manage notifications about
Thanks for taking the time to report this bug in the upstream bug
tracking system this is a tremendous help. Launchpad has the ability to
watch lots of upstream bug trackers and this can be done by following
the procedure documented at https://wiki.ubuntu.com/Bugs/Watches. I've
added the bug watch
** Changed in: linux
Status: Unknown = Confirmed
** Changed in: linux
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report at bugzilla.kernel.org [1]? That will allow the upstream
Developers to examine the issue, and may provide a quicker resolution to
the bug.
If you
The last time i made a shutdown i was able to see an additional comment
after this error reported above:
hub_port_status failed error (-110)
acpi_power_off called
wonder if that acpi call is made too late or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
bugzilla report: https://bugzilla.kernel.org/show_bug.cgi?id=43001
** Bug watch added: Linux Kernel Bug Tracker #43001
http://bugzilla.kernel.org/show_bug.cgi?id=43001
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Kernel upstream tested:
- still get the first cold boot failling
- with the nvidia 295.33 + xorg 1.12 + kernel 3.3 and the latest Precise
updates, now i dont get the verbose mode: the screen is fully black, so i cant
say if the kernel upstream have solved that bug error or not.
Ok got the verbose mode again on shutting down the system, and see again
this error ( 2 last lines ) with the upstream kernel; so its still an
issue. Tagged as such.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed error (-110)
To manage notifications about this bug go to:
note that this trouble is not very new, it exist since we use the kernel
3 series
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed error (-110)
To manage
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed error (-110)
To manage notifications about this bug
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed error (-110)
To manage notifications about this bug go to:
Can you post a screen shot of the panic?
Also, would it be possible for you to test the latest upstream kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v3.3 kernel[1] (Not a kernel in the daily directory). Once
you've tested the upstream kernel, please
hi Joseph,
the kernel panic is always with a black screen, so should i post it ?
As Precise will not have the 3.3 kernel serie, then this issue has to be fixed
with the LTS kernel. As said this issue is not new and all around the net.
** Changed in: linux (Ubuntu)
Status: Incomplete =
We ask to test the 3.3 kernel to see if it is fixed upstream. If it is
fixed, we can cherry pick the fix into precise, or many times the fix
will make it into Precise through the stable updates upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/962113
Title:
hub_port_status failed error (-110)
To manage notifications about this bug
25 matches
Mail list logo
