On Thu, Jun 02, 2005 at 04:27:30PM -0700, Derek Kuli?ski wrote:
> Hello Kris,
>
> Thursday, June 2, 2005, 11:06:54 AM, you wrote:
>
> >> > in 1.141 of ffs_softdep.c you added a call to backtrace() if bp->b_vp
> >> > == NULL..you removed it in current in 1.166, but some people are
> >> > seeing it
Hello Kris,
Thursday, June 2, 2005, 11:06:54 AM, you wrote:
>> > in 1.141 of ffs_softdep.c you added a call to backtrace() if bp->b_vp
>> > == NULL..you removed it in current in 1.166, but some people are
>> > seeing it trigger on 5.x
>> So it's harmless?
> I don't know, but I presume the debuggi
On Thu, Jun 02, 2005 at 09:11:23AM -0700, Derek Kuli?ski wrote:
> Hello Kris,
>
> Thursday, June 2, 2005, 12:37:41 AM, you wrote:
>
> > It looks like debugging code (it's been removed in -current).
>
> > Jeff:
>
> > in 1.141 of ffs_softdep.c you added a call to backtrace() if bp->b_vp
> > == NU
Hello Kris,
Thursday, June 2, 2005, 12:37:41 AM, you wrote:
> It looks like debugging code (it's been removed in -current).
> Jeff:
> in 1.141 of ffs_softdep.c you added a call to backtrace() if bp->b_vp
> == NULL..you removed it in current in 1.166, but some people are
> seeing it trigger on 5
On Sun, May 29, 2005 at 11:29:56AM -0700, Derek Kuli?ski wrote:
> Hello,
>
> Today I noticed following message in the log:
>
> > KDB: stack backtrace:
> > kdb_backtrace(c07163b8,2,c661994c,0,22) at kdb_backtrace+0x2e
> > getdirtybuf(d109ebac,0,1,c661994c,1) at getd
Hello Sven,
Tuesday, May 31, 2005, 2:29:36 PM, you wrote:
> Apparently this is still somewhat of a mystery, but you are not the
> first person to witness this:
> http://lists.freebsd.org/pipermail/freebsd-stable/2005-April/013679.html
> http://lists.freebsd.org/pipermail/freebsd-current/2004-Jul
On Sun, 2005-05-29 at 11:29 -0700, Derek Kuliński wrote:
> Hello,
>
> Today I noticed following message in the log:
>
> > KDB: stack backtrace:
> > kdb_backtrace(c07163b8,2,c661994c,0,22) at kdb_backtrace+0x2e
> > getdirtybuf(d109ebac,0,1,c661994c,1) at getd
Hello,
Today I noticed following message in the log:
> KDB: stack backtrace:
> kdb_backtrace(c07163b8,2,c661994c,0,22) at kdb_backtrace+0x2e
> getdirtybuf(d109ebac,0,1,c661994c,1) at getdirtybuf+0x2b
> flush_deplist(c282f4cc,1,d109ebd4,d109ebd8,0) at flush_deplist+0x57
> flus
On Tue, 2005-04-12 at 03:29 +0800, Rong-En Fan wrote:
> I saw these similar trace on a 5.4-RC1/amd64 with 9 NFS mount. I suspect
> this is a issue with busy NFS server?
No, no NFS involved at all, nor any other network filesystem, client or
server.
--
brandon s. allbery [linux,solaris,freebsd,
On Apr 11, 2005 3:16 AM, Brandon S. Allbery KF8NH <[EMAIL PROTECTED]> wrote:
> I have twice so far had the kernel syslog a stack backtrace with no
> other information. Inspection of the kernel source, to the best of my
> limited understanding, suggests that getdirtybuf() was
Brandon S. Allbery KF8NH presumably uttered the following on 04/10/05 15:16:
I have twice so far had the kernel syslog a stack backtrace with no
other information. Inspection of the kernel source, to the best of my
limited understanding, suggests that getdirtybuf() was handed a buffer
without an
I have twice so far had the kernel syslog a stack backtrace with no
other information. Inspection of the kernel source, to the best of my
limited understanding, suggests that getdirtybuf() was handed a buffer
without an associated vnode. Kernel config file and make.conf attached.
Should I be
12 matches
Mail list logo
