Date: Wed, 11 Aug 2021 16:38:44 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 257771] M.2 pcie/nvme device can't mount root and panics on Rock960 rk3399 Message-ID: <bug-257771-7@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257771 Bug ID: 257771 Summary: M.2 pcie/nvme device can't mount root and panics on Rock960 rk3399 Product: Base System Version: CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: maciphone2@googlemail.com Created attachment 227116 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D227116&action= =3Dedit u-boot, loader & dmesg well,=20 on cold boot nvme (directly attached to M.2-slot on Rock960) isn't detected= by u-boot . seems to be something with power cycling that it will be detected by u-boot= =20 AFTER REBOOT while machine was booted from eMMC before .... rock960 =3D> nvme info Device 0: Vendor: 0x15b7 Rev: 211070WD Prod: 20251C807274=20=20=20=20=20=20= =20=20 Type: Hard Disk Capacity: 238475.1 MB =3D 232.8 GB (488397168 x 512) ... well on loader prompt the nvme`s root filesystem is now detected as disk1p2= ( was previously installed by memstick.img) : OK lsdev disk devices: disk0: 59768832 X 512 blocks (removable) disk0p1: EFI disk0p2: FreeBSD UFS disk1: 488397168 X 512 blocks disk1p1: EFI disk1p2: FreeBSD UFS disk1p3: FreeBSD swap http: (unknown) net devices: OK show currdev disk0p2: OK set currdev=3Ddisk1p2 OK show currdev disk1p2 ... OK boot -v ... results in panic because pci/nvme driver never detects any /dev/nda0 or similar.. . .... cib0: <Rockchip PCIe controller> mem 0xf8000000-0xf9ffffff,0xfd000000-0xfdffffff irq 6,7,8 on ofwbus0 pcib0: Bus is not cache-coherent pcib0: Gen1 link training timeouted: 0x00180001. pci0: <OFW PCI bus> on pcib0 pci0: domain=3D0, physical bus=3D0 found-> vendor=3D0x1d87, dev=3D0x0100, revid=3D0x00 domain=3D0, bus=3D0, slot=3D0, func=3D0 class=3D06-04-00, hdrtype=3D0x01, mfdev=3D0 cmdreg=3D0x0106, statreg=3D0x0010, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Da, irq=3D255 powerspec 3 supports D0 D1 D3 current D0 MSI supports 1 message, 64 bit, vector masks MSI-X supports 1 message in map 0x10 secbus=3D1, subbus=3D31 pcib1: <PCI-PCI bridge> at device 0.0 on pci0 pcib0: failed to reserve resource for pcib1 pcib1: failed to allocate initial memory window: 0-0xfffff pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 31 pci1: <PCI bus> on pcib1 pcib1: allocated bus range (1-1) for rid 0 of pci1 pci1: domain=3D0, physical bus=3D1 ... same result if bootable system was removed from eMMC and machine booted directly from nvme, so nvme is bootable but panics. same panic regardless if UFS or ZFS formatted disk. full dmesg in attachment(UFS in this example). Regards K. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-257771-7>