*** This bug is a duplicate of bug 1305480 ***
https://bugs.launchpad.net/bugs/1305480
Hi
After yesterday's update the problem had gone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294729
*** This bug is a duplicate of bug 1305480 ***
https://bugs.launchpad.net/bugs/1305480
** This bug has been marked a duplicate of bug 1305480
BUG: pcmC0D0p:0, pos = 16390, buffer size = 16384, period size = 1024
--
You received this bug notification because you are a member of Ubuntu
I tested the 3.14 lowlatency and seems that this bug is fixed for me at
least. No more BUG info to kern.log and jackd is able to run just fine.
Using kernel:
3.14.0-031400-lowlatency #201403310035 SMP PREEMPT Mon Mar 31 04:44:05
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug
This vanished and then seems to have come back on the last ISO I tried. Looking
around at the log files in /var/log I can only find the line:
BUG: pcmC1D0c:0, pos = 5461, buffer size = 5461, period size = 2730
in kern.log and it only seems to happen right at boot, but the error reporter
seems to
This happens at login. It is something to do with the nvidia driver
(304.117) because when I switch to Nouveau the problem goes away. I can
reboot or logout/in and there is no problem.
I do not know if it is the nvidia driver itself, or something it
touches.
--
You received this bug
I tested both the cking and the 3.14 kernels but I am still getting the
messages .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294729
Title:
BUG: pcmC1D0c:0, pos = 5461, buffer size = 5461,
This appears it could be a duplicate of bug 1305480
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294729
Title:
BUG: pcmC1D0c:0, pos = 5461, buffer size = 5461, period size = 2730
To manage
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1294729
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, I was relying on the software center to install the kernels.
I tested now both kernels ( test kernel and 3.14 ) without any changes.
I tested the standard kernel.
Should I test the low latency one ?
I don't know what it involves.
--
You received this bug notification because you are a
Thanks for testing! You should only need to test the -generic kernel. So did
the kernel cking built, at the following link, resolve the bug:
http://kernel.ubuntu.com/~cking/lp-1294729/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I could not install the kernel mentioned in #12; it is telling me a newer
version is already installed. I don't know how to force it.
I could not install the 3.14 kernel either as I get a message that installation
failed.
Unfortunately, my other machine , that I use rarely, is in fact displaying
How are you attempting to install the test kernels? You should perform
the following from a terminal:
sudo dpkg -i linux-image-3.13.0-19-generic_3.13.0-19.39~lp1294729_amd64.deb
and
sudo dpkg -i
linux-image-extra-3.13.0-19-generic_3.13.0-19.39~lp1294729_amd64.deb
--
You received this bug
Comment from #1299794 bug
Hello
I checked the duplicate bug but I could not find a solution.
1/ I checked my disks with Gsmart but they seem OK
2/ My install is a clean install
3/ The bug persists despite the upgrade in the kernel
4/ I tried removing my M-audio card to no avail
5/ I booted on a
Just to confirm, the test kernel posted in comment #12 does not fix this
bug?
If that is the case, would it be possible for folks to test the latest mainline
kernel, which can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/
** Tags added: performing-bisect
--
I've reverted commit 25cb36334e92312684f5cc18bfcf1eb96eb00485 and put
test kernel packages in:
http://kernel.ubuntu.com/~cking/lp-1294729
Do you mind testing the appropriate 32 or 64 bit kernels and letting me
know if this resolves the issue for you?
--
You received this bug notification
I installed the 32 bit version
image-3.13.0-19-generic_3.13.0-19.39~lp1294729_i386 and files and the
same problem shows up. So that is not the problem. It would not allow me
to send a bug report as this is not an official package :)
The linux-tools-* package had to have --force-depends to
@Len, do you mind just double checking you are running that installed
version, using uname -a
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Colin King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, I will do that (the /var/crash files on that disk do show the
generic kernel with the bug number), but first... I realize it seems
from the top of the page that I am the only one this is affecting. SO I
am looking at what I may be doing different. The main thing is that I
have been using a USB
Ok, I installed the test kernel set from your directory (I don't seem to
be able to get -18) And from a system installed on an internal hard
drive I do not get any errors at all. I did a file system check/repair
from gparted on the external USB drive with no problems. I reinstalled
the same ISO on
Wonderful... (no not really) The problem has vanished on any drive, any
kernel. I am back up on the original install with the first kernel that
caused the problem 15min. running... doing all those lowlatency things I
was testing in the first place. No errors at all. My own conclusion is
that there
It's most definitely a kernel bug. Also, I looked at both 1294729,
1293828 and 1286866 and all of them refer to the ICE1712 driver.
A recent commit that affects ICE1712 is this one:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
trusty.git;a=commit;h=25cb36334e92312684f5cc18bfcf1eb96eb00485
On Thu, 20 Mar 2014, Joseph Salisbury wrote:
If you reboot again, does the error again start happening, or was it
just after the first reboot back into 3.13.0-18?
Yes it keeps happening. Not just after boot, (every boot) but as long as
the system is up the error keeps showing up, one box on
Can you attach /etc/pulse/daemon.conf to the bug report. We're seeing
audio buffer overruns, so it would be useful to see what the pulse audio
settings are.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As requested. This file is the stock as installed file.
** Attachment added: daemon.conf
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1294729/+attachment/4036256/+files/daemon.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
On Fri, 21 Mar 2014, Colin King wrote:
Can you attach /etc/pulse/daemon.conf to the bug report. We're seeing
audio buffer overruns, so it would be useful to see what the pulse audio
settings are.
It occures to me that I may have been testing kernel latency as the -17
version seemed worse
If you reboot again, does the error again start happening, or was it
just after the first reboot back into 3.13.0-18?
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of the
introduction of a regression, and when this regression was introduced.
If this is a
On Wed, 19 Mar 2014, Joseph Salisbury wrote:
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of the
introduction of a regression, and when
Booted old kernel (1.13.0-17), ran about 30 min with no problem. Booted
back to 1.13.0-18 and got same problem in about the same time it took to
fire up firefox. Second error report almost before cancelling the first.
Now it seems to be doing fine typing this and running you tube video.
Seems just
29 matches
Mail list logo
