Tested, the bug is present.
P.S Sorry for my bad english.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed patch for 3.13 (Trusty kernel)
** Attachment added: patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416702/+attachment/4321766/+files/patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Patch for Trusty kernel (3.13)
** Patch removed: Patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416702/+attachment/4309417/+files/patch
** Attachment added: patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416702/+attachment/4321767/+files/patch
--
You received
Public bug reported:
Hi all,
I have problem with my EMU 0404 USB. ALSA doesn't change sample rate frequency,
when I play songs with different sample rate. In process googling this bug I
found bugreport with patch —
http://mailman.alsa-project.org/pipermail/alsa-devel/2014-July/079103.html
I
** Description changed:
Hi all,
- I have problem with my EMU 0404 USB. ALSA doesn't change sample rate
frequency, when I play songs with different sample rate. In process googling
this bug I found bugreport with patch —
** Tags added: alsa kernel sound
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1416702
Title:
EMU 0404 USB automatic sample rate
To manage notifications about this bug go to:
** Description changed:
Hi all,
- I have a problem with my EMU 0404 USB. ALSA doesn't change sample rate
frequency when I play songs with different sample rate. While I was googling
for this bug I found bugreport with patch —
Through, script in OP doesn't work correctly.
fstrim: ./: FITRIM ioctl failed: input/output error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ
Samsung SSD 850 Pro, EXM02B6Q, Trusty with 3.13.0-55. There is no errors
in dmesg, multiple fstrim operatins runs just fine. Strange.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Seems Samsung fixed this bug in kernel
(https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f3f5da624e0a891c34d8cd513c57f1d9b0c7dadc)
and blacklist is no longer needed. Maybe we should remove blacklist and
apply this patch instead?
--
You received this bug notification
Or this patch fixes another trim bug... Then i'm sorry.
The queued TRIM issue with Samsung drives remains open but it has nothing
whatsoever to do with the Algolia bug.
http://techreport.com/news/28724/samsung-docs-detail-linux-trim-bug-and-fix
--
You received this bug notification because you
This patch from Samsung fixes trim bug in kernel.
1.
http://techreport.com/news/28674/samsung-says-data-eating-trim-bug-is-a-linux-kernel-problem
2. http://www.spinics.net/lists/raid/msg49440.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Dave Chiluk
No, I didn't. I have no that configuration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338706
Title:
Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
set
Seems 4.4.0-31 in 16.04 also affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603476
Title:
Boot failure with EFI stub
To manage notifications about this bug go to:
Will be fix release for 16.04 (4.4) kernel too?
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603476
Title:
Public bug reported:
After updating kernel to 3.13.0-92 system cannot startup with these errors:
Failed to get file info size
Failed to alloc highmem for files
I've found patch fixing it here —
http://kernel.opensuse.org/cgit/kernel/commit/?h=v3.15.9=396f1a08db212138418b38f784e4bbe516d2fdb2
Public bug reported:
I've found out that all my drives uses CFQ scheduler by default, since
that udev rule (60-ssd-scheduler.rules) for use CFQ for rotating disk is
useless. I heard that Ubuntu uses Deadline scheduler by default, but for
somewhat reason it's not that on my system.
ProblemType:
** Description changed:
I've found out that all my drives uses CFQ scheduler by default, since
- that udev rule (60-ssd-scheduler.rules) for use CFQ for rotating disk is
- useless. I heard that Ubuntu uses Deadline scheduler by default, but for
- somewhat reason it's not that on my system.
+
18 matches
Mail list logo
