Understanding “serial8250: too much work for irq4” kernel message

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
4
down vote

favorite
3












dmesg shows lots of messages from serial8250:



$ dmesg | grep -i serial
[ 0.884481] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 6.584431] systemd[1]: Created slice system-serialx2dgetty.slice.
[633232.317222] serial8250: too much work for irq4
[633232.453355] serial8250: too much work for irq4
[633248.378343] serial8250: too much work for irq4
...


I have not seen this message before. What does it generally mean? Should I be worried?



(From my research, it is not distribution specific, but in case it is relevant, I see the messages on an EC2 instance running Ubuntu 16.04.)










share|improve this question





















  • Why does an EC2 instance need a serial driver? What is connected to those serial "ports"? (Guess: Something else is causing lots of irq4 signals, and the driver gets confused. Solution: disable driver, as it's probably not needed).
    – dirkt
    Aug 22 '17 at 9:40










  • Maybe that can happen if you log in via SSH and interact with the console?
    – Philipp Claßen
    Aug 22 '17 at 10:06






  • 2




    The serial port in an EC2 instance is the EC2 "console output", dirkt.
    – JdeBP
    Aug 22 '17 at 11:30














up vote
4
down vote

favorite
3












dmesg shows lots of messages from serial8250:



$ dmesg | grep -i serial
[ 0.884481] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 6.584431] systemd[1]: Created slice system-serialx2dgetty.slice.
[633232.317222] serial8250: too much work for irq4
[633232.453355] serial8250: too much work for irq4
[633248.378343] serial8250: too much work for irq4
...


I have not seen this message before. What does it generally mean? Should I be worried?



(From my research, it is not distribution specific, but in case it is relevant, I see the messages on an EC2 instance running Ubuntu 16.04.)










share|improve this question





















  • Why does an EC2 instance need a serial driver? What is connected to those serial "ports"? (Guess: Something else is causing lots of irq4 signals, and the driver gets confused. Solution: disable driver, as it's probably not needed).
    – dirkt
    Aug 22 '17 at 9:40










  • Maybe that can happen if you log in via SSH and interact with the console?
    – Philipp Claßen
    Aug 22 '17 at 10:06






  • 2




    The serial port in an EC2 instance is the EC2 "console output", dirkt.
    – JdeBP
    Aug 22 '17 at 11:30












up vote
4
down vote

favorite
3









up vote
4
down vote

favorite
3






3





dmesg shows lots of messages from serial8250:



$ dmesg | grep -i serial
[ 0.884481] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 6.584431] systemd[1]: Created slice system-serialx2dgetty.slice.
[633232.317222] serial8250: too much work for irq4
[633232.453355] serial8250: too much work for irq4
[633248.378343] serial8250: too much work for irq4
...


I have not seen this message before. What does it generally mean? Should I be worried?



(From my research, it is not distribution specific, but in case it is relevant, I see the messages on an EC2 instance running Ubuntu 16.04.)










share|improve this question













dmesg shows lots of messages from serial8250:



$ dmesg | grep -i serial
[ 0.884481] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 6.584431] systemd[1]: Created slice system-serialx2dgetty.slice.
[633232.317222] serial8250: too much work for irq4
[633232.453355] serial8250: too much work for irq4
[633248.378343] serial8250: too much work for irq4
...


I have not seen this message before. What does it generally mean? Should I be worried?



(From my research, it is not distribution specific, but in case it is relevant, I see the messages on an EC2 instance running Ubuntu 16.04.)







kernel dmesg






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Aug 22 '17 at 8:45









Philipp Claßen

1,28231829




