new panics

[Peter Holm]

On Fri, Jun 24, 2005 at 03:01:34PM -0500, Mike Silbersack wrote:
> 
> The Memory modified after free panics you guys have reported are 
> unfortunately not pinpointing where the error occured, they're just 
> pinpointing where the error was detected. :)
> 
> So, either I need to improve the code to be more useful, or we could do 
> some quick code inspection - which network devices are you using, and are 
> you using any features like ipfw, netgraph, etc?
> 
> Mike "Silby" Silbersack

I'm stress testing with GENERIC + 

$ diff GENERIC PHO
68a69
> options         BREAK_TO_DEBUGGER
295a297,303
> 
> options         DEBUG_LOCKS
> options         DEBUG_VFS_LOCKS
> options         KTR
> options         KTR_ENTRIES=4096
> options         KTR_MASK=(KTR_BUF|KTR_VFS)
> options         KTR_COMPILE=(KTR_BUF|KTR_VFS)

rl0: <RealTek 8139 10/100BaseTX> port 0xd800-0xd8ff mem
0xff9ffc00-0xff9ffcff irq 22 at device 5.0 on pci2

I get the panics within minutes of testing, so if there's any thing I
can do to help ...
-- 
Peter Holm