*** This bug is a duplicate of bug 604122 ***
https://bugs.launchpad.net/bugs/604122
** This bug has been marked a duplicate of bug 604122
mmc0: Got command interrupt 0x0003 even though no command operation was
in progress.
--
You received this bug notification because you are a
** This bug is no longer a duplicate of bug 604122
mmc0: Got command interrupt 0x0003 even though no command operation was
in progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181520
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (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/1181520
petit-prince, we may want to find out the most recent kernel where one
could put the card in multiple times with no problem, if this scenario
exists. If not, we could at least bisect the least worst scenario of the
problem occurs after the first card insertion.
--
You received this bug
Christopher, thank you for pointing out this wiki article. Following the
instructions, I spent the whole day testing and bisecting. I realized that some
of the kernels I previously thought worked, only work the first time I put the
card in. Once I eject the card, I need to unload and re-load
As requested, I just tested Oneiric in a live environment and it appears
to show the same behavior (see apport information above). I'll try to
bisect which releases worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected oneiric running-unity
** Description changed:
Release of Ubuntu which I am using:
Description: Ubuntu 13.04
Release: 13.04
Linux version used: 3.8.0.21.37 (i386)
Hardware used: Dell Inspiron 6400n (also sold as E1505 in
petit-prince, thank you for testing in Oneiric. If you have personally
tested Natty and it works, it's clearly a regression from Natty to
Oneiric. Hence, could you please bisect from Natty to Oneiric to find
the offending commit via https://wiki.ubuntu.com/Kernel/KernelBisection
?
--
You
Looks like 10.04.04 is affected, too (see above logs) -- same behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181520
Title:
1180:0822 mmc0: Got command interrupt 0x0003 even though no
apport information
** Description changed:
Release of Ubuntu which I am using:
Description: Ubuntu 13.04
Release: 13.04
Linux version used: 3.8.0.21.37 (i386)
Hardware used: Dell Inspiron 6400n (also sold as E1505 in the US)
What I expected to happen:
I expected
9.10 is *not* affected, i.e. Karmic behaves as expected.
Working kernel: 2.6.31-14-generic (as shipped in 9.10 iso).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181520
Title:
1180:0822 mmc0: Got
While 10.04.04 is affected (see #50), 10.04 is *not* affected.
Working kernel: 2.6.32-21-generic (as shipped in 10.04 iso).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181520
Title:
1180:0822
10.04.2 is also *not* affected.
Working kernel: 2.6.32-28-generic (as shipped in 10.04.2 iso).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181520
Title:
1180:0822 mmc0: Got command interrupt
10.04.3 is also *not* affected.
Working kernel: 2.6.32-33-generic (as shipped in 10.04.3 iso).
Interestingly, after more testing, 10.04.4 is also *not* affected (contrary to
#50).
Working kernel: 2.6.32-38-generic (as shipped in 10.04.4 iso).
I'll have to test more releases.
--
You received
petit-prince, if you could test Natty that would be great. No need to
apport-collect further, just comment if in Natty it worked, or it did
not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181520
Christopher, thank you for bearing with me.
As suggested, I have tested Natty and can confirm it's working.
FWIW, Maverick is also working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181520
petit-prince, thank you for testing for this in Natty. Could you please
bisect this between Natty and Oneiric via
https://wiki.ubuntu.com/Kernel/KernelBisection ?
** Description changed:
- Release of Ubuntu which I am using:
- Description: Ubuntu 13.04
- Release: 13.04
+ What I expected
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181520
Title:
1180:0822 mmc0: Got command interrupt 0x0003 even though no
@Joseph: Tested with 3.10.0-031000rc2-generic. Same behaviour. As per
your suggestion, I have marked this bug as Confirmed. This bug has
already been tagged as kernel-bug-exists-upstream, so I haven't
touched the tags.
@Christopher: I am not sure if I understood your question correctly.
This bug
petit-prince, thank you for providing the requested information. For
regression testing purposes, could you please test for this in an
Oneiric live environment via http://releases.ubuntu.com/oneiric/ ?
** Tags added: precise
** Tags removed: regression-potential
** Tags added: regression-release
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.10 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
21 matches
Mail list logo
