Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #86546 > unrolled thread

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

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#988688: workaround for bug 988688 - disable security chip Salvatore Bonaccorso <carnil@debian.org> - 2025-03-22 14:30 +0100
    Bug#988688: workaround for bug 988688 - disable security chip "Jonathan Dowland" <jmtd@debian.org> - 2025-04-29 11:50 +0200
      Bug#988688: workaround for bug 988688 - disable security chip Salvatore Bonaccorso <carnil@debian.org> - 2025-04-30 16:50 +0200
        Bug#988688: workaround for bug 988688 - disable security chip Salvatore Bonaccorso <carnil@debian.org> - 2025-09-13 22:50 +0200
          Bug#988688: workaround for bug 988688 - disable security chip Salvatore Bonaccorso <carnil@debian.org> - 2025-11-01 21:00 +0100
            Bug#988688: workaround for bug 988688 - disable security chip Salvatore Bonaccorso <carnil@debian.org> - 2025-11-02 16:10 +0100

#86546 — Bug#988688: workaround for bug 988688 - disable security chip

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

[toc] | [next] | [standalone]

#87123

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

[toc] | [prev] | [next] | [standalone]

#87149

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

[toc] | [prev] | [next] | [standalone]

#89234

Hi Jonathan,

On Wed, Apr 30, 2025 at 04:38:49PM +0200, Salvatore Bonaccorso wrote:
> 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.

Did you had a chance to look into this? otherwise as stated earlier it
it would be helpful to not keep bugs open for years and close it.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#89881

Hi Jonathan,

On Sat, Sep 13, 2025 at 10:43:26PM +0200, Salvatore Bonaccorso wrote:
> Hi Jonathan,
> 
> On Wed, Apr 30, 2025 at 04:38:49PM +0200, Salvatore Bonaccorso wrote:
> > 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.
> 
> Did you had a chance to look into this? otherwise as stated earlier it
> it would be helpful to not keep bugs open for years and close it.

Any news here? Or should/can we go ahead and close the bug?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#89897

Hi Jonathan,

On Sun, Nov 02, 2025 at 02:00:46PM +0000, Jonathan Dowland wrote:
> Hi Salvatore,
> 
> On Sat Nov 1, 2025 at 7:54 PM GMT, Salvatore Bonaccorso wrote:
> > Any news here? Or should/can we go ahead and close the bug?
> 
> Let's close it. If/when I manage to carve out time to investigate more, I
> can always re-open. Sorry for wasting your time.

Thank you for your feedback! Ok let's do that. 

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web