Kernel Panic with Intel 660P 2TB

#1

Hi there,

I’m using the RockPI4b and want to use the Intel 660P 2TB ssd.
I installed the Raxda Ubuntu Core on eMMC and shortly (around 60s) after boot I get a kernel panic.
I tested and preformatted the ssd on a PC and it worked fine…

Any Ideas where my problem lies? Thank you very much!

Here are the versions:
Linux version 4.4.154-110-rockchip-gcef30e88a9f5
rockpi4b-rk-u-boot-latest (2017.09-2697-ge41695afe3)
rockchip-overlay (2.8)

[   62.841173] nvme 0000:01:00.0: Timeout I/O 1 QID 0

[ 62.841275] nvme 0000:01:00.0: I/O 1 QID 0 timeout, reset controller
[ 62.945289] nvme 0000:01:00.0: Cancelling I/O 1 QID 0
[ 62.946504] nvme 0000:01:00.0: Device failed to resume
[ 62.947674] Unable to handle kernel paging request at virtual address ffffff8009c7c01c
[ 62.948392] pgd = ffffffc0e72f2000
[ 62.948705] [ffffff8009c7c01c] *pgd=0000000000000000, *pud=0000000000000000
[ 62.949438] Internal error: Oops: 96000007 [#1] SMP
[ 62.949882] Modules linked in: ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 bcmdhd xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter nfsd autofs4
[ 62.953226] CPU: 5 PID: 559 Comm: nvme0 Not tainted 4.4.154-110-rockchip-gcef30e88a9f5 #1
[ 62.953947] Hardware name: ROCK PI 4B (DT)
[ 62.954322] task: ffffffc0e70d4600 task.stack: ffffffc0e7944000
[ 62.954869] PC is at nvme_remove+0x12c/0x158
[ 62.955259] LR is at nvme_remove+0x70/0x158
[ 62.955644] pc : [] lr : [] pstate: a0000145
[ 62.956301] sp : ffffffc0e7947cd0
[ 62.956601] x29: ffffffc0e7947cd0 x28: 0000000000000000
[ 62.957102] x27: 0000000000000000 x26: 0000000000000000
…
[ 63.091548] 7ba0: ffffff8009c7c01c 0000000000000000 ffffff80093b3890 ffffffbdc3b40e80
[ 63.092246] 7bc0: 0000000000000000 ffffff800823d948 0000000000000010 ffffffc0ef1c4160
[ 63.092945] 7be0: 0000000000003fa7 0000000001ffffff 0000000000010000 0000000000000030
[ 63.093644] 7c00: 0000000000000030 00000040eed2d000 ffffffc0ef2f4600 0000000000000000
[ 63.094339] 7c20: 0000000000000000 0000000000000000
[ 63.094791] [] nvme_remove+0x12c/0x158
[ 63.095282] [] pci_device_remove+0x48/0xd4
[ 63.095792] [] __device_release_driver+0x88/0xf8
[ 63.096345] [] device_release_driver+0x2c/0x40
[ 63.096888] [] pci_stop_bus_device+0x40/0xa4
[ 63.097407] [] pci_stop_and_remove_bus_device+0x20/0x34
[ 63.098010] [] pci_stop_and_remove_bus_device_locked+0x24/0x34
[ 63.098675] [] nvme_remove_dead_ctrl+0x2c/0x60
[ 63.099220] [] kthread+0xe0/0xf0
[ 63.099656] [] ret_from_fork+0x10/0x20
[ 63.100141] Code: f94013f5 a8c37bfd d65f03c0 91007000 (b9400000)
[ 63.100758] —[ end trace b57e0f5569df5bcd ]—

~$ dmesg | grep pcie

[ 1.521249] of_get_named_gpiod_flags: parsed ‘gpio’ property of node ‘/vcc3v3-pcie-regulator[0]’ - status (0)
[ 1.521295] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
[ 1.521330] vcc3v3_pcie: supplied by vcc3v3_sys
[ 1.521785] vcc3v3_pcie: at 3300 mV
[ 1.521946] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 0uV
[ 1.665547] phy phy-pcie-phy.9: Looking up phy-supply from device tree
[ 1.665557] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
[ 1.667005] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
[ 1.667014] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
[ 1.667044] of_get_named_gpiod_flags: parsed ‘ep-gpios’ property of node ‘/pcie@f8000000[0]’ - status (0)
[ 1.667290] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
[ 1.667301] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply property in node /pcie@f8000000 failed
[ 1.667314] rockchip-pcie f8000000.pcie: no vpcie3v3 regulator found
[ 1.667877] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
[ 1.667886] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
[ 1.667896] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
[ 1.668457] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
[ 1.668466] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
[ 1.668476] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
[ 1.703623] PCI host bridge /pcie@f8000000 ranges:
[ 1.705293] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[ 1.719667] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[ 1.720438] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
[ 1.721650] pcie_pme 0000:00:00.0:pcie01: service driver pcie_pme loaded
[ 1.721757] aer 0000:00:00.0:pcie02: service driver aer loaded

#2

Hi,
does nobody does have an idea whats causing this and how to fix this? :frowning:

Would appreciate it…thank you…

#3

The same for me, used Kingston SSD.
Try a official supported SSD, It’s works ion my case

#4

Thanks for your reply!

I thought Intel 660P is officially supported…
according to Wiki:
Known working under Linux kernel but not directly in bootloader(uSD/eMMC + NVMe booting)

  • Samsung EVO series( M key, NVMe ), work well on ROCK Pi 4, fast speed <-- Warning nvme boot via SPI is not possible (970 EVO Plus)
  • KingSpec NVMe M.2 2280( M key, NVMe ), works well
  • Western Digital WD Black 500GB M.2 2280 ( model WDS500G2X0C, NVMe ), works well on Debian Stretch
  • Western Digital WD Blue WDS500G1B0C
  • Sabrent Rocket NVMe PCIe M.2 2280 ssd 256GB, works perfectly in Ubuntu 18.04.2 server
  • Intel 660P SSD ([boots with 4.4 kernel]
#5

In my case, the kingston boots only one times after Installation. Magic?
Second boot ends in timeout.
Do you use kernel 4.4 ? It‘s may differ.
I have try last armbian kernel (5.4 at this time).

Bad Memory modules on RockPi 4?
#6

I use Acer VT500M.