[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-Only Filesystem

Bug #1269777 reported by Axel Pospischil
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Low
Unassigned

Bug Description

++++++++++++++++++++++++++++++++++++++++++++++++++++
[UPDATE 05th March 2014]

The lenovo service was here and changed the mainboard.
No problems any more with a Crucial M500 480 GB and therefore
I think witch any other SSD on the W510.

So the problem turned out a real hardware problem.
The lenovo diagnostic cd however did not turn out any problem.
So to make a long story short: If you encounter any problems like in
this thread, don't heasitate to contact the lenovo service and insist for
a repair. In my case, I had to contact the service twice because I am using
hardware that is not part of the supported lenovo device list.

++++++++++++++++++++++++++++++++++++++++++++++++++++

Like mentioned in bug #1266305 (and before in bug #1265309) the following problem occured:

1. System
--------------------------

- Ubuntu 14 04 LTS (acutal development branch)
- linux-image-generic v. 3.13.x, mainline kernel 3.13.x (first testing the standard kernel), last 3.12 mainline kernel
- lvm with trim support (batched discard)
- tlp (currently disabled for testing purpose)

2. Hardware:
---------------------------
- Lenovo W510 i7 quad core
- SSD Samsung 840 Pro (former Samsung 840 EVO, was changed in hope that the problem disapears)
- nvidia graphics

BIOS (defaults F9) and:

- BIOS Mode Standard 1: SATA: AHCI, POWER: pci and pcie power management AUTOMATIC
- BIOS Mode Standard 2: SATA: AHCI, POWER: pci and pcie power management OFF

- BIOS Mode Compat 1: SATA: Compatability Mode, POWER: pci and pcie power management AUTOMATIC
- BIOS Mode Compat 2: SATA: Compatability Mode, POWER: pci and pcie power management OFF

3. Problem descripton
-----------------------------------------------

The SSD randomly freezes with the following errors:
ata1: EH complete
ata1: limiting SATA link speed to 1.5 Gbps
ata1.00: exception Emask 0x52 SAct 0x1 SErr 0x1a80d00 action 0x6 frozen
ata1.00: irq_stat 0x08000000, interface fatal error
ata1: SError: { UnrecovData Proto HostInt 10B8B BadCRC LinkSeq TrStaTrns }
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:00:d8:b9:27/00:00:05:00:00/40 tag 0 ncq 4096 in
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Probably affect other Thinkpad models too:

- http://www.sevenforums.com/bsod-help-support/309288-bsod-after-few-minutes-5-55-minutes-samsung-ssd-840-evo.html
- [GERMAN] http://thinkpad-forum.de/threads/168841-Freezes-nach-Einbau-einer-neuen-SSD?p=1698795#post1698795
- http://www.howtoeverything.net/linux/hardware/ubuntu-freeze-issue-after-ssd-upgrade

4. Troubleshooting so far
------------------------------------------------
4.1. Kernel boot parameters:

libata.force=1:3.0G,2:1,5G libata.force=noncq

-> not working. DRDY, hard restting link.

4.2. BIOS Mode Compat 2 (Compat, PCI powermangement OFF), no additional kernel boot parameters.

System ran with standard generic kernel 3.13.x for over 12 hours usage without any problems.
I did some suspend/ resume cycles: no problems.

5. Further testing:
--------------------------------------------------------
Testing scenarios will be applied in the follwowing structure (if necessary)

5.1 Testing the standard trusty kernel (linux-image-generic)
5.1.1. with all BIOS modes.
5.1.2. eventually kernel boot parameters

5.2. Testing the latest mainline kernel with all BIOS modes.
5.2.1. with all BIOS modes.
5.2.2. eventually kernel boot parameters

This could take a few days, so be patient.

Keeping fingers crossed ;-)

P.S-.: Thanks a lot for Christopher M. Penalver for his excellent assistance so far!

######################################################################

Wed, 15 Jan 2014 18:00:00 +0100

- installed mainline kernel 3.13.0-031300rc8-generic
- BIOS:
      SATA: Compatibility,
      POWER: pci / pcie power management OFF (!)
- no tlp

No problems until the next day (switched POWER management for pci and pcie on)

######################################################################

Thu, 16 Jan 2014 13:18:45 +0100

- installed linux-image-generic -> 3.13.0-3-generic
- BIOS:
      SATA: AHCI,
      POWER: pci/pcie power management AUTOMATIC
- Reboot with new standard kernel
- no tlp yet!

######################################################################

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-generic 3.13.0.3.6
ProcVersionSignature: Ubuntu 3.13.0-3.18-generic 3.13.0-rc8
Uname: Linux 3.13.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: apos 3069 F.... pulseaudio
 /dev/snd/controlC0: apos 3069 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Jan 16 12:35:13 2014
