From: Simon Lindhorst <s.lindhorst@wut.de>
To: kernelnewbies@kernelnewbies.org
Subject: mabe a bug in kernel 5.4 since patchlevel 159 - dma error because use ttynull?
Date: Thu, 13 Oct 2022 12:48:01 +0200 [thread overview]
Message-ID: <6590dbfc-1d55-71f0-b26f-73c60dee97ec@wut.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2255 bytes --]
Hello all,
when I updated my Kernel from version 5.4.155 to 5.4.215 I get an
strange xhci error:
/xhci-hcd f10f0000.usb3: ERROR unknown event type 37//
//xhci-hcd f10f0000.usb3: ERROR Transfer event TRB DMA ptr not part of
current TD ep_index 2 comp_code 13//
/
After a lot of this messages, my hardware makes a reboot without any
more outputs.
The error only occures when i add /console=null/ to my kernel bootargs.
When I add instead console=/ttyS0,115200/ no error occured.
Now I go back in kernelversions. The error occured first in version
5.4.159. Between patchlevel 158 and 159 there is a change:
/--- linux-5.4.158/kernel/printk/printk.c 2021-11-06
13:59:45.000000000 +0100//
//+++ linux-5.4.159/kernel/printk/printk.c 2021-11-12
14:43:05.000000000 +0100//
//@@ -2193,8 +2193,15 @@//
// char *s, *options, *brl_options = NULL;//
// int idx;//
////
//- if (str[0] == 0)//
//+ /*//
//+ * console="" or console=null have been suggested as a way to//
//+ * disable console output. Use ttynull that has been created//
//+ * for exacly this purpose.//
//+ *///
//+ if (str[0] == 0 || strcmp(str, "null") == 0) {//
//+ __add_preferred_console("ttynull", 0, NULL, NULL);//
// return 1;//
//+ }//
////
// if (_braille_console_setup(&str, &brl_options))//
// return 1;/
I checked my kernelconfig and found that I have no ttynull device
configured (/CONFIG_NULL_TTY=n/). Add /CONFIG_NULL_TTY=y/ to my
kernelconfig doesn't made a change.
When I undo the change above, everything works fine.
Does anybody know, what could be the main trigger for the error above?
Regards,
Sarah
-- Unsere Aussagen koennen Irrtuemer und Missverstaendnisse enthalten.
Bitte pruefen Sie die Aussagen fuer Ihren Fall, bevor Sie Entscheidungen
auf Grundlage dieser Aussagen treffen.
Wiesemann & Theis GmbH, Porschestr. 12, D-42279 Wuppertal
Geschaeftsfuehrer: Dipl.-Ing. Ruediger Theis
Registergericht: Amtsgericht Wuppertal, HRB 6377
Infos zum Datenschutz: https://www.wut.de/datenschutz
Tel. +49-202/2680-0, Fax +49-202/2680-265, https://www.wut.de
[-- Attachment #1.2: Type: text/html, Size: 3294 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2022-10-13 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 10:48 Simon Lindhorst [this message]
2022-10-13 15:11 ` mabe a bug in kernel 5.4 since patchlevel 159 - dma error because use ttynull? jim.cromie
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=6590dbfc-1d55-71f0-b26f-73c60dee97ec@wut.de \
--to=s.lindhorst@wut.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).