Re: Kernel panic: gpioctl list + odroid-c1

> On May 10, 2022, at 8:46 PM, Brook Milligan wrote: > > One more piece of information. > > src/sys/arch/arm/amlogic/meson8b_pinctrl.c includes the following code: > > static const struct meson_pinctrl_gpio meson8b_cbus_gpios[] = { > > … < deleted sections > … > > /* GPIODV */

Re: Kernel panic: gpioctl list + odroid-c1

> On May 10, 2022, at 8:06 PM, Brook Milligan wrote: > > I have encountered a totally repeatable kernel panic by running "gpioctl > list” on an odroid-c1 board. > > # name -a > NetBSD armv7 9.99.96 NetBSD 9.99.96 (GENERIC) #0: Mon May 2 10:50:02 UTC > 2022 mk

Kernel panic: gpioctl list + odroid-c1

I have encountered a totally repeatable kernel panic by running "gpioctl list” on an odroid-c1 board. # name -a NetBSD armv7 9.99.96 NetBSD 9.99.96 (GENERIC) #0: Mon May 2 10:50:02 UTC 2022 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/evbarm/compile/GENERIC evbarm To investigate, I

Re: kernel panic in NetBSD-9.1-amd64-install.img (exiting unheld spin mutex)

r...@reedmedia.net ("Jeremy C. Reed") writes: >panic: lock error: Mutex error: mutex_vector_exit,742: exiting unheld >spin mutex: lock 0x8699588015c0 cpu 0 lwp 0xff... (my photo was >cropped) Index: athn.c === RCS file:

kernel panic in NetBSD-9.1-amd64-install.img (exiting unheld spin mutex)

uot; state but never connected to it. I ran multiple times: ifconfig athn0 inet 172.16.1.1 media autoselect mediaopt hostap chan 5 nwkey (in between using dhcpd and hostap and tcpdump) I had dhcpd and tcpdump running in background the final time I got a kernel panic Mutex error: mutex_vecto

kernel panic in genfs_deadunlock

hi folks, while testing a very recent kernel, and waiting for it to reboot, I got this: Crash version 8.99.37, image version 8.99.37. System panicked: lock error: Reader / writer lock: rw_vector_exit,454: assertion failed: RW_COUNT(rw) != 0: lock 0xed5bd50116b0 cpu 3 lwp 0xed5f70a20ae0

Re: Recent NetBSD/amd64 7.99.54 kernel panic

Hi, Sorry. This is as same as PR kern/51767. Thank you. From: Ryo ONODERA , Date: Wed, 04 Jan 2017 02:40:14 +0900 (JST) > Hi, > > Recent NetBSD/amd64 kernel panics with the following message > (manually transcripted). > Could anyone investigate this? > Thank you. > >

Re: Recent NetBSD/amd64 7.99.54 kernel panic

On 03.01.2017 18:40, Ryo ONODERA wrote: > Hi, > > Recent NetBSD/amd64 kernel panics with the following message > (manually transcripted). > Could anyone investigate this? > Thank you. > > stack overflow detected: terminated > fatal breakpoint trap in supervisor mode > trap type 1 code 0 rip

Recent NetBSD/amd64 7.99.54 kernel panic

Hi, Recent NetBSD/amd64 kernel panics with the following message (manually transcripted). Could anyone investigate this? Thank you. stack overflow detected: terminated fatal breakpoint trap in supervisor mode trap type 1 code 0 rip 80115455 cs 8 rflag 246 cr2 79b90fe688f0 ilevel 4 rsp

Re: kernel panic

On Sun, Jun 19, 2016 at 9:23 PM, Michael van Elst wrote: > brad.har...@gmail.com (bch) writes: > >>kernel (adjusted from GENNERIC to allow dtrace support) from latest src >>panics: > >>(transcription): > >>reboot after panic: panic: kernel diagnostic assertion "M_GETCTX(m,

Re: kernel panic

On Jun 15, 2016 9:29 PM, "Kengo NAKAHARA" wrote: > > Hi, > > On 2016/06/16 8:15, bch wrote: > > I am now at 1.414, and it seems stable. > > Thank you for your checking and reporting. My pleasure. Question, were my wm(4) and iwm(4) faults related (maybe some luck

Re: kernel panic

brad.har...@gmail.com (bch) writes: >kernel (adjusted from GENNERIC to allow dtrace support) from latest src panics: >(transcription): >reboot after panic: panic: kernel diagnostic assertion "M_GETCTX(m, >struct ieee80211_node *) == NULL)" failed: file >"/usr/src/sys/80211/ieee80211_output.c",

Re: kernel panic

On Thu, Jun 16, 2016 at 3:04 PM, Ryota Ozaki wrote: > On Thu, Jun 16, 2016 at 1:56 PM, bch wrote: >> >> On Jun 15, 2016 9:29 PM, "Kengo NAKAHARA" wrote: >>> >>> Hi, >>> >>> On 2016/06/16 8:15, bch wrote: >>> > I am now at 1.414,

Re: kernel panic

On Thu, Jun 16, 2016 at 1:56 PM, bch wrote: > > On Jun 15, 2016 9:29 PM, "Kengo NAKAHARA" wrote: >> >> Hi, >> >> On 2016/06/16 8:15, bch wrote: >> > I am now at 1.414, and it seems stable. >> >> Thank you for your checking and reporting. > > My

Re: kernel panic

I am now at 1.414, and it seems stable. On Jun 15, 2016 4:04 PM, "Kengo NAKAHARA" wrote: > Hi, > > On 2016/06/16 1:44, bch wrote: > > On 6/12/16, bch wrote: > >> On 6/11/16, bch wrote: > snip > > And now, on wm(4): > >

Re: kernel panic

Hi, On 2016/06/16 1:44, bch wrote: > On 6/12/16, bch wrote: >> On 6/11/16, bch wrote: snip > And now, on wm(4): > -rwxr-xr-x 1 root wheel 18218304 Jun 14 10:20 /netbsd > > strathcona# crash -M ./netbsd.8.core /netbsd > Crash version 7.99.30,

Re: kernel panic

On 6/12/16, bch wrote: > On 6/11/16, bch wrote: > previously reported bt on core from iwm(4) crash... > strathcona# crash -M ./netbsd.6.core > Crash version 7.99.30, image version /amd64/compile/G. > WARNING: versions differ, you may not be able to

Re: kernel panic

Hi, On Sat, Jun 11, 2016 at 3:58 AM, bch wrote: > kernel (adjusted from GENNERIC to allow dtrace support) from latest src > panics: > > (transcription): > > reboot after panic: panic: kernel diagnostic assertion "M_GETCTX(m, > struct ieee80211_node *) == NULL)" failed:

kernel panic

kernel (adjusted from GENNERIC to allow dtrace support) from latest src panics: (transcription): reboot after panic: panic: kernel diagnostic assertion "M_GETCTX(m, struct ieee80211_node *) == NULL)" failed: file "/usr/src/sys/80211/ieee80211_output.c", line 1347

Re: amd64-7.99.29 - Another kernel panic - ffs?

On 29/05/2016 17:43, Robert Swindells wrote: > One thing that could help would be if you could make an image of the > CF card after the panic has happened. > > The filesystem that you were creating is probably a fair bit smaller > than the ones where other people had the same problem. I baked

Re: amd64-7.99.29 - Another kernel panic - ffs?

Sevan Janiyan wrote: >On 29/05/2016 11:34, Paul Goyette wrote: >> Hmmm. Sevan opened PR port-hpcarm/50840 but perhaps we should >> recategorize the PR? > >Done. I'm still running a prebuilt image which Jun published back in >February but happy to do some test if that's

Re: amd64-7.99.29 - Another kernel panic - ffs?

On 29/05/2016 11:34, Paul Goyette wrote: > Hmmm. Sevan opened PR port-hpcarm/50840 but perhaps we should > recategorize the PR? Done. I'm still running a prebuilt image which Jun published back in February but happy to do some test if that's required. Sevan

Re: amd64-7.99.29 - Another kernel panic - ffs?

On Sun, 29 May 2016, Robert Swindells wrote: Paul Goyette wrote: Well, today I just had another crash, this time in ffs_newvnode(). The traceback (manually transcribed) is: [snip] Was the panic message "ffs_init_vnode: dup alloc" ? I missed copying down the panic

Re: NetBSD-current/i386 install kernel panic (sysv_ipc related)

(cc-ing current-users as a heads-up) Yes, I got another report of this as well. I am looking into it and will fix as quickly as possible. On Fri, 4 Dec 2015, Andreas Gustafsson wrote: Hi Paul, NetBSD-current/i386 panics during the install since yesterday. Since the panic message mentions

Re: NetBSD-current/i386 install kernel panic (sysv_ipc related)

This should be fixed now, although I am still testing a few more combinations. On Sat, 5 Dec 2015, Paul Goyette wrote: (cc-ing current-users as a heads-up) Yes, I got another report of this as well. I am looking into it and will fix as quickly as possible. On Fri, 4 Dec 2015, Andreas

Re: Kernel panic from network traffic

Hi, It's probably due to my recent change to refcnt. I'm investigating that defect. Thanks, ozaki-r On Fri, Jul 24, 2015 at 2:41 PM, Hisashi T Fujinaka ht...@twofifty.com wrote: Being a moron, I plugged ports of my switch together. The big surprise is two ports away is my -current box and

Re: Kernel panic from network traffic

Hi, I just fixed one bug related to refcnt. The fix may shut up the panic. Could you try again with a latest kernel? Thanks, ozaki-r On Fri, Jul 24, 2015 at 3:38 PM, Ryota Ozaki ozak...@netbsd.org wrote: On Fri, Jul 24, 2015 at 3:12 PM, Ryota Ozaki ozak...@netbsd.org wrote: Hi, It's

Re: Kernel panic from network traffic

On Fri, Jul 24, 2015 at 3:12 PM, Ryota Ozaki ozak...@netbsd.org wrote: Hi, It's probably due to my recent change to refcnt. I'm investigating that defect. Hmm, I cannot reproduce it. Could you tell me the kernel config, network setups and apps running on the box? Thanks, ozaki-r Thanks,

Re: Kernel panic from network traffic

On Thu, Jul 23, 2015 at 10:41 PM, Hisashi T Fujinaka ht...@twofifty.com wrote: Being a moron, I plugged ports of my switch together. The big surprise is two ports away is my -current box and it kept panicking. Hello fellow moron :) I have a general question: I see some comments around

Re: Kernel panic from network traffic

On Fri, 24 Jul 2015, Andy Ruhl wrote: On Thu, Jul 23, 2015 at 10:41 PM, Hisashi T Fujinaka ht...@twofifty.com wrote: Being a moron, I plugged ports of my switch together. The big surprise is two ports away is my -current box and it kept panicking. Hello fellow moron :) I have a general

