daily CVS update output
Updating src tree: P src/etc/rc.d/ip6addrctl P src/sys/arch/aarch64/include/types.h P src/sys/arch/arm/arm32/genassym.cf P src/sys/arch/mips/adm5120/dev/ahci.c P src/sys/dev/audio/audio.c P src/sys/dev/ic/sl811hs.c P src/sys/dev/mii/dmphy.c P src/sys/dev/mii/micphy.c P src/sys/dev/usb/ehci.c P src/sys/dev/usb/motg.c P src/sys/dev/usb/ohci.c P src/sys/dev/usb/u3g.c P src/sys/dev/usb/uhci.c P src/sys/dev/usb/umodeswitch.c P src/sys/dev/usb/usbdevs P src/sys/dev/usb/usbdevs.h P src/sys/dev/usb/usbdevs_data.h P src/sys/dev/usb/vhci.c P src/sys/dev/usb/xhci.c U src/sys/external/bsd/common/include/asm/div64.h P src/sys/external/bsd/common/include/linux/kernel.h P src/sys/external/bsd/common/include/linux/list.h P src/sys/external/bsd/drm2/amdgpu/files.amdgpu P src/sys/external/bsd/drm2/dist/drm/drm_agpsupport.c P src/sys/external/bsd/drm2/dist/drm/drm_atomic.c P src/sys/external/bsd/drm2/dist/drm/drm_atomic_helper.c P src/sys/external/bsd/drm2/dist/drm/drm_bufs.c P src/sys/external/bsd/drm2/dist/drm/drm_context.c P src/sys/external/bsd/drm2/dist/drm/drm_crtc.c P src/sys/external/bsd/drm2/dist/drm/drm_crtc_helper.c P src/sys/external/bsd/drm2/dist/drm/drm_dp_helper.c P src/sys/external/bsd/drm2/dist/drm/drm_dp_mst_topology.c P src/sys/external/bsd/drm2/dist/drm/drm_drv.c P src/sys/external/bsd/drm2/dist/drm/drm_edid.c P src/sys/external/bsd/drm2/dist/drm/drm_fb_helper.c P src/sys/external/bsd/drm2/dist/drm/drm_flip_work.c P src/sys/external/bsd/drm2/dist/drm/drm_gem.c P src/sys/external/bsd/drm2/dist/drm/drm_global.c P src/sys/external/bsd/drm2/dist/drm/drm_ioctl.c P src/sys/external/bsd/drm2/dist/drm/drm_irq.c P src/sys/external/bsd/drm2/dist/drm/drm_mm.c P src/sys/external/bsd/drm2/dist/drm/drm_modes.c P src/sys/external/bsd/drm2/dist/drm/drm_modeset_lock.c P src/sys/external/bsd/drm2/dist/drm/drm_plane_helper.c P src/sys/external/bsd/drm2/dist/drm/drm_prime.c P src/sys/external/bsd/drm2/dist/drm/drm_probe_helper.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_atom.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_atombios.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_atombios_crtc.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_atombios_dp.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_atombios_encoders.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_atombios_i2c.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_bo_list.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_cgs.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_ci_dpm.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_ci_smc.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_cik_ih.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_cik_sdma.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_cs.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_ctx.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_cz_dpm.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_cz_ih.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_cz_smc.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_dce_v10_0.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_dce_v11_0.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_dce_v8_0.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_device.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_display.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_dpm.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_fb.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_fence.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_fiji_dpm.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_fiji_smc.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_gem.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_gfx_v7_0.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_gfx_v8_0.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_gmc_v7_0.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_gmc_v8_0.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_i2c.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_iceland_dpm.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_iceland_ih.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_iceland_smc.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_ih.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_kms.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_kv_dpm.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_object.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_object.h P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_ring.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_sdma_v2_4.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_sdma_v3_0.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_test.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_tonga_dpm.c P src/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_tonga_ih.c P
Re: configuring raid using gpt, large drives
Michael van Elst wrote: > MLH wrote: > > I had jsut (apparently) got that working, where the bootloader was > > comoing up from either of my wd2 or wd3 boot wedges and askign for > > the raid0 but then this happened, which is preventing the kernel > > from seeing either wd2 or wd3: > > > > [ 2.152423] ahcisata1 port 5: device present, speed: 3.0Gb/s > > [ 2.152423] ahcisata1 port 0: device present, speed: 3.0Gb/s > > [ 2.152423] ahcisata1 port 4: device present, speed: 3.0Gb/s > > [ 2.752630] autoconfiguration error: ahcisata1 port 5: setting > > WDCTL_RST failed for drive 15 > > [ 2.752630] autoconfiguration error: ahcisata1 port 4: setting > > WDCTL_RST failed for drive 15 > > [ 3.252803] autoconfiguration error: ahcisata1 port 5: drive 15 reset > > failed, disabling PMP > > [ 3.252803] autoconfiguration error: ahcisata1 port 4: drive 15 reset > > failed, disabling PMP > > [ 3.352837] ahcisata1 port 5: device present, speed: 3.0Gb/s > > [ 3.352837] ahcisata1 port 4: device present, speed: 3.0Gb/s > > > > wd0 and wd1 are old drives I really need to take offline. wd1 is > > getting errors. > > How did this "happen" ? This has nothing to do with booting or RAID. Exactly. The bios sees the drives and can start the boot process by loading the NetBSD bootloader from either one of them and that bootloader can read "/netbsd' from either one of them and get that running but then one or both of the drives then disappear *sometimes* so the raid array is not available, or only one of the drives is available. > The disabled PMP should have helped the drive to be used, but apparently > that's didn't work. I have no idea what is going on. What was in the dmesg above is the only clue I have seen that might explain why wd2 and wd3 aren't being seen by the kernel *sometimes*. When they both are seen the WDCTL_RST failed messages are not in the dmesg and this is all there is instead: [ 2.158118] ahcisata1 port 0: device present, speed: 3.0Gb/s [ 2.158118] ahcisata1 port 5: device present, speed: 3.0Gb/s [ 2.158118] ahcisata1 port 4: device present, speed: 3.0Gb/s
Re: configuring raid using gpt, large drives
m...@goathill.org (MLH) writes: >I had jsut (apparently) got that working, where the bootloader was >comoing up from either of my wd2 or wd3 boot wedges and askign for >the raid0 but then this happened, which is preventing the kernel >from seeing either wd2 or wd3: >[ 2.752630] autoconfiguration error: ahcisata1 port 5: setting WDCTL_RST >failed for drive 15 >[ 2.752630] autoconfiguration error: ahcisata1 port 4: setting WDCTL_RST >failed for drive 15 >[ 3.252803] autoconfiguration error: ahcisata1 port 5: drive 15 reset >failed, disabling PMP >[ 3.252803] autoconfiguration error: ahcisata1 port 4: drive 15 reset >failed, disabling PMP How did this "happen" ? This has nothing to do with booting or RAID. The disabled PMP should have helped the drive to be used, but apparently that's didn't work. -- -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."
Re: configuring raid using gpt, large drives
Continuation of a long story... Emmanuel has expended an immense amount of time trying to help me solve this problem. I finally have accepted that while my motherboard purports to support EFI booting of large drives, the bios doesn't appear to support it in any way we can determine. Nor does it appear to support booting from a raid array that pretty clearly has been set up correctly. BAck with 7.x -current I had tried to use gpt with ffs booting to be able to use these two 4T drives in a raid array but back then there was some software problem with doing that under NetBSD. Emmanuel suggested I go back to using a boot wedge to bring up the bootloader and switching to the raid array. I had jsut (apparently) got that working, where the bootloader was comoing up from either of my wd2 or wd3 boot wedges and askign for the raid0 but then this happened, which is preventing the kernel from seeing either wd2 or wd3: [ 2.152423] ahcisata1 port 5: device present, speed: 3.0Gb/s [ 2.152423] ahcisata1 port 0: device present, speed: 3.0Gb/s [ 2.152423] ahcisata1 port 4: device present, speed: 3.0Gb/s [ 2.752630] autoconfiguration error: ahcisata1 port 5: setting WDCTL_RST failed for drive 15 [ 2.752630] autoconfiguration error: ahcisata1 port 4: setting WDCTL_RST failed for drive 15 [ 3.252803] autoconfiguration error: ahcisata1 port 5: drive 15 reset failed, disabling PMP [ 3.252803] autoconfiguration error: ahcisata1 port 4: drive 15 reset failed, disabling PMP [ 3.352837] ahcisata1 port 5: device present, speed: 3.0Gb/s [ 3.352837] ahcisata1 port 4: device present, speed: 3.0Gb/s wd0 and wd1 are old drives I really need to take offline. wd1 is getting errors. Full dmesg: [ 1.00] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, [ 1.00] 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, [ 1.00] 2018, 2019, 2020 The NetBSD Foundation, Inc. All rights reserved. [ 1.00] Copyright (c) 1982, 1986, 1989, 1991, 1993 [ 1.00] The Regents of the University of California. All rights reserved. [ 1.00] NetBSD 9.99.46 (HDMIAUDIO) #0: Thu Feb 13 13:00:32 EST 2020 [ 1.00] @xx:/opt/obj/amd64/opt/src/sys/arch/amd64/compile/HDMIAUDIO [ 1.00] total memory = 4079 MB [ 1.00] avail memory = 3933 MB [ 1.00] pool redzone disabled for 'buf4k' [ 1.00] pool redzone disabled for 'buf64k' [ 1.00] timecounter: Timecounters tick every 10.000 msec [ 1.00] Kernelized RAIDframe activated [ 1.00] running cgd selftest aes-xts-256 aes-xts-512 done [ 1.00] timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 [ 1.03] Gigabyte Technology Co., Ltd. H61M-S2-B3 ( ) [ 1.03] mainbus0 (root) [ 1.03] ACPI: RSDP 0x000F6EA0 14 (v00 GBT ) [ 1.03] ACPI: RSDT 0xDF7D3040 4C (v01 GBTGBTUACPI 42302E31 GBTU 01010101) [ 1.03] ACPI: FACP 0xDF7D3100 74 (v01 GBTGBTUACPI 42302E31 GBTU 01010101) [ 1.03] ACPI: DSDT 0xDF7D31C0 0049F2 (v01 GBTGBTUACPI 1000 MSFT 0400) [ 1.03] ACPI: FACS 0xDF7D 40 [ 1.03] ACPI: MSDM 0xDF7D7D00 55 (v03 GBTGBTUACPI 42302E31 GBTU 01010101) [ 1.03] ACPI: HPET 0xDF7D7DC0 38 (v01 GBTGBTUACPI 42302E31 GBTU 0098) [ 1.03] ACPI: MCFG 0xDF7D7E40 3C (v01 GBTGBTUACPI 42302E31 GBTU 01010101) [ 1.03] ACPI: ASPT 0xDF7D7F00 34 (v07 GBTPerfTune 312E3042 UTBG 01010101) [ 1.03] ACPI: SSPT 0xDF7D7F40 002270 (v01 GBTSsptHead 312E3042 UTBG 01010101) [ 1.03] ACPI: EUDS 0xDF7DA1B0 C0 (v01 GBT ) [ 1.03] ACPI: TAMG 0xDF7DA270 000382 (v01 GBTGBT B0 5455312E BG?? 45240101) [ 1.03] ACPI: APIC 0xDF7D7C00 BC (v01 GBTGBTUACPI 42302E31 GBTU 01010101) [ 1.03] ACPI: SSDT 0xDF7DA600 001EC8 (v01 INTEL PPM RCM 8001 INTL 20061109) [ 1.03] ACPI: 2 ACPI AML tables successfully acquired and loaded [ 1.03] ioapic0 at mainbus0 apid 2: pa 0xfec0, version 0x20, 24 pins [ 1.03] cpu0 at mainbus0 apid 0 [ 1.03] cpu0: Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz, id 0x206a7 [ 1.03] cpu0: node 0, package 0, core 0, smt 0 [ 1.03] cpu1 at mainbus0 apid 2 [ 1.03] cpu1: Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz, id 0x206a7 [ 1.03] cpu1: node 0, package 0, core 1, smt 0 [ 1.03] cpu2 at mainbus0 apid 1 [ 1.03] cpu2: Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz, id 0x206a7 [ 1.03] cpu2: node 0, package 0, core 0, smt 1 [ 1.03] cpu3 at mainbus0 apid 3 [ 1.03] cpu3: Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz, id 0x206a7 [ 1.03] cpu3: node 0, package 0, core 1, smt 1
Re: ZFS on root - almost there
Roy Marples writes: > So I thought I would have a go at setting up ZFS on root. > > Thanks to hannken@ it now boots :) > However, it panics at shutdown (or halt). Screen capture of the panic here: > http://www.netbsd.org/~roy/netbsd-zfs-panic.jpg > > Now, what I did during the initial setup was to adjust the mountpoint of > tank/ROOT/usr to /usr - ie relative to the chroot. > > The bootstrap phase is this in /etc/rc > > fsck -y / > zfs mount tank/ROOT > mount -t null /dev /tank/ROOT/dev > mount -t null / /tank/ROOT/altroot # this doesn't appear to work > sysctl -w init.root=/tank/ROOT > > This works fine, we enter the chroot > For the time being I've disabled fsck_root and adjusts zfs to load all mounts. > > We now get to the login with minimal errors and all appears to work. > You can see the mountlist inside the chroot at the top of the screen capture. > > If some kind person can fix this panic then I can copy across my live home > site > setup (web server, email, etc) and really test it out. > > Roy I have done the root-pivot thing before with cgd. I believe I noticed panics on shutdown there too. I also had lvm involved so I was never very sure what the problem was. This would have been in the late 6.x and early 7.x days. -- Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Re: KASLR
On Wed, Feb 12, 2020 at 09:55:36AM +, Patrick Welche wrote: > Just tried for the first time a kern-GENERIC_KASLR.tar.xz from yesterday's > source on a working GENERIC-9.99.17/amd64 box, with serial console. All > I see is > > >> NetBSD/x86 BIOS Boot, Revision 5.11 (Thu Nov 29 11:11:25 UTC 2018) (from > >> NetBSD 8.99.26) > >> Memory: 639/4189184 k > ... > command(s): rndseed /var/db/entropy-file;boot > default boot twice, skipping... > [860323- > > and then it reboots. > > kern-GENERIC.tar.xz from the same build.sh release run is fine. > > > Cheers, > > Patrick It cant use the regular bootloader, see instructions at https://blog.netbsd.org/tnf/entry/kernel_aslr_on_amd64
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: 2020.02.14.07.21.02 skrll src/sys/arch/aarch64/include/types.h,v 1.14 2020.02.14.07.23.24 skrll src/sys/arch/arm/arm32/genassym.cf,v 1.86 2020.02.14.09.35.40 riastradh src/sys/external/bsd/drm2/include/linux/delay.h,v 1.6 2020.02.14.09.35.52 riastradh src/sys/modules/drmkms/Makefile,v 1.13 2020.02.14.09.35.52 riastradh src/sys/modules/i915drmkms/Makefile,v 1.15 2020.02.14.09.38.51 riastradh src/sys/external/bsd/common/include/asm/div64.h,v 1.1 2020.02.14.09.38.51 riastradh src/sys/external/bsd/drm2/dist/drm/drm_dp_helper.c,v 1.11 2020.02.14.09.38.51 riastradh src/sys/external/bsd/drm2/include/asm/Attic/div64.h,v 1.2 2020.02.14.09.39.37 riastradh src/sys/external/bsd/drm2/dist/drm/i915/intel_bios.c,v 1.9 2020.02.14.09.39.37 riastradh src/sys/external/bsd/drm2/dist/drm/i915/intel_crt.c,v 1.8 2020.02.14.09.39.37 riastradh src/sys/external/bsd/drm2/dist/drm/i915/intel_display.c,v 1.31 2020.02.14.09.39.37 riastradh src/sys/external/bsd/drm2/dist/drm/i915/intel_fbdev.c,v 1.11 2020.02.14.09.39.37 riastradh src/sys/external/bsd/drm2/dist/drm/i915/intel_lvds.c,v 1.9 2020.02.14.09.39.37 riastradh src/sys/external/bsd/drm2/dist/drm/i915/intel_pm.c,v 1.23 2020.02.14.09.39.38 riastradh src/sys/external/bsd/drm2/dist/drm/i915/intel_sdvo.c,v 1.14 2020.02.14.09.39.38 riastradh src/sys/external/bsd/drm2/dist/drm/nouveau/nouveau_chan.c,v 1.6 2020.02.14.09.39.57 riastradh src/sys/external/bsd/drm2/dist/drm/i915/intel_fbdev.c,v 1.12 Log files can be found at: http://releng.NetBSD.org/b5reports/i386/commits-2020.02.html#2020.02.14.09.39.57
ZFS on root - almost there
So I thought I would have a go at setting up ZFS on root. Thanks to hannken@ it now boots :) However, it panics at shutdown (or halt). Screen capture of the panic here: http://www.netbsd.org/~roy/netbsd-zfs-panic.jpg Now, what I did during the initial setup was to adjust the mountpoint of tank/ROOT/usr to /usr - ie relative to the chroot. The bootstrap phase is this in /etc/rc fsck -y / zfs mount tank/ROOT mount -t null /dev /tank/ROOT/dev mount -t null / /tank/ROOT/altroot # this doesn't appear to work sysctl -w init.root=/tank/ROOT This works fine, we enter the chroot For the time being I've disabled fsck_root and adjusts zfs to load all mounts. We now get to the login with minimal errors and all appears to work. You can see the mountlist inside the chroot at the top of the screen capture. If some kind person can fix this panic then I can copy across my live home site setup (web server, email, etc) and really test it out. Roy
Re: Automated report: NetBSD-current/i386 build failure
> Date: Fri, 14 Feb 2020 09:19:13 + > From: Taylor R Campbell > > > Date: Fri, 14 Feb 2020 11:03:25 +0200 > > From: Andreas Gustafsson > > > > The NetBSD Test Fixture wrote: > > > nbmake[8]: stopped in > > > /tmp/bracket/build/2020.02.14.04.38.48-i386/src/sys/modules/drmkms > > > 1 error > > > > --- dependall-sys --- > > /tmp/bracket/build/2020.02.14.04.38.48-i386/src/sys/external/bsd/drm2/dist/drm/drm_bufs.c:958:40: > > error: pointer of type 'void *' used in arithmetic [-Werror=pointer-arith] > > buf->address = (void *)(dmah->vaddr + offset); > > ^ > > Sorry, I updated files.drmkms and made sure it built on i386, amd64, > and aarch64, but forgot there was a module with its own build > settings. Will fix shortly! Should be fixed now with src/sys/modules/drmkms/Makefile 1.13 src/sys/modules/i915drmkms/Makefile 1.15 src/sys/external/bsd/drm2/include/linux/delay.h 1.6
Re: Automated report: NetBSD-current/i386 build failure
> Date: Fri, 14 Feb 2020 11:03:25 +0200 > From: Andreas Gustafsson > > The NetBSD Test Fixture wrote: > > nbmake[8]: stopped in > > /tmp/bracket/build/2020.02.14.04.38.48-i386/src/sys/modules/drmkms > > 1 error > > --- dependall-sys --- > /tmp/bracket/build/2020.02.14.04.38.48-i386/src/sys/external/bsd/drm2/dist/drm/drm_bufs.c:958:40: > error: pointer of type 'void *' used in arithmetic [-Werror=pointer-arith] > buf->address = (void *)(dmah->vaddr + offset); > ^ Sorry, I updated files.drmkms and made sure it built on i386, amd64, and aarch64, but forgot there was a module with its own build settings. Will fix shortly!
Re: Automated report: NetBSD-current/i386 build failure
The NetBSD Test Fixture wrote: > nbmake[8]: stopped in > /tmp/bracket/build/2020.02.14.04.38.48-i386/src/sys/modules/drmkms > 1 error --- dependall-sys --- /tmp/bracket/build/2020.02.14.04.38.48-i386/src/sys/external/bsd/drm2/dist/drm/drm_bufs.c:958:40: error: pointer of type 'void *' used in arithmetic [-Werror=pointer-arith] buf->address = (void *)(dmah->vaddr + offset); ^ -- Andreas Gustafsson, g...@gson.org
