public inbox for kernelnewbies@kernelnewbies.org
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Forest Bond <forest@alittletooquiet.net>,
	kernelnewbies@kernelnewbies.org
Subject: Re: Linux driver of vt6656 from staging area causes system to freeze.
Date: Thu, 3 Feb 2022 20:19:39 +0100	[thread overview]
Message-ID: <b4a14ef0-fd8e-d218-28ac-a351ca89ed87@gmail.com> (raw)
In-Reply-To: <YfuYXS23CNEf3nIN@kroah.com>

On 2/3/22 09:54, Greg Kroah-Hartman wrote:
> On Thu, Feb 03, 2022 at 01:41:11AM +0100, Philipp Hortmann wrote:
>> I managed to get a device vt6656 (USB WiFi adapter). The device works OK
>> when the computer is started and driver loaded. When the WLAN is disabled
>> the system freezes often.
>>
>> I am using ubuntu 20.04 with kernel 5.17.0-rc1 x86_64
>> branch: staging-testing
>>
>> After some tries I found out that it is a function in vnt_stop() main_usb.c
>> with the following line that is causing this.
>> usb_kill_urb(priv→interrupt_urb);
>> But this memory is after this line still in use.
> 
> What "memory" do you mean?

They are calling usb_kill_urb(priv→interrupt_urb); while using 
priv→interrupt_urb and maybe also starting new 
usb_submit_urb(priv->interrupt_urb, GFP_ATOMIC);

Thanks for your quick answer.

Bye Philipp


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2022-02-03 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  0:41 Linux driver of vt6656 from staging area causes system to freeze Philipp Hortmann
2022-02-03  8:54 ` Greg Kroah-Hartman
2022-02-03 19:19   ` Philipp Hortmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b4a14ef0-fd8e-d218-28ac-a351ca89ed87@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=forest@alittletooquiet.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernelnewbies@kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox