entries in /var/log/errors.log once per second - how to troubleshoot

graysky · 2011-11-12 19:09:18

This happens once per sec

tail -f errors.log 
Nov 12 14:08:38 localhost udevd[266]: timeout: killing '/sbin/modprobe -bv pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00' [296]
Nov 12 14:08:39 localhost udevd[266]: timeout: killing '/sbin/modprobe -bv pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00' [296]
Nov 12 14:08:40 localhost udevd[266]: timeout: killing '/sbin/modprobe -bv pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00' [296]
Nov 12 14:08:41 localhost udevd[266]: timeout: killing '/sbin/modprobe -bv pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00' [296]
Nov 12 14:08:42 localhost udevd[266]: timeout: killing '/sbin/modprobe -bv pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00' [296]
Nov 12 14:08:43 localhost udevd[266]: timeout: killing '/sbin/modprobe -bv pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00' [296]
Nov 12 14:08:44 localhost udevd[266]: timeout: killing '/sbin/modprobe -bv pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00' [296]
Nov 12 14:08:45 localhost udevd[266]: timeout: killing '/sbin/modprobe -bv pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00' [296]
Nov 12 14:08:46 localhost udevd[266]: timeout: killing '/sbin/modprobe -bv pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00' [296]
Nov 12 14:08:47 localhost udevd[266]: timeout: killing '/sbin/modprobe -bv pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00' [296]
Nov 12 14:08:48 localhost udevd[266]: timeout: killing '/sbin/modprobe -bv pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00' [296]
Nov 12 14:08:49 localhost udevd[266]: timeout: killing '/sbin/modprobe -bv pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00' [296]

Output of dmesg contains several of these:

[ 1320.309919] INFO: task modprobe:296 blocked for more than 120 seconds.
[ 1320.309924] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1320.309927] modprobe        D 00000000fffea784     0   296    266 0x00000004
[ 1320.309933]  ffff880147549aa8 0000000000000082 ffff880100000000 ffffffff81147e7d
[ 1320.309939]  ffff88014772d640 ffff880147549fd8 ffff880147549fd8 ffff880147549fd8
[ 1320.309945]  ffffffff8189d020 ffff88014772d640 ffff880147549ab8 0000000000000296
[ 1320.309950] Call Trace:
[ 1320.309960]  [<ffffffff81147e7d>] ? new_slab+0x1fd/0x2d0
[ 1320.309967]  [<ffffffff81225c17>] ? idr_get_empty_slot+0x117/0x300
[ 1320.309988]  [<ffffffffa02bc58b>] ? drm_mode_crtc_set_gamma_size+0x2b/0x70 [drm]
[ 1320.309995]  [<ffffffff81226127>] ? idr_get_new_above_int+0x17/0x80
[ 1320.310001]  [<ffffffff81406d1f>] schedule+0x3f/0x60
[ 1320.310007]  [<ffffffff812eb939>] vga_get+0x119/0x1b0
[ 1320.310013]  [<ffffffff8105adf0>] ? try_to_wake_up+0x290/0x290
[ 1320.310040]  [<ffffffffa0fdf0cf>] intel_modeset_init+0x66f/0x1c30 [i915]
[ 1320.310059]  [<ffffffffa0f81200>] ? i915_stolen_to_phys+0x90/0x90 [i915]
[ 1320.310078]  [<ffffffffa0f81260>] ? i915_switcheroo_can_switch+0x60/0x60 [i915]
[ 1320.310098]  [<ffffffffa0f84068>] i915_driver_load+0xf38/0x17a0 [i915]
[ 1320.310104]  [<ffffffff812eedee>] ? device_register+0x1e/0x30
[ 1320.310116]  [<ffffffffa02ba626>] ? drm_sysfs_device_add+0x86/0xb0 [drm]
[ 1320.310127]  [<ffffffffa02b68df>] ? drm_get_minor+0x21f/0x2f0 [drm]
[ 1320.310139]  [<ffffffffa02b8da9>] drm_get_pci_dev+0x199/0x2c0 [drm]
[ 1320.310162]  [<ffffffffa10073f7>] i915_pci_probe+0x1b/0x1d [i915]
[ 1320.310168]  [<ffffffff8124c76c>] local_pci_probe+0x5c/0xd0
[ 1320.310175]  [<ffffffff8124cfb1>] pci_device_probe+0x101/0x120
[ 1320.310182]  [<ffffffff812f156e>] driver_probe_device+0x7e/0x1b0
[ 1320.310187]  [<ffffffff812f174b>] __driver_attach+0xab/0xb0
[ 1320.310192]  [<ffffffff812f16a0>] ? driver_probe_device+0x1b0/0x1b0
[ 1320.310198]  [<ffffffff812f16a0>] ? driver_probe_device+0x1b0/0x1b0
[ 1320.310204]  [<ffffffff812f052c>] bus_for_each_dev+0x5c/0x90
[ 1320.310210]  [<ffffffff812f11fe>] driver_attach+0x1e/0x20
[ 1320.310215]  [<ffffffff812f0e50>] bus_add_driver+0x1a0/0x270
[ 1320.310222]  [<ffffffff812f1cb6>] driver_register+0x76/0x140
[ 1320.310229]  [<ffffffff8124df16>] __pci_register_driver+0x56/0xd0
[ 1320.310235]  [<ffffffff8108a71d>] ? notifier_call_chain+0x4d/0x70
[ 1320.310246]  [<ffffffffa02b8fea>] drm_pci_init+0x11a/0x130 [drm]
[ 1320.310262]  [<ffffffffa1031000>] ? 0xffffffffa1030fff
[ 1320.310279]  [<ffffffffa103108b>] i915_init+0x8b/0x8d [i915]
[ 1320.310285]  [<ffffffff81002040>] do_one_initcall+0x40/0x180
[ 1320.310291]  [<ffffffff810a2be1>] sys_init_module+0x91/0x200
[ 1320.310297]  [<ffffffff8140a442>] system_call_fastpath+0x16/0x1b