Kernel panic from network traffic

Being a moron, I plugged ports of my switch together. The big surprise is two ports away is my -current box and it kept panicking. This is all I got so far. Jul 23 21:46:11 mara /netbsd: panic: kernel diagnostic assertion rt-rt_refcnt 0 failed: file /usr/src/sys/net/route.c, line 418 Jul 23

Kernel panic when entering ACPI sleep state S3

Hi all, I'm running the latest snapshot from nyftp.netbsd.org (201504151050Z) on a Thinkpad X120e. I seem to be encountering some issues when attempting to enter ACPI sleep state S3, using: sysctl -w hw.acpi.sleep.state=3 Upon invoking the above command, my system seems to attempt to sleep

Re: kernel panic: uvm_fault

On Mon, Dec 22, 2014 at 03:56:43PM +, Robert Swindells wrote: Thomas Klausner wrote: On Mon, Dec 22, 2014 at 03:29:58PM +, Robert Swindells wrote: Thomas Klausner wrote: I had a kernel panic today with a amd64/7.99.3 kernel from Dec 20. The last activity I had started

Re: kernel panic: uvm_fault

: Thomas Klausner wrote: I had a kernel panic today with a amd64/7.99.3 kernel from Dec 20. The last activity I had started was downloading a file from network to an NFS directory mounted from a Synology. It looks the same as the panic you had back in September to me

