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

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

Bug#1109116:

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#1109116:  Asho Yeh - 信佑 <ashoyeh@gmail.com> - 2025-07-25 08:10 +0200
    Bug#1109116:  Salvatore Bonaccorso <carnil@debian.org> - 2025-07-27 17:00 +0200
      Processed: Re: Bug#1109116: "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-07-27 17:00 +0200
      Bug#1109116:  Salvatore Bonaccorso <carnil@debian.org> - 2025-07-29 17:30 +0200
        Bug#1109116:  Asho Yeh - 信佑 <ashoyeh@gmail.com> - 2025-07-29 18:00 +0200
          Bug#1109116:  Asho Yeh - 信佑 <ashoyeh@gmail.com> - 2025-07-29 18:10 +0200
            Bug#1109116:  Asho Yeh - 信佑 <ashoyeh@gmail.com> - 2025-07-30 05:00 +0200

#88540 — Bug#1109116:

[Multipart message — attachments visible in raw view] — view raw

I found that this condition happened from the upstream kernel. I checked
kernel 6.12.35 ~ 6.12.40, they all had the same issues.

Maybe we can only wait until upstream fixes or upgrade to kernel-6.15.

Debian 13 is about to be released, shipping with the 6.12 kernel.
Unfortunately, after installation, it was found that the Intel B580
graphics card is not supported, which is quite a pity.

[toc] | [next] | [standalone]

#88558

Control: tags -1 + moreinfo
Control: found -1 6.12.39-1

Hi,

On Fri, Jul 25, 2025 at 01:59:09PM +0800, Asho Yeh - 信佑 wrote:
> I found that this condition happened from the upstream kernel. I checked
> kernel 6.12.35 ~ 6.12.40, they all had the same issues.
> 
> Maybe we can only wait until upstream fixes or upgrade to kernel-6.15.
> 
> Debian 13 is about to be released, shipping with the 6.12 kernel.
> Unfortunately, after installation, it was found that the Intel B580
> graphics card is not supported, which is quite a pity.

Can you bisect the changes between 6.12.33 and 6.12.35 upstream to
identify the breaking commit and report it back here?

Regards,
Salvatore

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

#88560 — Processed: Re: Bug#1109116:

Processing control commands:

> tags -1 + moreinfo
Bug #1109116 [src:linux] linux-image-6.12.35+deb13-amd64: The system cannot be fully booted, the system hangs before loading the graphical environment.
Added tag(s) moreinfo.
> found -1 6.12.39-1
Bug #1109116 [src:linux] linux-image-6.12.35+deb13-amd64: The system cannot be fully booted, the system hangs before loading the graphical environment.
The source 'linux' and version '6.12.39-1' do not appear to match any binary packages
Marked as found in versions linux/6.12.39-1.

-- 
1109116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109116
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

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

#88582

Hi,

On Tue, Jul 29, 2025 at 11:15:50PM +0800, Asho Yeh - 信佑 wrote:
> Hi,
> 
> I made a patch with B580 support.
> Tested with kernel-6.12.35-deb13-amd64 and 6.12.38-deb13-amd64.
> 
> I am not drm or gpu expert. Just digged the source code and found some
> differences.
> Hope this can help.

have you seen my earlier question?

As you were able to test upstream version, can you please bisect the
changes between 6.12.33 and 6.12.35 to identify the breaking ocmmit
and then report it back here?

Regards,
Salvatore

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

#88583

[Multipart message — attachments visible in raw view] — view raw

Hi,

I downloaded 6.12.34, 6.12.35, 6.12.38, 6.12.40 from kernel.org.

For kernel versions earlier than 6.12.34, during boot, dmesg shows the
following:

"
xe 0000:03:00.0: [drm] Using GuC firmware from xe/bmg_guc_70.bin version 70.40.2
xe 0000:03:00.0: [drm] Using GuC firmware from xe/bmg_guc_70.bin version 70.40.2
xe 0000:03:00.0: [drm] Using HuC firmware from xe/bmg_huc.bin version 8.2.1
0
xe 0000:03:00.0: [drm] Found BATTLEMAGE (device ID e20b) display
version 14.01 stepping B0

"

For kernel versions 6.12.35 and above, during boot, dmesg shows:
"xe 0000:03:00.0: probe with driver xe failed with error -110"

(Note: To check this, need to SSH into the system from another computer to
run dmesg.)

This is what I’ve observed, though I’m not sure if it matches the
information from Salvatore.
As for which commit caused this, I’m not sure. I manually compared the
source code across versions and created the patch mentioned in my previous
mail.

Regards,

Asho
Salvatore Bonaccorso <carnil@debian.org> 於 2025年7月29日 週二 下午11:23寫道：

> Hi,
>
> On Tue, Jul 29, 2025 at 11:15:50PM +0800, Asho Yeh - 信佑 wrote:
> > Hi,
> >
> > I made a patch with B580 support.
> > Tested with kernel-6.12.35-deb13-amd64 and 6.12.38-deb13-amd64.
> >
> > I am not drm or gpu expert. Just digged the source code and found some
> > differences.
> > Hope this can help.
>
> have you seen my earlier question?
>
> As you were able to test upstream version, can you please bisect the
> changes between 6.12.33 and 6.12.35 to identify the breaking ocmmit
> and then report it back here?
>
> Regards,
> Salvatore
>

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

#88584

