Re: new if_bge/mii panic

Hello, roy. (2013/06/13 20:19), Roy Marples wrote: On 13/06/2013 5:29, Masanobu SAITOH wrote: in6_createmkludge() does: mk = malloc(sizeof(*mk), M_IPMADDR, M_ZERO|M_WAITOK); in6_createmkludge() must not be called under interrupt context. Indeed. The attached patch should fix

Re: netbsd-6 is broken now

(2013/11/18 10:45), Hisashi T Fujinaka wrote: On Mon, 18 Nov 2013, Emmanuel Dreyfus wrote: Hisashi T Fujinaka ht...@twofifty.com wrote: A lot of cases in sys/dev/mii/bgephy.c need to have BGE_PHY_* changed to BGEPHYF_*. Fixed. Some hunks in the ticket have not merged. Thanks. Maybe,

Re: kernel build failure, very latest -current

Hi. (2014/01/10 3:39), B Harder wrote: # compile GENERIC/ahcisata_pci.o /usr/src/obj/tooldir.NetBSD-6.99.28-amd64/bin/x86_64--netbsd-gcc -mcmodel=kernel -mno-red-zone -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fno-zero-initialized-in-bss -O2 -fno-omit-frame-pointer -fstack-protector

Re: autobuild failed (sqlite3.pc)

Hi, Paul. (2014/02/20 13:04), Paul Goyette wrote: I think that dsl@ fixed this earlier today. Now the end of the page says: Currently building tag: HEAD started at Thu Feb 20 02:20:55 UTC 2014 4 passed 27 failed so far may be fixed. Thanks. On Thu, 20 Feb 2014, Masanobu SAITOH

Re: 82599EB 10-Gigabit not detected

Hello. (2014/04/09 2:36), 6b...@6bone.informatik.uni-leipzig.de wrote: Hello, On Sat, 22 Mar 2014, Matthias Scheler wrote: Please let us know whether that made the card work for you. only modifying the ixgbe_vendor_info_array is not enough. I attached a smal, patch. With it the card works

Re: src.7

On 2014/12/02 0:08, Patrick Welche wrote: Just noticed that we have a src.7, but according to src/share/man/man7/Makefile, it doesn't get intalled. Is that intentional? Parpaps it isn't. I committed to add it. Thanks! Cheers, Patrick -- ---

Re: netbsd-7, cpuctl error output says (null)

On 2014/12/16 12:39, Masanobu SAITOH wrote: On 2014/12/16 0:01, Fredrik Pettai wrote: (Recent) netbsd-7 version of cpuctl will returns (null) if you feed it with a non-existing parameter: -bash-4.3$ cpuctl foo cpuctl: unknown command ``(null)'' It used to say: -bash-4.3$ cpuctl foo cpuctl

Fwd: Re: kern/48960: ichlpcib maps I/O space from ACPI BAR which ichsmb wants

Hi, all. This change fixes a problem that ichlpcib can't map correctly for GPIO area. And, it will aslo fix some ACPI problem. Could you test if you have a problem with ACPI? Regards. Forwarded Message Return-Path: bounces-netbsd-bugs-owner-msaitoh=execsw@netbsd.org

Re: Fwd: Re: kern/48960: ichlpcib maps I/O space from ACPI BAR which ichsmb wants

On 2014/12/25 11:56, Masanobu SAITOH wrote: Hi, all. This change fixes a problem that ichlpcib can't map correctly for GPIO area. And, it will aslo fix some ACPI problem. Could you test if you have a problem with ACPI? Regards. The change was committed. Please report if you noticed

Re: current status of ixg(4)

On 2015/03/22 2:20, 6b...@6bone.informatik.uni-leipzig.de wrote: On Sat, 21 Mar 2015, SAITOH Masanobu wrote: New patch: http://www.netbsd.org/~msaitoh/ixg-20150321-0.dif Could you try with this patch again? Now the patch works, BTW, what card(or chip) does your machine have? X540,

current status of ixg(4)

Hello. Yesterday, I commited some changes to ixg(4) on -current. http://mail-index.netbsd.org/source-changes/2015/03/19/msg064110.html I'll wait for a few days to wait feedback of this change. And then I'll send pullup request to pullup-7@. And, I made a patch to support Intel

Re: current status of ixg(4)

New patch: http://www.netbsd.org/~msaitoh/ixg-20150321-0.dif This change have commited now. New patch: http://www.netbsd.org/~msaitoh/ixg-20150327-0.dif This change synchronizes our ixg(4) driver up to FreeBSD r38149: - Add TSO6 support. - The max size in dma tag is

Re: current status of ixg(4)

On 2015/03/27 16:03, Masanobu SAITOH wrote: New patch: http://www.netbsd.org/~msaitoh/ixg-20150321-0.dif This change have commited now. New patch: http://www.netbsd.org/~msaitoh/ixg-20150327-0.dif This change synchronizes our ixg(4) driver up to FreeBSD r38149: s/38149

Re: amd64 radeondrmkms near-invisble text

On 2015/02/21 0:12, John D. Baker wrote: I was recently gifted with a Dell PowerEdge 2850 (which might end up being a white elephant, judging by this thread: http://mail-index.netbsd.org/tech-kern/2015/02/11/msg018393.html but that's for later concern). I set up an NFS root and netboot

Re: current status of ixg(4)

Hi, Uwe. but I found a problem with vlan interfaces. You can create a vlan interface with: ifconfig vlan8 create ifconfig vlan8 vlan 8 vlanif ixg0 up The interface is generated. But there are no packages. ifconfig -v shows no inbound packets. tcpdump on ixg0 but indicates tagged packets for

Re: current status of ixg(4)

On 2015/04/02 18:13, Masanobu SAITOH wrote: On 2015/04/02 0:01, Thor Lancelot Simon wrote: On Tue, Mar 31, 2015 at 03:38:45PM +0200, 6b...@6bone.informatik.uni-leipzig.de wrote: On Fri, 27 Mar 2015, Masanobu SAITOH wrote: This change have commited now. New patch: http://www.netbsd.org

Re: current status of ixg(4)

On 2015/04/02 0:01, Thor Lancelot Simon wrote: On Tue, Mar 31, 2015 at 03:38:45PM +0200, 6b...@6bone.informatik.uni-leipzig.de wrote: On Fri, 27 Mar 2015, Masanobu SAITOH wrote: This change have commited now. New patch: http://www.netbsd.org/~msaitoh/ixg-20150327-0.dif I have

Re: current status of ixg(4)

On 2015/04/10 4:26, 6b...@6bone.informatik.uni-leipzig.de wrote: On Wed, 8 Apr 2015, SAITOH Masanobu wrote: Use new one: http://www.netbsd.org/~msaitoh/ixg-20150407-1.dif After a first test, it looks as if the interrupt throttling now works (better). Thanks. I committed the diff. I

Re: current status of ixg(4)

On 2015/04/14 17:22, Masanobu SAITOH wrote: On 2015/04/10 4:26, 6b...@6bone.informatik.uni-leipzig.de wrote: On Wed, 8 Apr 2015, SAITOH Masanobu wrote: Use new one: http://www.netbsd.org/~msaitoh/ixg-20150407-1.dif After a first test, it looks as if the interrupt throttling now works

Re: Currently: build failure

On 2015/05/13 9:11, Paul Goyette wrote: Change all of the FALSE -- false and TRUE--true :) Fixed. Thanks! On Tue, 12 May 2015, bch wrote: [...] --- dependall-usr.sbin --- /usr/src/usr.sbin/crash/../../sys/arch/amd64/amd64/db_disasm.c:216:19: error: 'FALSE' undeclared here (not in a

Re: libcrypto: Illegal instruction ``pshufb'' on non-sse3 CPU

Hi. On 2015/05/19 10:45, Timo Buhrmester wrote: As of late, when building (and installing) -head I end up with a libcrypto causing SIGILL, apparently due to using the ``pshufb'' instruction (which I believe is part of the SSE3 extension). My CPU is, according to /proc/cpuinfo: For x86,

Re: wm0: wm0: ROM image version 3.11 is older than 3.25

On 2015/06/28 0:33, Thomas Klausner wrote: Hi! I noted this message today: wm0: ROM image version 3.11 is older than 3.25 What does it want to tell me? Perhaps there is nothing to do by yourself :-) Thomas I210 and I211 have a bug that the PLL misconfigured very slowly. The NVM

Re: -current kernel on KVM with virtio disk fails to boot

On 2015/08/24 15:34, Ryota Ozaki wrote: On Mon, Aug 24, 2015 at 2:12 PM, Michael van Elst mlel...@serpens.de wrote: ozak...@netbsd.org (Ryota Ozaki) writes: Hi, I got the following panic on bootup. It seems recent IPL_VM = IPL_NONE change in dk_attach causes it. Yes. Unfortunately the

x86's /proc/cpuinfo (was Re: libcrypto: Illegal instruction ``pshufb'' on non-sse3 CPU)

On 2015/05/19 22:02, Masanobu SAITOH wrote: Hi. On 2015/05/19 10:45, Timo Buhrmester wrote: As of late, when building (and installing) -head I end up with a libcrypto causing SIGILL, apparently due to using the ``pshufb'' instruction (which I believe is part of the SSE3 extension). My CPU

