For anyone tracking this, the new bug is here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715861
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530187
Title:
r852 & r592 IRQ: DMA errors
Pontus Gråskæg, it will help immensely if you use the computer the problem is
reproducible with, and file a new report with Ubuntu by using the default
repository kernel (not mainline/upstream/3rd party) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
** Attachment remo
** Attachment removed: "Typical syslog Ricoh warning entry"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187/+attachment/4946403/+files/Typical%20syslog%20Ricoh%20warning%20entry
** Attachment added: "Typical syslog Ricoh warning entry"
https://bugs.launchpad.net/ubuntu/+source
** Attachment added: "hwinfo extract"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187/+attachment/4946428/+files/hwinfo%20extract
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1530187
I get the same issue on a newly installed Lubuntu 16.04.3 with 'apt
upgrade' freshly applied.
/var/log/syslog and /var/log/kern.log grow to 100s of MiB in less than a
day.
Typical syslog entry is attached (hostname redacted). I am not making
hardware changes at the times these entries are made.
** Attachment added: "Kernel warning at boot that taints kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187/+attachment/4946427/+files/Kernel%20warning%20at%20boot%20that%20taints%20kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Attachment added: "Typical syslog Ricoh warning entry"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530187/+attachment/4946403/+files/Typical%20syslog%20Ricoh%20warning%20entry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Laurent Martin-Borret, to clarify, what is needed is the most recent
kernel which didn't demonstrate the issue. If that's the 3.16 series,
then that would be the start of the bisect, versus 3.19.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Christopher, I am not sure regarding your proposed strategy...
Let me explained :
- when I first discovered & reported this issue, I was using Ubuntu 15.04 /
kernel 3.19.0-28-generic #30-Ubuntu on x86_64
- then I thought it was resolved when upgrading to kernel 3.19.0-39-generic
(now I more think
Laurent Martin-Borret, the next step is to fully commit bisect from
kernel 3.19 to 4.2 in order to identify the last good kernel commit,
followed immediately by the first bad one. This will allow for a more
expedited analysis of the root cause of your issue. Could you please do
this following https
I tested on latest available kernel as suggested by Christopher.
Issue is still present on kernel v4.4-rc7-wily
I got more or less the same stack trace when inserting an SD card. However, I
got the stack trace once, not repeatedly. Or maybe I did not wait enough time.
Gordon Dickens mentionned he
Laurent Martin-Borret, at your earliest convenience, could you please
test the latest upstream kernel available from the very top line at the
top of the page from http://kernel.ubuntu.com/~kernel-
ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and
please do not test the daily
Launchpad has imported 24 comments from the remote bug at
https://bugzilla.novell.com/show_bug.cgi?id=892249.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
13 matches
Mail list logo