[Multipart message — attachments visible in raw view] — view raw

I will try "git bisect" to find which commit cause this bug.

Asho Yeh - 信佑 <ashoyeh@gmail.com> 於 2025年7月29日 週二 下午11:51寫道：

> Hi,
>
> I downloaded 6.12.34, 6.12.35, 6.12.38, 6.12.40 from kernel.org.
>
> For kernel versions earlier than 6.12.34, during boot, dmesg shows the
> following:
>
> "
> xe 0000:03:00.0: [drm] Using GuC firmware from xe/bmg_guc_70.bin version 70.40.2
> xe 0000:03:00.0: [drm] Using GuC firmware from xe/bmg_guc_70.bin version 70.40.2
> xe 0000:03:00.0: [drm] Using HuC firmware from xe/bmg_huc.bin version 8.2.10
> xe 0000:03:00.0: [drm] Found BATTLEMAGE (device ID e20b) display version 14.01 stepping B0
>
> "
>
> For kernel versions 6.12.35 and above, during boot, dmesg shows:
> "xe 0000:03:00.0: probe with driver xe failed with error -110"
>
> (Note: To check this, need to SSH into the system from another computer to
> run dmesg.)
>
> This is what I’ve observed, though I’m not sure if it matches the
> information from Salvatore.
> As for which commit caused this, I’m not sure. I manually compared the
> source code across versions and created the patch mentioned in my previous
> mail.
>
> Regards,
>
> Asho
> Salvatore Bonaccorso <carnil@debian.org> 於 2025年7月29日 週二 下午11:23寫道：
>
>> Hi,
>>
>> On Tue, Jul 29, 2025 at 11:15:50PM +0800, Asho Yeh - 信佑 wrote:
>> > Hi,
>> >
>> > I made a patch with B580 support.
>> > Tested with kernel-6.12.35-deb13-amd64 and 6.12.38-deb13-amd64.
>> >
>> > I am not drm or gpu expert. Just digged the source code and found some
>> > differences.
>> > Hope this can help.
>>
>> have you seen my earlier question?
>>
>> As you were able to test upstream version, can you please bisect the
>> changes between 6.12.33 and 6.12.35 to identify the breaking ocmmit
>> and then report it back here?
>>
>> Regards,
>> Salvatore
>>
>

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

#88592

[Multipart message — attachments visible in raw view] — view raw

Hi,

These are git bisect log:

$ git bisect bad
d42b44736ea29fa6d0c3cb9c75569314134b7732 is the first bad commit
commit d42b44736ea29fa6d0c3cb9c75569314134b7732 (HEAD)
Author: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Date:   Mon Oct 14 13:25:44 2024 +0530

    drm/xe/gt: Update handling of xe_force_wake_get return

    [ Upstream commit 30d105577a3319094f8ae5ff1ceea670f1931487 ]

Regards,
Asho

Asho Yeh - 信佑 <ashoyeh@gmail.com> 於 2025年7月30日 週三 上午12:02寫道：

> I will try "git bisect" to find which commit cause this bug.
>
> Asho Yeh - 信佑 <ashoyeh@gmail.com> 於 2025年7月29日 週二 下午11:51寫道：
>
>> Hi,
>>
>> I downloaded 6.12.34, 6.12.35, 6.12.38, 6.12.40 from kernel.org.
>>
>> For kernel versions earlier than 6.12.34, during boot, dmesg shows the
>> following:
>>
>> "
>> xe 0000:03:00.0: [drm] Using GuC firmware from xe/bmg_guc_70.bin version 70.40.2
>> xe 0000:03:00.0: [drm] Using GuC firmware from xe/bmg_guc_70.bin version 70.40.2
>> xe 0000:03:00.0: [drm] Using HuC firmware from xe/bmg_huc.bin version 8.2.10
>> xe 0000:03:00.0: [drm] Found BATTLEMAGE (device ID e20b) display version 14.01 stepping B0
>>
>> "
>>
>> For kernel versions 6.12.35 and above, during boot, dmesg shows:
>> "xe 0000:03:00.0: probe with driver xe failed with error -110"
>>
>> (Note: To check this, need to SSH into the system from another computer
>> to run dmesg.)
>>
>> This is what I’ve observed, though I’m not sure if it matches the
>> information from Salvatore.
>> As for which commit caused this, I’m not sure. I manually compared the
>> source code across versions and created the patch mentioned in my previous
>> mail.
>>
>> Regards,
>>
>> Asho
>> Salvatore Bonaccorso <carnil@debian.org> 於 2025年7月29日 週二 下午11:23寫道：
>>
>>> Hi,
>>>
>>> On Tue, Jul 29, 2025 at 11:15:50PM +0800, Asho Yeh - 信佑 wrote:
>>> > Hi,
>>> >
>>> > I made a patch with B580 support.
>>> > Tested with kernel-6.12.35-deb13-amd64 and 6.12.38-deb13-amd64.
>>> >
>>> > I am not drm or gpu expert. Just digged the source code and found some
>>> > differences.
>>> > Hope this can help.
>>>
>>> have you seen my earlier question?
>>>
>>> As you were able to test upstream version, can you please bisect the
>>> changes between 6.12.33 and 6.12.35 to identify the breaking ocmmit
>>> and then report it back here?
>>>
>>> Regards,
>>> Salvatore
>>>
>>

[toc] | [prev] | [standalone]

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

csiph-web