Okay.. this is interesting. It seems like the Ubuntu dev version of
4.10 is actually intermittently failing (?!) I guess the next thing to
do here is keep rebooting on this version of the kernel and see how
often the bug occurs vs doesn't occur, so I can get a feel for a
reasonable number of
I should clarify, I know for certain that 4.4.0-51 is stable and
reliable (and doesn't exhibit the bug). As part of our attempt to
verify everything was correct with the installation we had a system run
from Wednesday before Thanksgiving, all the way through to the following
Monday, during which
Paul Graydon, if the bug is reproducible at any interval, then perhaps a
standard bisect between:
linux-image-4.4.0-53-generic - Fine
linux-image-4.4.0-57-generic - Affected
would be more appropriate to understand which commit introduced the
regression.
--
You received this bug notification
I can give that a shot, following the instructions here:
https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting_Ubuntu_kernel_versions
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The list below is not exhaustive, but does contain the necessary patches to
enable power9. These patches may have dependencies on prior patches.
Base Power9 patches to be merged:
-
c7c3f568beff2b72f02a7807ec48b0bc66a7ead6 powerpc/perf: macros for power9 format
Should I expect a response or new kernel? Regards.
--
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/1640297
Title:
16.04.1 LTS hang during boot 4.4.0-45-generic with /etc/crypttab.
[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.
[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.
[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.
latest update is looking good, this bug hasn't surfaced since I rebooted
about 15 minutes ago (and the bug always appeared well before that,
within 5 minutes if that)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: debian-installer (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi
1.We can reproducible in 16.04.1, but same that system would hang up and I have
provide a photo for the crash for you reference as the attachment file.
2.I have another question ,what root cause will rsolved in ubuntu 17.04?
** Attachment added: "IMG_0076.JPG"
Leo-Chen:
>"Hi 1.We can reproducible in 16.04.1, but same that system would hang up and I
>have provide a photo for the crash for you reference as the attachment file."
Thanks for the photo.
>"2.I have another question"
What was the first question?
>" ,what root cause will rsolved in ubuntu
** Changed in: zfs-linux (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1628279
Title:
python utilities script suffix (.py)
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1650054
Title:
Dell Precision 5520 & 3520 freezes at
I'll take a fresh look in the morning, but ran into this:
make[1]: Leaving directory
'/home/ubuntu/storage/ubuntu-xenial/debian/build/build-generic/zfs/module'
Debug: module-check-generic
install -d
/home/ubuntu/storage/ubuntu-xenial/debian.master/abi/4.4.0-54.76/amd64
find
** Summary changed:
- Xenial desktop 16.04.x will have a black screen after PXE installation
+ Xenial server 16.04.x will have a black screen after PXE installation
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: debian-installer (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
In Comments 5 ,Yes we're keep on Ubuntu 16.04.x.. Do you have solution
and will be impelmented on Ubuntu 16.04.2...later versions ?,as zesty is
LTS version?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You have been subscribed to a public bug:
I made a fresh install of 14.04 on a Dell XPS-8900 there is about two or three
month.
The driver was missing, and I have installed manually a driver. It has worked,
but with an ennoying problem.
Each time a new Linux version is updated and then the
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/3.13.0-107.154-generic/ms10-34-mcdivittB0-kernel__3.13.0-107.154__2016-12-27_07-03-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-34.36-generic/kernel02__4.8.0-34.36__2016-12-27_07-39-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.13.0-107.154-generic/modoc__3.13.0-107.154__2016-12-27_07-10-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 141, failed: 28;
http://kernel.ubuntu.com/testing/4.8.0-34.36-generic/kernel02__4.8.0-34.36__2016-12-27_08-34-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/3.19.0-79.87~14.04.1-generic/ms10-34-mcdivittB0-kernel__3.19.0-79.87~14.04.1__2016-12-27_08-15-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/vivid/3.19.0-79.87
/vivid-proposed-frozen.html
** Tags added: certification-testing-passed
** Changed in:
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) =>
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-11.12-generic/secchi__4.9.0-11.12__2016-12-27_07-35-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.19.0-79.87~14.04.1-generic/modoc__3.19.0-79.87~14.04.1__2016-12-27_08-22-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-34.36~16.04.1-generic/secchi__4.8.0-34.36~16.04.1__2016-12-27_08-58-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 4, failed: 2;
http://kernel.ubuntu.com/testing/4.4.0-58.79-generic/kernel01__4.4.0-58.79__2016-12-27_11-42-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 4, failed: 2;
http://kernel.ubuntu.com/testing/4.4.0-58.79-generic/s2lp3__4.4.0-58.79__2016-12-27_11-43-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-34.36-generic/ms10-34-mcdivittB0-kernel__4.8.0-34.36__2016-12-27_09-26-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-79.87-generic/modoc__3.19.0-79.87__2016-12-27_09-35-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 33, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-34.36-generic/kernel02__4.8.0-34.36__2016-12-27_10-41-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 16, failed: 4;
http://kernel.ubuntu.com/testing/4.8.0-34.36-generic/kernel02__4.8.0-34.36__2016-12-27_11-41-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.9.0-11.12-generic/naumann__4.9.0-11.12__2016-12-27_07-45-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 141, failed: 28;
http://kernel.ubuntu.com/testing/4.8.0-34.36-generic/kernel02__4.8.0-34.36__2016-12-27_08-02-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-34.36~16.04.1-generic/naumann__4.8.0-34.36~16.04.1__2016-12-27_09-07-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-58.79-generic/modoc__4.4.0-58.79__2016-12-27_10-46-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 6, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-34.36-generic/onza__4.8.0-34.36__2016-12-27_12-05-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1652778
Title:
package
You have been subscribed to a public bug:
Laptop Model : ASUS ROG GL552 DH71
First Appearance : Got laptop yesterday. dual booted with ubuntu 14.04.
Touchpad never detected.
Manufacturer : ASUS ( as listed under windows 10 )
* xinput list *
⎡ Virtual core pointer id=2
tests ran: 4, failed: 2;
http://kernel.ubuntu.com/testing/3.13.0-107.154-generic/ms10-35-mcdivittB0-kernel__3.13.0-107.154__2016-12-27_12-46-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'll get started on it. This might take a while to do.
A couple of quick observations:
1) we haven't validated that mainline 4.4.0 actually works. I only know
certain Ubuntu versions of the 4.4.0 kernel work. Given how much seems
to be changing between Ubuntu releases of it, that seems a risky
tests ran: 6, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-34.36-generic/onibi__4.8.0-34.36__2016-12-27_12-16-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Occurred during a routine upgrade.
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-32-generic 4.8.0-32.34
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
NonfreeKernelModules: wl
ApportVersion:
Ahh, I see where the kteam tools stuff is supposed to come from.
It's not clear if I'm supposed to go down that route and use the
mainline-build-one script or not when trying to build the kernel in this
case. If I use the mainline-build-one tool:
$ mainline-build-one
Gah.. okay https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
--
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/1652348
Title:
initrd dhcp fails / ignores valid response
Status in linux
Rolling that command against master fails too:
ubuntu@Beta:~/linux$ mainline-build-one
afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc xenial
*** BUILDING: commit:afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc series:xenial
abinum: ...
full_version<4.4.0>
version<4.4.0>
long
abinum<040400>
fatal: 'xenial'
** Also affects: linux (Debian)
Importance: Undecided
Status: New
--
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/1520519
Title:
ASUS ROG GL552 TouchPad not detected
Status in
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-34.36-generic/modoc__4.8.0-34.36__2016-12-27_13-10-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 4, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-34.36-generic/onza__4.8.0-34.36__2016-12-27_13-12-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 4, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-58.79-generic/onibi__4.4.0-58.79__2016-12-27_13-43-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 4, failed: 2;
http://kernel.ubuntu.com/testing/3.19.0-79.87~14.04.1-generic/ms10-35-mcdivittB0-kernel__3.19.0-79.87~14.04.1__2016-12-27_12-05-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** No longer affects: linux (Ubuntu)
--
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/1520519
Title:
ASUS ROG GL552 TouchPad not detected
Status in linux package in Ubuntu:
Incomplete
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1520519
Guido Granda Muñoz, to see if this is already resolved in Ubuntu, could
you please test http://cdimage.ubuntu.com/daily-live/current/ and advise
to the results?
** This bug is no longer a duplicate of bug 1520519
ASUS ROG GL552 TouchPad not detected
--
You received this bug notification
sameer, to see if this is already resolved in Ubuntu, could you please
test http://cdimage.ubuntu.com/daily-live/current/ and advise to the
results?
** Package changed: linux (Debian) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags removed:
tests ran: 3, failed: 1;
http://kernel.ubuntu.com/testing/3.13.0-107.154-generic/onibi__3.13.0-107.154__2016-12-27_15-10-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Paul Graydon, to advise, I have updated the article to move the
mainline-build-one section out of the way, as it has been distracting
here, and for other folks. Feel free to ignore it, as it is for those
who build kernels all the time (i.e. N/A here). Also, I don't maintain
it, so I won't be able
Someone on Debian has apparently found some drivers for the camera
hardware from Android- it is to be seen as of yet, however, if these
drivers work. Heres a link to their work on the MSSP4:
https://github.com/jimdigriz/debian-mssp4
If anyone could walk me through the steps of compiling them, I
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1652815
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
Kẏra, execute the following command only once, as it will automatically gather
debugging information, in a terminal:
apport-collect 1592201
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality
Public bug reported:
Hardware: Microsoft Surface Pro 4, 4gb/128gb nvme drive
Expected Behaviour: Pen/Touch function
Actual Behaviour: Pen/Touch do not work or respond to anything
Kernel/Ubuntu Versions: All
Cause: Hardware requires IPTS (Intel Precision Touch & Stylus) to
function. This is
You have been subscribed to a public bug:
Despite of the existing patch (e.g.
https://github.com/tiggerite/mint-17.3-for-surface-
pro-3/blob/master/patches-4.3/surface-cam.patch), it seems some surface
pro 4 model (E.g. my i7 16G) uses a different webcam solution.
>From windows, there are three
I tested kernel 4.10-rc1, and the issue is solved with it.
I'm not sure how to test the yakkety proposed kernel, because the
instructions seems to be for a desktop computer, and this issue shows up
much much more clearly on my server computers.
--
You received this bug notification because you
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1650635
Title:
vmxnet3 driver could causes kernel
Ben (ben-mueller1998), it will help immensely if you filed a new report with
the Ubuntu, using the default repository kernel (not mainline/upstream) via a
terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
The patchset is now in v4.10-rc1.
# git clone https://github.com/torvalds/linux.git
ae0ac0e netfilter: x_tables: pack percpu counter allocations
f28e15b netfilter: x_tables: pass xt_counters struct to counter allocator
4d31eef netfilter: x_tables: pass xt_counters struct instead of packet
70 matches
Mail list logo
