Re: Panic on yesterday's -current amd64

2023-04-24 Thread Julian Coleman
Hi, > panic: kernel diagnostic assertion "offset < map->dm_mapsize" failed: > file "/usr/src/sys/arch/x86/x86/bus_dma.c", line 826 bad offset 0x0 >= > 0x0 > cpu0: Begin traceback... > vpanic() at netbsd:vpanic+0x173 > kern_assert() at netbsd:kern_assert+0x4b > bus_dmamap_sync() at

Re: zero bytes in files written to NFS

2021-03-30 Thread Julian Coleman
Hi Thomas, > I was asked offlist: > > Yes, I see wcc errors like these: > > Mar 29 20:51:20 yt /netbsd: [ 208996.0919434] 192.168.0.18:/volume2/foo: > re-enabling wcc > Mar 29 20:51:20 yt /netbsd: [ 209116.2535171] 192.168.0.18:/volume2/foo: > inaccurate wcc data (ctime) detected, disabling

Re: Audio subsystem versus unplugging uaudio

2020-12-29 Thread Julian Coleman
Hello, > With a hint from skrll@, I looked at uaudio_detach(). We already have > code in uaudio_halt_out_dma() and uaudio_halt_in_dma() to stop any playback > or recording, so it looks like we can reuse these when detaching. With the > attached patch, I no longer see the panics when removing a

Re: Audio subsystem versus unplugging uaudio

2020-12-26 Thread Julian Coleman
Hello, > I ran into a problem with uaudio, but I'll have a look at uaudio_detach(). With a hint from skrll@, I looked at uaudio_detach(). We already have code in uaudio_halt_out_dma() and uaudio_halt_in_dma() to stop any playback or recording, so it looks like we can reuse these when detaching.

Re: Audio subsystem versus unplugging uaudio

2020-12-13 Thread Julian Coleman
Hello, > I have just fixed it in -current (I will pullup to -9 later). > Thank you for reporting. Thank you for the fast fix! I verified that this works for me. I ran into a problem with uaudio, but I'll have a look at uaudio_detach(). Regards, Julian

Re: How to fall back to PIO for IDE CD's?

2020-11-18 Thread Julian Coleman
Hi, > It seems to depend on the medium and readability. That's interesting. I've only tried with audio CD's and commercial DVD's. > I can read a DVD+R just fine, but a real data CD (not CDR) fails with: > and a commercial (movie) DVD > > fails similarily: > > aceride0:1:0: lost interrupt >

Re: How to fall back to PIO for IDE CD's?

2020-11-18 Thread Julian Coleman
Hi, > Can you elaborate on that part? I have > > cd0 at atapibus0 drive 0: cdrom removable > > in the SB2500 and something similar in the v210 but not sure I ever noticed > problems (likely because I barely use CDs or DVDs nowadays). > > How to reproduce? Maybe we can fix it better in a

How to fall back to PIO for IDE CD's?

2020-11-18 Thread Julian Coleman
Hi, Most (all) sparc64 have problems with DMA and CD/DVD drives connected to the internal controller (aceride). It's easy to work around this with flags in the kernel configuration. However the SPARCle has the hard drive and the CD both connected to aceride. Configuring PIO for all drives is

Re: Proposal to remove driver for the Cabletron EA41x SCSI Ethernet adapter

2020-06-26 Thread Julian Coleman
Hi all, > We have a driver for this device in sys/dev/scsipi/if_se.c. It was pretty > popular with the pc532 crowd back in the day because SCSI was the only > expansion bus the pc532 had. > > There are changes coming to the network stack and it's unlikely that (a) > anyone has such a device

Re: Jemalloc fallout on sandpoint

2019-04-09 Thread Julian Coleman
Hi Christos, > The problem is that on powerpc we use MAX_PAGE_SHIFT not the right page > shift for the machine. I will fix it to compute and use the MIN_PAGE_SHIFT > soon. This: Modified Files: src/external/bsd/jemalloc/include/jemalloc/internal: jemalloc_internal_defs.h

Jemalloc fallout on sandpoint

2019-04-08 Thread Julian Coleman
Hi all, Upgraded my QNAP TS-201 (sandpoint) to current, and all binaries crash with: : /usr/src/external/bsd/jemalloc/lib/../dist/src/pages.c:273: Failed assertion: "PAGE_ADDR2BASE(addr) == addr" [1] Abort trap (core dumped) sh Not sure how we can pass in an address that isn't the page

Re: Automated report: NetBSD-current/i386 build failure

2015-12-16 Thread Julian Coleman
Hi, > 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 2015.12.16.08.16.18. This was fixed with: