Re: -current boot failure @ wm(4)

2017-07-13 Thread Masanobu SAITOH
Hi, Brad. On 2017/07/14 3:12, bch wrote: Hello NetBSD. I think this maybe related to msaitoh@ work in ./sys/dev/pci/*wm*. The latest kernel begins boot, then just hangs, last 3 lines are (transcribed): wm0 at pci0 dev 25 function 0: PCH2 LAN (82579LM) controller (rev. 0x04) wm0: interrupting

daily CVS update output

2017-07-13 Thread NetBSD source update
Updating src tree: P src/doc/RESPONSIBLE P src/etc/etc.hpcmips/ttys P src/etc/powerd/scripts/sleep_button P src/lib/libc/citrus/citrus_none.c P src/libexec/ld.elf_so/tls.c P src/sbin/route/rtutil.c P src/sys/arch/arm/sunxi/sunxi_platform.c P src/sys/arch/evbarm/conf/SUNXI P

Re: pmc changes break kernels w/makeoptions "COPTS=-Os"

2017-07-13 Thread John D. Baker
On Thu, 13 Jul 2017, John D. Baker wrote: > On Thu, 13 Jul 2017, John D. Baker wrote: > > > Would the following patch be appropriate for appeasing GCC? > > [snip] > > It allows compilation to succeed. Will test run-time soon. A quick > look suggests CPU capability/feature detection is

Re: pmc changes break kernels w/makeoptions "COPTS=-Os"

2017-07-13 Thread John D. Baker
On Thu, 13 Jul 2017, John D. Baker wrote: > Would the following patch be appropriate for appeasing GCC? [snip] It allows compilation to succeed. Will test run-time soon. A quick look suggests CPU capability/feature detection is sufficient to render the pmc code inactive on the net4501. --

pmc changes break kernels w/makeoptions "COPTS=-Os"

2017-07-13 Thread John D. Baker
Kernel configs like "NET4501" routinely include: makeoptions "COPTS=-Os" This causes GCC to emit warnings (treated as errors) if it thinks a variable might be used uninitialized. For example, the following: # compile NET4501_JDB/pmc.o /r1/build/current/tools/amd64/bin/i486--netbsdelf-gcc

-current boot failure @ wm(4)

2017-07-13 Thread bch
Hello NetBSD. I think this maybe related to msaitoh@ work in ./sys/dev/pci/*wm*. The latest kernel begins boot, then just hangs, last 3 lines are (transcribed): wm0 at pci0 dev 25 function 0: PCH2 LAN (82579LM) controller (rev. 0x04) wm0: interrupting at msii vec 0 wm0: wm_init_lcd_from_nvm:

Re: netbsd-8 broken: sbin/fsck_lfs/lfs.c:369:4: error: 'struct inode' has no member named 'i_flag'

2017-07-13 Thread Hubert Feyrer
On Thu, 13 Jul 2017, co...@sdf.org wrote: I renamed i_flag to i_state in -current after the -8 branch. It looks like -current headers being used for building -8. Indeed, this seems to be a local problem. Thanks for the hint! - Hubert

Re: netbsd-8 broken: sbin/fsck_lfs/lfs.c:369:4: error: 'struct inode' has no member named 'i_flag'

2017-07-13 Thread Tom Spindler (moof)
On Thu, Jul 13, 2017 at 10:58:53AM +, co...@sdf.org wrote: > I renamed i_flag to i_state in -current after the -8 branch. > It looks like -current headers being used for building -8. An update build works without issue on my native netbsd-8 box.

Re: netbsd-8 broken: sbin/fsck_lfs/lfs.c:369:4: error: 'struct inode' has no member named 'i_flag'

2017-07-13 Thread coypu
I renamed i_flag to i_state in -current after the -8 branch. It looks like -current headers being used for building -8.

netbsd-8 broken: sbin/fsck_lfs/lfs.c:369:4: error: 'struct inode' has no member named 'i_flag'

2017-07-13 Thread Hubert Feyrer
How can a release branch be broken? Was this not tested before/after the pullup? Or is this some local problem? Where to look? Details below. - Hubert # compile lfs_cleanerd/lfs.o /Users/feyrer/work/NetBSD/cvs/src-8/tooldir.Darwin/bin/x86_64--netbsd-gcc -O2 -fPIE-std=gnu99

nouveau reboot

2017-07-13 Thread Patrick Welche
or "new" reboot: just updated a working 3rd July amd64 kernel with this morning's source, and the computer reboots after printing nouveau, but before drm. Haven't had a chance to dig (won't until tonight) - any first guesses? Cheers, Patrick