Last edited by graysky (2011-11-12 19:09:56)

graysky · 2011-12-01 00:51:13

Problem seems to come and go. If it helps someone else, I added "blacklist pci" to /etc/modprobe.d/modprobe.conf and it seems to have fixed the issue. I won't make as solved until I get some more error free time.

Kilzool · 2011-12-02 23:29:24

It looks like your video card, or lack of a module installed for it, is causing the panics.

My suggestions:

Please post a video card manufacturer, and model...of your video card, and some system details, and more information.
Please paste any files or code, etc, by forum pasting guidelines please.

First, I would like to see a list of all modules you are blacklisting (in /etc/modprobe.d/) and if any are in /etc/rc.conf

Secondly, have you done a 'pacman -Syyu' in console to update your system?

Thirdly, can you paste to us, (and using forum pasting guidelines) the output of 'lspci -v'

Also, are you using 32-bit or 64-bit kernel? (uname -m) and your Arch install version is? (uname -r)

Also, please elaborate more on your Arch Install.
a) Gnome, KDE, etc ?
b) X11 ?
c) and have you installed "xf86-video-intel"

---end

*** all the below are not fully necessary, unless you believe a card or plug is badly seated/inserted ****

a) shutdown and turn off power to computer, and then unplug it,
b) then open your case,
c) THIS STEP IS IMPORTANT: make sure you are not making static like rubbing on a carpet.
d) touch the metal case inside the computer with both hands for a few secs (clears a static charge)
before you touch anything else inside your computer.
e) and find your video card, make sure it is seated and inserted fully.
f) sometimes you have to remove the card, and put it back in.
g) Close the computer case, and make sure all connections are secure and tight.

Last edited by Kilzool (2011-12-02 23:34:46)

graysky · 2011-12-04 17:57:49

Blacklisting "pci" seems to have prevented the error (4 days and counting).

-> only blacklisting pci and nouveau
-> MODULES array in /etc/rc.conf contains no banged-out entries (behavior depreciated a few versions ago)
-> card is an geforce 6200 (pci); manufacture = jaton
-> system is up-to-date
-> lspci -v is here: http://pastebin.com/Xi8nAqbG
-> lspci -vv is here: http://pastebin.com/HNRqeCne
-> Arch x86_64
-> lxde/openbox

Tried pulling/re-seating the video card but no change.

Last edited by graysky (2011-12-04 18:02:57)

Kilzool · 2011-12-04 18:22:31

OK, looks like you have INTERNAL video card *AND* an NVIDIA 6200 card. (I could be wrong).

If this is the case, have you disabled the on-board video card in your BIOS?
Have you tried installing nvidia via the wiki instructions -> https://wiki.archlinux.org/index.php/Nvidia
Then renable 'pci' module, and nouveau will be auto blacklisted by the nvidia packages.
Reboot.

graysky · 2011-12-04 18:25:39

