It looks like this has been fixed upstream. I will close it. If the
problem still occurs, please reopen it.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
A proper fix for this is scheduled to be merged into kernel 3.6:
http://git.kernel.org/?p=linux/kernel/git/lenb/linux.git;a=commit;h=f197ac13f6eeb351b31250b9ab7d0da17434ea36
Would be great to see this fix incorporated into Ubuntu kernels...
--
You received this bug notification because you are a
As Xavier stated - an upgrade, that is not required for other systems is
not really a solution. It is also not the solution. However, I would
like to state that in precise, this seems to have stopped occurring,
along with the extremely frustrating new problem of no hibernate
functionality at all -
teh603, please stop posting comments here. If you have a problem in
Ubuntu, please file a new report as requested of you in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908560/comments/42
.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
So why is this still listed as "incomplete" when we have good evidence
there is a bug and we're still able to duplicate it, even with the
latest BIOS?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9085
I have already filed a new bug #969865.
2012/4/12 Christopher M. Penalver :
> xavier raynaud, please do not tack on your attachments to this bug.
>
> xavier raynaud / teh603, you are welcome to file a new report via executing
> the following at the Terminal and feel free to subscribe me to it:
>
xavier raynaud, please do not tack on your attachments to this bug.
xavier raynaud / teh603, you are welcome to file a new report via executing the
following at the Terminal and feel free to subscribe me to it:
ubuntu-bug linux
Thanks!
** Attachment removed: "dmidecode output"
https://bugs.
I'm also running the latest BIOS, and the oops happens every time I plug
it in while running. It also gives me a black screen of death if I try
to resume from suspend or hibernate and have plugged or unplugged it.
Either way, "Flash your BIOS" isn't a solution. For every story I've
heard of some p
** Changed in: linux
Status: Unknown => Invalid
** 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/908560
Title:
Kernel oops following dockin
I have BIOS A06 and the problem is still there. I'm attaching the output
from dmidecode.
** Attachment added: "dmidecode output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908560/+attachment/2943190/+files/dmidecode_output
--
You received this bug notification because you are a mem
Danny Staple, thank you for reporting this and helping make Ubuntu
better. Upstream found this to be a BIOS bug. As per
http://www.dell.com/support/drivers/us/en/19/DriverDetails/DriverFileFormats?DriverId=R302234
your BIOS is outdated. If you update your BIOS, is this oops
reproducible?
** Change
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=38782
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908560
Title:
Kernel oops f
Ok, as someone posted in the UNR thread, here's the nitty gritty about
what's going on here: https://bugzilla.kernel.org/show_bug.cgi?id=38782
. Now, for some reason the Kernel.org folks consider this bug "invalid,"
which seems like a bloody cop-out considering how quirky hardware
doesn't stop Wind
I need help because this occurs with my duo everytime I plug/unplug my
duo from the AC adapter. Can someone help me?
P.S. I'm new to this so I could use an explanation in simplest form
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
I tested kernel 3.2 from precise and it doesn't work for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908560
Title:
Kernel oops following docking dell duo
To manage notifications about this bu
I can test it tonight but can you give more details of what you mean
when you say "the touchpad regression is downright frustrating" and does
hibernate /suspend works with the new kernel ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Can anyone else confirm that this bug is partially fixed in Precise
using the latest kernel build?
Although the ACPI now fails to properly track when the AC adapter is
plugged in or not, but that's at least better than having to reboot.
--
You received this bug notification because you are a mem
Looks like this bug might be partially fixed in Precise, although the
touchpad regression is downright frustrating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908560
Title:
Kernel oops following
Looks like your stack dump is identical to mine, so I shouldn't need to
post it unless someone asks for it.
By the way, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/913848
is the one I filed on the black screen resume issue. The more attention
we can get from Dell Duo users, the more heat
I have the same problem with my duo when i plug in/out the ac adaptor. A
workaround is to shut down acpi at boot. However, without acpi, the duo
cannot go into suspend/hibernate modes anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
If it helps - I popped mine screen out on the scanner for the
screenshot. The flippy screen is handy for that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908560
Title:
Kernel oops following docki
The way mine crashes, I'm just going to take a photo of the trace on the
screen and see if that helps. At least next time I'm at home; my camera
isn't with me because I'm at work. It looks like the Duo is having ACPI
quirk issues the way the early Arrandale systems did- it seems to have
wake from s
@teh603 - I've had similar issues too, however, I'm not always able to
get to the stack trace to prove it. It crashed a fair few times on me
plugging that in. I've now taken the most recent updates, so I'll see if
it happens then. It is not 100% reproducible though - it happens often
enough to be a
I'm having a similar problem with my Duo, except it also sometimes
happens when I connect the AC adapter to the main power socket.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908560
Title:
Kernel
apport information
** Tags added: apport-collected
** Description changed:
With a Dell Duo laptop when docking while turned on, I get a kernel oops.
This is Oneiric, upgraded from 11.04 NBR to Xubuntu desktop (I tried KDE
desktop between).
Often (but not always) I get a kernel oops, r
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908560
Title:
Kernel oops following docking dell duo
To manage notifications about this bug g
Adding a likely package.
** Package changed: ubuntu => linux-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908560
Title:
Kernel oops following docking dell duo
To manage notification
Hmm okay - lspci when docked/not docked is the same. Trying lsusb.
Diff is:
$ diff lsusb_*
10,11d9
< Bus 001 Device 010: ID 413c:a502 Dell Computer Corp.
< Bus 001 Device 012: ID 0572:1412 Conexant Systems (Rockwell), Inc.
Probably a red herring - given the stack trace indicates ac notificati
Add first lspci (not docked):
** Attachment added: "Lspci when not docked"
https://bugs.launchpad.net/ubuntu/+bug/908560/+attachment/2646529/+files/lspci_not_docked.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Attachment added: "Stack dump"
https://bugs.launchpad.net/bugs/908560/+attachment/2646528/+files/IMG_NEW.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908560
Title:
Kernel oops following d
30 matches
Mail list logo