HibernationDevice: RESUME=UUID=7290992b-11df-4d5c-a9bc-579dafe5eb61
InstallationDate: Installed on 2014-01-08 (7 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140105)
MachineType: LENOVO 4391E46
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-3-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-3-generic N/A
 linux-backports-modules-3.13.0-3-generic N/A
 linux-firmware 1.121
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/03/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6NET84WW (1.45 )
dmi.board.name: 4391E46
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4391E46:pvrThinkPadW510:rvnLENOVO:rn4391E46:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4391E46
dmi.product.version: ThinkPad W510
dmi.sys.vendor: LENOVO

Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Revision history for this message
Axel Pospischil (apos) wrote : Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystems
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Axel Pospischil (apos) wrote :
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Axel Pospischil (apos) wrote :

####################################################################

Thu, 16 Jan 2014 13:18:45 +0100
- installed linux-image-generic -> 3.13.0-3-generic
- BIOS: switched AHCI, and pci/pcie power management on
- Reboot with new kernel
- no tlp yet!

Thu, 16 Jan 2014 13:28:13 +0100
Doing a supend/resume cylce ...

After some seconds:
System is going to slow down a little bit and shows the following messages

dmesg | grep ata1
Jan 16 13:22:18 madagaskar kernel: [ 3053.312643] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 16 13:22:18 madagaskar kernel: [ 3053.313348] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Jan 16 13:22:18 madagaskar kernel: [ 3053.313350] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Jan 16 13:22:18 madagaskar kernel: [ 3053.313352] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Jan 16 13:22:18 madagaskar kernel: [ 3053.313599] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
Jan 16 13:22:18 madagaskar kernel: [ 3053.473847] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Jan 16 13:22:18 madagaskar kernel: [ 3053.473853] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Jan 16 13:22:18 madagaskar kernel: [ 3053.473855] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out

>> Jan 16 13:22:18 madagaskar kernel: [ 3053.474168] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1

Jan 16 13:22:18 madagaskar kernel: [ 3053.474251] ata1.00: configured for UDMA/133

####################################################################
Thu, 16 Jan 2014 14:41:29 +0100

Hard resetting link and readonly filesystem

dmesg | egrep "ata|scsi|BOOT" see attached picture

####################################################################

Rebootig with BIOS Mode Standard and Kernel 3.13.0-3-generic.

Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Axel Pospischil (apos)
summary: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only
- Filesystems
+ Filesystem
Revision history for this message
penalvch (penalvch) wrote : Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only Filesystem

Axel Pospischil, could you please execute the following at a terminal, and post the results:
sudo hdparm -I /dev/sda

description: updated
Changed in linux (Ubuntu):
importance: Undecided → Low
tags: added: latest-bios-1.45 needs-upstream-testing regression-potential
Axel Pospischil (apos)
description: updated
Axel Pospischil (apos)
description: updated
description: updated
description: updated
Revision history for this message
Axel Pospischil (apos) wrote :

Hi Christopher,

I am now still in AHCI mode with PCI(e) powermanagement off in bios.
The system is absolutely stable.

hdparm -I /dev/sda attached

Do you need this with PCI(e) powermanagement enabled?

penalvch (penalvch)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Axel Pospischil (apos) wrote :

######################################################################

Thu, 16 Jan 2014 19:08:54 +0100

- Booting now with last mainline kernel linux-image-generic
  3.13.0-031300rc8-generic #201401120535 SMP Sun Jan 12 10:36:21 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

- BIOS:
      SATA: AHCI,
      POWER: pci/pcie power management AUTOMATIC

- no tlp

######################################################################

Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :

Sorry the last dmesg.log was the wrong for this bios settings ...

Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Download full text (4.1 KiB)

Running the mainline kernel for 3 hours now.

PCI(e) powermanagement is enabled and SATA is working in AHCI mode.
Started virtualbox, worked a lot with the system, ... no problems occured ...

Under the same conditions, the standard kernel 3.13.0-3-generic caused the system to freeze.

I' investigate further and keep the system running ...

