Re: CVS commit: src/sys/arch
Tom Ivar Helbekkmo writes: > This one goes black: > > nouveau0 at pci1 dev 0 function 0: vendor 10de product 06eb (rev. 0xa1) > drm kern info: nouveau [ DEVICE][nouveau0] BOOT0 : 0x298580a2 > drm kern info: nouveau [ DEVICE][nouveau0] Chipset: G98 (NV98) > drm kern info: nouveau [ DEVICE][nouveau0] Family : NV50 ...but works with maya's "big hammer" - albeit without acceleration, so I still can't use mplayer to watch videos on it. -tih -- Most people who graduate with CS degrees don't understand the significance of Lisp. Lisp is the most important idea in computer science. --Alan Kay
Re: CVS commit: src/sys/dev/usb
Sorry, I didn't check whether the module gets compiled.
Thanks,
rin
On 2018/12/12 1:45, Martin Husemann wrote:
Module Name:src
Committed By: martin
Date: Tue Dec 11 16:45:49 UTC 2018
Modified Files:
src/sys/dev/usb: if_mue.c
Log Message:
Avoid signed/unsigned comparision (if_mtu is uint64_t)
To generate a diff of this commit:
cvs rdiff -u -r1.22 -r1.23 src/sys/dev/usb/if_mue.c
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
Modified files:
Index: src/sys/dev/usb/if_mue.c
diff -u src/sys/dev/usb/if_mue.c:1.22 src/sys/dev/usb/if_mue.c:1.23
--- src/sys/dev/usb/if_mue.c:1.22 Tue Dec 11 13:35:02 2018
+++ src/sys/dev/usb/if_mue.cTue Dec 11 16:45:49 2018
@@ -1,4 +1,4 @@
-/* $NetBSD: if_mue.c,v 1.22 2018/12/11 13:35:02 rin Exp $ */
+/* $NetBSD: if_mue.c,v 1.23 2018/12/11 16:45:49 martin Exp $ */
/*$OpenBSD: if_mue.c,v 1.3 2018/08/04 16:42:46 jsg Exp $ */
/*
@@ -20,7 +20,7 @@
/* Driver for Microchip LAN7500/LAN7800 chipsets. */
#include
-__KERNEL_RCSID(0, "$NetBSD: if_mue.c,v 1.22 2018/12/11 13:35:02 rin Exp $");
+__KERNEL_RCSID(0, "$NetBSD: if_mue.c,v 1.23 2018/12/11 16:45:49 martin Exp $");
#ifdef _KERNEL_OPT
#include "opt_usb.h"
@@ -1218,7 +1218,8 @@ mue_encap(struct mue_softc *sc, struct m
M_CSUM_TCPv6 | M_CSUM_UDPv6);
len = m->m_pkthdr.len;
- if (__predict_false((!tso && len > MUE_FRAME_LEN(ifp->if_mtu)) ||
+ if (__predict_false((!tso &&
+ (unsigned)len > MUE_FRAME_LEN(ifp->if_mtu)) ||
( tso && len > MUE_TSO_FRAME_LEN))) {
MUE_PRINTF(sc, "packet length %d\n too long", len);
return EINVAL;
Re: CVS commit: src/sys/arch
I got it working well now :-) thanks. it was MSI. I should see how to disable it for just nouveau.
Re: CVS commit: src/sys/arch
m...@netbsd.org wrote: >On Tue, Dec 11, 2018 at 11:34:30AM -0600, Greg Oster wrote: >> On Tue, 11 Dec 2018 15:23:01 + >> Robert Swindells wrote: >> >> > "Maya Rashish" wrote: >> > >Module Name:src >> > >Committed By: maya >> > >Date: Tue Dec 11 11:00:18 UTC 2018 >> > > >> > >Modified Files: >> > >src/sys/arch/amd64/conf: GENERIC >> > >src/sys/arch/i386/conf: GENERIC >> > > >> > >Log Message: >> > >disable nouveau. it hasn't been functional since the import of new >> > >drmkms code. >> > >> > Nouveau works fine for me. >> > >> > Can we at least get some more data on which GPUs don't work ? >> >> drm kern info: nouveau [ DEVICE][nouveau0] Chipset: GF108 (NVC1) >> drm kern info: nouveau [ DEVICE][nouveau0] Family : NVC0 >> >> Works great with 8.0. Gets into a funky loop of some sort: [snip] >> with -current, and fails to display anything more than a black screen. >> >> Additional details happily provided on request. >My machine does this too, it does however manage to boot and I've even >see it startx. The monitor won't display anything though. I see similar messages on my working system. >Monitor is connected with DP and then a VGA adapter. What do you see in dmesg.boot when it is trying to attach a suitable output device ? The equivalent stage for me is this: ... kern info: nouveau: DRM:0039:0039: init children... kern info: nouveau: DRM:0039:0039: init completed in 378us nouveau0: info: DRM: MM: using M2MF for buffer copies nouveau0: info: DRM: Calling LVDS script 6: nouveau0: info: DRM: 0xD0D8: Parsing digital output script table nouveau0: info: DRM: Setting dpms mode 3 on TV encoder (output 2) nouveaufb0 at nouveau0 nouveaufb0: framebuffer at 0x800045c0d000, size 1280x800, depth 16, stride 2560 nouveau0: info: DRM: Calling LVDS script 2: nouveau0: info: DRM: 0xD13A: Parsing digital output script table nouveau0: info: DRM: Calling LVDS script 5: nouveau0: info: DRM: 0xD0B4: Parsing digital output script table wsdisplay0 at nouveaufb0 kbdmux 1: console (default, vt100 emulation), using wskbd0
Re: CVS commit: src/sys/arch
Robert Swindells writes: > Can we at least get some more data on which GPUs don't work ? This one goes black: nouveau0 at pci1 dev 0 function 0: vendor 10de product 06eb (rev. 0xa1) drm kern info: nouveau [ DEVICE][nouveau0] BOOT0 : 0x298580a2 drm kern info: nouveau [ DEVICE][nouveau0] Chipset: G98 (NV98) drm kern info: nouveau [ DEVICE][nouveau0] Family : NV50 ...as does this one: nouveau0 at pci1 dev 0 function 0: vendor 10de product 1200 (rev. 0xa1) drm kern info: nouveau [ DEVICE][nouveau0] BOOT0 : 0x0ce000a1 drm kern info: nouveau [ DEVICE][nouveau0] Chipset: GF114 (NVCE) drm kern info: nouveau [ DEVICE][nouveau0] Family : NVC0 -tih -- Most people who graduate with CS degrees don't understand the significance of Lisp. Lisp is the most important idea in computer science. --Alan Kay
Re: CVS commit: src/sys/arch
This is a pretty big hammer, but it works. Index: amd64/include/types.h === RCS file: /cvsroot/src/sys/arch/amd64/include/types.h,v retrieving revision 1.58 diff -u -r1.58 types.h --- amd64/include/types.h 15 Nov 2018 04:59:02 - 1.58 +++ amd64/include/types.h 11 Dec 2018 18:41:02 - @@ -108,7 +108,6 @@ #define__HAVE_DIRECT_MAP 1 #endif #if !defined(NO_PCI_MSI_MSIX) -#define__HAVE_PCI_MSI_MSIX #endif #endif #endif
Re: CVS commit: src/sys/arch
m...@netbsd.org wrote: >On Tue, Dec 11, 2018 at 03:23:01PM +, Robert Swindells wrote: >> >> "Maya Rashish" wrote: >> >Module Name:src >> >Committed By: maya >> >Date: Tue Dec 11 11:00:18 UTC 2018 >> > >> >Modified Files: >> >src/sys/arch/amd64/conf: GENERIC >> >src/sys/arch/i386/conf: GENERIC >> > >> >Log Message: >> >disable nouveau. it hasn't been functional since the import of new drmkms >> >code. >> >> Nouveau works fine for me. >> >> Can we at least get some more data on which GPUs don't work ? > >You're not even giving the data yourself I don't own any machines that it doesn't work on.
Re: CVS commit: src/sys/arch
On Tue, Dec 11, 2018 at 11:34:30AM -0600, Greg Oster wrote: > On Tue, 11 Dec 2018 15:23:01 + > Robert Swindells wrote: > > > "Maya Rashish" wrote: > > >Module Name:src > > >Committed By: maya > > >Date: Tue Dec 11 11:00:18 UTC 2018 > > > > > >Modified Files: > > >src/sys/arch/amd64/conf: GENERIC > > >src/sys/arch/i386/conf: GENERIC > > > > > >Log Message: > > >disable nouveau. it hasn't been functional since the import of new > > >drmkms code. > > > > Nouveau works fine for me. > > > > Can we at least get some more data on which GPUs don't work ? > > drm kern info: nouveau [ DEVICE][nouveau0] Chipset: GF108 (NVC1) > drm kern info: nouveau [ DEVICE][nouveau0] Family : NVC0 > > Works great with 8.0. Gets into a funky loop of some sort: > > [ 69.9188746] kern info: nouveau: user:001f906e:fff9: fini > children... > [ 69.9188746] kern info: nouveau: user:001f906e:fff9: > fini running... > [ 69.9188746] kern info: nouveau: user::: fini > children... > [ 69.9188746] kern info: nouveau: user::: fini > running... > [ 69.9188746] kern info: nouveau: user::: fini > completed in 31us > [ 69.9188746] kern info: nouveau: user:001f906e:fff9: fini > completed in 130us > [ 69.9188746] kern info: nouveau: user:001f906e:fff9: destroy > children... > [ 69.9188746] kern info: nouveau: user:001f906e:fff9: destroy > running... > > with -current, and fails to display anything more than a black screen. > > Additional details happily provided on request. My machine does this too, it does however manage to boot and I've even see it startx. The monitor won't display anything though. Monitor is connected with DP and then a VGA adapter. Martin pointed out his machine runs headless so it's not yet certain GF104 works.
Re: CVS commit: src/sys/arch
On Tue, 11 Dec 2018 15:23:01 + Robert Swindells wrote: > "Maya Rashish" wrote: > >Module Name:src > >Committed By: maya > >Date: Tue Dec 11 11:00:18 UTC 2018 > > > >Modified Files: > >src/sys/arch/amd64/conf: GENERIC > >src/sys/arch/i386/conf: GENERIC > > > >Log Message: > >disable nouveau. it hasn't been functional since the import of new > >drmkms code. > > Nouveau works fine for me. > > Can we at least get some more data on which GPUs don't work ? drm kern info: nouveau [ DEVICE][nouveau0] Chipset: GF108 (NVC1) drm kern info: nouveau [ DEVICE][nouveau0] Family : NVC0 Works great with 8.0. Gets into a funky loop of some sort: [ 69.9188746] kern info: nouveau: user:001f906e:fff9: fini children... [ 69.9188746] kern info: nouveau: user:001f906e:fff9: fini running... [ 69.9188746] kern info: nouveau: user::: fini children... [ 69.9188746] kern info: nouveau: user::: fini running... [ 69.9188746] kern info: nouveau: user::: fini completed in 31us [ 69.9188746] kern info: nouveau: user:001f906e:fff9: fini completed in 130us [ 69.9188746] kern info: nouveau: user:001f906e:fff9: destroy children... [ 69.9188746] kern info: nouveau: user:001f906e:fff9: destroy running... with -current, and fails to display anything more than a black screen. Additional details happily provided on request. Later... Greg Oster
Re: CVS commit: src/sys/arch
m...@netbsd.org wrote: >On Tue, Dec 11, 2018 at 05:36:56PM +0100, Martin Husemann wrote: >> On Tue, Dec 11, 2018 at 03:23:01PM +, Robert Swindells wrote: >> > Nouveau works fine for me. >> >> Seems to work fine for me too with -current: >> >> pci1: i/o space, memory space enabled, rd/line, wr/inv ok >> pci1: info: NVIDIA GF104 (0c4100a1) >> nouveau0 at pci1 dev 0 function 0: vendor 10de product 0e22 (rev. 0xa1) >> nouveau0: info: NVIDIA GF104 (0c4100a1) > >Are you sure it's not an optimus setup where nvidia failing to function >would still look fine? Mine isn't an optimus setup. It is a fairly old laptop with an AMD CPU, so there isn't another graphics controller to fall back to. cpu0 at mainbus0 apid 0 cpu0: AMD Turion(tm) 64 Mobile Technology MT-30, id 0x20f42 pci1: i/o space, memory space enabled, rd/line, wr/inv ok pci1: info: NVIDIA NV44 (044700a2) nouveau0 at pci1 dev 0 function 0: vendor 10de product 0167 (rev. 0xa1) nouveau0: info: NVIDIA NV44 (044700a2) I did have to make one local change to the nouveau sources to get it to work, Taylor does know about it. I added calls to printf until I could see where things were going wrong.
Re: CVS commit: src/sys/arch
On Tue, Dec 11, 2018 at 05:36:56PM +0100, Martin Husemann wrote: > On Tue, Dec 11, 2018 at 03:23:01PM +, Robert Swindells wrote: > > Nouveau works fine for me. > > Seems to work fine for me too with -current: > > pci1: i/o space, memory space enabled, rd/line, wr/inv ok > pci1: info: NVIDIA GF104 (0c4100a1) > nouveau0 at pci1 dev 0 function 0: vendor 10de product 0e22 (rev. 0xa1) > nouveau0: info: NVIDIA GF104 (0c4100a1) Are you sure it's not an optimus setup where nvidia failing to function would still look fine? I have a single GTX 770, no other graphics card.
Re: CVS commit: src/sys/arch
On Tue, Dec 11, 2018 at 03:23:01PM +, Robert Swindells wrote: > Nouveau works fine for me. Seems to work fine for me too with -current: pci1: i/o space, memory space enabled, rd/line, wr/inv ok pci1: info: NVIDIA GF104 (0c4100a1) nouveau0 at pci1 dev 0 function 0: vendor 10de product 0e22 (rev. 0xa1) nouveau0: info: NVIDIA GF104 (0c4100a1) Martin
Re: CVS commit: src/sys/arch
"Maya Rashish" wrote: >Module Name:src >Committed By: maya >Date: Tue Dec 11 11:00:18 UTC 2018 > >Modified Files: >src/sys/arch/amd64/conf: GENERIC >src/sys/arch/i386/conf: GENERIC > >Log Message: >disable nouveau. it hasn't been functional since the import of new drmkms >code. Nouveau works fine for me. Can we at least get some more data on which GPUs don't work ?
Re: CVS commit: src/sys/arch
On Tue, Dec 11, 2018 at 03:23:01PM +, Robert Swindells wrote: > > "Maya Rashish" wrote: > >Module Name:src > >Committed By: maya > >Date: Tue Dec 11 11:00:18 UTC 2018 > > > >Modified Files: > >src/sys/arch/amd64/conf: GENERIC > >src/sys/arch/i386/conf: GENERIC > > > >Log Message: > >disable nouveau. it hasn't been functional since the import of new drmkms > >code. > > Nouveau works fine for me. > > Can we at least get some more data on which GPUs don't work ? You're not even giving the data yourself
Re: CVS commit: src
Le 11/12/2018 à 13:42, Nick Hudson a écrit : On 02/12/2018 21:00, Maxime Villard wrote: Module Name:src Committed By:maxv Date:Sun Dec 2 21:00:13 UTC 2018 Modified Files: src/share/mk: bsd.sys.mk src/sys/arch/amd64/conf: GENERIC src/sys/arch/amd64/include: param.h src/sys/conf: files ssp.mk src/sys/kern: files.kern subr_pool.c sys_syscall.c src/sys/sys: systm.h src/sys/uvm: uvm_km.c Added Files: src/sys/arch/amd64/include: kleak.h src/sys/kern: subr_kleak.c src/usr.sbin/kleak: Makefile kleak.c Log Message: Introduce KLEAK, a new feature that can detect kernel information leaks. Nice. (just a matter of having the address of .text, and a stack unwinder). Not sure why we need an unwinder for each of ddb, KASAN and KLEAK. Can't we have one? We could. This would mean having a callback to handle each frame.
Re: CVS commit: src
On 02/12/2018 21:00, Maxime Villard wrote: Module Name:src Committed By: maxv Date: Sun Dec 2 21:00:13 UTC 2018 Modified Files: src/share/mk: bsd.sys.mk src/sys/arch/amd64/conf: GENERIC src/sys/arch/amd64/include: param.h src/sys/conf: files ssp.mk src/sys/kern: files.kern subr_pool.c sys_syscall.c src/sys/sys: systm.h src/sys/uvm: uvm_km.c Added Files: src/sys/arch/amd64/include: kleak.h src/sys/kern: subr_kleak.c src/usr.sbin/kleak: Makefile kleak.c Log Message: Introduce KLEAK, a new feature that can detect kernel information leaks. Nice. (just a matter of having the address of .text, and a stack unwinder). Not sure why we need an unwinder for each of ddb, KASAN and KLEAK. Can't we have one? Nick
