Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89

On Sat, Jul 22, 2023 at 1:21 AM Yasuhiro Kimura wrote: > > From: Kevin Bowling > Subject: Re: Kernel panic after updating 14-CURRENT amd64 to > main-n264268-ff4633d9f89 > Date: Fri, 21 Jul 2023 21:44:13 -0700 > > > Thanks, I have reverted for now. Can you tell me whic

Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89

From: Kevin Bowling Subject: Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89 Date: Fri, 21 Jul 2023 21:44:13 -0700 > Thanks, I have reverted for now. Can you tell me which NIC is > implemented there? Output of `pciconf -lv` says as following. em0@pci0

Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89

Thanks, I have reverted for now. Can you tell me which NIC is implemented there? On Fri, Jul 21, 2023 at 12:45 PM Yasuhiro Kimura wrote: > > From: Yasuhiro Kimura > Subject: Kernel panic after updating 14-CURRENT amd64 to > main-n264268-ff4633d9f89 > Date: Sat, 22 Jul 2023 02:50:23 +0900 (JST)

Re: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89

From: Yasuhiro Kimura Subject: Kernel panic after updating 14-CURRENT amd64 to main-n264268-ff4633d9f89 Date: Sat, 22 Jul 2023 02:50:23 +0900 (JST) > After updating my 14.0-CURRENT amd64 system from > main-n264162-f58378393fb to main-n264268-ff4633d9f89, kernel crashes > with panic as following.

Re: Kernel panic on jail start

On Tue, Apr 04, 2023 at 02:31:20AM +0200, Goran Mekić wrote: > > > > > exec.start = "echo ifconfig_${vnet.interface}_name=\\"eth0\\" > > > > > >/etc/rc.conf.d/network"; > > > > > > > > ah, I see where the problem is, > > > > until its fixed you can try to set c

Re: Kernel panic on jail start

> > > > exec.start = "echo ifconfig_${vnet.interface}_name=\\"eth0\\" > > > > >/etc/rc.conf.d/network"; > > > > > > ah, I see where the problem is, > > > until its fixed you can try to set compat.linux.use_real_ifnames to 1, or > > > s/eth0/to some oyhe if na

Re: Kernel panic on jail start

On Mon, Apr 03, 2023 at 02:08:09PM +0200, Goran Mekić wrote: > On Fri, Mar 31, 2023 at 12:20:47PM +0300, Dmitry Chagin wrote: > > On Thu, Mar 30, 2023 at 07:08:28PM +0200, Goran Mekić wrote: > > > exec.start = "echo ifconfig_${vnet.interface}_name=\\"eth0\\" > > > >/etc/rc.conf.d/network"; > >

Re: Kernel panic on jail start

On Fri, Mar 31, 2023 at 12:20:47PM +0300, Dmitry Chagin wrote: > On Thu, Mar 30, 2023 at 07:08:28PM +0200, Goran Mekić wrote: > > exec.start = "echo ifconfig_${vnet.interface}_name=\\"eth0\\" > > >/etc/rc.conf.d/network"; > > ah, I see where the problem is, ^^

Re: Kernel panic on jail start

On Thu, Mar 30, 2023 at 07:08:28PM +0200, Goran Mekić wrote: > Hello, > > I get the kernel panic when starting jail. With git bisect I found out > the offending commit is 0b56641cfcda30d06243223f37781ccc18455bef. After > reverting it, everything is back to normal. For completeness, this is my > ja

Re: Kernel panic on jail start

On Thu, Mar 30, 2023 at 07:08:28PM +0200, Goran Mekić wrote: > Hello, > > I get the kernel panic when starting jail. With git bisect I found out > the offending commit is 0b56641cfcda30d06243223f37781ccc18455bef. After > reverting it, everything is back to normal. For completeness, this is my > ja

Re: kernel panic during zfs pool import

Still the same with current.(from today). Opening a PR for it.. Santi On 8/22/22 10:43, Santiago Martinez wrote: Thanks Toommas, I compiling current right now and will give it a try, hopefully, will be able to mount and recover the machine. Will also open a PR as even if the is any corru

Re: kernel panic during zfs pool import

Thanks Toommas, I compiling current right now and will give it a try, hopefully, will be able to mount and recover the machine. Will also open a PR as even if the is any corruption/pool damage it should not panic the machine. Santi On 8/18/22 21:45, Toomas Soome wrote: On 18. Aug 2022, a

Re: kernel panic during zfs pool import

> On 18. Aug 2022, at 18:46, Santiago Martinez wrote: > > Hi everyone, > > I have a server running 13.1-stable that was powered off (gracefully) and now > is been powered on again and we have the following problem. > > The server boots almost properly, kernel load and when zfs import other p

Re: Kernel panic on armv7 when PF is enabled

W dniu 2.05.2022 o 11:02, Kristof Provost pisze: On 1 May 2022, at 5:13, qroxana wrote: After git bisecting the panic started since this commit. commit 78bc3d5e1712bc1649aa5574d2b8d153f9665113 Author: Kristof Provost < k...@freebsd.org Date: Mon Feb 14 20:09:54 2022 +0100

Re: Kernel panic on armv7 when PF is enabled

On Monday, May 2nd, 2022 at 9:02 AM, Kristof Provost wrote: > On 1 May 2022, at 5:13, qroxana wrote: > > > After git bisecting the panic started since this commit. > > > > commit 78bc3d5e1712bc1649aa5574d2b8d153f9665113 > > > > Author: Kristof Provost < > > k...@freebsd.org > > > > Date: Mon F

Re: Kernel panic on armv7 when PF is enabled

On 1 May 2022, at 5:13, qroxana wrote: After git bisecting the panic started since this commit. commit 78bc3d5e1712bc1649aa5574d2b8d153f9665113 Author: Kristof Provost < k...@freebsd.org Date: Mon Feb 14 20:09:54 2022 +0100 vlan: allow net.link.vlan.mtag_pcp to be set per vnet The prima

Re: Kernel panic on armv7 when PF is enabled

On Sun, 01 May 2022 03:13:43 +, qroxana wrote: > After git bisecting the panic started since this commit. > > commit 78bc3d5e1712bc1649aa5574d2b8d153f9665113 > Author: Kristof Provost > Date: Mon Feb 14 20:09:54 2022 +0100 > > vlan: allow net.link.vlan.mtag_pcp to be set per vnet > >

Re: Kernel panic for if_epair

On 16 Feb 2022, at 11:31, qroxana wrote: > It's running 14.0-CURRENT armv7 main-n252983-d21e71efce39 > > Kernel page fault with the following non-sleepable locks held: > exclusive sleep mutex epairidx (epairidx) r = 0 (0xe2fe9160) locked @ > /usr/src/sys/net/if_epair.c:165 > stack backtrace: > #0

Re: Kernel Panic main-n252492-ad15eeeaba3 - Solved

On 1/17/22 16:33, Thomas Laus wrote: I just updated today to main-n252492-ad15eeeaba3 from: main-n252313-ae13829ddce on 3 PC's. I tried bisecting the 87 changes involved between main-n252508-aac52f94ea5 to main-n252492-ad15eeeaba3 and started at the halfway point and worked forward. After 25

Re: Kernel panic in networking code

On Thu, Dec 9, 2021 at 12:35 PM Shawn Webb wrote: > > On Thu, Dec 09, 2021 at 12:05:30PM -0500, Mark Johnston wrote: > > On Thu, Dec 09, 2021 at 10:20:10AM -0500, Shawn Webb wrote: > > > Hey all, > > > > > > It looks like there's a potential deadlock in some networking code, > > > specifically wit

Re: Kernel panic in networking code

On Thu, Dec 09, 2021 at 12:05:30PM -0500, Mark Johnston wrote: > On Thu, Dec 09, 2021 at 10:20:10AM -0500, Shawn Webb wrote: > > Hey all, > > > > It looks like there's a potential deadlock in some networking code, > > specifically with ipv4 jails. I can reproduce by running Poudriere on > > 14-CUR

Re: Kernel panic in networking code

On Thu, Dec 09, 2021 at 10:20:10AM -0500, Shawn Webb wrote: > Hey all, > > It looks like there's a potential deadlock in some networking code, > specifically with ipv4 jails. I can reproduce by running Poudriere on > 14-CURRENT. > > I am using HardenedBSD 14-CURRENT, but we don't have any changes

Re: Kernel panic by executing `poudriere bulk`

From: Mateusz Guzik Subject: Re: Kernel panic by executing `poudriere bulk` Date: Fri, 26 Nov 2021 20:33:22 +0100 > On 11/26/21, Yasuhiro Kimura wrote: >> yasu@rolling-vm-freebsd1[1015]% uname -a >> ~ >> FreeBSD rolling-vm-freebsd1.

Re: Kernel panic by executing `poudriere bulk`

On 11/26/21, Yasuhiro Kimura wrote: > yasu@rolling-vm-freebsd1[1015]% uname -a > ~ > FreeBSD rolling-vm-freebsd1.home.utahime.org 14.0-CURRENT FreeBSD > 14.0-CURRENT #0 main-n251115-ae92ace05fd: Sat Nov 27 01:47:15 JST 2021 > ro...@rolling-vm-freebsd1.home.u

Re: kernel panic while copying files

I was sort of hoping that all the recent changes made by imp@ in cam and umass may have fixed the cause of the kernel crash. Unfortunately not. But there is a change - instead of a duplicate free the panic is now the result of an unaligned free. panic: Unaligned free of 0xf800259e2800 from z

