1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#988688: workaround for bug 988688 - disable security chip

    From Salvatore Bonaccorso@21:1/5 to Jonathan Dowland on Sat Mar 22 14:30:02 2025
    XPost: linux.debian.kernel

    Hi Jonathan,

    On Fri, Mar 07, 2025 at 10:18:46PM +0000, Jonathan Dowland wrote:
    There are some related reports in Ubuntu. Note that for a while, Ubuntu kernels worked where Debian ones did not, but modern Ubuntu kernels have stopped working.

    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970290
    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963802

    The workarounds there (disable security chip in BIOS) work for me on 6.12.12-1.

    Since the 22.04-era kernel worked without the workaround, I have some hope
    we can figure out why (what did Ubuntu include in that kernel that Debian didn't? What did they take out between then and 24.10? What's the intersection
    of those two sets?)

    BTH, I do not think its worth given the amount of open bugs we have
    for src:linux and htis seems quite hardware dependent, for which we
    need anyway much help from an affected user. That is, is you feel
    strong about the issue still beeing adressed you might try to "bisect"
    where things have changed in Ubuntu kernel and isolate the change
    where that happened that it is now not working as well on them.

    And then once it's isolated verify again a most recent version as
    possible and report it upstream.

    Please do not get me wrong, hopefully I could make the position for us
    clear. I just do not see what we could do here.

    Regards,
    Salvatore

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jonathan Dowland@21:1/5 to Salvatore Bonaccorso on Tue Apr 29 11:50:01 2025
    XPost: linux.debian.kernel

    Hi Salvatore,

    Sorry I have not responded yet, I've been too busy and had to prioritise
    other things.

    On Thu Apr 24, 2025 at 1:57 PM BST, Salvatore Bonaccorso wrote:
    Accordingly going to close now the bug. If you feel though strongly
    taht it is not okay please *do* reopen, but in that case we really
    would need your help for the above.

    I intend to work on this post-Trixie. I personally would find it useful
    if the bug was open: Between first discovering it, and finding the bug
    and useful information in it; and when I hit the bug a second time, a
    year or more later, it took me longer to find the useful information
    because the bug was closed and archived. However, I won't re-open it
    myself without your consent.


    --

    👱🏻 Jonathan Dowland
    ✎ jmtd@debian.org
    🔗 https://jmtd.net

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Salvatore Bonaccorso@21:1/5 to Jonathan Dowland on Wed Apr 30 16:50:02 2025
    XPost: linux.debian.kernel

    Hi Jonathan,

    On Tue, Apr 29, 2025 at 10:40:28AM +0100, Jonathan Dowland wrote:

    Hi Salvatore,

    Sorry I have not responded yet, I've been too busy and had to prioritise other things.

    On Thu Apr 24, 2025 at 1:57 PM BST, Salvatore Bonaccorso wrote:
    Accordingly going to close now the bug. If you feel though strongly
    taht it is not okay please *do* reopen, but in that case we really
    would need your help for the above.

    I intend to work on this post-Trixie. I personally would find it useful if the bug was open: Between first discovering it, and finding the bug and useful information in it; and when I hit the bug a second time, a year or more later, it took me longer to find the useful information because the bug was closed and archived. However, I won't re-open it myself without your consent.

    Given you have a clear intent to work on it post-trixie, let's reopen
    it. I do not want to hide things, just make things more easy for us
    for issues which are not anymore relevant.

    With your above statement, lets keep it open for now.

    Regards,
    Salvatore

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)