Re: kernel panic: uvm_fault

On Mon, Jan 26, 2015 at 01:07:40PM -0500, Thor Lancelot Simon wrote: On Mon, Jan 26, 2015 at 04:28:22PM +0100, Thomas Klausner wrote: On Mon, Jan 26, 2015 at 10:01:41AM -0500, Thor Lancelot Simon wrote: alloc_bouncebus? On amd64? I think you've got a trashed pointer somewhere. I

Re: kernel panic: uvm_fault

On Mon, Jan 26, 2015 at 04:28:22PM +0100, Thomas Klausner wrote: On Mon, Jan 26, 2015 at 10:01:41AM -0500, Thor Lancelot Simon wrote: alloc_bouncebus? On amd64? I think you've got a trashed pointer somewhere. I have makeoptions DEBUG=-g # compile full symbol table # grep -r

Re: kernel panic: uvm_fault

Thor Lancelot Simon wrote: On Mon, Jan 26, 2015 at 08:03:26PM +0100, Joerg Sonnenberger wrote: On Mon, Jan 26, 2015 at 01:07:40PM -0500, Thor Lancelot Simon wrote: On Mon, Jan 26, 2015 at 04:28:22PM +0100, Thomas Klausner wrote: On Mon, Jan 26, 2015 at 10:01:41AM -0500, Thor Lancelot Simon