Re: kernel panic while copying files

On Sat, 12 Jun 2021 14:10:36 +0100 Edward Tomasz Napiera__a wrote: > On 0610T1150, Gary Jennejohn wrote: > > On Tue, 8 Jun 2021 17:54:05 +0200 > > Gary Jennejohn wrote: > > > > [big snip] > > [..] > > > So, I did ``git reset --hard 8dc96b74edb844bb621afeba38fe4af104b13120'', > > which was t

Re: kernel panic while copying files

On 0610T1150, Gary Jennejohn wrote: > On Tue, 8 Jun 2021 17:54:05 +0200 > Gary Jennejohn wrote: > > [big snip] [..] > So, I did ``git reset --hard 8dc96b74edb844bb621afeba38fe4af104b13120'', > which was the penultimate commit made by trasz to clear CCBs on the stack > after he committed 3394d42

Re: kernel panic while copying files

On Tue, 8 Jun 2021 17:54:05 +0200 Gary Jennejohn wrote: [big snip] > Here's the kgdb backtrace with the -O0 kernel: > > (kgdb) bt > #0 0x8081d706 in doadump (textdump=0) > at /usr/src/sys/kern/kern_shutdown.c:398 > #1 0x804ef15a in db_dump (dummy=-2138500043, dummy2=false,

Re: kernel panic while copying files

On Tue, 8 Jun 2021 06:27:04 -0600 Warner Losh wrote: > On Tue, Jun 8, 2021 at 2:47 AM Gary Jennejohn wrote: > [snip old stuff] > > Here the kgdb backtrace: > > > > Unread portion of the kernel message buffer: > > panic: Duplicate free of 0xf800356b9000 from zone > > 0xfe00dcbdd800(da_cc

Re: kernel panic while copying files

On Tue, Jun 8, 2021 at 8:42 AM Gary Jennejohn wrote: > On Tue, 8 Jun 2021 06:48:19 -0600 > Warner Losh wrote: > > > Sorry to reply to myself... had a thought as my brain rested while making > > tea... > > > > I think we may need to consider reverting (or at least not yet enabling) > > the uma st

Re: kernel panic while copying files

On Tue, 8 Jun 2021 06:48:19 -0600 Warner Losh wrote: > Sorry to reply to myself... had a thought as my brain rested while making > tea... > > I think we may need to consider reverting (or at least not yet enabling) > the uma stuff. > I tested and enabled the UMA CCB stuff immediately after tra

Re: kernel panic while copying files

Sorry to reply to myself... had a thought as my brain rested while making tea... I think we may need to consider reverting (or at least not yet enabling) the uma stuff. On Tue, Jun 8, 2021 at 6:27 AM Warner Losh wrote: > > > On Tue, Jun 8, 2021 at 2:47 AM Gary Jennejohn > wrote: > >> On Mon, 7

Re: kernel panic while copying files

On Tue, Jun 8, 2021 at 2:47 AM Gary Jennejohn wrote: > On Mon, 7 Jun 2021 16:54:11 -0400 > Mark Johnston wrote: > > > On Mon, Jun 07, 2021 at 11:01:09AM +0200, Gary Jennejohn wrote: > > > I've seen this panic three times in the last two days: > > > > > > [first panic] > > > Unread portion of the

Re: kernel panic while copying files

On Tue, 8 Jun 2021 11:04:33 +0200 Mateusz Guzik wrote: > Given how easy it is to reproduce perhaps you can spend a little bit > of time narrowing it down to a specific commit. You can do it with > git-bisect. > Ok, I'll give it a try. -- Gary Jennejohn

Re: kernel panic while copying files

On 6/8/21 1:34 PM, Gary Jennejohn wrote: Fields in the ccb like periph_name, unit_number and dev_name are filled with zeroes. Smells like a double free, like the panic message indicates, but would be nice to know exactly which driver is doing this, if it is "ATA" or "UMASS", so to speak. Ma

Re: kernel panic while copying files

On Tue, 8 Jun 2021 11:20:37 +0200 Hans Petter Selasky wrote: > On 6/8/21 11:04 AM, Mateusz Guzik wrote: > > Apparently caused by recent changes to CAM. > > > > Let me know if you want more information. > > Maybe you can print the *ccb being freed and figure out which device > it belongs to. >

Re: kernel panic while copying files

On 6/8/21 11:04 AM, Mateusz Guzik wrote: Apparently caused by recent changes to CAM. Let me know if you want more information. Maybe you can print the *ccb being freed and figure out which device it belongs to. --HPS

Re: kernel panic while copying files

Given how easy it is to reproduce perhaps you can spend a little bit of time narrowing it down to a specific commit. You can do it with git-bisect. On 6/8/21, Gary Jennejohn wrote: > On Mon, 7 Jun 2021 16:54:11 -0400 > Mark Johnston wrote: > >> On Mon, Jun 07, 2021 at 11:01:09AM +0200, Gary Jenn

Re: kernel panic while copying files

On Mon, 7 Jun 2021 16:54:11 -0400 Mark Johnston wrote: > On Mon, Jun 07, 2021 at 11:01:09AM +0200, Gary Jennejohn wrote: > > I've seen this panic three times in the last two days: > > > > [first panic] > > Unread portion of the kernel message buffer: > > > > > > Fatal trap 12: page fault while

Re: kernel panic while copying files

On Mon, Jun 07, 2021 at 11:01:09AM +0200, Gary Jennejohn wrote: > I've seen this panic three times in the last two days: > > [first panic] > Unread portion of the kernel message buffer: > > > Fatal trap 12: page fault while in kernel mode > cpuid = 3; apic id = 03 > fault virtual address = 0x8

Re: kernel panic and fun debugging

On Sat, Oct 17, 2020 at 1:17 PM Steve Kargl < s...@troutmask.apl.washington.edu> wrote: > On Sat, Oct 17, 2020 at 12:58:48PM -0600, Warner Losh wrote: > > On Sat, Oct 17, 2020, 12:00 PM Andrey V. Elsukov > wrote: > > > > > On 15.10.2020 09:56, Steve Kargl wrote: > > > > Just had a kernel panic.

Re: kernel panic and fun debugging

On Sat, Oct 17, 2020 at 12:58:48PM -0600, Warner Losh wrote: > On Sat, Oct 17, 2020, 12:00 PM Andrey V. Elsukov wrote: > > > On 15.10.2020 09:56, Steve Kargl wrote: > > > Just had a kernel panic. Best info I give you is > > > > > > % uname -a > > > FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURREN

Re: kernel panic and fun debugging

On Sat, Oct 17, 2020 at 08:57:31PM +0300, Andrey V. Elsukov wrote: > On 15.10.2020 09:56, Steve Kargl wrote: > > Just had a kernel panic. Best info I give you is > > > > % uname -a > > FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r366176M: Sat Sep 26 > > 10:35:23 PDT 2020 kargl@mobile

Re: kernel panic and fun debugging

On Sat, Oct 17, 2020, 12:00 PM Andrey V. Elsukov wrote: > On 15.10.2020 09:56, Steve Kargl wrote: > > Just had a kernel panic. Best info I give you is > > > > % uname -a > > FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r366176M: Sat Sep 26 > 10:35:23 PDT 2020 kargl@mobile:/usr/obj/usr

Re: kernel panic and fun debugging

On 15.10.2020 09:56, Steve Kargl wrote: > Just had a kernel panic. Best info I give you is > > % uname -a > FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r366176M: Sat Sep 26 > 10:35:23 PDT 2020 kargl@mobile:/usr/obj/usr/src/i386.i386/sys/MOBILE i386 > > % kgdb gdb /usr/lib/debug/boo

Re: Kernel panic on recent 12.1 on bridge creation.

I've reproduced this on the latest snapshot build of stable/12 and created a PR here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248046 On 7/16/20 6:26 PM, Daniel Dettlaff wrote: On 17.07.2020, at 00:16, Daniel Dettlaff wrote: Hello, I heard it's known? I built recent system from stab

Re: Kernel panic on recent 12.1 on bridge creation.

> On 17.07.2020, at 00:16, Daniel Dettlaff wrote: > > Hello, I heard it's known? > > I built recent system from stable/12 branch and either "ifconfig bridge0 > create" and `cloned_interfaces="bridge0"` + `ifconfig_bridge0_aliases="inet > 172.16.7.1/16` in rc.conf.local causes instant KP and

Re: Kernel panic after rebuilding CURRENT

Yes for me too. Op vr 27 sep. 2019 om 13:23 schreef mms.vanbreukelin...@gmail.com < mms.vanbreukelin...@gmail.com>: > Works again, just 'svn up' to the latest release, rebuuld, nothing to > do with virtualization but a serious kernel problem - IMO having too little > userspace and too much r

Re: Kernel panic after rebuilding CURRENT

Just a me too, for me it is a standard FreeBSD running on virtualbox. regards, Johan Op wo 25 sep. 2019 om 17:30 schreef mms.vanbreukelin...@gmail.com < mms.vanbreukelin...@gmail.com>: > Had verbose on and got the following kernel error on 290: > taskqgroup_adjust_if_config_tqg: panic: sche

Re: kernel panic in wireless-related sysctl walk

On 1/12/19 5:12 AM, O. Hartmann wrote: > Am Thu, 10 Jan 2019 22:22:05 +0100 > "O. Hartmann" schrieb: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 > >> Am Thu, 10 Jan 2019 12:02:15 -0800 >> Cy Schubert schrieb: > >>> I'm not able to reproduce this at the moment. I can confirm that SV

Re: kernel panic in wireless-related sysctl walk

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Thu, 10 Jan 2019 22:22:05 +0100 "O. Hartmann" schrieb: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Am Thu, 10 Jan 2019 12:02:15 -0800 > Cy Schubert schrieb: > > > I'm not able to reproduce this at the moment. > > > > > > I ha

RE: kernel panic in wireless-related sysctl walk

-current Subject: Re: kernel panic in wireless-related sysctl walk -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Thu, 10 Jan 2019 12:02:15 -0800 Cy Schubert schrieb: > I'm not able to reproduce this at the moment. > > I have a oldish Lenovo R500 Notebook running FreeBSD-12 S

Re: kernel panic in wireless-related sysctl walk

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Thu, 10 Jan 2019 12:02:15 -0800 Cy Schubert schrieb: > I'm not able to reproduce this at the moment. > > I have a oldish Lenovo R500 Notebook running FreeBSD-12 STABLE. I'm not sure what WiFi Interface driver the system is using right now; t

Re: kernel panic in wireless-related sysctl walk

- > > -Original Message- > From: Michael Zhilin > Sent: 10/01/2019 08:00 > To: Michael Butler > Cc: freebsd-current > Subject: Re: kernel panic in wireless-related sysctl walk > > I'm not lucky to reproduce it even if i use iwn and "sysctl > net.wlan.0

RE: kernel panic in wireless-related sysctl walk

pports top post. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -Original Message- From: Michael Zhilin Sent: 10/01/2019 08:00 To: Michael Butler Cc: freebsd-current Subject: Re: kernel panic in wireless-related sysctl walk I'm not lucky to reprodu

Re: kernel panic in wireless-related sysctl walk

I'm not lucky to reproduce it even if i use iwn and "sysctl net.wlan.0.rate_stats" Problem is related to 802.11n, but all my networks are 11g. BR On Thu, Jan 10, 2019 at 6:53 PM Michael Zhilin wrote: > Hi, > > Is it possible to print out any local variables of frame #8? > > Thx! > > On Thu, Jan

Re: kernel panic in wireless-related sysctl walk

Hi, Is it possible to print out any local variables of frame #8? Thx! On Thu, Jan 10, 2019 at 6:31 PM Michael Butler wrote: > With 'device iwn' and all the related wireless bits compiled into a > custom kernel for a laptop, executing 'sysctl -a' yields a kernel panic > of the form .. > > Fatal

Re: Kernel Panic - Sublime Text - 12.0-PRERELEASE r340650M

Updated to r340868 and the issue has been resolved, thank you for your time! James On 24/11/2018 09:53, Tijl Coosemans wrote: On Sat, 24 Nov 2018 02:05:51 + James Wright wrote: When trying to run sublime text via the linuxulator my system panics and reboots. Unfortunately I do not have m

Re: Kernel Panic - Sublime Text - 12.0-PRERELEASE r340650M

On Sat, 24 Nov 2018 02:05:51 + James Wright wrote: > When trying to run sublime text via the linuxulator my system panics > and reboots. Unfortunately I do not have much extra info as it crashes > immediately and seems to corrupt the UFS filesystem in the process > (which has to be fixed with

[SOLVED] Re: Kernel Panic On Boot after r327979

On 01/15/2018 09:26, Pete Wright wrote: Hello, I updated an amd64 system last night to r327979 and it panics into gdb after rc attempts to mount local filesystems. The panic line is: Fatal trap 12: page fault while in kernel mode gdb states that it stopped at: Stopped at    prison_allow+0x4

Re: kernel panic: make_dev_alias_v bad si_name (error=22) si_name=vtcon/ org.qemu.guest_agent.0)

Hi Wolfram, I believe r305900 broke it. I don't have any patch or workaround, sorry. It wouldn't be too hard for someone interested in virtualization to fix the issue. Please follow up in the bug :-). Best, Conrad On Wed, Nov 15, 2017 at 7:16 AM, Wolfram Schneider wrote: > Hi Conrad, > > tha