##############################################################
DATE: Thu, 16 Jan 2014 22:31:11 +0100
UPTIME: 22:31:11 up 2:58, 4 users, load average: 0,13, 0,29, 0,27
STATUS: dmesg | egrep ata|scsi|BOOT
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-031300rc8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
[ 0.000000] BIOS-e820: [mem 0x00000000c3f7a000-0x00000000c3f7cfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000c3f81000-0x00000000c3f81fff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000c3f8b000-0x00000000c3f8bfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000c3f9f000-0x00000000c3ffefff] ACPI data
[ 0.000000] ACPI: BOOT 00000000c3ffefd8 000028 (v01 LENOVO TP-6N 00001450 LTP 00000001)
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-031300rc8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
[ 0.000000] Memory: 8076940K/8318476K available (7476K kernel code, 1128K rwdata, 3500K rodata, 1344K init, 1436K bss, 241536K reserved)
[ 0.532393] ACPI : EC: GPE = 0x11, I/O: command/status = 0x66, data = 0x62
[ 0.532809] libata version 3.00 loaded.
[ 1.563008] Write protecting the kernel read-only data: 12288k
[ 1.666129] scsi0 : ahci
[ 1.666590] scsi1 : ahci
[ 1.667004] scsi2 : ahci
[ 1.667416] scsi3 : ahci
[ 1.667756] scsi4 : ahci
[ 1.668144] scsi5 : ahci
[ 1.668269] ata1: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627100 irq 53
[ 1.668280] ata2: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627180 irq 53
[ 1.668283] ata3: DUMMY
[ 1.668286] ata4: DUMMY
[ 1.668295] ata5: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627300 irq 53
[ 1.668304] ata6: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627380 irq 53
[ 1.985559] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.986404] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 1.986407] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 1.986410] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 1.986936] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 1.986943] ata1.00: ATA-9: Samsung SSD 840 PRO Series, DXM05B0Q, max UDMA/133
[ 1.986948] ata1.00: 1000215216 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 1.988299] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 1.988308] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 1.988315] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 1.988803] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 1.988995] ata1.00: configured for UDMA/133
[ 1.989365] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 840 DXM0 PQ: 0 ANSI: 5
[ 1.989628] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 2.309623] ata2: SATA li...

Read more...

Revision history for this message
Axel Pospischil (apos) wrote :
Download full text (31.0 KiB)

As time of writing, the error occured!

#############################################################
DATE: Thu, 16 Jan 2014 22:31:11 +0100
UPTIME: 22:31:11 up 2:58, 4 users, load average: 0,13, 0,29, 0,27
STATUS: dmesg | egrep ata|scsi|BOOT
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-031300rc8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
[ 0.000000] BIOS-e820: [mem 0x00000000c3f7a000-0x00000000c3f7cfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000c3f81000-0x00000000c3f81fff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000c3f8b000-0x00000000c3f8bfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000c3f9f000-0x00000000c3ffefff] ACPI data
[ 0.000000] ACPI: BOOT 00000000c3ffefd8 000028 (v01 LENOVO TP-6N 00001450 LTP 00000001)
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-031300rc8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
[ 0.000000] Memory: 8076940K/8318476K available (7476K kernel code, 1128K rwdata, 3500K rodata, 1344K init, 1436K bss, 241536K reserved)
[ 0.532393] ACPI : EC: GPE = 0x11, I/O: command/status = 0x66, data = 0x62
[ 0.532809] libata version 3.00 loaded.
[ 1.563008] Write protecting the kernel read-only data: 12288k
[ 1.666129] scsi0 : ahci
[ 1.666590] scsi1 : ahci
[ 1.667004] scsi2 : ahci
[ 1.667416] scsi3 : ahci
[ 1.667756] scsi4 : ahci
[ 1.668144] scsi5 : ahci
[ 1.668269] ata1: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627100 irq 53
[ 1.668280] ata2: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627180 irq 53
[ 1.668283] ata3: DUMMY
[ 1.668286] ata4: DUMMY
[ 1.668295] ata5: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627300 irq 53
[ 1.668304] ata6: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627380 irq 53
[ 1.985559] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.986404] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 1.986407] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 1.986410] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 1.986936] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 1.986943] ata1.00: ATA-9: Samsung SSD 840 PRO Series, DXM05B0Q, max UDMA/133
[ 1.986948] ata1.00: 1000215216 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 1.988299] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 1.988308] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 1.988315] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 1.988803] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 1.988995] ata1.00: configured for UDMA/133
[ 1.989365] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 840 DXM0 PQ: 0 ANSI: 5
[ 1.989628] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 2.309623] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.312424] ata2.00: ACPI cmd e3/00:1f:00:00:00:a0 (IDLE) succeeded
[ 2.312714] ata2.00: ACPI cmd e3/00:02:00:00:00:a0 (IDLE) succeeded
[ 2.314314] ata2.00: ATAPI: HL-DT-STDVDRAM GT33N, LT20, max UDMA/66
[ 2.317168] ata2.00: ACPI cmd e3/00:1f:00:00:00...

Revision history for this message
Axel Pospischil (apos) wrote :

