Am 24.09.2018 um 14:50 schrieb Andrey V. Elsukov:
On 24.09.2018 11:31, Harry Schmalzbauer wrote:
Hello,
unfortunately this is far beyond my scope and I forgot to report in time.
If this is begnin, feel free to ignore, but in any case I'd appreciate
any comments.
Hi,
I posted a review targete
On 24.09.2018 11:31, Harry Schmalzbauer wrote:
> Hello,
>
> unfortunately this is far beyond my scope and I forgot to report in time.
> If this is begnin, feel free to ignore, but in any case I'd appreciate
> any comments.
Hi,
I posted a review targeted to fix this problem:
htt
Hello,
unfortunately this is far beyond my scope and I forgot to report in time.
If this is begnin, feel free to ignore, but in any case I'd appreciate
any comments.
uma_zalloc_arg: zone "1024" with the following non-sleepable locks held:
exclusive sleep mutex xforms_list (I
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:
Rear Pink0
hdaa1: 26 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA
hdaa1: 27 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA
hdaa1: 30 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA
Kernel page fault with the foll
On Jul 2, 2012, at 5:43 AM, Anton Shterenlikht wrote:
>>
>> I think you're kernel is seriously screwed-up. Do you have any
>> non-standard (for ia64) kernel configuration options?
>
> I didn't think so.
> The latest was this:
*snip*
Looks fine indeed. I have pretty much the same, except for th
> > 23080512, 24362752,
> > 25644992, 26927232, 28209472, 29491712, 30773952, 32056192, 8432
> > # mount /dev/da2p2 /mnt
> > # cd /mnt
> > # dump 0aLuf - / | restore -rf -
> >
> > results in this panic:
> >
> > KDB: stack backtrace:
> &
mnt
> # cd /mnt
> # dump 0aLuf - / | restore -rf -
>
> results in this panic:
>
> KDB: stack backtrace:
> getenv with the following non-sleepable locks held:
> exclusive sleep mutex vnode interlock (vnode interlock) r = 0
> (0xe0001238f6e8) locked @ /usr/src/sys/ker
the following non-sleepable locks held:
exclusive sleep mutex vnode interlock (vnode interlock) r = 0
(0xe0001238f6e8) locked @ /usr/src/sys/kern/vfs_hash.c:79
KDB: stack backtrace:
getenv with the following non-sleepable locks held:
exclusive sleep mutex vnode interlock (vnode interlock) r = 0
-sleepable locks held:
exclusive sleep mutex vnode interlock (vnode interlock) r = 0
(0xe000116c78c0) locked @ /usr/src/sys/ufs/ffs/ffs_snapshot.c:2257
KDB: stack backtrace:
getenv with the following non-sleepable locks held:
exclusive sleep mutex vnode interlock (vnode interlock) r = 0
...
Kernel page fault with the following non-sleepable locks held:
exclusive sleep mutex ATA state lock (ATA state lock) r = 0
(0xff0002a922c0) locked @ /usr/src/sys/dev/ata/ata-all.c:503
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
_witness_debugger() at
; > I updated to current yesterday and got the following 'witness_warn'
> > > panic upon executing 'reboot':
> > >
> > > suspending ithread with the following locks held:
> > > exclusive sleep mutex mskc0 (network driver) r = 0 (0xc32c3690)
x27;
> > panic upon executing 'reboot':
> >
> > suspending ithread with the following locks held:
> > exclusive sleep mutex mskc0 (network driver) r = 0 (0xc32c3690) locked @
> > /usr/src/sys/dev/msk/if_msk.c:3589
> > panic: witness_warn
> > cpu
ing 'reboot':
>>
>> suspending ithread with the following locks held:
>> exclusive sleep mutex mskc0 (network driver) r = 0 (0xc32c3690) locked @
>> /usr/src/sys/dev/msk/if_msk.c:3589
>> panic: witness_warn
>
> It seems msk(4) didn't honor IFF_D
On Mon, May 03, 2010 at 07:01:56AM -0700, Mark Atkinson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I updated to current yesterday and got the following 'witness_warn'
> panic upon executing 'reboot':
>
> suspending ithread with the foll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I updated to current yesterday and got the following 'witness_warn'
panic upon executing 'reboot':
suspending ithread with the following locks held:
exclusive sleep mutex mskc0 (network driver) r = 0 (0xc32c3690) locked @
On Wed, Dec 03, 2003 at 10:29:19AM -0700, Scott Long wrote:
> Clive Lin wrote:
> >Hi,
> >
> >Here comes more helpful ServeRAID related warnings:
> >
> >Bad malloc flags: 0
> >Stack backtrace:
> >malloc() of "16" with the following non-s
Clive Lin wrote:
Hi,
Here comes more helpful ServeRAID related warnings:
Bad malloc flags: 0
Stack backtrace:
malloc() of "16" with the following non-sleepable locks held:
exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @
/usr/src/sys/geom/geom_io.c:355
Bad uma_zalloc flag
Hi,
Here comes more helpful ServeRAID related warnings:
Bad malloc flags: 0
Stack backtrace:
malloc() of "16" with the following non-sleepable locks held:
exclusive sleep mutex g_xdown r = 0 (0xe1f31cbc) locked @
/usr/src/sys/geom/geom_io.c:355
Bad uma_zalloc flags: 0
Stack
This morning's cvsup.
checking stopevent 2 with the following non-sleepable locks held:
exclusive sleep mutex sigacts r = 0 (0xc6b8baa8) locked @
/space1s1/freebsd/FreeBSD/branches/-current/src/sys/kern/subr_trap.c:260
Eric
___
[EMAIL PROT
lowing non-sleepable locks held:
exclusive sleep mutex sigacts r = 0 (0xc1cb8aa8) locked @
/usr/src/sys/kern/kern_synch.c:293
Debugger("witness_warn")
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
db> trace
Debugger(c0675228,c93f4b88,1,c93f4b84,0) at Debugger+0x54
John,
I believe you've already seen the assertion fire, so this
may be redundant info:
kernel: checking stopevent 2 with the following non-sleepable \
locks held:
kernel: exclusive sleep mutex sigacts r = 0 (0xc4a25aa8) locked \
locked @ /usr/src/sys/kern/subr_trap.c:260
Note the assert
On Thu, Oct 30, 2003 at 10:18:43AM -0800, Kris Kennaway wrote:
> One of the amd64 machines died with the following. The kernel is a
> few weeks old, so this might already be fixed.
>
> Kris
>
> malloc() of "64" with the following non-sleepable locks held:
> exclu
gt; malloc() of "16" with the following non-sleepable locks held:
> > > exclusive sleep mutex g_xdown r = 0 (0xe044eca8) locked @
> > > /usr/src/sys/geom/geom_io.c:351
> > > malloc() of "16" with the following non-sleepable locks held:
> > >
On Thu, 30 Oct 2003 10:18:43 -0800
Kris Kennaway <[EMAIL PROTECTED]> wrote:
> One of the amd64 machines died with the following. The kernel is a
> few weeks old, so this might already be fixed.
>
> Kris
>
> malloc() of "64" with the following non-sleepable l
On 2003/10/30 00:16:47, Clive Lin wrote:
> On Sat, Oct 04, 2003 at 02:00:33AM +0800, Clive Lin wrote:
> > Hi,
> >
> > I've seen lots of messages on rescent -CURRENT
> >
> > malloc() of "16" with the following non-sleepable locks held:
>
One of the amd64 machines died with the following. The kernel is a
few weeks old, so this might already be fixed.
Kris
malloc() of "64" with the following non-sleepable locks held:
exclusive sleep mutex mntvnode r = 0 (0x80758220) locked @
/a/asami/portbuild/amd64/src-clie
On Sat, Oct 04, 2003 at 02:00:33AM +0800, Clive Lin wrote:
> Hi,
>
> I've seen lots of messages on rescent -CURRENT
>
> malloc() of "16" with the following non-sleepable locks held:
> exclusive sleep mutex g_xdown r = 0 (0xe044eca8) locked @
> /usr/src/
e following non-sleepable locks held:
> exclusive sleep mutex ifnet r = 0 (0xc07cc940) locked @ net/if.c:459
> Debugger("witness_warn")
> Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
> db> trace
> Debugger(c070f058,c0c21ce8,1,c07396e3,c0778ec0) at Debugger+0
Updated to HEAD, booted with WITNESS enabled, and the boot dies here:
ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to accept,
logging unlimited
malloc() of "16" with the following non-sleepable locks held:
exclusive sleep mutex ifnet r = 0 (0xc07cc940) lo
Hello Paolo,
See below.
On Oct 20, Paolo Pisati wrote:
> from my dmesg:
> [snip]
> exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc2d34540) locked @
> /usr/src/sys/dev/sound/pcm/mixer.c:322
Could you try deleting the snd_mtxlock and snd_mtxunlock in
mixer_hwv
On Mon, Oct 20, 2003 at 10:37:00AM -0700, Kris Kennaway wrote:
> Unfortunately none of the sound developers have been interested in
> looking at the locking problems in the code.
=(
> > acquiring duplicate lock of same type: "pcm channel"
> > 1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/sound
On Mon, Oct 20, 2003 at 07:15:19PM +0200, Paolo Pisati wrote:
>
> from my dmesg:
> [snip]
> pcm0: port 0xb800-0xb8ff irq 5 at device 1.0 on pci2
> pcm0: failed to enable memory mapping!
> pcm0:
> malloc() of "64" with the following non-sleepable locks held:
>
from my dmesg:
[snip]
pcm0: port 0xb800-0xb8ff irq 5 at device 1.0 on pci2
pcm0: failed to enable memory mapping!
pcm0:
malloc() of "64" with the following non-sleepable locks held:
exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc2d34540) locked @
/usr/src/sys/dev/sound/pcm/m
Hi,
I've seen lots of messages on rescent -CURRENT
malloc() of "16" with the following non-sleepable locks held:
exclusive sleep mutex g_xdown r = 0 (0xe044eca8) locked @
/usr/src/sys/geom/geom_io.c:351
malloc() of "16" with the following non-sleepable locks he
I'm getting the following when I try and netboot the alpha package
machines (note also the missing space in the diagnostic message):
malloc() of "4096" with the following non-sleepablelocks held:
exclusive sleep mutex ifnet r = 0 (0xfc6dca90) locked @
/a/asami/portbuild/a
have a more recent one, but
it didnt help.
The kernel dumps an error like this :
Sleeping on "stopevent" with the following non-sleepablelocks held:
exclusive sleep mutex sigacts r = 0 (0xc684caa8) locked @
kern/subr_trap.c:250
The SAPDB port can be found ( as a beta preview
27;t seen any
>> >messages about this, so I figured I'd ask here.
>> >
>> >Message:
>> >Mar 11 17:33:30 lorne kernel: malloc() of "64" with the following
>> >non-sleepablelocks held:
>> >Mar 11 17:33:30 lorne kernel: exclusive sle
Terry Lambert wrote:
> Derek Tattersall wrote:
> > Mar 10 20:55:09 lorne kernel: malloc() of "64" with the following
> > non-sleepablelocks held:
>
> The only malloc of 64 bytes in this code path should be the
> transient template structure malloc (FWIW).
>
> John: did you look at my patch for t
Derek Tattersall wrote:
> Mar 10 20:55:09 lorne kernel: malloc() of "64" with the following non-sleepablelocks
> held:
The only malloc of 64 bytes in this code path should be the
transient template structure malloc (FWIW).
John: did you look at my patch for the locking?
-- Terry
To Unsubscribe
* Jonathan Lemon ([EMAIL PROTECTED]) [030312 01:12]:
> Date: Tue, 11 Mar 2003 18:59:15 -0600 (CST)
> From: Jonathan Lemon <[EMAIL PROTECTED]>
> Message-Id: <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: Re: exclusive sleep mutex netisr...
>
) of "64" with the following
>non-sleepablelocks held:
>Mar 11 17:33:30 lorne kernel: exclusive sleep mutex netisr lock r = 0
>(0xc0579160) locked @ /usr/src/sys/net/netisr.c:215
>
>Can anybody supply me a clue as to what's going on here?
It can be ignored for now, t
lloc() of "64" with the following
> non-sleepablelocks held:
> Mar 11 17:33:30 lorne kernel: exclusive sleep mutex netisr lock r = 0
> (0xc0579160) locked @ /usr/src/sys/net/netisr.c:215
>
> Can anybody supply me a clue as to what's going on here?
Problem with Jonathan
elocks held:
Mar 11 17:33:30 lorne kernel: exclusive sleep mutex netisr lock r = 0
(0xc0579160) locked @ /usr/src/sys/net/netisr.c:215
Can anybody supply me a clue as to what's going on here?
--
Derek Tattersall[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAI
44 matches
Mail list logo
