Re: iwx and sysupgrade
On Tue, May 04, 2021 at 11:33:31AM BST, Stefan Sperling wrote: > On Tue, May 04, 2021 at 11:15:45AM +0100, Raf Czlonka wrote: > > Unless I'm missing something, Hrvoje's not suing dhclient(8) - as > > there's no 'dhcp' entry in the /etc/hostname.iwx0 - but dhcpleased(8), > > most likely. > > It is happening in the ramdisk kernel, which is still using dhclient > at this point in time regardless of hostname.if keywords. The ramdisk > install/upgrade scripts simply treat 'autoconf' like 'dhcp' and start > dhclient. Thanks for clarifying, Stefan. I now see that both are, relatively, recent changes[0][1]. [0] https://cvsweb.openbsd.org/src/share/man/man5/hostname.if.5.diff?r1=1.74=1.75=h [1] https://cvsweb.openbsd.org/src/distrib/miniroot/install.sub.diff?r1=1.1161=1.1162=h [2] https://cvsweb.openbsd.org/src/distrib/miniroot/install.sub?rev=1.1162=text/x-cvsweb-markup Cheers, Raf
Re: iwx and sysupgrade
On Tue, May 04, 2021 at 11:15:45AM +0100, Raf Czlonka wrote: > Unless I'm missing something, Hrvoje's not suing dhclient(8) - as > there's no 'dhcp' entry in the /etc/hostname.iwx0 - but dhcpleased(8), > most likely. It is happening in the ramdisk kernel, which is still using dhclient at this point in time regardless of hostname.if keywords. The ramdisk install/upgrade scripts simply treat 'autoconf' like 'dhcp' and start dhclient.
Re: iwx and sysupgrade
On 4.5.2021. 12:15, Raf Czlonka wrote: > On Tue, May 04, 2021 at 10:55:37AM BST, Stefan Sperling wrote: >> On Tue, May 04, 2021 at 11:47:43AM +0200, Hrvoje Popovski wrote: >>> I'm not sure that with iwx and eduroam, sysupgrade can finish. Maybe i >>> need to wait longer, will try that ... sysupgrade will finish if iwx is >>> disabled or hostname.iwx0 is removed from etc before doing sysupgrade >> >> If iwx is disabled, dhclient won't be started. The problem for sysupgrade >> is that dhclient never goes into the background when it gets started. This >> has nothing to with iwx. It is about dhclient and 802.1x. >> >> I suspect proper link state reporting doesn't occur with 802.1x and no >> wpa_supplicant running. But I don't know enough. Locate someone who >> understands dhclient, and/or someone who understands our 802.1x hack, >> and they will hopefully find a solution for you. >> > > Unless I'm missing something, Hrvoje's not suing dhclient(8) - as > there's no 'dhcp' entry in the /etc/hostname.iwx0 - but dhcpleased(8), > most likely. > > P.S. Commenting only as an 'eduroam', not iwx(4), user. > > Raf > Hi, i tried with dhclient right now and results are the same .. This isn't big problem for me, i know what i need to do I've sent mail to tech@ because i thought that it's some problem with iwx
Re: iwx and sysupgrade
On Tue, May 04, 2021 at 10:55:37AM BST, Stefan Sperling wrote: > On Tue, May 04, 2021 at 11:47:43AM +0200, Hrvoje Popovski wrote: > > I'm not sure that with iwx and eduroam, sysupgrade can finish. Maybe i > > need to wait longer, will try that ... sysupgrade will finish if iwx is > > disabled or hostname.iwx0 is removed from etc before doing sysupgrade > > If iwx is disabled, dhclient won't be started. The problem for sysupgrade > is that dhclient never goes into the background when it gets started. This > has nothing to with iwx. It is about dhclient and 802.1x. > > I suspect proper link state reporting doesn't occur with 802.1x and no > wpa_supplicant running. But I don't know enough. Locate someone who > understands dhclient, and/or someone who understands our 802.1x hack, > and they will hopefully find a solution for you. > Unless I'm missing something, Hrvoje's not suing dhclient(8) - as there's no 'dhcp' entry in the /etc/hostname.iwx0 - but dhcpleased(8), most likely. P.S. Commenting only as an 'eduroam', not iwx(4), user. Raf
Re: iwx and sysupgrade
On 4.5.2021. 11:55, Stefan Sperling wrote: > On Tue, May 04, 2021 at 11:47:43AM +0200, Hrvoje Popovski wrote: >> I'm not sure that with iwx and eduroam, sysupgrade can finish. Maybe i >> need to wait longer, will try that ... sysupgrade will finish if iwx is >> disabled or hostname.iwx0 is removed from etc before doing sysupgrade > > If iwx is disabled, dhclient won't be started. The problem for sysupgrade > is that dhclient never goes into the background when it gets started. This > has nothing to with iwx. It is about dhclient and 802.1x. > > I suspect proper link state reporting doesn't occur with 802.1x and no > wpa_supplicant running. But I don't know enough. Locate someone who > understands dhclient, and/or someone who understands our 802.1x hack, > and they will hopefully find a solution for you. > Thank you for information and sorry for noise ..
Re: iwx and sysupgrade
On Tue, May 04, 2021 at 11:47:43AM +0200, Hrvoje Popovski wrote: > I'm not sure that with iwx and eduroam, sysupgrade can finish. Maybe i > need to wait longer, will try that ... sysupgrade will finish if iwx is > disabled or hostname.iwx0 is removed from etc before doing sysupgrade If iwx is disabled, dhclient won't be started. The problem for sysupgrade is that dhclient never goes into the background when it gets started. This has nothing to with iwx. It is about dhclient and 802.1x. I suspect proper link state reporting doesn't occur with 802.1x and no wpa_supplicant running. But I don't know enough. Locate someone who understands dhclient, and/or someone who understands our 802.1x hack, and they will hopefully find a solution for you.
Re: iwx and sysupgrade
On 2021-05-04 11:47 +02, Hrvoje Popovski wrote: > I'm not sure that with iwx and eduroam, sysupgrade can finish. Maybe i We have seen bugs before where we would wait for network while doing an automated upgrade. I think bsd.rd should not bring up the network when it detects that it's in sysupgrade mode since it doesn't need it. -- I'm not entirely sure you are real.
Re: iwx and sysupgrade
On 4.5.2021. 11:44, Stefan Sperling wrote: > On Tue, May 04, 2021 at 11:36:01AM +0200, Hrvoje Popovski wrote: >> On 4.5.2021. 11:02, Hrvoje Popovski wrote: >>> i've disabled and stopped wpa_supplicant and reboot laptop and iwx0 >>> didn't get ip but laptop did boot normally .. >>> >>> iwx0: flags=808843 mtu >>> 1500 >>> lladdr xx:xx:xx:xx:xx:xx >>> index 2 priority 4 llprio 3 >>> groups: wlan >>> media: IEEE802.11 autoselect (HT-MCS11 mode 11n) >>> status: no network >>> ieee80211: join eduroam wpaprotos wpa2 wpaakms 802.1x wpaciphers >>> ccmp wpagroupcipher ccmp >>> >>> >> >> sorry, yes, yes same logs appears but not same second as i thought > > Ok, thanks. This is something I might take a look at myself. > > Looks like the firmware is failing to send an association request in > this broken configuration (802.1x enabled but no wpa_supplicant running). > Not that it would help much if it did send the frame, since you cannot get > link anyway without the wpa_supplicant running. But a firmware crash is > not pretty. > > You are in range of an eduroam AP when this happens? > Yes I am. AP is above my head staring at me :)
Re: iwx and sysupgrade
On 4.5.2021. 11:38, Stefan Sperling wrote: > On Tue, May 04, 2021 at 11:02:49AM +0200, Hrvoje Popovski wrote: >> On 4.5.2021. 10:47, Stefan Sperling wrote: >>> On Tue, May 04, 2021 at 10:32:02AM +0200, Hrvoje Popovski wrote: >>>> Hi all, >>>> >>>> today i tried to do sysupgrade and it wouldn't finish because of iwx >>>> errors. >>>> iwx is working just fine with with snapshots, even with eduroam :) >>>> >>>> e14gen2# cat /etc/hostname.iwx0 >>>> debug >>>> join "eduroam" wpa wpaakms 802.1x >>>> autoconf >>> >>> You probably have wpa_supplicant running when it works, right? >> >> yes ... >> >>> Does this issue really occur only in bsd.rd, or can this be reproduced >>> on any kernel while wpa_supplicant is not running? >> >> i've disabled and stopped wpa_supplicant and reboot laptop and iwx0 >> didn't get ip but laptop did boot normally .. >> >> iwx0: flags=808843 mtu >> 1500 >> lladdr xx:xx:xx:xx:xx:xx >> index 2 priority 4 llprio 3 >> groups: wlan >> media: IEEE802.11 autoselect (HT-MCS11 mode 11n) >> status: no network >> ieee80211: join eduroam wpaprotos wpa2 wpaakms 802.1x wpaciphers >> ccmp wpagroupcipher ccmp > > Hmm. OK. > > I have no idea how exactly 802.1x is supposed to work. > I am not the person who added support for 802.1x. I have never used it, > and I don't have a wpa enterprise setup. > > Nevertheless, I can reproduce the following: > > I think your problem is that dhclient is waiting for link to come up in > the foreground, long enough that the sysupgrade watchdog timeout triggers > and the system reboots. > > (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s > # ifconfig iwx0 join "eduroam" wpa wpaakms 802.1x > # cd /dev > # sh MAKEDEV sd0 > # fsck -p /dev/sd0a > /dev/rsd0a: file system is clean; not checking > # mount /dev/sd0a /mnt > # route monitor & > [1] 26254 > # dhclient iwx0 > iwx0: hw rev 0x340, fw ver 48.1335886879.0, address d0:ab:d5:f4:6b:31 > got message of size 200 on Tue May 4 09:32:35 2021 > RTM_IFINFO: iface status change: len 200, if# 5, name iwx0, link: no carrier, > m> > sockaddrs: > d0:ab:d5:f4:6b:31 > got message of size 96 on Tue May 4 09:32:35 2021 > RTM_PROPOSAL: config proposal: len 96, source dhcp, table 0, if# 5, name > iwx0, 0 > flags: > fmask: > use:0 mtu:0expire:0 > locks: inits: > > > At this point dhclient stays blocked in the foreground, seemingly forever. > The expected behaviour would be that it eventually times out and prints > its "...sleeping" message. > > I don't see any of the iwx firmware errors you are seeing. > But would fixing such iwx errors even help you, given that eduroam is an > entirely useless wifi network for bsd.rd? I'm not sure that with iwx and eduroam, sysupgrade can finish. Maybe i need to wait longer, will try that ... sysupgrade will finish if iwx is disabled or hostname.iwx0 is removed from etc before doing sysupgrade
Re: iwx and sysupgrade
On Tue, May 04, 2021 at 11:36:01AM +0200, Hrvoje Popovski wrote: > On 4.5.2021. 11:02, Hrvoje Popovski wrote: > > i've disabled and stopped wpa_supplicant and reboot laptop and iwx0 > > didn't get ip but laptop did boot normally .. > > > > iwx0: flags=808843 mtu > > 1500 > > lladdr xx:xx:xx:xx:xx:xx > > index 2 priority 4 llprio 3 > > groups: wlan > > media: IEEE802.11 autoselect (HT-MCS11 mode 11n) > > status: no network > > ieee80211: join eduroam wpaprotos wpa2 wpaakms 802.1x wpaciphers > > ccmp wpagroupcipher ccmp > > > > > > sorry, yes, yes same logs appears but not same second as i thought Ok, thanks. This is something I might take a look at myself. Looks like the firmware is failing to send an association request in this broken configuration (802.1x enabled but no wpa_supplicant running). Not that it would help much if it did send the frame, since you cannot get link anyway without the wpa_supplicant running. But a firmware crash is not pretty. You are in range of an eduroam AP when this happens?
Re: iwx and sysupgrade
On Tue, May 04, 2021 at 11:02:49AM +0200, Hrvoje Popovski wrote: > On 4.5.2021. 10:47, Stefan Sperling wrote: > > On Tue, May 04, 2021 at 10:32:02AM +0200, Hrvoje Popovski wrote: > >> Hi all, > >> > >> today i tried to do sysupgrade and it wouldn't finish because of iwx > >> errors. > >> iwx is working just fine with with snapshots, even with eduroam :) > >> > >> e14gen2# cat /etc/hostname.iwx0 > >> debug > >> join "eduroam" wpa wpaakms 802.1x > >> autoconf > > > > You probably have wpa_supplicant running when it works, right? > > yes ... > > > Does this issue really occur only in bsd.rd, or can this be reproduced > > on any kernel while wpa_supplicant is not running? > > i've disabled and stopped wpa_supplicant and reboot laptop and iwx0 > didn't get ip but laptop did boot normally .. > > iwx0: flags=808843 mtu > 1500 > lladdr xx:xx:xx:xx:xx:xx > index 2 priority 4 llprio 3 > groups: wlan > media: IEEE802.11 autoselect (HT-MCS11 mode 11n) > status: no network > ieee80211: join eduroam wpaprotos wpa2 wpaakms 802.1x wpaciphers > ccmp wpagroupcipher ccmp Hmm. OK. I have no idea how exactly 802.1x is supposed to work. I am not the person who added support for 802.1x. I have never used it, and I don't have a wpa enterprise setup. Nevertheless, I can reproduce the following: I think your problem is that dhclient is waiting for link to come up in the foreground, long enough that the sysupgrade watchdog timeout triggers and the system reboots. (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s # ifconfig iwx0 join "eduroam" wpa wpaakms 802.1x # cd /dev # sh MAKEDEV sd0 # fsck -p /dev/sd0a /dev/rsd0a: file system is clean; not checking # mount /dev/sd0a /mnt # route monitor & [1] 26254 # dhclient iwx0 iwx0: hw rev 0x340, fw ver 48.1335886879.0, address d0:ab:d5:f4:6b:31 got message of size 200 on Tue May 4 09:32:35 2021 RTM_IFINFO: iface status change: len 200, if# 5, name iwx0, link: no carrier, m> sockaddrs: d0:ab:d5:f4:6b:31 got message of size 96 on Tue May 4 09:32:35 2021 RTM_PROPOSAL: config proposal: len 96, source dhcp, table 0, if# 5, name iwx0, 0 flags: fmask: use:0 mtu:0expire:0 locks: inits: At this point dhclient stays blocked in the foreground, seemingly forever. The expected behaviour would be that it eventually times out and prints its "...sleeping" message. I don't see any of the iwx firmware errors you are seeing. But would fixing such iwx errors even help you, given that eduroam is an entirely useless wifi network for bsd.rd? The question is why dhclient doesn't go into the background. If it did, then sysupgrade would work. I hope that others who are more familiar with how this is supposed to work could take a look.
Re: iwx and sysupgrade
On 4.5.2021. 11:02, Hrvoje Popovski wrote: > On 4.5.2021. 10:47, Stefan Sperling wrote: >> On Tue, May 04, 2021 at 10:32:02AM +0200, Hrvoje Popovski wrote: >>> Hi all, >>> >>> today i tried to do sysupgrade and it wouldn't finish because of iwx errors. >>> iwx is working just fine with with snapshots, even with eduroam :) >>> >>> e14gen2# cat /etc/hostname.iwx0 >>> debug >>> join "eduroam" wpa wpaakms 802.1x >>> autoconf >> >> You probably have wpa_supplicant running when it works, right? > > yes ... > >> Does this issue really occur only in bsd.rd, or can this be reproduced >> on any kernel while wpa_supplicant is not running? > > i've disabled and stopped wpa_supplicant and reboot laptop and iwx0 > didn't get ip but laptop did boot normally .. > > iwx0: flags=808843 mtu > 1500 > lladdr xx:xx:xx:xx:xx:xx > index 2 priority 4 llprio 3 > groups: wlan > media: IEEE802.11 autoselect (HT-MCS11 mode 11n) > status: no network > ieee80211: join eduroam wpaprotos wpa2 wpaakms 802.1x wpaciphers > ccmp wpagroupcipher ccmp > > sorry, yes, yes same logs appears but not same second as i thought May 4 10:56:37 e14gen2 reorder_kernel: kernel relinking done May 4 10:57:05 e14gen2 /bsd: iwx0: dumping device error log May 4 10:57:05 e14gen2 /bsd: iwx0: Start Error Log Dump: May 4 10:57:05 e14gen2 /bsd: iwx0: Status: 0x9, count: 6 May 4 10:57:05 e14gen2 /bsd: iwx0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL May 4 10:57:05 e14gen2 /bsd: iwx0: 00A0A200 | trm_hw_status0 May 4 10:57:05 e14gen2 /bsd: iwx0: | trm_hw_status1 May 4 10:57:05 e14gen2 /bsd: iwx0: 004F8E3C | branchlink2 May 4 10:57:05 e14gen2 /bsd: iwx0: 00016BFE | interruptlink1 May 4 10:57:05 e14gen2 /bsd: iwx0: 00016BFE | interruptlink2 May 4 10:57:05 e14gen2 /bsd: iwx0: 004F4B14 | data1 May 4 10:57:05 e14gen2 /bsd: iwx0: 1000 | data2 May 4 10:57:05 e14gen2 /bsd: iwx0: F008 | data3 May 4 10:57:05 e14gen2 /bsd: iwx0: 64410D2E | beacon time May 4 10:57:05 e14gen2 /bsd: iwx0: 2485C522 | tsf low May 4 10:57:05 e14gen2 /bsd: iwx0: 0057 | tsf hi May 4 10:57:05 e14gen2 /bsd: iwx0: | time gp1 May 4 10:57:05 e14gen2 /bsd: iwx0: 02BAFA49 | time gp2 May 4 10:57:05 e14gen2 /bsd: iwx0: 0001 | uCode revision type May 4 10:57:05 e14gen2 /bsd: iwx0: 0030 | uCode version major May 4 10:57:05 e14gen2 /bsd: iwx0: 4FA0041F | uCode version minor May 4 10:57:05 e14gen2 /bsd: iwx0: 0340 | hw version May 4 10:57:05 e14gen2 /bsd: iwx0: 18489000 | board version May 4 10:57:05 e14gen2 /bsd: iwx0: 809BFC14 | hcmd May 4 10:57:05 e14gen2 /bsd: iwx0: 2402 | isr0 May 4 10:57:05 e14gen2 /bsd: iwx0: 0100 | isr1 May 4 10:57:05 e14gen2 /bsd: iwx0: 08B2 | isr2 May 4 10:57:05 e14gen2 /bsd: iwx0: 04C1DFCC | isr3 May 4 10:57:05 e14gen2 /bsd: iwx0: | isr4 May 4 10:57:05 e14gen2 /bsd: iwx0: 021C | last cmd Id May 4 10:57:05 e14gen2 /bsd: iwx0: 004F4B14 | wait_event May 4 10:57:05 e14gen2 /bsd: iwx0: 00C0 | l2p_control May 4 10:57:05 e14gen2 /bsd: iwx0: 00018014 | l2p_duration May 4 10:57:05 e14gen2 /bsd: iwx0: 003F | l2p_mhvalid May 4 10:57:05 e14gen2 /bsd: iwx0: | l2p_addr_match May 4 10:57:05 e14gen2 /bsd: iwx0: 000B | lmpm_pmg_sel May 4 10:57:05 e14gen2 /bsd: iwx0: | timestamp May 4 10:57:05 e14gen2 /bsd: iwx0: E808 | flow_handler May 4 10:57:05 e14gen2 /bsd: iwx0: Start UMAC Error Log Dump: May 4 10:57:05 e14gen2 /bsd: iwx0: Status: 0x9, count: 7 May 4 10:57:05 e14gen2 /bsd: iwx0: 0x20003421 | ADVANCED_SYSASSERT May 4 10:57:05 e14gen2 /bsd: iwx0: 0x | umac branchlink1 May 4 10:57:05 e14gen2 /bsd: iwx0: 0xC008CC3C | umac branchlink2 May 4 10:57:05 e14gen2 /bsd: iwx0: 0xC0084696 | umac interruptlink1 May 4 10:57:05 e14gen2 /bsd: iwx0: 0x | umac interruptlink2 May 4 10:57:05 e14gen2 /bsd: iwx0: 0x | umac data1 May 4 10:57:05 e14gen2 /bsd: iwx0: 0x0001 | umac data2 May 4 10:57:05 e14gen2 /bsd: iwx0: 0xDEADBEEF | umac data3 May 4 10:57:05 e14gen2 /bsd: iwx0: 0x0030 | umac major May 4 10:57:05 e14gen2 /bsd: iwx0: 0x4FA0041F | umac minor May 4 10:57:05 e14gen2 /bsd: iwx0: 0x02BAFA3B | frame pointer May 4 10:57:05 e14gen2 /bsd: iwx0: 0xC0885DB0 | stack pointer May 4 10:57:05 e14gen2 /bsd: iwx0: 0x002D0028 | last host cmd May 4 10:57:05 e14gen2 /bsd: iwx0: 0x | isr status reg May 4 10:57:05 e14gen2 /bsd: driver status: May 4 10:57:05 e14gen2 /bsd: tx ring 0: qid=0 cur=46 queued=1 May 4 10:57:05 e14gen2 /bsd: tx ring 1: qid=1 cur=0 queued=0 May 4 10:57:05 e14gen2 /bsd: tx ring 2: qid=2 cur=1 queued=0 May 4 10:57:05 e14gen2 /bsd: tx ring 3: qid=3 cur=0 queued=0 May 4 10:57:05 e14gen2 /bsd: tx ring 4: qid=4 cur=0 queued=0 May 4 10:57:05 e14gen2 /bsd: tx ring 5: qid=5 cur=0 queued=0 May 4 10:57:05 e14gen2 /bsd: tx ring 6: qid=6 cur=0 queued=0 May 4 10:57:05 e14gen2 /bsd: tx ring 7: qid=7 cur=0 queued=0 May 4 10:57:05
Re: iwx and sysupgrade
On 4.5.2021. 10:47, Stefan Sperling wrote: > On Tue, May 04, 2021 at 10:32:02AM +0200, Hrvoje Popovski wrote: >> Hi all, >> >> today i tried to do sysupgrade and it wouldn't finish because of iwx errors. >> iwx is working just fine with with snapshots, even with eduroam :) >> >> e14gen2# cat /etc/hostname.iwx0 >> debug >> join "eduroam" wpa wpaakms 802.1x >> autoconf > > You probably have wpa_supplicant running when it works, right? yes ... > Does this issue really occur only in bsd.rd, or can this be reproduced > on any kernel while wpa_supplicant is not running? i've disabled and stopped wpa_supplicant and reboot laptop and iwx0 didn't get ip but laptop did boot normally .. iwx0: flags=808843 mtu 1500 lladdr xx:xx:xx:xx:xx:xx index 2 priority 4 llprio 3 groups: wlan media: IEEE802.11 autoselect (HT-MCS11 mode 11n) status: no network ieee80211: join eduroam wpaprotos wpa2 wpaakms 802.1x wpaciphers ccmp wpagroupcipher ccmp
Re: iwx and sysupgrade
On Tue, May 04, 2021 at 10:32:02AM +0200, Hrvoje Popovski wrote: > Hi all, > > today i tried to do sysupgrade and it wouldn't finish because of iwx errors. > iwx is working just fine with with snapshots, even with eduroam :) > > e14gen2# cat /etc/hostname.iwx0 > debug > join "eduroam" wpa wpaakms 802.1x > autoconf You probably have wpa_supplicant running when it works, right? Does this issue really occur only in bsd.rd, or can this be reproduced on any kernel while wpa_supplicant is not running?
iwx and sysupgrade
Hi all, today i tried to do sysupgrade and it wouldn't finish because of iwx errors. iwx is working just fine with with snapshots, even with eduroam :) e14gen2# cat /etc/hostname.iwx0 debug join "eduroam" wpa wpaakms 802.1x autoconf e14gen2# ifconfig iwx0 iwx0: flags=808847 mtu 1500 lladdr xx:xx:xx:xx:xx:xx index 2 priority 4 llprio 3 groups: wlan egress media: IEEE802.11 autoselect (HT-MCS11 mode 11n) status: active ieee80211: join eduroam chan 40 bssid yy:yy:yy:yy:yy:yy 83% wpaprotos wpa2 wpaakms 802.1x wpaciphers ccmp wpagroupcipher ccmp inet xxx.xxx.xxx.xxx netmask 0xff00 broadcast xxx.xxx.xxx.xxx if i disable iwx0 or remove hostname.iwx0 from etc, sysupgrade successfully finish dmesg and logs from ramdisk when iwx error happened OpenBSD 6.9-current (RAMDISK_CD) #1: Mon May 3 11:11:38 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 7742496768 (7383MB) avail mem = 7503826944 (7156MB) random: good seed from bootblocks mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0xbf913000 (62 entries) bios0: vendor LENOVO version "R1AET36W (1.12 )" date 03/15/2021 bios0: LENOVO 20T6000TSC acpi0 at bios0: ACPI 6.3 acpi0: tables DSDT FACP SSDT SSDT IVRS SSDT SSDT TPM2 SSDT MSDM BATB HPET APIC MCFG SBST WSMT VFCT SSDT CRAT CDIT FPDT SSDT SSDT SSDT BGRT UEFI SSDT SSDT acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 5 4500U with Radeon Graphics, 2370.85 MHz, 17-60-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 32 pa 0xfec0, version 21, 24 pins, can't remap ioapic1 at mainbus0: apid 33 pa 0xfec01000, version 21, 32 pins, can't remap acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (GPP3) acpiprt2 at acpi0: bus 1 (GPP4) acpiprt3 at acpi0: bus 2 (GPP5) acpiprt4 at acpi0: bus 3 (GPP6) acpiprt5 at acpi0: bus 4 (GP17) acpiprt6 at acpi0: bus -1 (GP18) acpiprt7 at acpi0: bus -1 (GP19) acpiec0 at acpi0 "ACPI0010" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "ACPI0007" at acpi0 not configured "PNP0C0C" at acpi0 not configured acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x acpicmos0 at acpi0 "PNP0C0A" at acpi0 not configured "ACPI0003" at acpi0 not configured "LEN0268" at acpi0 not configured "LEN0130" at acpi0 not configured "LEN0100" at acpi0 not configured "SMB0001" at acpi0 not configured "PNP0C0D" at acpi0 not configured "PNP0C0E" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured amdgpio0 at acpi0 GPIO uid 0 addr 0xfed81500/0x400 irq 7, 184 pins "USBC000" at acpi0 not configured "STM0125" at acpi0 not configured "PNP0C14" at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "AMD 17h/6xh Root Complex" rev 0x00 "AMD 17h/6xh IOMMU" rev 0x00 at pci0 dev 0 function 2 not configured pchb1 at pci0 dev 1 function 0 "AMD 17h/6xh Host" rev 0x00 pchb2 at pci0 dev 2 function 0 "AMD 17h/6xh Host" rev 0x00 ppb0 at pci0 dev 2 function 2 "AMD 17h/6xh PCIE" rev 0x00: msi pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 "Realtek 8168" rev 0x10: RTL8168GU/8111GU (0x5080), msi, address 8c:8c:aa:1a:b2:35 rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 ppb1 at pci0 dev 2 function 3 "AMD 17h/6xh PCIE" rev
