From owner-freebsd-net@FreeBSD.ORG  Sun Sep 24 19:59:28 2006
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: freebsd-net@freebsd.org
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EBDD316A415;
	Sun, 24 Sep 2006 19:59:28 +0000 (UTC) (envelope-from sem@FreeBSD.org)
Received: from mail.ciam.ru (ns.ciam.ru [213.247.195.75])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8D66043D46;
	Sun, 24 Sep 2006 19:59:28 +0000 (GMT) (envelope-from sem@FreeBSD.org)
Received: from [87.240.16.199] (helo=[192.168.0.4])
	by mail.ciam.ru with esmtpa (Exim 4.x)
	id 1GRa8M-000GxU-RE; Sun, 24 Sep 2006 23:59:27 +0400
Message-ID: <4516E395.8090208@FreeBSD.org>
Date: Sun, 24 Sep 2006 23:59:17 +0400
From: Sergey Matveychuk <sem@FreeBSD.org>
User-Agent: Thunderbird 1.5.0.5 (X11/20060902)
MIME-Version: 1.0
To: Max Laier <max@love2party.net>
References: <4516AADD.2050108@FreeBSD.org>
	<200609242045.15648.max@love2party.net>
In-Reply-To: <200609242045.15648.max@love2party.net>
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 7bit
Cc: freebsd-net@freebsd.org, freebsd-mobile@freebsd.org
Subject: Re: iwi bricks my T43 on boot
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Sep 2006 19:59:29 -0000

Max Laier wrote:
> 
>> The problem has appeared when a new driver for ipw/iwi was introduced.
>>
>> A fresh CURRENT here. When the problem was firstly arised it was 6.0.
> 
> The new driver has never been in 6.0.

Well, I'm not quite sure here. May be it was CURRENT that time.

> 
>> Because my notebook bricked I can't get a core dump or a debugger.
>>
>> Any hints please how can I get more info on this?
> 
> Can you make sure you have a complete debugging kernel with WITNESS 
> enabled?  Setting debug.iwi could also reveal what's going on.  
> Unfortunately it's only a sysctl, not a tuneable, so you'd have to change 
> the default in sys/dev/iwi/if_iwi.c line 88 by hand and recompile your 
> kernel/module.  By the way, are you using iwi built in or as a module?  
> Do you load it via loader.conf or on demand from rc.d/*?
> 

I have WITNESS in my kernel. I'll try with debug.iwi.
I have iwi-firmware-kmod-3.0_1 port installed.

-- 
Dixi.
Sem.