Date: Fri, 24 Aug 2007 01:24:37 +0400 From: pluknet <pluknet@gmail.com> To: "Andrew Thompson" <thompsa@freebsd.org> Cc: FreeBSD Current <current@freebsd.org> Subject: Re: wireless Message-ID: <a31046fc0708231424l98c3e7qed1ff0ee641b7108@mail.gmail.com> In-Reply-To: <20070723114821.GA6575@heff.fud.org.nz> References: <20070619011908.GA53748@heff.fud.org.nz> <20070620042023.GA17424@nowhere> <4678B1E4.7080909@errno.com> <467ED084.4000002@petri.cc> <46A484CA.8030805@petri.cc> <20070723114821.GA6575@heff.fud.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Andrew.
On 23/07/07, Andrew Thompson <thompsa@freebsd.org> wrote:
> On Mon, Jul 23, 2007 at 12:36:58PM +0200, Nicolai Petri (lists) wrote:
> > Nicolai Petri (lists) wrote:
> > >
> > >>>In short, ipw doesn't seem to work at all for me anymore. It worked
> > >>>okay in 6-stable with an occasional hiccup, but upon upgrading to
> > >>>current it doesn't seem to be doing anything.
> > >>>Sometimes "ifconfig scan" does nothing, sometimes it results in a panic.
> > >>
> > >>I'm not sure how well ipw got tested while the changes were in p4.
> > >>We'll need to test again now that code has been merged to CVS. I'll try
> > >>to look at this weekend if noone else beats me to it.
> > >>
> > >> Sam
> > >
> > ><rant-about-ipw-giving-instant-panic-removed/>
> > >I'm running -current from following time : Thu Jun 20
> > >
> > >Best regards,
> > >Nicolai Petri
> > >
> > Are there any news on this matter ? We are now 1 month closer to beta
> > and ipw is still useless. I'm willing to test if anyone have patches but
> > I don't have time to look at code myself.
>
> You can test this WIP.
>
>
> cheers,
> Andrew
I have a firmware problem with iwi(4) on recent current.
iwi0: <Intel(R) PRO/Wireless 2200BG>
It throws "iwi0: firmware error" if it has setup to associate in authmode WPA
(via wpa_supplicant). It worked for me before 80211n introduce.
Otherwise, it associates as well in authmode OPEN (without supplicant).
Any hopes it will be fixed before 7.0?
Also I can get "firmware error" if I kill watchdogd and then system goes to KDB
state over a specific timeout. Nevertheless, after 'continue' command
it associates
in OPEN, and not in WPA (i.e. same as mentioned above).
Cut from dmesg right after watchdogd's death:
interrupt total
irq0: clk 23255323
irq1: atkbd0 198187
irq8: rtc 14882328
irq9: pcm0 iwi0+ 173519
irq11: fxp0 uhci0* 215
irq12: psm0 489456
irq14: ata0 194865
irq15: ata1 844
Total 39194737
KDB: stack backtrace:
db_trace_self_wrapper(c07a8e50,cba76c04,c051f4b5,c07a3ba7,2561071,...)
at db_trace_self_wrapper+0x26
kdb_backtrace(c07a3ba7,2561071,0,2561071,0,...) at kdb_backtrace+0x29
hardclock(0,c0a68c65,c1ebce80,0,cba76c44,...) at hardclock+0x1b5
clkintr(cba76c70,0,0,c1cd3660,c1cd0c00,...) at clkintr+0xda
intr_execute_handlers(c0807280,cba76c70,0,c1d64200,c1d64218,...) at
intr_execute_handlers+0xf5
atpic_handle_intr(0,cba76c70) at atpic_handle_intr+0xbc
Xatpic_intr0() at Xatpic_intr0+0x21
--- interrupt, eip = 0xc0a68c65, esp = 0xcba76cb0, ebp = 0xcba76cb0 ---
acpi_cpu_c1(1,10,c1cd3660,c1d64218,0,...) at acpi_cpu_c1+0x5
acpi_cpu_idle(cba76cf4,c05729c5,cba76d24,c05354e1,0,...) at acpi_cpu_idle+0x271
cpu_idle(cba76d24,c05354e1,0,cba76d38,0,...) at cpu_idle+0x26
sched_idletd(0,cba76d38,0,0,0,...) at sched_idletd+0x15
fork_exit(c05729b0,0,cba76d38) at fork_exit+0xa1
fork_trampoline() at fork_trampoline+0x8
--- trap 0, eip = 0, esp = 0xcba76d70, ebp = 0 ---
KDB: enter: watchdog timeout
interrupt total
irq0: clk 23255324
irq1: atkbd0 198187
irq8: rtc 14882328
irq9: pcm0 iwi0+ 173519
irq11: fxp0 uhci0* 215
irq12: psm0 489456
irq14: ata0 194865
irq15: ata1 844
Total 39194738
KDB: stack backtrace:
db_trace_self_wrapper(c07a8e50,cba7cc0c,c051f4b5,c07a3ba7,2561072,...)
at db_trace_self_wrapper+0x26
kdb_backtrace(c07a3ba7,2561072,0,2561072,0,...) at kdb_backtrace+0x29
hardclock(0,c0754129,c1ebce80,0,cba7cc4c,...) at hardclock+0x1b5
clkintr(cba7cc78,1ca0,0,c1cd3aa0,c1cd0c00,...) at clkintr+0xda
intr_execute_handlers(c0807280,cba7cc78,c1cd3aa0,c1cd0400,0,...) at
intr_execute_handlers+0xf5
atpic_handle_intr(0,cba7cc78) at atpic_handle_intr+0xbc
Xatpic_intr0() at Xatpic_intr0+0x21
--- interrupt, eip = 0xc0754129, esp = 0xcba7ccb8, ebp = 0xcba7ccbc ---
spinlock_exit(1,0,c07a4a4c,46b,0,...) at spinlock_exit+0x29
ithread_loop(c1c9f460,cba7cd38,0,0,0,...) at ithread_loop+0x353
fork_exit(c0538a60,c1c9f460,cba7cd38) at fork_exit+0xa1
fork_trampoline() at fork_trampoline+0x8
--- trap 0, eip = 0, esp = 0xcba7cd70, ebp = 0 ---
KDB: enter: watchdog timeout
iwi0: firmware error
^^^^
iwi0: link state changed to DOWN
iwi0: link state changed to UP
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a31046fc0708231424l98c3e7qed1ff0ee641b7108>