Hi,
I had the same problem with a K800 Keyboard from Logitech.
a better way would be to edit the file
/etc/initramfs-tools/modules
and add
hid-logitech-hidpp
there.
Then it is sufficiant to to
sudo update-initramfs -c -k $(uname -r)
for the running kernel (or -k all for all kernels).
Hi,
on Ubuntu 14.04 according to this thread:
* http://askubuntu.com/questions/125367/enabling-mic-mute-button-and-
light-on-lenovo-thinkpads
I cannot see
/sys/devices/platform/thinkpad_acpi/leds/tpacpi::micmute/brightness as a
link in /sys/devices/platform/thinkpad_acpi/leds:
# ls
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
[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
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
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
##
DIARY since Wed, 15 Jan 2014
-
Please see the attached log of this post for the last 6 days.
##
CONCLUSION (mainline kernel)
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
Duplicate bug?
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/984127
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1269777
Title:
[ Ubuntu 14.04 - Lenovo W510 - SSD Samsung
** Summary changed:
- [ 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
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Summary changed:
- [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only
Filesystem
+ [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 PRO] Sudden Read-Only
Filesystem
** Description changed:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.13.0-031300rc8-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1269777
Title:
[ Ubuntu 14.04 - Lenovo W510
** Tags removed: needs-upstream-testing
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1269777
Title:
[ 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
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
Public bug reported:
Like mentioned in bug #1266305 (and before in bug #1265309) the
following problem occured:
1. System
--
- Ubuntu 14 04 LTS (acutal development branch)
-
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950025/+files/dmesg.log
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: uname-a.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950028/+files/uname-a.log
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: lspci-vvnn.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950027/+files/lspci-vvnn.log
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: lsb_release-rd.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950026/+files/lsb_release-rd.log
--
You received this bug notification because you
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: BIOS Mode Compat 2 - SATA
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950030/+files/20140116_45.jpg
--
You received this bug notification
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: BIOS Mode Compat 2 - POWER
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950031/+files/20140116_28.jpg
** Changed in: linux (Ubuntu)
Status:
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
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
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Attachment added: dmesg_egrep_ata_scsi_BOOT.jpg
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950081/+files/dmesg_egrep_ata_scsi_BOOT.jpg
--
You received this bug
*** This bug is a duplicate of bug 1266305 ***
https://bugs.launchpad.net/bugs/1266305
** Summary changed:
- [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only
Filesystems
+ [ Ubuntu 14.04 - Lenovo W510 - SSD Samsung 840 EVO PRO] Sudden Read-Only
Filesystem
--
You
** Description changed:
+ 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
** Description changed:
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
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?
** Attachment added: hdparm -I /dev/sda
** Attachment added: dmesg_egrep_ata_scsi_BOOT.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950214/+files/dmesg_egrep_ata_scsi_BOOT.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950215/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1269777
** Attachment added: hdparm-I.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950213/+files/hdparm-I.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: uname-a.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950234/+files/uname-a.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Sorry the last dmesg.log was the wrong for this bios settings ...
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950227/+files/dmesg.log
** Attachment removed: dmesg_egrep_ata_scsi_BOOT.log
** Attachment added: ls_proc.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950235/+files/ls_proc.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: proc_scsi_scsi.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950240/+files/proc_scsi_scsi.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: proc_modules.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950239/+files/proc_modules.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: proc_ioports.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950238/+files/proc_ioports.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: usr_src_3.13.0-031300rc8-generic_scripts_ver_linux
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950241/+files/usr_src_3.13.0-031300rc8-generic_scripts_ver_linux
--
You received this bug notification because you are a member of Kernel
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'
Running the mainline kernel for 3 hours now. PCI(e) powermanagement is
enabled and SATA is working in AHCI mode. This caused the standard
kernel 3.13.0-3-generic
##
DATE: Thu, 16 Jan 2014 22:31:11 +0100
UPTIME: 22:31:11 up 2:58, 4
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).
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950407/+files/dmesg.log
--
You received this bug
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
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
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
** Attachment added: dmesg_egrep_ata_scsi_BOOT.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950612/+files/dmesg_egrep_ata_scsi_BOOT.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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
** Attachment added: proc_modules.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950623/+files/proc_modules.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: proc_ioports.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950616/+files/proc_ioports.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950611/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1269777
##
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
The /etc/default/tlp for sake of completeness ;-)
** Attachment added: /etc/default/tlp
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950651/+files/tlp
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Attachment removed: /etc/default/tlp
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950651/+files/tlp
** Attachment added: tlp-stat.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269777/+attachment/3950663/+files/tlp-stat.log
--
You received this
Hi, unfortunately my enthusiasm was a little bit too big.
Yesterday I got a freeze again, but this time a little time after wakeup
from standby.
- I tried then the kernel 3.12.7-031207-generic (which is the last trusty
kernel for the 3.12 line).
- I uninstalled tlp ro minimize side effects.
-
Please give me a few days of doing a clear testing plan about this.
** Description changed:
After a while of running the system, the SSD goes into a readonly file
system mode.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-15-generic 3.11.0-15.23
** Attachment added: 20140115_09-00_dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266305/+attachment/3949128/+files/20140115_09-00_dmesg.txt
** Changed in: linux (Ubuntu)
Status: Invalid = Incomplete
--
You received this bug notification because you are a member of
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1266305/+attachment/3949130/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: 20140115_09-00_dmesg_error_grep_ata.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1266305/+attachment/3949127/+files/20140115_09-00_dmesg_error_grep_ata.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Unfortunately the lttng-modules for the kernel 3.13 are not installable.
Any advise for another tool to trap kernel messages?
https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1267652
--
You received this bug notification because you are a member of Kernel
Packages, which is
Thanks Christopher for your advice.
Yes the firmware of the Samsung EVO 840 was updated to the latest one
(last firmware Dec.' 13) with the Samsung Magician software. I checked
the update twice after a reboot.
I have to add: the new replacement drive is an exact 1:1 copy of the
SSD, and shows no
A few hours ago I got a new Samsung EVO 840 Pro. I made a clone of the
actual system.
I booted up, stress tested the system (4GB file video conversion while running
a virtual machine, ...).
It runs for 3 hours now. Not any single problem so far.
MY PERSONAL CONCLUSION:
DON'T USE THE SAMSUNG EVO
Hi Christopher, thank you for the explanations.
I returned the EVO 840 and got the EVO 840 Pro instead from my local reseller.
So I cannot test any more into the subject.
I learned a lot about filing bugs in ubuntu, so this was very interesting.
Thank you for your advise so far.
I found another
Due to the fact, that the drive was returned but was OK (tested in
another system), I marked the bug Opinion so that it is closed.
** Changed in: linux (Ubuntu)
Status: Incomplete = Opinion
--
You received this bug notification because you are a member of Kernel
Packages, which is
apport information
** Attachment added: AlsaInfo.txt
https://bugs.launchpad.net/bugs/1266305/+attachment/3946973/+files/AlsaInfo.txt
** Tags removed: needs-upstream-testing
** Tags added: needs-upstream-testing-3.13.0-1.16
--
You received this bug notification because you are a member of
Today I made a backup of the drive to another 500GB disk since the
problem occured during the last days after a certain time of beeing up
with the pc.
Today:
1. I updated the Samsung EVO's firmware the the one from october 13th 2013.
2. I dist-upgraded to kernel 3.13.0-1.16 on Ubuntu 12.04
~$
Thanks Christopher for your answer.
I could not test the upstream kernel due to massive problems with the nvidia
card.
And I first wanted to the test the standard distribution - as advised.
Sorry for the wrong tagging this way ..
Nevertheless: tomorrow I try to return the drive, because it
System freezes with above kernel ...
But when I try to investigate, I cannot use the machine for debugging
because the system is in a read-only state.
I need some help to investigate the problem:
How can I trigger the kernel event ata1.00: status: { DRDY } to run
a script (e.g. sende me an
Hi,.
I am now testing with a fresh install ob Ubuntu 14.04 LTS.
Yesterday evening I installed a new system.
(Since I had problems getting nvidia and mainline kernel to run, I
decided to got this way).
I wrote a little script, that sends me an mail with dmesg output, if the
system goes into
kernel 3.12.0-1-generic (AMD 64)
Twice today I recognized a freeze.
BUT:
* the system becomes stable again after a while
* ata1 will be reset
* system becomes unstable (eth0 network, wlan still works)
You can see some message, that come from a service, that every minute
tries to touch and
Given kernel was wrong:
linux-image-3.13.0-1-generic3.13.0-1.16
Collection apport informations at the moment ...
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.13.0-1.16
--
You received this bug notification because you are a member of Kernel
Hi.
I completely reinstalled a fresh system of Ubuntu 11.10
- encrypted partition (LVM)
- TRIM support (based weekly on cron)
I encounter the same problems, booting grub either normal command line
or libata.force=noncq libata.noacpi=1. Due to the fact, that my
machine uses a 6G SATA device,
You are welcome, Christopher.
But the more I think about this, I tend that this is a problem between
machine bios and the ssd.
I will investigate further.
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Reports are here: bug #1266305
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1265309
Title:
[Lenovo W510 - SSD Samsung EVO] Sudden Read-Only Filesystems
Status in “linux” package in
Public bug reported:
This is the next step in the bug mentioned here:
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265309
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-15-generic 3.11.0-15.23
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname:
Hi there: Lenovo W510, Ubuntu 12.04 LTS, SSD
In my last comment I hoped, the problem was solved
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/comments/123).
Unfortunately it is not. Yeterday morning my filesystem was readonly
again.
So I am going to remove now all noatime, all
** Attachment added: 20140101-BUG-1265309-ubuntu-bug-report.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265309/+attachment/3938581/+files/20140101-BUG-1265309-ubuntu-bug-report.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
-
Data from the machine: Lenovo W510 TYPE 4391-E46
-
dmidecode -s bios-version sudo dmidecode -s bios-release-date
6NET84WW (1.45 )
10/03/2012
This is the newest available BIOS for this machine.
lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/1265309/+attachment/3938587/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected running-unity
** Description changed:
After a while of running the system, the SSD goes into a readonly file system
mode. I am running Ubuntu 12.04 LTS linux-image-generic-lts-saucy, lvm2 in a
version that supports trim and are encrypted on
apport information
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/1265309/+attachment/3938583/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.launchpad.net/bugs/1265309/+attachment/3938586/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1265309/+attachment/3938585/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Christopher, thank you for your answer. I know about this
But i don't have the https://launchpad.net/~brightbox/+archive/experimental -
ppa installed.
I removed all system relevant ppa repositories especially for lvm2.
The ppa's which are enabled on the sytem are only updates for user
[Problem probably solved]
I changed my fstab and removed the defaults-entry:
Probably this was the problem and the defaults-entry puts some mount options,
that interfere with the ssd.
fatab-NEW: /dev/mapper/vg--myvg-root /ext4noatime,errors=remount-ro 0
1
fstab-OLD:
Unfortunetely with the settings from above i was not lucky this morning.
When I turned on the W510 notebook (#3.) it stuck like before. I really
think, this is system specific for this laptop, because the other
computers with itdentical software are running flawlessly ... 24/7 (via
suspend /
Hi there,
I am running Ubuntu 12.04 LTS on three machines:
1. An intel xeon with an asus motherboard, 32GB RAM, SSD (SAMSUNG older model)
2. An Lenovo Thinkpad 201s i7, 8GB RAM, SSD (Crucial)
3. An Lenovo Thinkpad W510 i7 720, 8GB RAM, SSD (Samsung EVO)
All systems are running under kernel 3.11
83 matches
Mail list logo
