r323412: Panic on boot (slab->us_keg == keg)

I've recently tried to upgrade a HEAD VM (running on a Linux host with QEMU) from r321082 to r323412. The new kernel panics right after I try to boot into it with: panic: Assertion slab->us_keg == keg failed at /usr/src/sys/vm/uma_core.c:2285 cpuid = 0 time = 1 KDB: stack backtrace:

[ solved ] Re: Panic on boot after upgrade from r320827 -> r320869

On 07/15/17 15:32, I wrote: Something about SVN r320844 causes almost all KDE applications to fail on a signal 6. I've recompiled KDE and other components obviously dependent on kernel structures (e.g. everything dbus-related). I still get core-files with a back-trace that looks like: [

Re: Panic on boot after upgrade from r320827 -> r320869

Warner Losh imp at bsdimp.com wrote on Sat Jul 15 23:22:22 UTC 2017 : > On Sat, Jul 15, 2017 at 1:32 PM, Michael Butler protected-networks.net> > wrote: > > > On 07/11/17 19:53, Michael Butler wrote: > > > . . . > > > > Something about SVN r320844 causes almost all KDE applications to fail on >

Re: Panic on boot after upgrade from r320827 -> r320869

On Sat, Jul 15, 2017 at 6:49 PM, Michael Butler wrote: > On 07/15/17 20:39, Mark Millard wrote: > >> FYI for Michael B.: the incomplete kernel rebuild problem has a fix: >> -r320919 . >> See the fix (to the building problem that was created in -r320220 ): >> >>

Re: Panic on boot after upgrade from r320827 -> r320869

On 07/15/17 20:39, Mark Millard wrote: FYI for Michael B.: the incomplete kernel rebuild problem has a fix: -r320919 . See the fix (to the building problem that was created in -r320220 ): https://lists.freebsd.org/pipermail/svn-src-head/2017-July/102622.html If the KDE problem persists based

Re: Panic on boot after upgrade from r320827 -> r320869

