Subject: Re: Please audit pool use in your code!
To: tech-kern <firstname.lastname@example.org>
From: David Brownlee <abs@NetBSD.org>
Date: 07/28/2006 15:59:21
On Sun, 23 Jul 2006, David Brownlee wrote:
> Another (posible) data point.
> I've been seeing very similar issues on two of my boxes (0xe),
> and switched one of then to a GENERIC 3 kernel from NetBSD.org,
> but it happened again (after about four days). If this is the
> same issue then it rules out PF for me (my only common factor).
> I'm going to dig out a SATA card and swap out every piece of
> hardware apart from the disks next, just to make absolutely
> certain I have a software issue and not a rogue datapoint.
Just had this on a box which had until this point been running
NetBSD-3 without any problems for many months. Only change was
it now had a USB printer attached (previously no UDB devices).
It _did_ fill up the disk, though its done that before
occasionally without problems:
Is there a PR open to which it would be useful appending this?
uid 2015, pid 15953, command smbd, on /home: file system full
uvm_fault(0xbe1a17ec, 0, 0, 1) -> 0xe
fatal page fault in supervisor mode
trap type 6 code 0 eip a053e92b cs 8 eflags 10246 cr2 48 ilevel 5
trap() at netbsd:trap+0x171
--- trap (number 6) ---
ulptclose(3900,2,2000,bdb9d4cc,40500) at netbsd:ulptclose+0x6e
spec_close(bd99fdb4,10002,c2503dd8,0,a07a2a80) at netbsd:spec_close+0xbf
VOP_CLOSE(c2503dd8,2,bd770ccc,bdb9d4cc,bde07ee0) at netbsd:VOP_CLOSE+0x36
vn_close(c2503dd8,2,bd770ccc,bdb9d4cc,a25cfaa8) at netbsd:vn_close+0x44
vn_closefile(bde07ee0,bdb9d4cc,2,bd99fe44,20) at netbsd:vn_closefile+0x29
closef(bde07ee0,bdb9d4cc,bdd68c38,bdb9d4cc,0) at netbsd:closef+0xd5
fdfree(bdb9d4cc,0,bd99ff3c,a03a0cd3,bd99fed4) at netbsd:fdfree+0x5f
exit1(be0af6bc,0,bdb9d4cc,be0af6bc,0) at netbsd:exit1+0x1af
sys_exit(be0af6bc,bd99ff64,bd99ff5c,bdb9d4cc,1) at netbsd:sys_exit+0x29
syscall_plain() at netbsd:syscall_plain+0x85
--- syscall (number 1) ---
David/absolute -- www.NetBSD.org: No hype required --