Re: iwi bricks my T43 on boot

Max Laier <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile,gmane.os.freebsd.devel.net
Organization FreeBSD
Message-ID <[email protected]>
On Sunday 24 September 2006 17:57, Sergey Matveychuk wrote:
> I have IBM T43 notebook with this wireless internal card:
>
> iwi0: <Intel(R) PRO/Wireless 2200BG> mem 0xa8401000-0xa8401fff irq 11
> at device 2.0 on pci4
>
> The problem is FreeBSD bricks my notebook on boot sometime. After I've
> turned rc.d debugging on I see it hangs after ifconfig_up: iwi0
> operation. It happens quite rarely when I use a power supply and very
> often when my notebook boots on battery.

This rather sound like a hardware problem - a power consumption spike the 
battery can't provide anymore or something, but let's see ...

> 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.

> 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/*?

-- 
/"\  Best regards,                      | [email protected]
\ /  Max Laier                          | ICQ #67774661
 X   http://pf4freebsd.love2party.net/  | mlaier@EFnet
/ \  ASCII Ribbon Campaign              | Against HTML Mail and News
signature.asc (application/pgp-signature, 187 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQBFFtI7XyyEoT62BG0RAhfBAJ4rJsdDkRwz0YiRjURENjj+LdH9agCeNThc
HWmwmcb2j561KpN2a7i76Eo=
=JDPq
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.