RE: boot hang: ata1: resetting devices .. done (5.1-CURRENT, IBM T30)

2003-10-08 Thread Robert Ferguson 
I see this problem as well. I'm running on a T40, with a DVD/CDRW in  
the ultrabay, and -CURRENT as of this morning. At boot, it hangs  
immediately after

ad0: 35174MB IC25N040ATCS05-0 [71465/16/63] at ata0-master UDMA100
ata1: resetting devices ..
done
Backing out the most recent checkin to sys/dev/ata/ata-queue.c (i.e.  
reverting to version 1.6) makes the problem go away.

A verbose dmesg from the machine (with that change removed) can be  
found at http://www.fergusonlabs.com/t40/dmesg0.txt

Thanks,
Rob Ferguson


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

ATAFD still reusing freed memory in latest snapshot

2003-09-23 Thread Robert Ferguson 
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:  [EMAIL PROTECTED]
 
 -Nate
 
 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]