rust fix for netbsd-8
Can the pthread_attr fix for rust mentioned in http://mail-index.netbsd.org/pkgsrc-users/2017/08/03/msg025409.html be pulled up to netbsd-8? I'm getting the same thing there, and rust is required for the latest firefox. Thanks. Gary Duzan
Panic in radeon/drm/linux_idr (netbsd-8)
NetBSD capo.xnet.duzan.org 8.0_BETA NetBSD 8.0_BETA (GENERIC) #15: Fri Jul 21
02:27:38 EDT 2017
r...@bldr.6net.duzan.org:/usr/build/netbsd-8/obj/usr/build/netbsd-8/src/sys/arch/amd64/compile/GENERIC
amd64
# crash -N netbsd.2 -M netbsd.2.core
Crash version 8.0_BETA, image version 8.0_BETA.
System panicked: trap
Backtrace from time of crash is available.
crash> bt
_KERNEL_OPT_NARCNET() at 0
_KERNEL_OPT_NARCNET() at 0
vpanic() at vpanic+0x149
snprintf() at snprintf
startlwp() at startlwp
calltrap() at calltrap+0x11
linux_idr_preload_end() at linux_idr_preload_end+0xeb
drm_gem_handle_create_tail() at drm_gem_handle_create_tail+0x88
radeon_gem_create_ioctl() at radeon_gem_create_ioctl+0x98
drm_ioctl() at drm_ioctl+0xfd
sys_ioctl() at sys_ioctl+0x101
syscall() at syscall+0x1bc
--- syscall (number 54) ---
769c5c51771a:
I have reverted some changes to get audio working again, but
otherwise this is netbsd-8 branch from the end of last week.
Gary Duzan
Re: hdaudio1: RIRB timeout in 8.0_BETA
In Message <20170702022455.71f27115...@xen1.duzan.org>, "Gary Duzan" <g...@duzan.org>wrote: => After upgrading from an earlier netbsd-8 snapshot, I got this on reboot: => =>[...] =>hdaudio1 at pci0 dev 20 function 2: HD Audio Controller =>hdaudio1: interrupting at ioapic0 pin 16 =>hdafg1 at hdaudio1: vendor 10ec product 0892 =>hdafg1: DAC00 8ch: Speaker [Jack] =>hdafg1: DAC01 2ch: HP Out [Jack] =>hdafg1: DIG02 2ch: SPDIF Out [Jack] =>hdafg1: DIG03 2ch: SPDIF Out [Built-In] =>hdafg1: ADC04 2ch: Line In [Jack], Mic In [Jack] =>hdafg1: ADC05 2ch: Mic In [Jack] =>hdafg1: DIG-In06 2ch: SPDIF In [Jack] =>hdafg1: 8ch/2ch 32000Hz 44100Hz 48000Hz 88200Hz 96000Hz 192000Hz PCM16 PCM20 PCM24 AC3 =>audio0 at hdafg1: full duplex, playback, capture, mmap, independent =>hdaudio1: RIRB timeout =>hdaudio1: RIRB timeout =>hdaudio1: RIRB timeout =>hdaudio1: RIRB timeout =>[...] =>hdaudio1: RIRB timeout =>hdaudio1: RIRB timeout =>hdaudio1: RIRB timeout =>hdaudio1: RIRB timeout =>hdafg1: Virtual format configured - Format SLINEAR, precision 16, channels 2, frequency 48000 =>spkr1 at audio0: PC Speaker (synthesized) =>[...] => => There were enough timeout messages to overflow past the top of =>the dmesg buffer, but here is the uname: => =>NetBSD capo.xnet.duzan.org 8.0_BETA NetBSD 8.0_BETA (GENERIC) #4: Fri Jun 30 08:42:43 EDT 2017 r...@bldr.6net.duzan.org:/usr/build/netbsd-8/obj/usr/build/netbsd-8/src/sys/arch/amd64/compile/GENERIC amd64 => => I get the same message when I try to play any audio. Does this =>ring any bells, or should I go ahead and send-pr it? FWIW, backing out the following changes restores audio: sys/dev/ic/am7930.c 1.54, 1.55 Make vsaudio(4) work again. [nat, ticket #68] sys/dev/aurateconv.c1.20 Enable rate conversion for 8-bit audio. [nat, ticket #69] sys/dev/auconv.c1.27, 1.28 sys/dev/auconv.h1.17, 1.18 sys/dev/mulaw.c 1.29, 1.30 sys/dev/mulaw.h 1.21-1.24 auconv/mulaw.c: allow for 32 bit precision and more filters for conversion between formats. [nat, ticket #70] sys/dev/audio.c 1.359-1.366 sys/dev/audiovar.h 1.56 audio(4): Fix several stability issues. [nat, ticket #71] sys/dev/mulaw.c 1.31, 1.32 Fix big endian bug. [nat, ticket #74] I did try backing out some subsets of these changes, but the best I got was noise from the audio device. Gary Duzan
hdaudio1: RIRB timeout in 8.0_BETA
After upgrading from an earlier netbsd-8 snapshot, I got this on reboot: [...] hdaudio1 at pci0 dev 20 function 2: HD Audio Controller hdaudio1: interrupting at ioapic0 pin 16 hdafg1 at hdaudio1: vendor 10ec product 0892 hdafg1: DAC00 8ch: Speaker [Jack] hdafg1: DAC01 2ch: HP Out [Jack] hdafg1: DIG02 2ch: SPDIF Out [Jack] hdafg1: DIG03 2ch: SPDIF Out [Built-In] hdafg1: ADC04 2ch: Line In [Jack], Mic In [Jack] hdafg1: ADC05 2ch: Mic In [Jack] hdafg1: DIG-In06 2ch: SPDIF In [Jack] hdafg1: 8ch/2ch 32000Hz 44100Hz 48000Hz 88200Hz 96000Hz 192000Hz PCM16 PCM20 PCM24 AC3 audio0 at hdafg1: full duplex, playback, capture, mmap, independent hdaudio1: RIRB timeout hdaudio1: RIRB timeout hdaudio1: RIRB timeout hdaudio1: RIRB timeout hdaudio1: RIRB timeout hdaudio1: RIRB timeout hdaudio1: RIRB timeout hdaudio1: RIRB timeout [...] hdaudio1: RIRB timeout hdaudio1: RIRB timeout hdaudio1: RIRB timeout hdaudio1: RIRB timeout hdafg1: Virtual format configured - Format SLINEAR, precision 16, channels 2, frequency 48000 spkr1 at audio0: PC Speaker (synthesized) [...] There were enough timeout messages to overflow past the top of the dmesg buffer, but here is the uname: NetBSD capo.xnet.duzan.org 8.0_BETA NetBSD 8.0_BETA (GENERIC) #4: Fri Jun 30 08:42:43 EDT 2017 r...@bldr.6net.duzan.org:/usr/build/netbsd-8/obj/usr/build/netbsd-8/src/sys/arch/amd64/compile/GENERIC amd64 I get the same message when I try to play any audio. Does this ring any bells, or should I go ahead and send-pr it? Thanks. Gary Duzan
Seg Faults building devel/gobject-inspection with latest 8.0_BETA
I just upgraded my desktop from 7.1_STABLE to 8.0_BETA, and I'm
in the process of rebuilding all packages using pkg_rolling-replace.
However, I'm getting consistent failures trying to build
devel/gobject-inspection:
NetBSD capo.xnet.duzan.org 8.0_BETA NetBSD 8.0_BETA (GENERIC) #2: Sun Jun 18
18:18:17 EDT 2017
r...@bldr.6net.duzan.org:/usr/build/netbsd-8/obj/usr/build/netbsd-8/src/sys/arch/amd64/compile/GENERIC
amd64
[...]
GEN g-ir-scanner
GEN g-ir-annotation-tool
GISCAN GLib-2.0.gir
/usr/pkg/include/glib/glib-2.0/glib/glib-autocleanups.h:41: syntax error,
unexpected typedef-name, expecting identifier or '(' in 'typedef GAsyncQueue
*GAsyncQueue_autoptr;' at 'GAsyncQueue_autoptr'
/usr/pkg/include/glib/glib-2.0/glib/glib-autocleanups.h:42: syntax error,
unexpected typedef-name, expecting identifier or '(' in 'typedef GBookmarkFile
*GBookmarkFile_autoptr;' at 'GBookmarkFile_autoptr'
/usr/pkg/include/glib/glib-2.0/glib/glib-autocleanups.h:43: syntax error,
unexpected typedef-name, expecting identifier or '(' in 'typedef GBytes
*GBytes_autoptr;' at 'GBytes_autoptr'
/usr/pkg/include/glib/glib-2.0/glib/glib-autocleanups.h:44: syntax error,
unexpected typedef-name, expecting identifier or '(' in 'typedef GChecksum
*GChecksum_autoptr;' at 'GChecksum_autoptr'
/usr/pkg/include/glib/glib-2.0/glib/glib-autocleanups.h:45: syntax error,
unexpected typedef-name, expecting identifier or '(' in 'typedef GDateTime
*GDateTime_autoptr;' at 'GDateTime_autoptr'
[...]
/usr/pkg/include/glib/glib-2.0/glib/glib-autocleanups.h:86: syntax error,
unexpected typedef-name, expecting identifier or '(' in 'typedef GVariantDict
*GVariantDict_autoptr;' at 'GVariantDict_autoptr'
/usr/pkg/include/glib/glib-2.0/glib/glib-autocleanups.h:88: syntax error,
unexpected typedef-name, expecting identifier or '(' in 'typedef GVariantType
*GVariantType_autoptr;' at 'GVariantType_autoptr'
Command
'[u'/usr/pkgsrc/devel/gobject-introspection/work/gobject-introspection-1.50.0/tmp-introspectm6Wk6w/GLib-2.0',
u'--introspect-dump=/usr/pkgsrc/devel/gobject-introspection/work/gobject-introspection-1.50.0/tmp-introspectm6Wk6w/functions.txt,/usr/pkgsrc/devel/gobject-introspection/work/gobject-introspection-1.50.0/tmp-introspectm6Wk6w/dump.xml']'
returned non-zero exit status -11
[1] Segmentation fault (core dumped) CPPFLAGS="-I/usr...
Makefile:3520: recipe for target 'GLib-2.0.gir' failed
[...]
GLib-2.0.core: ELF 64-bit LSB core file x86-64, version 1 (SYSV),
NetBSD-style, from 'GLib-2.0', pid=9686, uid=0, gid=0, nlwps=1, lwp=1 (signal
11/code 32767)
python2.7.core: ELF 64-bit LSB core file x86-64, version 1 (SYSV),
NetBSD-style, from 'python2.7', pid=27916, uid=0, gid=0, nlwps=1, lwp=1 (signal
11/code 32767)
The python stack (what there is of it) looks like:
#0 0x793f79805663 in ?? ()
#1 0x793f79400585 in ?? () from /usr/pkg/lib/libgthread-2.0.so.0
#2 0x793f849fa140 in ?? ()
#3 0x793f79400669 in _fini () from /usr/pkg/lib/libgthread-2.0.so.0
#4 0x in ?? ()
The other core appears to be from some temporary executable
which got cleaned up, so there is even less information in its
stack trace.
#0 0x70f568605663 in ?? ()
#1 0x70f568200585 in ?? ()
#2 0x70f56c2a4e80 in ?? ()
#3 0x70f568200669 in ?? ()
#4 0x in ?? ()
Can anyone else recreate this?
Thanks.
Gary Duzan
Re: USB Issues in 7.1_STABLE
In Message <58fbb951.3000...@netbsd.org>, Nick Hudson <sk...@netbsd.org>wrote: =>On 04/22/17 20:05, Gary Duzan wrote: =>> In Message <58fb8a80.7000...@netbsd.org>, =>> Nick Hudson <sk...@netbsd.org>wrote: =>> =>> =>On 04/22/17 13:57, Gary Duzan wrote: =>> =>> Booting from the installer image, I noticed a couple of USB related =>> =>> issues. First, the boot menu wouldn't recognize my USB keyboard; =>> =>> I had to hit ENTER on my PS/2 keyboard to get the boot to continue. =>> =>> Then the boot process stopped after probing usb1 (see dmesg below), =>> =>> only continuing after I pressed a key on the PS/2 keyboard. It =>> =>> seemed like my USB devices worked after that, but I didn't do any =>> =>> additional testing. =>> =>> =>> =>> Is there anything I can do to help diagnose the problem? =>> => =>> =>xhci debug output please =>> => =>> =>http://www.netbsd.org/docs/kernel/#usb-debugging => =>I mean compile a kernel with XHCI_DEBUG and set xhcidebug=20 and extract =>the output. See the URL for more details The URL mentioned setting it to 5, so perhaps the page needs updating. I'll try with 20 tomorrow. Thanks. Gary =>> All I see different is the kbd probe and hub ordering. (See diff =>> below.) I should correct myself about the boot menu: the USB keyboard =>> doesn't work on that with my March 27 7.1_STABLE bootloader, either, =>> so the only real concern is the boot hang. => => => => => => => =>> => =>> =>> xhci0 at pci2 dev 0 function 0: vendor 0x1033 product 0x0194 (rev. 0x03) =>> =>> xhci0: interrupting at ioapic0 pin 17 =>> =>> xhci0: xHCI version 0.96 =>> =>> usb0 at xhci0: USB revision 3.0 =>> =>> usb1 at xhci0: USB revision 2.0 =>> =>> [boot pauses here] =>> => =>> => =>> =>Not sure NEC controllers are working yet, although does HEAD do any better? =>> =>> It has been a while since I tried, but the result was similar, =>> which was why I held off switching to -current. Getting USB3 working =>> would be awesome, but initially I'd settle for the driver not being =>> troublesome. Again, if there is anything I can do to help, let me =>> know. => =>There's at least of xhci change on HEAD over netbsd-7 and all sorts of =>other fixes, so it'd be good to test HEAD. =>> =>> Gary =>> => =>Thanks, =>Nick
Re: USB Issues in 7.1_STABLE
In Message <58fb8a80.7000...@netbsd.org>, Nick Hudson <sk...@netbsd.org>wrote: =>On 04/22/17 13:57, Gary Duzan wrote: =>> Booting from the installer image, I noticed a couple of USB related =>> issues. First, the boot menu wouldn't recognize my USB keyboard; =>> I had to hit ENTER on my PS/2 keyboard to get the boot to continue. =>> Then the boot process stopped after probing usb1 (see dmesg below), =>> only continuing after I pressed a key on the PS/2 keyboard. It =>> seemed like my USB devices worked after that, but I didn't do any =>> additional testing. =>> =>> Is there anything I can do to help diagnose the problem? => =>xhci debug output please => =>http://www.netbsd.org/docs/kernel/#usb-debugging All I see different is the kbd probe and hub ordering. (See diff below.) I should correct myself about the boot menu: the USB keyboard doesn't work on that with my March 27 7.1_STABLE bootloader, either, so the only real concern is the boot hang. --- installer-dmesg.txt 2017-04-22 08:28:59.0 -0400 +++ dmesg-usbdebug 2017-04-22 14:44:43.0 -0400 @@ -4,10 +4,10 @@ Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. -NetBSD 7.1_STABLE (GENERIC) #40: Fri Apr 21 08:45:52 EDT 2017 +NetBSD 7.1_STABLE (GENERIC) #42: Sat Apr 22 14:36:24 EDT 2017 r...@bldr.6net.duzan.org:/usr/build/netbsd-7/obj/usr/build/netbsd-7/src/sys/arch/amd64/compile/GENERIC total memory = 12028 MB -avail memory = 11661 MB +avail memory = 11657 MB kern.module.path=/stand/amd64/7.1/modules timecounter: Timecounters tick every 10.000 msec timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 @@ -44,7 +44,6 @@ midi0 at pcppi1: PC speaker sysbeep0 at pcppi1 FDC0 (PNP0700) at acpi0 not configured -pckbc1 at acpi0 (PS2K, PNP0303) (kbd port): io 0x60,0x64 irq 1 EXPL (PNP0C02) at acpi0 not configured MEM (PNP0C01) at acpi0 not configured acpiwmi0 at acpi0 (AOD, PNP0C14-0): ACPI WMI Interface @@ -52,9 +51,6 @@ ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131218/hwxface-646) ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-646) attimer1: attached to pcppi1 -pckbd0 at pckbc1 (kbd slot) -pckbc1: using irq 1 for kbd slot -wskbd0 at pckbd0: console keyboard pci0 at mainbus0 bus 0: configuration mode 1 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok pchb0 at pci0 dev 0 function 0: vendor 0x1022 product 0x9601 (rev. 0x00) @@ -177,6 +173,10 @@ amdtemp0 at amdnb_misc0: AMD CPU Temperature Sensors (Family10h) pchb4 at pci0 dev 24 function 4: vendor 0x1022 product 0x1204 (rev. 0x00) isa0 at pcib0 +pckbc0 at isa0 port 0x60-0x64 +pckbd0 at pckbc0 (kbd slot) +pckbc0: using irq 1 for kbd slot +wskbd0 at pckbd0: console keyboard fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2 acpicpu0 at cpu0: ACPI CPU acpicpu0: C1: HLT, lat 0 us, pow 0 mW @@ -200,10 +200,10 @@ uhub3: 5 ports with 5 removable, self powered uhub4 at usb4: vendor 0x1002 OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub4: 5 ports with 5 removable, self powered -uhub5 at usb5: vendor 0x1002 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 -uhub5: 5 ports with 5 removable, self powered -uhub6 at usb6: vendor 0x1002 OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 -uhub6: 2 ports with 2 removable, self powered +uhub5 at usb6: vendor 0x1002 OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 +uhub5: 2 ports with 2 removable, self powered +uhub6 at usb5: vendor 0x1002 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 +uhub6: 5 ports with 5 removable, self powered uhub7 at usb7: vendor 0x1002 OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub7: 4 ports with 4 removable, self powered ahcisata0 port 0: device present, speed: 6.0Gb/s @@ -241,7 +241,7 @@ cd0 at atapibus0 drive 0: cdrom removable cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100) cd0(ahcisata0:4:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100) (using DMA) -uhub9 at uhub5 port 1: USB2.0 Hub, class 9/0, rev 2.00/77.63, addr 2 +uhub9 at uhub6 port 1: USB2.0 Hub, class 9/0, rev 2.00/77.63, addr 2 uhub9: single transaction translator uhub9: 4 ports with 4 removable, self powered umass0 at uhub8 port 1 configuration 1 interface 0 => =>> xhci0 at pci2 dev 0 function 0: vendor 0x1033 product 0x0194 (rev. 0x03) =>> xhci0: interrupting at ioapic0 pin 17 =>> xhci0: xHCI version 0.96 =>> usb0 at xhci0: USB revision 3.0 =>> usb1 at xhci0: USB revision 2.0 =>> [boot pauses here] => => =>Not sure NEC controllers are working yet, although does HEAD do any better? It has been a while since I tried, but the result was similar, which was why I held off switching to -current. Getting USB3 working would be awesome, but initially I'd settle for the driver not being troublesome. Again, if there is anything I can do to help, let me know. Gary =>Thanks, =>Nick => =>
USB Issues in 7.1_STABLE
Booting from the installer image, I noticed a couple of USB related issues. First, the boot menu wouldn't recognize my USB keyboard; I had to hit ENTER on my PS/2 keyboard to get the boot to continue. Then the boot process stopped after probing usb1 (see dmesg below), only continuing after I pressed a key on the PS/2 keyboard. It seemed like my USB devices worked after that, but I didn't do any additional testing. Is there anything I can do to help diagnose the problem? Thanks. Gary Duzan --- Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 7.1_STABLE (GENERIC) #40: Fri Apr 21 08:45:52 EDT 2017 r...@bldr.6net.duzan.org:/usr/build/netbsd-7/obj/usr/build/netbsd-7/src/sys/arch/amd64/compile/GENERIC total memory = 12028 MB avail memory = 11661 MB kern.module.path=/stand/amd64/7.1/modules timecounter: Timecounters tick every 10.000 msec timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 Gigabyte Technology Co., Ltd. GA-880GMA-UD2H ( ) mainbus0 (root) ACPI: RSDP 0xf5df0 14 (v00 GBT ) ACPI: RSDT 0xcfcf1000 3C (v01 GBTGBTUACPI 42302E31 GBTU 01010101) ACPI: FACP 0xcfcf1040 74 (v01 GBTGBTUACPI 42302E31 GBTU 01010101) ACPI: DSDT 0xcfcf10c0 007732 (v01 GBTGBTUACPI 1000 MSFT 0300) ACPI: FACS 0xcfcf 40 ACPI: SSDT 0xcfcf88c0 00088C (v01 PTLTD POWERNOW 0001 LTP 0001) ACPI: HPET 0xcfcf9180 38 (v01 GBTGBTUACPI 42302E31 GBTU 0098) ACPI: MCFG 0xcfcf91c0 3C (v01 GBTGBTUACPI 42302E31 GBTU 01010101) ACPI: MATS 0xcfcf9200 34 (v01 GBT ) ACPI: APIC 0xcfcf8800 BC (v01 GBTGBTUACPI 42302E31 GBTU 01010101) ACPI: All ACPI Tables successfully acquired ioapic0 at mainbus0 apid 2: pa 0xfec0, version 0x21, 24 pins cpu0 at mainbus0 apid 0: AMD Athlon(tm) II X4 640 Processor, id 0x100f53 cpu0: SVM disabled by the BIOS cpu1 at mainbus0 apid 1: AMD Athlon(tm) II X4 640 Processor, id 0x100f53 cpu2 at mainbus0 apid 2: AMD Athlon(tm) II X4 640 Processor, id 0x100f53 cpu3 at mainbus0 apid 3: AMD Athlon(tm) II X4 640 Processor, id 0x100f53 acpi0 at mainbus0: Intel ACPICA 20131218 acpi0: X/RSDT: OemId , AslId <GBTU,01010101> acpi0: SCI interrupting at int 9 timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000 hpet0 at acpi0: high precision event timer (mem 0xfed0-0xfed00400) timecounter: Timecounter "hpet0" frequency 14318180 Hz quality 2000 acpibut0 at acpi0 (PWRB, PNP0C0C): ACPI Power Button SYSR (PNP0C02) at acpi0 not configured PMIO (PNP0C02) at acpi0 not configured attimer1 at acpi0 (TMR, PNP0100): io 0x40-0x43 irq 0 pcppi1 at acpi0 (SPKR, PNP0800): io 0x61 midi0 at pcppi1: PC speaker sysbeep0 at pcppi1 FDC0 (PNP0700) at acpi0 not configured pckbc1 at acpi0 (PS2K, PNP0303) (kbd port): io 0x60,0x64 irq 1 EXPL (PNP0C02) at acpi0 not configured MEM (PNP0C01) at acpi0 not configured acpiwmi0 at acpi0 (AOD, PNP0C14-0): ACPI WMI Interface acpiwmibus at acpiwmi0 not configured ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131218/hwxface-646) ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-646) attimer1: attached to pcppi1 pckbd0 at pckbc1 (kbd slot) pckbc1: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pci0 at mainbus0 bus 0: configuration mode 1 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok pchb0 at pci0 dev 0 function 0: vendor 0x1022 product 0x9601 (rev. 0x00) ppb0 at pci0 dev 1 function 0: vendor 0x1022 product 0x9602 (rev. 0x00) pci1 at ppb0 bus 1 pci1: i/o space, memory space enabled radeon0 at pci1 dev 5 function 0: vendor 0x1002 product 0x9715 (rev. 0x00) hdaudio0 at pci1 dev 5 function 1: HD Audio Controller hdaudio0: interrupting at ioapic0 pin 19 hdafg0 at hdaudio0: ATI RS690/780 HDMI hdafg0: HDMI00 2ch: Digital Out [Jack] hdafg0: 2ch/0ch 44100Hz 48000Hz PCM16 AC3 ppb1 at pci0 dev 9 function 0: vendor 0x1022 product 0x9608 (rev. 0x00) ppb1: PCI Express capability version 2 x1 @ 5.0GT/s pci2 at ppb1 bus 2 pci2: i/o space, memory space enabled, rd/line, wr/inv ok xhci0 at pci2 dev 0 function 0: vendor 0x1033 product 0x0194 (rev. 0x03) xhci0: interrupting at ioapic0 pin 17 xhci0: xHCI version 0.96 usb0 at xhci0: USB revision 3.0 usb1 at xhci0: USB revision 2.0 [boot pauses here] ppb2 at pci0 dev 10 function 0: vendor 0x1022 product 0x9609 (rev. 0x00) ppb2: PCI Express capability version 2 x1 @ 5.0GT/s ppb2: link is x1 @ 2.5GT/s pci3 at ppb2 bus 3 pci3: i/o space, memory space enabled, rd/line, wr/inv ok re0 at pci3 dev 0 function 0: RealTek 8168/8111 PCIe Gigabit Ethernet (rev. 0x06) re0: interrupting at ioapic0 pin 18 re0
xHCI Interrupt Issue?
Booting a freshly built -current amd64 install image seems to mostly work on my netbsd-7 box, but the kernel gets stuck on: uhub0 at usb0: vendor 1033 xHCI Root Hub, class 9/0, rev 1.00/1.00, addr 0 However, if I press keys on my PS/2 keyboard, the boot process continues and I get the installer. (Full dmesg included below.) Is this a known issue? Is there anything I can do to help diagnose it? I'm up for whatever code hackery may be required. Thanks. Gary Duzan Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 7.99.36 (GENERIC) #1: Sun Sep 11 23:56:08 EDT 2016 root@my.build.machine:/usr/build/netbsd-current/obj/usr/build/netbsd-current/src/sys/arch/amd64/compile/GENERIC total memory = 12028 MB avail memory = 11659 MB timecounter: Timecounters tick every 10.000 msec Kernelized RAIDframe activated timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 Gigabyte Technology Co., Ltd. GA-880GMA-UD2H ( ) mainbus0 (root) ACPI: RSDP 0x000F5DF0 14 (v00 GBT ) ACPI: RSDT 0xCFCF1000 3C (v01 GBTGBTUACPI 42302E31 GBTU 01010101) ACPI: FACP 0xCFCF1040 74 (v01 GBTGBTUACPI 42302E31 GBTU 01010101) ACPI: DSDT 0xCFCF10C0 007732 (v01 GBTGBTUACPI 1000 MSFT 0300) ACPI: FACS 0xCFCF 40 ACPI: SSDT 0xCFCF88C0 00088C (v01 PTLTD POWERNOW 0001 LTP 0001) ACPI: HPET 0xCFCF9180 38 (v01 GBTGBTUACPI 42302E31 GBTU 0098) ACPI: MCFG 0xCFCF91C0 3C (v01 GBTGBTUACPI 42302E31 GBTU 01010101) ACPI: MATS 0xCFCF9200 34 (v01 GBT ) ACPI: APIC 0xCFCF8800 BC (v01 GBTGBTUACPI 42302E31 GBTU 01010101) ACPI: 2 ACPI AML tables successfully acquired and loaded ioapic0 at mainbus0 apid 2: pa 0xfec0, version 0x21, 24 pins cpu0 at mainbus0 apid 0 cpu0: AMD Athlon(tm) II X4 640 Processor, id 0x100f53 cpu0: SVM disabled by the BIOS cpu1 at mainbus0 apid 1 cpu1: AMD Athlon(tm) II X4 640 Processor, id 0x100f53 cpu2 at mainbus0 apid 2 cpu2: AMD Athlon(tm) II X4 640 Processor, id 0x100f53 cpu3 at mainbus0 apid 3 cpu3: AMD Athlon(tm) II X4 640 Processor, id 0x100f53 acpi0 at mainbus0: Intel ACPICA 20160527 acpi0: X/RSDT: OemId , AslId <GBTU,01010101> acpi0: MCFG: segment 0, bus 0-255, address 0xe000 acpi0: SCI interrupting at int 9 timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000 hpet0 at acpi0: high precision event timer (mem 0xfed0-0xfed00400) timecounter: Timecounter "hpet0" frequency 14318180 Hz quality 2000 acpibut0 at acpi0 (PWRB, PNP0C0C): ACPI Power Button SYSR (PNP0C02) at acpi0 not configured PMIO (PNP0C02) at acpi0 not configured attimer1 at acpi0 (TMR, PNP0100): io 0x40-0x43 irq 0 pcppi1 at acpi0 (SPKR, PNP0800): io 0x61 midi0 at pcppi1: PC speaker sysbeep0 at pcppi1 FDC0 (PNP0700) at acpi0 not configured pckbc1 at acpi0 (PS2K, PNP0303) (kbd port): io 0x60,0x64 irq 1 EXPL (PNP0C02) at acpi0 not configured MEM (PNP0C01) at acpi0 not configured acpiwmi0 at acpi0 (AOD, PNP0C14-0): ACPI WMI Interface acpiwmibus at acpiwmi0 not configured attimer1: attached to pcppi1 pckbd0 at pckbc1 (kbd slot) pckbc1: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pci0 at mainbus0 bus 0: configuration mode 1 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok pchb0 at pci0 dev 0 function 0: vendor 1022 product 9601 (rev. 0x00) ppb0 at pci0 dev 1 function 0: vendor 1022 product 9602 (rev. 0x00) pci1 at ppb0 bus 1 pci1: i/o space, memory space enabled radeon0 at pci1 dev 5 function 0: vendor 1002 product 9715 (rev. 0x00) hdaudio0 at pci1 dev 5 function 1: HD Audio Controller hdaudio0: interrupting at ioapic0 pin 19 hdafg0 at hdaudio0: vendor 1002 product 791a hdafg0: HDMI00 2ch: Digital Out [Jack] hdafg0: 2ch/0ch 44100Hz 48000Hz PCM16 AC3 ppb1 at pci0 dev 9 function 0: vendor 1022 product 9608 (rev. 0x00) ppb1: PCI Express capability version 2 x1 @ 5.0GT/s pci2 at ppb1 bus 2 pci2: i/o space, memory space enabled, rd/line, wr/inv ok xhci0 at pci2 dev 0 function 0: vendor 1033 product 0194 (rev. 0x03) xhci0: interrupting at ioapic0 pin 17 xhci0: xHCI version 0.96 usb0 at xhci0: USB revision 3.0 ppb2 at pci0 dev 10 function 0: vendor 1022 product 9609 (rev. 0x00) ppb2: PCI Express capability version 2 x1 @ 5.0GT/s ppb2: link is x1 @ 2.5GT/s pci3 at ppb2 bus 3 pci3: i/o space, memory space enabled, rd/line, wr/inv ok re0 at pci3 dev 0 function 0: RealTek 8168/8111 PCIe Gigabit Ethernet (rev. 0x06) re0: interrupting at ioapic0 pin 18 re0: Ethernet address xx:xx:xx:xx:xx:xx re0: using 256 tx descriptors rgephy0 at re0 phy 7: RTL8169S/8
Re: USB scanners and PR 50340
In Message <rmih9g3tkij@fnord.ir.bbn.com>, Greg Troxel <g...@ir.bbn.com>wrote: =>Dave Tyson <dty...@anduin.org.uk> writes: => =>> I note that PR 50340 has been closed and with the latest pkgsrc =>>under current (amd64) my Mustek 1200 UB scanner seems to work OK =>>- but I have comment out the uscanner device in the kernel and use =>>it as a ugen device. It seems that this is the 'new world order' =>>and the sane backend code to handle uscanner devices is deprecated. =>>Given this is the case is there any point in still keeping the =>> =>> uscanner* at uhub? port ? =>> =>> in GENERIC? => =>Quite possibly we should remove (comment out) uscanner in GENERIC. =>ulpt is more controversial, but cups wants to use libusb too. => =>> I am of the same opinion as the PR originator that it is easier =>>to control access permissions with a uscanner device rather than =>>having to open up a whole raft of ugen devices, but I guess the =>>sane developers feel that using libusb makes support easier... => =>Perhaps if we had something called uscanner that would match scanners =>and that libusb would fine, we could have the permissions management of =>direct matching but the cope-with-the-rest-of-the-world benefit of =>libusb. Can we not build some sort of bus-like device to which both the specialized and generic devices can attach which prevents opening both at the same time? Gary Duzan
Re: pathological cvs recursion ?
In Message <20151218115627.40e521d7cf90a5467164a...@pandora.be>, dieter roelants <dieter.net...@pandora.be>wrote: =>On Thu, 17 Dec 2015 16:50:49 -0800 =>bch <brad.har...@gmail.com> wrote: => =>> I've run into this a few times: =>> =>> U external/bsd/libc++/dist/libcxx/test/libcxx/experimental/containers/sequences/src/external/gpl3/binutils/dist/opcodes/aarch64-tbl.h =>> =>> =>> where there are sub-trees seem to be recursively re-added (see =>> .../src/external/gpl3... as part of ./src/external/bsd/...). =>> =>> Has anybody else experienced this ? Does anybody know what's going on ? => =>Hi Brad, => =>I'm almost certain it's because the CVS server has its temp directory =>on a tmpfs. I got reports of the same issue back wen I ran a CVS mirror =>and I "fixed" it by changing the tmpfs to an mfs mount. See also PR 46148. Thanks for the pointer. I got rid of the tmpfs and at least a few updates have gone through cleanly. If anyone has any ideas of how to track this down, I can certainly take a whack at it. It would be nice to know that this isn't going to be a problem for other uses of tmpfs. Gary Duzan
Re: Finding the current network devices
In Message <rmizizg9qqm@fnord.ir.bbn.com>, Greg Troxel <g...@ir.bbn.com>wrote: =>"D'Arcy J.M. Cain" <da...@druid.net> writes: => =>> Maybe Linux has the right idea. The ethernet cards are always eth# no =>> matter what the actual hardware. => =>But how is the ordering determined? The basic issue is that you have =>cables plugged into ports and then interfaces appearing, and ordering is =>based on some probe order, somehow. They have udev to do that. http://serverfault.com/questions/614216/how-do-i-control-the-ordering-of-network-interfaces As you can see from the config example, it can remember the MAC address and assign device names accordingly. Presumably NetBSD would need some kernel facility to rename devices, or maybe provide interface name aliases, to support a similar capability. Gary Duzan
Re: Killing a zombie process?
In Message <pine.neb.4.64.1509241821230.1...@vps1.whooppee.com>, Paul Goyette <p...@vps1.whooppee.com>wrote: =>I'm not sure how I got to this point (but see high-level steps below). =>I have this zombie process: => =>root27237 0.0 0.0 0 0 pts/2- Z - 0:00.00 (sh) => =>Various web resources say "kill the parent" and the zombie child will =>die, too. But that's probably not a good idea here, since the parent is =>(or at least, appears to be) init (pid==1). Can you conform with "ps axl"? =>I checked for other potential parents (ie, any process with pts/2 for =>its TTY), and found two shell processes (one was my "login" shell on =>that terminal, and the other was the result of a "su" command). I =>logged out of both processes, but the zombie remained. => =>This is the second time this has happened, and both times were when I =>was using pkgsrc's mksandbox to rebuild something. The sandbox is =>"almost" standard, created with this command: => => # mksandbox --src=/build/netbsd-local/src \ => --xsrc=/build/netbsd-local/xsrc \ => --rwdirs=/tmp \ => /sandbox => =>(I added the rwdirs=/tmp so that /sandbox/tmp would be a memory-based =>tmpfs filesystem.) => =>I wouldn't usually worry too much about the zombie, but it's running =>/bin/sh _from_within_the_sandbox_ and therefore its image/text file owns =>a reference to /sandbox/bin/sh and this reference prevents me from =>properly unmounting the sandbox. => =>I suppose I could just manually run "umount -f" but I just hate forcing =>an unmount of an in-use file-system. :) => =>Suggestions? If init is really its parent, check its "ps axl" output and check its WCHAN. If it isn't "wait", maybe run "ktruss -p 1" to get an idea of what it is doing instead of wait*() calls. Gary Duzan
ipsec on 7.0_RC1
Has anyone gotten ipsec to work on RC1? NetBSD myhost 7.0_RC1 NetBSD 7.0_RC1 (XEN3_DOMU) #7: Tue Jul 7 11:58:44 EDT 2015 root@mybuildhost:/usr/build/netbsd-7/obj/usr/build/netbsd-7/src/sys/arch/amd64/compile/XEN3_DOMU amd64 app1# /sbin/setkey -f /etc/ipsec.conf pfkey_open: Address family not supported by protocol family 2365 1 setkey CALL __socket30(0x1d,3,2) 2365 1 setkey RET __socket30 -1 errno 47 Address family not supported by protocol family From the kdump output above, it looks like it is trying to call socket(pseudo_AF_KEY, SOCK_RAW, ?). I haven't used this tunnel for a while, but I think it should be working. The tunnel is over IPv6, in case that matters, and I just upgraded this DOMU (via installer kernel/ISO image) from a netbsd-6 snapshot about a year old. A similar setup is still working on my 6.1_STABLE/amd64/DOM0. Thanks. Gary Duzan
Argument list too long error from Linux cross-build
On a recent Arch Linux x86_64 DOMU with netbsd-7 branch src/xsrc I get: [root@lnx src]# ./build.sh -r -x -U -m amd64 tools release live-image | tee ../build-7.log === build.sh command:./build.sh -r -x -U -m amd64 tools release live-image === build.sh started:Sat Mar 28 23:05:51 EDT 2015 === NetBSD version: 7.0_BETA === MACHINE: amd64 === MACHINE_ARCH:x86_64 === Build platform: Linux 3.19.2-1-ARCH x86_64 === HOST_SH: /usr/bin/sh === Bootstrapping nbmake [...] dependall === gmp nbmake[2]: exec(/usr/bin/sh) failed (Argument list too long) *** Failed target: dependall *** Failed command: cd /opt/netbsd/src/tools/gmp; /opt/netbsd/src/obj/tooldir.Linux-3.19.2-1-ARCH-x86_64/bin/nbmake realall *** Error code 1 Stop. [...] ERROR: Failed to make build_install in tools *** BUILD ABORTED *** Adding -N 4 to the build didn't turn up any more information. Any ideas where to look for the next clue? Thanks. Gary Duzan
Re: USB 3.0 status in NetBSD-current?
In Message 47660.34987...@smtp111.sbc.mail.gq1.yahoo.com, Thomas Mueller mueller6...@bellsouth.netwrote: =Is there, or is there supposed to be, USB 3.0 support in the current kernel? = =I see xhci in kernel config, but have not yet been able to access anything on a USB 3.0 port. = =This would be for amd64 and i386 in my case. Yes, though last I checked it wasn't very clean. As I recall, it wasn't handling legacy support properly, causing the boot to hang until a key on the keyboard was pressed. After that, though, I was able to access a USB 2 flash drive on one of my USB 3 ports. YMMV. Gary Duzan
Re: sysctl vm on 6.1_STABLE DOMU
In Message 20131229102854.ga...@antioche.eu.org, Manuel Bouyer bou...@antioche.eu.orgwrote: =On Thu, Dec 26, 2013 at 10:12:00PM -0500, Gary Duzan wrote: = In Message 52ba64e6.8020...@tastylime.net, =Jeff Rizzo r...@tastylime.netwrote: = = =Yeah, this is a problem with the libxc in the dom0; it's been fixed in = =recent versions, but you can't do anything about it in the domU. :( = =Interesting. I know it worked before, though, with earlier = netbsd-6 branch versions. Did something on the NetBSD DOMU side = change to trigger this behavior? = =I don't think so, but an update of the dom0 could have brocken it. =This has been brocken in Xen by a security-related change. = = I'm assuming the DOM0 is Linux, = so if there is a DOM0 bug I would need more detail about it to try = to get it addressed by the hosting folks. = =This has been fixed upstream, but I'm not sure the fix is in a released =version yet. Thanks for the info. I've confirmed that a newer xentools42 does, in fact, fix the problem. Since there is a workaround and upstream is clued in to the fix, that's good enough for me. Thanks. Gary Duzan
Re: sysctl vm on 6.1_STABLE DOMU
In Message 201312240139.rbo1dkea024...@server.cornerstoneservice.ca, John Nemeth jnem...@cue.bc.cawrote: =On Dec 23, 8:18pm, Gary Duzan wrote: =} =}For a month or so, sysctl vm on my 6.1_STABLE amd64/XEN3_DOMU =} machine has errored out with: =} =} systat: nlist: can't find following symbols: =} _intrnames =} _eintrnames =} _intrcnt =} _eintrcnt =} _allevents =} =} Non-Xen amd64 is fine, as are the other sysctl screens. Does this =} sound familiar to anyone, or should I just send-pr? = = You should update. Sorry, I should have been more clear. I just updated from the netbsd-6 branch two days ago, so I am up to date (minus gethnamaddr.c:1.85 and getaddrinfo.c:1.106). I saw the same thing with a netbsd-6 kernel and userland from November 27. Gary Duzan
Re: xhci hang on boot
In Message 5280eddd.5020...@netbsd.org, Nick Hudson sk...@netbsd.orgwrote: =On 11/11/13 14:25, Gary Duzan wrote: = As has been mentioned earlier, the xhci driver causes the boot = process to hang on some machines, including mine. However, it turns = out that a single keystroke on the PS/2 keyboard (the USB one had = not been probed yet) allowed the boot to continue, and I successfully = accessed a USB2 flash drive connected to one of my USB3 ports. I'm = guessing then that there is an interrupt being lost somewhere, or = perhaps a missing timeout. The hang was occurring shortly after = attaching uhub0, as indicated in the dmesg.boot below, and you can = see the umass0 device attaching to it afterwards. = =I guess it's not talking to the legacy USB BIOS stuff properly. = =A quick glance at the code seems to confirm this. I didn't know if it was what you were referring to, but just in case I disabled USB Legacy support in the BIOS, but it didn't help. From that I conclude that it wasn't what you were talking about, but there it is. Thanks. Gary Duzan
Re: amd64 hangs during boot
In Message 526cd990.6070...@msys.ch, Marc Balmer m...@msys.chwrote: =Kernel from freshly built sources from this morning on amd64 hangs =during boot. = =Last message: = =xhci0: xhci_open addr 0 depth 0 port 0 speed 3 I got that when I tried booting a -current installer. Disabling the USB 3 host controller in BIOS allowed it to boot, though obviously without the xhci. xhci was just recently added to GENERIC which is why you are seeing it now. Gary Duzan
