please fix ahci driver when in pcie-32bit-dma mode #4848
Comments
|
Does running in 64-bit mode ( |
|
well it crashes harder (as in i loose ssh and had to uart to get the logs) uname -ar [ 20.748085] SError Interrupt on CPU0, code 0xbf000002 -- SError |
|
Does it work without the PCIe switch in the way but I think I have a spare SATA card at home (should be a https://www.amazon.co.uk/Ziyituod-Controller-Expansion-Profile-Non-Raid/dp/B07TD57RGZ), so I can bring it in if it helps. |
|
nope tried with arm_64bit=1 and without same results once i set dtoverlay=pcie-32bit-dma crash from arm64 without PCIe switch in the middle : |
In some ways this is good, as it simplifies the configuration. |
|
i forgot to add this is the card i am using |
|
Testing in the office and it seems happy, at least with no drives connected. FWIW my card reports as There is an error message in dmesg I do have a suspicion I may have had msi disabled ( |
|
correct with no drive connected the error does not present itself... i do not have pci=nomsi in my cmdline.txt |
|
OK, I'll take a drive into the office tomorrow. |
|
I forgot to pick up a drive until today. Doing a comparison with and without dtoverlay=pcie-32bit-dma. There seems to be something funky going on, and I would chase down the window definition, but it looks like it's being done via some magic, and I'm out of time for today, but I think we want to define it as less than 4GB in this case. |
|
arm_64bit=1 issue appears to be different to 32bit. It crashes during brcm_pcie_probe, with callstack And that is with or without a drive connected. 32bit issue does seem to be down to that MSI address. With pci-32bit-dma we have an offset of 0 and size of 0x100000000 (4GB). Without we have an offset of 0x400000000 (16GB) and size of 0x100000000 (4GB). I can't immediately deduce where these window values come from. |
|
The base address and window size are provided by the firmware (via the The first thing to try would be to set |
|
With Issue found anyway. The 3GB size was therefore being rounded up to 4GB, and the MSI vector couldn't fit in at 0x0_fffffffc. Drop the dma-range to 2GB with and the MSI vector slots in where expected, and the warning goes away. 64 bit also then seems to be happy to boot as well. Is that a reasonable change to make to the base DT? I don't know the full implications. |
|
Rather than patch the base dts file I would prefer that change to go into the pcie-32bit-dma overlay, making it live up to the name. |
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi#4848 Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi#4848 Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi#4848 Signed-off-by: Dave Stevenson <[email protected]>
|
pcie-32bit-dma patched, and PR #4870 created. @FrancescoRestelli any chance you could test with your setup? |
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi#4848 Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. #4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi#4848 Fixes: ee6a81c "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. #4848 Fixes: ee6a81c "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
|
i can confirm that my ssd drive is now mounted and working with dtoverlay=pcie-32bit-dma enabled with and without the pcie switch! since the PR was already merged i just compiled current upstream version and a 32bit kernel 5.10.95-v7l+ thanks a lot to both of you will test more over the weekend report and then closed the issue br francesco |
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. #4848 Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. #4848 Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. #4848 Signed-off-by: Dave Stevenson <[email protected]>
|
well nothing realy to report it all works compiled the kernel on a ssd (over the bridge), did some tests with dd and copied over the network it all just works stable from what i can tell quickly, thanks again |
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
BugLink: https://bugs.launchpad.net/bugs/1960323 The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]> (cherry picked from commit 80ba7d923e1e1f3fafbbc2490c5ff6f259f5485c rpi-5.15.y) Signed-off-by: Juerg Haefliger <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Adding the dma-ranges to the overlay missed setting the field sizes, so the compiler rightly flagged a warning. raspberrypi/linux#4848 Fixes: ee6a81c85402 "dtoverlay: Reduce size of PCIE IB window in pcie-32-dma overlay" Signed-off-by: Dave Stevenson <[email protected]>
The PCIE inbound window is rounded up to a power of 2, so the default of 3GB rounds up to 4GB starting at 0. This prohibits the MSI vector sitting at 0x0_fffffffc, and causes warnings from some subsystems (eg ahci) of a 64bit address on a 32bit configuration. Reduce the window down to 2GB to avoid this issue. raspberrypi/linux#4848 Signed-off-by: Dave Stevenson <[email protected]>
Describe the bug
when setting dtoverlay=pcie-32bit-dma (which is necessary for some dvb cards i am playing with) the ahci driver does not work and crashes
Steps to reproduce the behaviour
install ASM1064 based sata card with a connected ssd
set dtoverlay=pcie-32bit-dma in /boot/config.txt
reboot
dmesg shows errors
lspci crashes
no /dev/sda* exists
Device (s)
Raspberry Pi CM4
System
os:
pi@raspberrypi:~ $ cat /etc/rpi-issue
Raspberry Pi reference 2021-10-30
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 288b21fc27e128ea6b330777aca68e0061ebf4fe, stage4
firmware:
Jan 20 2022 13:56:48
Copyright (c) 2012 Broadcom
version bd88f66f8952d34e4e0613a85c7a6d3da49e13e2 (clean) (release) (start)
uname:
Linux raspberrypi 5.10.92-v7l+ #1 SMP Tue Jan 25 18:46:39 GMT 2022 armv7l GNU/Linux
Logs
[ 12.771119] ata1.00: qc timeout (cmd 0xec)
[ 12.911545] 8<--- cut here ---
[ 12.914604] Unhandled fault: asynchronous external abort (0x1211) at 0x00000000
[ 12.921915] pgd = 7ed806c6
[ 12.924617] [00000000] *pgd=042cc003, *pmd=1fd26d003
[ 12.976726] 8<--- cut here ---
[ 12.979781] Unhandled fault: asynchronous external abort (0x1211) at 0x00000000
[ 12.987083] pgd = bc4626ff
[ 12.989783] [00000000] *pgd=80000000004003, *pmd=00000000
[ 12.995185] Internal error: : 1211 [#1] SMP ARM
[ 12.999710] Modules linked in: snd_soc_hdmi_codec cfg80211 rfkill 8021q garp stp llc v3d gpu_sched i2c_brcmstb raspberrypi_hwmon v4l2_mem2mem(O) bcm2835_mmal_vchiq(C) videobuf2_dma_contig(O) videobuf2_vmalloc(O) videobuf2_memops(O) videobuf2_v4l2(O) videobuf2_common(O) snd_bcm2835(C) videodev(O) mc(O) vc_sm_cma(C) vc4 ahci libahci cec drm_kms_helper libata snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm rpivid_mem snd_timer snd syscopyarea sysfillrect sysimgblt fb_sys_fops uio_pdrv_genirq uio nvmem_rmem i2c_dev drm fuse drm_panel_orientation_quirks backlight ip_tables x_tables ipv6
[ 13.051725] CPU: 1 PID: 200 Comm: scsi_eh_0 Tainted: G C O 5.10.92-v7l+ #1
[ 13.059721] Hardware name: BCM2711
[ 13.063159] PC is at ata_wait_register+0xb0/0x134 [libata]
[ 13.068651] LR is at _cond_resched+0x34/0x6c
[ 13.072915] pc : [] lr : [] psr: 60000013
[ 13.079175] sp : c37fdb70 ip : c37fdb28 fp : c37fdbb4
[ 13.084393] r10: c377e000 r9 : c37fc000 r8 : 00008000
[ 13.089619] r7 : 00000001 r6 : c1203d00 r5 : 00000001 r4 : c377c000
[ 13.096149] r3 : f0868118 r2 : deaddead r1 : 00000000 r0 : 00000000
[ 13.102681] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
[ 13.109828] Control: 30c5383d Table: 04655e40 DAC: 55555555
[ 13.109835] Process scsi_eh_0 (pid: 200, stack limit = 0xe537caac)
[ 13.109838] Stack: (0xc37fdb70 to 0xc37fe000)
[ 13.109843] db60: 00008001 0000041a 000003e8 00008000
[ 13.109850] db80: f0868118 ffff9008 c377e000 00000001 000001f4 c377c000 c377e000 c377e000
[ 13.142442] dba0: deaddead c377d780 c37fdbdc c37fdbb8 bf1953dc bf244308 00000001 000001f4
[ 13.142447] dbc0: c377c000 60000113 f086810 c237f240 c37fdc0c c37fdbe0 bf194ca8 bf195348
[ 13.142451] dbe0: 60000113 60000113 c377d000 60000113 c377c000 c377dac0 c377d6b0 00000001
[ 13.142455] dc00: c37fdc1c c37fdc10 bf194d5c bf194c6c c37fdc94 c37fdc20 bf246c7c bf194d40
[ 13.142460] dc20: c37fdc64 000000ec c377d770 00000000 00000000 00000000 00000000 fafbfcfd
[ 13.171252] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 13.175126] dc40: c37fdce8 60000113 c377d000 c37fdcd0 bf19694c 00000001 00030003 c37fdc5c
[ 13.183340] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 13.191285] dc60: c37fdc5c c470ab9d 60000113 c37fdce8 c377dac0 c377dd00 00000001 00000001
[ 13.191290] dc80: c377c000 00000001 c37fdd34 c37fdc98 bf24790c bf246980 c37fdce8 00000001
[ 13.191294] dca0: 00001388 c1203d00 bf264894 bf2644bc bf264850 bf264434 c377dca8 ffffc004
[ 13.191298] dcc0: 00000001 c377e000 00000000 00000001 00000046 00000801 00000000 00000000
[ 13.191302] dce0: 0000eca0 00000000 d647cd96 00000d00 00000200 00000000 0377dd00 00000000
[ 13.191311] dd00: 00000001 c470ab9d 60000113 c377dac0 00000000 c377c000 00000001 c377eaa8
[ 13.254748] dd20: c377d780 00000155 c37fdddc c37fdd38 bf256314 bf2474c8 bf19694c bf195448
[ 13.254753] dd40: 00000000 00000000 00000000 bf2675dc bf2675b8 00000000 c1203d00 bf195448
[ 13.254757] dd60: bf19694c bf196da8 bf244430 00000000 00000000 bf267208 00000000 00000000
[ 13.254761] dd80: bf266e20 c377c000 c377e000 c12050b4 00000000 c470ab9d c377c000 c377d780
[ 13.254766] dda0: c377c000 c377c000 00000001 c470ab9d c377dac0 00000003 00000000 c377c000
[ 13.254770] ddc0: 00000001 c377e000 c377dac0 c377c000 c37fdea4 c37fdde0 bf25f928 bf255b70
[ 13.254774] dde0: bf195448 00000000 bf268c14 bf268c40 c1203d00 c020ca80 c377e000 00000005
[ 13.254779] de00: bf1990f4 bf19694c bf195448 bf196da8 bf244430 c37fde20 c020bb6c bf268934
[ 13.254783] de20: c377d780 c0bc9590 00000000 00000001 c377e000 60000013 00000003 c37fde48
[ 13.254787] de40: c020cb04 c020bb48 c020cb04 00000000 bf25727c c37fdef4 c1094c10 c0bc9590
[ 13.254791] de60: bf25727c 00000001 c377e000 60000013 c37fdea4 c470ab9d c03356c4 c377c000
[ 13.254796] de80: c237f240 c377c000 00000001 c377e000 60000013 c377eaf0 c37fdebc c37fdea8
[ 13.254800] dea0: bf19586c bf25f354 00000000 c377d968 c37fdef4 c37fdec0 bf25729c bf19582c
[ 13.254804] dec0: bf266e20 00020200 60000093 c3262800 c37fdefc c377c000 c3262974 ffffe000
[ 13.254809] dee0: c0c31414 c08ac288 c37fdf24 c37fdef8 bf25777c bf257024 ffffe000 c37fdefc
[ 13.254813] df00: c37fdefc c470ab9d c37fdef0 00000000 c3262800 c37fc000 c37fdf74 c37fdf28
[ 13.254817] df20: c08ae848 bf2576e8 c08ae784 c3262800 c37fdf54 c37fdf40 c0bc9590 c0335678
[ 13.254821] df40: c37fc000 c470ab9d c37fdf74 c34299c0 c2b27580 00000000 c37fc000 c08ae784
[ 13.254825] df60: c3262800 c35b9a24 c37fdfac c37fdf78 c02467ec c08ae790 ffffe000 c34299e4
[ 13.254830] df80: c37fdfac c2b27580 c0246684 00000000 00000000 00000000 00000000 00000000
[ 13.254834] dfa0: 00000000 c37fdfb0 c02000ec c0246690 00000000 00000000 00000000 00000000
[ 13.254838] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 13.254842] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
[ 13.254846] Backtrace:
[ 13.254899] [] (ata_wait_register [libata]) from [] (ahci_stop_engine+0xa0/0x10c [libahci])
[ 13.254905] r10:c377d780 r9:deaddead r8:c377e000 r7:c377e000 r6:c377c000 r5:000001f4
[ 13.254908] r4:00000001
[ 13.254923] [] (ahci_stop_engine [libahci]) from [] (ahci_kick_engine+0x48/0xd4 [libahci])
[ 13.254927] r7:c237f240 r6:f0868100 r5:60000113 r4:c377c000
[ 13.254941] [] (ahci_kick_engine [libahci]) from [] (ahci_post_internal_cmd+0x28/0x2c [libahci])
[ 13.254946] r9:00000001 r8:c377d6b0 r7:c377dac0 r6:c377c000 r5:60000113 r4:c377d000
[ 13.254987] [] (ahci_post_internal_cmd [libahci]) from [] (ata_exec_internal_sg+0x308/0x504 [libata])
[ 13.255052] [] (ata_exec_internal_sg [libata]) from [] (ata_dev_read_id+0x450/0x600 [libata])
[ 13.255056] r10:00000001 r9:c377c000 r8:00000001 r7:00000001 r6:c377dd00 r5:c377dac0
[ 13.255059] r4:c37fdce8
[ 13.255123] [] (ata_dev_read_id [libata]) from [] (ata_eh_recover+0x7b0/0x13c4 [libata])
[ 13.255127] r10:00000155 r9:c377d780 r8:c377eaa8 r7:00000001 r6:c377c000 r5:00000000
[ 13.255130] r4:c377dac0
[ 13.255193] [] (ata_eh_recover [libata]) from [] (sata_pmp_error_handler+0x5e0/0x96c [libata])
[ 13.255198] r10:c377c000 r9:c377dac0 r8:c377e000 r7:00000001 r6:c377c000 r5:00000000
[ 13.255200] r4:00000003
[ 13.255240] [] (sata_pmp_error_handler [libata]) from [] (ahci_error_handler+0x4c/0x80 [libahci])
[ 13.255245] r10:c377eaf0 r9:60000013 r8:c377e000 r7:00000001 r6:c377c000 r5:c237f240
[ 13.255247] r4:c377c000
[ 13.255286] [] (ahci_error_handler [libahci]) from [] (ata_scsi_port_error_handler+0x284/0x6c4 [libata])
[ 13.255289] r5:c377d968 r4:00000000
[ 13.255350] [] (ata_scsi_port_error_handler [libata]) from [] (ata_scsi_error+0xa0/0xf0 [libata])
[ 13.255355] r10:c08ac288 r9:c0c31414 r8:ffffe000 r7:c3262974 r6:c377c000 r5:c37fdefc
[ 13.255357] r4:c3262800
[ 13.255397] [] (ata_scsi_error [libata]) from [] (scsi_error_handler+0xc4/0x3c8)
[ 13.255401] r6:c37fc000 r5:c3262800 r4:00000000
[ 13.255408] [] (scsi_error_handler) from [] (kthread+0x168/0x16c)
[ 13.255413] r10:c35b9a24 r9:c3262800 r8:c08ae784 r7:c37fc000 r6:00000000 r5:c2b27580
[ 13.255415] r4:c34299c0
[ 13.255421] [] (kthread) from [] (ret_from_fork+0x14/0x28)
[ 13.255424] Exception stack(0xc37fdfb0 to 0xc37fdff8)
[ 13.255428] dfa0: 00000000 00000000 00000000 00000000
[ 13.255432] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 13.255436] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 13.255440] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c0246684
[ 13.255443] r4:c2b27580
[ 13.255447] Code: 1a00001d e51b3034 e5932000 f57ff04f (e51b3038)
[ 13.255453] ---[ end trace b82c263ff79ec1ac ]---
lspci -vv
06:00.0 SATA controller: ASMedia Technology Inc. Device 1064 (rev 02) (prog-if 01 [AHCI 1.0])
Subsystem: ZyDAS Technology Corp. Device 2116
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 89
Region 0: Memory at 600080000 (32-bit, non-prefetchable) [size=8K]
Region 5: Memory at 600082000 (32-bit, non-prefetchable) [size=8K]
Expansion ROM at 600000000 [virtual] [disabled] [size=512K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fffffffc Data: 6544
Capabilities: [80] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 26.000W
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 8GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s (downgraded), Width x1 (ok)
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR-
10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS- TPHComp- ExtTPHComp-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled,
AtomicOpsCtl: ReqEn-
LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis+
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1-
EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
Retimer- 2Retimers- CrosslinkRes: unsupported
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
Capabilities: [130 v1] Secondary PCI Express
LnkCtl3: LnkEquIntrruptEn- PerformEqu-
LaneErrStat: 0
Kernel driver in use: ahci
Kernel modules: ahci
Additional context
also @6by9 noticed the bug on his hardware
The text was updated successfully, but these errors were encountered: