From owner-freebsd-stable Sat Sep 18 15:53:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7A2F914D41 for ; Sat, 18 Sep 1999 15:53:54 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA70760; Sat, 18 Sep 1999 16:53:28 -0600 (MDT) (envelope-from ken) Message-Id: <199909182253.QAA70760@panzer.kdm.org> Subject: Re: da1 reported as cda1 in dmesg In-Reply-To: <4.2.0.58.19990918153822.00a760d0@mail.elcjn1.sdca.home.com> from Bryan Talbot at "Sep 18, 1999 03:43:22 pm" To: btalbot@ucsd.edu (Bryan Talbot) Date: Sat, 18 Sep 1999 16:53:28 -0600 (MDT) Cc: stable@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bryan Talbot wrote... > My 3.3-stable system is reporting the same thing. I think that the 'c' > from the "changing root device" string is getting screwed up in an output > buffer somehow and is appearing before the "da" device name. Here's my output: > > Waiting 3 seconds for SCSI devices to settle > de0: enabling 10baseT port > cda0 at ncr0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled > da0: 1033MB (2117025 512 byte sectors: 255H 63S/T 131C) > da1 at ncr0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 10.000MB/s transfers (10.000MHz, offset 8) > da1: 1222MB (2503872 512 byte sectors: 255H 63S/T 155C) > hanging root device to wd0s1a That's an old problem and it's been discussed before in -current or -hackers, I think. (Look in the list archives. I don't remember the subject, but I'd imagine that the discussion took place sometime after the CAM integration in mid-September, 1998.) The bottom line is that the printf that prints "changing root.." gets interrupted by the interrupt-driven probe messages for your disks. IIRC, the solution would be worse than the problem, so just don't worry about it. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message