I remember seeing this panic many months back. I had fixed this in our
Freebsd source base.
Here is the scenario:
vrele() {
if (vp->v_usecount == 1) {
vp->usecount--;
if (VSHOULDFREE(vp))
vfree(vp);
vn_lock(vp, LK_EXCLUS
On 10 Sep, Don Lewis wrote:
> It looks like the call to vrele() from vn_close() is executing the
> following code:
>
> if (vp->v_usecount == 1) {
> vp->v_usecount--;
> /*
> * We must call VOP_INACTIVE with the node locked.
>
I've gotten a couple "lockmgr: locking against myself" panics today and
it seems to be somewhat reproduceable. I had the serial console hooked
up for the last one, so I was able to get a stack trace:
panic: lockmgr: locking against myself
Debugger("panic")
Stopped at Debugger+0x45: xchgl
On 10 Sep, Don Lewis wrote:
> On 10 Sep, Nate Lawson wrote:
>
>> I'm not sure why fdcheckstd() and setugidsafety() couldn't both happen
>> before grabbing the proc lock. Dropping locks in the middle or
>> pre-allocating should always be a last resort.
>
> That is ok as long as there aren't othe
walt <[EMAIL PROTECTED]> writes:
> uudecode compiles again, but now I'm getting this making world:
>
> ===> share/tabset
> uudecode < /usr/src/share/tabset/3101.uu
> uudecode < /usr/src/share/tabset/9837.uu
> uudecode: stdin: 9837: character out of range: [33-96]
> *** Error code 1
>
> Stop in /
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
uudecode compiles again, but now I'm getting this making world:
===> share/tabset
uudecode < /usr/src/share/tabset/3101.uu
uudecode < /usr/src/share/tabset/9837.uu
uudecode: stdin: 9837: character out of range: [33-96]
*** Error code 1
Stop in /usr/src/share/tabset.
Dunno whether the problem is
On 10 Sep, Nate Lawson wrote:
> I'm not sure why fdcheckstd() and setugidsafety() couldn't both happen
> before grabbing the proc lock. Dropping locks in the middle or
> pre-allocating should always be a last resort.
That is ok as long as there aren't other threads that can mess things up
after
On Tue, 10 Sep 2002, Don Lewis wrote:
> On 7 Sep, Garrett Wollman wrote:
> > I just noted the following:
> >
> > ../../../vm/uma_core.c:1332: could sleep with "process lock" locked from
>../../../kern/kern_exec.c:368
> > lock order reversal
> > 1st 0xc438e6a8 process lock (process lock) @ ../.
On 2002-09-11 00:04, Riccardo Torrini <[EMAIL PROTECTED]> wrote:
> Now last doubt: after next upgrade to post-gcc_3.2 is a complete port
> rebuild necessary because c++ ports stop working or not?
Yes.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body o
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On 7 Sep, Garrett Wollman wrote:
> I just noted the following:
>
> ../../../vm/uma_core.c:1332: could sleep with "process lock" locked from
>../../../kern/kern_exec.c:368
> lock order reversal
> 1st 0xc438e6a8 process lock (process lock) @ ../../../kern/kern_exec.c:368
> 2nd 0xc0413d20 fileli
On Tue, Sep 10, 2002 at 05:09:55PM -0700, walt wrote:
> cc -O -pipe -mcpu=pentiumpro -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings
>-Wswitch
> -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/usr.bin/
cc -O -pipe -mcpu=pentiumpro -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings
-Wswitch
-Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/usr.bin/uudecode/uudecode.c
cc1: warnings being treated as errors
/us
===> usr.bin/uudecode
/usr/obj/usr/src/i386/usr/src/usr.bin/uudecode created for
/usr/src/usr.bin/uudecode
rm -f .depend
mkdep -f .depend -a-D__FBSDID=__RCSID
/usr/src/usr.bin/uudecode/uudecode.c
echo uudecode: /usr/lib/libc.a >> .depend
cc -O -pipe -Wall -Wno-format-y2k -W -Wstrict-prototy
On 9 Sep, Don Lewis wrote:
> nfs_link() contains the following code:
>
> /*
> * Push all writes to the server, so that the attribute cache
> * doesn't get "out of sync" with the server.
> * XXX There should be a better way!
> */
> VOP_FSYNC(vp,
On 9 Sep, Don Lewis wrote:
> On 9 Sep, Robert Watson wrote:
>
>> What I'd actually like to do is lock vp on going in to the VOP. I need to
>> grab the lock in the link() code anyway to do the MAC check. UFS and
>> others all immediately lock the vnode on entry anyway...
>
> Here's a patch to
On 08-Sep-2002 (19:54:17/GMT) Riccardo Torrini wrote:
>> There have been at least two gcc upgrades since then. I believe
>> the easiest way to upgrade to today's -current would be to install
>> a fairly recent snapshot ... instead of trying to debug ...
> I have tryed with a middle version (1 j
On Tuesday 10 September 2002 10:11 am, Kris Kennaway wrote:
> On Tue, Sep 10, 2002 at 08:21:31AM -0800, Beech Rintoul wrote:
> > I was trying to update linux_base and got the following build failure:
>
> Known problem; see the list archives for a patch.
>
> Kris
Already applied those patches, sti
On Wed, 11 Sep 2002, Bruce Evans wrote:
> On Tue, 10 Sep 2002, Robert Watson wrote:
>
> > ... Also, last time I tried to use the ddb
> > show lockedvnods command, I got the problem attached below due to locking
> > issues, which makes it a lot harder to debug locking problems...
> >
> > Robert
On Tue, 10 Sep 2002, Robert Watson wrote:
> ... Also, last time I tried to use the ddb
> show lockedvnods command, I got the problem attached below due to locking
> issues, which makes it a lot harder to debug locking problems...
>
> Robert N M Watson FreeBSD Core Team, TrustedBSD Pr
On 10 Sep, Robert Watson wrote:
> On Tue, 10 Sep 2002, Don Lewis wrote:
>> I'm mostly worried about the vnode being recycled as something else
>> after the vput() or vrele() call. I think a better approach would be to
>> add the assertion checks to vput() and vrele(), which would mean that we
>>
On Tue, 10 Sep 2002, Don Lewis wrote:
> On 11 Sep, Bruce Evans wrote:
> > On Tue, 10 Sep 2002, Don Lewis wrote:
> >
> > I have just one thing to add to Robert's reply.
> >
> >> BTW, is it safe to call ASSERT_VOP_UNLOCKED() in the SMP case after the
> >> reference has been dropped with vput() or
On Tue, 10 Sep 2002, Mikhail Teterin wrote:
> Regardless of whether the xl driver is linked into the kernel or
> loaded as a module, the machine freezes shortly after ifconfig-ing
> the card. Sunday's -current. Complete freeeze -- can not go into
> debugger...
>
> More information available upon
On 11 Sep, Bruce Evans wrote:
> On Tue, 10 Sep 2002, Don Lewis wrote:
>
> I have just one thing to add to Robert's reply.
>
>> BTW, is it safe to call ASSERT_VOP_UNLOCKED() in the SMP case after the
>> reference has been dropped with vput() or vrele()?
>
> I think it is. It has some internal l
On Wed, Sep 11, 2002 at 12:22:04AM +0900, Mitsuru IWASAKI wrote:
> > Do you think that there is a change that this is in the direction of DPMS,
> > or is that very unliky? I tried to find the spec for DPMS but it seems to
> > be a closed on (at least to non-members).
>
> It seems that old laptops
I've seen the scrn_timer() one too:
Expensive timeout(9) function: 0xc049b3f0(0xc0657200) 0.003659743
c049b3f0 t scrn_timer
as well as uma_timeout().
Expensive timeout(9) function: 0xc047c6b0(0) 0.002146136
c047c6b0 t uma_timeout
Bill
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "u
> Yes. we are aware of the work and we are pleased that it is hapenning, but
> few of us have even SEEN any bluetooth stuff yet..
> certainly in the US it's not yet being marketted a lot.
Fry's Electronics in the SF bayarea has a bunch of bluetooth
gadgets. Go to www.outpost.com and search for
Am Di, 2002-09-10 um 19.48 schrieb Julian Elischer:
>
>
>
> On Tue, 10 Sep 2002, Chris Dillon wrote:
>
> > On Mon, 9 Sep 2002, Maksim Yevmenkin wrote:
> >
> > > I still would like to hear from people. I'm extremely surprised that
> > > FreeBSD community seems not interested in this at all. I
Julian,
> On Tue, 10 Sep 2002, Chris Dillon wrote:
>
> > On Mon, 9 Sep 2002, Maksim Yevmenkin wrote:
> >
> > > I still would like to hear from people. I'm extremely surprised that
> > > FreeBSD community seems not interested in this at all. I got very
> > > few replies from few people (Julian E
subscribe freebsd-current [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, Sep 10, 2002 at 08:21:31AM -0800, Beech Rintoul wrote:
> I was trying to update linux_base and got the following build failure:
Known problem; see the list archives for a patch.
Kris
msg42849/pgp0.pgp
Description: PGP signature
I got this on the bento cluster this morning (-current from about 2 days ago):
/x: bad dir ino 3180135 at offset 0: mangled entry
panic: ufs_dirbad: bad dir
Debugger("panic")
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
db> trace
Debugger(c03f45bc,c0473f80,c040e087,ceac4974,
On Tue, 10 Sep 2002, Chris Dillon wrote:
> On Mon, 9 Sep 2002, Maksim Yevmenkin wrote:
>
> > I still would like to hear from people. I'm extremely surprised that
> > FreeBSD community seems not interested in this at all. I got very
> > few replies from few people (Julian Elischer, Terry Lambe
On 10-Sep-2002 M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Chris Dillon <[EMAIL PROTECTED]> writes:
>: On Mon, 9 Sep 2002, Maksim Yevmenkin wrote:
>:
>: > I still would like to hear from people. I'm extremely surprised that
>: > FreeBSD community seems not interested in
On Tue, 10 Sep 2002, Dag-Erling Smorgrav wrote:
:cc1: warnings being treated as errors
:/local0/scratch/des/src/sys/dev/cardbus/cardbus.c: In function `cardbus_driver_added':
:/local0/scratch/des/src/sys/dev/cardbus/cardbus.c:319: warning: unused variable
:`cardattached'
:*** Error code 1
I just
In message: <[EMAIL PROTECTED]>
Chris Dillon <[EMAIL PROTECTED]> writes:
: On Mon, 9 Sep 2002, Maksim Yevmenkin wrote:
:
: > I still would like to hear from people. I'm extremely surprised that
: > FreeBSD community seems not interested in this at all. I got very
: > few replies from
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
FUJIMOTO Kou wrote:
>
> Poul-Henning Kamp wrote:
> >
> > In message <[EMAIL PROTECTED]>, Maksim Yevmenkin writes:
> >
> > >I still would like to hear from people. I'm extremely
> > >surprised that FreeBSD community seems not interested in
> > >this at all. I got very few replies from few people
>
I was trying to update linux_base and got the following build failure:
cc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../build -I../misc -I/usr/local/include
-I/usr/local/include -O -pipe -D_GNU_SOURCE -Wall -Wpointer-arith
-Wstrict-prototypes -Wmissing-prototypes -Wno-char-subscripts -c cpio.c
-fPIC
On Mon, 9 Sep 2002, Maksim Yevmenkin wrote:
> I still would like to hear from people. I'm extremely surprised that
> FreeBSD community seems not interested in this at all. I got very
> few replies from few people (Julian Elischer, Terry Lambert -
> thanks!) and that's it.
I'm very interested, as
I just bought an new battery and that combined with the fact that
I've seen so many recent emails about acpi that I decided to check my
laptop. I've never really been able to take advantage of acpi with it
and may never be able to, but previously I was able to do an acpidump
and now I get:
/root
On Wed, Sep 11, 2002 at 12:22:04AM +0900, Mitsuru IWASAKI wrote:
> It seems that old laptops don't have VGA specific ACPI objects, so
> many people will be happy if we can implement non-ACPI VGA driver w/
> ATI chips hack.
> BTW, have you checked for XFree86 code? Hopefully we might find
> some h
> On Thu, Aug 29, 2002 at 11:11:15PM +0200, Mark Santcroos wrote:
> > I worked around this by making the driver a child of pci instead of a
> > child of acpi. (Which is even more correct too)
>
> My driver is a child of acpi again and at this point it always seems to be
> called at resume too. I
On Tue, 10 Sep 2002, Don Lewis wrote:
I have just one thing to add to Robert's reply.
> BTW, is it safe to call ASSERT_VOP_UNLOCKED() in the SMP case after the
> reference has been dropped with vput() or vrele()?
I think it is. It has some internal locking (v_interlock at least), and
only asse
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On Tue, 10 Sep 2002, Don Lewis wrote:
> >>> > The changes are obviously just cleanups for leaf file systems, but I
> >>> > wonder why everything wasn't always locked at the top. Could it have
> >>> > been because locking all the way down is harmful?
>
> >> I think this is because some places a
On Thu, Aug 29, 2002 at 11:11:15PM +0200, Mark Santcroos wrote:
> I worked around this by making the driver a child of pci instead of a
> child of acpi. (Which is even more correct too)
My driver is a child of acpi again and at this point it always seems to be
called at resume too. I don't know w
Regardless of whether the xl driver is linked into the kernel or
loaded as a module, the machine freezes shortly after ifconfig-ing
the card. Sunday's -current. Complete freeeze -- can not go into
debugger...
More information available upon request...
-mi
To Unsubscribe: send mail to [E
On 10 Sep, Terry Lambert wrote:
> Bruce Evans wrote:
>> The changes are obviously just cleanups for leaf file systems, but I
>> wonder why everything wasn't always locked at the top. Could it have
>> been because locking all the way down is harmful?
>
> For a stacked local media FS, you can end
On 10 Sep, Don Lewis wrote:
> On 10 Sep, Bruce Evans wrote:
>> On Tue, 10 Sep 2002, Don Lewis wrote:
>>
>>> On 10 Sep, Bruce Evans wrote:
>
>>> > The changes are obviously just cleanups for leaf file systems, but I
>>> > wonder why everything wasn't always locked at the top. Could it have
>>> >
Hi Martin:
On Tue, 10 Sep 2002, Martin Blapp wrote:
> > and Martins patch:
> > This one works standalone and with 2 and 3 above. It seems to have
> > increase ftp transfer rates too from 8600Kbytes/sec to 10577Kbytes/sec.
>
> Cool.
Seems to depend on which notebook the card is in. Wit
On Tue, 10 Sep 2002, Martin Blapp wrote:
Hi,
> > 1) dc driver uses wrong case to read MAC from eeprom.
> >
> > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/35482
> >
> > This one seems to break data sending/receiving as the only thing that
> > works is pinging and that's only on the alias/sec
On 10 Sep 2002, Sid Carter wrote:
> > On Mon, 9 Sep 2002 12:09:05 -1000 (HST), Vincent Poy
><[EMAIL PROTECTED]> said:
>
> Vincent> On Mon, 9 Sep 2002, Julian Elischer wrote:
> >> On Mon, 9 Sep 2002, Vincent Poy wrote:
> >> > > Timecounters tick every 10.000 msec
> >> > >
Bruce Evans wrote:
> The changes are obviously just cleanups for leaf file systems, but I
> wonder why everything wasn't always locked at the top. Could it have
> been because locking all the way down is harmful?
For a stacked local media FS, you can end up with a deadlock, if
a lower vnode is e
On 10 Sep, Bruce Evans wrote:
> On Tue, 10 Sep 2002, Don Lewis wrote:
>
>> On 10 Sep, Bruce Evans wrote:
>> > The changes are obviously just cleanups for leaf file systems, but I
>> > wonder why everything wasn't always locked at the top. Could it have
>> > been because locking all the way down
On Tue, 10 Sep 2002, Don Lewis wrote:
> On 10 Sep, Bruce Evans wrote:
> >>The locking changes in union_link() need a thorough review,
> >> though the light testing of that I performed didn't turn up any
> >> glaring problems.
> >
> > The changes are obviously just cleanups for
> On Mon, 9 Sep 2002 14:37:45 -0700 (PDT), Julian Elischer <[EMAIL PROTECTED]>
>said:
Julian> On Mon, 9 Sep 2002, Vincent Poy wrote:
>> > I compiled the kernel last nite and I haven't been able to boot into the
>> > system with that kernel. This is where the kernel hangs
>>
> On Mon, 9 Sep 2002 12:09:05 -1000 (HST), Vincent Poy <[EMAIL PROTECTED]>
>said:
Vincent> On Mon, 9 Sep 2002, Julian Elischer wrote:
>> On Mon, 9 Sep 2002, Vincent Poy wrote:
>> > > Timecounters tick every 10.000 msec
>> > > ---
>>
>>
On 10 Sep, Bruce Evans wrote:
>> The locking changes in union_link() need a thorough review,
>> though the light testing of that I performed didn't turn up any
>> glaring problems.
>
> The changes are obviously just cleanups for leaf file systems, but I
> wonder why everythin
> The locking changes in union_link() need a thorough review,
> though the light testing of that I performed didn't turn up any
> glaring problems.
The changes are obviously just cleanups for leaf file systems, but I
wonder why everything wasn't always locked at the top. Co
On Thu, 29 Aug 2002 12:05:25 +0200,
Alexander Leidinger <[EMAIL PROTECTED]> said:
Alexander> After booting the system up xdm didn't showed up and there was no
Alexander> possibility to login on the console, so I breaked into ddb and send a
Alexander> "kill 1" to xdm. Nothing happened so I again
Hi,
> 1) dc driver uses wrong case to read MAC from eeprom.
>
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/35482
>
> This one seems to break data sending/receiving as the only thing that
> works is pinging and that's only on the alias/secondary IP and not the
> primary IP network which is c
Hi,
> and Martins patch:
> This one works standalone and with 2 and 3 above. It seems to have
> increase ftp transfer rates too from 8600Kbytes/sec to 10577Kbytes/sec.
Cool.
> Ofcourse, for some odd reason, if the ftp was done from a Windows XP Pro
> machine, it's only 6722KBytes/sec.
Hmm. T
unsubscribe
--
katty
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Poul-Henning Kamp wrote:
>
> In message <[EMAIL PROTECTED]>, Maksim Yevmenkin writes:
>
> >I still would like to hear from people. I'm extremely
> >surprised that FreeBSD community seems not interested in
> >this at all. I got very few replies from few people
> >(Julian Elischer, Terry Lambert -
66 matches
Mail list logo