On Sat, Jul 15, 2017 at 1:32 PM, Michael Butler wrote: > On 07/11/17 19:53, Michael Butler wrote: > >> On 07/11/17 13:13, I wrote: >> >>> Take sdhci out of the kernel and try again. If that works, it tells us one thing (need to troubleshoot sdhci stuff

Re: Panic on boot after upgrade from r320827 -> r320869

On 07/11/17 19:53, Michael Butler wrote: On 07/11/17 13:13, I wrote: Take sdhci out of the kernel and try again. If that works, it tells us one thing (need to troubleshoot sdhci stuff more). If not it tells us another (need to troubleshoot CAM more), do we get errors with the ATA_IDENTIFY

Re: Panic on boot after upgrade from r320827 -> r320869

On 7/11/17 10:13 AM, Bryan Drewery wrote: > On 7/11/17 10:09 AM, Warner Losh wrote: >> Plus we know we have at least one bug in meta-mode rebuilding since not >> everything is being rebuilt that should be across this change. > > Yes I'm looking into that. > This was a bug with buildkernel with

Re: Panic on boot after upgrade from r320827 -> r320869

On 07/11/17 13:13, I wrote: Take sdhci out of the kernel and try again. If that works, it tells us one thing (need to troubleshoot sdhci stuff more). If not it tells us another (need to troubleshoot CAM more), do we get errors with the ATA_IDENTIFY command? Does it try multiple times per AHCI

Re: Panic on boot after upgrade from r320827 -> r320869

On 7/11/17 1:09 PM, Warner Losh wrote: On a machine with SDHCI, a clean rebuild (after "r -rf /usr/obj") refuses to find /dev/ada0 :-( Take sdhci out of the kernel and try again. If that works, it tells us one thing (need to troubleshoot sdhci stuff more). If not it tells us another (need

Re: Panic on boot after upgrade from r320827 -> r320869

On 7/11/17 10:09 AM, Warner Losh wrote: > Plus we know we have at least one bug in meta-mode rebuilding since not > everything is being rebuilt that should be across this change. Yes I'm looking into that. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature

Re: Panic on boot after upgrade from r320827 -> r320869

On Tue, Jul 11, 2017 at 10:47 AM, Michael Butler wrote: > On 7/11/17 10:32 AM, Warner Losh wrote: > >> On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill >> wrote: >> >>> I believe that each of the machines has an MMC slot, but I also believe

Re: Panic on boot after upgrade from r320827 -> r320869

On 7/11/17 10:32 AM, Warner Losh wrote: On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill wrote: I believe that each of the machines has an MMC slot, but I also believe that in each case, it is empty. Is there anything else I might be able to do to help resolve this?

Re: Panic on boot after upgrade from r320827 -> r320869

On Tue, Jul 11, 2017 at 08:32:26AM -0600, Warner Losh wrote: > ... > > While O. Hartmann had written to indicate the he had identified r320844 > > as the culprit, and I had other reason to suspect it, I was a bit busy > > at work yesterday, and unable to determine this for myself empirically. > >

Re: Panic on boot after upgrade from r320827 -> r320869

On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill wrote: > On Mon, Jul 10, 2017 at 04:51:09AM -0700, David Wolfskill wrote: > > Pnic occurred prior to mounting file systems > > While O. Hartmann had written to indicate the he had identified r320844 > as the culprit, and

Re: Panic on boot after upgrade from r320827 -> r320869

On Mon, Jul 10, 2017 at 04:51:09AM -0700, David Wolfskill wrote: > Pnic occurred prior to mounting file systems While O. Hartmann had written to indicate the he had identified r320844 as the culprit, and I had other reason to suspect it, I was a bit busy at work yesterday, and unable to

Re: Panic on boot after upgrade from r320827 -> r320869

Am Mon, 10 Jul 2017 04:51:09 -0700 David Wolfskill schrieb: > Pnic occurred prior to mounting file systems; I was able to boot > from the r320827 (as "kernel.old") OK. I was not able to get a > dump. Both the laptop and the build machine panicked, but the build >

Panic on boot after upgrade from r320827 -> r320869

Pnic occurred prior to mounting file systems; I was able to boot from the r320827 (as "kernel.old") OK. I was not able to get a dump. Both the laptop and the build machine panicked, but the build machine's keyboard was unresponsive and its serial console isn't funtioning at the moment (because

Re: Panic on boot current amd64

Am Tue, 17 Jan 2017 06:45:42 -0700 Sean Bruno <sbr...@freebsd.org> schrieb: > On 01/17/17 02:10, O. Hartmann wrote: > > Am Mon, 16 Jan 2017 10:33:35 -0800 > > Manfred Antar <n...@pozo.com> schrieb: > > > >> From current today after changes to /sys/sy

Re: Panic on boot current amd64

On 01/17/17 02:10, O. Hartmann wrote: > Am Mon, 16 Jan 2017 10:33:35 -0800 > Manfred Antar <n...@pozo.com> schrieb: > >> From current today after changes to /sys/sys/gtaskqueue.h (r312293) I get >> panic on boot. >> reverting to r312235 boot ok >> >&g

Re: Panic on boot current amd64

Am Mon, 16 Jan 2017 10:33:35 -0800 Manfred Antar <n...@pozo.com> schrieb: > From current today after changes to /sys/sys/gtaskqueue.h (r312293) I get > panic on boot. > reverting to r312235 boot ok > > random: harvesting attach, 8 bytes (4 bits) from uhub9 > ugen1.3: at

Re: Panic on boot current amd64

Am Mon, 16 Jan 2017 10:33:35 -0800 Manfred Antar <n...@pozo.com> schrieb: > From current today after changes to /sys/sys/gtaskqueue.h (r312293) I get > panic on boot. > reverting to r312235 boot ok > > random: harvesting attach, 8 bytes (4 bits) from uhub9 > ugen1.3: at

Re: Panic on boot current amd64

On 01/16/17 11:33, Manfred Antar wrote: >>From current today after changes to /sys/sys/gtaskqueue.h (r312293) I get >>panic on boot. > reverting to r312235 boot ok > > random: harvesting attach, 8 bytes (4 bits) from uhub9 > ugen1.3: at usbus1 > kernel trap

Panic on boot current amd64

>From current today after changes to /sys/sys/gtaskqueue.h (r312293) I get >panic on boot. reverting to r312235 boot ok random: harvesting attach, 8 bytes (4 bits) from uhub9 ugen1.3: at usbus1 kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpu

Re: IPFW panic on boot

On Tue, Nov 3, 2015, at 21:29, David Wolfskill wrote: > On Tue, Nov 03, 2015 at 09:08:28PM -0600, Mark Felder wrote: > > Recent ipfw commits now cause my firewall to panic on boot. I had to > > revert them and only pull in Adrian's ath fix which was to fix yet a > &

IPFW panic on boot

Recent ipfw commits now cause my firewall to panic on boot. I had to revert them and only pull in Adrian's ath fix which was to fix yet a different panic I was encountering... :-) KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe01226a33e0 vpanic

Re: IPFW panic on boot

On Tue, Nov 03, 2015 at 09:08:28PM -0600, Mark Felder wrote: > Recent ipfw commits now cause my firewall to panic on boot. I had to > revert them and only pull in Adrian's ath fix which was to fix yet a > different panic I was encountering... :-) > > KDB: stack backtrace: > db_

Re: Panic on boot during scan with pmspcv

On Tuesday, August 25, 2015 02:27:42 PM Conrad Meyer wrote: > For some reason, it only crops up on UEFI boot. "Legacy" boot "just works." > > It looks like we're locking a mutex in a struct at NULL. > > (trap) > __mtx_assert+0xdb > agtiapi_cam_action+0x45 > xpt_action_default+0xbe3(?) >

Re: Panic on boot during scan with pmspcv

> On Sep 1, 2015, at 13:30, Conrad Meyer wrote: > >> On Mon, Aug 31, 2015 at 6:20 PM, John Baldwin wrote: >> Probably pCardInfo is NULL. >> >> Looking at the pms driver source is making my stomach churn, but I don't >> see anything obvious. The field is

Re: Panic on boot during scan with pmspcv

On Mon, Aug 31, 2015 at 6:20 PM, John Baldwin wrote: > Probably pCardInfo is NULL. > > Looking at the pms driver source is making my stomach churn, but I don't > see anything obvious. The field is set during attach, so it shouldn't be > NULL when the intrhook runs. Do you have

Panic on boot during scan with pmspcv

For some reason, it only crops up on UEFI boot. Legacy boot just works. It looks like we're locking a mutex in a struct at NULL. (trap) __mtx_assert+0xdb agtiapi_cam_action+0x45 xpt_action_default+0xbe3(?) scsi_scan_bus+0x1cd xpt_scanner_thread+0x15c ... Fault is at 0x18.

Re: pmspcv panic on boot on this box

On Aug 4, 2015, at 6:13 PM, Glen Barber g...@freebsd.org wrote: On Mon, Aug 03, 2015 at 12:10:57PM -0500, Larry Rosenman wrote: Just to close this out, current -HEAD is fine on this box with pmspcv in GENERIC, and using that as my base. No nasty pmspcv messages. Sorry for the delayed

Re: pmspcv panic on boot on this box

On 2015-08-04 19:13, Glen Barber wrote: On Mon, Aug 03, 2015 at 12:10:57PM -0500, Larry Rosenman wrote: Just to close this out, current -HEAD is fine on this box with pmspcv in GENERIC, and using that as my base. No nasty pmspcv messages. Sorry for the delayed reply. Again, Larry, thank

Re: pmspcv panic on boot on this box

On Mon, Aug 03, 2015 at 12:10:57PM -0500, Larry Rosenman wrote: Just to close this out, current -HEAD is fine on this box with pmspcv in GENERIC, and using that as my base. No nasty pmspcv messages. Sorry for the delayed reply. Again, Larry, thank you for your help with this - you very

Re: pmspcv panic on boot on this box

Just to close this out, current -HEAD is fine on this box with pmspcv in GENERIC, and using that as my base. No nasty pmspcv messages. Copyright (c) 1992-2015 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of

Re: pmspcv panic on boot on this box

On 31/07/15 4:52 pm, Glen Barber wrote: On Fri, Jul 31, 2015 at 04:48:18AM +, mailingli...@debank.tv wrote: July 31 2015 4:21 PM, Glen Barber g...@freebsd.org wrote: On Fri, Jul 31, 2015 at 04:18:15AM +, Glen Barber wrote: On Thu, Jul 30, 2015 at 06:57:05PM -0500, Larry Rosenman

Re: pmspcv panic on boot on this box

On 1/08/15 4:26 pm, Glen Barber wrote: On Sat, Aug 01, 2015 at 04:24:26PM +1200, mailinglists wrote: On 31/07/15 4:52 pm, Glen Barber wrote: So, to be clear, you have 'device pmsdrv' removed from the kernel config, but the /boot/kernel/pmspcv.ko is still available to the system? I removed

Re: pmspcv panic on boot on this box

On Sat, Aug 01, 2015 at 04:34:14PM +1200, mailinglists wrote: On 1/08/15 4:26 pm, Glen Barber wrote: On Sat, Aug 01, 2015 at 04:24:26PM +1200, mailinglists wrote: On 31/07/15 4:52 pm, Glen Barber wrote: So, to be clear, you have 'device pmsdrv' removed from the kernel config, but the

Re: pmspcv panic on boot on this box

On Sat, Aug 01, 2015 at 04:24:26PM +1200, mailinglists wrote: On 31/07/15 4:52 pm, Glen Barber wrote: So, to be clear, you have 'device pmsdrv' removed from the kernel config, but the /boot/kernel/pmspcv.ko is still available to the system? I removed the module from /boot/kernel to be

Re: pmspcv panic on boot on this box

On Fri, Jul 31, 2015 at 05:27:22AM -0500, Larry Rosenman wrote: Ok, I made a GENERIC-NOPMS, without the device pmspcv, and adjusted my custom to include GENERIC-NOPMS. And we boot (I'm typing this from a ssh session to the box). Larry, thank you very much for testing this. Benno, for

Re: pmspcv panic on boot on this box

Please do pull it from GENERIC until this is fixed in HEAD and RELENG/10. On July 31, 2015 8:32:17 AM Glen Barber g...@freebsd.org wrote: On Fri, Jul 31, 2015 at 05:27:22AM -0500, Larry Rosenman wrote: Ok, I made a GENERIC-NOPMS, without the device pmspcv, and adjusted my custom to include

Re: pmspcv panic on boot on this box

I'm getting ready to commit to head and stable/10 now, and will also update releng/10.2 and restart the -RC2 builds with the change. Glen On Fri, Jul 31, 2015 at 09:41:39AM -0500, Larry Rosenman wrote: Please do pull it from GENERIC until this is fixed in HEAD and RELENG/10. On July 31,

Re: pmspcv panic on boot on this box

Try the following patch. There’s a fundamental misunderstanding of newbus that’s screwing things up… Also available at http://people.freebsd.org/~imp/patch-queue/pms The problem is that the first time through for ahd0 we’re setting cardMap[0] to 5. The second time through it is already 5, so

Re: pmspcv panic on boot on this box

Is this with or without Benno's patch? On July 31, 2015 12:24:11 PM Warner Losh i...@bsdimp.com wrote: Try the following patch. There’s a fundamental misunderstanding of newbus that’s screwing things up… Also available at http://people.freebsd.org/~imp/patch-queue/pms The problem is that

Re: pmspcv panic on boot on this box

It replaces it. Or you could just add the #if 0 bits to remove the atomic_cmpset_32 from the picture entirely. All this state saving should be done in attach anyway, so it is mis-located here… But the current patch will tell me if my theory of the crime is correct and offer a path forward...

Re: pmspcv panic on boot on this box

On 2015-07-31 15:44, Glen Barber wrote: On Fri, Jul 31, 2015 at 03:41:37PM -0500, Larry Rosenman wrote: We have a winner -- rebuilt with just this patch, and GENERIC with pmspcv, and we boot. Larry, thank you so much for your willingness to test this. It is greatly appreciated. Glen

Re: pmspcv panic on boot on this box

On Fri, Jul 31, 2015 at 03:41:37PM -0500, Larry Rosenman wrote: We have a winner -- rebuilt with just this patch, and GENERIC with pmspcv, and we boot. Larry, thank you so much for your willingness to test this. It is greatly appreciated. Glen pgpxqgmxk674m.pgp Description: PGP

Re: pmspcv panic on boot on this box

We have a winner -- rebuilt with just this patch, and GENERIC with pmspcv, and we boot. On Fri, Jul 31, 2015 at 12:03:27PM -0600, Warner Losh wrote: It replaces it. Or you could just add the #if 0 bits to remove the atomic_cmpset_32 from the picture entirely. All this state saving

Re: pmspcv panic on boot on this box

On Jul 31, 2015, at 3:32 PM, Glen Barber g...@freebsd.org wrote: On Fri, Jul 31, 2015 at 03:11:15PM -0600, Warner Losh wrote: On Jul 31, 2015, at 2:46 PM, Larry Rosenman l...@lerctr.org wrote: On 2015-07-31 15:44, Glen Barber wrote: On Fri, Jul 31, 2015 at 03:41:37PM -0500, Larry

Re: pmspcv panic on boot on this box

I'll try it when I get back to Austin tomorrow. On July 31, 2015 1:03:43 PM Warner Losh i...@bsdimp.com wrote: It replaces it. Or you could just add the #if 0 bits to remove the atomic_cmpset_32 from the picture entirely. All this state saving should be done in attach anyway, so it is

Re: pmspcv panic on boot on this box

On Jul 31, 2015, at 2:46 PM, Larry Rosenman l...@lerctr.org wrote: On 2015-07-31 15:44, Glen Barber wrote: On Fri, Jul 31, 2015 at 03:41:37PM -0500, Larry Rosenman wrote: We have a winner -- rebuilt with just this patch, and GENERIC with pmspcv, and we boot. Larry, thank you so much for

Re: pmspcv panic on boot on this box

On Fri, Jul 31, 2015 at 03:11:15PM -0600, Warner Losh wrote: On Jul 31, 2015, at 2:46 PM, Larry Rosenman l...@lerctr.org wrote: On 2015-07-31 15:44, Glen Barber wrote: On Fri, Jul 31, 2015 at 03:41:37PM -0500, Larry Rosenman wrote: We have a winner -- rebuilt with just this patch, and

Re: pmspcv panic on boot on this box

On Fri, Jul 31, 2015 at 01:33:32AM -0500, Larry Rosenman wrote: On 2015-07-30 23:21, Glen Barber wrote: On Fri, Jul 31, 2015 at 04:18:15AM +, Glen Barber wrote: On Thu, Jul 30, 2015 at 06:57:05PM -0500, Larry Rosenman wrote: On 2015-07-30 17:17, Glen Barber wrote: On Thu, Jul 30, 2015

Re: pmspcv panic on boot on this box

On 2015-07-30 23:21, Glen Barber wrote: On Fri, Jul 31, 2015 at 04:18:15AM +, Glen Barber wrote: On Thu, Jul 30, 2015 at 06:57:05PM -0500, Larry Rosenman wrote: On 2015-07-30 17:17, Glen Barber wrote: On Thu, Jul 30, 2015 at 03:20:46PM -0500, Larry Rosenman wrote: Kernel compiling --

Re: pmspcv panic on boot on this box

On Fri, Jul 31, 2015 at 06:50:16AM +, Glen Barber wrote: On Fri, Jul 31, 2015 at 01:33:32AM -0500, Larry Rosenman wrote: On 2015-07-30 23:21, Glen Barber wrote: On Fri, Jul 31, 2015 at 04:18:15AM +, Glen Barber wrote: On Thu, Jul 30, 2015 at 06:57:05PM -0500, Larry Rosenman wrote:

Re: pmspcv panic on boot on this box

On Thu, Jul 30, 2015 at 03:09:30PM -0500, Larry Rosenman wrote: $ sudo -s Password: # cd /usr/src # patch -p0 ~ler/pmspcv.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -- |Index: sys/dev/pms/freebsd/driver/common/lxutil.c

Re: pmspcv panic on boot on this box

On Thu, Jul 30, 2015 at 08:13:51PM +, Glen Barber wrote: On Thu, Jul 30, 2015 at 03:09:30PM -0500, Larry Rosenman wrote: $ sudo -s Password: # cd /usr/src # patch -p0 ~ler/pmspcv.diff Hmm... Looks like a unified diff to me... The text leading up to this was:

Re: pmspcv panic on boot on this box

Can you try the attached patch and let me know if it fixes the issue? Many thanks, Benno. pmspcv.diff Description: Binary data On Jul 30, 2015, at 11:55 AM, Benno Rice be...@freebsd.org wrote: Hi Larry, I’ve brought this to the attention of PMC Sierra and we’re pretty sure

Re: pmspcv panic on boot on this box

$ sudo -s Password: # cd /usr/src # patch -p0 ~ler/pmspcv.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -- |Index: sys/dev/pms/freebsd/driver/common/lxutil.c |=== |---

Re: pmspcv panic on boot on this box

On 2015-07-30 15:15, Glen Barber wrote: On Thu, Jul 30, 2015 at 08:13:51PM +, Glen Barber wrote: On Thu, Jul 30, 2015 at 03:09:30PM -0500, Larry Rosenman wrote: $ sudo -s Password: # cd /usr/src # patch -p0 ~ler/pmspcv.diff Hmm... Looks like a unified diff to me... The text leading

Re: pmspcv panic on boot on this box

On Thu, Jul 30, 2015 at 03:20:46PM -0500, Larry Rosenman wrote: Kernel compiling -- give mr a bit and I'll boot it and make sure it comes up. Larry, have you had any luck with this patch applied? If it resolves your issue, I want to make sure it is included in the 10.2-RC2 build. Thanks.

Re: pmspcv panic on boot on this box

On Fri, Jul 31, 2015 at 04:18:15AM +, Glen Barber wrote: On Thu, Jul 30, 2015 at 06:57:05PM -0500, Larry Rosenman wrote: On 2015-07-30 17:17, Glen Barber wrote: On Thu, Jul 30, 2015 at 03:20:46PM -0500, Larry Rosenman wrote: Kernel compiling -- give mr a bit and I'll boot it and make

Re: pmspcv panic on boot on this box

On Fri, Jul 31, 2015 at 04:48:18AM +, mailingli...@debank.tv wrote: July 31 2015 4:21 PM, Glen Barber g...@freebsd.org wrote: On Fri, Jul 31, 2015 at 04:18:15AM +, Glen Barber wrote: On Thu, Jul 30, 2015 at 06:57:05PM -0500, Larry Rosenman wrote: On 2015-07-30 17:17, Glen Barber

Re: pmspcv panic on boot on this box

On Thu, Jul 30, 2015 at 06:57:05PM -0500, Larry Rosenman wrote: On 2015-07-30 17:17, Glen Barber wrote: On Thu, Jul 30, 2015 at 03:20:46PM -0500, Larry Rosenman wrote: Kernel compiling -- give mr a bit and I'll boot it and make sure it comes up. Larry, have you had any luck with this

Re: pmspcv panic on boot on this box

July 31 2015 4:21 PM, Glen Barber g...@freebsd.org wrote: On Fri, Jul 31, 2015 at 04:18:15AM +, Glen Barber wrote: On Thu, Jul 30, 2015 at 06:57:05PM -0500, Larry Rosenman wrote: On 2015-07-30 17:17, Glen Barber wrote: On Thu, Jul 30, 2015 at 03:20:46PM -0500, Larry Rosenman wrote:

Re: pmspcv panic on boot on this box

On 2015-07-30 17:17, Glen Barber wrote: On Thu, Jul 30, 2015 at 03:20:46PM -0500, Larry Rosenman wrote: Kernel compiling -- give mr a bit and I'll boot it and make sure it comes up. Larry, have you had any luck with this patch applied? If it resolves your issue, I want to make sure it is

Re: pmspcv panic on boot on this box

Hi Larry, I’ve brought this to the attention of PMC Sierra and we’re pretty sure we’ve worked out what the problem is. I’m just waiting on their review of the fix I’ve suggested. Sorry this has caused you problems. Many apologies, Benno. On Jul 28, 2015, at 2:01 PM, Larry Rosenman

pmspcv panic on boot on this box

When I upgraded an approximately 3 month old -CURRENT system to yesterday, I got page not present panics, after a message about pmspcv not supporting my ahd(4) deviceid. I did NOT capture the panic, but adding nodevicepmspcv Allowed me to boot. Dmesg.boot from the WORKING system

Re: Early panic at boot: exclusive sleep mutex hdac1 (HDA driver mutex) ...

On Thu, Mar 19, 2015 at 07:23:19AM -0700, David Wolfskill wrote: As noted in a thread on -mobile yesterday, I'm replacing my long-serving Dell M4400 laptop with a newer model (M4800) -- you can see -mobile archives for additional details if you're interested. What prompted this note was: *

Early panic at boot: exclusive sleep mutex hdac1 (HDA driver mutex) ...

As noted in a thread on -mobile yesterday, I'm replacing my long-serving Dell M4400 laptop with a newer model (M4800) -- you can see -mobile archives for additional details if you're interested. What prompted this note was: * When I tried to boot head/i386, I got a rather quick panic (well

Re: panic on boot

-CURRENT FreeBSD 11.0-CURRENT #47 r269949: Wed Aug 13 14:18:28 EDT 2014 root@FBSD11:/usr/obj/usr/src/sys/MYKERNEL amd64 Trying to rebuild the system at r270973 I get a kernel panic on boot. I am able to boot into kernel.old at r269949 and the system is functional. Is anyone else seeing

Re: panic on boot

the system at r270973 I get a kernel panic on boot. I am able to boot into kernel.old at r269949 and the system is functional. Is anyone else seeing a panic on boot at a recent svn update? Could you please provide the traceback? I’m also seeing panics at boot on BBB (armv6) with a kernel

Re: panic on boot

root@FBSD11:/usr/obj/usr/src/sys/MYKERNEL amd64 Trying to rebuild the system at r270973 I get a kernel panic on boot. I am able to boot into kernel.old at r269949 and the system is functional. Is anyone else seeing a panic on boot at a recent svn update? Could you please provide

panic on boot

FreeBSD FBSD11 11.0-CURRENT FreeBSD 11.0-CURRENT #47 r269949: Wed Aug 13 14:18:28 EDT 2014 root@FBSD11:/usr/obj/usr/src/sys/MYKERNEL amd64 Trying to rebuild the system at r270973 I get a kernel panic on boot. I am able to boot into kernel.old at r269949 and the system is functional

Re: panic on boot

On Tue, Sep 2, 2014 at 9:47 AM, AN a...@neu.net wrote: FreeBSD FBSD11 11.0-CURRENT FreeBSD 11.0-CURRENT #47 r269949: Wed Aug 13 14:18:28 EDT 2014 root@FBSD11:/usr/obj/usr/src/sys/MYKERNEL amd64 Trying to rebuild the system at r270973 I get a kernel panic on boot. I am able to boot

panic on boot with fresh current

Hi, I just rebuilt a fresh current on my laptop. It panics on boot with: panic: witness_init: pending locks list is too small, increase WITNESS_PENDLIST I'm in a hurry right now so I can't gather much more info at the moment, but I thought I'd mention it. -- Joel

Re: panic on boot with fresh current

On 8/10/2013 6:24 AM, Joel Dahl wrote: Hi, I just rebuilt a fresh current on my laptop. It panics on boot with: panic: witness_init: pending locks list is too small, increase WITNESS_PENDLIST I'm in a hurry right now so I can't gather much more info at the moment, but I thought I'd

Re: panic on boot with fresh current

On 8/10/2013 11:44 AM, Bryan Drewery wrote: On 8/10/2013 6:24 AM, Joel Dahl wrote: panic: witness_init: pending locks list is too small, increase WITNESS_PENDLIST I also get this. The last stable revision for me was r254150 r254150 stable, r254171 panic. backtrace:

Re: panic on boot with fresh current

On Sat, Aug 10, 2013 at 12:15:35PM -0500, Bryan Drewery wrote: On 8/10/2013 11:44 AM, Bryan Drewery wrote: On 8/10/2013 6:24 AM, Joel Dahl wrote: panic: witness_init: pending locks list is too small, increase WITNESS_PENDLIST I also get this. The last stable revision for me was r254150

Re: panic on boot with fresh current

On Sat, Aug 10, 2013 at 08:44:07PM +0300, Konstantin Belousov wrote: On Sat, Aug 10, 2013 at 12:15:35PM -0500, Bryan Drewery wrote: On 8/10/2013 11:44 AM, Bryan Drewery wrote: On 8/10/2013 6:24 AM, Joel Dahl wrote: panic: witness_init: pending locks list is too small, increase

Re: panic on boot with fresh current

On Sat, Aug 10, 2013 at 08:45:47PM +0300, Konstantin Belousov wrote: On Sat, Aug 10, 2013 at 08:44:07PM +0300, Konstantin Belousov wrote: On Sat, Aug 10, 2013 at 12:15:35PM -0500, Bryan Drewery wrote: On 8/10/2013 11:44 AM, Bryan Drewery wrote: On 8/10/2013 6:24 AM, Joel Dahl wrote:

Re: panic on boot with fresh current

Konstantin Belousov kostik...@gmail.com writes: The right fix looks to be just what the panic message told, please try this: The patch managed to fix the crash here at least. ___ freebsd-current@freebsd.org mailing list

Re: panic on boot with fresh current

On 8/10/2013 12:45 PM, Konstantin Belousov wrote: On Sat, Aug 10, 2013 at 08:44:07PM +0300, Konstantin Belousov wrote: On Sat, Aug 10, 2013 at 12:15:35PM -0500, Bryan Drewery wrote: On 8/10/2013 11:44 AM, Bryan Drewery wrote: On 8/10/2013 6:24 AM, Joel Dahl wrote: panic: witness_init: pending

Re: panic on boot with fresh current

Hi, I can reproduce it locally, purely by booting an unchanged amd64 GENERIC. Are you testing it against an _unmodified_ GENERIC, on amd64? If it doesn't panic for you but it does panic for me (and I'll go and get the svn version once I reboot to the old kernel and test) then there may be a

Re: panic on boot with fresh current

On 8/10/2013 1:21 PM, Konstantin Belousov wrote: On Sat, Aug 10, 2013 at 08:45:47PM +0300, Konstantin Belousov wrote: On Sat, Aug 10, 2013 at 08:44:07PM +0300, Konstantin Belousov wrote: On Sat, Aug 10, 2013 at 12:15:35PM -0500, Bryan Drewery wrote: On 8/10/2013 11:44 AM, Bryan Drewery wrote:

Re: tws(4) kernel panic on boot

On Wed, May 22, 2013 at 11:08:50AM -0700, Andreas Turriff wrote: On 5/21/2013 9:25 AM, Andreas Turriff wrote: On 5/21/2013 5:33 AM, Konstantin Belousov wrote: On Mon, May 20, 2013 at 07:09:41PM -0700, Andreas Turriff wrote: On migrating one of my servers to -current, I discovered that the

Re: tws(4) kernel panic on boot

On 5/22/2013 11:23 PM, Konstantin Belousov wrote: On Wed, May 22, 2013 at 11:08:50AM -0700, Andreas Turriff wrote: On 5/21/2013 9:25 AM, Andreas Turriff wrote: On 5/21/2013 5:33 AM, Konstantin Belousov wrote: On Mon, May 20, 2013 at 07:09:41PM -0700, Andreas Turriff wrote: On migrating one

Re: tws(4) kernel panic on boot

On Wed, May 22, 2013 at 11:37:33PM -0700, Andreas Turriff wrote: I've been running that kernel all day, rebuilding userland (ports) on a 4-drive ZFS RAID-Z on that controller, and not seen a single crash, slowdown, hiccup or untoward log message. Thank you for the confirmation, I will commit

Re: tws(4) kernel panic on boot

On 5/21/2013 9:25 AM, Andreas Turriff wrote: On 5/21/2013 5:33 AM, Konstantin Belousov wrote: On Mon, May 20, 2013 at 07:09:41PM -0700, Andreas Turriff wrote: On migrating one of my servers to -current, I discovered that the tws driver panics on boot; I will follow up with a full backtrace

Re: tws(4) kernel panic on boot

On Mon, May 20, 2013 at 07:09:41PM -0700, Andreas Turriff wrote: On migrating one of my servers to -current, I discovered that the tws driver panics on boot; I will follow up with a full backtrace once I have a chance to extract it. In the meantime, there is a PR about a very similar error

Re: tws(4) kernel panic on boot

On 5/21/2013 5:33 AM, Konstantin Belousov wrote: On Mon, May 20, 2013 at 07:09:41PM -0700, Andreas Turriff wrote: On migrating one of my servers to -current, I discovered that the tws driver panics on boot; I will follow up with a full backtrace once I have a chance to extract it. In the

tws(4) kernel panic on boot

On migrating one of my servers to -current, I discovered that the tws driver panics on boot; I will follow up with a full backtrace once I have a chance to extract it. In the meantime, there is a PR about a very similar error in twa - 177020. Is it possible those are related, and the same sort

Revision 248649 - causes panic during boot

Hello: I have identified svn Revision 248649 as causing my system to panic during boot up. http://svnweb.freebsd.org/base?view=revisionrevision=248649 I have verified this by doing the following: svn up -r 248648 - buildkernel, installkernel, reboot = boot successful svn up -r 248649

Re: Revision 248649 - causes panic during boot

A stack trace would be helpful. Thanks, --Will. On Tue, Mar 26, 2013 at 4:27 PM, AN a...@neu.net wrote: Hello: I have identified svn Revision 248649 as causing my system to panic during boot up. http://svnweb.freebsd.org/**base?view=revisionrevision=**248649http://svnweb.freebsd.org/base

Panic during boot with fresh CURRENT (r248090)

Hi, Just updated to the latest CURRENT. Got this during boot: (sorry for the large image) http://mirror.vnode.se/upload/r248090_panic.jpg -- Joel ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current

Re: Panic during boot with fresh CURRENT (r248090)

On Sat, Mar 09, 2013 at 10:39:20AM +0100, Joel Dahl wrote: Hi, Just updated to the latest CURRENT. Got this during boot: (sorry for the large image) http://mirror.vnode.se/upload/r248090_panic.jpg This is fixed with r248093. -- Joel ___

Re: Panic on boot after svn update

On Sat, Jul 28, 2012 at 10:15 PM, Greg 'groggy' Lehey g...@freebsd.org wrote: On Sunday, 29 July 2012 at 0:53:55 -0400, David J. Weller-Fahy wrote: So, I recently updated and encountered a panic on boot which is reproducible, and wanted to see if anyone's encountered this before I file a PR

Re: Panic on boot after svn update

* Garrett Cooper yaneg...@gmail.com [2012-07-29 02:34 -0400]: See this thread: http://lists.freebsd.org/pipermail/freebsd-current/2012-July/035593.html Huh - apparently my SA was not at its highest yesterday... Thanks for the heads up! -- dave [ please don't CC me ] pgp9V1FHEuPMz.pgp

Panic on boot after svn update

So, I recently updated and encountered a panic on boot which is reproducible, and wanted to see if anyone's encountered this before I file a PR. I found a problem in (I think) recent changes to the e1000 driver. I'm running FreeBSD 10-CURRENT as a VirtualBox guest. #v+ FreeBSD fork-pooh 10.0

Re: Panic on boot after svn update

On Sunday, 29 July 2012 at 0:53:55 -0400, David J. Weller-Fahy wrote: So, I recently updated and encountered a panic on boot which is reproducible, and wanted to see if anyone's encountered this before I file a PR. I found a problem in (I think) recent changes to the e1000 driver. I'm

<    1   2   3   4   >