Re: panic: Memory modified after free

Hi, thanks for taking a gander at my problem.  The original panic
can be reviewed here:
http://article.gmane.org/gmane.os.freebsd.current/31913

now to answer your query...

Doug Rabson wrote:
> On Thu, 2003-10-23 at 22:45, othermark wrote:
>> I wrote:
>> > I will try seeing how far I can go up the list of snapshots until I
>> > encounter the first boot -s panic.
>> 
>> Well I walked up the available snapshots and the first panic occurs with
>> the snapshot from the 17th of October.  Reviewing the commit logs between
>> the 16th and the 17th I note the following commits are the most
>> 'interesting.' as related to this panic..   This is just a cursory look
>> at the logs, I haven't gotten into compiling and fingering an exact
>> commit yet (which takes loads of time).
>> 
>> dfr         2003/10/16 02:16:28 PDT
>> 
>>   FreeBSD src repository
>> 
>>   Modified files:
>>     sys/sys              bus.h kobj.h param.h
>>     sys/kern             subr_bus.c subr_kobj.c
>>   Log:
>>   * Add multiple inheritance to kobj.
> 
> I haven't had any other reports of breakage related to this. Is it
> possible that you are using a kernel module which you have not re-built
> after this date (e.g. nvidia.ko)?

I'm not loading any modules with the single user boot 'boot -s'. (kldstat
shows no modules, just 'kernel'). In fact I only downloaded the 'kernel'
file for each snapshot off current.freebsd.org, placed it in it's own
directory under /boot and referenced it explicitly at the boot prompt. 
Beginning at the oct 17th snapshot, I got the same panic as referenced in
my original post to the list.

Does anyone else have a box with several legacy isa pnp cards or embedded
devices that can try to boot up -current from after the 17th?  

-- 
othermark
atkin901 at nospam dot yahoo dot com
(!wired)?(coffee++):(wired);