Re: kernel panic: uvm_fault

On Mon, Dec 22, 2014 at 03:49:20PM +0100, Thomas Klausner wrote: I had a kernel panic today with a amd64/7.99.3 kernel from Dec 20. The last activity I had started was downloading a file from network to an NFS directory mounted from a Synology. I just saw that the Synology had installed

kernel panic: uvm_fault

Hi! I had a kernel panic today with a amd64/7.99.3 kernel from Dec 20. The last activity I had started was downloading a file from network to an NFS directory mounted from a Synology. I don't know if that's related, but there was no particular load on the machine. From dmesg after reboot

Re: kernel panic: uvm_fault

On Mon, Dec 22, 2014 at 03:29:58PM +, Robert Swindells wrote: Thomas Klausner wrote: I had a kernel panic today with a amd64/7.99.3 kernel from Dec 20. The last activity I had started was downloading a file from network to an NFS directory mounted from a Synology. last activity I had

Re: kernel panic on a cold start amd64.(msk0 and bridge problem).

On 27.05.2014 16:09, Ilia Zykov wrote: Now I can reproduce it persistent. Kernel panic on a network bridge with a msk interface hasn't connection. Do I need open a new bug? Or it can be fixed easy? The main reason is: msk0: watchdog timeout from source: void msk_watchdog(struct ifnet

Re: kernel panic on a cold start amd64.

Now I can reproduce it persistent. Kernel panic on a network bridge with a msk interface hasn't connection. Do I need open a new bug? Or it can be fixed easy? The main reason is: msk0: watchdog timeout from source: void msk_watchdog(struct ifnet *ifp) { [...] /* XXX

kernel panic on a cold start amd64.

But it is five years old the testing machine and can has hardware degradation. Crash version 6.99.42, image version 6.99.42. System panicked: kernel diagnostic assertion (!cpu_intr_p() !cpu_softintr_p()) || (pc-pc_pool.pr_ipl != IPL_NONE || cold || panicstr != NULL) failed: file

kernel panic in xhci on boot

On my desktop machine I am pretty much guaranteed a kernel panic when I reboot from windows 8 into NetBSD, the traceback is: softint_schedule() usb_schedsoftintr() xhci_intr1() The assert in softint_schedule is firing because offset is 0, this is passed in by usb_schedsoftintr, it should

Re: Kernel panic when trying to mount non-existing file-system

On Sat, Mar 29, 2014 at 03:19:48PM -0700, Andy Ruhl wrote: I didn't get the memo either. Sorry about the unusefull answer - of course the crash is not intended, but I couldn't reproduce it at first try last night - might depend on the architecture and concrete kernel (e.g. wether trying to load

Re: Kernel panic when trying to mount non-existing file-system

On Sat, Mar 29, 2014 at 08:54:36PM +0100, Adam Ciarci?ski wrote: Is that intentional? Yes, didn't you get the memo? Martin

Re: Kernel panic when trying to mount non-existing file-system

Is that intentional? Yes, didn't you get the memo? Martin No. I guess the postman stole it again. 8-) Adam

Re: Kernel panic when trying to mount non-existing file-system

On Sat, Mar 29, 2014 at 1:01 PM, Adam Ciarciński a...@netbsd.org wrote: Is that intentional? Yes, didn't you get the memo? Martin No. I guess the postman stole it again. 8-) I didn't get the memo either. This is not true in a relatively recent build of 6 when trying to mount NTFS and