RE: [ipw3945-devel] Panic in iwl3945 driver

Cahill, Ben M
2010-01-06T05:23:47Z

>-----Original Message-----
>From: Zhu, Yi
>Sent: Tuesday, January 05, 2010 10:57 PM
>To: Cahill, Ben M
>Cc: Maxim Levitsky; Chatre, Reinette; linux-wireless; iwlwifi
>maling list
>Subject: RE: [ipw3945-devel] Panic in iwl3945 driver
>
>On Wed, 2010-01-06 at 06:26 +0800, Cahill, Ben M wrote:
>> >><3>[ 330.762510] iwl3945 0000:06:00.0: 1035963222
>> >>0x04dc0018 0401
>> >
>> >Last good command 0x18, with (driver provided) header
>> >indicating sent via queue 4, queue index 0xdc
>> >
>> >><3>[ 330.762547] iwl3945 0000:06:00.0: 1035963229
>> >>0x00000000 0401
>> >
>> >This shows command "0" (non-existant/unsupported/bad command)
>> >with (driver provided) header indicating sent via queue "0",
>> >index "0"; obviously bad data in command queue.
>>
>> Or index ("pointer") is getting out of sync. (Reminder to
>self; never
>> use the word "obviously").
>
>Ben, does it smell like driver issue or firmware bug?

I would tend to suspect driver or platform issue, but that's just a guess of course. Something seems to be telling the device to read DRAM that contains "0". Do we reset unused command buffers to 0? Just wondering if the index/pointers are getting out of sync somehow (double-increment or who-knows-what?).

I haven't followed this thread closely (plus I've been on vacation!); can you give me a summary of what you're trying to fix?

Also, not sure if it's relevant, but a community member discovered that MSI should be enabled in kernel config. See bugzilla 1944.

-- Ben --

>
>Thanks,
>-yi
>
>