From: Ferry Toth <fntoth@gmail.com>
To: Felipe Balbi <balbi@kernel.org>
Cc: Wesley Cheng <wcheng@codeaurora.org>,
gregkh@linuxfoundation.org, robh+dt@kernel.org,
agross@kernel.org, bjorn.andersson@linaro.org,
frowand.list@gmail.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, jackp@codeaurora.org,
heikki.krogerus@linux.intel.com, andy.shevchenko@gmail.com
Subject: Re: [PATCH v10 0/6] Re-introduce TX FIFO resize for larger EP bursting
Date: Sun, 25 Jul 2021 15:32:54 +0200 [thread overview]
Message-ID: <6e8bb4ad-fe68-ad36-7416-2b8e10b6ae96@gmail.com> (raw)
In-Reply-To: <87a6mbudvc.fsf@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 3369 bytes --]
Hi
Op 25-07-2021 om 08:05 schreef Felipe Balbi:
> Hi,
>
> Ferry Toth <fntoth@gmail.com> writes:
>>>>>> Hardware name: Intel Corporation Merrifield/BODEGA BAY, BIOS 542
>>>>>> 2015.01.21:18.19.48
>>>>>> RIP: 0010:0x500000000
>>>>>> Code: Unable to access opcode bytes at RIP 0x4ffffffd6.
>>>>>> RSP: 0018:ffffa4d00045fc28 EFLAGS: 00010046
>>>>>> RAX: 0000000500000000 RBX: ffff8cd546aed200 RCX: 0000000000000000
>>>>>> RDX: 0000000000000000 RSI: ffff8cd547bfcae0 RDI: ffff8cd546aed200
>>>>>> RBP: ffff8cd547bfcae0 R08: 0000000000000000 R09: 0000000000000001
>>>>>> R10: ffff8cd541fd28c0 R11: 0000000000000000 R12: ffff8cd547342828
>>>>>> R13: ffff8cd546aed248 R14: 0000000000000000 R15: ffff8cd548b1d000
>>>>>> FS: 0000000000000000(0000) GS:ffff8cd57e200000(0000) knlGS:0000000000000000
>>>>>> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>>>>>> CR2: 0000000500000000 CR3: 000000000311e000 CR4: 00000000001006f0
>>>>>> Call Trace:
>>>>>> ? dwc3_remove_requests.constprop.0+0x14d/0x170
>>>>>> ? __dwc3_gadget_ep_disable+0x7a/0x160
>>>>>> ? dwc3_gadget_ep_disable+0x3d/0xd0
>>>>>> ? usb_ep_disable+0x1c/0x
>>>>>> ? u_audio_stop_capture+0x79/0x120 [u_audio]
>>>>>> ? afunc_set_alt+0x73/0x80 [usb_f_uac2]
>>>>>> ? composite_setup+0x224/0x1b90 [libcomposite]
>>>>>> ? __dwc3_gadget_kick_transfer+0x160/0x400
>>>>>> ? dwc3_gadget_ep_queue+0xf3/0x1a0
>>>>>> ? configfs_composite_setup+0x6b/0x90 [libcomposite]
>>>>>> ? configfs_composite_setup+0x6b/0x90 [libcomposite]
>>>>>> ? dwc3_ep0_interrupt+0x459/0xa40
>>>>>> ? dwc3_thread_interrupt+0x8ee/0xf40
>>>>>> ? __schedule+0x235/0x6c0
>>>>>> ? disable_irq_nosync+0x10/0x10
>>>>>> ? irq_thread_fn+0x1b/0x60
>>>>>> ? irq_thread+0xc0/0x160
>>>>>> ? irq_thread_check_affinity+0x70/0x70
>>>>>> ? irq_forced_thread_fn+0x70/0x70
>>>>>> ? kthread+0x122/0x140
>>>>>> ? set_kthread_struct+0x40/0x40
>>>>>> ? ret_from_fork+0x22/0x30
>>>>> Do you mind enabling dwc3 traces and collecting them? Trying to figure
>>>>> out how we got here.
>>>>>
>>>> I'll try if I can get the same error by booting with USB in host mode
>>>> and then switch to device mode. If so I can enable traces and collect as
>>>> you explained me before.
>>>>
>>>> I'll try before monday, as then I fly for a holiday and will not be
>>>> available before rc5.
>>> you can enable all of those with kernel cmdline :-)
>>>
>>> https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html
>>>
>>> you need ftrace_dump_on_oops=1 and also need the correct options on
>>> trace_buf_size and trace_event.
>>>
>> On Edison-Arduino I have a switch to go to device mode, after which
>> udev triggers a script configure gadgets through configfs.
>>
>> I tried to log following these instructions:
>>
>> https://www.kernel.org/doc/html/latest/driver-api/usb/dwc3.html#reporting-bugs <https://www.kernel.org/doc/html/latest/driver-api/usb/dwc3.html#reporting-bugs>
>>
>> Unfortunately the kernel crashes so badly I can not get to the ` cp
>> /t/trace /root/trace.txt` line (after a while the watchdog kicks).
>>
>> What to do next?
> Pass ftrace_dump_on_oops to kernel cmdline.
>
No sure if I did this right, on oops everything is pushed to console
(115k2 serial), I hope nothing essential is lost.
I copied the screen buffer to file see attached.
[-- Attachment #2: dump-on-oops.7z --]
[-- Type: application/x-7z-compressed, Size: 35551 bytes --]
next prev parent reply other threads:[~2021-07-25 13:33 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 9:58 [PATCH v10 0/6] Re-introduce TX FIFO resize for larger EP bursting Wesley Cheng
2021-06-17 9:58 ` [PATCH v10 1/6] usb: gadget: udc: core: Introduce check_config to verify USB configuration Wesley Cheng
2021-06-17 11:09 ` Greg KH
2021-06-22 5:27 ` Wesley Cheng
2021-06-17 9:58 ` [PATCH v10 2/6] usb: gadget: configfs: Check USB configuration before adding Wesley Cheng
2021-06-17 11:07 ` Greg KH
2021-06-22 5:27 ` Wesley Cheng
2021-06-22 6:05 ` Greg KH
2021-06-23 9:38 ` Wesley Cheng
2021-06-23 11:35 ` Greg KH
2021-06-23 21:44 ` Wesley Cheng
2021-06-24 12:09 ` Greg KH
2021-06-17 9:58 ` [PATCH v10 3/6] usb: dwc3: Resize TX FIFOs to meet EP bursting requirements Wesley Cheng
2021-06-17 11:10 ` Greg KH
2021-06-22 5:27 ` Wesley Cheng
2021-06-22 6:06 ` Greg KH
2021-06-17 17:56 ` kernel test robot
2021-06-17 18:01 ` kernel test robot
2021-06-17 9:58 ` [PATCH v10 4/6] of: Add stub for of_add_property() Wesley Cheng
2021-06-17 9:58 ` [PATCH v10 5/6] usb: dwc3: dwc3-qcom: Enable tx-fifo-resize property by default Wesley Cheng
2021-06-17 11:12 ` Greg KH
2021-06-17 18:04 ` kernel test robot
2021-06-18 4:35 ` Jack Pham
2021-06-17 9:58 ` [PATCH v10 6/6] dt-bindings: usb: dwc3: Update dwc3 TX fifo properties Wesley Cheng
2021-06-17 21:01 ` [PATCH v10 0/6] Re-introduce TX FIFO resize for larger EP bursting Ferry Toth
2021-06-17 21:48 ` Wesley Cheng
[not found] ` <f5ed0ee7-e333-681f-0f1a-d0227562204b@gmail.com>
2021-06-17 22:25 ` Wesley Cheng
2021-06-19 12:40 ` Ferry Toth
2021-06-22 18:38 ` Wesley Cheng
2021-06-22 20:09 ` Ferry Toth
2021-06-22 22:00 ` Wesley Cheng
2021-06-22 22:12 ` Ferry Toth
2021-06-23 7:50 ` Wesley Cheng
2021-06-25 21:10 ` Ferry Toth
2021-06-25 21:19 ` Wesley Cheng
2021-06-25 22:31 ` Ferry Toth
2021-07-22 18:43 ` Ferry Toth
2021-07-23 6:59 ` Felipe Balbi
[not found] ` <d9aef50c-4bd1-4957-13d8-0b6a14b9fcd0@gmail.com>
2021-07-23 11:23 ` Felipe Balbi
2021-07-24 20:59 ` Ferry Toth
2021-07-24 21:19 ` Andy Shevchenko
2021-07-24 22:56 ` Ferry Toth
2021-07-25 6:05 ` Felipe Balbi
2021-07-25 13:32 ` Ferry Toth [this message]
2021-07-25 14:05 ` Felipe Balbi
2021-07-25 16:54 ` Ferry Toth
2021-07-26 5:57 ` Felipe Balbi
2021-07-26 14:33 ` Wesley Cheng
2021-07-26 21:51 ` Ferry Toth
2021-08-15 20:56 ` Ferry Toth
2021-08-16 5:18 ` Felipe Balbi
2021-08-17 22:00 ` Ferry Toth
2021-08-18 19:07 ` Ferry Toth
2021-08-19 7:51 ` Pavel Hofman
2021-08-19 20:10 ` Ferry Toth
2021-08-19 21:04 ` Pavel Hofman
2021-08-21 2:57 ` Thinh Nguyen
2021-08-22 20:10 ` Ferry Toth
2021-08-23 7:57 ` Pavel Hofman
2021-09-02 0:28 ` Jack Pham
2021-09-02 22:58 ` Thinh Nguyen
2021-08-22 19:43 ` Ferry Toth
2021-08-23 14:59 ` Pavel Hofman
2021-08-23 15:21 ` Andy Shevchenko
2021-08-23 15:34 ` Pavel Hofman
2021-08-23 18:54 ` Ferry Toth
2021-08-23 22:50 ` Thinh Nguyen
2021-08-24 5:39 ` Pavel Hofman
2021-08-24 13:44 ` Ferry Toth
[not found] ` <7ffab777-0f77-f949-f70f-7bf34c504381@gmail.com>
2021-08-26 1:18 ` Thinh Nguyen
2021-08-26 7:30 ` Ferry Toth
2021-08-26 13:35 ` Pavel Hofman
2021-08-19 7:55 ` Andy Shevchenko
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=6e8bb4ad-fe68-ad36-7416-2b8e10b6ae96@gmail.com \
--to=fntoth@gmail.com \
--cc=agross@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jackp@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wcheng@codeaurora.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;
as well as URLs for NNTP newsgroup(s).