** Description changed:
== Justification ==
In Xenial KVM kernel, the CONFIG_DEBUG_KERNEL is enabled, security team would
like to see CONFIG_DEBUG_RODATA to be enabled as well.
-
- In such case, the kernel can pass the test_072_config_debug_rodata check
- in the qa-regression-testing test ui
Of course, here it is
~$ grep . /sys/class/power_supply/*/capacity
0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1769075
Title:
Upgrade to 18.04 broke the battery reporting of blueto
looks like two of the patches are not in cosmic yet, which has 1.1.6-1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1768830
Title:
the audio can't work on Lenovo machines with dual
It would be interesting to try the linux kernel v4.15, it had solved a boot
freeze on my side.
See : https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
$ echo /sys/class/power_supply/*/capacity
/sys/class/power_supply/hid-34:88:5d:5e:0c:2f-battery/capacity
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1769075
Title:
[regression][bionic
As it appears the problem is entirely in the kernel and not bluez, I
have reassigned this bug to the kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1769075
Title:
[regression][bi
Can you please also provide the file name?
echo /sys/class/power_supply/*/capacity
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: bluez (Ubuntu)
Status: Incomplete => Invalid
** Summary changed:
- Upgrade to 18.04 broke the battery reporting of bluetooth
** Tags added: bionic regression-release
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1769075
Title:
[regression][bionic] Bluetooth keyboard battery reports 0%
Status in bluez package
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1769075
and then change the status of the bug to 'Confirmed'.
If, due to the nature
apport information
** Tags added: apport-collected
** Description changed:
I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
reports always 0% as battery percentage of the bluetooth Logitech K810
keyboard.
Which is a bit annoying since I get a KDE warning on the
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135273/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135271/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135270/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1769075
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135269/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1769075
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135268/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135272/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.l
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135267/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1769075
Ti
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135276/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135274/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135277/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1769075
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135275/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1769075/+attachment/5135278/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bug
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1769075
Title:
[regression][bionic] Bluetooth keyboard battery reports
: 172.22.5.150_controller.pp
Error: Failed to apply catalog: Execution of '/usr/bin/openstack image list
--quiet --format csv --long' returned 1: Could not determine a suitable URL for
the plugin (tried 26, for a total of 170 seconds)
You will find full trace in log
/var/tmp/packstack/20180507-141
Public bug reported:
Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty
On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
HID's INT3511/INT3512 [1].
As a consequence, HW manufacturers ha
Mark this task as incomplete for the missing i386 tests.
4.13.0-40.45 - generic
Regression test CMPL.
Issue to note in amd64:
libhugetlbfs - failed 7 killed by signal 7 bad config 1
monotonic_time - lodygin constantly failed with tsc test (bug 1732620)
ubuntu_bpf - test_maps failed (bug 175
** Description changed:
Support Intel Atom (Baytrail-I) HS-UART serdev slaves over tty
On systems using Intel Atom (Baytrail-I) SoC's, slave devices connected on
HSUART1/2 ports are described by the ACPI BIOS as virtual hardware using
HID's INT3511/INT3512 [1].
As a consequence, HW
I'm marking this as invalid in snappy as it doesn't seem related to
snapd proper.
** Changed in: snappy
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/b
--- Comment From grom...@br.ibm.com 2018-05-07 07:16 EDT---
Hello,
So have the kernel team confirmed that issue?
Is the absent file (libperf-jvmti.so) marked to be included in any
packaged already?
Thank you.
--
You received this bug notification because you are a member of Kernel
Pack
You have been subscribed to a public bug:
Problem desctriptin for following already Fix Releaed Bug:
https://bugzilla.linux.ibm.com/show_bug.cgi?id=166796
https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1764744
The package is still failing to configure
root@fipas1:~# ipa-server-install --
Default Comment by Bridge
** Attachment added: "free-ipa install failure log"
https://bugs.launchpad.net/bugs/1769631/+attachment/5135421/+files/fipa.tar
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubunt
table URL for
the plugin (tried 26, for a total of 170 seconds)
You will find full trace in log
/var/tmp/packstack/20180507-141926-6F9a8m/manifests/172.22.5.150_controller.pp.log
Please check log file
/var/tmp/packstack/20180507-141926-6F9a8m/openstack-setup.log for more
information
Addi
** Also affects: linux-oem (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem (Ubuntu)
Status: New => Confirmed
** Changed in: linux-oem (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packa
** Package changed: linux (Ubuntu) => freeipa (Ubuntu)
** Tags added: s390x universe
** Summary changed:
- freeipa-server installatio/configuration problem for s390x
+ freeipa-server installation/configuration problem on s390x
** Also affects: ubuntu-z-systems
Importance: Undecided
St
Hi,
Sorry I just chose the wrong package.. As you may know ASUS does not provide
support for Linux for this laptop...
You will find attached to this message the result of sosreport --batch.
Please let me know if I can do something in order to help you.
Regards
--
You received this bug notifica
*** This bug is a duplicate of bug 1720641 ***
https://bugs.launchpad.net/bugs/1720641
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rtl8812au (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ke
--- Comment on attachment From mdr...@us.ibm.com 2018-05-05 13:16 EDT---
Logs from crashes after SAN bring-up of boslcp6 and subsequent logs of success
boot after install of bz166588 patch
** Attachment added: "Logs from crashes after SAN bring-up of boslcp6 and
subsequent logs of succ
--- Comment (attachment only) From mdr...@us.ibm.com 2018-05-05 13:35
EDT---
** Attachment added: "fuller version of previous boslcp6 log"
https://bugs.launchpad.net/bugs/1762844/+attachment/5135440/+files/kern-boslcp6-before-and-after-bz166588-patch-fuller.log
--
You received this
Public bug reported:
ao baixar atu8alizações ele reporta que ha problemas. muito boa a versaO
uBUNTU 16.04 , INFORME WENO EMAIL jesus.alci...@hotmail.com
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-101-generic 4.4.0-101.124
ProcVersionSignature: Ubuntu 4.4.0-104.1
The attachment...
** Attachment added: "sosreport-potassium-20180507142110.tar.xz"
https://bugs.launchpad.net/ubuntu-certification/+bug/1767832/+attachment/5135442/+files/sosreport-potassium-20180507142110.tar.xz
--
You received this bug notification because you are a member of Kernel
Packag
** Description changed:
Support latest Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel.
This is the latest version of the driver provided by Redpine. For now,
this driver is enabled only on x86, x86_64 architectures. The impact is
also restricted to { SDIO_DEVICE(0x041B, 0x9330) }
** Tags removed: need-duplicate-check
--
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/1769655
Title:
package linux-image-4.4.0-101-generic 4.4.0-101.124 failed to
install/upgrade: packa
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/1769655
Title:
package linux-image-4.4.0-101-
Public bug reported:
Dell Edge 300x IoT Gateways have a relative humidity sensor hts221. The
sensor stops working (and reports stale values) after the system resumes
from suspend-to-ram/suspend-to-disk PM states.
This bug is for tracking purposes only, please don't triage.
** Affects: linux-oem
I have posted a full dmesg with the 'drm-tip' kernel compiled
especially.
Please see "upstream" (link above) for details.
--
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/1731784
Title:
s
--- Comment From cdead...@us.ibm.com 2018-05-07 09:41 EDT---
Two comments above, it points to a URL that does not match the commit id it is
refering to " cpufreq: powernv: Fix hardlockup due to synchronous smp_call in
timer interrupt"
The right URL seems to be
https://github.com/torvalds
** Tags added: regression-testing-passed
--
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/1767397
Title:
linux: 4.15.0-21.22 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Public bug reported:
There's quite a chance to find kernel oops when mwifiex is in AP mode.
Previously two workaround commits were added in the Xenial kernel,
8a034f97a28dba62026343eef7992766c91273a7 and
f21d12781c88413aec7ee44983f05b1cdf90662f, to mitigate this issue. The
original report can be f
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
--
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/1767397
Title:
linux: 4.15.0-21.22 -proposed
Same issue in Ubuntu 18.04, fresh install on Lenovo e540 notebook, with two
different bluetooth mouse
- Logitech M557
- Tecknet BM307
The problem occurs in the following cases:
- Mouse Switch off then on
- Mouse inactivity (leaving the notebook for 5/10 minutes)
- Notebook sleep
- Notebook
This fix has been merged in bionic/master via the stable update 4.15.11
so only Xenial is affected.
** Summary changed:
- [Xenial/Bionic] Kernels OOPS when mwifiex is in AP mode
+ [Xenial] Kernels OOPS when mwifiex is in AP mode
--
You received this bug notification because you are a member of
This bug was fixed in the package linux-meta-hwe-edge - 4.15.0.20.42
---
linux-meta-hwe-edge (4.15.0.20.42) xenial; urgency=medium
* Fix transitional linux-signed* packages to use the proper suffix.
linux-meta-hwe-edge (4.15.0.20.41) xenial; urgency=medium
* Bump ABI 4.15.0-20
--- Comment From mainam...@in.ibm.com 2018-05-07 10:52 EDT---
*** Bug 167297 has been marked as a duplicate of this bug. ***
--
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/1711283
You have been subscribed to a public bug:
== Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 ==
---Problem Description---
Request to revert SAUCE patches from 18.04 and apply the patches from
next/master.
Below set of cxlflash patches were submitted to Canonical after they
were sent to the com
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Tags added
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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 fix t
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
** Chan
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
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/1768526
T
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: kernel-da-key
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Triaged
** Changed in
Public bug reported:
[Impact]
on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at
address 00a99000/0xa99000" while booting. These messages are a false
positive and triggered at random.
[Test]
There is no reliable way to reproduce these warnings, they are trig
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Critical
** Changed
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[
Does this issue go away if you boot back into the -19 kernel?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1768647
Title:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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 fix t
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1769696
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1769236
and then change the status of the bug to 'Confirmed'.
If, due to the nature
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Ch
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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 fix t
Is there a way to easily revert my changes if the latest kernel doesn't
work?
On Mon, May 7, 2018, 12:01 PM Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this partic
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Tags added: needs-bisect
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1728238
Title:
update-initramfs not adding i91
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1768583
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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 fix t
** Package changed: linux-signed (Ubuntu) => 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/1769331
Title:
broken upgrade/ full install bionic from ubuntu-budgie 17.10
St
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[
And more. Different output of the command: cat
/sys/kernel/debug/vgaswitcheroo/switch
nouveau driver:
0:IGD:+:Pwr::00:02.0
1:DIS: :DynOff::01:00.0
nvidia 390.48, after prime-select intel:
0:IGD:+:Pwr::00:02.0
1:DIS: :Off::01:00.0
You can see the different status of the discrete c
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[
On 05/04/2018 07:14 AM, Rafael J. Wysocki wrote:
> On Thursday, May 3, 2018 11:29:18 PM CEST Rafael J. Wysocki wrote:
>> On Thu, May 3, 2018 at 9:11 PM, Bjorn Helgaas wrote:
>>> On Thu, May 03, 2018 at 02:29:02PM -0400, Joseph Salisbury wrote:
On 05/02/2018 06:41 AM, Rafael J. Wysocki wrote:
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1769331
and then change the status of the bug to 'Confirmed'.
If, due to the nature
--- Comment (attachment only) From dougm...@us.ibm.com 2018-05-02 14:28
EDT---
** Attachment added: "dmesg log thus far, for May 1 run."
https://bugs.launchpad.net/bugs/1762844/+attachment/5135512/+files/dmesg
--
You received this bug notification because you are a member of Kernel
--- Comment From dougm...@us.ibm.com 2018-05-07 12:10 EDT---
Of the "boslcp" systems, only 3 appear to have QLogic adapters. Of those, one
has been running without the extended error logging and so collected no data,
and one has been down (or non-functional) for about 36 hours. Of the dat
--- Comment on attachment From indira.pr...@in.ibm.com 2018-05-04 11:12
EDT---
Attached host console logs for reboot issue after fresh installation
** Attachment added: "boslcp3_host_reboot_consolelogs"
https://bugs.launchpad.net/bugs/1762844/+attachment/5135525/+files/boslcp3_reboo
--- Comment on attachment From indira.pr...@in.ibm.com 2018-05-02 23:49
EDT---
Attached latest dmesg log for boslcp3 - may1st run
** Attachment added: "dmesg log_boslcp3_latest for may1 run"
https://bugs.launchpad.net/bugs/1762844/+attachment/5135514/+files/dmesg_boslcp3_may3
--
Y
--- Comment on attachment From mdr...@us.ibm.com 2018-05-05 13:16 EDT---
Logs from crashes after SAN bring-up of boslcp6 and subsequent logs of success
boot after install of bz166588 patch
** Attachment added: "Logs from crashes after SAN bring-up of boslcp6 and
subsequent logs of succ
--- Comment on attachment From indira.pr...@in.ibm.com 2018-05-02 23:51
EDT---
Attached /var/log/syslog file from boslcp3 host
** Attachment added: "/var/log/syslog boslcp3 host"
https://bugs.launchpad.net/bugs/1762844/+attachment/5135523/+files/syslog
--
You received this bug noti
--- Comment on attachment From indira.pr...@in.ibm.com 2018-05-02 23:22
EDT---
Attached boslcp3 host console tee logs
** Attachment added: "boslcp3 host console tee logs"
https://bugs.launchpad.net/bugs/1762844/+attachment/5135513/+files/boslcp3-host-may1.txt
--
You received this
--- Comment (attachment only) From mdr...@us.ibm.com 2018-05-05 13:35
EDT---
** Attachment added: "fuller version of previous boslcp6 log"
https://bugs.launchpad.net/bugs/1762844/+attachment/5135527/+files/kern-boslcp6-before-and-after-bz166588-patch-fuller.log
--
You received this
--- Comment on attachment From indira.pr...@in.ibm.com 2018-05-02 23:53
EDT---
Attached /var/log/syslog.1 file from boslcp3 host
** Attachment added: "/var/log/syslog1.file boslcp3"
https://bugs.launchpad.net/bugs/1762844/+attachment/5135524/+files/syslog.1
--
You received this bug
1 - 100 of 215 matches
Mail list logo