[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED

2017-07-04 Thread xenus
Upgraded to Ubuntu 17.04 = Linux 4.10.x Problem has gone away. I'm assuming the 4.10 queueing changes have fixed the issue. -- 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/1682892 Title:

[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED

2017-06-29 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 Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED

2017-04-30 Thread xenus
Now using: 4.8.0-49-generic #52-Ubuntu SMP Thu Apr 20 09:38:39 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux related to heavy disc load, typically an rsync running as part of backup. But the sda drive is the only one that generates the errors, sdb and sdc that actually have the backup files don't

[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED

2017-04-26 Thread xenus
Tried the kernel above, unfortunately dkms fails trying to add nvidia module so I can't get it running. Attaching dkms 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/1682892 Title:

[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED

2017-04-26 Thread xenus
** Attachment added: "dkms log for kerel 3.11 and nvidia 378" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682892/+attachment/4868342/+files/make.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED

2017-04-18 Thread xenus
This has only started happening recently, so I'm trying -45 and -41 to see if it goes away partly because I need to use this machine but also to see if I can identify when the problem was introduced. Is the 4.11 r7 reasonably stable? I don't want to lose any data (even with backups) as it's a

[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED

2017-04-18 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 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

[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED

2017-04-17 Thread xenus
Kernel param set but still seeing the issue: Apr 15 10:08:58 mark-linux kernel: [3.467285] ata3.00: FORCE: horkage modified (noncq) Apr 15 10:08:58 mark-linux kernel: [3.467531] ata3.00: ATA-9: ST2000DX001-1CM164, CC43, max UDMA/133 Apr 15 10:08:58 mark-linux kernel: [3.467532]

[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED

2017-04-15 Thread xenus
Kernel param set but still seeing the issue: Apr 15 10:08:58 mark-linux kernel: [3.467285] ata3.00: FORCE: horkage modified (noncq) Apr 15 10:08:58 mark-linux kernel: [3.467531] ata3.00: ATA-9: ST2000DX001-1CM164, CC43, max UDMA/133 Apr 15 10:08:58 mark-linux kernel: [3.467532]