[Kernel-packages] [Bug 1990425] Re: Keyboard inoperative on Asus Vivobook S5402ZA

2022-10-11 Thread Kellen Renshaw
*** This bug is a duplicate of bug 1992266 *** https://bugs.launchpad.net/bugs/1992266 ** This bug has been marked a duplicate of bug 1992266 input/keyboard: the keyboard on some Asus laptops can't work -- You received this bug notification because you are a member of Kernel Packages,

[Kernel-packages] [Bug 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work

2022-10-11 Thread Kellen Renshaw
Marked LP#1990425 as a duplicate of this one, since the patches include that patch. -- 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/1992266 Title: input/keyboard: the keyboard on some

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

2022-09-28 Thread Kellen Renshaw
Thanks Dann! Oof, the links didn't make it from the draft document, fixed now. If I understand your previous comment correctly, a better variant of this testing procedure would be a regression testing checklist against a library (linked to in the page) of dump files and a single manual test of

[Kernel-packages] [Bug 1990425] Re: Keyboard inoperative on Asus Vivobook S5402ZA

2022-09-28 Thread Kellen Renshaw
** Description changed: [Impact] * The builtin keyboard on the Asus S5402ZA doesn't work with any currently released kernel. [Fix] * 6e5cbe7c4b41824e500acbb42411da692d1435f1 ACPI: resource: Add ASUS model S5402ZA to quirks   *

[Kernel-packages] [Bug 1990425] Re: Keyboard inoperative on Asus Vivobook S5402ZA

2022-09-28 Thread Kellen Renshaw
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete -- You received this bug notification

[Kernel-packages] [Bug 1990425] Re: Keyboard inoperative on Asus Vivobook S5402ZA

2022-09-28 Thread Kellen Renshaw
** Description changed: - The builtin keyboard on the Asus S5402ZA doesn't work with the 5.15 - kernel in Jammy Jellyfish. + [Impact] - Adapting the patch from - https://bugzilla.kernel.org/show_bug.cgi?id=216158 and applying to the - 5.15 kernel allows the keyboard to work. + * The builtin

[Kernel-packages] [Bug 1990425] Re: Keyboard inoperative on Asus Vivobook S5402ZA

2022-09-28 Thread Kellen Renshaw
Fix accepted upstream: https://lore.kernel.org/linux- acpi/CAJZ5v0g=x2cbofjoufod6_4nlhhrqofmm+4bhtwfifvggnc...@mail.gmail.com/T/#t ** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

2022-09-23 Thread Kellen Renshaw
I have put up a draft SRU exception page at https://wiki.ubuntu.com/MakedumpfileUpdates. Comments/edits are welcome. I am working on finding an appropriate place for test vmcores to be stored. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed

[Kernel-packages] [Bug 1990425] [NEW] Keyboard inoperative on Asus Vivobook S5402ZA

2022-09-21 Thread Kellen Renshaw
Public bug reported: The builtin keyboard on the Asus S5402ZA doesn't work with the 5.15 kernel in Jammy Jellyfish. Adapting the patch from https://bugzilla.kernel.org/show_bug.cgi?id=216158 and applying to the 5.15 kernel allows the keyboard to work. ** Affects: linux (Ubuntu) Importance:

[Kernel-packages] [Bug 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter

2022-07-20 Thread Kellen Renshaw
** Description changed: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] - spin up azure vm + Create VM on Azure - sudo apt-get install azure-cli + Install crash dump utilies (from guide: + https://ubuntu.com/server/docs/kernel-crash-dump)

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

2022-05-26 Thread Kellen Renshaw
During a discussion about the potential for autopkgtests it was brought up that a representative sample of unfiltered vmcores would be large (even compressed). This would impose bandwidth and disk space constraints on anyone attempting to run the autopkgtests locally. That tends to make me lean

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

2022-05-25 Thread Kellen Renshaw
Thanks everyone for the awesome input and ideas! I will draft the special case exception and figure out some way to post it here for review. Regarding testing, I really like Dann and Guilherme's idea for automated testing of vmcores. Where would that infrastructure live and how would we maintain

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

2022-05-23 Thread Kellen Renshaw
Hi Guilherme! I have been looking at the possibility of an SRU exception for makedumpfile, although I like your idea better (LTS N to LTS N+1). How would we go about implementing that? I am willing to do the building/testing work, but would need guidance on how to do that and properly

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

2022-04-27 Thread Kellen Renshaw
** Summary changed: - makedumpfile fails with __vtop4_x86_64: Can't get a valid pmd_pte. + makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in

[Kernel-packages] [Bug 1970672] [NEW] makedumpfile fails with __vtop4_x86_64: Can't get a valid pmd_pte.

2022-04-27 Thread Kellen Renshaw
[Where problems could occur] * This change could adversely affect the collection/compression of vmcores during a kdump situation resulting in fallback to cp. ** Affects: makedumpfile (Ubuntu) Importance: Undecided Assignee: Kellen Renshaw (krenshaw) Status: New *

[Kernel-packages] [Bug 1966803] Re: xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename()

2022-04-26 Thread Kellen Renshaw
** Attachment added: "109-xfs-bionic.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966803/+attachment/5584117/+files/109-xfs-bionic.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1966803] Re: xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename()

2022-04-26 Thread Kellen Renshaw
Verification for Bionic Ran the xfstests (https://git.kernel.org/pub/scm/fs/xfs/xfstests- dev.git) on the current 5.4.0-109-generic #123~18.04.1-Ubuntu kernel and the -proposed kernel 5.4.0-110-generic #124~18.04.1-Ubuntu in a VM to exercise the XFS filesystem thoroughly. Detailed log files of

[Kernel-packages] [Bug 1966803] Re: xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename()

2022-04-21 Thread Kellen Renshaw
** Attachment added: "110-xfs.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966803/+attachment/5582132/+files/110-xfs.log ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1966803] Re: xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename()

2022-04-21 Thread Kellen Renshaw
Verification for Focal Ran the xfstests (https://git.kernel.org/pub/scm/fs/xfs/xfstests- dev.git) on the current 5.4.0-109-generic #123-Ubuntu kernel and the -proposed kernel 5.4.0-110-generic #124-Ubuntu in a VM to exercise the XFS filesystem thoroughly. Detailed log files of the tests are

[Kernel-packages] [Bug 1966803] Re: xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename()

2022-03-28 Thread Kellen Renshaw
Unable to run the apport command. ** 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 Ubuntu. https://bugs.launchpad.net/bugs/1966803 Title: xfs: Fix deadlock

[Kernel-packages] [Bug 1966803] Re: xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename()

2022-03-28 Thread Kellen Renshaw
Example backtraces: Mar 4 05:41:40 host kernel: [291932.968664] INFO: task tar:44877 blocked for more than 120 seconds. Mar 4 05:41:40 host kernel: [291932.968826] Tainted: P OE 5.4.0-100-generic #113~18.04.1-Ubuntu Mar 4 05:41:40 host kernel: [291932.969019] "echo 0 >

[Kernel-packages] [Bug 1966803] [NEW] xfs: Fix deadlock between AGI and AGF when target_ip exists in xfs_rename()

2022-03-28 Thread Kellen Renshaw
Public bug reported: SRU Justification: [Impact] * The xfs filesystem suffers from a deadlock issue in kernels < 5.5. This hangs IO to/from the affected filesystem. [Fix] * 93597ae8dac0149b5c00b787cba6bf7ba213e666 93597ae8dac0 "xfs: Fix deadlock between AGI and AGF when target_ip exists in

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-06-22 Thread Kellen Renshaw
** Attachment added: "squashfs" https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272424/+files/squashfs -- 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/1797581 Title:

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-06-22 Thread Kellen Renshaw
** Attachment added: "boot-initrd" https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272416/+files/boot-initrd -- 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/1797581 Title:

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-06-22 Thread Kellen Renshaw
** Attachment added: "host1_dpkg.txt" https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272418/+files/host1_dpkg.txt -- 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/1797581

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-06-22 Thread Kellen Renshaw
** Attachment added: "host2_dpkg.txt" https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272419/+files/host2_dpkg.txt -- 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/1797581

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-06-22 Thread Kellen Renshaw
** Attachment added: "vm2.xml" https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272422/+files/vm2.xml -- 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/1797581 Title:

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-06-22 Thread Kellen Renshaw
** Attachment added: "vm1_console.log" https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272421/+files/vm1_console.log -- 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/1797581

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-06-22 Thread Kellen Renshaw
** Attachment added: "vm2_console.log" https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272423/+files/vm2_console.log -- 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/1797581

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-06-22 Thread Kellen Renshaw
** Attachment added: "vm1.xml" https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272420/+files/vm1.xml -- 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/1797581 Title:

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-06-22 Thread Kellen Renshaw
** Attachment added: "boot-kernel" https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5272417/+files/boot-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/1797581 Title:

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2019-06-22 Thread Kellen Renshaw
Ran into this today, attaching the information requested in #51. Unable to commission/install 18.04 with "No minimum kernel" MAAS version: maas 2.5.3-7533-g65952b418-0ubuntu1~18.04.1 all Guests kernel paniced on two hosts (host1 and host2), dpkg -l attached for each host. Console output from