Linux commit 97dec564fd4948e0e560869c80b76e166ca2a83e breaks communication with XYRATEX

Bug #1189928 reported by Jack Hill on 2013-06-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Confirmed
Medium
linux (Ubuntu)
Medium
Joseph Salisbury
Precise
Medium
Joseph Salisbury
Saucy
Medium
Joseph Salisbury

Bug Description

When I upgraded my machine from Lucid to Precise, I ran into upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=59601

I am filing this bug here so tha you are aware of the problem and any fix in the hope that it can be backported to precise.

Thank you.

Brad Figg (brad-figg) on 2013-06-11
affects: linux-meta (Ubuntu) → linux (Ubuntu)

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

apport-collect 1189928

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
tags: added: precise
tags: added: bot-stop-nagging
Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Joseph Salisbury (jsalisbury) wrote :

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 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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

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

Jack Hill (jackhill) wrote :

I tested the mainline kernel. The most recent commit that I tested was e8193ce572f0ddb8004acf976bba119f0abbe6ca which is after 3.10-rc4.

I'm not sure how to add a tag. Can you add the kernel-bug-exists-upstream tag?

Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Joseph Salisbury (jsalisbury) wrote :

I created a test kernel with commit 97dec564fd4948e0e560869c80b76e166ca2a83e. reverted. The test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1189928/

Can you test that kernel and post back if it still exhibits this bug?

Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Jack Hill (jackhill) wrote :

Joseph,

That kernel unfortunatly still exhibits this bug.

I have attached the dmesg output with extended error reporting enabled for the qla2xxx driver.

Best,
Jack

Jack Hill (jackhill) wrote :

Upstream has proposed a patch <https://bugzilla.kernel.org/show_bug.cgi?id=59601#c9> which seems to fix the problem for me.

Best,
Jack

Joseph Salisbury (jsalisbury) wrote :

Thanks for the update, Jack. Do you know if that patch will be sent upstream for inclusion in the mainline kernel?

Jack Hill (jackhill) wrote :

Joseph,

The patch has now been submitted to upstream:

http://marc.info/?l=linux-scsi&m=137365649318663&w=2

Best,
Jack

tags: added: cherry-pick needs-kernel-logs regression-release
Jack Hill (jackhill) wrote :

Greg KH has applied the patch to the 3.10, 3.4 and 3.0 trees. I'm not sure why it wasn't applied to the 3.2 tree, but I'm not that familiar with kernel development.

Message-ID:
<email address hidden>
<email address hidden>
<email address hidden>

--Jack

Jack Hill (jackhill) wrote :

I just heard back from Greg and he says that the 3.2 branch is maintained by someone else and the patch will probably be added to that in time.

--Jack

Joseph Salisbury (jsalisbury) wrote :

Correct, the 3.2 branch is maintained by Ben Hutchings. Precise will get this patch through the usual stable update process, once it is applied to the upstream 3.2 tree.

Changed in linux (Ubuntu Precise):
importance: Undecided → Medium
status: New → Triaged
Joseph Salisbury (jsalisbury) wrote :

I'll also build a Precise test kernel with this commit, to confirm it fixes this bug for you. If it does, I can submit a SRU request for Precise. That way Precise will have the fix instead of waiting for it from upstream.

Joseph Salisbury (jsalisbury) wrote :

A Precise test kernel is available with commit c3ccb1d applied.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1189928/

Can you test this kernel and post back if it resolves this bug?

Changed in linux (Ubuntu Precise):
status: Triaged → In Progress
assignee: nobody → Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Joseph Salisbury (jsalisbury)
Jack Hill (jackhill) wrote :

Joseph,

I can confirm that your kernel resolves this bug.

Best,
Jack

Joseph Salisbury (jsalisbury) wrote :

It looks like the fix was picked up upstream for 3.2.50:

commit f6c02a04b0409f2b55fa79f0bba7307434a22c83
Author: Saurav Kashyap <email address hidden>
Date: Fri Jul 12 14:47:51 2013 -0400

    qla2xxx: Properly set the tagging for commands.

git describe --contains f6c02a0
v3.2.50~18

However, I'll submit an SRU to have this fix in Precise until it gets all the 3.2.50 updates.