Re: kernel panic: make_dev_alias_v bad si_name (error=22) si_name=vtcon/ org.qemu.guest_agent.0)

On 15 November 2017 at 10:58, Conrad Meyer wrote: > Hi Wolfram, > > Looks like the same issue as > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531 . Hi Conrad, thanks for the hint. Do you know which commit may broke the driver? Is there any patch or workaround? I do not have access to

Re: kernel panic: make_dev_alias_v bad si_name (error=22) si_name=vtcon/ org.qemu.guest_agent.0)

Hi Wolfram, Looks like the same issue as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531 . Best, Conrad On Wed, Nov 15, 2017 at 1:31 AM, Wolfram Schneider wrote: > Hi, > > I have a virtual machine running with FreeBSD 11-stable at a cloud > provider. It runs fine. I tried to upgrade to

Re: kernel panic with ipnat/dummynet

___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: kernel panic caused by virtualbox(?)

On Thu, Aug 11, 2016 at 03:22:44PM -0700, Don Lewis wrote: > On 11 Aug, Konstantin Belousov wrote: > > On Wed, Aug 10, 2016 at 04:47:15PM -0700, Don Lewis wrote: > >> On 10 Aug, Jung-uk Kim wrote: > >> > On 08/09/16 05:12 AM, Konstantin Belousov wrote: > >> >> On Mon, Aug 08, 2016 at 04:44:20PM -07

