[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

2018-11-29 Thread Ian Ozsvald
I have posted my 1TB (PM951) issue as a new bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for

[Bug 1805816] ProcEnviron.txt

2018-11-29 Thread Ian Ozsvald
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1805816/+attachment/5217299/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805816

[Bug 1805816] Re: APST quirk needed for PM951 Samsung 1TB NVMe Drive

2018-11-29 Thread Ian Ozsvald
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816/+attachment/5217297/+files/lspci-vnvn.log ** Tags added: apport-collected tara ** Description changed: This is a fresh posted connected to a very similar now-solved bug ("APST quirk needed

[Bug 1805816] [NEW] APST quirk needed for PM951 Samsung 1TB NVMe Drive

2018-11-29 Thread Ian Ozsvald
Public bug reported: This is a fresh posted connected to a very similar now-solved bug ("APST quirk needed for Samsung 512GB NVMe drive"): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 My NVMe is the less-common 1TB version. It exhibits similar (possibly identical) behaviour but ha

[Bug 1805816] ProcCpuinfoMinimal.txt

2018-11-29 Thread Ian Ozsvald
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1805816/+attachment/5217298/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/

[Bug 1805816] ProcEnviron.txt

2018-11-29 Thread Ian Ozsvald
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1805816/+attachment/5217334/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805816

[Bug 1805816] Re: APST quirk needed for PM951 Samsung 1TB NVMe Drive

2018-11-29 Thread Ian Ozsvald
apport information ** Description changed: This is a fresh posted connected to a very similar now-solved bug ("APST quirk needed for Samsung 512GB NVMe drive"): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 My NVMe is the less-common 1TB version. It exhibits similar (pos

[Bug 1805816] Re: APST quirk needed for PM951 Samsung 1TB NVMe Drive

2018-11-29 Thread Ian Ozsvald
Sorry - I've hit a hiccup. `apport` wants me to file extra information (as uploaded above, twice) but upon running at the command line it notes: ` It appears you are currently running a mainline kernel. It would be better to report this bug upstream at http://bugzilla.kernel.org/ so that the ups

[Bug 1805816] Re: APST quirk needed for PM951 Samsung 1TB NVMe Drive

2018-11-29 Thread Ian Ozsvald
Oops - I can mark this issue as "New" but not "Complete" (which in turn was me mis-reading the instruction from the bot in #4). Sorry for the noise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/180581

[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

2018-11-20 Thread Ian Ozsvald
I'd like to follow-up on this bug - it affects me using kernel 4.19.0 on a Dell XPS 9550 with a 1TB Samsung drive. Details below. Do I need to open a new bug as I've got a 1TB drive and this bug report was opened for a 512GB drive? $ uname -a Linux ian-XPS-15-9550 4.19.0-041900-generic #2018102218

[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

2018-11-20 Thread Ian Ozsvald
To follow-up. Earlier today I fresh-booted and didn't use the APST disable command - my machine crashed out with read-only errors after minutes. I then updated grub to use `nvme_core.default_ps_max_latency_us=250` as suggested - it was stable for 6 hours, through 2 suspends. A little while ago it

[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

2018-11-21 Thread Ian Ozsvald
Hi Kai-Heng, thanks! Overnight I've used `nvme_core.default_ps_max_latency_us=0` in GRUB with no read-only crashes (everything has been smooth). I left the machine awake all night, I've since suspended & awoken it twice, all seems to be ok. As expected all APSTE is disabled: ` $ sudo nvme get-fea

[Bug 1805816] Re: APST quirk needed for PM951 Samsung 1TB NVMe Drive

2019-05-27 Thread Ian Ozsvald
Thanks for following up - we can close this bug, I no longer have this issue. I have attached info just for the record. I upgraded my system BIOS and the problems went away. $ sudo nvme id-ctrl /dev/nvme0 [sudo] password for ian: NVME Identify Controller: vid : 0x144d ssvid : 0x144d

[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

2018-12-18 Thread Ian Ozsvald
Hello Yingfag - can I check please - was it a 1TB Samsung SSD? Which model of SSD (950? 960? 970? something else?). When you changed the SSD - did you keep the same model? What was your final solution? Regards, Ian. -- You received this bug notification because you are a member of Ubuntu Bugs, wh

[Bug 1297049] Re: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia]

2015-07-10 Thread Ian Ozsvald
Further note - when I made comment #4 I was using the NVIDIA driver 331.113 and kernel 3.13.0-24. I've just updated from Mint 17.1 to Mint 17.2 (with a new nvidia driver and kernel), I'll try suspend & hibernate over the coming days and report back. -- You received this bug notification because y

[Bug 1297049] Re: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia]

2015-06-18 Thread Ian Ozsvald
** This bug is no longer a duplicate of bug 1275621 [Hewlett-Packard HP Pavilion dv6 Notebook PC] suspend/resume failure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297049 Title: [Dell Inc. La

[Bug 1297049] Re: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia]

2015-06-18 Thread Ian Ozsvald
Note I removed the duplicate link (to #1275621) as the other link doesn't mention NVIDIA and it isn't a Dell machine, I suspect that the NVIDIA chipset is the problem. For the 4 years I've owned my E6420 I've failed to get reliable suspend/hibernate behaviour, I always turn the laptop off when I w

[Bug 1297049] Re: [Dell Inc. Latitude E6420] suspend/resume failure [non-free: nvidia]

2015-06-22 Thread Ian Ozsvald
Further notes - the A19 bios was from approx June 2013, there is an A21 bios released in 2014 but the few fixes don't seem relevant. I would *very much* like to have a way of getting some sort of kernel log dump after a failure on the next boot, so I can even diagnose if it is failing the same way

[Bug 1311257] Re: Wifi cannot connect or unstable after suspend 14.04

2014-11-26 Thread Ian Ozsvald
In reference to Milton's comments (and thanks for the follow-ups) - my problems (listed in #11) are *not* related to a post-suspend loss of wifi. My problems happen consistently on a fresh boot. Frankly my E6420 can be 'wobbly' after suspend (it has been since 10.10) so I rarely suspend (it can fa

[Bug 1303079] Re: refresh rate value is not saved

2014-11-26 Thread Ian Ozsvald
I'm seeing this on 14.04 (Linux mint 17), 64 bit. I can't help but remember that I've seen this bug over the years. Two scenarios: 1) Edit|Preferences, Resources tab, Update interval is shown as "0.00", you can adjust it, Close, then if you go back it'll be marked as "0.00" (although the update

[Bug 1311257] Re: Wifi cannot connect or unstable after suspend 14.04

2014-11-18 Thread Ian Ozsvald
I'll mirror the above reports, I'm using a Intel Corporation Centrino Advanced-N 6205 on Linux Mint 17 (Ubuntu 14.04 Trusty), I recently upgraded from 12.04 Linux Mint 16 (Ubuntu 13.04 Saucy) using a complete clean reinstall and now the problem manifests. On Mint 16 (13.04) I had *no* wifi problem

[Bug 760142] Re: Several Ubuntu-certified Dell laptops: ImPS/2 ALPS GlidePoint configure as PS/2 mouse instead of proper touchpad

2011-12-15 Thread Ian Ozsvald
*** This bug is a duplicate of bug 606238 *** https://bugs.launchpad.net/bugs/606238 Agreeing with #83 - on my Dell E6420 with 11.10 (Linux Mint 12 with NVS4200M) I just downloaded and installed the .deb from #81, rebooted and then I saw the Touchpad tab in Mouse and Settings - two finger scro

[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510 and others

2011-12-15 Thread Ian Ozsvald
Echoing #88 - on that thread comment #81 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/760142/comments/81 links back to #78, I downloaded and installed the .deb via #81, rebooted and now I have the Touchpad settings in Ubuntu 11.10 (Linux Mint 12) on my Dell E6420. -- You received this b

[Bug 893597] Re: Phantom batteries are reported on Dell E6420

2011-12-27 Thread Ian Ozsvald
Additionally - after un-suspending and seeing 2 or 3 batteries, if I run Power Statistics (this is a Mint package that reports batter/AC statistics) it shows the 2 or 3 batteries. After 20 seconds if I close and re-open Power Statistics it will only show 1 battery. If I then restart Gnome (using:

[Bug 893597] Re: Phantom batteries are reported on Dell E6420

2011-12-27 Thread Ian Ozsvald
I'll report a similar problem. I'm using Linux Mint 12 (based on Ubuntu 11.10) with the default Gnome 3 interface. On approximately every 3rd to 5th wake-up from suspend (using the default pm-suspend) the system reports not 1 battery but 2 or 3 with the extra 1 or 2 having 0 charge. This used to c

[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510

2011-08-08 Thread Ian Ozsvald
*** This bug is a duplicate of bug 550625 *** https://bugs.launchpad.net/bugs/550625 In reply to Philip Aston's comment #41 I have a slightly tweaked KeyboardDetector.py script which catches two OSError exceptions (numbers 4 and 24) which cause the script to die quickly on my E6420. The fixe

[Bug 893597] Re: Phantom batteries are reported on Dell E6420

2012-02-07 Thread Ian Ozsvald
It looks like this bug is a duplicate and it is now fixed: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/852406 along with the fix message at #44 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/852406/comments/44 which requires kernel 3.0.0-14.23 (I'm on 3.0.0-12-generic so will have to