Bug 241428 - /dev/fb0 produces "has set "memattr" inconsistently" messages
Summary: /dev/fb0 produces "has set "memattr" inconsistently" messages
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: arm (show other bugs)
Version: CURRENT
Hardware: arm Any
: --- Affects Only Me
Assignee: freebsd-arm (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-23 08:54 UTC by Poul-Henning Kamp
Modified: 2019-10-23 08:54 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Poul-Henning Kamp freebsd_committer freebsd_triage 2019-10-23 08:54:36 UTC 
BeagleBoneBlack

FreeBSD-13.0-CURRENT-arm-armv7-BEAGLEBONE-20191018-r353709.img.xz

when starting X-server console spews:

    WARNING: Device driver ttydev has set "memattr" inconsistently (drv 4 pmap 3).
    WARNING: Device driver ttydev has set "memattr" inconsistently (drv 4 pmap 3).
    WARNING: Device driver ttydev has set "memattr" inconsistently (drv 4 pmap 3).

According to a quick glance in the source code, this is impossible.

According to this: 

http://freebsd.1045724.x6.nabble.com/Writing-to-dev-fb0-td6335760.html

I'm not the only one seing it.

This seems relevant:  https://reviews.freebsd.org/D6149