rum driver triggers panic after wlan update

[Paul B. Mahol]

Look usb/124758, I think it is already known problem.

On 6/23/08, Thomas Sparrevohn <Thomas.Sparrevohn at btinternet.com> wrote:
> Hi
>
>
>
> Before I send a pr in - I just wanted to check whether the issue is known
>
>
>
> A seemly random period time after I plugin the rum0 device the kernel
> crashes
>
>
>
> rum0: <Belkin Belkin 54g USB Network Adapter, class 0/0, rev 2.00/0.01, addr
> 5> on uhub1
>
> rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528
>
> rum0: WARNING: using obsoleted IFF_NEEDSGIANT flag
>
> rum0: bpf attached
>
> rum0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
>
> rum0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps
> 36Mbps 48Mbps 54Mbps
>
> wlan0: bpf attached
>
> wlan0: Ethernet address: 00:17:3f:72:40:90
>
> wlan0: bpf attached
>
> rum0: need multicast update callback
>
> rum0: need multicast update callback
>
>
>
>
>
> Fatal trap 12: page fault while in kernel mode
>
> cpuid = 1; apic id = 01
>
> fault virtual address   = 0x40
>
> fault code        = supervisor read data, page not present
>
> instruction pointer     = 0x8:0xffffffff803e082e
>
> stack pointer             = 0x10:0xffffffffd75bfb50
>
> frame pointer             = 0x10:0xffffffffd75bfb80
>
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>
>                   = DPL 0, pres 1, long 1, def32 0, gran 1
>
> processor eflags  = interrupt enabled, resume, IOPL = 0
>
> current process         = 12 (irq22: ehci0)
>
>
>
> It I boot the machine USB rum0 device attached - The crash comes normally
> pretty instantaneously (dmesg_8.txt)
>
>
>
> wlan0: Ethernet address: 00:17:3f:72:40:90
>
> rum0: need multicast update callback
>
> rum0: could not transmit buffer: SHORT_XFER
>
>
>
>
>
> Fatal trap 12: page fault while in kernel mode
>
> cpuid = 1; apic id = 01
>
> fault virtual address   = 0x8
>
> fault code        = supervisor read data, page not present
>
> instruction pointer     = 0x8:0xffffffff803e0712
>
> stack pointer             = 0x10:0xffffffffd75bfb50
>
> frame pointer             = 0x10:0xffffffffd75bfb80
>
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>
>                   = DPL 0, pres 1, long 1, def32 0, gran 1
>
> processor eflags  = interrupt enabled, resume, IOPL = 0
>
> current process         = 12 (irq22: ehci0)
>
> Physical memory: 4076 MB
>
> Dumping 317 MB: 302 286 270 254 238 222 206 190 174 158 142 126 110 94 78 62
> 46 30 14
>
>
>
> If I use a kernel without debugging - the kernel simply freezes totally - no
> panic - no nothing - does anybody have any idea?
>
>
>
>
>
>