Last week, Nate Lawson reported a panic in 5.1-CURRENT as described below. However, despite the apparent resolution, doing a clean install on an IBM t40 with the most recent snapshot from snapshots.jp.freebsd.org still results in the same panic for me. I can provide more information as necessary. Thanks, Rob Ferguson rob_at_fergusonlabs_dot_com > On Mon, 8 Sep 2003, Soren Schmidt wrote: > > It seems Nate Lawson wrote: > > > With a fresh checkout of last night's -current, I cannot boot my laptop. > > > ATAFD panics the box by reusing freed memory. I do not have a floppy > > > drive in the laptop and when I do, it's a legacy floppy, not atapi. Here > > > are the messages: > > > > > > [normal ad0/acd0 probe message] > > > afd0: timeout waiting for ATAPI ready > > > afd0: timeout waiting for ATAPI ready > > > afd0: timeout waiting for ATAPI ready > > > afd0: timeout waiting for ATAPI ready > > > afd0: timeout waiting for ATAPI ready > > > panic: Memory modified after free: 0xc33ed400 (252) > > > Most recently used by AFD driver > > > > > > A working dmesg: > > > http://www.root.org/~nate/acpi/ibm.dmesg > > > > >From the above I can tell whats going on, please upgrade to the latest > > -current as I've fixed a couble of things in the probe code there. > > > > If it still panic's please include a verbose boot from a atapicam-less > > kernel... > > This has been fixed. However, ATAng is still not usable for the reasons > in my next email message: > Message-ID: <20030913164950.S3069_at_root.org> > > -Nate > >Received on Tue Sep 23 2003 - 08:28:22 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:23 UTC