Re: Slow down problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



another trick is install the perf package, and then run "perf top" and
this should show you where the kernel is spending its time (it might
tell us the driver and the driver will tell us what hardware it is).

On Mon, Oct 5, 2020 at 6:22 PM ToddAndMargo via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> On 2020-10-05 16:07, Mike Wright wrote:
> > On 10/5/20 3:57 PM, ToddAndMargo via users wrote:
> >> On 2020-10-05 15:48, Mike Wright wrote:
> >>> On 10/5/20 3:37 PM, ToddAndMargo via users wrote:
> >>>> On 2020-10-05 15:31, Mike Wright wrote:
> >>>>> On 10/5/20 3:21 PM, ToddAndMargo via users wrote:
> >>>>>> On 2020-10-05 15:09, Roger Heflin wrote:
> >>>>>>> you need output from "top"
> >>>>>>
> >>>>>> It is the same as htop with less data.  Both
> >>>>>> show virtually no activity.  But htop does show
> >>>>>> core 2 being swamped with something
> >>>>>
> >>>>> When running "top" press "1".  It will give you specifics on each
> >>>>> core/thread.
> >>>>
> >>>> "top" with "1" pressed:
> >>>> https://ibb.co/mCFKRF7
> >>>>
> >>>> Not really seeing anything useful.  Maybe I am missing something.
> >>>
> >>> Look at %Cpu1.  It is using 91.5% of its time servicing hardware
> >>> interrupts.  I looked at two different boxes and neither of them show
> >>> anything > 0.0 on 4 cores or 12 cores.
> >>>
> >>> Maybe it's time to start unplugging devices until that time comes
> >>> down. Then you'll have a culprit.
> >>
> >> I do not understand.  Cpu 2 is the issue, not cpu 1.
> >>
> >> And what do you mean by devices?  I do not even have an flash
> >> drives plugged in.
> >
> > Part 2 :/
> >
> > If you have no external devices then it must be internal.  Could a drive
> > be failing?  Motherboard?
>
> Perhaps.  But a reboot would not clear it up if that
> was the case.
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux