From owner-freebsd-current@FreeBSD.ORG Tue Jan 27 09:47:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 2780D16A4D1; Tue, 27 Jan 2004 09:47:26 -0800 (PST) In-Reply-To: <20040127111802.GA96935@fit.vutbr.cz> from Rudolf Cejka at "Jan 27, 2004 12:18:02 pm" To: cejkar@fit.vutbr.cz (Rudolf Cejka) Date: Tue, 27 Jan 2004 09:47:26 -0800 (PST) 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: <20040127174726.2780D16A4D1@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: freebsd-current@FreeBSD.ORG Subject: Re: Project Evil: The Evil Continues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 17:47:26 -0000 > Bill Paul wrote (2004/01/27): > > a) you only gave me one instruction where the crash occured, rather > > than showing me the entire stack trace and console display so I could > > see what other messages (if any) appeared on the console when it happened, > > This and other points: Ok, ok ;o) I just waited, how much you are > interested in which things. As the first show, you can download > ftp://ftp.FreeBSD.cz/pub/FreeBSD-local/ndis/gdb.out.bz2 , where is > output of these gdb commands: > > file kernel.debug > core-file /var/crash/vmcore.14 > bt > up 12 > disas > quit Unfortunately, this doesn't tell me much. :( > > b) you > > didn't tell me what speed/mode you were using at the time, > > Is output of ifconfig sufficient? In other case, I do know how get > this information. *sigh* Look, you told me you tried the card with both 11b and 11g modes. Which one where you using when the system crashed? It's a simple question. You could also tell me what access point you were connected to at the time. > cbg0: flags=8843 mtu 1500 > inet6 fe80::207:40ff:fec1:b188%cbg0 prefixlen 64 scopeid 0x4 > inet 147.229.12.36 netmask 0xffffff00 broadcast 147.229.12.255 > ether 00:07:40:c1:b1:88 > media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) > status: associated > ssid FITZAM 1:FITZAM > channel 1 authmode OPEN powersavemode OFF powersavesleep 100 > wepmode MIXED weptxkey 1 > wepkey 1:104-bit You were not using 11g mode then, correct? (I.e. this was at 11Mbps, not 54Mbps.) > > and c) > > you have not provided a more precise means of duplicating the crash > > (I can't do cvsup from home: I only have a dialup). Cvsup is not > > a network diagnostic or traffic generation tool: it is not possible > > to generate consistent, reproducible results with it. Use ttcp or > > netperf instead, then show me _EXACTLY_ how you ran it to produce > > the crash so I can do it too. > > Ok, I do it. Now I have to go to lunch ;o) Do you have this or similar > card too? The driver is bcmwl5.sys and it seems that it is shared > among several cards. > > > > *) Cisco AIR-CB20A / AIR-CB20A-A-K9 (802.11a) > > I don't have a card like this. What chipset is it? > > I'm sorry - how do you get information about used chipsets? For PCI or cardbus, it's really simple: just do pciconf -lv and send it to me. > If you want, it would not be problem for me to give you an ssh access > to my notebook in my working time (about 4 hours before and 4 hours > after exactly this time). Unfortunately, I usually need more time than this, and matching up my free time with your free time is hard. I just received an SMC card to experiment with, so I'll probably be busy with that for a while. -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 =============================================================================