Re: kernel panic caused by virtualbox(?)

On 11 Aug, Konstantin Belousov wrote: > On Wed, Aug 10, 2016 at 04:47:15PM -0700, Don Lewis wrote: >> On 10 Aug, Jung-uk Kim wrote: >> > On 08/09/16 05:12 AM, Konstantin Belousov wrote: >> >> On Mon, Aug 08, 2016 at 04:44:20PM -0700, Don Lewis wrote: >> >>> On 8 Aug, Konstantin Belousov wrote: >>

Re: kernel panic caused by virtualbox(?)

On Wed, Aug 10, 2016 at 04:47:15PM -0700, Don Lewis wrote: > On 10 Aug, Jung-uk Kim wrote: > > On 08/09/16 05:12 AM, Konstantin Belousov wrote: > >> On Mon, Aug 08, 2016 at 04:44:20PM -0700, Don Lewis wrote: > >>> On 8 Aug, Konstantin Belousov wrote: > On Mon, Aug 08, 2016 at 10:22:44AM -0700

Re: kernel panic caused by virtualbox(?)

On 10 Aug, Jung-uk Kim wrote: > On 08/09/16 05:12 AM, Konstantin Belousov wrote: >> On Mon, Aug 08, 2016 at 04:44:20PM -0700, Don Lewis wrote: >>> On 8 Aug, Konstantin Belousov wrote: On Mon, Aug 08, 2016 at 10:22:44AM -0700, John Baldwin wrote: > On Thursday, August 04, 2016 05:10:29 PM

Re: kernel panic caused by virtualbox(?)

On 08/09/16 05:12 AM, Konstantin Belousov wrote: > On Mon, Aug 08, 2016 at 04:44:20PM -0700, Don Lewis wrote: >> On 8 Aug, Konstantin Belousov wrote: >>> On Mon, Aug 08, 2016 at 10:22:44AM -0700, John Baldwin wrote: On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote: > Reposted to -

Re: kernel panic caused by virtualbox(?)

On Mon, Aug 08, 2016 at 04:44:20PM -0700, Don Lewis wrote: > On 8 Aug, Konstantin Belousov wrote: > > On Mon, Aug 08, 2016 at 10:22:44AM -0700, John Baldwin wrote: > >> On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote: > >> > Reposted to -current to get some more eyes on this ... > >> > >

Re: kernel panic caused by virtualbox(?)

On 8 Aug, Konstantin Belousov wrote: > On Mon, Aug 08, 2016 at 10:22:44AM -0700, John Baldwin wrote: >> On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote: >> > Reposted to -current to get some more eyes on this ... >> > >> > I just got a kernel panic when I started up a CentOS 7 VM in virt

Re: kernel panic caused by virtualbox(?)

On 8 Aug, Konstantin Belousov wrote: > On Mon, Aug 08, 2016 at 10:22:44AM -0700, John Baldwin wrote: >> On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote: >> > Reposted to -current to get some more eyes on this ... >> > >> > I just got a kernel panic when I started up a CentOS 7 VM in virt

Re: kernel panic caused by virtualbox(?)

On 8 Aug, John Baldwin wrote: > On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote: >> Reposted to -current to get some more eyes on this ... >> >> I just got a kernel panic when I started up a CentOS 7 VM in virtualbox. >> The host is: >> FreeBSD 12.0-CURRENT #17 r302500 GENERIC amd64

Re: kernel panic caused by virtualbox(?)

On Mon, Aug 08, 2016 at 10:22:44AM -0700, John Baldwin wrote: > On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote: > > Reposted to -current to get some more eyes on this ... > > > > I just got a kernel panic when I started up a CentOS 7 VM in virtualbox. > > The host is: > > FreeBSD 12.

Re: kernel panic caused by virtualbox(?)

On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote: > Reposted to -current to get some more eyes on this ... > > I just got a kernel panic when I started up a CentOS 7 VM in virtualbox. > The host is: > FreeBSD 12.0-CURRENT #17 r302500 GENERIC amd64 > The virtualbox version is: >

Re: Kernel panic - help

