Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 907669 - >=sys-kernel/gentoo-kernel-5.15 hpsa driver not functional
Summary: >=sys-kernel/gentoo-kernel-5.15 hpsa driver not functional
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Distribution Kernel Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-01 18:55 UTC by Henry R. Bent
Modified: 2023-06-01 19:08 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henry R. Bent 2023-06-01 18:55:48 UTC
I have an HP DL380 G7 server and I'm getting lockups in the hpsa driver with kernel versions 5.15 LTS and above.  I've only tried LTS versions so far.  I'm on 5.10 now and everything is fine, but newer versions lock up fairly quickly leading to an unusable system.  Looks like this could be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720359

[  387.416591] hpsa 0000:05:00.0: Controller lockup detected: 0x00120005 after 30
[  387.416658] hpsa 0000:05:00.0: failed 10 commands in fail_all
[  387.416670] hpsa 0000:05:00.0: controller lockup detected: LUN:0000004000000000 CDB:01040000000000000000000000000000
[  387.416678] hpsa 0000:05:00.0: Controller lockup detected during reset wait
[  387.416683] hpsa 0000:05:00.0: scsi 0:1:0:0: reset logical  failed Direct-Access     HP       LOGICAL VOLUME   RAID-5 SSDSmartPathCap- En- Exp=1
[  387.416696] sd 0:1:0:0: Device offlined - not ready after error recovery
[  387.416700] sd 0:1:0:0: Device offlined - not ready after error recovery
[  387.416703] sd 0:1:0:0: Device offlined - not ready after error recovery
[  387.416705] sd 0:1:0:0: Device offlined - not ready after error recovery
[  387.416708] sd 0:1:0:0: Device offlined - not ready after error recovery
[  387.416710] sd 0:1:0:0: Device offlined - not ready after error recovery
[  387.416713] sd 0:1:0:0: Device offlined - not ready after error recovery
[  387.416715] sd 0:1:0:0: Device offlined - not ready after error recovery
[  387.416717] sd 0:1:0:0: Device offlined - not ready after error recovery
[  387.416731] sd 0:1:0:0: [sda] tag#191 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=58s
[  387.416736] sd 0:1:0:0: [sda] tag#191 CDB: opcode=0x2a 2a 00 20 a4 21 90 00 00 08 00
[  387.416739] I/O error, dev sda, sector 547627408 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2
[  387.416745] Buffer I/O error on dev sda4, logical block 59801906, lost async page write
[  387.416767] sd 0:1:0:0: [sda] tag#190 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=58s
[  387.416772] sd 0:1:0:0: [sda] tag#190 CDB: opcode=0x2a 2a 00 20 a4 20 38 00 00 08 00
[  387.416774] I/O error, dev sda, sector 547627064 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2
[  387.416779] Buffer I/O error on dev sda4, logical block 59801863, lost async page write
[  387.416788] sd 0:1:0:0: [sda] tag#189 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=58s
[  387.416792] sd 0:1:0:0: [sda] tag#189 CDB: opcode=0x2a 2a 00 20 a4 1f 68 00 00 08 00
[  387.416794] I/O error, dev sda, sector 547626856 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2
[  387.416798] Buffer I/O error on dev sda4, logical block 59801837, lost async page write
[  387.416807] sd 0:1:0:0: [sda] tag#188 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=58s
[  387.416810] sd 0:1:0:0: [sda] tag#188 CDB: opcode=0x2a 2a 00 06 40 0f 80 00 00 08 00
[  387.416812] I/O error, dev sda, sector 104861568 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[  387.416817] EXT4-fs warning (device sda4): ext4_end_bio:343: I/O error 10 writing to inode 14962854 starting block 13107696)
[  387.416823] Buffer I/O error on device sda4, logical block 4456176
[  387.416833] sd 0:1:0:0: [sda] tag#187 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=58s
[  387.416837] sd 0:1:0:0: [sda] tag#187 CDB: opcode=0x2a 2a 00 06 3e cc c0 00 00 08 00
[  387.416839] I/O error, dev sda, sector 104778944 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[  387.416843] EXT4-fs warning (device sda4): ext4_end_bio:343: I/O error 10 writing to inode 14958889 starting block 13097368)
[  387.416848] Buffer I/O error on device sda4, logical block 4445848
[  387.416856] sd 0:1:0:0: [sda] tag#130 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=58s
[  387.416860] sd 0:1:0:0: [sda] tag#130 CDB: opcode=0x2a 2a 00 06 20 18 38 00 00 08 00
[  387.416862] I/O error, dev sda, sector 102766648 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2
[  387.416866] Buffer I/O error on dev sda4, logical block 4194311, lost async page write
[  387.416875] sd 0:1:0:0: [sda] tag#129 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=58s
[  387.416878] sd 0:1:0:0: [sda] tag#129 CDB: opcode=0x2a 2a 00 04 20 18 18 00 00 08 00
[  387.416880] I/O error, dev sda, sector 69212184 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 2
[  387.416885] Buffer I/O error on dev sda4, logical block 3, lost async page write
[  387.416893] sd 0:1:0:0: [sda] tag#128 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=58s
[  387.416897] sd 0:1:0:0: [sda] tag#128 CDB: opcode=0x2a 2a 00 06 3d 00 70 00 00 08 00
[  387.416899] I/O error, dev sda, sector 104661104 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[  387.416904] EXT4-fs warning (device sda4): ext4_end_bio:343: I/O error 10 writing to inode 14962862 starting block 13082638)
[  387.416908] Buffer I/O error on device sda4, logical block 4431118
[  387.416917] sd 0:1:0:0: [sda] tag#854 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=64s
[  387.416920] sd 0:1:0:0: [sda] tag#854 CDB: opcode=0x2a 2a 00 13 24 20 c8 00 00 18 00
[  387.416922] I/O error, dev sda, sector 321134792 op 0x1:(WRITE) flags 0x800 phys_seg 3 prio class 2
[  387.416940] sd 0:1:0:0: rejecting I/O to offline device
[  387.416942] I/O error, dev sda, sector 534155424 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
[  387.416946] EXT4-fs warning (device sda4): ext4_end_bio:343: I/O error 10 writing to inode 14944394 starting block 66769428)
[  387.416951] Buffer I/O error on device sda4, logical block 58117908
[  387.416997] Aborting journal on device sda4-8.
[  387.417004] EXT4-fs error (device sda4) in ext4_do_update_inode:5286: Journal has aborted
[  387.417015] EXT4-fs error (device sda4): ext4_dirty_inode:6118: inode #14958889: comm syslogd: mark_inode_dirty error
[  387.417022] EXT4-fs error (device sda4) in ext4_dirty_inode:6119: IO failure
[  387.417024] Buffer I/O error on dev sda4, logical block 31490048, lost sync page write
[  387.417037] EXT4-fs error (device sda4): ext4_journal_check_start:83: comm syslogd: Detected aborted journal
[  387.417043] JBD2: I/O error when updating journal superblock for sda4-8.
[  387.417074] Buffer I/O error on dev sda4, logical block 0, lost sync page write
[  387.417098] EXT4-fs (sda4): I/O error while writing superblock
[  387.417137] Buffer I/O error on dev sda4, logical block 0, lost sync page write
[  387.417152] EXT4-fs (sda4): I/O error while writing superblock
[  387.417155] EXT4-fs (sda4): Remounting filesystem read-only