148f:5370 Please enable Ralink rt35xx and rt53xx support on the rt2800usb driver

Bug #1019561 reported by Fabien Lusseau
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Leann Ogasawara
Precise
Fix Released
Medium
Leann Ogasawara
Quantal
Fix Released
Medium
Leann Ogasawara

Bug Description

== Precise SRU Justification ==
Enable support for rt33xx and rt35xx wireless chipsets in the rt2800usb driver. Without this some wifi devices are inoperable.

== Fix ==
Enable CONFIG_RT2800USB_RT35XX and CONFIG_RT2800USB_RT53XX

== Impact ==
Minimal risk of regression. Enables support for the following:

#ifdef CONFIG_RT2800USB_RT35XX
        /* Allwin */
        { USB_DEVICE(0x8516, 0x3572) },
        /* Askey */
        { USB_DEVICE(0x1690, 0x0744) },
        /* Cisco */
        { USB_DEVICE(0x167b, 0x4001) },
        /* EnGenius */
        { USB_DEVICE(0x1740, 0x9801) },
        /* I-O DATA */
        { USB_DEVICE(0x04bb, 0x0944) },
        /* Linksys */
        { USB_DEVICE(0x13b1, 0x002f) },
        { USB_DEVICE(0x1737, 0x0079) },
        /* Ralink */
        { USB_DEVICE(0x148f, 0x3572) },
        /* Sitecom */
        { USB_DEVICE(0x0df6, 0x0041) },
        { USB_DEVICE(0x0df6, 0x0062) },
        /* Toshiba */
        { USB_DEVICE(0x0930, 0x0a07) },
        /* Zinwell */
        { USB_DEVICE(0x5a57, 0x0284) },
#endif
#ifdef CONFIG_RT2800USB_RT53XX
        /* Azurewave */
        { USB_DEVICE(0x13d3, 0x3329) },
        { USB_DEVICE(0x13d3, 0x3365) },
        /* Ralink */
        { USB_DEVICE(0x148f, 0x5370) },
        { USB_DEVICE(0x148f, 0x5372) },
#endif

== Original Bug Description ==

Linux 3.0 and later kernels have some experimental support for the Ralink rt35xx and rt53xx chipsets. But it's not enabled on Ubuntu.

I recompiled the kernel with this module, and it's working fine with my rt5370 wifi dongle. And this dongle work out of the box in debian Sid and work on wheezy if I add the correct firmware.

It's already enabled in the Debian configuration of the 3.2 kernel, Ubuntu is using the same kernel and have support enabled for the same chipsets (rt35xx and rt53xx) for the pci variant of the module.

I think this was disabled by mistake.

Please add this to the kernel configuration on Precise and Quantal:

CONFIG_RT2800USB_RT35XX=y
CONFIG_RT2800USB_RT53XX=y

----

A little more about the rt35xx and rt53xx. Theses chipsets are used in a lot of very cheap wifi dongle and arm devices such as Android Tablets (Sometime compatible with Ubuntu Arm). They are very common and work very well despite the very low price. There is an official Linux driver on the Ralink Website, but it is nearly impossible to make it work. The driver provided officially with the Kernel work flawlessly (based on my own experience).

There is a package of backported network modules on Precise, and this contain a rt2800usb module that work with the rt53xx. But this package is nearly undocumented, and that was a lucky find. Nobody will do that instinctively in order to make that dongle work.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SI7012 [SiS SI7012], device 0: Intel ICH [SiS SI7012]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: fabien 1484 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'SI7012'/'SiS SI7012 with ALC650F at irq 18'
   Mixer name : 'Realtek ALC650F'
   Components : 'AC97a:414c4723'
   Controls : 50
   Simple ctrls : 33
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=a83d504e-0cd5-4d79-90d2-c3502453047f
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MachineType: ASUSTeK Computer Inc. A6K
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.2.0-26-generic-pae root=UUID=b698ea91-9c8b-41a4-950c-720314a4423c ro rootflags=subvol=@ quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-26-generic-pae N/A
 linux-backports-modules-3.2.0-26-generic-pae N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: precise precise
Uname: Linux 3.2.0-26-generic-pae i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 08/18/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 207
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: A6K
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr207:bd08/18/2005:svnASUSTeKComputerInc.:pnA6K:pvr1.0:rvnASUSTeKComputerInc.:rnA6K:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: A6K
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 1019561

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
Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : Re: Please enable Ralink rt35xx and rt53xx support on the rt2800usb driver

I can provide a dmesg of the device not loading any module when plugged in but that will not be very usefull.