What I did was taking the PC from the docking station, switch of LAN and switch on WLAN.

Started a program to whatch TV (mythfrontend).

Revision history for this message
Axel Pospischil (apos) wrote :

Booting now the mainline kernel.

BIOS: turned powermanagement for PCI to AUTOMATIC, for PCIE (!) to Disable

######################################################################

Thu, 16 Jan 2014 22:43:27 +0100

- Booting now with last mainline kernel linux-image-generic
  3.13.0-031300rc8-generic #201401120535 SMP Sun Jan 12 10:36:21 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

- BIOS:
      SATA: AHCI,
      POWER: PCI AUTOMATIC
                         PCIE power management DISABLE

- no tlp

Revision history for this message
Axel Pospischil (apos) wrote :

ANALYTICS:
-------------------

If you look at comment #31 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/comments/31), you will notice in dmesg.log (which I could safe at runntime to /tmp and copy it over to another pc), that the freeze occurs right after taking the system from the series 3 docking station.

[10053.907277] thinkpad_acpi: undocked from hotplug port replicator
[10894.439599] ata2.00: exception Emask 0x40 SAct 0x0 SErr 0x880800 action 0x6 frozen
[10894.439610] ata2: SError: { HostInt 10B8B LinkSeq }
[10894.439618] sr 1:0:0:0: CDB:
[...]

According to an article about docking solutions in Think-Wiki, this might be a problem with the hotplugging of this device and newer kernel series:
* http://www.thinkwiki.org/wiki/Docking_Solutions#Newer_series_3_docks
* http://phihag.de/2012/thinkpad-docking.html

I am investigating in this!

Revision history for this message
Axel Pospischil (apos) wrote :

I rebooted with the paramters of comment #33 ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/comments/33). PCIE powermanagement is DISABLED in the BIOS.

Then I did the undocking operation:
It is working like expected without any problem!

[ 1866.096092] thinkpad_acpi: undocked from hotplug port replicator
[ 1866.816786] thinkpad_acpi: undocked from hotplug port replicator
[ 1868.539250] thinkpad_acpi: undocked from hotplug port replicator
[ 1869.262918] thinkpad_acpi: undocked from hotplug port replicator
[ 1871.740846] usb 1-1.5: new high-speed USB device number 5 using ehci-pci
[ 1871.837436] usb 1-1.5: New USB device found, idVendor=17ef, idProduct=100a
[ 1871.837446] usb 1-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1871.838073] hub 1-1.5:1.0: USB hub found
[ 1871.838218] hub 1-1.5:1.0: 6 ports detected
[ 1872.205253] e1000e 0000:00:19.0: irq 54 for MSI/MSI-X
[ 1872.237244] thinkpad_acpi: docked into hotplug port replicator
[ 1875.306042] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 1875.306084] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1886.197392] wlan0: deauthenticating from 00:15:0c:25:3a:20 by local choice (reason=3)
[ 1886.209324] cfg80211: Calling CRDA to update world regulatory domain
[ 1886.213833] cfg80211: World regulatory domain updated:
[ 1886.213838] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1886.213840] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1886.213843] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1886.213845] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 1886.213847] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1886.213849] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 2278.442035] usb 1-1.5: USB disconnect, device number 5
[ 2278.715642] e1000e: eth0 NIC Link is Down
[ 2279.131886] thinkpad_acpi: undocked from hotplug port replicator
[ 2463.374118] usb 1-1.5: new high-speed USB device number 6 using ehci-pci
[ 2463.466471] usb 1-1.5: New USB device found, idVendor=17ef, idProduct=100a
[ 2463.466483] usb 1-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2463.467060] hub 1-1.5:1.0: USB hub found
[ 2463.467211] hub 1-1.5:1.0: 6 ports detected
[ 2463.814673] e1000e 0000:00:19.0: irq 54 for MSI/MSI-X
[ 2463.838596] thinkpad_acpi: docked into hotplug port replicator

I will try this again, after the system worked a few hours, e.g. tomorrow morning.

Revision history for this message
Axel Pospischil (apos) wrote :

Yesterday evening I applied the Thinkpad dock / undock scripts from comment #34 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/comments/34).

I also installed tlp, which cares mainly for network interface switching upon dock / undock evnets (see config attached).

I rebooted the pc with the mainline kernel and switched the BIOS powermanagement on:

- BIOS:
      SATA: AHCI,
      POWER: PCI AUTOMATIC
      PCIE power management AUTOMATIC

A couple of docking / undocking, suspend / resumes, hibernates which worked right away.
The computer was running the whole night.

