Date: Fri, 29 May 2020 07:00:10 +0200 From: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> To: Robert Crowston <crowston@protonmail.com>, freebsd-arm@freebsd.org Subject: Re: bootverbose Test-session Re: Driver for Raspberry Pi 4 PCI-express controller Message-ID: <3B0A1C72-C4C3-4B32-986D-FBF2970DF12A@googlemail.com> In-Reply-To: <3040F106-13F6-462C-B655-DE7F79FFE52A@googlemail.com> References: <Pm_LEzoJP7MAKrZ9L-pRYQ4-qTv7TK1QARu1mwqoNFS5mzra-4zmS_0WYotf7CKSKDoZ2fjC3BSEUGIy-k95Qv1g35Zq0AsfiXwLHXpS0bE=@protonmail.com> <7F058E92-DDD3-4728-9A51-09BF1D47855C@googlemail.com> <1RBZ-1AclgkiNDwWUqrWhun8T8YSAX6g64NeSc2DKy9EF1wGsJobselP4UYGflpcmbfUx3sEEM2YplIJOXPmZ6EG_GwiMC1_3GLrqpZxisQ=@protonmail.com> <46519DEB-E96D-43DD-B739-401F9F51371E@googlemail.com> <87EE030D-5323-477B-9FF3-CB8970138729@googlemail.com> <t9qxjbkckKn-ohuWeAtdO6YomotuNUUJrldo1QJcMjWu7RcTaESt1LfG1uz3arRRVdbIbGDZcv3bfFODv0vxmdHa2r2sSQc3nQoZa3nKAGg=@protonmail.com> <3040F106-13F6-462C-B655-DE7F79FFE52A@googlemail.com>
index | next in thread | previous in thread | raw e-mail
> Am 29.05.2020 um 05:07 schrieb Klaus Küchemann <maciphone2@googlemail.com>: > > > ... > > O.K., here is a funny bootverbose test-session (using Original rpi-power adaptor 3A & UPS(Uninterruptible power supply ) : > > …….blablabla…. > Tonight there was absolutely no way to get the keyboard to work what let me assume that the filesystem (or u-boot) or eventually some hardware-chip was „attacked“ by these tests… > Yep(filesystem was „attacked“ by tests), after „renewing“ the (msdos-)root-filesystem(incl.. U-boot.bin) on the uSD , `got the keyboard/mouse back to responding state (keyboard/mouse-response on HDMI while no simultaneously access to UART-console-keyboard-input(using picocom)… And (!) detaching and then reattaching the keyboard/mouse suddenly gives simultaneously access on picocom and HDMI-console) , last test for today: third trial ofunplug/replug keyboard/mouse worked so this was a good test, which let me assume that after some fixes Robert`s pcie-driver will be ready for review on phabricator... — … psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0 gic0: <ARM Generic Interrupt Controller> mem 0x40041000-0x40041fff,0x40042000-0x40043fff,0x40044000-0x40045fff,0x40046000-0x40047fff irq 46 on simplebus0 … bcm_dma0: <BCM2835 DMA Controller> mem 0x7e007000-0x7e007aff irq 9,10,11,12,13,14,15,16,17,18,19 on simplebus0 bcmwd0: <BCM2708/2835 Watchdog> mem 0x7e100000-0x7e100113,0x7e00a000-0x7e00a023,0x7ec11000-0x7ec1101f on simplebus0 mbox0: <BCM2835 VideoCore Mailbox> mem 0x7e00b880-0x7e00b8bf irq 21 on simplebus0 … pcib0: <BCM2838-compatible PCI-express controller> mem 0x7d500000-0x7d50930f,0x7e00f300-0x7e00f31f irq 66,67 on simplebus2 pcib0: hardware identifies as revision 0x304. pci0: <PCI bus> on pcib0 pcib1: <PCI-PCI bridge> irq 77 at device 0.0 on pci0 pcib0: bcm_pcib_alloc_resource FAIL: type=3, rid=36, start=00000000f8000000, end=00000000f80fffff, count=0000000000100000, flags=40 pcib1: failed to allocate initial prefetch window: 0-0xfffff pci1: <PCI bus> on pcib1 xhci0: <XHCI (generic) USB 3.0 controller> irq 78 at device 0.0 on pci1 xhci0: 32 bytes context size, 64-bit DMA usbus0 on xhci0 … usbus0: 5.0Gbps Super Speed USB v3.0 iicbus0: <OFW I2C bus> on iichb0 iic0: <I2C generic I/O> on iicbus0 ugen0.1: <0x1106 XHCI root HUB> at usbus0 uhub0 on usbus0 uhub0: <0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 … uhub0: 5 ports with 4 removable, self powered … ugen0.2: <Unknown > at usbus0 (disconnected) uhub0: at usbus0, port 1, addr 1 (disconnected) uhub0: detached uhub0 on usbus0 uhub0: <0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/nss /usr/local/lib/perl5/5.30/mach/CORE /usr/local/lib/samba4 /usr/local/llvm80/lib … Setting up harvesting: [UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,[NET_ETHER],NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED Feeding entropy: uhub0: 5 ports wit … xhci0: Resetting controller ugen0.2: <Unknown > at usbus0 (disconnected) uhub0: at usbus0, port 1, addr 1 (disconnected) uhub0: detached uhub0 on usbus0 uhub0: <0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 uhub0: 5 ports with 4 removable, self powered … ugen0.2: <Unknown > at usbus0 (disconnected) uhub0: at usbus0, port 1, addr 1 (disconnected) uhub0: detached .. uhub0 on usbus0 uhub0: <0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 Starting devd. .. uhub0: 5 ports with 4 removable, self powered .. ugen0.2: <vendor 0x2109 USB2.0 Hub> at usbus0 uhub1 on uhub0 uhub1: <vendor 0x2109 USB2.0 Hub, class 9/0, rev 2.10/4.21, addr 1> on usbus0 uhub1: 4 ports with 4 removable, self powered ugen0.3: <Mitsumi Electric Hub in Apple Extended USB Keyboard> at usbus0 uhub2 on uhub1 uhub2: <Mitsumi Electric Hub in Apple Extended USB Keyboard, class 9/0, rev 1.10/4.20, addr 2> on usbus0 uhub2: 3 ports with 2 removable, bus powered ugen0.4: <SIGMACHIP Usb Mouse> at usbus0 ugen0.5: <Mitsumi Electric Apple Extended USB Keyboard> at usbus0 ukbd0 on uhub2 ukbd0: <Mitsumi Electric Apple Extended USB Keyboard, class 0/0, rev 1.10/4.20, addr 4> on usbus0 kbd1 at ukbd0 ugen0.4: <SIGMACHIP Usb Mouse> at usbus0 (disconnected) Starting dhclient. ugen0.4: <SIGMACHIP Usb Mouse> at usbus0 … ums0 on uhub2 ums0: <SIGMACHIP Usb Mouse, class 0/0, rev 1.10/1.10, addr 3> on usbus0 ums0: 3 buttons and [XYZ] coordinates ID=0 uhid0 on uhub2 uhid0: <Mitsumi Electric Apple Extended USB Keyboard, class 0/0, rev 1.10/4.20, addr 4> on usbus0 Autoloading module: uhid.ko Autoloading module: wmt.ko Autoloading module: uhid.ko Autoloading module: ums.ko Starting ums0 moused. — Hotplugging USB-stick : ugen0.6: <SanDisk Ultra USB 3.0> at usbus0 umass0 on uhub0 umass0: <SanDisk Ultra USB 3.0, class 0/0, rev 3.00/1.00, addr 5> on usbus0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: <SanDisk Ultra USB 3.0 1.00> Removable Direct Access SPC-4 SCSI device da0: Serial Number 4C530000260314105595 da0: 400.000MB/s transfers da0: 29327MB (60062500 512 byte sectors) da0: quirks=0x2<NO_6_BYTE> GEOM: da0s2: invalid disklabel. --home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B0A1C72-C4C3-4B32-986D-FBF2970DF12A>