As already said, the support is (maybe mistakenly) disabled on Ubuntu (Precise and Quantal).

description: updated
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Fabien Lusseau, thank you for reporting this and helping make Ubuntu better. Regarding your comments:
>"I can provide a dmesg of the device not loading any module when plugged in but that will not be very usefull."

It is agreed only providing dmesg is not useful. What we need is for you to follow the instructions in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1019561/comments/1 .

As well, if you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote :

Already tested on the latest kernel, it's working on upstream 3.5-rc4 and 3.2.21

But it's also working on the Ubuntu kernel (3.2.0-26-generic amd64), just have to enable the support before compilation.

I will do the apport-collect thing, but i already know what is the problem and the fix that need to be done (description).

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : AcpiTables.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote :

apport information

description: updated
Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : AlsaDevices.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : ArecordDevices.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : BootDmesg.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : CRDA.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : Card0.Codecs.codec97.0.ac97.0.0.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : Card0.Codecs.codec97.0.ac97.0.0.regs.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : IwConfig.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : Lspci.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : Lsusb.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : PciMultimedia.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : ProcModules.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : UdevDb.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : UdevLog.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : WifiSyslog.txt

apport information

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote : Re: Please enable Ralink rt35xx and rt53xx support on the rt2800usb driver

Apport-collect done ! I've done it on a freshly installed Precise with updates.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Fabien Lusseau, just to clarify, we would need you to test the mainline kernel, without the kernel module recompilation you noted makes the Ubuntu repo kernel work, and provide the results of this in this report.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
summary: - Please enable Ralink rt35xx and rt53xx support on the rt2800usb driver
+ 148f:5370 Please enable Ralink rt35xx and rt53xx support on the
+ rt2800usb driver
tags: added: needs-upstream-testing
removed: driver ralink rt5370 wifi
Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote :

I didn't recompiled the module I recompiled the whole kernel !

You are turning me crazy with that, it's just a kernel configuration mistake !

You forgot theses config key:

CONFIG_RT2800USB_RT35XX=y
CONFIG_RT2800USB_RT53XX=y

And without that of course there will not be support for this chipset. Because it is disabled.

I haven't done anything special to make it work, I just added a config time option that is (I really don't know why) disabled.

I can do all sort of things if you want. But I have the feeling you are playing a game with me. It's so simple !

Without that:
CONFIG_RT2800USB_RT35XX=y
CONFIG_RT2800USB_RT53XX=y

It doesn't work

With that:

CONFIG_RT2800USB_RT35XX=y
CONFIG_RT2800USB_RT53XX=y

It's working.

It's working on 3.5-Rc4, in 3.2.21 and even with 3.2.0-26-generic that Ubuntu is coming with if I recompile the Kernel with this options (the driver is already here in source !).

The apport-collect I'have done is without the modification but this computer have two wifi cards. One on the mini pci and the other is the usb dongle that is not working.

And this summary you just changed is not what I mean. I do want you to enable the support for those chipsets, not just that specific card.

It's not a driver that is missing a card ID, it's a driver that has two options disabled, and theses options are to make those chipsets work.

To sum it up: Please add support for Ralink rt35xx and rt53xx support on the rt2800usb driver that is already in the kernel but disabled by Ubuntu kernel team (or left disabled by not noticing it).

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote :

And yes of course this doesn't work with 3.5-rc4 without those options set in the kernel. I tested all sort of combinations. But if it's not enabled, it's not enabled, I don't know what is so special about it ... That seems so obvious. I must have been not clear enough because I don't know why I should do all this work in pure waist just to prove you that it's just a simple and common disabled driver thing.

tags: removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote :

I'm really sorry Christopher M. Penalver, but I have taken so much time before sending this bug report to make sure I wasn't wrong, to be sure that was not my mistake and that this bug was legitimate that doing all theses basic verifications have droved me nuts.

I'm so sorry if you found me unrespectfull. But that's not the case. I'm just tired.

Just to prove my good will, I have just compiled the last mainstream kernel, linux-3.5-rc5, and the result is the same. I have to set:

CONFIG_RT2800USB_RT53XX=y

to make the rt5370 work. And I think this should be a good idea to also add:

CONFIG_RT2800USB_RT35XX=y

For those who use RT35xx chipsets that are I'm sure, in the same boat. A driver is in the kernel, but is not compiled on Ubuntu for whatever reason.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Fabien,

