[Bug 1388559] Re: failed command: WRITE FPDMA QUEUED

2017-12-14 Thread Kai-Heng Feng
Lorenzo, Can you file a new bug? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1388559 Title: failed command: WRITE FPDMA QUEUED To manage notifications about this bug go to:

[Bug 1388559] Re: failed command: WRITE FPDMA QUEUED

2017-12-13 Thread Lorenzo Delana
I got same problem using latest 4.15rc-3 ec 13 20:57:59 bigone kernel: [ 23.575115] ata10.00: status: { DRDY } Dec 13 20:57:59 bigone kernel: [ 23.577829] ata10.00: failed command: WRITE FPDMA QUEUED Dec 13 20:57:59 bigone kernel: [ 23.580536] ata10.00: cmd

[Bug 1388559] Re: failed command: WRITE FPDMA QUEUED

2015-01-07 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1388559

[Bug 1388559] Re: failed command: WRITE FPDMA QUEUED

2014-11-08 Thread Sapsa
I will be having to switch probably to other distro. btw, if its irrelevant so why theres 2rc (one names utopic othere named vivid) I have been reading here that this bug is more than 2 years old now... probably will stick to distro that support it better Thanks for your replays. Oh, the

[Bug 1388559] Re: failed command: WRITE FPDMA QUEUED

2014-11-04 Thread Sapsa
There is no 3.18-rc3 for utopic. I dont know if it was before because I allways used debian those are kernels avaiable and no utopic rc3 there: [DIR] v3.18-rc3-vivid/03-Nov-2014 00:16 - [DIR] v3.18-rc2-vivid/28-Oct-2014 22:28 - [DIR]

[Bug 1388559] Re: failed command: WRITE FPDMA QUEUED

2014-11-04 Thread Christopher M. Penalver
Sapsa, the names of each kernel are irrelevant for the purposes of testing in a given release. ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1388559] Re: failed command: WRITE FPDMA QUEUED

2014-11-03 Thread Sapsa
uname -a Linux AKIRA 3.18.0-031800rc1-generic #201410192135 SMP Mon Oct 20 01:37:04 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux used this kernel rc1: linux-image-3.18.0-031800rc1-generic_3.18.0-031800rc1.201410192135_amd64.deb booted without problems [ 92.215824] ata7.00: exception Emask 0x10

[Bug 1388559] Re: failed command: WRITE FPDMA QUEUED

2014-11-03 Thread Christopher M. Penalver
Sapsa, did this problem not occur in a release prior to Utopic? As well, could you please test the latest mainline kernel 3.18-rc3 and advise to the results? ** Tags added: latest-bios-2102 ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug

[Bug 1388559] Re: failed command: WRITE FPDMA QUEUED

2014-11-02 Thread Christopher M. Penalver
Sapsa, is there any notable performance impact? As well, did this problem not occur in a release prior to Utopic? Also, could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following

[Bug 1388559] Re: failed command: WRITE FPDMA QUEUED

2014-11-02 Thread Sapsa
About inpact, screen freezee. Im watching twitch on XBMC, copying data from one disk to another (the disk affected is the system disk not the one that im coping to/from) and screen freezee (black screen or frame stop) but the audio is streaming ok, I cant do anything beside go to terminal (for

[Bug 1388559] Re: failed command: WRITE FPDMA QUEUED

2014-11-02 Thread Sapsa
Not sure about how to edit my post But before I install I got error from dmesg about potential corupting of system files, because its bad mounted droping in performence is big from 200 to 80 MB/s (acording to mc) Im using WD Black HDD, not SSD. To make this happend I jiust copy files from

[Bug 1388559] Re: failed command: WRITE FPDMA QUEUED

2014-11-02 Thread Christopher M. Penalver
Sapsa, if you can't boot, then it's not considered kernel-bug-exists- upstream. Despite this, could you please test 3.18-rc1 and advise if this allows a testing environment? ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Tags removed: kernel-bug-exists-upstream-3.18-rc2