daily CVS update output
Updating src tree: P src/bin/kill/kill.c P src/common/lib/libc/atomic/atomic_c11_compare_exchange_cas_32.c P src/external/mit/ctwm/etc/system.ctwmrc P src/games/gomoku/Makefile P src/games/gomoku/bdinit.c P src/games/gomoku/bdisp.c P src/games/gomoku/gomoku.h P src/games/gomoku/main.c P src/games/gomoku/makemove.c P src/games/gomoku/pickmove.c P src/lib/libcurses/curses_input.3 P src/rescue/list P src/sbin/cgdconfig/Makefile P src/share/man/man9/rnd.9 P src/sys/arch/arm/acpi/cpu_acpi.c P src/sys/arch/arm/arm/cpufunc.c P src/sys/arch/sparc64/dev/vdsk.c P src/sys/arch/sparc64/sparc64/cache.h P src/sys/arch/sparc64/sparc64/locore.s P src/sys/arch/sparc64/sparc64/trap.c P src/sys/dev/pci/if_wm.c P src/sys/dev/sdmmc/ld_sdmmc.c P src/sys/dev/tprof/tprof_armv8.c P src/sys/dev/tprof/tprof_armv8.h P src/usr.sbin/makemandb/apropos.1 P src/usr.sbin/makemandb/apropos.c P src/usr.sbin/sysinst/disks.c P src/usr.sbin/sysinst/msg.mi.de P src/usr.sbin/sysinst/msg.mi.en P src/usr.sbin/sysinst/msg.mi.es P src/usr.sbin/sysinst/msg.mi.fr P src/usr.sbin/sysinst/msg.mi.pl Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 43137984 May 17 03:03 ls-lRA.gz
Re: Using NetBSD-current/amd64 on Sunfire X2200-M2 servers
hello. After close to a month with struggling with this issue, I feel like I have a better understanding of the bge(4) driver, but I still don't have a solution to my specific problem. Following up on my original message regarding this issue, see below, I've figured out how to get the port to autonegotiate speed and duplex at boot time, but I still can't get the ASE/IPMI side of the chip to auto-enable itself as it does under V1.152.4.6 of the if_bge.c file. While I can get the IPMI port to work if I log into the machine once it's booted and type: ifconfig bge1 up; ifconfig bge1 down this does me no good if I have to boot the machine in single user mode for some maintenance purpose. And, no, because of the way one of my installations is set up, abandoning the port that's running in dual-use mode from the NetBSD side of the port isn't an option because the machine in question is remotely located and cannot be physically accessed in a timely manner. So, any thoughts would be helpful in tracking this issue down. -thanks -Brian On Apr 20, 11:02pm, Brian Buhrow wrote: } Subject: Re: Using NetBSD-current/amd64 on Sunfire X2200-M2 servers } hello. Following up on this post, I can now more succinctly describe the problem. } The issue appears to be that when the port is configured at boot time, the media autoselect } code selects 10baset-fdx on the port with ASF running even though the actual speed should be } 100baset-fdx. Typing: } ifconfig bge1 up;ifconfig bge1 down } causes the autoselect code to select the correct speed and duplex. } I realize the ifconfig bge1 down isn't necessary, but I want to show that turning the port off } doesn't revert it to the broken state. } } What I don't understand is what's different between the initial sequence of configuring the } port and doing it again with ifconfig up. I've combed through the if_bge.c file, looking at } the initialization differences between bge_init() and bge_attach(), and they look pretty much } the same relative to the handling of the phy. } Clearly, however, they are not. } Also,I've tried to factor out the differences between what the driver in NetBSD-5.2 does, } versus the current driver, since the 5.2 driver works correctly relative to the ASF firmware. } } Any thoughts anyone might have would be greatly appreciated. I feel I'm close to the answer, } but don't yet have it. } -thanks } -Brian } >-- End of excerpt from Brian Buhrow
Re: uvideo uvm_fault panic
On Sat, May 14, 2022 at 03:30:49PM +, Taylor R Campbell wrote: > > Date: Sat, 14 May 2022 15:14:50 + > > From: sc.dy...@gmail.com > > > > On 2022/05/14 13:47, Taylor R Campbell wrote: > > > Can you please try the two attached patches? > > > > > > 1. uvideobadstream.patch should fix the _crash_ when you try to open a > > >video stream on a device that the driver deemed to have a bad > > >descriptor. Try this one first, if you have time -- it prevents a > > >malicious USB device from causing this kernel crash. > > > > Yes, it fixes crash -- as it prevents attaching video(4)... > > > > > 2. uvideosizeof.patch should fix the sizeof calculations so that the > > >driver stops rejecting your device's descriptor. This one should > > >make your device work again. > > > > It works well again. > > Thanks, committed! Just logged into zoom.us without a panic :-) and now # videoctl -a videoctl: couldn't open '/dev/video0': Input/output error Does this dmesg look sensible? $ dmesg -t | grep video uvideo0 at uhub1 port 6 configuration 1 interface 0: CKFIH12P466071019182 (0x0bda) Integrated_Webcam_HD (0x5531), rev 2.01/81.78, addr 2 video0 at uvideo0: CKFIH12P466071019182 (0x0bda) Integrated_Webcam_HD (0x5531), rev 2.01/81.78, addr 2 video1 at uvideo0: CKFIH12P466071019182 (0x0bda) Integrated_Webcam_HD (0x5531), rev 2.01/81.78, addr 2 uvideo1 at uhub1 port 6 configuration 1 interface 2: CKFIH12P466071019182 (0x0bda) Integrated_Webcam_HD (0x5531), rev 2.01/81.78, addr 2 video2 at uvideo1: CKFIH12P466071019182 (0x0bda) Integrated_Webcam_HD (0x5531), rev 2.01/81.78, addr 2 video3 at uvideo1: CKFIH12P466071019182 (0x0bda) Integrated_Webcam_HD (0x5531), rev 2.01/81.78, addr 2 there is just the one built-in camera... Cheers, Patrick
re: Radeon HD 5450?
Phil Nelson writes:
> On Wed, 11 May 2022 11:15:42 +1000
> matthew green wrote:
>
> > do you have anything else handy to test? gpus are crazy stupid
> > prices these days :-(
>
> Hi Matthew,
>
> My department has several nvidia around and I have not yet found
> one that works to the point of getting X running. I've tried
> the following:
>
>MSI GEFORCE GTX 1060
>GIGABYTE GEFORCE GTX 1650
>EVGA GEFORCE GTX 1018Ti (not enough power)
>An older Radeon I had sitting around, not sure which one but
> it blew up in the same place as the 5450 ... not mapping
> the BIOS.
>The video chip on the motherboard ... it finds it as
> acpivga0 with acpiout0 to acpiout7. It finds a genfb0
> and labels it "Intel Rocket Lake UHD Graphics 750 (32EU) (rev. 0x04)
> It then reports drm at genfb0 not configured. I do get a
> working wscons with 4 screens. "X -configure" quits with
> an error saying that the number of created screens does not
> match number of detected devices. In the Xorg.0.log when
> it probes for the Intel integrated Graphics Chipsets it
> doesn't list the 750 and it doesn't match it.
> I don't have heavy gpu requirements so if I could get the
> intel UHD graphics working, that would be good.
>
> You said you have a working nouveau 730. I'll see if I can
> acquire one of those to try. Any specific card you recommend?
i have asus 730 and asus 1030 silent cards both working for me
in my two main desktop systems now. the 730 did once assert(3)
in libdrm_nouveau and X exited, and the 1030 has one had some
minor display damage (green dots over the root window, likely
generated by my green-on-black terminal, but cleared by simply
moving a window over that space), and it's only been a couple
of weeks using the 730, and few days for 1030.
i don't have anything newer/better due to prices, and also cuz
the above are more than sufficient for my needs.
it's possible that back porting the rocket lake code wouldn't
be too difficult -- that was true a few years back when i did
this for kabylake when skylake was already supported... quick
peek says that RKL appeared right after our drm, sometime between
linux 5.6 and 5.10, and unfortunately, this struct:
static const struct intel_device_info rkl_info = {
in the new code has a couple of new members inside struct
intel_device_info{} than our code, so the back port would need
to consider these parts too.
.mrg.
Re: Radeon HD 5450?
On Wed, 11 May 2022 11:15:42 +1000 matthew green wrote: > do you have anything else handy to test? gpus are crazy stupid > prices these days :-( Hi Matthew, My department has several nvidia around and I have not yet found one that works to the point of getting X running. I've tried the following: MSI GEFORCE GTX 1060 GIGABYTE GEFORCE GTX 1650 EVGA GEFORCE GTX 1018Ti (not enough power) An older Radeon I had sitting around, not sure which one but it blew up in the same place as the 5450 ... not mapping the BIOS. The video chip on the motherboard ... it finds it as acpivga0 with acpiout0 to acpiout7. It finds a genfb0 and labels it "Intel Rocket Lake UHD Graphics 750 (32EU) (rev. 0x04) It then reports drm at genfb0 not configured. I do get a working wscons with 4 screens. "X -configure" quits with an error saying that the number of created screens does not match number of detected devices. In the Xorg.0.log when it probes for the Intel integrated Graphics Chipsets it doesn't list the 750 and it doesn't match it. I don't have heavy gpu requirements so if I could get the intel UHD graphics working, that would be good. You said you have a working nouveau 730. I'll see if I can acquire one of those to try. Any specific card you recommend? --Phil
Automated report: NetBSD-current/i386 build success
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2022.05.16.14.55.56 christos src/rescue/list,v 1.55 2022.05.16.14.57.44 christos src/sbin/cgdconfig/Makefile,v 1.20 Logs can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2022.05.html#2022.05.16.14.57.44
Automated report: NetBSD-current/i386 build failure
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2022.05.16.10.53.14.
An extract from the build.sh output follows:
/tmp/build/2022.05.16.10.53.14-i386/tools/bin/nbctfconvert -g -L VERSION -o
msg_defs.o msg_defs.o.o && rm -f msg_defs.o.o
--- gpt_uuid.o ---
# compile i386/gpt_uuid.o
/tmp/build/2022.05.16.10.53.14-i386/tools/bin/i486--netbsdelf-gcc -Os -Os
-Wno-format-truncation -fcommon -std=gnu99-Wall -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wsystem-headers
-Wno-traditional -Wa,--fatal-warnings -Wreturn-type -Wswitch -Wshadow
-Wcast-qual -Wwrite-strings -Wextra -Wno-unused-parameter -Wno-sign-compare
-Wsign-compare -Wformat=2 -Wno-format-zero-length -Werror -DBOOTSEL
-DWSKBD -D_KERNTYPES --sysroot=/tmp/build/2022.05.16.10.53.14-i386/destdir
-DHAVE_GPT -DHAVE_MBR -DCHECK_ENTROPY=1 -DHAVE_MODULES -I.
-I/tmp/build/2022.05.16.10.53.14-i386/src/usr.sbin/sysinst/arch/i386/../..
-I/tmp/build/2022.05.16.10.53.14-i386/src/usr.sbin/sysinst/arch/i386
-I/tmp/build/2022.05.16.10.53.14-i386/src/usr.sbin/sysinst/arch/i386/../../../../sbin/fsck
-DSETS_TAR_SUFF=\"tgz\" -DREL=\"9.99.96\" -DMACH=\"i386\" -DMACH_i386
-DARCH_i386 -DSYSINST_FTP_HOST=\"nyftp.NetBSD.org\"
-DSYSINST_HTTP_HOST=\"nycdn.NetBSD.org\" -DRE
L_PATH=\"HEAD\" -DPKG_SUBDIR="\"9.0\"" -DNETBSD_MAJOR='"9"'
-DCATALOG_DIR=\"/usr/share/sysinst/catalog\" -DINET6 -c
-I/tmp/build/2022.05.16.10.53.14-i386/src/usr.sbin/sysinst/arch/i386/../../../../sbin/gpt
/tmp/build/2022.05.16.10.53.14-i386/src/usr.sbin/sysinst/arch/i386/../../gpt_uuid.c
-o gpt_uuid.o.o
--- all-ramdisk-cgdroot ---
collect2: error: ld returned 1 exit status
*** Failed target: ramdiskbin
*** Failed commands:
${_MKTARGET_LINK}
=> @echo '# ' " link " ramdisk-cgdroot/ramdiskbin
${_CCLINK.${:Uramdiskbin}} ${_LDFLAGS.${:Uramdiskbin}}
${_LDSTATIC.${:Uramdiskbin}} -o ${.TARGET} ${OBJS.${:Uramdiskbin}}
${_PROGLDOPTS} ${_LDADD.${:Uramdiskbin}}
The following commits were made between the last successful build and
the failed build:
2022.05.16.10.44.06 christos src/sbin/cgdconfig/Makefile,v 1.19
2022.05.16.10.52.09 christos src/rescue/list,v 1.54
2022.05.16.10.53.14 kre src/bin/kill/kill.c,v 1.33
Logs can be found at:
http://releng.NetBSD.org/b5reports/i386/commits-2022.05.html#2022.05.16.10.53.14