Thank you for your patience and understanding here. Indeed the request you've made is for a small configuration change and thus the extra testing of mainline kernels and apport collect information wasn't entirely necessary in this case. Just for some extra background information, our typical kernel configuration policy is to disable options marked EXPERIMENTAL until a request such as this has been made to justify enabling it. This is the reason both of the config options you've noted were disabled:

config RT2800USB_RT35XX
        bool "rt2800usb - Include support for rt35xx devices (EXPERIMENTAL)"
        depends on EXPERIMENTAL
        default y
        ---help---
          This adds support for rt35xx wireless chipset family to the
          rt2800usb driver.
          Supported chips: RT3572

config RT2800USB_RT53XX
       bool "rt2800usb - Include support for rt53xx devices (EXPERIMENTAL)"
       depends on EXPERIMENTAL
       ---help---
         This adds support for rt53xx wireless chipset family to the
         rt2800usb driver.
         Supported chips: RT5370

I'll follow up and post a test kernel with both of these options enabled in the Quantal kernel for now. We'll want to get testing and confirmation for the changes in the Quantal development kernel before this will be considered for SRU (stable release update) for Precise. I'll try and get the test kernel posted here by end of day. Thanks again for your time and reporting this issue.

Changed in linux (Ubuntu):
assignee: nobody → Leann Ogasawara (leannogasawara)
importance: Undecided → Medium
status: Confirmed → In Progress
Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote :

Thanks a lot !

This change can be made also made in Oneiric, because if I recall correctly it use 3.0 Kernel. But I haven't checked if this option is working properly in 3.0.

I will follow and check every updates and test everything you want me to test. (proposed updates activated)

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Fabien,

I've posted a Quantal test kernel (see url below) with the requested config options enabled. Please test and let me know your results. Note: Please be sure to install both the linux-image and linux-image-extra test packages as you'll need both for a complete kernel install for Quantal. Thanks.

http://people.canonical.com/~ogasawara/lp1019561/i386/

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote :

Thanks. I tested it and it's working.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Fabien,

Thanks for the testing and the feedback. I've applied this fix to the Quantal kernel git repo. I'll work on building a test kernel for Precise so that we can get a positive test confirmation there as well before submitting this for SRU for Precise. I'm unfortunately away for the next few days so please bear with me as I prep this for Precise.

Changed in linux (Ubuntu Quantal):
status: In Progress → Fix Committed
Changed in linux (Ubuntu Precise):
assignee: nobody → Leann Ogasawara (leannogasawara)
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Fabien,

Thanks for your patience. I've built a Precise test kernel with the requested config options enabled (see url below). When you have a moment, can you please test and let me know your results. Thanks in advance.

http://people.canonical.com/~ogasawara/lp1019561/i386/precise/

Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote :

Yes it's working perfectly !

Thanks a lot !

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 3.5.0-4.4

---------------
linux (3.5.0-4.4) quantal-proposed; urgency=low

  [ Andy Whitcroft ]

  * [Packaging] getabis should be extracting all packages
    - LP: #1021174
  * [Config] getabis -- series uses linux-image-extra
    - LP: #1021174
  * rebase to v3.5-rc6

  [ Bryan Wu ]

  * [Config] built-in CONFIG_MICREL_PHY as other PHY drivers for all
    flavours
  * [Config] sync CONFIG_MOUSE_PS2_ config for all flavours

  [ Leann Ogasawara ]

  * [Config] Enable CONFIG_RT2800USB_RT35XX and CONFIG_RT2800USB_RT53XX
    - LP: #1019561

  [ Paolo Pisati ]

  * [Config] SND_OMAP_SOC, SND_OMAP_SOC_MCBSP and SND_OMAP_SOC_OMAP3_BEAGLE =y
    - LP: #1019321

  [ Stefan Bader ]

  * SAUCE: (pre-up) net: dont use __netdev_alloc_skb for bounce buffer
    - LP: #1018456
  * (config) Disable ACPI_PROCFS_POWER

  [ Tim Gardner ]

  * [Config] CONFIG_ACPI_BGRT=y
  * Extract firmware module info during getabi
    - LP: #1021174

  [ Upstream Kernel Changes ]

  * rebase to v3.5-rc6
 -- Leann Ogasawara <email address hidden> Mon, 09 Jul 2012 08:50:20 -0700

Changed in linux (Ubuntu Quantal):
status: Fix Committed → Fix Released
description: updated
description: updated
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :
Tim Gardner (timg-tpi)
Changed in linux (Ubuntu Precise):
status: In Progress → Fix Committed
Revision history for this message
Thomas M Steenholdt (tmus) wrote :

When will a kernel with this fix be released? Pending that, is there somewhere to download a "daily" kernel package for Precise?

