Hello,
I thought I'd finally ask about these messages that appear on boot
on my machine.
It's a Lenovo A485, with an AMD Ryzen laptop running CURRENT as of
8 hours ago, in case that's relevant.
Are some of these actionable/would it make sense to take a deeper
look or are they about something needing further debugging with
the "right" hardware?
1. "this should not happen":
FTR:
- I switched the wireless chip for an Intel AC 8265.
- I'm used to having wireless be wlan0, so I rename iwm0 in
rc.conf
- This was connecting to a mobile hotspot, but I've seen the
message on "normal" networks.
And this is what I am seeing in /var/log/messages:
Jan 14 06:33:50 kernel: iwm0: <Intel(R) Dual Band Wireless AC
8265> mem 0xc0a00000-0xc0a01fff at device 0.0 on pci2
Jan 14 06:33:50 kernel: iwm0: hw rev 0x230, fw ver 22.361476.0,
address XX
Jan 14 06:33:50 kernel: wlan0: Ethernet address: XX
Jan 14 06:33:50 kernel: wlan0: link state changed to UP
Jan 14 06:33:50 kernel: iwm0: frame 3/122 b800002c UNHANDLED (this
should not happen)
Jan 14 06:33:50 kernel: iwm0: frame 4/192 b800002c UNHANDLED (this
should not happen)
Jan 14 06:33:50 kernel: iwm0: frame 5/233 b800002c UNHANDLED (this
should not happen)
2. There is also this "driver bug":
Jan 14 06:33:50 kernel: AMD-Vi: IVRS Info VAsize = 64 PAsize = 48
GVAsize = 2 flags:0
Jan 14 06:33:50 kernel: driver bug: Unable to set devclass (class:
ppc devname: (unknown))
3. And "see your local kernel hacker" has been around on my system
for about a year, suspend and resume work just fine.
Jan 14 06:33:52 kernel: __pm_runtime_resume not implemented -- see
your local kernel hacker
Jan 14 06:33:52 kernel: pm_runtime_mark_last_busy not implemented
-- see your local kernel hacker
Jan 14 06:33:52 kernel: __pm_runtime_suspend not implemented --
see your local kernel hacker
Jan 14 06:33:52 kernel: __pm_runtime_resume not implemented -- see
your local kernel hacker
Jan 14 06:33:52 kernel: pm_runtime_mark_last_busy not implemented
-- see your local kernel hacker
Jan 14 06:33:52 kernel: __pm_runtime_suspend not implemented --
see your local kernel hacker
4. Then 'Giant locked and may be deleted':
Jan 14 06:33:50 kernel: WARNING: Device "kbd" is Giant locked and
may be deleted before FreeBSD 13.0.
Jan 14 06:33:50 kernel: WARNING: Device "psm" is Giant locked and
may be deleted before FreeBSD 13.0.
Jan 14 06:33:50 kernel: WARNING: Device "fb" is Giant locked and
may be deleted before FreeBSD 13.0.
I am guessing number 4 has to do with recent changes, and
shouldn't really affect the system if the devices are deleted? Is
there a way I can test if its deletion would leave the system
unusable?
Thank you,
--
Evilham
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
