From owner-freebsd-bugs Sat Feb 12 13:59: 0 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by builder.freebsd.org (Postfix) with ESMTP id C1C3440F3; Sat, 12 Feb 2000 13:58:55 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA71282; Sat, 12 Feb 2000 14:58:54 -0700 (MST) (envelope-from ken) Date: Sat, 12 Feb 2000 14:58:54 -0700 From: "Kenneth D. Merry" To: Torsten Kuehn Cc: freebsd-bugs@freebsd.org, wilko@freebsd.org, gibbs@freebsd.org Subject: Re: ahb Bug still not resolved in 3.2-release (ref. kern/12495) Message-ID: <20000212145854.A71056@panzer.kdm.org> References: <000212222503224500@mail1.pcom.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <000212222503224500@mail1.pcom.de>; from tkuehn@websurf.pcom.de on Fri, Mar 21, 2036 at 04:54:47AM +0000 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Mar 21, 2036 at 04:54:47 +0000, Torsten Kuehn wrote: > I've got a problem similar PR kern/12495 reported by Wilko Bulte. > With a freshly installed system, 3.2-release's GENERIC kernel fails to > attach a Nec 502 (6x Caddy) CDROM drive connected to AHA-1742. > dmesg reveals > (cd0:ahb0:0:3:0): got CAM status 0x4a FWIW, CAM status 0x4a means selection timeout. i.e. we timed out just trying to select the device. Interestingly enough, this happened after a number of commands, including an inquiry and probably a test unit ready succeeded. (I know that's the case, since the above error message came from the CD driver's attach routine, where it attempts to issue a read capacity.) Have you tried booting both with and without a CD in the drive? > " " " fatal error, failed to attach to device > " " " lost device > " " " removing device entry > Unlike Wilko's experiences, this happens with an *installed* system. > In fact, I am not completely sure if I probably used a different drive > during installation. Any post install modifications can only be run > over a network connection (just like Wilko did). The drive itself and > whole SCSI subsystem run fine with Warp SMP, NT351SMP, Linux 2.2 > (the latter has a horrible driver bug which only turns out in SMP mode, > did 'fix' it by disabling EISA to PCI buffers in chipset setup). > I have tried various modifications to GENERIC kernel, wired-down and > unwired devices, got unbootable kernels and reverted - nothing helps. > Another oberservation: if machine is restarted (issuing 'reboot') after > successful SMP boot (without CDROM), the next reboot fails with > SMP: AP CPU #1 launched! <- normally, SCSI probing starts here > (probe0:ahb0:0:0:0) ECB 0xc2e83e80 - timed out > (probe0:ahb0:0:0:0) Queuing BDR > ahb0: no longer in timeout > [...] > (probe0:ahb0:0:0:0) ECB 0xc2e83e80 - timed out > System only restarts successfully after reset button is pressed once. > Torsten Kuehn Note that the errors you're seeing there are from a different device, most likely your hard disk. I'm not entirely sure what is going on here, but it is probably worth trying to boot with and without a CD in the drive. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message