1,28231829











  • Why does an EC2 instance need a serial driver? What is connected to those serial "ports"? (Guess: Something else is causing lots of irq4 signals, and the driver gets confused. Solution: disable driver, as it's probably not needed).
    – dirkt
    Aug 22 '17 at 9:40










  • Maybe that can happen if you log in via SSH and interact with the console?
    – Philipp Claßen
    Aug 22 '17 at 10:06






  • 2




    The serial port in an EC2 instance is the EC2 "console output", dirkt.
    – JdeBP
    Aug 22 '17 at 11:30
















  • Why does an EC2 instance need a serial driver? What is connected to those serial "ports"? (Guess: Something else is causing lots of irq4 signals, and the driver gets confused. Solution: disable driver, as it's probably not needed).
    – dirkt
    Aug 22 '17 at 9:40










  • Maybe that can happen if you log in via SSH and interact with the console?
    – Philipp Claßen
    Aug 22 '17 at 10:06






  • 2




    The serial port in an EC2 instance is the EC2 "console output", dirkt.
    – JdeBP
    Aug 22 '17 at 11:30















Why does an EC2 instance need a serial driver? What is connected to those serial "ports"? (Guess: Something else is causing lots of irq4 signals, and the driver gets confused. Solution: disable driver, as it's probably not needed).
– dirkt
Aug 22 '17 at 9:40




Why does an EC2 instance need a serial driver? What is connected to those serial "ports"? (Guess: Something else is causing lots of irq4 signals, and the driver gets confused. Solution: disable driver, as it's probably not needed).
– dirkt
Aug 22 '17 at 9:40












Maybe that can happen if you log in via SSH and interact with the console?
– Philipp Claßen
Aug 22 '17 at 10:06




Maybe that can happen if you log in via SSH and interact with the console?
– Philipp Claßen
Aug 22 '17 at 10:06




2




2




The serial port in an EC2 instance is the EC2 "console output", dirkt.
– JdeBP
Aug 22 '17 at 11:30




The serial port in an EC2 instance is the EC2 "console output", dirkt.
– JdeBP
Aug 22 '17 at 11:30










2 Answers
2






active

oldest

votes

















up vote
8
down vote



accepted










There is nothing wrong with your kernel or device drivers. The problem is with your machine hardware. The problem is that it is impossible hardware.



This is an error in several virtualization platforms (including at least XEN, QEMU, and VirtualBox) that has been plaguing people for at least a decade. The problem is that the UART hardware that is emulated by various brands of virtual machine behaves impossibly, sending characters at an impossibly fast line speed. To the kernel, this is indistinguishable from faulty real UART hardware that is continually raising an interrupt for an empty output buffer/full input buffer. (Such faulty real hardwares exist, and you will find embedded Linux people also discussing this problem here and there.) The kernel pushes the data out/pulls the data in, and the UART is immediately raising an interrupt saying that it is ready for more.



H. Peter Anvin provided a patch to fix QEMU in 2008. You'll need to ask Amazon when EC2 is going to catch up.



Further reading



  • Alan Cox (2008-01-12). Re: [PATCH] serial: remove "too much work for irq" printk. Linux Kernel Mailing List.

  • H. Peter Anvin (2008-02-07). Re: 2.6.24 says "serial8250: too much work for irq4" a lot.. Linux Kernel Mailing List.

  • Casey Dahlin (2009-05-15). 'serial8250: too much work for irq4' message when viewing serial console on SMP full-virtualized xen domU. 501026. Red Hat Bugzilla.

  • Sibiao Luo (2013-07-21). guest kernel will print many "serial8250: too much work for irq3" when using kvm with isa-serial. 986761. Red Hat Bugzilla.

  • schinkelm (2008-12-16). serial port in linux guest gives "serial8250: too much work for irq4". 2752. VirtualBox bugs.

  • Marc PF (2015-09-05). EC2 instance becomes unresponsive. AWS Developer Forums.





share|improve this answer




















  • A patch came out in 2008? and "You'll need to ask Amazon when EC2 is going to catch up".. I'm getting this error on Azure on an Ubuntu Server in Azure (July/18) Linux 4.15.0-1013-azure x86_64.
    – KevinY
    Jul 10 at 14:12


















up vote
0
down vote













Just to add a data-point in support of JdeBP: I've been seeing this in my XEN VMs, and I've only been seeing it when I run dmesg. My guess is that when I run dmesg, I'm overloading the virtual UART (and manifesting the bug described above), because dmesg is spewing a whole bunch of stuff at once. In any case, it's a non-problem for me, just a red herring.






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f387600%2funderstanding-serial8250-too-much-work-for-irq4-kernel-message%23new-answer', 'question_page');

    );

    Post as a guest






























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    8
    down vote



    accepted










    There is nothing wrong with your kernel or device drivers. The problem is with your machine hardware. The problem is that it is impossible hardware.



    This is an error in several virtualization platforms (including at least XEN, QEMU, and VirtualBox) that has been plaguing people for at least a decade. The problem is that the UART hardware that is emulated by various brands of virtual machine behaves impossibly, sending characters at an impossibly fast line speed. To the kernel, this is indistinguishable from faulty real UART hardware that is continually raising an interrupt for an empty output buffer/full input buffer. (Such faulty real hardwares exist, and you will find embedded Linux people also discussing this problem here and there.) The kernel pushes the data out/pulls the data in, and the UART is immediately raising an interrupt saying that it is ready for more.



    H. Peter Anvin provided a patch to fix QEMU in 2008. You'll need to ask Amazon when EC2 is going to catch up.



    Further reading



    • Alan Cox (2008-01-12). Re: [PATCH] serial: remove "too much work for irq" printk. Linux Kernel Mailing List.

    • H. Peter Anvin (2008-02-07). Re: 2.6.24 says "serial8250: too much work for irq4" a lot.. Linux Kernel Mailing List.

    • Casey Dahlin (2009-05-15). 'serial8250: too much work for irq4' message when viewing serial console on SMP full-virtualized xen domU. 501026. Red Hat Bugzilla.

    • Sibiao Luo (2013-07-21). guest kernel will print many "serial8250: too much work for irq3" when using kvm with isa-serial. 986761. Red Hat Bugzilla.

    • schinkelm (2008-12-16). serial port in linux guest gives "serial8250: too much work for irq4". 2752. VirtualBox bugs.

    • Marc PF (2015-09-05). EC2 instance becomes unresponsive. AWS Developer Forums.





    share|improve this answer




















    • A patch came out in 2008? and "You'll need to ask Amazon when EC2 is going to catch up".. I'm getting this error on Azure on an Ubuntu Server in Azure (July/18) Linux 4.15.0-1013-azure x86_64.
      – KevinY
      Jul 10 at 14:12















    up vote
    8
    down vote



    accepted










    There is nothing wrong with your kernel or device drivers. The problem is with your machine hardware. The problem is that it is impossible hardware.



    This is an error in several virtualization platforms (including at least XEN, QEMU, and VirtualBox) that has been plaguing people for at least a decade. The problem is that the UART hardware that is emulated by various brands of virtual machine behaves impossibly, sending characters at an impossibly fast line speed. To the kernel, this is indistinguishable from faulty real UART hardware that is continually raising an interrupt for an empty output buffer/full input buffer. (Such faulty real hardwares exist, and you will find embedded Linux people also discussing this problem here and there.) The kernel pushes the data out/pulls the data in, and the UART is immediately raising an interrupt saying that it is ready for more.



    H. Peter Anvin provided a patch to fix QEMU in 2008. You'll need to ask Amazon when EC2 is going to catch up.



    Further reading



    • Alan Cox (2008-01-12). Re: [PATCH] serial: remove "too much work for irq" printk. Linux Kernel Mailing List.

    • H. Peter Anvin (2008-02-07). Re: 2.6.24 says "serial8250: too much work for irq4" a lot.. Linux Kernel Mailing List.

    • Casey Dahlin (2009-05-15). 'serial8250: too much work for irq4' message when viewing serial console on SMP full-virtualized xen domU. 501026. Red Hat Bugzilla.

    • Sibiao Luo (2013-07-21). guest kernel will print many "serial8250: too much work for irq3" when using kvm with isa-serial. 986761. Red Hat Bugzilla.

    • schinkelm (2008-12-16). serial port in linux guest gives "serial8250: too much work for irq4". 2752. VirtualBox bugs.

    • Marc PF (2015-09-05). EC2 instance becomes unresponsive. AWS Developer Forums.





    share|improve this answer




















    • A patch came out in 2008? and "You'll need to ask Amazon when EC2 is going to catch up".. I'm getting this error on Azure on an Ubuntu Server in Azure (July/18) Linux 4.15.0-1013-azure x86_64.
      – KevinY
      Jul 10 at 14:12













    up vote
    8
    down vote



    accepted







    up vote
    8
    down vote



    accepted






    There is nothing wrong with your kernel or device drivers. The problem is with your machine hardware. The problem is that it is impossible hardware.



    This is an error in several virtualization platforms (including at least XEN, QEMU, and VirtualBox) that has been plaguing people for at least a decade. The problem is that the UART hardware that is emulated by various brands of virtual machine behaves impossibly, sending characters at an impossibly fast line speed. To the kernel, this is indistinguishable from faulty real UART hardware that is continually raising an interrupt for an empty output buffer/full input buffer. (Such faulty real hardwares exist, and you will find embedded Linux people also discussing this problem here and there.) The kernel pushes the data out/pulls the data in, and the UART is immediately raising an interrupt saying that it is ready for more.



    H. Peter Anvin provided a patch to fix QEMU in 2008. You'll need to ask Amazon when EC2 is going to catch up.



    Further reading



    • Alan Cox (2008-01-12). Re: [PATCH] serial: remove "too much work for irq" printk. Linux Kernel Mailing List.

    • H. Peter Anvin (2008-02-07). Re: 2.6.24 says "serial8250: too much work for irq4" a lot.. Linux Kernel Mailing List.

    • Casey Dahlin (2009-05-15). 'serial8250: too much work for irq4' message when viewing serial console on SMP full-virtualized xen domU. 501026. Red Hat Bugzilla.

    • Sibiao Luo (2013-07-21). guest kernel will print many "serial8250: too much work for irq3" when using kvm with isa-serial. 986761. Red Hat Bugzilla.

    • schinkelm (2008-12-16). serial port in linux guest gives "serial8250: too much work for irq4". 2752. VirtualBox bugs.

    • Marc PF (2015-09-05). EC2 instance becomes unresponsive. AWS Developer Forums.





    share|improve this answer












    There is nothing wrong with your kernel or device drivers. The problem is with your machine hardware. The problem is that it is impossible hardware.



    This is an error in several virtualization platforms (including at least XEN, QEMU, and VirtualBox) that has been plaguing people for at least a decade. The problem is that the UART hardware that is emulated by various brands of virtual machine behaves impossibly, sending characters at an impossibly fast line speed. To the kernel, this is indistinguishable from faulty real UART hardware that is continually raising an interrupt for an empty output buffer/full input buffer. (Such faulty real hardwares exist, and you will find embedded Linux people also discussing this problem here and there.) The kernel pushes the data out/pulls the data in, and the UART is immediately raising an interrupt saying that it is ready for more.



    H. Peter Anvin provided a patch to fix QEMU in 2008. You'll need to ask Amazon when EC2 is going to catch up.



    Further reading



    • Alan Cox (2008-01-12). Re: [PATCH] serial: remove "too much work for irq" printk. Linux Kernel Mailing List.

    • H. Peter Anvin (2008-02-07). Re: 2.6.24 says "serial8250: too much work for irq4" a lot.. Linux Kernel Mailing List.

    • Casey Dahlin (2009-05-15). 'serial8250: too much work for irq4' message when viewing serial console on SMP full-virtualized xen domU. 501026. Red Hat Bugzilla.

    • Sibiao Luo (2013-07-21). guest kernel will print many "serial8250: too much work for irq3" when using kvm with isa-serial. 986761. Red Hat Bugzilla.

    • schinkelm (2008-12-16). serial port in linux guest gives "serial8250: too much work for irq4". 2752. VirtualBox bugs.

    • Marc PF (2015-09-05). EC2 instance becomes unresponsive. AWS Developer Forums.






    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Aug 22 '17 at 12:18









    JdeBP

    29.3k460136




    29.3k460136











    • A patch came out in 2008? and "You'll need to ask Amazon when EC2 is going to catch up".. I'm getting this error on Azure on an Ubuntu Server in Azure (July/18) Linux 4.15.0-1013-azure x86_64.
      – KevinY
      Jul 10 at 14:12

















    • A patch came out in 2008? and "You'll need to ask Amazon when EC2 is going to catch up".. I'm getting this error on Azure on an Ubuntu Server in Azure (July/18) Linux 4.15.0-1013-azure x86_64.
      – KevinY
      Jul 10 at 14:12
















    A patch came out in 2008? and "You'll need to ask Amazon when EC2 is going to catch up".. I'm getting this error on Azure on an Ubuntu Server in Azure (July/18) Linux 4.15.0-1013-azure x86_64.
    – KevinY
    Jul 10 at 14:12





    A patch came out in 2008? and "You'll need to ask Amazon when EC2 is going to catch up".. I'm getting this error on Azure on an Ubuntu Server in Azure (July/18) Linux 4.15.0-1013-azure x86_64.
    – KevinY
    Jul 10 at 14:12













    up vote
    0
    down vote













    Just to add a data-point in support of JdeBP: I've been seeing this in my XEN VMs, and I've only been seeing it when I run dmesg. My guess is that when I run dmesg, I'm overloading the virtual UART (and manifesting the bug described above), because dmesg is spewing a whole bunch of stuff at once. In any case, it's a non-problem for me, just a red herring.






    share|improve this answer
























      up vote
      0
      down vote













      Just to add a data-point in support of JdeBP: I've been seeing this in my XEN VMs, and I've only been seeing it when I run dmesg. My guess is that when I run dmesg, I'm overloading the virtual UART (and manifesting the bug described above), because dmesg is spewing a whole bunch of stuff at once. In any case, it's a non-problem for me, just a red herring.






      share|improve this answer






















        up vote
        0
        down vote










        up vote
        0
        down vote









        Just to add a data-point in support of JdeBP: I've been seeing this in my XEN VMs, and I've only been seeing it when I run dmesg. My guess is that when I run dmesg, I'm overloading the virtual UART (and manifesting the bug described above), because dmesg is spewing a whole bunch of stuff at once. In any case, it's a non-problem for me, just a red herring.






        share|improve this answer












        Just to add a data-point in support of JdeBP: I've been seeing this in my XEN VMs, and I've only been seeing it when I run dmesg. My guess is that when I run dmesg, I'm overloading the virtual UART (and manifesting the bug described above), because dmesg is spewing a whole bunch of stuff at once. In any case, it's a non-problem for me, just a red herring.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Aug 10 at 15:49









        pdelong

        11




        11



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f387600%2funderstanding-serial8250-too-much-work-for-irq4-kernel-message%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            Peggy Mitchell

            Palaiologos

            The Forum (Inglewood, California)