From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 15 14:13:06 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7202F37B401; Tue, 15 Jul 2003 14:13:06 -0700 (PDT) Received: from mail.ludost.net (tonib-gw.customer.0rbitel.net [195.24.39.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0235643F75; Tue, 15 Jul 2003 14:13:05 -0700 (PDT) (envelope-from maav@bastun.net) Received: from SABBATH (ozzy.ddns.cablebg.net [217.18.240.240]) by mail.ludost.net (Postfix) with ESMTP id 098144C729; Wed, 16 Jul 2003 00:13:02 +0300 (EEST) Message-ID: <000901c34b15$d48db900$020aa8c0@SABBATH> From: "Boris Georgiev" To: "william paul" References: <200307142126.OAA17158@huisne.wrs.com> Date: Wed, 16 Jul 2003 00:12:41 +0300 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 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-net@freebsd.org cc: ken@kdm.org cc: freebsd-current@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: Broadcom NetXtreme BCM5705M support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 21:13:06 -0000 Hi Bill, Sorry for the previous e-mail, but have in mind that I'm trying to cooperate by testing your drivers and I am not aware of the rules for declaring a hardware problem in the mailing lists. The only way I can send you the messages from the kernel is if I rewrite them from the console. Here is the information that you requested: bge0: mem 0x90000000-0x9000ffff irq 11 at device 14.0 on pci2 bge0: firmware handshake timed out bge0: RX CPU self-diagnostics failed! bge0: chip initialization failed device_probe_and_attach: bge0 attach returned 6 If you need more detailed information, I can send it to you on request. Boris Georgiev > Uh.... > > First of all, the driver does not load any firmware into the chip. > > Second, you're not supposed to tell me your interpretation of what > happened: you're supposed to cut&paste the messages into an e-mail > so that I can see for myself what happened. > > Please show me all of the information that led you to your conclusion > that this alleged firmware upload failed. > > > It gave me out > > an timeout message and didn't load the driver at all. I am sorry that at > > this time I cannot send > > the exact message from the kernel, but the notbook is at my office, so I > > will post it > > tomorrow if the output will help for finding out what the problem is. > > Best regards, > > Ok, note to all reading this: if I ask for information and you don't > have the information available, don't bother sending me an e-mail > just to tell me that you don't have the information available. Wait > until you do have the information available, and then e-mail me. You'll > save precious time and electrons. > > -Bill