Re: wm devices don't work under current amd64

Hi, Tom. On 2016/03/07 20:42, Tom Ivar Helbekkmo wrote: Masanobu SAITOH <msai...@execsw.org> writes: 0) Did you check /var/log/message if device timouts occured? No timeouts. Everything behaves as if there were no incoming traffic. 1) Is Intel AMT set to enable by BIOS? No

Re: wm devices don't work under current amd64

Hi. On 2016/03/07 21:12, Tobias Nygren wrote: On Mon, 7 Mar 2016 20:57:02 +0900 Masanobu SAITOH <msai...@execsw.org> wrote: One of the possibility is that the multicast filter table and broadcast bit in a register aren't set correctly on ICH9. I'm not sure if this is re

Re: wm devices don't work under current amd64

Hi. On 2016/03/07 19:35, Tom Ivar Helbekkmo wrote: I've recently set up a Dell E6400 laptop with NetBSD, and it's working great - over WiFi. The built-in wm ethernet interface doesn't work. It can send packets out, but can't receive anything. 0) Did you check /var/log/message if device

Re: wm devices don't work under current amd64

Hi, Tom. On 2016/03/07 21:34, Tom Ivar Helbekkmo wrote: Masanobu SAITOH <msai...@execsw.org> writes: Is the port connecting 100BaseT switch or gigabit switch. It's connected to a Cisco 2924 VLAN switch, and both the switch port and the wm0 device on the laptop are explicitly conf

nbctfconvert and /etc/malloc.conf

Hi. While compiling amd64's GENERIC kernel. I found a problem: > --- kern_sig_43.o --- > /disk/sources/NetBSD-current/src/obj/tooldir.NetBSD-7.99.26-amd64/bin/nbctfconvert > -g -L VERSION -g kern_sig_43.o > ERROR: kern_sig_43.c: die 20756: failed to get ref: Invalid attribute form >

Re: wm devices don't work under current amd64

Hi. Sorry for the long delay. On 2016/03/10 4:26, SAITOH Masanobu wrote: Hi, Tom. On 2016/03/10 4:12, Tom Ivar Helbekkmo wrote: SAITOH Masanobu writes: You mean your machine works with INTx but it doesn't work on MSI, right? That is correct. If so, could you show

Re: wm devices don't work under current amd64

On 2016/07/06 18:06, Tom Ivar Helbekkmo wrote: Masanobu SAITOH <msai...@execsw.org> writes: I got a Latitude E6400 via an auction. I tried -current and it worked with MSI. While checking your dmesg, I noticed that you didn't use ACPI. I tried without ACPI and I could reproduce the p

Re: wm WOL not working anymore

Hi, Frank. On 2016/10/24 14:56, Masanobu SAITOH wrote: Hello. On 2016/10/22 19:32, Frank Kardel wrote: Hi ! There has be quite some work going on for wm interfaces. When testing current kernels I found that some time after if_wm.c:1.347 the WOL functionality has stopped working on my ASRock

Re: WANTED: nvme(4) driver testing on MP systems on -current

On 2016/09/22 5:54, Jaromír Doleček wrote: Hello, NVMe driver in NetBSD-current was recently tweaked to fix several MP and locking issues, and the driver is now marked as MPSAFE by default. Most of this work was done on emulators since I lack the the hardware, so it's not clear if everything

Re: wm WOL not working anymore