When I analysed the syslog this mornning, there occured some hard resettings of the ata2 device (dvd) within the night:

 - The DVD cannot mount any devices.
 - Network interface eth0 is dead
 - Ata1 is living (SSD).

But I think it is just a matter of time, when the SSD becomes unavailable.

- Suspend / resume

Worked, but did not change anything.

- Eject of the ultrabay (which I do with this script: http://www.thinkwiki.org/wiki/How_to_hotswap_Ultrabay_devices#Script_for_Ultrabay_eject)

This brought back
- the ata2 device
- AND the network interface as well.

Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :

##############################################################
DATE: Fri, 17 Jan 2014 08:14:35 +0100
UPTIME: 08:14:35 up 6:21, 3 users, load average: 0,18, 0,70, 0,88
KERNEL: 3.13.0-031300rc8-generic #201401120535 SMP Sun Jan 12 10:36:21 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

##############################################################
CONCLUSION SO FAR:
------------------------------------

1. Applying the Thinkpad dock / undock scripts from comment #34 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/comments/34) seems to make the system more robust.

2. Eject of the ultrabay (which I do with this script from comment #36: http://www.thinkwiki.org/wiki/How_to_hotswap_Ultrabay_devices#Script_for_Ultrabay_eject) brings back the ata2 device (DVD) and eth0

3. Booting the machine with

- BIOS:
      SATA: AHCI,
      POWER: PCI AUTOMATIC
      ->> POWER: PCIE power management OFF /DISABLED

seams to solve the problems and lead to a stable system.

4. Booting the machine with

- BIOS:
      SATA: AHCI,
      POWER: PCI AUTOMATIC
      -->> POWER: PCIE power management AUTOMATIC (!!!)

leads to an unstable system. Hard resetting links occur, when the machine is idle, not on dock / undock events any more (undock script comment #36)

So folks ... what now?

Revision history for this message
Axel Pospischil (apos) wrote :
Axel Pospischil (apos)
summary: - [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only
+ [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
Filesystem
description: updated
Axel Pospischil (apos)
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.13.0-031300rc8-generic
Axel Pospischil (apos)
tags: removed: needs-upstream-testing
Revision history for this message
Axel Pospischil (apos) wrote : Re: [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only Filesystem

############################
Fri, 17 Jan 2014 12:54:39 +0100

hard link reset ata1 -> readonly filesystem

=> Booting now with PCI-Express powermanagement disabled in BIOS !

Some comments:

############################
NCQ
-------------

When I am diving into the subject, I see this NCQ kernel error appear

[ 2.184511] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2.185682] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 2.185685] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 2.185688] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 2.186097] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 2.186104] ata1.00: ATA-9: Samsung SSD 840 PRO Series, DXM05B0Q, max UDMA/133
[ 2.186109] ata1.00: 1000215216 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 2.187422] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 2.187432] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 2.187438] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out

-> [ 2.187860] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1

[ 2.188017] ata1.00: configured for UDMA/133

There is a good article about NCQ here. According to this it is no good idea to disable this within the kernel command line:

* http://blog.disksurvey.org/blog/2013/10/28/ncq-disabled

###########################
SATA and PCIE Power Management
-----------------------------------------------------

In gentoo forums I found an article with this error caused by LAPTOP MODE:

* http://forums.gentoo.org/viewtopic-t-980628.html?sid=7b7a7aadcd0e124cafc3f54a07049799

For my system I get:

$ for no in 0 1 2 3 4 5; do echo -n "host${no}: "; cat /sys/class/scsi_host/host${no}/link_power_management_policy ; done
host0: max_performance
host1: max_performance
host2: max_performance
host3: max_performance
host4: max_performance
host5: max_performance

With tlp I can alter this by the following settings int /etc/default/tlp (this are my actual settings):

[...]

# SATA aggressive link power management (ALPM):
# min_power/medium_power/max_performance
SATA_LINKPWR_ON_AC=max_performance
SATA_LINKPWR_ON_BAT=min_power

# PCI Express Active State Power Management (PCIe ASPM):
# default/performance/powersave
# Hint: needs kernel boot option pcie_aspm=force on some machines
PCIE_ASPM_ON_AC=performance
PCIE_ASPM_ON_BAT=powersave

[...]

Probably altering these settings will solve the problem?

Revision history for this message
Axel Pospischil (apos) wrote :
Download full text (4.0 KiB)

##########################################################

DIARY since Wed, 15 Jan 2014
-----------------------------------------
Please see the attached log of this post for the last 6 days.

##########################################################
CONCLUSION (mainline kernel)
----------------------------
Wed, 22 Jan 2014 10:58:57 +0100
 10:58:57 up 23:45, 4 users, load average: 0,11, 0,12, 0,19

