Date: Mon, 28 Nov 2005 18:45:06 +0100 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Eric Anderson <anderson@centtech.com>, Chris Howells <howells@kde.org> Cc: acpi@freebsd.org, freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org, Graham North <northg@shaw.ca> Subject: Re: ACPI problems with Dell laptops Message-ID: <20051128174506.GD963@eucla.lemis.com> In-Reply-To: <200511272310.02378.howells@kde.org> <20051127115041.GD867@eucla.lemis.com> References: <4383C20E.20509@shaw.ca> <43891936.7090904@centtech.com> <20051127115041.GD867@eucla.lemis.com> <200511272310.02378.howells@kde.org> <4383C20E.20509@shaw.ca> <20051123195120.GE908@eucla.lemis.com> <43891936.7090904@centtech.com> <20051127115041.GD867@eucla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 27 November 2005 at 23:10:01 +0000, Chris Howells wrote:
> On Sunday 27 November 2005 11:50, Greg 'groggy' Lehey wrote:
>> Since then I've also discovered that the builtin wireless card doesn't
>> work either. It's:
>>
>> iwi0: <Intel(R) PRO/Wireless 2915ABG> mem 0xdfcfd000-0xdfcfdfff irq 10 at
>> device 3.0 on pci3 iwi0: Ethernet address: 00:13:ce:46:28:49
>
> <snip>
>
>> DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 6
>> DHCPDISCOVER on iwi0 to 255.255.255.255 port 67 interval 15
>> send_packet: Network is down
>>
>> On the console I get the detailed error message:
>>
>> iwi0: fatal error
>
> iwi(4) is unfortunately pretty unstable so I'm not sure if it's directly
> related to the ACPI problems.
Yes, as I said: since then. It doesn't work with or without ACPI, so
I see this as unrelated to ACPI. It does seem relevant to the
original Subject: line ("Laptop choices"), though.
Even more information about iwi0: I googled and found some information
about iwi and Dell laptops, and after issuing the command
# ifconfig iwi0 mode b
I got an association and was able to use the card. Then I tried
# ifconfig iwi0 mode g
which caused a panic
#9 0xc0648ff7 in panic (fmt=0xc087130c "mutex %s recursed at %s:%d") at /usr/src/sys/kern/kern_shutdown.c:539
#10 0xc064180b in _mtx_assert (m=0xc4d1cb6c, what=0xc1033000, file=0xc08726bd "/usr/src/sys/kern/kern_synch.c",
line=0xbc) at /usr/src/sys/kern/kern_mutex.c:748
#11 0xc064ee6a in msleep (ident=0xc4d1c000, mtx=0xc4d1cb6c, priority=0x0, wmesg=0xc0aadbd3 "iwiinit", timo=0x3e8)
at /usr/src/sys/kern/kern_synch.c:188
Unfortunately, the stack beyond this point was corrupt. Since then I
haven't been able to reproduce getting the card to associate or
(obviously) the panic. So I'd agree that iwi is still a bit flaky.
Greg
--
See complete headers for address and phone numbers
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051128174506.GD963>