Re: Re: Occasional panics with 0.2.2 and DWL-122

Dave

Time to transfer this to the devel list.

skb_under_panic is only ever called from skb_push.


skb_push is called once from the prism usb driver (and
a few times from the prism p80211 driver). In the
prism driver it is called from hfa384x_usbin_rx -
a procedure on your stack dump.

The line of code is:

		memmove(skb_push(skb, hdrlen),
		        &usbin->rxfrm.desc.frame_control,
		        hdrlen);


The panic will happen when hdrlen is larger than the
headroom available in the skb. This points to either
a bug in the prism code somewhere, or a corrupt hdrlen
being computed.

Chris - any ideas?

Karl


> --- Dave Jenkins <[email protected]> wrote:
> > > When I had this kind of thing, I had to tweak my init
> > > script sequence to start syslog much earlier - so I
> > > could catch the messages on disk. That gave me
> > > some idea of what was going on.
> > 
> > Good idea. I'll try that.
> 
> I had another panic when I booted up this morning. I had configured
> syslog to be the first service started in runlevels 2-5 but that
> evidently isn't early enough. By default FC4 configures it to start
> just after network, presumably in case you're logging remotely. For
> local logging I suppose it could be started any time after / is
> remounted rw, which happens in rc.sysinit . Not sure how that relates
> to the timing of rc1.d etc. Karl, how do you start yours?
> 
> 
> Anyway the following was captured by birolog ;-)
> 
> hcd_submit_urb+0x2de/0x480
> error_code+0x4f/0x54
> skb_under_panic+0x59/0x67
> hfa384x_usbin_rx+0x2b7/0x304 [prism2_usb]
> hfa384x_usbin_rx+0x2c0/0x304 [prism2_usb]
> usb_hcd_giveback_urb+0x21/0x63
> uhci_finish_urb+0x84/0x266 [uhci_hcd]
> uhci_transfer_result+0x23a/0x37f [uhci_hcd]
> uhci_finish_completion+0x44/0x56 [uhci_hcd]
> uhci_scan_schedule+0xb4/0x15e [uhci_hcd]
> ide_dma_intr+0x0/0xb5
> uhci_irq+0x10b/0x6bc [uhci_hcd]
> uhci_hcd_irq+0x22/0x52
> handle_IRQ_event+0x2e/0x5a
> __do_IRQ+0x1c7/0x577
> do_IRQ+0x4a/0x82
> =====================================
> schedule+0x356/0x938
> common_interrupt+0x1a/0x20
> acpi_processor_idle+0x0/0x272
> acpi_processor_idle+0xf0/0x272
> cpu_idle+0x34/0x4c
> start_kernel+0x164/0x1be
> unknown_bootoption+0x0/0x1b6
> 
> This is with:
> lwlan 0.2.2
> D-Link DWL-122 USB
> Fedora Core 4
> 2.6.13-1.1532_FC4
> 


-----------------------------------------
Email sent from www.ntlworld.com
Virus-checked using McAfee(R) Software 
Visit www.ntlworld.com/security for more information