Hello. On 2016/10/22 19:32, Frank Kardel wrote: Hi ! There has be quite some work going on for wm interfaces. When testing current kernels I found that some time after if_wm.c:1.347 the WOL functionality has stopped working on my ASRock 990FX Extreme 9 wm interfaces (PHYs are down after

Re: wm devices don't work under current amd64

Hello, Jarle. On 2016/11/27 0:45, Jarle Greipsland wrote: Masanobu SAITOH <msai...@execsw.org> writes: Hi. On 2016/03/07 21:12, Tobias Nygren wrote: On Mon, 7 Mar 2016 20:57:02 +0900 Masanobu SAITOH <msai...@execsw.org> wrote: One of the possibility is that the multicast

Re: wm devices don't work under current amd64

On 2016/11/28 17:16, Masanobu SAITOH wrote: Hello, Jarle. On 2016/11/27 0:45, Jarle Greipsland wrote: Masanobu SAITOH <msai...@execsw.org> writes: Hi. On 2016/03/07 21:12, Tobias Nygren wrote: On Mon, 7 Mar 2016 20:57:02 +0900 Masanobu SAITOH <msai...@execsw.org>

Re: wm devices don't work under current amd64

On 2017/01/14 2:03, Tom Ivar Helbekkmo wrote: Masanobu SAITOH <msai...@execsw.org> writes: Please test the latest -current. knakahara found a problem: That worked fine! No longer any need for the tcpdump hack. :) (I didn't get the latest -current; I just added those patches to 7

Re: wm devices don't work under current amd64

On 2017/01/14 6:43, Jarle Greipsland wrote: Masanobu SAITOH <msai...@execsw.org> writes: On 2016/11/28 17:16, Masanobu SAITOH wrote: Hello, Jarle. On 2016/11/27 0:45, Jarle Greipsland wrote: [ ... ] Was this problem ever fixed? Perhaps no. I've added a lot of changes into i

panic in vfs_wapbl.c

I updated my machine's kernel which was made from 1 hour ago's -current source. It paniced. It's reproducible. /dev/rwd0a: file system is clean; not checking panic: kernel diagnostic assertion "!(bp->b_oflags & BO_DELWRI)" failed: file "../../../../kern/vfs_wapbl.c", line 1142 fatal

Re: panic: kernel diagnostic assertion "next != _PSLIST_POISON"

and possibly recent mount update (-u) changes, Other ideas ? Frank On 03/14/17 08:56, Masanobu SAITOH wrote: Hi. On 2017/03/14 16:36, Frank Kardel wrote: Has anyone seen this panic recently? Seen in -current-20170311, i386, Soekris 6501. panic: kernel diagnostic assertion "next !=

Re: panic: kernel diagnostic assertion "next != _PSLIST_POISON"

On 2017/03/15 14:11, Masanobu SAITOH wrote: On 2017/03/15 0:30, Jaromír Doleček wrote: Yes, this panic is already fixed in -current: panic: kernel diagnostic assertion "!(bp->b_oflags & BO_DELWRI)" failed: file "../../../../kern/vfs_wapbl.c", line 1142 Jaromir I

Re: panic: kernel diagnostic assertion "next != _PSLIST_POISON"

Hi. On 2017/03/14 16:36, Frank Kardel wrote: Has anyone seen this panic recently? Seen in -current-20170311, i386, Soekris 6501. panic: kernel diagnostic assertion "next != _PSLIST_POISON" failed: file "/fs/raid2a/src/NetBSD/cur/src/sys/sys/pslist.h", line 270 cpu0: Begin traceback...

Re: panic: kernel diagnostic assertion "next != _PSLIST_POISON"

On 2017/03/14 17:15, Ryota Ozaki wrote: Hi, On Tue, Mar 14, 2017 at 4:36 PM, Frank Kardel wrote: Has anyone seen this panic recently? Seen in -current-20170311, i386, Soekris 6501. panic: kernel diagnostic assertion "next != _PSLIST_POISON" failed: file

Re: lm0 at isa reboot

Hi, Patrick On 2017/07/27 18:28, Patrick Welche wrote: On Fri, Jul 21, 2017 at 10:59:51PM +0100, Patrick Welche wrote: On Fri, Jul 21, 2017 at 08:17:44AM +0100, Patrick Welche wrote: On Fri, Jul 21, 2017 at 07:53:09AM +0100, Patrick Welche wrote: On Thu, Jul 20, 2017 at 09:06:16PM +,

UEFI status? (was Re: GPT/UEFI booting)

Hi, all. A few days ago, I successfully booted from UP board. http://www.up-board.org/up/comparison-up-versus-edisongalileo-joule/ UP board's UEFI doesn't support legacy boot. Currently, our sysinst doesn't support creating UEFI bootable disk, so I tried creating disk with reading

Re: -current boot failure @ wm(4)

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

Re: -current boot failure @ wm(4)

On 2017/07/14 13:34, Masanobu SAITOH wrote: 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

Re: -current boot failure @ wm(4)

On 2017/07/20 0:33, Lars Reichardt wrote: Masanobu SAITOH <msai...@execsw.org> hat am 18. Juli 2017 um 12:04 geschrieben: On 2017/07/14 13:34, Masanobu SAITOH wrote: Hi, Brad. On 2017/07/14 3:12, bch wrote: Hello NetBSD. I think this maybe related to msaitoh@ work in ./sys/dev/p

Re: bad counter for ixg* interfaces

Hi, Uwe. On 2017/04/28 21:11, 6b...@6bone.informatik.uni-leipzig.de wrote: Hello, ifconfig -v ixg0 shows: ixg0: flags=8843 mtu 1500 capabilities=fff80

Re: Possible regression in wm(4)?

Hi, all On 2017/11/22 0:21, Bert Kiers wrote: Hi, A different computer with the same type motherboard has the same problem. A quad I350 (also wm(4)) works fine (with GENERIC netbsd-8 kernel). Still wondering what queue drops are. Grtnx, Could you test the following diff?

Re: netbsd 8 (beta) failing to load ixg device

Hi, all. On 2017/11/14 7:01, Jaromír Doleček wrote: I had a very brief look on the crashing function ixgbe_update_stats_count(). The only division there is in the one using adapter->num_queue. Looking at ixgbe_configure_interrups(), seems that one can happily set it to 0 if number of MSI

Re: netbsd-8 crash in ixg driver during booting

Hi, Uwe. On 2017/11/15 15:41, 6b...@6bone.informatik.uni-leipzig.de wrote: Does your machine boot with the latest -current? I have tested the current sources from tonight. https://suse.uni-leipzig.de/crash/crash-current1.jpg https://suse.uni-leipzig.de/crash/crash-current2.jpg Regards Uwe

Re: Possible regression in wm(4)?

On 2017/12/06 22:26, Bert Kiers wrote: On Fri, Dec 01, 2017 at 04:40:37PM +0900, Masanobu SAITOH wrote: Hi, all On 2017/11/22 0:21, Bert Kiers wrote: Hi, A different computer with the same type motherboard has the same problem. A quad I350 (also wm(4)) works fine (with GENERIC netbsd-8

Re: adding devices to puc(4)

Hi. On 2018/05/07 16:38, John Nemeth wrote: I'm trying to add an Oxford Semiconductor 4-port serial card to puc(4). Using the datasheet, I've gotten to the point where all four serial ports are probed and attached. However, I don't seem to be able to communicate through the ports. And,

Re: ixg tester needed (was Re: Problems with netbsd-8 RC1 and ixg drivers (?))

Hi, all. New patch: --- Don't call ixgbe_rearm_queues() in ixgbe_local_timer1(). ixgbe_enable_queue() and ixgbe_disable_queue() try to enable/disable queue interrupt safely. It has the internal counter. When a queue's MSI-X is received, ixgbe_msix_que() is

Re: ixg tester needed (was Re: Problems with netbsd-8 RC1 and ixg drivers (?))

machines. Today, I could set up a system that this RX stall problem occurs quickly (in a few minutes). I don't know if I can fix this problem soon. Thanks. Regards Uwe On Mon, 28 May 2018, Masanobu SAITOH wrote: Date: Mon, 28 May 2018 17:10:02 +0900 From: Masanobu SAITOH To: Martin

Re: ixg tester needed (was Re: Problems with netbsd-8 RC1 and ixg drivers (?))

. Thanks. I've committed the latest patch now! Thank you for your efforts Regards Uwe On Fri, 1 Jun 2018, Masanobu SAITOH wrote: Date: Fri, 1 Jun 2018 12:47:32 +0900 From: Masanobu SAITOH To: 6b...@6bone.informatik.uni-leipzig.de Cc: msai...@execsw.org, Martin Husemann ,     current-users

Re: ixg tester needed (was Re: Problems with netbsd-8 RC1 and ixg drivers (?))

 The same diff is at: http://www.netbsd.org/~msaitoh/ixgbe-norearm-20180530-0.dif Updated patch (Fix compile error and ixv patch): -- Don't call ixgbe_rearm_queues() in ixgbe_local_timer1(). ixgbe_enable_queue() and ixgbe_disable_queue() try

ixg tester needed (was Re: Problems with netbsd-8 RC1 and ixg drivers (?))

On 2018/05/28 16:51, Martin Husemann wrote: On Mon, May 28, 2018 at 09:46:21AM +0200, 6b...@6bone.informatik.uni-leipzig.de wrote: Hello, At the weekend I tried to update to a current version of netbsd-8 rc1. After the restart, the kernel will work for a few hours. After that, no packets

Re: kernels with "pseudo-device pfsync" fail to build

On 2018/06/27 11:58, John D. Baker wrote: After the recent bpf_tap/bpf_mtap change, kernels which include: pseudo-device pfsync fail to build: [...] --- if_pfsync.o --- /x/current/src/sys/dist/pf/net/if_pfsync.c: In function 'pfsync_tdb_sendout':

Re: dmesg | grep -c "not configured" = 240...

On 2018/02/24 18:55, Patrick Welche wrote: On Mon, Feb 19, 2018 at 03:17:48PM +, Stephen Borrill wrote: So I've just got a Lenovo ThinkSystem SR630 and: # dmesg | grep -c "not configured" 240 http://www.netbsd.org/~sborrill/sr630.dmesg.txt Main issues are missing Ethernet (Intel X722)

if_addrflags6: Can't assign requested address

Hi. While testing netbsd-7, I've noticed dhcpcd put the following message: Configuring network interfaces: wm0wm0: if_addrflags6: Can't assign requested address wm0: if_addrflags6: Can't assign requested address wm0: if_addrflags6: Can't assign requested address wm0: if_addrflags6: Can't

Re: if_addrflags6: Can't assign requested address

On 2018/08/12 0:11, Roy Marples wrote: Hi On 08/08/2018 03:13, Masanobu SAITOH wrote:   Hi.   While testing netbsd-7, I've noticed dhcpcd put the following message: Configuring network interfaces: wm0wm0: if_addrflags6: Can't assign requested address wm0: if_addrflags6: Can't assign

Re: CTL_*_NAMES macros

On 2018/08/10 17:22, Masanobu SAITOH wrote:  Hi.  While debugging some counters which can be taken from sysctl, I've noticed that some macros are not used from anywhere. % egrep -r 'CTL_.*_NAMES' . ./sys/arch/m68k/include/sysctl.h:#ifndef CTL_MACHDEP_NAMES ./sys/arch/m68k/include/sysctl.h

CTL_*_NAMES macros

/04/msg138997.html http://mail-index.netbsd.org/source-changes/2003/12/04/msg138998.html http://mail-index.netbsd.org/source-changes/2003/12/04/msg138999.html -- - Masanobu SAITOH(masan...@iij.ad.jp msai...@netbsd.org)

error of makerumpdefs.sh

Hi. While cleaning some header files, I've noticed that sys/rump/include/rump/makerumpdefs.sh complained some sed lines: % sh -f makerumpdefs.sh Generating rumpdefs.h sed: 1: "/#define[ ]*_FCN/{:t;N ...": unexpected EOF (pending }'s) sed: 1: "/#define[ ]*_IO.*\\$/{ ...":

Re: CTL_*_NAMES macros

rjs@ wrote: Masanobu SAITOH wrote: % egrep -r 'CTL_.*_NAMES' . ./sys/arch/m68k/include/sysctl.h:#ifndef CTL_MACHDEP_NAMES ./sys/arch/m68k/include/sysctl.h:#endif /* CTL_MACHDEP_NAMES */ These are not examples of sysctl counter names, they are just the multiple inclusion prevention symbols

SIOC[GZ]IFDATA fix

Hi. I noticed that -current's SIOC[GZ]IFDATA doesn't work correctly. It's OK on netbsd-8. static int doifioctl(struct socket *so, u_long cmd, void *data, struct lwp *l) { struct ifnet *ifp; struct ifreq *ifr; int error = 0; #if defined(COMPAT_OSOCK) ||

Panic in ahci_detach

Hi. One of my machine panics in ahci_detach while shutdown. dmesg related to ahci: ci0 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 8086 product 1980 (rev. 0x10) pchb1 at pci0 dev 4 function

Re: Panic in ahci_detach

On 2018/11/03 6:28, Jaromír Doleček wrote: Le jeu. 1 nov. 2018 à 06:38, Masanobu SAITOH a écrit : The meaning of atac_nchannels changed or numbering of channel changed? ahci_detach() counted improperly. Can you confirm rev. 1.66 of dev/ic/ahcisata_core.c fixes the problem? Jaromir I've

Re: Panic with recent -current with interrupt setup

On 2018/10/03 5:47, Brad Spencer wrote: m...@netbsd.org writes: On Tue, Oct 02, 2018 at 06:55:48AM -0400, Brad Spencer wrote: Just wondering if anyone else has seen this, but I am getting panics on boot during probe with sources after 2018-09-23 [at some point, at least 2018-09-29 and

tester need: MII PHY register read/write API change

Hi. I'll commit the following diff to -current in this weekend: http://www.netbsd.org/~msaitoh/miiphy-20190117-0.dif This diff changes all of Ethernet driver which use mii(4) and all mii drivers. This change is not complicated, but more than a hundred files are modified. It might

Re: tester need: MII PHY register read/write API change

EPIA board and partially vte (dmesg only, since media status is incorrect now and network is not working for it (PR/53494)). On Thu, Jan 17, 2019 at 7:27 AM Masanobu SAITOH wrote: Hi. I'll commit the following diff to -current in this weekend: http://www.netbsd.org/~msaitoh

Re: tester need: MII PHY register read/write API change

On 2019/01/17 14:26, Masanobu SAITOH wrote:  Hi.  I'll commit the following diff to -current in this weekend: http://www.netbsd.org/~msaitoh/miiphy-20190117-0.dif This diff changes all of Ethernet driver which use mii(4) and all mii drivers. This change is not complicated, but more

Re: tester need: MII PHY register read/write API change

Hi, all. This change was committed yesterday. Please report if you got a new problem related to PHY access after the change. Thanks. -- --- SAITOH Masanobu (msai...@execsw.org msai...@netbsd.org)

Re: Panic on a -current from 13/12/2018

tried to get a panic with the .gdb kernel, but it never happened. Obviously it is not a problem for me or anyone running NetBSD as a VirtualBox guest, as using vioif / virtio is almost as twice as fast, but I reported the panic thinking it may be relevant in other use cases. Thank you for y

Re: dependency of magic.h

On 2018/12/11 21:40, Christos Zoulas wrote: In article <944c79fd-4414-1936-67f4-03ec228bd...@execsw.org>, Masanobu SAITOH wrote: Hi. While doing "./build.sh -j16 distribution", I got "unterminated ifdef" error in magic.h(src/external/bsd/file/lib). When I

dependency of magic.h

Hi. While doing "./build.sh -j16 distribution", I got "unterminated ifdef" error in magic.h(src/external/bsd/file/lib). When I got this compile error, I checked the file and the #ifdef...#endif was consistent. It seems the compiler saw unfinished magic.h. Have you ever seen this error before?

Re: Panic on a -current from 13/12/2018

On 2018/12/17 1:09, Chavdar Ivanov wrote: I have no idea. As I said, it is running under VirtualBox on a Windows 10 host; I put the host in hibernation whilst the NetBSD guest is running. I tested today's -current on VirtualBox 5.2.22 on Windows 7 64bit (on Core i7-2600). I tried

Re: ThinkPad - suspend-to-RAM intel-x86 issues and tests

On 2018/11/28 22:12, SAITOH Masanobu wrote: On 2018/11/28 14:18, Masanobu SAITOH wrote: Hi, David. On 2018/11/28 6:09, David Brownlee wrote: On Tue, 27 Nov 2018 at 18:10, David Brownlee wrote: On Tue, 27 Nov 2018 at 08:27, Masanobu SAITOH wrote:    Hi, David. On 2018/11/26 6:11, David

Re: ThinkPad - suspend-to-RAM intel-x86 issues and tests

On 2018/12/06 0:22, David Brownlee wrote: On Sat, 1 Dec 2018 at 01:27, SAITOH Masanobu wrote: Committed. Hi - is this worth pulling up into netbsd-8? Of course yes! I ran a quick test and my T420s suspends/resumes fine with a netbsd-8 kernel and no X11 running. x11 looks to have

Re: ThinkPad - suspend-to-RAM intel-x86 issues and tests

Hi, David. On 2018/11/28 6:09, David Brownlee wrote: On Tue, 27 Nov 2018 at 18:10, David Brownlee wrote: On Tue, 27 Nov 2018 at 08:27, Masanobu SAITOH wrote: Hi, David. On 2018/11/26 6:11, David Brownlee wrote: I've bisected the changes against the github src copy, and it looks like

Re: ThinkPad - suspend-to-RAM intel-x86 issues and tests

Hi, David. On 2018/11/26 6:11, David Brownlee wrote: I've bisected the changes against the github src copy, and it looks like the suspend/resume issue is related to the following commit: commit 0fe469276f49bf0dc003300e0b8a35a80b7b246d (HEAD) Author: jdolecek Date:   Mon Oct 22 20:57:07 2018

Re: ThinkPad - suspend-to-RAM intel-x86 issues and tests

On 2018/11/27 17:27, Masanobu SAITOH wrote:  Hi, David. On 2018/11/26 6:11, David Brownlee wrote: I've bisected the changes against the github src copy, and it looks like the suspend/resume issue is related to the following commit: commit 0fe469276f49bf0dc003300e0b8a35a80b7b246d (HEAD

Re: Panic on a -current from 13/12/2018

On 2018/12/18 20:13, Masanobu SAITOH wrote: Hi! On 2018/12/17 19:38, Chavdar Ivanov wrote: I went through a series of tests. It is indeed that point the panic takes place, the two parts of the screendump are in http://ci4ic4.tx0.org/nb-panic-wm-03.png and http://ci4ic4.tx0.org/nb-panic-wm-04

Re: tester need: MII PHY register read/write API change

On 2019/01/24 23:47, Riccardo Mottola wrote: Hello Masanobu, I updated and recompiled kernel, [ 1.049407] re0 at pci5 dev 0 function 0: RealTek 8100E/8101E/8102E/8102EL PCIe 10/100BaseTX (rev. 0x02) [ 1.049407] re0: interrupting at msix1 vec 0 [ 1.049407] re0: Ethernet address

Re: building kernel w/ options MIIVERBOSE fails

On 2019/03/25 18:25, K. Schreiner wrote: Hi, with current source cvs'upped an hour or so ago fails with: ... compile vNBx64/mii_verbose.o In file included from /u/NetBSD/src/sys/dev/mii/mii_verbose.c:62:0: /u/NetBSD/src/sys/dev/mii/miidevs_data.h:39:21: error: array type has incomplete

Re: README: libstdc++.so bumped

On 2019/03/20 14:41, matthew green wrote: hi folks. users of -current may notice issues with libstdc++.so major being increased. i've described the issues why this was done in the commit: http://mail-index.netbsd.org/source-changes/2019/03/20/msg104433.html this may break update builds

Re: README: libstdc++.so bumped

On 2019/03/22 17:45, matthew green wrote: Masanobu SAITOH writes: On 2019/03/20 14:41, matthew green wrote: hi folks. users of -current may notice issues with libstdc++.so major being increased. i've described the issues why this was done in the commit: http://mail-index.netbsd.org

Re: varshm check in postinstall

On 2019/01/31 18:49, Martin Husemann wrote: On Thu, Jan 31, 2019 at 05:23:45PM +0900, Masanobu SAITOH wrote: - if ${GREP} -w "/var/shm" "${DEST_DIR}/etc/fstab" >/dev/null 2>&1; + if ${GREP} -E "^var_shm_symlink" &q

varshm check in postinstall

Hi. If var_shm_symlink="/tmp/.shm" is in /etc/rc.conf and no /var/shm mount in /etc/fstab, postinstall complains: varshm check: No /var/shm mount found in /etc/fstab So, I propose the following change: Index: postinstall

i386/conf/ALL link error

`trace_cmp': /disk2/sources/NetBSD-current/src/sys/arch/i386/compile/ALL/../../../../kern/subr_kcov.c:430: undefined reference to `__atomic_store_8' *** [netbsd] Error code 1 -- - Masanobu SAITOH(masan...@iij.ad.jp

Re: i386/conf/ALL link error

On 2019/04/11 18:59, Kamil Rytarowski wrote: > On 11.04.2019 07:32, Masanobu SAITOH wrote: >> Hi. >> >> i386/conf/ALL kernel can't link. See below. >> > > This used to work. > > It means that __HAVE_ATOMIC64_OPS is defined but 64-bit atomics are >

no options COMPAT_43

Hi. I tried to make a kernel without COMPAT_43 from conf/GENERIC. I added "no options COMPAT_43" at the end of conf/GENERIC or conf/GENERIC.local, but compile/GENERIC/opt_compat_43.h had: #define COMPAT_43 1 Is this behavior intended? When I added "no options COMPAT_43" twice,

Re: Does IPv6 on athn(4) work?

On 2019/05/26 14:33, Thomas Mueller wrote: > from: Masanobu SAITOH: > >> While modifying Ethernet multicast's code, I noticed that >> athn.c doesn't modify the multicast filter. Does IPv6 on >> athn(4) work? > > --- >> Index: sys/dev/ic/athn.c

Re: 8.99.41 panic in nvm_poll

On 2019/06/10 17:17, Thomas Klausner wrote: > I tried some more stuff. > > Enabling the NVME_QUIRK_DELAY_B4_CHK_RDY quirk didn't help, it paniced > during boot. However, forcing nvme_pci_force_intx to 1 makes it boot > successfully! Please show the following information: - "FULL" dmesg

Does IPv6 on athn(4) work?

Hi. While modifying Ethernet multicast's code, I noticed that athn.c doesn't modify the multicast filter. Does IPv6 on athn(4) work? --- Index: sys/dev/ic/athn.c === RCS file: /cvsroot/src/sys/dev/ic/athn.c,v

Re: no options COMPAT_43

T_LINUX32 no options COMPAT_43 Thanks! > >> On Mon, 15 Apr 2019, Masanobu SAITOH wrote: >> >>> Hi. >>> >>> I tried to make a kernel without COMPAT_43 from conf/GENERIC. >>> I added "no options COMPAT_43" at th

Re: wm0 panic

Hi, all. On 2020/06/29 12:53, Kengo NAKAHARA wrote: > Hi, > > On 2020/06/28 0:24, Patrick Welche wrote: >> Trying a today's -current/amd64 with DIAGNOSTIC/DEBUG/LOCKDEBUG, I can >> boot multiuser without a network. If I log in as root, as soon as I hit >> enter: >> >> # ifconfig wm0 inet

Re: Crash on various Supermicro motherboards

On 2022/04/08 15:29, 6b...@6bone.informatik.uni-leipzig.de wrote: > Here is the CPU type: > > https://speicherwolke.uni-leipzig.de/index.php/s/SM6LQqKPqKYeCqM > > > Regards > Uwe > > On Thu, 7 Apr 2022, Christos Zoulas wrote: > >> Date: Thu, 7 Apr 2022 20:36:26 - (UTC) >> From: Christos

  1   2   >