That's a somewhat strange oops...

On Monday 21 November 2005 22:10, Dick Streefland wrote:
> Nov 21 21:45:09 acer kernel: bcm430x: Transmit Status received:  flags: 0x00, 
>  cnt1: 0x00,  cnt2: 0x01,  cookie: 0x103a,  seq: 0x003b,  unk: 0x0000
> Nov 21 21:45:09 acer kernel: bcm430x: Transmit Status received:  flags: 0x00, 
>  cnt1: 0x00,  cnt2: 0x01,  cookie: 0x103b,  seq: 0x003c,  unk: 0x0000

The oops reason is missing here (kernel NULL pointer dereference, or page fault 
or something like that...)

> Nov 21 21:45:09 acer kernel: e094adf8
> Nov 21 21:45:09 acer kernel: Modules linked in: bcm430x
> Nov 21 21:45:09 acer kernel: CPU:    0
> Nov 21 21:45:09 acer kernel: EIP:    0060:[pg0+539553272/1066673152]    Not 
> tainted VLI
> Nov 21 21:45:09 acer kernel: EFLAGS: 00010086   (2.6.15-rc2) 
> Nov 21 21:45:09 acer kernel: EIP is at 
> bcm430x_phy_estimate_power_out+0xc8/0xe0 [bcm430x]
> Nov 21 21:45:09 acer kernel: eax: 00000000   ebx: 00000000   ecx: db2aec80   
> edx: fffffff0
> Nov 21 21:45:09 acer kernel: esi: 00000000   edi: db2aeb74   ebp: 00000000   
> esp: dbb3def4
> Nov 21 21:45:09 acer kernel: ds: 007b   es: 007b   ss: 0068
> Nov 21 21:45:09 acer kernel: Process bcm430x_wq/0 (pid: 3799, 
> threadinfo=dbb3c000 task=dbadf540)
> Nov 21 21:45:09 acer kernel: Stack: e0945865 db2aeb74 00000001 00000072 
> 00007f7f 00000000 e094af51 db2aeb74 
> Nov 21 21:45:09 acer kernel:        00000000 00000072 c067f410 003d0903 
> db2aeab8 000c3500 66775b00 003d09e0 
> Nov 21 21:45:09 acer kernel:        dbadf668 dbadf540 66775b00 db2aeb74 
> 00000292 db2aeb74 e093a0a0 e093a0c6 
> Nov 21 21:45:09 acer kernel: Call Trace:
> Nov 21 21:45:09 acer kernel:  [pg0+539531365/1066673152] 
> bcm430x_radio_clear_tssi+0xe5/0xf0 [bcm430x]
> Nov 21 21:45:09 acer kernel:  [pg0+539553617/1066673152] 
> bcm430x_phy_xmitpower+0x141/0x430 [bcm430x]
> Nov 21 21:45:09 acer kernel:  [pg0+539484320/1066673152] 
> bcm430x_periodic_work0_handler+0x0/0x70 [bcm430x]
> Nov 21 21:45:09 acer kernel:  [pg0+539484358/1066673152] 
> bcm430x_periodic_work0_handler+0x26/0x70 [bcm430x]

bcm430x_periodic_work0_handler is not called resursive.

> Nov 21 21:45:09 acer kernel:  [worker_thread+433/608] 
> worker_thread+0x1b1/0x260
> Nov 21 21:45:09 acer kernel:  [default_wake_function+0/32] 
> default_wake_function+0x0/0x20
> Nov 21 21:45:09 acer kernel:  [worker_thread+0/608] worker_thread+0x0/0x260
> Nov 21 21:45:09 acer kernel:  [kthread+182/192] kthread+0xb6/0xc0
> Nov 21 21:45:09 acer kernel:  [kthread+0/192] kthread+0x0/0xc0
> Nov 21 21:45:09 acer kernel:  [kernel_thread_helper+5/12] 
> kernel_thread_helper+0x5/0xc
> Nov 21 21:45:09 acer kernel: Code: 04 04 87 95 e0 c7 04 24 3c 13 95 e0 e8 22 
> 4f 7d df 89 da 83 c4 14 89 d0 5b c3 31 db 85 d2 78 08 b3 3f 83 fa 40 0f 4c da 
> 8b 41 18 <0f> be 14 18 83 c4 14 5b 89 d0 c3 8d b6 00 00 00 00 8d bc 27 00 
> Nov 21 21:45:28 acer kernel:  <4>printk: 19 messages suppressed.
> Nov 21 21:45:28 acer kernel: bcm430x: Unhandled IRQ! Reason: 0x00000084,  
> Unhandled: 0x00000080,  DMA: 0x00000000, 0x00000000, 0x00000000, 0x00000000
> 

Could you try to get another oops, please?
The clear_tssi func is quite small and I do not see where it is possible to 
oops there.
In fact: EIP is at bcm430x_phy_estimate_power_out
clear_tssi does not call that.

-- 
Greetings Michael.

Attachment: pgpjB62ip4C0d.pgp
Description: PGP signature

Reply via email to