Re: Resume Issue with em(4) ALPHA7
I'm having also the same problem on my Thinkpad x230. However I'm running a minimal kernel, so usually I do kldunload/kldload if_em, to reset the hardware and to avoid a reboot. Hopefully this gets fixed soon. Cheers, Ali On Sat, Sep 29, 2018 at 7:06 PM Pete Wright wrote: > Hello, > > More suspend/resume testing on my end. This system is a desktop, so not > critical for my daily workflow but wanted to flag it regardless. The > system is a Lenovo m900 with skylake and em(4) NIC. Entering suspend > works without issues, resuming seems to mostly work as well. I.e. no > issues with display or input from keyboard or mouse. > > The one issue I am running into is my NIC is non-functional after > resume. restarting the network stack via "service netif restart" does > not work - as in no DHCP lease is aquired and no link is detected. Nor > does manually down'ing and up'ing the interface work. I see these > messages in my dmesg buffer after resume: > > in6_purgeaddr: err=65, destination address delete failed > lo0: link state changed to DOWN > lo0: link state changed to UP > Link state changed to down > em0: link state changed to DOWN > em0: TX(0) desc avail = 1024, pidx = 0 > em0: TX(0) desc avail = 1024, pidx = 0 > em0: TX(0) desc avail = 1024, pidx = 0 > em0: TX(0) desc avail = 1024, pidx = 0 > > Another thing I noticed is that after resume "ifconfig" hangs for a > couple seconds printing after printing the first line of my em0 device > (after the flags). Not sure if that's helpful but thought it could be a > useful datapoint. > > It is easy to reproduce this, so I am happy to do any additional > debugging or testing on this. > > > Cheers, > > -pete > > -- > Pete Wright > p...@nomadlogic.org > @nomadlogicLA > > ___ > 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" > ___ 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"
devmatch sideeffec: No sound
HW: Thinkpad T480 with T3 Dock. SW: -current, r338952 With devmatch enabled in /etc/rc.conf (the default0, snd_uaudio gets loaded automatically and finds the audio stuff in the dock, which is connected to a screen output(s) I do not use. Firefox ends up with /dev/dsp2.0 which goes there, and as a result I get no sound through the laptops speakers where I expect it. Obvious workaround: Disable devmatch. Yet to be discovered workaround: Prioritize sound devices, when there are multiple. This kind of thing may cause some support-work when 12 comes out... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ 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"
PR id=231810
Hello, Can some kind soul please modify this PR to reflect the Version and the affected people: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810 Thanks matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub signature.asc Description: PGP signature
Re: UEFI Loader problems in CURRENT
If the hung/crash is after printout of bootorder, and the fix (at least in some cases) is about setting the boot device (with linux tools, but I’d assume the efi bootmanager setup would do the same), it means, we do get bad value from efi boot manager variables, and if the fbsd installer and/or boot program update does not include the variable setup, we can not rely on those values in loader. Or, we should have foolproof way to check the values - if we can trust them. Rgds, Toomas > On 30 Sep 2018, at 08:06, Warner Losh wrote: > > Having had a few hours to think about things, I'm starting to think that > the loader may be crashing w/o any clue or traceback. I'll look into this > being a possibility. In the past, this has happened because of an untested > error condition and/or assuming pointers were non-NULL. It would be super > swell if there were a cheap to obtain box that exhibits this problem. > > Warner > >> On Sat, Sep 29, 2018 at 6:14 PM Warner Losh wrote: >> >> Sadly both of these bugs are thin on detail beyond it doesn't work. Makes >> it hard to even look into it. >> >> Warner >> >>> On Sat, Sep 29, 2018, 6:00 PM Yuri wrote: >>> >>> See: >>> >>> * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230090 >>> >>> * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219957 >>> >>> >>> Yuri >>> >>> >>> ___ >>> 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 >>> " >>> >> > ___ > 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" ___ 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"
Re: Resume Issue with em(4) ALPHA7
On Sun, Sep 30, 2018 at 8:24 AM Ali Abdallah wrote: > I'm having also the same problem on my Thinkpad x230. However I'm running a > minimal kernel, so usually I do kldunload/kldload if_em, > to reset the hardware and to avoid a reboot. > > Hopefully this gets fixed soon. > > Hi I've been having the same problem for at least several months with if_em, hw I218-LM and I219-LM. Need to unload and reload if_em to make it work again after resume. /Johannes Cheers, > Ali > > On Sat, Sep 29, 2018 at 7:06 PM Pete Wright wrote: > > > Hello, > > > > More suspend/resume testing on my end. This system is a desktop, so not > > critical for my daily workflow but wanted to flag it regardless. The > > system is a Lenovo m900 with skylake and em(4) NIC. Entering suspend > > works without issues, resuming seems to mostly work as well. I.e. no > > issues with display or input from keyboard or mouse. > > > > The one issue I am running into is my NIC is non-functional after > > resume. restarting the network stack via "service netif restart" does > > not work - as in no DHCP lease is aquired and no link is detected. Nor > > does manually down'ing and up'ing the interface work. I see these > > messages in my dmesg buffer after resume: > > > > in6_purgeaddr: err=65, destination address delete failed > > lo0: link state changed to DOWN > > lo0: link state changed to UP > > Link state changed to down > > em0: link state changed to DOWN > > em0: TX(0) desc avail = 1024, pidx = 0 > > em0: TX(0) desc avail = 1024, pidx = 0 > > em0: TX(0) desc avail = 1024, pidx = 0 > > em0: TX(0) desc avail = 1024, pidx = 0 > > > > Another thing I noticed is that after resume "ifconfig" hangs for a > > couple seconds printing after printing the first line of my em0 device > > (after the flags). Not sure if that's helpful but thought it could be a > > useful datapoint. > > > > It is easy to reproduce this, so I am happy to do any additional > > debugging or testing on this. > > > > > > Cheers, > > > > -pete > > > > -- > > Pete Wright > > p...@nomadlogic.org > > @nomadlogicLA > > > > ___ > > 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" > > > ___ > 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" > ___ 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"
Re: devmatch sideeffec: No sound
On Sun, 30 Sep 2018 07:51:38 + Poul-Henning Kamp wrote: > HW: Thinkpad T480 with T3 Dock. > > SW: -current, r338952 > > With devmatch enabled in /etc/rc.conf (the default0, snd_uaudio > gets loaded automatically and finds the audio stuff in the dock, > which is connected to a screen output(s) I do not use. > > Firefox ends up with /dev/dsp2.0 which goes there, and as a result > I get no sound through the laptops speakers where I expect it. > > Obvious workaround: Disable devmatch. Warner talked about adding blacklist to devmatch > Yet to be discovered workaround: Prioritize sound devices, when > there are multiple. hw.snd.default_unit=XXX hw.snd.default_auto=0 in /etc/sysctl.conf should do the trick. > This kind of thing may cause some support-work when 12 comes out... The only new "issue" is that now with devmatch every hardware got its driver loaded, so on this case this would cause "problems" but for other it solve the problem of finding which driver you need to load to use your usb/pci/blah driver. > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > p...@freebsd.org | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > ___ > 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" -- Emmanuel Vadot ___ 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"
APU Bristol Ridge graphics support
Hello! Is this graphics supported? A10-9700 Bristol Ridge Radeon R7 vgapci0@pci0:0:1:0: class=0x03 card=0x1e201002 chip=0x98741002 rev=0xe2 hdr=0x00 vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]' device = 'Wani [Radeon R5/R6/R7 Graphics]' class = display subclass = VGA ___ 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"
Re: PR id=231810
On 30/09/2018 5:52 pm, Matthias Apitz wrote: > > Hello, > > Can some kind soul please modify this PR to reflect the Version and the > affected people: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810 > > Thanks > > matthias > Hi Matthias, I've updated the Severity, but the Version is better left at the lowest (earliest) reported/confirmed version, to ensure it gets merged back to the relevant stable branch. ./koobs ___ 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"
Re: devmatch sideeffec: No sound
In message <20180930114717.0cfb5e6cdc881f39dbf4b...@bidouilliste.com>, Emmanuel Vadot writes: >On Sun, 30 Sep 2018 07:51:38 + >> Yet to be discovered workaround: Prioritize sound devices, when >> there are multiple. > > hw.snd.default_unit=XXX > hw.snd.default_auto=0 > > in /etc/sysctl.conf should do the trick. Will try. >> This kind of thing may cause some support-work when 12 comes out... > > The only new "issue" is that now with devmatch every hardware got its >driver loaded, so on this case this would cause "problems" but for >other it solve the problem of finding which driver you need to load to >use your usb/pci/blah driver. Ohh, absolutely! Devmatch is a great improvement over "kldload /boot/kernel/*.ko" But until now I had not expected any sideeffects in the "stopped working" category. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ 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"
Re: PR id=231810
El día Sunday, September 30, 2018 a las 08:12:17PM +1000, Kubilay Kocak escribió: > On 30/09/2018 5:52 pm, Matthias Apitz wrote: > > > > Hello, > > > > Can some kind soul please modify this PR to reflect the Version and the > > affected people: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231810 > > > > Thanks > > > > matthias > > > > Hi Matthias, > > I've updated the Severity, but the Version is better left at the lowest > (earliest) reported/confirmed version, to ensure it gets merged back to > the relevant stable branch. Hello Kubilay, At work we use Atlassian's JIRA as bugtracking system. This allows to set multiple versions affected by a single issue. Doesn't bugzilla allow this? Thanks anyway for changing the Severity. If someone needs me for some test to nail down this, I have a system for this. matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub 13. August 2018: Manchmal möchte ich nun einen AUSREISEANTRAG stellen. August 13, 2018: Sometimes I'd like to ask for an exit permission now. ___ 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"
Clang cross-compiling to Cortex-M4 (ARM)
Hello,
With Clang 4.0 cross-compiling works, but any later versions (I tried
5.0, 6.0 and 7.0 from packages) fails. This is the simple test program:
#include
int main() {
return 0;
}
These are the results:
clang -fno-builtin -nostdlib -ffreestanding -target arm-none-eabi
-march=armv7-m -mcpu=cortex-m4 -o test test.c
test.c:1:10: fatal error: 'stdio.h' file not found
#include
^
1 error generated.
clang40 -fno-builtin -nostdlib -ffreestanding -target arm-none-eabi
-march=armv7-m -mcpu=cortex-m4 -o test test.c
/usr/local/bin/arm-none-eabi-ld: warning: cannot find entry symbol _start;
defaulting to 8000
System clang is 6.0.1, but it's the same with the one from packages (to
be precise, clang60 command). I suppose this is more suitable for LLVM
mailing list, but I wanted to check if there's something specific on
FreeBSD I should know about before I write there? Also, this does
compile:
clang -fno-builtin -nostdlib -ffreestanding -target arm-none-eabi
-march=armv7-m -mcpu=cortex-m4 -isystem /usr/include -o test test.c
/usr/bin/ld.lld: warning: cannot find entry symbol _start; defaulting to 0x11000
Besides a course on compilers at University, I don't have much
experience in this field, so feel free to point me to proper
documentation/literature if what I just described is known.
Regards,
meka
signature.asc
Description: PGP signature
Re: devmatch sideeffec: No sound
> HW: Thinkpad T480 with T3 Dock. > > SW: -current, r338952 > > With devmatch enabled in /etc/rc.conf (the default0, snd_uaudio > gets loaded automatically and finds the audio stuff in the dock, > which is connected to a screen output(s) I do not use. > > Firefox ends up with /dev/dsp2.0 which goes there, and as a result > I get no sound through the laptops speakers where I expect it. > > Obvious workaround: Disable devmatch. I have just the opposite issue on my x230, as I use external speakers plugged into the audio jack, and to get them on I have to do a: sysctl hw.snd.default_unit=1 Or it may need to be: sysctl hw.snd.default_unit=0 > Yet to be discovered workaround: Prioritize sound devices, when > there are multiple. > > This kind of thing may cause some support-work when 12 comes out... > -- Rod Grimes rgri...@freebsd.org ___ 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"
Re: APU Bristol Ridge graphics support
On Sunday, September 30, 2018, Rozhuk Ivan wrote: > Hello! > > Is this graphics supported? > > A10-9700 > Bristol Ridge Radeon R7 > > vgapci0@pci0:0:1:0: class=0x03 card=0x1e201002 chip=0x98741002 rev=0xe2 > hdr=0x00 > vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]' > device = 'Wani [Radeon R5/R6/R7 Graphics]' > class = display > subclass = VGA Yes, I've had a Bristol Ridge as a daily driver until a few days ago. Use the LinuxKPI based DRM from ports, if you are on CURRENT graphics/drm-devel-kmod, and load amdgpu.ko. Thanks, Johannes ___ > freebsd-sta...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ 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"
Re: Resume Issue with em(4) ALPHA7
On 9/30/18 1:27 AM, Johannes Lundberg wrote: On Sun, Sep 30, 2018 at 8:24 AM Ali Abdallah wrote: I'm having also the same problem on my Thinkpad x230. However I'm running a minimal kernel, so usually I do kldunload/kldload if_em, to reset the hardware and to avoid a reboot. Hopefully this gets fixed soon. Hi I've been having the same problem for at least several months with if_em, hw I218-LM and I219-LM. Need to unload and reload if_em to make it work again after resume. thanks for the workaround suggestion Ali and Johannes! if there isn't a PR for this yet i'll file one now. -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ 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"
Re: Resume Issue with em(4) ALPHA7
On 9/30/18 10:12 AM, Pete Wright wrote: On 9/30/18 1:27 AM, Johannes Lundberg wrote: On Sun, Sep 30, 2018 at 8:24 AM Ali Abdallah wrote: I'm having also the same problem on my Thinkpad x230. However I'm running a minimal kernel, so usually I do kldunload/kldload if_em, to reset the hardware and to avoid a reboot. Hopefully this gets fixed soon. Hi I've been having the same problem for at least several months with if_em, hw I218-LM and I219-LM. Need to unload and reload if_em to make it work again after resume. thanks for the workaround suggestion Ali and Johannes! if there isn't a PR for this yet i'll file one now. file this PR for those playing along at home: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231828 -p -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ 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"
Re: APU Bristol Ridge graphics support
On Sun, 30 Sep 2018 17:04:26 + Johannes Dieterich wrote: > > A10-9700 > > Bristol Ridge Radeon R7 > > > > vgapci0@pci0:0:1:0: class=0x03 card=0x1e201002 > > chip=0x98741002 rev=0xe2 hdr=0x00 vendor = 'Advanced Micro > > Devices, Inc. [AMD/ATI]' device = 'Wani [Radeon R5/R6/R7 > > Graphics]' class = display > > subclass = VGA > Yes, I've had a Bristol Ridge as a daily driver until a few days ago. > Use the LinuxKPI based DRM from ports, if you are on CURRENT > graphics/drm-devel-kmod, and load amdgpu.ko. > I am on 11.2. I try drm-stable-kmod-g20180822 but it fail to load, as I understand. Is xf86-video-amdgpu must be used with drm-*-kmod* ? ___ 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"
Re: APU Bristol Ridge graphics support
On Sunday, September 30, 2018, Rozhuk Ivan wrote: > On Sun, 30 Sep 2018 17:04:26 + > Johannes Dieterich wrote: > > > > A10-9700 > > > Bristol Ridge Radeon R7 > > > > > > vgapci0@pci0:0:1:0: class=0x03 card=0x1e201002 > > > chip=0x98741002 rev=0xe2 hdr=0x00 vendor = 'Advanced Micro > > > Devices, Inc. [AMD/ATI]' device = 'Wani [Radeon R5/R6/R7 > > > Graphics]' class = display > > > subclass = VGA > > > Yes, I've had a Bristol Ridge as a daily driver until a few days ago. > > Use the LinuxKPI based DRM from ports, if you are on CURRENT > > graphics/drm-devel-kmod, and load amdgpu.ko. > > > > I am on 11.2. > > I try drm-stable-kmod-g20180822 but it fail to load, as I understand. That should work, could you post the error messages? I assume you followed the instructions in the port? > Is xf86-video-amdgpu must be used with drm-*-kmod* ? Yes, you should use the amdgpu DDX with the amdgpu kernel DRM. I used it and it works well but you may also be able to use the modesetting DDX, I haven't tried that. Johannes ___ 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"
Re: APU Bristol Ridge graphics support
On Sun, 30 Sep 2018 18:12:01 + Johannes Dieterich wrote: > > I try drm-stable-kmod-g20180822 but it fail to load, as I > > understand. > That should work, could you post the error messages? I assume you > followed the instructions in the port? # kldload /boot/modules/amdgpu.ko [drm] Initialized [drm] amdgpu kernel modesetting enabled. drmn0: on vgapci0 vgapci0: child drmn0 requested pci_enable_io vgapci0: child drmn0 requested pci_enable_io [drm] initializing kernel modesetting (CARRIZO 0x1002:0x9874 0x1002:0x1E20 0xE2). [drm] register mmio base: 0xFE90 [drm] register mmio size: 262144 [drm] doorbell mmio base: 0xF000 [drm] doorbell mmio size: 8388608 [drm:amdgpu_device_init] Unable to find PCI I/O BAR [drm] probing mlw for device 1002:9874 = 0 [drm] UVD is enabled in physical mode [drm] VCE enabled in physical mode [drm:amdgpu_atombios_init] Unable to find PCI I/O BAR; using MMIO for ATOM IIO ATOM BIOS: BRISTOL [drm] GPU post is not needed Zone kernel: Available graphics memory: 3104154 kiB Zone dma32: Available graphics memory: 2097152 kiB [TTM] Initializing pool allocator drmn0: VRAM: 2048M 0x - 0x7FFF (2048M used) drmn0: GTT: 3031M 0x8000 - 0x00013D7667FF [drm] Detected VRAM RAM=2048M, BAR=256M [drm] RAM width 64bits UNKNOWN [drm] amdgpu: 2048M of VRAM memory ready [drm] amdgpu: 3031M of GTT memory ready. [drm] GART: num cpu pages 776038, num gpu pages 776038 [drm] PCIE GART of 3031M enabled (table at 0x0004). [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] Driver supports precise vblank timestamp query. [drm] amdgpu: irq initialized. amdgpu: powerplay initialized [drm] Connector DP-1: get mode from tunables: [drm] - kern.vt.fb.modes.DP-1 [drm] - kern.vt.fb.default_mode [drm] Connector HDMI-A-1: get mode from tunables: [drm] - kern.vt.fb.modes.HDMI-A-1 [drm] - kern.vt.fb.default_mode [drm] Connector HDMI-A-2: get mode from tunables: [drm] - kern.vt.fb.modes.HDMI-A-2 [drm] - kern.vt.fb.default_mode [drm] AMDGPU Display Connectors [drm] Connector 0: [drm] DP-1 [drm] HPD1 [drm] DDC: 0x4868 0x4868 0x4869 0x4869 0x486a 0x486a 0x486b 0x486b [drm] Encoders: [drm] DFP1: INTERNAL_UNIPHY [drm] Connector 1: [drm] HDMI-A-1 [drm] HPD2 [drm] DDC: 0x486c 0x486c 0x486d 0x486d 0x486e 0x486e 0x486f 0x486f [drm] Encoders: [drm] DFP2: INTERNAL_UNIPHY [drm] Connector 2: [drm] HDMI-A-2 [drm] HPD3 [drm] DDC: 0x4870 0x4870 0x4871 0x4871 0x4872 0x4872 0x4873 0x4873 [drm] Encoders: [drm] DFP3: INTERNAL_UNIPHY1 amdgpu/carrizo_pfp.bin: could not load firmware image, error 2 amdgpu/carrizo_pfp.bin: could not load firmware image, error 2 amdgpu/carrizo_me.bin: could not load firmware image, error 2 amdgpu/carrizo_me.bin: could not load firmware image, error 2 amdgpu/carrizo_ce.bin: could not load firmware image, error 2 amdgpu/carrizo_ce.bin: could not load firmware image, error 2 amdgpu/carrizo_rlc.bin: could not load firmware image, error 2 amdgpu/carrizo_rlc.bin: could not load firmware image, error 2 amdgpu/carrizo_mec.bin: could not load firmware image, error 2 amdgpu/carrizo_mec.bin: could not load firmware image, error 2 amdgpu/carrizo_mec2.bin: could not load firmware image, error 2 amdgpu/carrizo_mec2.bin: could not load firmware image, error 2 drmn0: fence driver on ring 0 use gpu addr 0x8010, cpu addr 0x0xf800444aa010 drmn0: fence driver on ring 1 use gpu addr 0x8020, cpu addr 0x0xf800444aa020 drmn0: fence driver on ring 2 use gpu addr 0x8030, cpu addr 0x0xf800444aa030 drmn0: fence driver on ring 3 use gpu addr 0x8040, cpu addr 0x0xf800444aa040 drmn0: fence driver on ring 4 use gpu addr 0x8050, cpu addr 0x0xf800444aa050 drmn0: fence driver on ring 5 use gpu addr 0x8060, cpu addr 0x0xf800444aa060 drmn0: fence driver on ring 6 use gpu addr 0x8070, cpu addr 0x0xf800444aa070 drmn0: fence driver on ring 7 use gpu addr 0x8080, cpu addr 0x0xf800444aa080 drmn0: fence driver on ring 8 use gpu addr 0x8090, cpu addr 0x0xf800444aa090 amdgpu/carrizo_sdma.bin: could not load firmware image, error 2 amdgpu/carrizo_sdma.bin: could not load firmware image, error 2 amdgpu/carrizo_sdma1.bin: could not load firmware image, error 2 amdgpu/carrizo_sdma1.bin: could not load firmware image, error 2 drmn0: fence driver on ring 9 use gpu addr 0x80a0, cpu addr 0x0xf800444aa0a0 drmn0: fence driver on ring 10 use gpu addr 0x80b0, cpu addr 0x0xf800444aa0b0 amdgpu/carrizo_uvd.bin: could not load firmware image, error 2 amdgpu/carrizo_uvd.bin: could not load firmware image, error 2 [drm] Found UVD firmware Version: 1.91 Family ID: 11 drmn0: fence driver on ring 11 use gpu addr 0x00681560, cpu addr 0x0xf800e0681560 amdgpu/carrizo_vce.bin: could not load firmware image, error 2 amdgpu/carrizo_vce.bin: could not l
Re: APU Bristol Ridge graphics support
On Sunday, September 30, 2018, Rozhuk Ivan wrote: > On Sun, 30 Sep 2018 18:12:01 + > Johannes Dieterich wrote: > > > > I try drm-stable-kmod-g20180822 but it fail to load, as I > > > understand. > > That should work, could you post the error messages? I assume you > > followed the instructions in the port? > > > # kldload /boot/modules/amdgpu.ko > > [drm] Initialized > [drm] amdgpu kernel modesetting enabled. > drmn0: on vgapci0 > vgapci0: child drmn0 requested pci_enable_io > vgapci0: child drmn0 requested pci_enable_io > [drm] initializing kernel modesetting (CARRIZO 0x1002:0x9874 0x1002:0x1E20 > 0xE2). > [drm] register mmio base: 0xFE90 > [drm] register mmio size: 262144 > [drm] doorbell mmio base: 0xF000 > [drm] doorbell mmio size: 8388608 > [drm:amdgpu_device_init] > Unable to find PCI I/O BAR > [drm] probing mlw for device 1002:9874 = 0 > [drm] UVD is enabled in physical mode > [drm] VCE enabled in physical mode > [drm:amdgpu_atombios_init] Unable to find PCI I/O BAR; using MMIO for ATOM IIO > ATOM BIOS: BRISTOL > [drm] GPU post is not needed > Zone kernel: Available graphics memory: 3104154 kiB > Zone dma32: Available graphics memory: 2097152 kiB > [TTM] Initializing pool allocator > drmn0: VRAM: 2048M 0x - 0x7FFF (2048M used) > drmn0: GTT: 3031M 0x8000 - 0x00013D7667FF > [drm] Detected VRAM RAM=2048M, BAR=256M > [drm] RAM width 64bits UNKNOWN > [drm] amdgpu: 2048M of VRAM memory ready > [drm] amdgpu: 3031M of GTT memory ready. > [drm] GART: num cpu pages 776038, num gpu pages 776038 > [drm] PCIE GART of 3031M enabled (table at 0x0004). > [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [drm] Driver supports precise vblank timestamp query. > [drm] amdgpu: irq initialized. > amdgpu: powerplay initialized > [drm] Connector DP-1: get mode from tunables: > [drm] - kern.vt.fb.modes.DP-1 > [drm] - kern.vt.fb.default_mode > [drm] Connector HDMI-A-1: get mode from tunables: > [drm] - kern.vt.fb.modes.HDMI-A-1 > [drm] - kern.vt.fb.default_mode > [drm] Connector HDMI-A-2: get mode from tunables: > [drm] - kern.vt.fb.modes.HDMI-A-2 > [drm] - kern.vt.fb.default_mode > [drm] AMDGPU Display Connectors > [drm] Connector 0: > [drm] DP-1 > [drm] HPD1 > [drm] DDC: 0x4868 0x4868 0x4869 0x4869 0x486a 0x486a 0x486b 0x486b > [drm] Encoders: > [drm] DFP1: INTERNAL_UNIPHY > [drm] Connector 1: > [drm] HDMI-A-1 > [drm] HPD2 > [drm] DDC: 0x486c 0x486c 0x486d 0x486d 0x486e 0x486e 0x486f 0x486f > [drm] Encoders: > [drm] DFP2: INTERNAL_UNIPHY > [drm] Connector 2: > [drm] HDMI-A-2 > [drm] HPD3 > [drm] DDC: 0x4870 0x4870 0x4871 0x4871 0x4872 0x4872 0x4873 0x4873 > [drm] Encoders: > [drm] DFP3: INTERNAL_UNIPHY1 > amdgpu/carrizo_pfp.bin: could not load firmware image, error 2 > amdgpu/carrizo_pfp.bin: could not load firmware image, error 2 > amdgpu/carrizo_me.bin: could not load firmware image, error 2 > amdgpu/carrizo_me.bin: could not load firmware image, error 2 > amdgpu/carrizo_ce.bin: could not load firmware image, error 2 > amdgpu/carrizo_ce.bin: could not load firmware image, error 2 > amdgpu/carrizo_rlc.bin: could not load firmware image, error 2 > amdgpu/carrizo_rlc.bin: could not load firmware image, error 2 > amdgpu/carrizo_mec.bin: could not load firmware image, error 2 > amdgpu/carrizo_mec.bin: could not load firmware image, error 2 > amdgpu/carrizo_mec2.bin: could not load firmware image, error 2 > amdgpu/carrizo_mec2.bin: could not load firmware image, error 2 > drmn0: fence driver on ring 0 use gpu addr 0x8010, cpu addr > 0x0xf800444aa010 > drmn0: fence driver on ring 1 use gpu addr 0x8020, cpu addr > 0x0xf800444aa020 > drmn0: fence driver on ring 2 use gpu addr 0x8030, cpu addr > 0x0xf800444aa030 > drmn0: fence driver on ring 3 use gpu addr 0x8040, cpu addr > 0x0xf800444aa040 > drmn0: fence driver on ring 4 use gpu addr 0x8050, cpu addr > 0x0xf800444aa050 > drmn0: fence driver on ring 5 use gpu addr 0x8060, cpu addr > 0x0xf800444aa060 > drmn0: fence driver on ring 6 use gpu addr 0x8070, cpu addr > 0x0xf800444aa070 > drmn0: fence driver on ring 7 use gpu addr 0x8080, cpu addr > 0x0xf800444aa080 > drmn0: fence driver on ring 8 use gpu addr 0x8090, cpu addr > 0x0xf800444aa090 > amdgpu/carrizo_sdma.bin: could not load firmware image, error 2 > amdgpu/carrizo_sdma.bin: could not load firmware image, error 2 > amdgpu/carrizo_sdma1.bin: could not load firmware image, error 2 > amdgpu/carrizo_sdma1.bin: could not load firmware image, error 2 > drmn0: fence driver on ring 9 use gpu addr 0x80a0, cpu addr > 0x0xf800444aa0a0 > drmn0: fence driver on ring 10 use gpu addr 0x80b0, cpu addr > 0x0xf800444aa0b0 > amdgpu/carrizo_uvd.bin: could not load firmware image, error 2 > amdgpu/carrizo_uvd.bin: could
Re: APU Bristol Ridge graphics support
On Sun, 30 Sep 2018 20:37:07 + Johannes Dieterich wrote: > > finishing device. [TTM] Memory type 2 has not been initialized > > device_attach: drmn0 attach returned 22 > Just to make sure, the gpu-firmware port is installed > and /boot/modules contains these files the load is looking for? Which > drm port gets installed if you use the new graphics/drm-kmod > metaport? If it is next, could you try with that? # pkg version -v | grep gpu gpu-firmware-kmod-g20180825= up-to-date with index xf86-video-amdgpu-1.3.0_3 = up-to-date with index # pkg version -v | grep kmod drm-stable-kmod-g20180822 = up-to-date with index gpu-firmware-kmod-g20180825= up-to-date with index # ls /boot/modules/ | grep carrizo -r-xr-xr-x 1 root wheel13K Aug 26 21:20:06 2018 amdgpu_carrizo_ce_bin.ko* -r-xr-xr-x 1 root wheel21K Aug 26 21:20:06 2018 amdgpu_carrizo_me_bin.ko* -r-xr-xr-x 1 root wheel 261K Aug 26 21:20:06 2018 amdgpu_carrizo_mec_bin.ko* -r-xr-xr-x 1 root wheel 261K Aug 26 21:20:06 2018 amdgpu_carrizo_mec2_bin.ko* -r-xr-xr-x 1 root wheel21K Aug 26 21:20:06 2018 amdgpu_carrizo_pfp_bin.ko* -r-xr-xr-x 1 root wheel23K Aug 26 21:20:06 2018 amdgpu_carrizo_rlc_bin.ko* -r-xr-xr-x 1 root wheel15K Aug 26 21:20:06 2018 amdgpu_carrizo_sdma_bin.ko* -r-xr-xr-x 1 root wheel15K Aug 26 21:20:06 2018 amdgpu_carrizo_sdma1_bin.ko* -r-xr-xr-x 1 root wheel 270K Aug 26 21:20:06 2018 amdgpu_carrizo_uvd_bin.ko* -r-xr-xr-x 1 root wheel 176K Aug 26 21:20:06 2018 amdgpu_carrizo_vce_bin.ko* drm-next requires FreeBSD 12, I do not try it yet. ___ 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"
Re: APU Bristol Ridge graphics support
On Sunday, September 30, 2018, Rozhuk Ivan wrote: > On Sun, 30 Sep 2018 20:37:07 + > Johannes Dieterich wrote: > > > > finishing device. [TTM] Memory type 2 has not been initialized > > > device_attach: drmn0 attach returned 22 > > Just to make sure, the gpu-firmware port is installed > > and /boot/modules contains these files the load is looking for? Which > > drm port gets installed if you use the new graphics/drm-kmod > > metaport? If it is next, could you try with that? > > > # pkg version -v | grep gpu > gpu-firmware-kmod-g20180825= up-to-date with index > xf86-video-amdgpu-1.3.0_3 = up-to-date with index > > # pkg version -v | grep kmod > drm-stable-kmod-g20180822 = up-to-date with index > gpu-firmware-kmod-g20180825= up-to-date with index > > # ls /boot/modules/ | grep carrizo > -r-xr-xr-x 1 root wheel13K Aug 26 21:20:06 2018 > amdgpu_carrizo_ce_bin.ko* > -r-xr-xr-x 1 root wheel21K Aug 26 21:20:06 2018 > amdgpu_carrizo_me_bin.ko* > -r-xr-xr-x 1 root wheel 261K Aug 26 21:20:06 2018 > amdgpu_carrizo_mec_bin.ko* > -r-xr-xr-x 1 root wheel 261K Aug 26 21:20:06 2018 > amdgpu_carrizo_mec2_bin.ko* > -r-xr-xr-x 1 root wheel21K Aug 26 21:20:06 2018 > amdgpu_carrizo_pfp_bin.ko* > -r-xr-xr-x 1 root wheel23K Aug 26 21:20:06 2018 > amdgpu_carrizo_rlc_bin.ko* > -r-xr-xr-x 1 root wheel15K Aug 26 21:20:06 2018 > amdgpu_carrizo_sdma_bin.ko* > -r-xr-xr-x 1 root wheel15K Aug 26 21:20:06 2018 > amdgpu_carrizo_sdma1_bin.ko* > -r-xr-xr-x 1 root wheel 270K Aug 26 21:20:06 2018 > amdgpu_carrizo_uvd_bin.ko* > -r-xr-xr-x 1 root wheel 176K Aug 26 21:20:06 2018 > amdgpu_carrizo_vce_bin.ko* Ok, this looks good. It may be that Bristol is not well supported on DRM 4.9 yet, I need to check that. > > drm-next requires FreeBSD 12, I do not try it yet. It requires a FreeBSD version equal or higher than 1101511, could you provide sysctl kern.osrelease? Johannes ___ 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"
Re: APU Bristol Ridge graphics support
On Sun, 30 Sep 2018 23:21:36 + Johannes Dieterich wrote: > > drm-next requires FreeBSD 12, I do not try it yet. > It requires a FreeBSD version equal or higher than 1101511, could you > provide sysctl kern.osrelease? kern.osrelease: 11.2-STABLE /usr/ports/graphics/drm-kmod /usr/ports/graphics/drm-stable-kmod /usr/ports/graphics/drm-legacy-kmod /usr/ports/graphics/drm-next-kmod /usr/ports/graphics/drm-devel-kmod Too many drm... ___ 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"
Re: APU Bristol Ridge graphics support
* Rozhuk Ivan [180930 23:15]: > On Sun, 30 Sep 2018 20:37:07 + > Johannes Dieterich wrote: > [..] >> Just to make sure, the gpu-firmware port is installed >> and /boot/modules contains these files the load is looking for? Which >> drm port gets installed if you use the new graphics/drm-kmod >> metaport? If it is next, could you try with that? > [..] > drm-next requires FreeBSD 12, I do not try it yet. that is no longer true; drm-next requires at least FreeBSD 11.2 now Wolfgang ___ 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"
Re: APU Bristol Ridge graphics support
On Sunday, September 30, 2018, Rozhuk Ivan wrote: > On Sun, 30 Sep 2018 23:21:36 + > Johannes Dieterich wrote: > > > > > drm-next requires FreeBSD 12, I do not try it yet. > > It requires a FreeBSD version equal or higher than 1101511, could you > > provide sysctl kern.osrelease? > > kern.osrelease: 11.2-STABLE > > /usr/ports/graphics/drm-kmod > /usr/ports/graphics/drm-stable-kmod > /usr/ports/graphics/drm-legacy-kmod > /usr/ports/graphics/drm-next-kmod > /usr/ports/graphics/drm-devel-kmod > > Too many drm... Which is why there is graphics/drm-kmod which will install the most recent recommended DRM for your OS version. Could you try that? ___ 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"
Re: APU Bristol Ridge graphics support
On Sun, 30 Sep 2018 23:38:02 + Johannes Dieterich wrote: > > /usr/ports/graphics/drm-kmod > > /usr/ports/graphics/drm-stable-kmod > > /usr/ports/graphics/drm-legacy-kmod > > /usr/ports/graphics/drm-next-kmod > > /usr/ports/graphics/drm-devel-kmod > > > > Too many drm... > Which is why there is graphics/drm-kmod which will install the most > recent recommended DRM for your OS version. Could you try that? It install graphics/drm-stable-kmod. ___ 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"
Re: APU Bristol Ridge graphics support
On Mon, 1 Oct 2018 01:04:20 +0200 Wolfgang Zenker wrote: > > drm-next requires FreeBSD 12, I do not try it yet. > > that is no longer true; drm-next requires at least FreeBSD 11.2 now Got kernel panic on amdgpu load. ___ 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"
vmstat -m and netstat -m dumping core when run on vmcores
Hi, I've noticed the following rebooting after a panic: pid 41246 (vmstat), uid 0: exited on signal 11 (core dumped) pid 47091 (netstat), uid 0: exited on signal 11 And indeed, trying to manually run those on the resulting vmcore makes them crash: # vmstat -m -M /var/crash/vmcore.0 Segmentation fault (core dumped) # netstat -m -M /var/crash/vmcore.0 Segmentation fault Backtrace is below: * thread #1, name = 'vmstat', stop reason = signal SIGSEGV * frame #0: 0x00080026d19f libmemstat.so.3`memstat_kvm_malloc(list=0x0008007c5000, kvm_handle=0x00080070e000) at memstat_malloc.c:351 frame #1: 0x00204b15 vmstat`main [inlined] domemstat_malloc at vmstat.c:1406 frame #2: 0x00204af4 vmstat`main(argc=, argv=0x7fffeb28) at vmstat.c:386 frame #3: 0x00204095 vmstat`_start(ap=, cleanup=) at crt1.c:74 Wonder if it's just me or something is broken here? ___ 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"
