|
|
About ::
TODO ::
Blog ::
RSS ::
Old blog ::
Projects ::
GIT ::
Gallery ::
Notes
Wed, 24 Sep 2008
First ipw2100 testing: fatal interrupt.
I managed to compile small enough kernel, which boots on
my laptop (do not know how long it took, since fell asleep),
and managed to bring fatal interrupt error just after several seconds
of ping -f 192.168.1.1 -s 8192 on freshly booted
machine. 192.168.1.1 is my gateway address.
Here is the result with the patch I posted to the mail lists,
which was not acked, replied and commented though (well, I have to admit,
that if I would send it couple of mails earlier, it could probably find its
way into the tree, but I still believe that it would not result in anything,
since everyone knows about this bug, it just is not fixed by some reasons).
Intel developers (at least those who maintain the driver) continue to keep silence.
[ 613.960164] ipw2100: exit - failed to send CARD_DISABLE command
[ 624.456033] eth1: no IPv6 routers present
[ 690.721534] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 690.721554] eth1: Fatal error value: 0x5000C97C, address: 0x100E201C, inta: 0x40000000
[ 690.721580] ------------[ cut here ]------------
[ 690.721587] WARNING: at drivers/net/wireless/ipw2100.c:3188
ipw2100_irq_tasklet+0x8fe/0x9b0 [ipw2100]()
[ 690.721736] Pid: 0, comm: swapper Not tainted 2.6.27-rc7-mainline #2
[ 690.721744] [] warn_on_slowpath+0x5f/0x90
[ 690.721763] [] up+0x11/0x40
[ 690.721773] [] release_console_sem+0x190/0x1d0
[ 690.721786] [] enqueue_hrtimer+0x72/0xf0
[ 690.721795] [] printk+0x1b/0x20
[ 690.721805] [] ipw2100_irq_tasklet+0x8fe/0x9b0 [ipw2100]
[ 690.721831] [] hrtick_start_fair+0x157/0x170
[ 690.721844] [] enqueue_hrtimer+0x72/0xf0
[ 690.721855] [] snd_intel8x0_interrupt+0x1d7/0x250 [snd_intel8x0]
[ 690.721875] [] tasklet_action+0x46/0xb0
[ 690.721886] [] __do_softirq+0x75/0xf0
[ 690.721897] [] do_softirq+0x37/0x40
[ 690.721906] [] do_IRQ+0x40/0x70
[ 690.721917] [] getnstimeofday+0x37/0xe0
[ 690.721927] [] common_interrupt+0x23/0x28
[ 690.721937] [] sys_setpgid+0xd8/0x190
[ 690.721955] [] acpi_idle_enter_simple+0x15a/0x1c1 [processor]
[ 690.721980] [] cpuidle_idle_call+0x7b/0xc0
[ 690.721991] [] cpu_idle+0x46/0xe0
[ 690.722000] =======================
[ 690.722006] ---[ end trace 70268f59a00d957c ]---
[ 695.271318] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 695.271337] eth1: Fatal error value: 0x50014148, address: 0x60207E04, inta: 0x40000000
writing this note and starting over
[ 1520.709136] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 1520.709156] eth1: Fatal error value: 0x5000C96C, address: 0x538E7E40, inta: 0x40000000
[ 1550.954315] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 1550.954334] eth1: Fatal error value: 0x5000C99C, address: 0x08418004, inta: 0x40000000
[ 1592.175473] ipw2100: Fatal interrupt. Scheduling firmware restart.
[ 1592.175492] eth1: Fatal error value: 0x50018588, address: 0x57E77A00, inta: 0x40000000
So, this fatal error value and address numbers do not tell me anything,
but since they are always different on different addresses, I think firmware
just loses its mind and stops responding.
The first line, where ipw2100 fails to send a command, was obtained during
ifdown of the interface. I never saw it before, but do not think
it is related though.
So, I need to move to the office and want to make some
distributed storage
changes, namely fix an issue with name collision (kernel already has a dvb card, which
module is called dst.ko), and implement better minor number allocation
scheme for the imported devices, since right now after node was created and distroyed,
new one will not get the same number, but continuously increasing one, which looks
confusing and may bring a sysfs initialization error (when system tries to
register kobject with existing name).
I will continue ipw2100 experiments today's night if will not fall asleep again
because of jetlag. Stay tuned!
/devel/networking/ipw2100 :: Link / Comments ()
|