Tim Gardner (timg-tpi) on 2013-08-20
Changed in linux (Ubuntu Precise):
status: In Progress → Fix Committed
Changed in linux (Ubuntu):
status: In Progress → Fix Released
Brad Figg (brad-figg) wrote :

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

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
Jack Hill (jackhill) wrote :

I have tested the kernel from -proposed, and it does indeed solve the bug. Thanks!

tags: added: verification-done-precise
removed: verification-needed-precise
Launchpad Janitor (janitor) wrote :
Download full text (13.1 KiB)

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

---------------
linux (3.2.0-53.81) precise; urgency=low

  [ Tim Gardner ]

  * SAUCE: net: ifb: Added include file <linux/sched.h>

linux (3.2.0-53.80) precise; urgency=low

  [Brad Figg]

  * Release Tracking Bug
    - LP: #1215173

  [ Andy Whitcroft ]

  * [Packaging] supply perf with appropriate prefix to ensure use of local
    config
    - LP: #1206200
    - CVE-2013-1060

  [ Joseph Salisbury ]

  * SAUCE: (no-up) intel_ips: blacklist ASUSTek G60JX laptops
    - LP: #1210848

  [ Tim Gardner ]

  * [Config] Include rbd and kvm in the virtual inclusion list
    - LP: #1206961

  [ Upstream Kernel Changes ]

  * qla2xxx: Properly set the tagging for commands.
    - LP: #1189928
  * r8169: fix offloaded tx checksum for small packets.
    - LP: #1214984
  * printk: Fix rq->lock vs logbuf_lock unlock lock inversion
    - LP: #1214984
  * zfcp: fix adapter (re)open recovery while link to SAN is down
    - LP: #1214984
  * zfcp: block queue limits with data router
    - LP: #1214984
  * zfcp: status read buffers on first adapter open with link down
    - LP: #1214984
  * ahci: Add AMD CZ SATA device ID
    - LP: #1214984
  * i2c-piix4: Add AMD CZ SMBus device ID
    - LP: #1214984
  * zram: avoid invalid memory access in zram_exit()
    - LP: #1214984
  * zram: use zram->lock to protect zram_free_page() in swap free notify
    path
    - LP: #1214984
  * zram: destroy all devices on error recovery path in zram_init()
    - LP: #1214984
  * zram: avoid access beyond the zram device
    - LP: #1214984
  * zram: protect sysfs handler from invalid memory access
    - LP: #1214984
  * ahci: remove pmp link online check in FBS EH
    - LP: #1214984
  * usb: gadget: f_mass_storage: add missing memory barrier for
    thread_wakeup_needed
    - LP: #1214984
  * libata: skip SRST for all SIMG [34]7x port-multipliers
    - LP: #1214984
  * b43: ensue that BCMA is "y" when B43 is "y"
    - LP: #1214984
  * ath9k_hw: Assign default xlna config for AR9485
    - LP: #1214984
  * ath9k: fill channel mode in caldata
    - LP: #1214984
  * ath9k: Fix noisefloor calibration
    - LP: #1214984
  * ath9k: Do not assign noise for NULL caldata
    - LP: #1214984
  * Bluetooth: Fix crash in l2cap_build_cmd() with small MTU
    - LP: #1214984
  * ASoC: wm8962: Remove remaining direct register cache accesses
    - LP: #1214984
  * rtlwifi: rtl8192cu: Add new USB ID for TP-Link TL-WN8200ND
    - LP: #1214984
  * ALSA: hda - Cache the MUX selection for generic HDMI
    - LP: #1214984
  * xhci: check for failed dma pool allocation
    - LP: #1214984
  * drivers: hv: switch to use mb() instead of smp_mb()
    - LP: #1214984
  * media: dmxdev: remove dvb_ringbuffer_flush() on writer side
    - LP: #1214984
  * rtlwifi: rtl8192cu: Fix duplicate if test
    - LP: #1214984
  * hw_breakpoint: Use cpu_possible_mask in {reserve,release}_bp_slot()
    - LP: #1214984
  * ata_piix: IDE-mode SATA patch for Intel Coleto Creek DeviceIDs
    - LP: #1214984
  * ahci: AHCI-mode SATA patch for Intel Coleto Creek DeviceIDs
    - LP: #1214984
  * iommu/amd: Only unmap large pages from the first pte
    - LP: #1214984
  * ARM: 7765/1: ...

Changed in linux (Ubuntu Precise):
status: Fix Committed → Fix Released
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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