Finally got quite stable system with some error remaining.

A. What DID "solve" the problem:
----------------------------------

1. Disabling the POWER: PCIe / PCI powermanagementin the bios.
I seemed to work, but did not in the end. After a while a hard reset occured and the system freezed.

That's why additional tasks are necessary:

2. The usage of the tlp package seams to force PCIe powermangement, at least with my settings (see formerly attached files).
Since freezes also occured with ubuntu 12.04, it should not be a problem with the tlp package itself, but the machine.
Removing tlp seems to work.

3. Additionally disabling PCIe powermanagement by adding the boot parameter libata.noacpi=1 seams to be crucial.

4. Adding "options libata noacpi=1" in "/etc/modprobe.conf" is also crucial for getting a stable system after supsend or resume.

5. I also applied the Thinkpad dock / undock scripts from comment #34 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/comments/34).
Without this, I enountered various problems when docking / undocking the machine.

B. What did NOT solve the problem:
-------------------------------

1. Using a different SSD (Samsung 840 Pro instead of 840 EVO) is not the point.
The same problems did occur with both type of hardware.

2. Using the mainline, the standard or an older kernel lead to the same problems.

3. Adding the libata.noncq=1 kernel option is not necessay and not advised due to performance (see comment #44)
Nevertheless: the error messages in dmesg "failed to get NCQ Send/Recv Log Emask 0x1" remain.

4. Using the SATA/Compatibility mode in bios.

5. I also applied the kernel parameters "libata.force=1:3.0Gbps,2:1,5Gbps,2:80c modprobe.blacklist=pata_acpi" which lead to the same results: ata1 was limited to 1,5 Gbps after a while.
Also created an /etc/modprobe.conf with this content: "options libata noacpi=1 force=1:3.0Gbps,2:1.5Gbps,2:40c"

C. What causes still problems:
-------------------------------

1. Hibernation: seams to force upcoming of hard resets. In the end this forces the kernel to set the ata1 device to a limit of 1,5 Gbps (when libata.noacpi=1 is applied)

2. After a while ata1 is limited to 1,5 Gbps.

2. Setting modprobe.conf and kernel parameters is far from perfect.

D. FURTHER TESTING
-------------------

1. Apply the SSD of another Tinkpad (X201 / Samsung EVO 830) to this machine for testing purpose.
Just to see if this is really a problem with the Samsung 840 series SSD.

2. Test "safe" settings the Trusty mainline kernel.

3. Talking to the maintainer of the tlp package - this might solve interferences with PCIe powermangement.

4. Testing a normal harddisk with PCIe on, without libata kernel boot options and tlp and see if it works.

Please be patient, this could tak...

Read more...

Revision history for this message
Axel Pospischil (apos) wrote :

DIARY since Wed, 15 Jan 2014
--------------------------------------------

Revision history for this message
Axel Pospischil (apos) wrote :

dmesg since 2014-01-21 with

/etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash libata.noacpi=1 libata.force=1:3.0Gbps,2:1,5Gbps,2:40c modprobe.blacklist=pata_acpi "

/etc/modprobe.d/blacklist-pata_acpi.conf
blacklist pata_acpi

/etc/modprobe.conf
options libata noacpi=1 force=1:3.0Gbps,2:1.5Gbps

Revision history for this message
Axel Pospischil (apos) wrote :

dmesg for sytem running from 2014-01-19 to 2014-01-21

/etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash libata.noacpi=1"

/etc/modprobe.conf
options libata noacpi=1

Revision history for this message
Axel Pospischil (apos) wrote :
Revision history for this message
Axel Pospischil (apos) wrote :

I will test now a STANDARD HARDDRIVE CLONE known to work with

- mainline kernel
- tlp uninstalled / installed
- standard grub and bios settings

Please be patient for news.

I will report when all tests are done (except you have any suggestions).

Greets
Axel

Axel Pospischil (apos)
summary: - [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
- Filesystem
+ [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO 512GB] Sudden Read-
+ Only Filesystem
Revision history for this message
Axel Pospischil (apos) wrote :

################################################
Fri, 24 Jan 2014 08:54:15 +0100
 08:54:15 up 1 day, 20:49, 4 users, load average: 0,90, 2,21, 1,61

Hi again,

as said in comment #50, I put a clone of the SSD, Seagate Momentus XT Hypbrid into the laptop.
As you can see, the system is running without any problems: no NCQ warnings, no problems after supspend, hibernation, docking.
And this this tlp enabled and ACPI powermanagement in the bios.

I also tested the SSD in a Thinkpad X201 yesterday evening which has the the same chipset.
There I had exact the same problems!

I filed a question in lenovos forum and the answer is clear:
nothing but trouble with the Samsung 840 series with this Cipset!
People did not have trouble with the 830 series and capacities of 256 GB:

- http://forums.lenovo.com/t5/W-Series-ThinkPad-Laptops/W510-SSD-My-Story/td-p/1401955/highlight/false

The only drive which is guarantied by manufactor to run with the Thinkpad W510 with a capacity of more than 256GB (!) - there is none of this size in the hardware specifications mentioned by lenovo - is the crucial M500 480GB.

- http://www.crucial.com/store/mpartspecs.aspx?mtbpoid=AC617B31A5CA7304

#########################################################
CONCLUSION
----------------------

I have to return the Samsung 840 Pro 512 GB (as I did with the Samsung 840 EVO) and have to state that it is not compatible with the Thinkpad W510 and the Intel 5/3400 Chipset and the BIOS 6NET84WW (1.45 ) 10/03/2012.

All efforts to get things running stable where - in the end - not successfull.

Probably this bug report might help to fix things in future kernels or lenovo will fix this.
Sorry that I can't wait until this will happen ;-)

Cheers, over and out.
Closing bug.

Axel

Changed in linux (Ubuntu):
status: Confirmed → Opinion
Revision history for this message
Axel Pospischil (apos) wrote :

Hi,

[Crucial M500 - a hope? - NO]
-------------------------------------------

after returning the Samsung and found this thread in the lenovo forum:

http://forums.lenovo.com/t5/W-Series-ThinkPad-Laptops/W510-SSD-My-Story/m-p/1402387

my hope was the Crucial M500 should be compatible to the W510:

http://www.crucial.com/store/mpartspecs.aspx?mtbpoid=AC617B31A5CA7304

Unfortunately, I encounterd the very same problems like with the other SSD's.
The ata port hard resets and the SSD goes into read-only state after a certain amount of time.

More or less stable I could get things running with turning PCIe powermanagement off in the BIOS an using libata.force=noncq as kernel boot parameters. Nevertheless the system freezes from time to time.

I will open a new bug report for this drive as soon as the

[Contacting Lenovo support]
-------------------------------------------

The lenovo support stated, that only very special SSDs from Intel with a capacity of 160GB are compatible with this device.
So no help from lenovo.

[FURTHER TESTING]
-----------------------------

Since the fact, that an older drive, the Samsung 830 is running fine in a laptop (Lenovo X201, i7) with the same laptop, I tested all drives (Samsung 840 EVO, PRO and the Crucial M500 480) in the X201. Same problem there. So it IS DEFINITELY an incompatibility with the drive and the machine / chipset / kernel.

Within the next weeks, I will try an older Crucial M4 256GB in the W510.
This is an older drive model like the Samsung 830 and probably will work.

[OPINION]
---------------

Comming across certain threads, this problem is very common an occurs here and there with certain chipsets.
I don't think it is a problem of the linux kernel, but probably could be fixed?

I will post my results about the Crucial M4 and the problems with the Crucial M500 and link here.

Revision history for this message
Axel Pospischil (apos) wrote :

++++++++++++++++++++++++++++++++++++++++++++++++++++
[UPDATE 05th March 2014]

The lenovo service was here and changed the mainboard.
No problems any more with a Crucial M500 480 GB and therefore
I think witch any other SSD on the W510.

So the problem turned out a real hardware problem.
The lenovo diagnostic cd however did not turn out any problem.
So to make a long story short: If you encounter any problems like in
this thread, don't heasitate to contact the lenovo service and insist for
a repair. In my case, I had to contact the service twice because I am using
hardware that is not part of the supported lenovo device list.

++++++++++++++++++++++++++++++++++++++++++++++++++++

description: updated
Changed in linux (Ubuntu):
status: Opinion → Invalid
Revision history for this message
Mateusz Gryzzli (gryzzli) wrote :

This is a regression from kernel 3.12 and 3.13 onwards (i can't reproduce the 'failed to get NCQ Send/Recv Log Emask 0x1' in kernel 3.11 on samsung 840 ssd). I think those ncq changes upstream make some spotty ssd's firmware's go nuts, like samsung (which for example has ncq disabled for their macbook pcie-express ssd's). For the time being as a workaround you can either disable power saving on sata link, downgrade the kernel or disable ncq altogether. This has nothing to do with bios manufacturer afaik, because even disabling acpi or other aspm features still produces those errors. Maybe this has to be reopened, because that bug can cause data-loss in laptops (and pc's) and seems not to be vendor specific (i have an asus mobo for example).

Revision history for this message
Augusto Bortoluzzi (augusto-bortoluzzi) wrote :

I confirm I have a similar problem on Ubuntu 14.04 amd64 with similar hardware, the error is "failed to get NCQ Send/Recv Log Emask 0x1". In my case the disk is not available, it is not listed with lshw.

My HDD Model: ATA Samsung SSD 840 Series (250GB)
My sysboard is an Asus M3N78-EM, with updated BIOS.

Some details:
$ lspci -vvnn | grep -i sata
00:09.0 IDE interface [0101]: NVIDIA Corporation MCP78S [GeForce 8200] SATA Controller (non-AHCI mode) [10de:0ad0] (rev a2) (prog-if 85 [Master SecO PriO])

$ tail -n 2000 /var/log/syslog | grep -B 3 -A 1 -i samsung
Jul 6 16:38:08 user-pc kernel: [ 1.432094] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 6 16:38:08 user-pc kernel: [ 1.432109] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jul 6 16:38:08 user-pc kernel: [ 1.432638] ata4.00: failed to get NCQ Send/Recv Log Emask 0x1
Jul 6 16:38:08 user-pc kernel: [ 1.432641] ata4.00: ATA-9: Samsung SSD 840 Series, DXT06B0Q, max UDMA/133
Jul 6 16:38:08 user-pc kernel: [ 1.432643] ata4.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
--
Jul 6 17:27:05 user-pc kernel: [ 1.512031] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 6 17:27:05 user-pc kernel: [ 1.512051] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 6 17:27:05 user-pc kernel: [ 1.512798] ata4.00: failed to get NCQ Send/Recv Log Emask 0x1
Jul 6 17:27:05 user-pc kernel: [ 1.512801] ata4.00: ATA-9: Samsung SSD 840 Series, DXT06B0Q, max UDMA/133
Jul 6 17:27:05 user-pc kernel: [ 1.512804] ata4.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)

***I quickly test with Ubuntu 12.04 and the Bug wasn't present:
This is from lshw output with Ubuntu 12.04 amd64:

        *-disk:1
             description: ATA Disk
             product: Samsung SSD 840
             physical id: 1
             bus info: scsi@1:0.0.0
             logical name: /dev/sdb
             version: DXT0
             serial: S14GNEACA42011P
             size: 232GiB (250GB)
             capabilities: partitioned partitioned:dos
             configuration: ansiversion=5 signature=00048686
           *-volume:0
                description: Linux filesystem partition
                vendor: Linux
                physical id: 1
                bus info: scsi@1:0.0.0,1
                logical name: /dev/sdb1
                version: 1.0

Revision history for this message
Augusto Bortoluzzi (augusto-bortoluzzi) wrote :

I missed to mention that I also switched BIOS setting forcing AHCI mode, but the disk is not available.

$ dmesg | egrep "ata4"
[ 1.195248] ata4: SATA max UDMA/133 abar m8192@0xfcf76000 port 0xfcf76180 irq 40
[ 1.512031] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.512798] ata4.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 1.512801] ata4.00: ATA-9: Samsung SSD 840 Series, DXT06B0Q, max UDMA/133
[ 1.512804] ata4.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 6.512027] ata4.00: qc timeout (cmd 0x2f)
[ 6.512034] ata4.00: failed to get Identify Device Data, Emask 0x5
[ 6.512043] ata4.00: failed to set xfermode (err_mask=0x40)
[ 6.832022] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 6.832784] ata4.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 11.832036] ata4.00: qc timeout (cmd 0x2f)
[ 11.832043] ata4.00: failed to get Identify Device Data, Emask 0x5
[ 11.832054] ata4.00: failed to set xfermode (err_mask=0x40)
[ 11.832058] ata4: limiting SATA link speed to 1.5 Gbps
[ 11.832060] ata4.00: limiting speed to UDMA/133:PIO3
[ 12.152021] ata4: SATA link up <unknown> (SStatus 103 SControl 310)
[ 12.152182] ata4.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 17.152034] ata4.00: qc timeout (cmd 0x2f)
[ 17.152039] ata4.00: failed to get Identify Device Data, Emask 0x5
[ 17.152045] ata4.00: failed to set xfermode (err_mask=0x40)
[ 17.152047] ata4.00: disabled
[ 17.152057] ata4: hard resetting link
[ 17.472022] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 17.472027] ata4: EH complete

Revision history for this message
penalvch (penalvch) wrote :

Augusto Bortoluzzi, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Revision history for this message
Augusto Bortoluzzi (augusto-bortoluzzi) wrote :

Thanks Christopher, I filed a new bug as you suggested
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706

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.