I sent the requested report. And indeed received a new patch to be
tested. In progress...
Le 02/04/2023 à 10:30, Diederik de Haas a écrit :
On Sunday, 2 April 2023 00:24:26 CEST Diederik de Haas wrote:
2) The commit that Bjørn identified also contained a "Link:" tag:
On Sunday, 2 April 2023 00:24:26 CEST Diederik de Haas wrote:
> 2) The commit that Bjørn identified also contained a "Link:" tag:
> https://lore.kernel.org/r/20230105041059.39366-1-kvija...@amd.com
>
> The best thing to do is to respond to that thread and explain the issue you
> ran into.
If you
Processing control commands:
> tag -1 upstream
Bug #1033732 [src:linux] linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64
kernel launching crashes with a panic message
Added tag(s) upstream.
--
1033732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033732
Debian Bug Tracking System
Control: tag -1 upstream
On Saturday, 1 April 2023 22:47:35 CEST Guy Durrieu wrote:
> I just finished to build the patched kernel.
Well done!
> After installing it, the system 6.1.0-7 boots again and run fine.
> Thus the source was well identified by Bjørn Mork.
This is great :-)
> I just
Hello everybody,
I just finished to build the patched kernel. After installing it, the
system 6.1.0-7 boots again and run fine. Thus the source was well
identified by Bjørn Mork. I just had problems trying to install
linux-headers-6.1.0-7-amd64_6.1.20-1a~test_amd64.deb, for dependencies
Thanks for your help !
That was more or less my conclusion, but it would indeed be useful to
clarify that 4.1 and 4.21. are mutually exclusive.
And I must admit that the # vs $ steps had escaped me :(
Best regards.
-- Guy
Le 01/04/2023 à 18:56, Diederik de Haas a écrit :
On Saturday, 1
Thanks for your help !
That was more or less my conclusion, but it would indeed be useful to
clarify that 4.1 and 4.21. are mutually exclusive.
And I must admit that the # vs $ steps had escaped me :(
Best regards.
-- Guy
Le 01/04/2023 à 18:56, Diederik de Haas a écrit :
On Saturday, 1
On Saturday, 1 April 2023 17:44:21 CEST Guy Durrieu wrote:
> I am in trouble... I first did "Obtaining the kernel source", and at the
> end I got a /root/linux-source-6.1/ directory.
>
> Then I did "Rebuilding official Debian kernel packages" and
> "Preparation", and then I got among others a
>
I am in trouble... I first did "Obtaining the kernel source", and at the
end I got a /root/linux-source-6.1/ directory.
Then I did "Rebuilding official Debian kernel packages" and
"Preparation", and then I got among others a
/root/linux-source-6.1/linux-6.1.20 the content of which is
On April 1, 2023 4:31:49 PM GMT+02:00, Guy Durrieu
wrote:
>Thanks for your help !
>
>There is something not clear for me in the section 4.2.2. Simple patching and
>building...
>
>I ran apt-get install devscripts but I can't find any debian directory nor
>patches. Is it sufficient to apply
Thanks for your help !
There is something not clear for me in the section 4.2.2. Simple
patching and building...
I ran apt-get install devscripts but I can't find any debian directory
nor patches. Is it sufficient to apply the patch given by Diederik de Haas ?
Regards.
-- Guy
Le
Hi,
On Sat, Apr 01, 2023 at 11:51:38AM +0200, Guy Durrieu wrote:
> Hello,
>
> This is something I have never done, but I can try.
>
> However some time ago, for solving a previous issue, a guy from Debian
> compiled for me an unofficial release including the patch to be tested,
> along with
Salvatore Bonaccorso writes:
> AFAIK there is no commit upstream with fixes tag on that commit. But
> Bjorn suspects that might be the suspicious commit introducing the
> issue.
Yes, I noticed that, so I could very well be wrong...
But it stood out as the only change to any x86 IOAPIC stuff
Hello,
This is something I have never done, but I can try.
However some time ago, for solving a previous issue, a guy from Debian
compiled for me an unofficial release including the patch to be tested,
along with some credentials. I know this is not the recommended
procedure :) but it
Processing control commands:
> tags -1 + moreinfo
Bug #1033732 [src:linux] linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64
kernel launching crashes with a panic message
Added tag(s) moreinfo.
--
1033732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033732
Debian Bug Tracking System
Control: tags -1 + moreinfo
Hi Guy,
On Sat, Apr 01, 2023 at 10:09:09AM +0200, Guy Durrieu wrote:
> Hello,
>
> Thanks for your answer !
>
> Before receiving it I tried to update my BIOS to the last available version
> (F51h). Without any effect.
>
> I am not sure I understand everything that
On Saturday, 1 April 2023 10:09:09 CEST Guy Durrieu wrote:
> Le 01/04/2023 à 09:25, Bjørn Mork a écrit :
> > Guy Durrieu writes:
> >>
> >> [ 0.117782] Kernel panic — not syncing: timer doesn’t work through
> >> Interrupt-
> >> remapped I0-APIC
> >> [ 0.117848] CPU: 0 PID: 0 Comm: swapper/0
Hello,
Thanks for your answer !
Before receiving it I tried to update my BIOS to the last available
version (F51h). Without any effect.
I am not sure I understand everything that is said in your link, except
I must wait for the next updates... Right ?
Best regards.
-- Guy
Le 01/04/2023
Guy Durrieu writes:
>
> [ 0.117782] Kernel panic — not syncing: timer doesn’t work through
> Interrupt-
> remapped I0-APIC
> [ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1
> Debian
> 6.1.20-1
> [ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming
Package: src:linux
Version: 6.1.20-1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
Up to now I worked with Linux 6.1.0-7-amd64, without any trouble. I just
installed Linux 6.1.0-7-amd64 and I get a kernel panic when launching it.
Here is a transcription of what
20 matches
Mail list logo
