marcoNLD: FixCommonProblems Reported "one or more call traces"

[marcoNLD]

i have the same error and no idea where or how to correct it.

my system runs fine

 

so if anyone will check i would be very happy.

marconld diag-syslog -20170222.rar

[trurl]

Split your post into its own topic. Best if you don't hijack another users support thread. It just gets confusing trying to respond to different people about what are often actually different things.

[Squid]

Search the forums for IRQ 16  This is probably one the the cases where the trace may be benign.

[marcoNLD]

thx @trurl for creating this, newbie as you noticed

 

will search aswell but i already looked for this solution. 

hence the fact i posted the diag.log.

maybe someone can put me in the right direction.

and BTW, i am a newbie with little to none linux experience.

i can build and maintain a windows PC. already proud i made this server

[John_M]

IRQ 16 is in use by a USB 2 controller:

 

Quote

Feb 21 13:07:50 Tower kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7efa000
Feb 21 13:07:50 Tower kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00

 

which might be a problem if it was hosting your boot device. However, it isn't:

 

Quote

[0:0:0:0]    disk    Kingston DataTraveler 2.0 PMAP  /dev/sda   /dev/sg0 
  state=running queue_depth=1 scsi_level=7 type=0 device_blocked=0 timeout=30
  dir: /sys/bus/scsi/devices/0:0:0:0  [/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/host0/target0:0:0/0:0:0:0]

 

so it might well not be a problem because it's being hosted by a USB 2 controller that's using IRQ 23:

 

Quote

Feb 21 13:07:50 Tower kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7ef9000
Feb 21 13:07:50 Tower kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00

 

Be aware though, if you're ever tempted to move your boot device to a different USB port.

You have a very old BIOS:

 

Quote

Feb 21 22:16:23 Tower kernel: Hardware name: System manufacturer System Product Name/P7H55D-M PRO, BIOS 1604    07/22/2010

 

It might be worth checking for an update.

[marcoNLD]

thank you @John_M for your response.

but what i get from your answer is that there's nothing major going on with my system.

The bios is the latest version. bios 1604.

yeah i know, an old board but its what i had available.

 

thanks again.

it's people like you that keep these projects fun.

[John_M]

That's right. Nothing really to worry about. I gave you the diagnosis in some detail so that you could see for yourself, since you said you had little Linux experience.