I can verify that I was unable to reproduce this bug with the latest
proposed kernel on a highbank.
ubuntu@hb07-15:~$ cat /etc/issue
Ubuntu 13.10 \n \l
ubuntu@hb07-15:~$ uname -a
Linux hb07-15 3.11.0-15-generic #22-Ubuntu SMP Mon Dec 2 23:36:39 UTC 2013
armv7l armv7l armv7l GNU/Linux
I can verify that the patch fixes the bug above, with this patch I am
able to see messages at boot...
[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[
This patch is a temporary fix.
** Patch added: Patch to enable earlyprintk via the PL011.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248233/+attachment/3900688/+files/0001-Patch-to-enable-earlyprintk-via-the-PL011.-Because-t.patch
--
You received this bug notification because
Public bug reported:
There is no earlyprintk via the PL011 because there's no defined device
tree binding for earlyprintk UART to get the PL011 to work you'll need
to tweak the kernel a bit. kernel doesn't ever add the clock to its
list, and then it refuses to probe for the PL011. This is a
due to the nature of the issue encountered log files that will aid in
diagnosing the problem might be missing.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
D-I does not detect USB devices on servers that have On-Chip EHCI Host
Controller (ehci_msm), as a results install to USB devices fail. Adding
ehci-msm to d-i/modules/usb-modules fixes this issue.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Manoj Iyer (manjo)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
ARM64 builds needs build dependency on libz-dev inorder to support
compressed kernels. The attached patch adds that support. Note. amd64
and i386 do not have this dependency, I tested the current zesty version
of the kexec-tools on amd64 and i386 and it works. The patch only apply
to ARM64 build.
ARM64 builds needs build dependency on libz-dev inorder to support
compressed kernels. The attached patch adds that support. Note. amd64
and i386 do not have this dependency, I tested the current zesty version
of the kexec-tools on amd64 and i386 and it works. The patch only apply
to ARM64 build.
(unassigned) => Manoj Iyer (manjo)
** Changed in: kexec-tools (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1661363
Title:
Fails
[Testing on VM]
== Default kernel on Yakkety ==
ubuntu@test:~$ uname -a
Linux test 4.8.0-37-generic #39-Ubuntu SMP Thu Jan 26 02:26:41 UTC 2017 aarch64
aarch64 aarch64 GNU/Linux
ubuntu@test:~$
== No kexec-tools for ARM64 ==
ubuntu@test:~$ sudo apt-get install kexec-tools
Reading package lists...
** Description changed:
[Impact]
- * If the kernel is not built with CONFIG_KEXEC support, kexec-tools will not
be able to live boot a new kernel over the running one.
- * Our partners/customers have requested this feature.
+ * If the kernel is not built with CONFIG_KEXEC support,
[AMD64 regression testing]
[Testing with stock Yakkety kernel & kexec-tools]
ubuntu@test:~$ sudo file /boot/vmlinuz-4.8.0-30-generic
/boot/vmlinuz-4.8.0-30-generic: Linux kernel x86 boot executable bzImage,
version 4.8.0-30-generic (buildd@lcy01-08) #32-Ubuntu SMP Fri Dec 2 03:,
RO-rootFS,
note that kexec-tools currently is not built for ARM64
* I have an SRU to enable that bugs.launchpad.net/bugs/1659618
* I am working with dannf to get kexec-tools to support ARM64 in yakkety.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Manoj Iyer (manjo)
Status: In Pro
[Testing]
== Build & Install kernel and kexec-tools ==
Built kexec-tools with patches needed for ARM64 support, and built a 4.8.0-38
Yakkety kernel with CONFIG_KEXEC and CONFIG_KEXEC_CORE set to Y.
ubuntu@test:~$ cat /etc/issue
Ubuntu 16.10 \n \l
ubuntu@test:~$
ubuntu@test:~$ dpkg -l | grep
** Summary changed:
- [Yakkety] Enable KEXEC support in ARM64 kernel
+ [Yakkety SRU] Enable KEXEC support in ARM64 kernel
--
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/1662554
Title:
** Patch added: "Yakkety kexec-tools arm64 support V4"
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+attachment/4814952/+files/yakkety-kexec-tools-enable-arm64-support-V4.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is
Please ignore my previous comment, I introduced an err in the changelog.
Please use this cleaned up version of the patch.
** Patch added: "Yakkety kexec-tools arm64 support V3"
Please note that the previous debdiff patch I attached introduced some
spurious changes by accident. Here is a cleaner version of the debdiff
patch for Yakkety. I applied this patch to Yakkety kexec-tools and I was
able to build and test.
Please consider this patch for SRU to kexec-tools in
I was able to apply this patch and build kexec-tools on Xenial. Please
see this link for details: https://pastebin.ubuntu.com/23950298/
[TESTING]
== Y kernel for X series with kexec support ==
I had to build a Yakkety kernel for Xenial series with KEXEC enabled.
ubuntu@test:~$ uname -a
Linux
[Regression testing on Xenial AMD64]
AMD64 kernel already has kexec support on Xenial. The attached patch applies
cleanly and builds on AMD64: https://pastebin.ubuntu.com/23950437/
== Installed kexec-tools built with ARM64 enablement patches ==
ubuntu@test:~$ dpkg -l | grep kexec-tools
ii
Public bug reported:
[IMPACT]
* kexec-tools in Xenial (16.04) currently does not support ARM64
architecture.
* Backport support for ARM64 arch from upstream
https://github.com/horms/kexec-tools
* Majority of the patches are contained in kexec/arch/arm64/ except for
one patch that
** Description changed:
[IMPACT]
* kexec-tools in Xenial (16.04) currently does not support ARM64
architecture.
* Backport support for ARM64 arch from upstream
https://github.com/horms/kexec-tools
* Majority of the patches are contained in kexec/arch/arm64/ except for
[TESTING ON ARM64 HARDWARE]
$ cat /etc/issue
Ubuntu 16.04.1 LTS \n \l
$ sudo apt-add-repository ppa:manjo/kexec-tools
$ sudo apt update
$ sudo apt install kexec-tools
$ kexec --version
kexec-tools 2.0.10 released 26 January 2017
$ ls /boot
abi-4.7.0-2-generic grub
The above test was that of the kexec-tools package that includes review
comments from dannf.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1659618
Title:
Enable ARM64 support in
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Taco Screen team (taco-screen-team)
--
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/1659111
Title:
UbuntuKVM guest crashed
Updated changelog to refer to LP: #1659618
new debdiff attached.
** Patch added: "updated debdiff - changelog referring to LP# 1659618"
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+attachment/4809480/+files/updated-debdiff-withLP%23.diff
--
You received this bug
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Jon Grimm (jgrimm)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
[ Fixing fixdep - from x86_64 to ppc64el ]
After you install the debs for kernel and headers do the following:
root@lazy:/# updatedb
root@lazy:/# locate fixdep
/usr/src/linux-headers-4.10.0-041000/scripts/basic/fixdep.c
/usr/src/linux-headers-4.10.0-041000-generic/scripts/basic/.fixdep.cmd
[ Installing debs on ppc64el works ]
root@lazy:/# wget
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/linux-image-4.10.0-041000-generic_4.10.0-041000.201702191831_ppc64el.deb
--2017-02-23 21:16:49--
Please file bugs with bug description and process to recreate.
--
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/1667599
Title:
CAPI:Ubuntu: Kernel panic while rebooting
Status in linux
** Changed in: linux (Ubuntu)
Status: New => Won't Fix
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The attached patch is for:
* kexec: Increase the upper limit for RAM segments (LP: #1663400)
This patch applies cleanly on Zesty kexec-tools:
https://pastebin.ubuntu.com/23995216/
[TESTING with Zesty kexec-tools on hardware]
ubuntu@ubuntu:~$ dpkg -l | grep kexec-tools
ii kexec-tools
increases the value to 64.
[Test Case]
NA
[Regression Potential]
Since patches are confined to arm[64] there is a low overall risk of regression.
** Affects: kexec-tools (Ubuntu)
Importance: Undecided
Assignee: Manoj Iyer (manjo)
Status: New
--
You received this bug
** Description changed:
[Impact]
On a newer UEFI based Qualcomm target the number of system ram regions
retrieved from /proc/iomem are ~40. Currently KEXEC_SEGMENT_MAX is set to 16,
which represents the kexec segments passed to kexec_load syscall, like kernel
image, initrd image etc. The
[TEST with yakkety kexec-tools]
ubuntu@ubuntu:~$ sudo cat /proc/iomem | grep "System RAM"
0020-0020 : System RAM
0082-0307 : System RAM
0308-0308 : System RAM
0309-031f : System RAM
0320-033f : System RAM
0341-0589 : System RAM
058a-058a :
The attached patch has the complete set of patches needed for kexec support on
ARM64.
* Enable ARM64 support in kexec-tools (LP: #1659618)
* Enable support for compressed kernels on ARM64 (LP: #1661363)
* kexec: Increase the upper limit for RAM segments (LP: #1663400)
This patch applies cleanly
The attached patch has the complete set of patches needed for kexec support on
ARM64.
* kexec: Increase the upper limit for RAM segments [LP: #1663400]
* Enable compressed kernel support for ARM64 [LP: #1661363]
* Enable ARM64 support [LP: #1659618]
This patch applies cleanly on Xenial
The attached patch is for:
* kexec: Increase the upper limit for RAM segments (LP: #1663400)
This patch applies cleanly on Zesty kexec-tools:
https://pastebin.ubuntu.com/23995216/
[TESTING with Zesty kexec-tools on hardware]
ubuntu@ubuntu:~$ dpkg -l | grep kexec-tools
ii kexec-tools
How long does it take for you to reproduce this issue? I ran the same
test on AMD64 for over 12hrs and was not able to reproduce the failure.
The 17.04 kernel I have is 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20.
--
You received this bug notification because you are a member of Kernel
Packages,
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854826
Importance: Unknown
Status: Unknown
** Changed in: kexec-tools (Ubuntu Xenial)
Assignee: (unassigned) => Manoj Iyer (manjo)
** Changed in: kexec-tools (Ubuntu Yakkety)
Assignee: (unassigned) => Manoj Iyer (manjo)
** C
** Changed in: kexec-tools (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Louis Bouchard
(louis-bouchard)
** Changed in: kexec-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Colin, Could you please help resolving this OOM with stress-ng?
** Also affects: stress-ng (Ubuntu)
Importance: Undecided
Status: New
** Changed in: stress-ng (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Assignee: Taco Screen
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Seth Forshee (sforshee)
--
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/1650062
Title:
I would assume that the keys are generated by the emvctl package. This
would require evmctl tools packaged in Ubuntu. Could you please confirm
that this package might be a likely candidate that we might want to
carry in Ubuntu? https://sourceforge.net/p/linux-ima/ima-evm-
utils/ci/v0.9/tree/
**
Leann, could you please get someone to pull in commit referenced in this
bug to fix the oops ?
** Changed in: makedumpfile (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Leann Ogasawara
(leannogasawara)
** Changed in: makedumpfile (Ubuntu)
Importance: Undecided => Critical
Steve, could your team please take a look ?
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Steve Langasek (vorlon)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
IBM needs to identify a patch that fixes this issue. We do not have a
good mechanism to reproduce the bug.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This package is supported by the community, it would require a community
effort to resolve this issue.
** Also affects: cpufrequtils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => (unassigned)
** No longer
Looks like the kernel option needs to be added when you setup kdump, and
you have already updated the wiki pages to document this. I am marking
this as fix released because there is nothing more to do from
canonical's side.
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You
ash (Ubuntu)
** Also affects: makedumpfile (Ubuntu)
Importance: Undecided
Status: New
** Changed in: crash (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Manoj Iyer (manjo)
** Changed in: makedumpfile (Ubuntu)
Assignee: (unassigned) => Manoj Iyer (manjo)
in this direction for hardware error handling.
Currently EDAC_MM_EDAC=m is in Ubuntu, but EDAC_GHES requires this to be
=y therefore it is not selected.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Manoj Iyer (manjo)
Status: Incomplete
--
You received this bug
** Description changed:
EDAC_GHES is essential for ARMv8.0 Server systems, as it enables
firmware-first error handling of memory and CPU errors. Due to a lack of
standard RAS architecture (or machine check architecture equivalent) on
ARMv8.0 systems, APEI/GHES is the only mechanism
** Description changed:
EDAC_GHES is essential for ARMv8.0 Server systems, as it enables
firmware-first error handling of memory and CPU errors. Due to a lack of
standard RAS architecture (or machine check architecture equivalent) on
ARMv8.0 systems, APEI/GHES is the only mechanism
** Description changed:
EDAC_GHES is essential for ARMv8.0 Server systems, as it enables
firmware-first error handling of memory and CPU errors. Due to a lack of
standard RAS architecture (or machine check architecture equivalent) on
ARMv8.0 systems, APEI/GHES is the only mechanism
Config change wont be sufficient at this time, We will also need
supporting patch: https://lkml.org/lkml/2016/8/10/231
--
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/1628111
Title:
systems with high memory to test with.
[Regression Potential]
Changes are confined to ARM architecture, patches apply cleanly to
Ubuntu-4.10.0-13.15. Potential for any regression is low.
** Affects: linux (Ubuntu)
Importance: Critical
Assignee: Manoj Iyer (manjo)
Status: New
test login: [ 146.606156] cloud-init[1023]: Cloud-init v. 0.7.9 running
'modules:config' at Tue, 21 Mar 2017 17:23:44 +. Up 143.57 seconds.
[ 168.868544] cloud-init[1161]: Cloud-init v. 0.7.9 running 'modules:final' at
Tue, 21 Mar 2017 17:24:06 +. Up 165.37 seconds.
[ 168.914038]
> It's not unrelated. That is the actusl phy on the SDP.
and the same for REPs? our target cert platform?
>
> From: Manoj Iyer [manoj.i...@canonical.com]
> Sent: Wednesday, March 29, 2017 10:11 PM
> To: Timur Tabi
> Cc: Manoj Iyer; A
These are in the next branch of the maintainer's tree -
https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git/log/?h=next
--
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/1675046
nic.
[Regression Potential]
At present this driver applies only to amberwing systems, any regression will
be isolated to amberwing platforms. The over all risk of regression is low.
** Affects: linux (Ubuntu)
Importance: Critical
Assignee: Manoj Iyer (manjo)
Status: New
qcom_emac driver that is in Zesty (4.10) kernel is able to bring up the
interface but fails to get a DHCP address. This bug is currently blocked
until upstream fixes the qcom_emac driver.
** Changed in: linux (Ubuntu)
Assignee: Manoj Iyer (manjo) => Timur Tabi (timur-tabi)
--
You recei
t; driver resolves, although I've never seen it make a difference until today.
>
> On 03/29/2017 04:50 PM, Manoj Iyer wrote:
>> Timur,
>>
>> Based on https://bugs.launchpad.net/bandera/ubuntu-17.04/+bug/1657261 yes
>> this was backported from 4.11 to 4.10 and commited to ze
Assignee: Manoj Iyer (manjo)
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/1674466
Title:
tty: acpi/spcr: QDF2400 E44 checks for wrong OEM revision
Status in linux
Timur,
I strongly suspect that the NMI watchdog softlockups caused by mlx5_core
dma mapping is the root cause of why qcom_emac driver is unable to get a
dhcp address. I blacklisted the mlx5_core driver and the soft lockups
went away. Nate suggested that we might need some additional iommu
related
** Description changed:
[IMPACT]
- On QDF2400 ARM64 servers, booting Zesty 4.10 kernel causes soft lockups on
multiple CPUs.
+ On QDF2400 ARM64 servers, booting Zesty 4.10 kernel causes soft lockups on
multiple CPUs.
[ 104.205397] Modules linked in: nls_iso8859_1 cdc_acm bridge stp llc
The qcom_emac driver in the installer is able to get a DHCP lease once I
blacklisted the mlx5_core module.
~ # lsmod
Module Size Used by
uas28672 0
usb_storage77824 1 uas
at803x 16384 1
devlink36864 0
ptp
With the PHY module and the qcom-emac driver enabled in D-I I am able
to see the interface in the installer configure network screen.
┌─┤ [!!] Configure the network ├──┐
│ │
│
I built a DI where the initrd has both the PHY and the qcom_emac driver.
The d-i installer now loads both at803x and qcom_emac, but dhclient
fails to get a DHCP address. So, I am not sure what is going on with
qcom_emac.. is there another module dependency I am missing ?
~ # lsmod
Module
** Summary changed:
- [Zesty] rename msm_emac to qcom_emac
+ [Zesty] replace msm_emac with qcom_emac
** Summary changed:
- [Zesty] replace msm_emac with qcom_emac
+ [Zesty] d-i: replace msm_emac with qcom_emac
--
You received this bug notification because you are a member of Kernel
Packages,
esty Ubuntu-4.10.0-18.20 on QDF2400 SDP.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Manoj Iyer (manjo)
Status: In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
on my qdf2400 server. Looks like dhclient is able to get a lease and
ifconfig displays the ip address.
ubuntu@ubuntu:~$ sudo dhclient -v eth0
[sudo] password for ubuntu:
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info,
Please try the LTS backport HWE-X kernel or LTS 14.04.05, and see if you
can reproduce 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/1486152
Title:
Kernel WARN @
/Yakkety source in armhf system.
[Regression Potential]
Since patch is confined to arm there is a low overall risk of regression
** Affects: kexec-tools (Ubuntu)
Importance: High
Assignee: Manoj Iyer (manjo)
Status: New
--
You received this bug notification because you are a m
This debdiff applies cleanly and builds
https://pastebin.canonical.com/181891/
** Patch added: "[Xenial] kexec fix armhf build failure"
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1671246/+attachment/4834009/+files/xenial-kexec-tools-armhf-build.patch
--
You received this bug
This debdiff applies and builds cleanly
https://pastebin.canonical.com/181893/ on armhf
** Patch added: "[Yakkety] kexec fix armhf build failure"
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1671246/+attachment/4834067/+files/yakkety-kexec-tools-armhf-build.patch
** Changed
~ # rmmod qcom_emac
~ # modprobe qcom_emac
~ # dmesg | tail -n 15
[ 211.382709] Atheros 8031 ethernet QCOM8070:00:04: attached PHY driver
[Atheros 8031 ethernet] (mii_bus:phy_addr=QCOM8070:00:04, irq=-2)
[ 211.382789] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 4479.862691] Atheros
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
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/1680549
Title:
[Zesty] QDF2400 ARM64 server - NMI watchdog: BUG: soft
Based on the last comment making this bug invalid.
** Changed in: makedumpfile (Ubuntu)
Status: New => Invalid
** Changed in: makedumpfile (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => (unassigned)
--
You received this bug notification because you are a member of Kernel
/proc/vmcore is generated by kdump support in the kernel. This might not
be a bug, but a case of missing support for regenerating /proc/vmcore
entries after DLPAR memory removal.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Yakkety Proposed Testing]
ubuntu@test:~$ cat /etc/issue
Ubuntu 16.10 \n \l
ubuntu@test:~$ sudo apt policy kexec-tools
kexec-tools:
Installed: (none)
Candidate: 1:2.0.10-2ubuntu1.1
Version table:
1:2.0.10-2ubuntu1.1 500
500 http://ports.ubuntu.com/ubuntu-ports
[Xenial Proposed Testing]
ubuntu@ubuntu:~$ sudo apt policy kexec-tools
kexec-tools:
Installed: (none)
Candidate: 1:2.0.10-1ubuntu2.1
Version table:
1:2.0.10-1ubuntu2.1 500
500 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main arm64
Packages
ubuntu@ubuntu:~$ sudo kexec
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => (unassigned)
--
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/1486152
Title:
Kernel WARN @
Timur found that the at803x module (needed for an erratum) is the reason
we are unable to get a dhcp lease on the emac interface. He is exploring
his options on fixing the issue, ie have a an option to pass in a phy
driver if the erratum is encountered. We found that on my SDP we did not
need the
I got the following review comments for SRU from kernel team. IBM could
you please comment?
Looking at upstream 4.9.y, I see the patches to the ibmvscsis driver [2-4]
applied but not the change to the genric target driver. And I am not seeing any
justification why patch #1 is strictly required.
** Tags added: triage-a
--
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/1680349
Title:
Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine
crashes while running
** Tags added: triage-a
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1676884
Title:
kdump-tools uses the wrong crashkernel command line parameter in
ppc64le
Status in The
** Tags added: triage-g
--
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/1678745
Title:
Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c
Status in The Ubuntu-power-systems
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
** Tags added: triage-g
--
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/1680888
Title:
Disable
** Tags added: triage-g
** Changed in: ubuntu-power-systems
Status: Incomplete => Fix Committed
--
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/1677685
Title:
[SRU Zesty] Target:
** Tags added: triage-a
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
is configured on
** Summary changed:
- Possible to turn on 16g huge pages on Ubuntu 16.04.2 PowerNV
+ It should not be possible to turn on 16g huge pages on Ubuntu 16.04.2 PowerNV
** Tags added: triage-g
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags added: triage-g
--
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/1689946
Title:
Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with
split op
Status in The
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Canonical Kernel Team (canonical-kernel-team)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: triage-g
--
You received this bug notification because you
** Tags added: triage-g
--
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/1684054
Title:
[LTCTest][Opal][FW860.20] HMI recoverable errors failed to recover and
system goes to dump state.
** Changed in: kernel-package (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Ubuntu on IBM Power
Systems Bug Triage (ubuntu-power-triage)
** Tags added: triage-g
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Tags added: triage-g
--
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/1689360
Title:
TCMU: Fix possible overwrite of t_data_sg's last iov[] and wrongly
calculating base_command_size
** Tags added: triage-a
--
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/1667245
Title:
ISST-LTE:pVM:roselp4:ubuntu 17.04: kdump failed after memory DLPAR
Status in The
** Tags added: triage-a
** Changed in: makedumpfile (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => Ubuntu on IBM Power
Systems Bug Triage (ubuntu-power-triage)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed
1 - 100 of 1113 matches
Mail list logo