Revision history for this message
Tim Gardner (timg-tpi) wrote :
Revision history for this message
Luis Henriques (henrix) wrote :

This bug is awaiting verification that the kernel for Precise in -proposed solves the problem (3.2.0-29.46). Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-precise' to 'verification-done-precise'.

If verification is not done by one week from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-precise
Revision history for this message
Fabien Lusseau (fabien-beosfrance) wrote :

I tested it and it's working ! Thanks !

tags: added: verification-done-precise verification-needed-precise-collected
removed: verification-needed-precise
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (16.5 KiB)

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

---------------
linux (3.2.0-29.46) precise-proposed; urgency=low

  [ Tim Gardner ]

  * No change upload to fix armel/armhf FTBS caused by
    'UBUNTU: [Config] SND_OMAP_SOC, SND_OMAP_SOC_MCBSP and SND_OMAP_SOC_OMAP3_BEAGLE =y'
    Added ignore and ignore.module files to ABI directories.

  [Luis Henriques]

  * Release Tracking Bug
    - LP: #1029507

linux (3.2.0-29.45) precise-proposed; urgency=low

  [Luis Henriques]

  * Release Tracking Bug
    - LP: #1029507

  [ Andy Whitcroft ]

  * SAUCE: rds_ib_send() -- prevent local pings triggering BUG_ON()
    - LP: #1016299
    - CVE-2012-2372

  [ Upstream Kernel Changes ]

  * Revert "samsung-laptop: make the dmi check less strict"
    - LP: #1029431
  * samsung-laptop: make the dmi check less strict
    - LP: #1029431
  * raid5: delayed stripe fix
    - LP: #1029431
  * tcp: drop SYN+FIN messages
    - LP: #1029431
  * tg3: Apply short DMA frag workaround to 5906
    - LP: #1029431
  * rtl8187: ->brightness_set can not sleep
    - LP: #1029431
  * net/wireless: ipw2x00: add supported cipher suites to wiphy
    initialization
    - LP: #1029431
  * kbuild: do not check for ancient modutils tools
    - LP: #1029431
  * brcmsmac: "INTERMEDIATE but not AMPDU" only when tracing
    - LP: #1029431
  * ext4: Report max_batch_time option correctly
    - LP: #1029431
  * NFSv4: Reduce the footprint of the idmapper
    - LP: #1029431
  * NFSv4: Further reduce the footprint of the idmapper
    - LP: #1029431
  * macvtap: zerocopy: fix offset calculation when building skb
    - LP: #1029431
  * macvtap: zerocopy: fix truesize underestimation
    - LP: #1029431
  * macvtap: zerocopy: put page when fail to get all requested user pages
    - LP: #1029431
  * macvtap: zerocopy: set SKBTX_DEV_ZEROCOPY only when skb is built
    successfully
    - LP: #1029431
  * macvtap: zerocopy: validate vectors before building skb
    - LP: #1029431
  * KVM: Fix buffer overflow in kvm_set_irq()
    - LP: #1029431
  * scsi: Silence unnecessary warnings about ioctl to partition
    - LP: #1029431
  * iommu/amd: Fix missing iommu_shutdown initialization in passthrough
    mode
    - LP: #1029431
  * iommu/amd: Initialize dma_ops for hotplug and sriov devices
    - LP: #1029431
  * usb: Add support for root hub port status CAS
    - LP: #1029431
  * gpiolib: wm8994: Pay attention to the value set when enabling as output
    - LP: #1029431
  * sched/nohz: Rewrite and fix load-avg computation -- again
    - LP: #1029431
  * USB: option: add ZTE MF60
    - LP: #1029431
  * USB: option: Add MEDIATEK product ids
    - LP: #1029431
  * USB: cdc-wdm: fix lockup on error in wdm_read
    - LP: #1029431
  * mtd: nandsim: don't open code a do_div helper
    - LP: #1029431
  * dvb-core: Release semaphore on error path dvb_register_device()
    - LP: #1029431
  * hwspinlock/core: use global ID to register hwspinlocks on multiple
    devices
    - LP: #1029431
  * libsas: fix taskfile corruption in sas_ata_qc_fill_rtf
    - LP: #1029431
  * md/raid1: fix use-after-free bug in RAID1 data-check code.
    - LP: #1029431
  * PCI: EHCI: fix crash during suspend on ASUS computers
    - L...

Changed in linux (Ubuntu Precise):
status: Fix Committed → Fix Released
Revision history for this message
Adam Conrad (adconrad) wrote : Update Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.