From owner-cvs-src@FreeBSD.ORG Wed Apr 21 08:49:43 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 0C46E16A4CF; Wed, 21 Apr 2004 08:49:43 -0700 (PDT) In-Reply-To: from Niki Denev at "Apr 21, 2004 12:32:16 pm" To: nike_d@cytexbg.com (Niki Denev) Date: Wed, 21 Apr 2004 08:49:43 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20040421154943.0C46E16A4CF@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: cvs-src@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/if_ndis if_ndis.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2004 15:49:43 -0000 > > doesn't seem to help here.... i got exactly the same lockup after the first > packets transmitted/recvd over the wireless as before... > the machine is ibm tp X31, with the above mentioned centrino wireless mini > pci card, and -current as from 1-2 hours ago. > is there any info that i can provide, to help on this? > > --niki Well, seeing as how you didn't provide any info at all in this e-mail, what do you think? I really wish people would stop asking questions like this and just offer me the information. It's not like you need me to lay it all out for you. There isn't anything magical or complicated that requires any hand-holding my my part. Just show me how to reproduce your problem. Now, notice: I said _SHOW_, not _TELL_. Don't describe the problem or interpret the problem. Just show me the precise sequence of steps which you take that precipitates the problem. And don't summarize. Saying "I just bring the interface up" is not helpful. Saying "I use ifconfig to bring the interface up, and here's the commands I typed and all the error/console messages I saw" is helpful. You want to show me the minimum number of steps I need to take to reproduce the issue. And you don't want to assume anything or skip a step because you think it's trivial or unimportant. Oh, and somewhere along the line, you're going to forget that I can't see what kind of network you're attached to (ad-hoc? bss?) and what kind of AP, if any, that you're connected to (manufacturer? model?), so I'm warning you right now _NOT_ to do that. You're also going to forget to give me a copy of the exact driver that you're using, so I'm going to caution you against that as well. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose =============================================================================