[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-arm
Subject:    [Bug 241428] /dev/fb0 produces "has set "memattr" inconsistently" messages
From:       bugzilla-noreply () freebsd ! org
Date:       2019-10-23 8:54:36
Message-ID: bug-241428-7 () https ! bugs ! freebsd ! org/bugzilla/
[Download RAW message or body]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241428

            Bug ID: 241428
           Summary: /dev/fb0 produces "has set "memattr" inconsistently"
                    messages
           Product: Base System
           Version: CURRENT
          Hardware: arm
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: arm
          Assignee: freebsd-arm@FreeBSD.org
          Reporter: phk@FreeBSD.org

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

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-arm@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]