@Kilzool - Yes, onboard video is indeed a feature on this board and it is disabled in the BIOS. I am running the nvidia package and nouveau is auto-blacklisted.

Kilzool · 2011-12-04 18:33:22

Ok, do you have the multilib included in your /etc/pacman.conf ?

[multilib]
Include = /etc/pacman.d/mirrorlist

If not, add it, then do a 'pacman -Syyu'

Last edited by Kilzool (2011-12-04 18:33:40)

graysky · 2011-12-04 18:34:00

no multilib enabled... why would I need it?

falconindy · 2011-12-04 18:54:17

graysky wrote:

@Kilzool - Yes, onboard video is indeed a feature on this board and it is disabled in the BIOS. I am running the nvidia package and nouveau is auto-blacklisted.

Sounds like the BIOS still exposes some small enough amount of the interface that the kernel finds it, even though its inoperative. I would just blacklist i915. Granted, this only masks the problem... Check for a BIOS update?

Last edited by falconindy (2011-12-04 18:55:27)

graysky · 2011-12-04 18:59:51

@falconindy - no bios update. Holy shit, though:

$ lsmod | grep 915
i915                  725698  0 
drm_kms_helper         25721  1 i915
drm                   185736  2 i915,drm_kms_helper
intel_agp              10904  1 i915
intel_gtt              14455  3 i915,intel_agp
video                  11164  1 i915
button                  4470  1 i915
i2c_algo_bit            5199  4 cx88xx,i915,ivtv,bttv
i2c_core               20460  18 cx8800,cx88xx,tuner_simple,tuner,msp3400,i915,drm_kms_helper,drm,nvidia,saa7115,i2c_i801,ivtv,bttv,i2c_algo_bit,tveeprom,v4l2_common,videodev,lirc_i2c

I blacklisted it per your suggestion. What about pci. Should I leave it blacklisted (doesn't seem to do any harm)?

falconindy · 2011-12-04 19:19:42

I'm assuming you mean the modalias "pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00". No, you don't need to do anything with this -- its the hardware signature that resolves to i915.

$ modprobe -R 'pci:v00008086d00002E22sv00001458sd0000D000bc03sc00i00'
i915

You'll need to rip out the module with either rmmod or just reboot. If it still shows up, it means it's being pulled in as a dependency of something else, and you'll need to blacklist it using 'install i915 /bin/false'.

graysky · 2011-12-04 19:44:11

Right... I have pci blacklisted now along with i915. Guess I just leave the two of them in there since it doesn't seem to hurt anything. A welcomed side effect of blacklisting i915 is that my entire boot process is printed to stdout. Before, it would get to the loading udev or loading user modules and go black until X came up.

Thanks again for the suggestion.... I mark as solved in a few weeks assuming it doesn't happen again between now and then.

Last edited by graysky (2011-12-04 19:44:49)

Kilzool · 2011-12-04 23:38:24

I would: rmmod i915 -- then add it to /etc/modprobe.d/modprobe.conf

I would then remove the blacklisting of 'pci'. (meaning: do not blacklist 'pci')

Sometimes trial and error is the way to go.

Arch Linux

#1 2011-11-12 19:09:18

entries in /var/log/errors.log once per second - how to troubleshoot

#2 2011-12-01 00:51:13

Re: entries in /var/log/errors.log once per second - how to troubleshoot

#3 2011-12-02 23:29:24

Re: entries in /var/log/errors.log once per second - how to troubleshoot

#4 2011-12-04 17:57:49

Re: entries in /var/log/errors.log once per second - how to troubleshoot

#5 2011-12-04 18:22:31

Re: entries in /var/log/errors.log once per second - how to troubleshoot

#6 2011-12-04 18:25:39

Re: entries in /var/log/errors.log once per second - how to troubleshoot

#7 2011-12-04 18:33:22

Re: entries in /var/log/errors.log once per second - how to troubleshoot

#8 2011-12-04 18:34:00

Re: entries in /var/log/errors.log once per second - how to troubleshoot

#9 2011-12-04 18:54:17

Re: entries in /var/log/errors.log once per second - how to troubleshoot

#10 2011-12-04 18:59:51

Re: entries in /var/log/errors.log once per second - how to troubleshoot

#11 2011-12-04 19:19:42

Re: entries in /var/log/errors.log once per second - how to troubleshoot

#12 2011-12-04 19:44:11

Re: entries in /var/log/errors.log once per second - how to troubleshoot

#13 2011-12-04 23:38:24

Re: entries in /var/log/errors.log once per second - how to troubleshoot

Board footer