And again, at almost the same time ... kernel panic!!! May 17 03:06:18 dns0 syslogd: kernel boot file is /boot/kernel/kernel May 17 03:06:18 dns0 kernel: panic: softdep_deallocate_dependencies: dangling deps May 17 03:06:18 dns0 kernel: cpuid = 1 May 17 03:06:18 dns0 kernel: KDB: stack backtrace:

Re: Kernel panic from recent build

I intend it as a workaround to be committed, not as debugging. Eric On 05/02/2016 18:51, Ryan Stone wrote: > Do we need this debug output? It's quite clear from the acpidump output > that there is an entry for APIC ID 0 in memory domain 0 and memory > domain 1. Not sure if that's legal by the s

Re: Kernel panic from recent build

On Monday, May 02, 2016 05:17:49 PM Eric van Gyzen wrote: > On 05/02/2016 16:14, Bill O'Hanlon wrote: > > On Mon, May 2, 2016 at 3:55 PM, John Baldwin wrote: > > > >> On Monday, May 02, 2016 01:35:54 PM Bill O'Hanlon wrote: > >>> ​ > >>> IMG_20160502_130335.jpg > >>> < > >> https://drive.google.c

Re: Kernel panic from recent build

Do we need this debug output? It's quite clear from the acpidump output that there is an entry for APIC ID 0 in memory domain 0 and memory domain 1. Not sure if that's legal by the spec. On Mon, May 2, 2016 at 6:17 PM, Eric van Gyzen wrote: > On 05/02/2016 16:14, Bill O'Hanlon wrote: > > On Mo

Re: Kernel panic from recent build

On 05/02/2016 16:14, Bill O'Hanlon wrote: > On Mon, May 2, 2016 at 3:55 PM, John Baldwin wrote: > >> On Monday, May 02, 2016 01:35:54 PM Bill O'Hanlon wrote: >>> ​ >>> IMG_20160502_130335.jpg >>> < >> https://drive.google.com/file/d/1dtJxTwWXfhXVUUtn1Vvpzh3laJt7AILyCg/view?usp=drive_web >>> ​ >>>

Re: Kernel panic from recent build

On Mon, May 2, 2016 at 3:55 PM, John Baldwin wrote: > On Monday, May 02, 2016 01:35:54 PM Bill O'Hanlon wrote: > > ​ > > IMG_20160502_130335.jpg > > < > https://drive.google.com/file/d/1dtJxTwWXfhXVUUtn1Vvpzh3laJt7AILyCg/view?usp=drive_web > > > > ​ > > I'm getting the following panic from a rec

Re: Kernel panic from recent build

On Monday, May 02, 2016 01:35:54 PM Bill O'Hanlon wrote: > ​ > IMG_20160502_130335.jpg > > ​ > I'm getting the following panic from a recent (May 2, 2016) build. > panic: Duplicate local APIC ID 0 > > The sys

Re: kernel panic by enabling net.inet.ip.random_id

On Wed, Jan 06, 2016 at 01:24:53PM -0500, Shawn Webb wrote: S> That's what gets toggled via the sysctl. I think I figured out that I S> need to call ip_initid() in the SYSINIT. Compiling and testing now. Right, that's the problem. You actually want VNET_SYSINIT(). Please next time you report a pa

Re: kernel panic by enabling net.inet.ip.random_id

Yup, calling ip_initid() in the SYSINIT works! Thanks for the help. Thanks, Shawn On Wed, Jan 06, 2016 at 01:24:53PM -0500, Shawn Webb wrote: > That's what gets toggled via the sysctl. I think I figured out that I > need to call ip_initid() in the SYSINIT. Compiling and testing now. > > Thanks,

Re: kernel panic by enabling net.inet.ip.random_id

That's what gets toggled via the sysctl. I think I figured out that I need to call ip_initid() in the SYSINIT. Compiling and testing now. Thanks, Shawn On Wed, Jan 06, 2016 at 10:15:08AM -0800, Adrian Chadd wrote: > Why'd you condition the vimage definition? :) > > > > -a > > > On 6 January

Re: kernel panic by enabling net.inet.ip.random_id

Why'd you condition the vimage definition? :) -a On 6 January 2016 at 06:46, Shawn Webb wrote: > (kgdb) list *(0x80b5de9e) > 0x80b5de9e is in ip_fillid (/usr/src/sys/netinet/ip_id.c:237). > warning: Source file is more recent than executable. > > 232 new_id = 0; >

Re: kernel panic by enabling net.inet.ip.random_id

