Re: rtl8xxxu 4.4.5(from f23): I get a panic adding a new device to the driver

2016-03-20 Thread Greg KH
On Thu, Mar 17, 2016 at 09:01:25PM +0100, poma wrote: > On 17.03.2016 19:02, Jes Sorensen wrote: > > Jes Sorensen writes: > >> Xose Vazquez Perez writes: > >>> Hi, > >>> > >>> If I do: > >>> # echo "0bda 8176" > /sys/bus/usb/drivers/rtl8xxxu/new_id > >> > >> Hi Xose, > >> > >> Yes please don't do

Re: rtl8xxxu 4.4.5(from f23): I get a panic adding a new device to the driver

2016-03-19 Thread Jes Sorensen
poma writes: > On 17.03.2016 19:02, Jes Sorensen wrote: >> Jes Sorensen writes: >>> Xose Vazquez Perez writes: Hi, If I do: # echo "0bda 8176" > /sys/bus/usb/drivers/rtl8xxxu/new_id >>> >>> Hi Xose, >>> >>> Yes please don't do that. The rtl8xxxu driver relies on the .driver_i

Re: rtl8xxxu 4.4.5(from f23): I get a panic adding a new device to the driver

2016-03-19 Thread Jes Sorensen
Xose Vazquez Perez writes: > Hi, > > If I do: > # echo "0bda 8176" > /sys/bus/usb/drivers/rtl8xxxu/new_id Hi Xose, Yes please don't do that. The rtl8xxxu driver relies on the .driver_info field in struct use_device_id to carry information for the different types of devices. If you hot add a devi

Re: rtl8xxxu 4.4.5(from f23): I get a panic adding a new device to the driver

2016-03-19 Thread poma
On 17.03.2016 19:02, Jes Sorensen wrote: > Jes Sorensen writes: >> Xose Vazquez Perez writes: >>> Hi, >>> >>> If I do: >>> # echo "0bda 8176" > /sys/bus/usb/drivers/rtl8xxxu/new_id >> >> Hi Xose, >> >> Yes please don't do that. The rtl8xxxu driver relies on the .driver_info >> field in struct use

Re: rtl8xxxu 4.4.5(from f23): I get a panic adding a new device to the driver

2016-03-19 Thread Alan Stern
On Thu, 17 Mar 2016, poma wrote: > On 17.03.2016 19:02, Jes Sorensen wrote: > > Jes Sorensen writes: > >> Xose Vazquez Perez writes: > >>> Hi, > >>> > >>> If I do: > >>> # echo "0bda 8176" > /sys/bus/usb/drivers/rtl8xxxu/new_id > >> > >> Hi Xose, > >> > >> Yes please don't do that. The rtl8xxxu

Re: rtl8xxxu 4.4.5(from f23): I get a panic adding a new device to the driver

2016-03-19 Thread Jes Sorensen
Greg KH writes: > On Thu, Mar 17, 2016 at 09:01:25PM +0100, poma wrote: >> On 17.03.2016 19:02, Jes Sorensen wrote: >> > Jes Sorensen writes: >> >> Xose Vazquez Perez writes: >> >>> Hi, >> >>> >> >>> If I do: >> >>> # echo "0bda 8176" > /sys/bus/usb/drivers/rtl8xxxu/new_id >> >> >> >> Hi Xose, >

Re: rtl8xxxu 4.4.5(from f23): I get a panic adding a new device to the driver

2016-03-19 Thread Jes Sorensen
Jes Sorensen writes: > Xose Vazquez Perez writes: >> Hi, >> >> If I do: >> # echo "0bda 8176" > /sys/bus/usb/drivers/rtl8xxxu/new_id > > Hi Xose, > > Yes please don't do that. The rtl8xxxu driver relies on the .driver_info > field in struct use_device_id to carry information for the different > t

rtl8xxxu 4.4.5(from f23): I get a panic adding a new device to the driver

2016-03-15 Thread Xose Vazquez Perez
Hi, If I do: # echo "0bda 8176" > /sys/bus/usb/drivers/rtl8xxxu/new_id I get: ---dmesg--- usbcore: registered new interface driver rtl8xxxu BUG: unable to handle kernel NULL pointer dereference at (null) IP: [] rtl8xxxu_probe+0x810/0x22a0 [rtl8xxxu] PGD 0 Oops: [#1] SMP Modules linked in: rt