Kernel oops during btrfs access

Bug #1247647 reported by Gregor Suhr
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

cat /proc/version_signature
Ubuntu 3.11.0-12.19-generic 3.11.3

root@ubuntunas:~# sudo lspci -vnvn
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02)
 Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000]
 Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
 Physical Slot: 1
 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] (prog-if 80 [Master])
 Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
 Physical Slot: 1
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
 Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
 Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
 Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
 Region 4: I/O ports at c160 [size=16]
 Kernel driver in use: ata_piix

00:01.2 USB controller [0c03]: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] [8086:7020] (rev 01) (prog-if 00 [UHCI])
 Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
 Physical Slot: 1
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin D routed to IRQ 11
 Region 4: I/O ports at c100 [size=32]
 Kernel driver in use: uhci_hcd

00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03)
 Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
 Physical Slot: 1
 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Interrupt: pin A routed to IRQ 9
 Kernel driver in use: piix4_smbus

00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc Device [1af4:1100]
 Physical Slot: 2
 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Region 0: Memory at fc000000 (32-bit, prefetchable) [size=32M]
 Region 1: Memory at febf0000 (32-bit, non-prefetchable) [size=4K]
 Expansion ROM at febd0000 [disabled] [size=64K]
 Kernel driver in use: cirrus

00:03.0 Ethernet controller [0200]: Red Hat, Inc Virtio network device [1af4:1000]
 Subsystem: Red Hat, Inc Device [1af4:0001]
 Physical Slot: 3
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 10
 Region 0: I/O ports at c120 [size=32]
 Region 1: Memory at febf1000 (32-bit, non-prefetchable) [size=4K]
 Expansion ROM at febe0000 [disabled] [size=64K]
 Capabilities: [40] MSI-X: Enable+ Count=3 Masked-
  Vector table: BAR=1 offset=00000000
  PBA: BAR=1 offset=00000800
 Kernel driver in use: virtio-pci

00:04.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block device [1af4:1001]
 Subsystem: Red Hat, Inc Device [1af4:0002]
 Physical Slot: 4
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 11
 Region 0: I/O ports at c000 [size=64]
 Region 1: Memory at febf2000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: [40] MSI-X: Enable+ Count=2 Masked-
  Vector table: BAR=1 offset=00000000
  PBA: BAR=1 offset=00000800
 Kernel driver in use: virtio-pci

00:05.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block device [1af4:1001]
 Subsystem: Red Hat, Inc Device [1af4:0002]
 Physical Slot: 5
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 10
 Region 0: I/O ports at c040 [size=64]
 Region 1: Memory at febf3000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: [40] MSI-X: Enable+ Count=2 Masked-
  Vector table: BAR=1 offset=00000000
  PBA: BAR=1 offset=00000800
 Kernel driver in use: virtio-pci

00:06.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block device [1af4:1001]
 Subsystem: Red Hat, Inc Device [1af4:0002]
 Physical Slot: 6
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 11
 Region 0: I/O ports at c080 [size=64]
 Region 1: Memory at febf4000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: [40] MSI-X: Enable+ Count=2 Masked-
  Vector table: BAR=1 offset=00000000
  PBA: BAR=1 offset=00000800
 Kernel driver in use: virtio-pci

00:07.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block device [1af4:1001]
 Subsystem: Red Hat, Inc Device [1af4:0002]
 Physical Slot: 7
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 10
 Region 0: I/O ports at c0c0 [size=64]
 Region 1: Memory at febf5000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: [40] MSI-X: Enable+ Count=2 Masked-
  Vector table: BAR=1 offset=00000000
  PBA: BAR=1 offset=00000800
 Kernel driver in use: virtio-pci

00:08.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon [1af4:1002]
 Subsystem: Red Hat, Inc Device [1af4:0005]
 Physical Slot: 8
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 11
 Region 0: I/O ports at c140 [size=32]
 Kernel driver in use: virtio-pci

00:09.0 System peripheral [0880]: Intel Corporation 6300ESB Watchdog Timer [8086:25ab]
 Subsystem: Red Hat, Inc Device [1af4:1100]
 Physical Slot: 9
 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Region 0: Memory at febf6000 (32-bit, non-prefetchable) [size=16]

root@ubuntunas:~#

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-12-generic 3.11.0-12.19
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Nov 3 20:23 seq
 crw-rw---- 1 root audio 116, 33 Nov 3 20:23 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Sun Nov 3 20:26:49 2013
HibernationDevice: RESUME=UUID=2447d766-b078-4ed0-87f3-c27412c10649
InstallationDate: Installed on 2011-02-03 (1003 days ago)
InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release amd64 (20101007)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Bochs Bochs
MarkForUpload: True
PciMultimedia:

ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=0dbf4328-2e66-42b3-88dd-b96a5c25b11d ro console=tty0 console=ttyS0,115200n8 crashkernel=384M-2G:64M,2G-:128M quiet
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-08-25 (70 days ago)
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs

Revision history for this message
Gregor Suhr (gresuh) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Revision history for this message
Gregor Suhr (gresuh) wrote :

Hi this problem started after the update 13.10 and 3.11.0-11.17-generic see report Bug #1235798.
The last working kernel was 3.11.0.7.9
Tell me if an can provide further debug info...

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

We can perform a kernel bisect to try and identify the commit that introduced this regression. Would you be able to install some test kernels on this machine?

Revision history for this message
Gregor Suhr (gresuh) wrote : Re: [Bug 1247647] Re: Kernel oops during btrfs access
Download full text (11.3 KiB)

