mmc no longer detected on omap (BeagleXM) since

Bug #921934 reported by Tobin Davis on 2012-01-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

The last working omap image was 20120116 with the kernel. Since then, the system fails to boot as it cannot detect the mmc.

I have tested this on,, and kernels for omap.

Attached is the serial console log from

Tobin Davis (gruemaster) wrote :

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 921934

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Tobin Davis (gruemaster) on 2012-01-26
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-da-key precise regression-update

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-11.19
Tobin Davis (gruemaster) wrote :

Thanks, kernel bot. Already tested that kernel. It failed. Have a nice day.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: bot-stop-nagging kernel-failed-3.2.0-11.19
removed: kernel-request-3.2.0-11.19
Changed in linux (Ubuntu):
status: Confirmed → Fix Committed
tags: removed: kernel-da-key
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 3.2.0-12.20

linux (3.2.0-12.20) precise; urgency=low

  [ Andy Whitcroft ]

  * switch to new style rebase marker with bug number

  [ Leann Ogasawara ]

  * Add CONFIG_GPIO_TWL4030=y for arm[el|hf] to the config enforcer
    - LP: #921934

  [ Paolo Pisati ]

  * [Config] Switch CONFIG_GPIO_TWL4030=y back on arm[el|hf].
    - LP: #921934

  [ Tim Gardner ]

  * Rebase to v3.2.2, CONFIG_SND_KCTL_JACK=y
  * [Config] Add Hyper-V modules to virtual inclusion list
    - LP: #922063

  [ Upstream Kernel Changes ]

  * Revert "CHROMIUM: Fix kref usage"
  * Revert "CHROMIUM: Fix seccomp_t compile error"
  * Revert "CHROMIUM: seccomp_filter: make inherited filters composable"
  * Revert "CHROMIUM: seccomp_filter: inheritance documentation"
  * Revert "CHROMIUM: seccomp_filter: allow CAP_SYS_ADMIN management of
  * Revert "CHROMIUM: seccomp_filter: remove "skip" from copy and add drop
  * Revert "CHROMIUM: seccomp_filters: clean up warnings; kref mistake"
  * Revert "CHROMIUM: seccomp_filters: guard all ftrace wrapper code"
  * Revert "CHROMIUM: seccomp_filter: kill NR_syscall references"
  * Revert "CHROMIUM: enable CONFIG_BTREE"
  * Revert "CHROMIUM: seccomp_filters: move to btrees"
  * Revert "CHROMIUM: arm: select HAVE_SECCOMP_FILTER"
  * Revert "CHROMIUM: x86: add HAVE_SECCOMP_FILTER and seccomp_execve"
  * Revert "CHROMIUM: seccomp_filter: Document what seccomp_filter is and
    how it works."
  * Revert "CHROMIUM: seccomp_filter: add process state reporting"
  * Revert "CHROMIUM: seccomp_filter: new mode with configurable syscall
  * rebase to v3.2.2
    - LP: #795823
    - LP: #909419
    - LP: #724831
 -- Tim Gardner <email address hidden> Thu, 26 Jan 2012 02:54:56 +0000

Changed in linux (Ubuntu Precise):
status: Fix Committed → Fix Released
Tobin Davis (gruemaster) wrote :

Tested, ok.

tags: added: verification-done
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments