Hello,
on kernel.org I was told to write to these addresses and report about a minor problem with the latest version of the kernel I use. I am using my own compiled kernels ever since, and right now I am using the LTS series 6.6.x. After 6.6.43 tools like hddtemp stopp working: they all tell me that the drive are sleeping, which they are certainly not. Even netcat can't tell me the temperature any more. In a small script I use these commands:
/bin/netcat -4d localhost 7634 | awk -F '|' '{print $4 " °C"}' /bin/netcat -4d localhost 7634 | awk -F '|' '{print $9 " °C"}'
Those commands work very well on kernel 6.6.43, and they don't work any more on 6.6.44 and 6.6.45. The error is reproduceable: when I boot into 6.6.43 the temperature is retrieved, when I reboot into 6.6.44 or 6.6.45 the commands stopp working. The tool hddtemp even claims that the "drive is sleeping", and it does so for both drives.
Is this a bug or has a new parameter or configuration option been added to the kernel code that has to be activated in order to retrieve the temperature?
Attached you'll find my kernel configuration from version 6.6.43, where the hdd temperature is still retrieved by the above command.
My system:
Kernel Version: 6.6.43 (64-bit) Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Manufacturer: FUJITSU Product Name: ESPRIMO_D756
/dev/sda:
Model=Samsung SSD 870 EVO 500GB, FwRev=SVT01B6Q, SerialNo=S62BNJ0NC06737D Config={ Fixed } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=unknown, MaxMultSect=1, MultSect=1 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773168 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 AdvancedPM=no WriteCache=enabled Drive conforms to: unknown: ATA/ATAPI-2,3,4,5,6,7
/dev/sdb:
Model=TOSHIBA MK5061GSYB, FwRev=ME0A, SerialNo=42JNT0TGT Config={ Fixed } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=16384kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773167 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 AdvancedPM=yes: unknown setting WriteCache=enabled Drive conforms to: Unspecified: ATA/ATAPI-3,4,5,6,7
Thank you very much for any help in advance! If you need any more information, just let me know!
Kind regards,
Wolfgang
* Wolfgang Klein klein.wolfg@web.de wrote:
Is this a bug or has a new parameter or configuration option been added to the kernel code that has to be activated in order to retrieve the temperature?
The problem is known, have a look here:
https://lore.kernel.org/regressions/e206181e-d9d7-421b-af14-2a70a7f83006@heu...
linux-stable-mirror@lists.linaro.org