I will try. Didn't do kernel tweaks for a long time.

Mit freundlichen Grüßen

Gregor Suhr

On Mon, Nov 4, 2013 at 9:20 PM, Joseph Salisbury <
<email address hidden>> wrote:

> We can perform a kernel bisect to try and identify the commit that
> introduced this regression. Would you be able to install some test
> kernels on this machine?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1247647
>
> Title:
> Kernel oops during btrfs access
>
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> cat /proc/version_signature
> Ubuntu 3.11.0-12.19-generic 3.11.3
>
>
> root@ubuntunas:~# sudo lspci -vnvn
> 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC
> [Natoma] [8086:1237] (rev 02)
> Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
> Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
>
> 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA
> [Natoma/Triton II] [8086:7000]
> Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
> Physical Slot: 1
> Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
>
> 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE
> [Natoma/Triton II] [8086:7010] (prog-if 80 [Master])
> Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
> Physical Slot: 1
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable)
> [size=8]
> Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable)
> [size=1]
> Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable)
> [size=8]
> Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable)
> [size=1]
> Region 4: I/O ports at c160 [size=16]
> Kernel driver in use: ata_piix
>
> 00:01.2 USB controller [0c03]: Intel Corporation 82371SB PIIX3 USB
> [Natoma/Triton II] [8086:7020] (rev 01) (prog-if 00 [UHCI])
> Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
> Physical Slot: 1
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin D routed to IRQ 11
> Region 4: I/O ports at c100 [size=32]
> Kernel driver in use: uhci_hcd
>
> 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI
> [8086:7113] (rev 03)
> Subsystem: Red Hat, Inc Qemu vir...

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

To start a bisect, we first need to identify the last good kernel version and first bad kernel version. Can you test the following two kernels:

v3.10 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-saucy/
v3.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/

They can be installed by installing the linux-image .deb package and rebooting.

tags: added: performing-bisect
Revision history for this message
Gregor Suhr (gresuh) wrote :
Download full text (25.2 KiB)

Strange, i get the same problem with both kernels.

Nov 5 08:12:31 ubuntunas kernel: [ 18.506379] ------------[ cut here ]------------
Nov 5 08:12:31 ubuntunas kernel: [ 18.507390] Kernel BUG at ffffffffa014f0d2 [verbose debug info unavailable]
Nov 5 08:12:31 ubuntunas kernel: [ 18.508754] invalid opcode: 0000 [#1] SMP
Nov 5 08:12:31 ubuntunas kernel: [ 18.509711] Modules linked in: dm_crypt kvm_intel kvm microcode psmouse serio_raw virtio_balloon i2c_piix4 mac_hid lp parport btrfs xor zlib_deflate raid6_pq libcrc32c cirrus syscopyarea sysfillrect sysimgblt ttm drm_kms_helper drm floppy
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] CPU: 0 PID: 611 Comm: btrfs-balance Not tainted 3.11.0-031100-generic #201309021735
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] task: ffff8800360d1770 ti: ffff8800b5a68000 task.ti: ffff8800b5a68000
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] RIP: 0010:[<ffffffffa014f0d2>] [<ffffffffa014f0d2>] build_backref_tree+0x282/0x1250 [btrfs]
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] RSP: 0018:ffff8800b5a69ab8 EFLAGS: 00010246
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] RAX: 0000000000000000 RBX: ffff8800b7bf8240 RCX: ffff8800b4c4f590
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] RDX: ffff8800b5a69b58 RSI: ffff8800b4c4f580 RDI: ffff88004d7a8280
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] RBP: ffff8800b5a69bb8 R08: ffff88004d7a8b80 R09: ffff88004d7a8b80
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] R10: 0000000000000001 R11: 0000000000000000 R12: ffff8800b4c4f590
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] R13: ffff88004d7a8580 R14: 0000000000000000 R15: ffff8800b3dfe800
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] FS: 0000000000000000(0000) GS:ffff8800bb200000(0000) knlGS:0000000000000000
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] CR2: 00007fef3c9972f0 CR3: 00000000b4d93000 CR4: 00000000000006f0
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] Stack:
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] 0000000000000000 ffff88004d7a8b80 ffff8800b4c4f060 ffff8800b3dfe920
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] ffff88003607a000 ffff88004d7a8380 ffff88004d7a83c0 ffff8800b7bf8240
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] ffff88004d7a8380 ffff8800b7bf8120 ffff8800b3dfe924 ffff8800b3dfe820
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] Call Trace:
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [<ffffffffa01501db>] relocate_tree_blocks+0x13b/0x1e0 [btrfs]
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [<ffffffffa0150d23>] relocate_block_group+0x193/0x570 [btrfs]
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [<ffffffffa01512b7>] btrfs_relocate_block_group+0x1b7/0x2f0 [btrfs]
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [<ffffffffa01293b6>] btrfs_relocate_chunk.isra.62+0x56/0x3e0 [btrfs]
Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [<ffffffffa00e4d80>] ? block_group_cache_tree_search+0xb0/0xf0 [btrfs]
Nov 5 08:12:31 ubuntunas kernel: [ ...

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Thanks for testing. The bug may have been introduced in 3.9 or maybe one of the 3.10 rc kernels. Can you test the following kernels:

v3.9 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-saucy/

v3.10-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc1-saucy/

v3.10-rc5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc5-saucy/

You don't have to test them all, just up until the first one that exhibits the bug.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.