[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-06-11 Thread Launchpad Bug Tracker
This bug was fixed in the package makedumpfile - 1:1.6.3-2~16.04.1

---
makedumpfile (1:1.6.3-2~16.04.1) xenial; urgency=medium

  * Backport latest makedumpfile to xenial. (LP: #1746299)
  * Revert to build-depending on dh-systemd, as xenial does not have
debhelper >= 9.20160709.

 -- Thadeu Lima de Souza Cascardo   Mon, 21 May
2018 11:02:15 -0300

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: Fix Committed => 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/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in makedumpfile source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

  break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
  a0b1280368d1e91ab72f849ef095b4f07a39bbf1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-06-11 Thread Launchpad Bug Tracker
This bug was fixed in the package makedumpfile - 1:1.6.3-2~17.10.1

---
makedumpfile (1:1.6.3-2~17.10.1) artful; urgency=medium

  * Backport latest makedumpfile to artful. (LP: #1746299)

 -- Thadeu Lima de Souza Cascardo   Mon, 21 May
2018 10:56:29 -0300

** Changed in: makedumpfile (Ubuntu Artful)
   Status: Fix Committed => 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/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Released
Status in makedumpfile source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

  break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
  a0b1280368d1e91ab72f849ef095b4f07a39bbf1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-06-04 Thread Thadeu Lima de Souza Cascardo
I will verify this works with makedumpfile on -proposed.

** Changed in: makedumpfile (Ubuntu Artful)
   Status: New => Fix Committed

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed-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/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Released
Status in makedumpfile source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

  break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
  a0b1280368d1e91ab72f849ef095b4f07a39bbf1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package makedumpfile - 1:1.6.3-2

---
makedumpfile (1:1.6.3-2) unstable; urgency=medium

  * Add support for SPARSEMEM_EXTREME mem_section as a pointer. (LP: #1750021)
  * Add an autopkgtest that test that a crash produces a compressed dump
file.
  * Create initrd for previously installed kernels. (LP: #1751329)

 -- Thadeu Lima de Souza Cascardo   Mon, 05 Mar
2018 09:28:55 -0300

** Changed in: makedumpfile (Ubuntu Bionic)
   Status: In Progress => 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/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Artful:
  Fix Released
Status in makedumpfile source package in Artful:
  New
Status in linux source package in Bionic:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

  break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
  a0b1280368d1e91ab72f849ef095b4f07a39bbf1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.13.0-38.43

---
linux (4.13.0-38.43) artful; urgency=medium

  * linux: 4.13.0-38.43 -proposed tracker (LP: #1755762)

  * Servers going OOM after updating kernel from 4.10 to 4.13 (LP: #1748408)
- i40e: Fix memory leak related filter programming status
- i40e: Add programming descriptors to cleaned_count

  * [SRU] Lenovo E41 Mic mute hotkey is not responding (LP: #1753347)
- platform/x86: ideapad-laptop: Increase timeout to wait for EC answer

  * fails to dump with latest kpti fixes (LP: #1750021)
- kdump: write correct address of mem_section into vmcoreinfo

  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289
- ALSA: hda - Fix headset mic detection problem for two Dell machines
- ALSA: hda - Fix a wrong FIXUP for alc289 on Dell machines

  * CIFS SMB2/SMB3 does not work for domain based DFS (LP: #1747572)
- CIFS: make IPC a regular tcon
- CIFS: use tcon_ipc instead of use_ipc parameter of SMB2_ioctl
- CIFS: dump IPC tcon in debug proc file

  * i2c-thunderx: erroneous error message "unhandled state: 0" (LP: #1754076)
- i2c: octeon: Prevent error message on bus error

  * hisi_sas: Add disk LED support (LP: #1752695)
- scsi: hisi_sas: directly attached disk LED feature for v2 hw

  * EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs
entries with KNL SNC2/SNC4 mode) (LP: #1743856)
- EDAC, sb_edac: Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode

  * [regression] Colour banding and artefacts appear system-wide on an Asus
Zenbook UX303LA with Intel HD 4400 graphics (LP: #1749420)
- drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA

  * DVB Card with SAA7146 chipset not working (LP: #1742316)
- vmalloc: fix __GFP_HIGHMEM usage for vmalloc_32 on 32b systems

  * [Asus UX360UA] battery status in unity-panel is not changing when battery is
being charged (LP: #1661876) // AC adapter status not detected on Asus
ZenBook UX410UAK (LP: #1745032)
- ACPI / battery: Add quirk for Asus UX360UA and UX410UAK

  * ASUS UX305LA - Battery state not detected correctly (LP: #1482390)
- ACPI / battery: Add quirk for Asus GL502VSK and UX305LA

  * support thunderx2 vendor pmu events (LP: #1747523)
- perf pmu: Extract function to get JSON alias map
- perf pmu: Pass pmu as a parameter to get_cpuid_str()
- perf tools arm64: Add support for get_cpuid_str function.
- perf pmu: Add helper function is_pmu_core to detect PMU CORE devices
- perf vendor events arm64: Add ThunderX2 implementation defined pmu core
  events
- perf pmu: Add check for valid cpuid in perf_pmu__find_map()

  * lpfc.ko module doesn't work (LP: #1746970)
- scsi: lpfc: Fix loop mode target discovery

  * Ubuntu 17.10 crashes on vmalloc.c (LP: #1739498)
- powerpc/mm/book3s64: Make KERN_IO_START a variable
- powerpc/mm/slb: Move comment next to the code it's referring to
- powerpc/mm/hash64: Make vmalloc 56T on hash

  * ethtool -p fails to light NIC LED on HiSilicon D05 systems (LP: #1748567)
- net: hns: add ACPI mode support for ethtool -p

  * CVE-2017-17807
- KEYS: add missing permission check for request_key() destination

  * [Artful SRU] Fix capsule update regression (LP: #1746019)
- efi/capsule-loader: Reinstate virtual capsule mapping

  * [Artful/Bionic] [Config] enable EDAC_GHES for ARM64 (LP: #1747746)
- Ubuntu: [Config] enable EDAC_GHES for ARM64

  * linux-tools: perf incorrectly linking libbfd (LP: #1748922)
- SAUCE: tools -- add ability to disable libbfd
- [Packaging] correct disablement of libbfd

  * Cherry pick c96f5471ce7d for delayacct fix (LP: #1747769)
- delayacct: Account blkio completion on the correct task

  * Error in CPU frequency reporting when nominal and min pstates are same
(cpufreq) (LP: #1746174)
- cpufreq: powernv: Dont assume distinct pstate values for nominal and pmin

  * retpoline abi files are empty on i386 (LP: #1751021)
- [Packaging] retpoline-extract -- instantiate retpoline files for i386
- [Packaging] final-checks -- sanity checking ABI contents
- [Packaging] final-checks -- check for empty retpoline files

  * [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping
different pmu events using perf fuzzer . (perf:) (LP: #1746225)
- powerpc/perf: Fix oops when grouping different pmu events

  * bnx2x_attn_int_deasserted3:4323 MC assert! (LP: #1715519) //
CVE-2018-126
- net: create skb_gso_validate_mac_len()
- bnx2x: disable GSO where gso_size is too big for hardware

  * Ubuntu16.04.03: ISAv3 initialize MMU registers before setting partition
table (LP: #1736145)
- powerpc/64s: Initialize ISAv3 MMU registers before setting partition table

  * powerpc/powernv: Flush console before platform error reboot (LP: #1735159)
- 

[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-03-19 Thread Stefan Bader
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-
artful'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-artful

-- 
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/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Artful:
  Fix Committed
Status in makedumpfile source package in Artful:
  New
Status in linux source package in Bionic:
  Fix Released
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

  break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
  a0b1280368d1e91ab72f849ef095b4f07a39bbf1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-03-13 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Artful)
   Status: New => Fix Committed

-- 
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/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Artful:
  Fix Committed
Status in makedumpfile source package in Artful:
  New
Status in linux source package in Bionic:
  Fix Released
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

  break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
  a0b1280368d1e91ab72f849ef095b4f07a39bbf1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-03-05 Thread Thadeu Lima de Souza Cascardo
Xenial does not have 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4. Though,
linux-hwe 4.13 has been shipped for Xenial. So, on the kernel side,
there is nothing to fix on our 4.4 kernels, but on the makedumpfile
side, that still needs to be fixed if we want to have some of those
kernels dumpable.

** Description changed:

  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.
  
  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions won't
  be dumpable. A solution for makedumpfile should be done as well.
  
  Cascardo.
+ 
+ break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
+ a0b1280368d1e91ab72f849ef095b4f07a39bbf1

** Tags removed: kernel-da-key
** Tags added: kernel-bug-break-fix

** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => Fix Released

** Changed in: linux (Ubuntu Xenial)
   Status: New => Invalid

-- 
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/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in makedumpfile source package in Artful:
  New
Status in linux source package in Bionic:
  Fix Released
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

  break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
  a0b1280368d1e91ab72f849ef095b4f07a39bbf1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-02-20 Thread Joseph Salisbury
** 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.launchpad.net/bugs/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in makedumpfile source package in Artful:
  New
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-02-16 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

-- 
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/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in makedumpfile source package in Artful:
  New
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-02-16 Thread Thadeu Lima de Souza Cascardo
Now building on my ppa:

sudo add-apt-repository ppa:cascardo/ppa
sudo apt-get update

-- 
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/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in makedumpfile source package in Artful:
  New
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-02-16 Thread Thadeu Lima de Souza Cascardo
** Patch added: "debdiff containing a patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+attachment/5056827/+files/makedumpfile_1.6.3-1ubuntu1.debdiff

-- 
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/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in makedumpfile source package in Artful:
  New
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-02-16 Thread Thadeu Lima de Souza Cascardo
I intend to send this fix upstream and test it with more kernel
versions. At least added with a 4.13 kernel without the patch and one
with the patch.

-- 
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/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in makedumpfile source package in Artful:
  New
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

2018-02-16 Thread Thadeu Lima de Souza Cascardo
Linux needs commit a0b1280368d1e91ab72f849ef095b4f07a39bbf1 ("kdump:
write correct address of mem_section into vmcoreinfo").

** Changed in: makedumpfile (Ubuntu)
   Status: New => In Progress

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
   Status: Confirmed

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
   Status: In Progress

** Also affects: linux (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: makedumpfile (Ubuntu Artful)
   Importance: Undecided
   Status: New

-- 
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/1750021

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Artful:
  New
Status in makedumpfile source package in Artful:
  New
Status in linux source package in Bionic:
  Confirmed
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750021/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp