Hi,
Salvatore Bonaccorso wrote:
> > > Francesco reported that the issue was fixed for him in 5.17.0-2-686 which
> > > corresponds to 5.17.6 upstream kernel.
> > > Petra & Axel: can you verify whether it is also fixed for you?
[…]
> > and installed it with "dpkg -i" on both T41 Thinkpads, and they
Source: linux
Source-Version: 5.17.6-1
On Fri, May 13, 2022 at 09:38:37AM +0200, Petra R.-P. wrote:
> Hello Diederik,
>
> Thanks for the good news:
>
> On Fri 13 May 2022 at 02:19:44 +0200 Diederik de Haas
> wrote:
>
> [...]
>
> > Francesco reported that the issue was fixed for him in 5.1
Hello Diederik,
Thanks for the good news:
On Fri 13 May 2022 at 02:19:44 +0200 Diederik de Haas
wrote:
[...]
> Francesco reported that the issue was fixed for him in 5.17.0-2-686 which
> corresponds to 5.17.6 upstream kernel.
> Petra & Axel: can you verify whether it is also fixed for you
Hi Petra and Axel,
On Thursday, 28 April 2022 09:56:29 CEST Salvatore Bonaccorso wrote:
> Now this gives us probably a good hint!
>
> https://bugzilla.kernel.org/show_bug.cgi?id=215909
>
> d6b88ce2eb9d ("ACPI: processor idle: Allow playing dead in C3 state")
> and a followup commit bfe55a1f7fd6
Hi
After updating linux-image-686 with the latest update (5.17.0-2-686) ,
finally my machine successfully boots. The problem should be solved
also for other people affected by this bug.
P.S. : For other people interested , starting from linux-5.18-rc5-rt4
and beyond ( latest I've built is linux-
Am Sa., 9. Apr. 2022, um 08:20 +0200 schrieb Petra R.-P.
:
> Am Sa., 26. Mär. 2022, um 17:19 +0100 schrieb Petra Rübe-Pugliese
> :
> > On Sat 12 Mar 2022 at 21:31:38 +0100 Petra R.-P.
> > wrote:
> > > On Sat 05 Mar 2022 at 17:59:51 +0100 Petra R.-P.
> > > wrote:
> > > [...]
> > >
> >
Hi
I've done more tests (basically recompiled and installed 2 times the
same kernel) with linux-5.17.5 but I am still having no luck : I can't
figure out why it does not detect the controller ... I've checked the
config and the drivers for the controller (ata_piix , ata_generic )
are built but the
Hi ,
reverting d6b88ce2eb9d ("ACPI: processor idle: Allow playing dead in
C3 state") made kernel version 5.15.35 booting , but still not kernel
version 5.17.5 in my case.
The last one has changed behaviour : now the kernel seems to boot - at
least it is not freezing and key combination works to r
Hi,
On Thu, Apr 28, 2022 at 12:04:50AM +0200, Francesco C wrote:
> Hi ,
>
> 5.16 series is EOL so I've just continued to do tests with vanilla
> linux-5.17.4 and linux-5.17.5 : both do not boot and stop at the same
> point as indicated in the messages above _but_ ... something strange
> is happen
Hi ,
5.16 series is EOL so I've just continued to do tests with vanilla
linux-5.17.4 and linux-5.17.5 : both do not boot and stop at the same
point as indicated in the messages above _but_ ... something strange
is happening also with longterm 5.15 series since version 5.15.35 and
5.15.36 do not bo
Damien Le Moal wrote :
> I posted another patch which disables the read log command for the adapter
> instead of just for your disk. Can you try that one too ?
It did not work in my case ... and neither blacklisting the entire
ICH4 class of pci adapters worked.
Blacklisting components and/or add
Am Sa., 26. Mär. 2022, um 17:19 +0100 schrieb Petra Rübe-Pugliese
:
> On Sat 12 Mar 2022 at 21:31:38 +0100 Petra R.-P.
> wrote:
> > On Sat 05 Mar 2022 at 17:59:51 +0100 Petra R.-P.
> > wrote:
> > [...]
> >
> > The error persists also in linux-image-5.16.0-4-686 (5.16.12-1) .
>
> ... a
I've also tested linux-5.17.1 from experimental but it does not boot
as expected :)
It could be interesting to know if there is any 32 bit pentium-m based
platform with ICH4 controller that boots with any kernel in the range
from 5.16.0 to 5.17.1
Anyway I think I will remain with my custom kernel
Hello everyone
I've tested also a patch based on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006149#260 and
modified simply by adding the disk drive model installed in my machine
to the backlist, but the final result is exactly the same ... the
computer stops booting always at the same poin
Hi people !
Big news here :
- I didn't apply the first patch since the disk drive installed in my
machine is exactly an "old" Western Digital :)
> hdparm -I /dev/sda
!
! /dev/sda:
!
!ATA device, with non-removable media
!Model Number: WDC WD1200BEVE-00WZT0
.
_
Axel Beckert wrote:
> ... but I actually have no idea how to cross-compile a
> kernel package from amd64 to i386.
The 64 bits compiler supports native build of 32 bits binaries through
the -m32 flag so you have just to install kernel build dependencies ,
multilibs support and point to the kernel
On Mon 04 Apr 2022 at 18:09:59 +0900 Damien Le Moal
wrote:
[...]
> hdparm -I /dev/sdX
,-[ 1st T41 ]-
| netty:~# hdparm -I /dev/sda
|
| /dev/sda:
|
| ATA device, with non-removable media
| Model Number: IC25N030ATMR04
Am Mo., 4. Apr. 2022, um 10:05 +0200 schrieb Axel Beckert :
[...]
> "fdisk -l /dev/sda" should suffice.
,-[ 1st T41 ]---
| ~ > fdisk -l /dev/sda
| Disk /dev/sda: 27.95 GiB, 30005821440 bytes, 58605120 sectors
| Disk model: IC25N030ATMR0
Hi Petra,
Petra R.-P. wrote:
> Sorry for the stupid question, but: How can I find out?
> What command shall I enter?
"fdisk -l /dev/sda" should suffice.
Look for a line like this:
Disk model: SAMSUNG HM160HC
It's the second line of output in my case.
Regards, Axel
--
,''`
Am Mo., 4. Apr. 2022, um 16:39 +0900 schrieb Damien Le Moal
:
[...]
> By the way, what is the drive connected on your Thinkpad ? Same as Axel, a
> Samsung HM160HC ? If it is a different drive, then patch 2 (big hammer) may
> be better as this may indicate that the adapter does not like read log
>
Hi Damien,
Damien Le Moal wrote:
> > My T41 Thinkpads only have 500MB of ram and little space left on
> > their hd. Added to that my inexperience and lack of time I'm
> > afraid I cannot be of much help for re-compiling kernels (which
> > AFAIK is quite a stress test for computers).
> > Sorry.
>
Just for the record:
On Mon 04 Apr 2022 at 14:49:05 +0900 Damien Le Moal
wrote:
[...]
> There will be no issue with your 1GB of ram. Giving this amount of ram and
> CPU, step (4) will indeed take a while, but it will run fine.
My T41 Thinkpads only have 500MB of ram and little space left on
th
Hi Damien,
Damien Le Moal wrote:
> > > I will send a patch to blacklist read log for that drive later today, to
> > > try. If that patch works, I will queue it and cc stable so that it gets
> > > backported.
> >
> > I assume this still requires recompilation as this blacklist is
> > probably comp
Hi Damien,
Damien Le Moal wrote:
> My hunch is that this drive simply reacts badly to read log commands
> and should be marked with a horkage to blacklist that command for
> it.
Hrm, do really mean drive or controller? If you really mean "drive",
shall all who are affected by this send in all the
> Did you try the patch that Damien posted here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006149#131
Exactly ... when I write "same behaviour" I mean exactly the same :)
It stops at the same point as shown in the videos , no further
messages ... with a vanilla kernel 5.16.18 with that
On Sunday, 3 April 2022 15:16:06 CEST Francesco C wrote:
> > As you appear to be familiar with kernel building, could you look at the
> > patches that Damien Le Moal posted in this bug report?
>
> Done ... same behaviour : as before the only way to restart the
> machine is by pressing the power bu
> As you appear to be familiar with kernel building, could you look at the
> patches that Damien Le Moal posted in this bug report?
Done ... same behaviour : as before the only way to restart the
machine is by pressing the power button ; Ctl+Alt+Del and Alt+SysReq+b
do not work.
> AFAICT, we're s
On Saturday, 2 April 2022 15:36:53 CEST Francesco C wrote:
> Vanilla kernel 5.16.18 built with custom .config for the specific
> machine fails to boot at the same point too.
As you appear to be familiar with kernel building, could you look at the
patches that Damien Le Moal posted in this bug rep
linux-image-5.16.0-6-686 (5.16.18-1) still does not boot on a
different machine with the same controller.
Vanilla kernel 5.16.18 built with custom .config for the specific
machine fails to boot at the same point too.
I'm also trying to track stable patches in the stable tree queue
(https://git.ke
Hi,
Diederik de Haas wrote:
> I (still) think the most likely culprit is in the ATA/disk subsystem, but the
> progress stalled when the request came in to apply custom patches to the
> kernel (which IIRC was primarily to gather further information).
Yep, and that's still on my TODO list.
On woensdag 30 maart 2022 08:38:30 CEST Salvatore Bonaccorso wrote:
> Do we have a report upstream already about this issue?
What I tried to achieve with my involvement is determining where (exactly) the
problem is to determine which upstream to contact.
I (still) think the most likely culprit is
Am Mi., 30. Mär. 2022, um 08:38 +0200 schrieb Salvatore Bonaccorso
:
[...]
> Thanks for constantly testing the new versions (there is 5.16.18-1
> upcoming btw, or 5.17.1 in experiemntal).
I'm just testing whatever is pulled in automatically by linux-image-686 (in
bookworm).
>
> Do we have a r
Hi,
On Sat, Mar 26, 2022 at 05:19:03PM +0100, Petra Rübe-Pugliese wrote:
> On Sat 12 Mar 2022 at 21:31:38 +0100 Petra R.-P.
> wrote:
> > On Sat 05 Mar 2022 at 17:59:51 +0100 Petra R.-P.
> > wrote:
> > [...]
> >
> > The error persists also in linux-image-5.16.0-4-686 (5.16.12-1) .
>
>
On Sat 12 Mar 2022 at 21:31:38 +0100 Petra R.-P.
wrote:
> On Sat 05 Mar 2022 at 17:59:51 +0100 Petra R.-P.
> wrote:
> [...]
>
> The error persists also in linux-image-5.16.0-4-686 (5.16.12-1) .
... and in linux-image-5.16.0-5-686 (5.16.14-1) ...
Petra
On Sat 05 Mar 2022 at 17:59:51 +0100 Petra R.-P.
wrote:
> Update for linux-image-5.16.0-3-686 :
[...]
The error persists also in linux-image-5.16.0-4-686 (5.16.12-1) .
Petra
The same here with linux-image-5.16.0-4-686 : different machine but
the same ata controller (ata_piix).
linux-image-5.15.x were all fine ; the same with custom kernels of the
5.15.x series : custom kernels of the 5.16 series all fail to boot and
stop loading at the same point.
For the sake of completeness ...
On Wed 09 Mar 2022 at 08:35:57 +0100 Petra R.-P.
wrote:
[...]
> Okay, that's easier: See attached dmesg-T41-k5.15.txt .
Adding dmesg-T41-b-k5.15.txt — corresponding file for the other
T41 notebook, which has slightly different hardware.
Best,
Petra
Hi Damien,
Damien Le Moal wrote:
> > Ok, did another one, this time with "debug loglevel=7" added on the
> > kernel commandline by editing it in GRUB:
> >
> > https://noone.org/debian/Bug-Reports/1006149/DSCN5259.MOV
>
> Thanks for this. But unfortunately, it does not tell us much as to what
> i
Hi Petra and Axel,
On Wednesday, 9 March 2022 08:11:37 CET Damien Le Moal wrote:
> Could you try this patch:
>
> diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
> index 62eb9921cc94..525ce40b524d 100644
> --- a/drivers/scsi/sd.c
> +++ b/drivers/scsi/sd.c
> @@ -3320,6 +3320,7 @@ static int sd_r
Hello Damien,
Thanks for looking into the problem:
On Wed 09 Mar 2022 at 16:11:37 +0900 Damien Le Moal
wrote:
[...]
> Could you try this patch:
>
> diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
[...]
I am very sorry, but I am a simple user, not a developer.
It would need a lot of tui
Hello,
I am the "OP" with the T41 Thinkpads.
On Tue 08 Mar 2022 at 05:58:53 +0900 Damien Le Moal
wrote:
> Could you try taking a video of the boot messages ?
You can find my first attempt (only ≈12MB) here:
https://prp.in-berlin.de/MAQ01257.MP4
I will leave it there for 2 weeks.
Not sure i
Hi Damien,
Damien Le Moal wrote:
> > Damien Le Moal wrote:
> >> In the bug report, I did not see a dmesg output for a failed boot. But I
> >> guess it is because the user cannot capture it.
> >
> > Correct.
>
> Could you try taking a video of the boot messages ?
Did that now.
https://noone.org
Hi Damien,
one of the affected users here.
Damien Le Moal wrote:
> In the bug report, I did not see a dmesg output for a failed boot. But I
> guess it is because the user cannot capture it.
Correct.
> Could you have a look at this bug report for Fedora:
>
> https://bugzilla.kernel.org/show_bug
Hi Damien,
On Sunday, 6 March 2022 23:26:03 CET Diederik de Haas wrote:
> Upstream commit 68dbbe7d5b4fde736d104cbbc9a2fce875562012 [1]
> seems potentially relevant (included in 5.16-rc1), but given ...
>
> On Saturday, 5 March 2022 17:59:50 CET Petra R.-P. wrote:
> > The "Read log 0x00 page 0x00
On Sunday, 6 March 2022 21:05:10 CET Petra R.-P. wrote:
> > Update for linux-image-5.16.0-3-686 :
Indeed. Somehow I missed it, sorry.
Upstream commit 68dbbe7d5b4fde736d104cbbc9a2fce875562012 [1]
seems potentially relevant (included in 5.16-rc1), but given ...
On Saturday, 5 March 2022 17:59:50 C
Hi Petra,
On Sunday, 6 March 2022 11:23:57 CET Petra R.-P. wrote:
> > I saw that the 5.16.11-1 kernel transitioned to testing and it is useful
> > to know if the issue is still present with that version.
>
> Today's "apt-get dist-upgrade" did not yield anything kernel-related.
Do you have 'linux
Hi Diederik,
Am So., 6. Mär. 2022, um 00:44 +0100 schrieb Diederik de Haas
:
> On Saturday, 5 March 2022 21:12:12 CET Petra R.-P. wrote:
[...]
> How about in /var/log/kern.log.1 (f.e.) ?
The kern.log I inspected yesterday reached back until earlier
days, so I don't think kern.log.1 would have
Hi Petra,
On Saturday, 5 March 2022 21:12:12 CET Petra R.-P. wrote:
> On Sat 05 Mar 2022 at 18:23:52 +0100 Diederik de Haas
> wrote:
> > On Monday, 21 February 2022 17:25:33 CET Petra Rübe-Pugliese wrote:
> [...]
>
> > So if you remove the 'quiet' word there and do an update-grub, then the
> >
On Monday, 21 February 2022 17:25:33 CET Petra Rübe-Pugliese wrote:
> > if yes, can you remote if from the kernel command line and see
> > if you get more information on the screen?
>
> How would that be done?
If you do "cat /proc/cmdline" and see the word 'quiet' in there, then it's not
as verb
Update for linux-image-5.16.0-3-686 :
On Sat 19 Feb 2022 at 22:04:14 +0100 Petra R.-P.
wrote:
[...]
> After the lines
>
>Loading Linux 5.16.0-1-686 ...
Now of course: s/-1-/-3-/
>Loading initial ramdisk ...
>
> the screen gets flushed, and I see:
>
>[ 4.xx] ata1.00: Re
Hi Diederik,
Diederik de Haas wrote:
> > pn firmware-iwlwifi
>
> I see you don't have firmware-iwlwifi installed, but there have been other
> bug
> reports which could be similar, so with the 5.15 kernel, do you have the
> 'iwlwifi' kernel module loaded?
Likely not. IIRC the first
Hello Salvatore,
Am Mo., 21. Feb. 2022, um 14:56 +0100 schrieb Salvatore Bonaccorso
:
> Control: tags -1 + moreinfo
[...]
> Are you booting in quite mode?
I do not think so.
I usually get _heaps_ of output scrolling away on the screen,
but in this case absolutely _nothing_ happens after the
firs
Processing control commands:
> tags -1 + moreinfo
Bug #1006149 [src:linux] linux-image-5.16.0-1-686: Fails to boot on T41
Thinkpads
Added tag(s) moreinfo.
--
1006149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + moreinfo
Hi
On Sat, Feb 19, 2022 at 10:04:14PM +0100, Petra R.-P. wrote:
> Package: src:linux
> Version: 5.16.7-2
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
> This new kernel version does not boot on two fairly similar
> old IBM T41 T
Hello Diederik,
Thanks for your quick reply:
Am Sa., 19. Feb. 2022, um 22:36 +0100 schrieb Diederik de Haas
:
> On Saturday, 19 February 2022 22:04:14 CET Petra R.-P. wrote:
> > Package: src:linux
> > Version: 5.16.7-2
[...]
> > pn firmware-iwlwifi
>
> I see you don't have firmware-i
On Saturday, 19 February 2022 22:04:14 CET Petra R.-P. wrote:
> Package: src:linux
> Version: 5.16.7-2
>
> This new kernel version does not boot on two fairly similar
> old IBM T41 Thinkpads.
> ...
> linux-image-5.15.0-3-686, which I am using to write this
> message, runs fine.
>
> pn firmware-i
Package: src:linux
Version: 5.16.7-2
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
This new kernel version does not boot on two fairly similar
old IBM T41 Thinkpads.
What reproducibly happens is as follows:
After the lines
Loading Linux 5.16.0-1-686 ...
Loadi
57 matches
Mail list logo
