From owner-freebsd-current Sun Jan 17 14:05:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06943 for freebsd-current-outgoing; Sun, 17 Jan 1999 14:05:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06919; Sun, 17 Jan 1999 14:05:21 -0800 (PST) (envelope-from gelderen@mediaport.org) Received: from wit395301.student.utwente.nl ([130.89.235.121]:4100 "HELO deskfix" ident: "NO-IDENT-SERVICE[2]") by schuimpje.snt.utwente.nl with SMTP id <7966-10514>; Sun, 17 Jan 1999 23:05:09 +0100 Message-ID: <000e01be4265$588824c0$1400000a@deskfix.local> From: "Jeroen C. van Gelderen" To: "jack" , "Jordan K. Hubbard" Cc: , Subject: Re: Annoying messages on startup.. Date: Sun, 17 Jan 1999 23:04:25 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Jordan K. Hubbard >I don't like this error much either (especially since it generates >tech support questions on USENET and other places from users going >"Aieee! What does this mean?!") me too Question is what to do about the messages. I can think of a few options: 1. move them to verbose mode. There are more drivers that spew this kind of message in verbose mode. 2. handle them trough the quirk mechanism. I was told that this would cause kernel-bloat but that might be remedied by using a more compact format (now 17 bytes per entry) for the quirk table and/or allowing the quirk table to be paged out (if possible?) 3. issue them only when the driver expects it to be a quirk. There are a lot of drives that will cause the openings to run down to a certain number and stay there. Don't issue a warning when the number stays above ??. 4. adjust the number of tagged openings on boot. Simply issue a lot of tagged openings and adjust the number appropriately. This would look very nice: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled (31 concurrent transactions) da0: 4096MB (8388608 512 byte sectors: 255H 63S/T 522C) or, if you want to do something about the formatting of the boot msgs: da0 at ahc0 bus 0 target 0 lun 0 Fixed Direct Access SCSI-2 device 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled (31 concurrent transactions) 4096MB (8388608 512 byte sectors: 255H 63S/T 522C) A combination of these ideas might do. Basically you want to get rid of the warnings when there's nothing wrong with the hardware. DISCLAIMER: I don't know much about CAM so please don't shoot me if this is nonsense... Cheers, Jeroen -- Jeroen C. van Gelderen -- gelderen@mediaport.org -- &[8-D}~<= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message