(kgdb) list *(0x80b5de9e) 0x80b5de9e is in ip_fillid (/usr/src/sys/netinet/ip_id.c:237). warning: Source file is more recent than executable. 232 new_id = 0; 233 do { 234 if (new_id != 0) 235 V_random_id_collis

Re: kernel panic by enabling net.inet.ip.random_id

try list *(0x[address]) . That line is mtx_unlock(), which makes no sense (as mtx_lock succeeded fine.) -a On 5 January 2016 at 18:13, Shawn Webb wrote: > Thanks for the quick reply! Here's some more debugging output: > > === Begin Log === > (kgdb) bt > #0 doadump (textdump=0) at pcpu.h:221

Re: kernel panic by enabling net.inet.ip.random_id

Thanks for the quick reply! Here's some more debugging output: === Begin Log === (kgdb) bt #0 doadump (textdump=0) at pcpu.h:221 #1 0x8037c78b in db_dump (dummy=, dummy2=false, dummy3=0, dummy4=0x0) at /usr/src/sys/ddb/db_command.c:533 #2 0x8037c57e in db_command (cmd_table=0x0

Re: kernel panic by enabling net.inet.ip.random_id

looks like a null pointer deference. What's kgdb show at that IP? -a On 5 January 2016 at 17:57, Shawn Webb wrote: > Hey All, > > Here's a kernel panic I'm experiencing by enabling net.inet.ip.random_id > at boot. > > I'm on latest HEAD on amd64 in bhyve. I'll soon-ish be testing on native > h

Re: Kernel panic with my kernel config. Applies to 9.x up to 10.2

On Sunday, September 13, 2015 05:17:03 PM Daniel Dettlaff wrote: > Hi, I have custom kernel config: > https://gist.github.com/dmilith/234b3e6b65b6fa606e27 > If I uncomment VIMAGE and epair from lines 10-11, each time I try to launch > any jail with vnet it panics the kernel. (also HBSD options mi

Re: Kernel panic with fresh current, probably nfs related

On 08/29/15 00:38, Joel Dahl wrote: > On Tue, Aug 25, 2015 at 12:55:02PM -0700, Sean Bruno wrote: >> >> >> On 08/25/15 12:10, Joel Dahl wrote: > Seems to work. However, I cannot reproduce the user panic in the first > place. What's the scenario that seems to work here? NFS seems happy >

Re: Kernel panic with fresh current, probably nfs related

On Tue, Aug 25, 2015 at 12:55:02PM -0700, Sean Bruno wrote: > > > On 08/25/15 12:10, Joel Dahl wrote: > >> > Seems to work. However, I cannot reproduce the user panic in the first > >> > place. What's the scenario that seems to work here? NFS seems happy > >> > with/without the patch so I'm not

Re: Kernel panic with fresh current, probably nfs related

On 08/25/15 12:10, Joel Dahl wrote: >> > Seems to work. However, I cannot reproduce the user panic in the first >> > place. What's the scenario that seems to work here? NFS seems happy >> > with/without the patch so I'm not confident in anything we are doing her >> > e. > I see several patches

Re: Kernel panic with fresh current, probably nfs related

On Mon, Aug 24, 2015 at 11:18:00AM -0700, Sean Bruno wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > > > On 08/23/15 18:36, Yonghyeon PYUN wrote: > > Index: sys/dev/e1000/if_em.c > > === > > > > > - --- sys/dev/e100

Re: Kernel panic with fresh current, probably nfs related

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 08/23/15 18:36, Yonghyeon PYUN wrote: > Index: sys/dev/e1000/if_em.c > === > > - --- sys/dev/e1000/if_em.c (revision 287087) > +++ sys/dev/e1000/if_em.c (working copy) @@

Re: Kernel panic with fresh current, probably nfs related

On Sat, Aug 22, 2015 at 08:57:40AM -0400, Rick Macklem wrote: > Joel Dahl wrote: > > Hi, > > > > I hit a kernel panic running a fresh -CURRENT today. This machine is my home > > NFS > > server and it exports src and obj to a bunch of other machines. During an > > installkernel on one of the other

Re: Kernel panic with fresh current, probably nfs related

On Sat, Aug 22, 2015 at 11:25:58AM -0700, Sean Bruno wrote: > > > > > I'm going to guess that you're using an "em" net driver, since that is the > > only one that sets if_hw_tsomax > IP_MAXPACKET (65535) from what I can see. > > > > Sean, EM_TSO_SIZE is defined as (65535 + sizeof(struct ether_v

Re: Kernel panic with fresh current, probably nfs related

> I'm going to guess that you're using an "em" net driver, since that is the > only one that sets if_hw_tsomax > IP_MAXPACKET (65535) from what I can see. > > Sean, EM_TSO_SIZE is defined as (65535 + sizeof(struct ether_vlan_header)), > which makes it > IP_MAXPACKET. The value of if_hw_tsomax m

Re: Kernel panic with fresh current, probably nfs related

Joel Dahl wrote: > Hi, > > I hit a kernel panic running a fresh -CURRENT today. This machine is my home > NFS > server and it exports src and obj to a bunch of other machines. During an > installkernel on one of the other machines (using the src and obj exports > from > the NFS server) the NFS ser

  1   2   3   4   >