Hi all!
I'm running an up to date Centos-7 on my Acer Aspire One netbook. have been for, well, ever since C7 was released.
Just had an event today that also happened 2 or 3 times with earlier systems installed, but I never pursued it.
What happens is that suddenly while working away on the desktop the display suddenly goes black... not black as in turned off, I can see that the backlight is still on, but no image is displayed.
Nothing I can do fixes it except a reboot. I've tried CTRL-ALT-BKSP, CTRL-ALT-DEL, alt+printscreen+r+e+i+s+u+b. none of them do anything noticeable.
I've been looking at system logs and don't find anything that gives me a clue what is going wrong when that happens.
neither dmesg, /var/log/Xorg*, nor /var/log/messages contins much. I've tried digging thru "man journalctl" and ultimately reading thru the output of journalctl with no arguments.
Can anyone of you provide further hints on what I should be looking for or at?
thanks!
Fred
On Sun, 19 Jun 2016 21:10:24 -0400 Fred Smith wrote:
I'm running an up to date Centos-7 on my Acer Aspire One netbook. have been for, well, ever since C7 was released.
I'm typing this on my Acer Aspire One netbook running Centos 7.
What happens is that suddenly while working away on the desktop the display suddenly goes black... not black as in turned off, I can see that the backlight is still on, but no image is displayed.
Haven't encountered that, ever.
Have you checked to insure that your bios is up to date? I have a vague memory of re-flashing the bios on this netbook at some point in the past....
On Sun, Jun 19, 2016 at 08:29:22PM -0600, Frank Cox wrote:
On Sun, 19 Jun 2016 21:10:24 -0400 Fred Smith wrote:
I'm running an up to date Centos-7 on my Acer Aspire One netbook. have been for, well, ever since C7 was released.
I'm typing this on my Acer Aspire One netbook running Centos 7.
What happens is that suddenly while working away on the desktop the display suddenly goes black... not black as in turned off, I can see that the backlight is still on, but no image is displayed.
Haven't encountered that, ever.
I'm not suggesting its a centos problem, I'm just looking for advice on where to look to get hints as to what is failing.]
Have you checked to insure that your bios is up to date? I have a vague memory of re-flashing the bios on this netbook at some point in the past....
hmm. no, I haven't. I'll look into that.
Try with CTRL-ALT-F2 (go to the console) and CTRL-ALT-F1 (go back to the X-Window). This may help...
suomi
On 06/20/2016 03:10 AM, Fred Smith wrote:
Hi all!
I'm running an up to date Centos-7 on my Acer Aspire One netbook. have been for, well, ever since C7 was released.
Just had an event today that also happened 2 or 3 times with earlier systems installed, but I never pursued it.
What happens is that suddenly while working away on the desktop the display suddenly goes black... not black as in turned off, I can see that the backlight is still on, but no image is displayed.
Nothing I can do fixes it except a reboot. I've tried CTRL-ALT-BKSP, CTRL-ALT-DEL, alt+printscreen+r+e+i+s+u+b. none of them do anything noticeable.
I've been looking at system logs and don't find anything that gives me a clue what is going wrong when that happens.
neither dmesg, /var/log/Xorg*, nor /var/log/messages contins much. I've tried digging thru "man journalctl" and ultimately reading thru the output of journalctl with no arguments.
Can anyone of you provide further hints on what I should be looking for or at?
thanks!
Fred
On Mon, Jun 20, 2016 at 07:02:35AM +0200, anax wrote:
Try with CTRL-ALT-F2 (go to the console) and CTRL-ALT-F1 (go back to the X-Window). This may help...
suomi
oh, sorry, I did try that, but failed to mention it. No, it makes no visible difference at all.
On 06/20/2016 03:10 AM, Fred Smith wrote:
Hi all!
I'm running an up to date Centos-7 on my Acer Aspire One netbook. have been for, well, ever since C7 was released.
Just had an event today that also happened 2 or 3 times with earlier systems installed, but I never pursued it.
What happens is that suddenly while working away on the desktop the display suddenly goes black... not black as in turned off, I can see that the backlight is still on, but no image is displayed.
Nothing I can do fixes it except a reboot. I've tried CTRL-ALT-BKSP, CTRL-ALT-DEL, alt+printscreen+r+e+i+s+u+b. none of them do anything noticeable.
I've been looking at system logs and don't find anything that gives me a clue what is going wrong when that happens.
neither dmesg, /var/log/Xorg*, nor /var/log/messages contins much. I've tried digging thru "man journalctl" and ultimately reading thru the output of journalctl with no arguments.
Can anyone of you provide further hints on what I should be looking for or at?
thanks!
Fred
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On Mon, Jun 20, 2016 at 01:34:30PM +0300, Александр Кириллов wrote:
Can anyone of you provide further hints on what I should be looking for or at?
Is it trying to hibernate?
gosh, I hope not! I was in the middle of using it, playing solitaire and moving the mouse around a lot.
Motherboard time. Netbook is probably a throw away issue. Cost more t to repair than buy new.
Sent from my iPad
On Jun 20, 2016, at 7:58 AM, Fred Smith fredex@fcshome.stoneham.ma.us wrote:
On Mon, Jun 20, 2016 at 01:34:30PM +0300, Александр Кириллов wrote:
Can anyone of you provide further hints on what I should be looking for or at?
Is it trying to hibernate?
gosh, I hope not! I was in the middle of using it, playing solitaire and moving the mouse around a lot.
-- ---- Fred Smith -- fredex@fcshome.stoneham.ma.us ----------------------------- "Not everyone who says to me, 'Lord, Lord,' will enter the kingdom of heaven, but only he who does the will of my Father who is in heaven." ------------------------------ Matthew 7:21 (niv) ----------------------------- _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Dr. Mikeal Hughes wrote:
Motherboard time. Netbook is probably a throw away issue. Cost more t to repair than buy new.
On Jun 20, 2016, at 7:58 AM, Fred Smith fredex@fcshome.stoneham.ma.us wrote:
On Mon, Jun 20, 2016 at 01:34:30PM +0300, Александр Кириллов wrote:
Can anyone of you provide further hints on what I should be looking for or at?
Is it trying to hibernate?
gosh, I hope not! I was in the middle of using it, playing solitaire and moving the mouse around a lot.
Have you checked the PSU? Maybe vacuum it out (or open up the back of the laptop, and vacuum the whole thing)?
mark
On Mon, June 20, 2016 9:28 am, m.roth@5-cent.us wrote:
Dr. Mikeal Hughes wrote:
Motherboard time. Netbook is probably a throw away issue. Cost more t to repair than buy new.
On Jun 20, 2016, at 7:58 AM, Fred Smith fredex@fcshome.stoneham.ma.us wrote:
On Mon, Jun 20, 2016 at 01:34:30PM +0300, ÐлекÑÐ°Ð½Ð´Ñ ÐиÑиллов wrote:
Can anyone of you provide further hints on what I should be looking for or at?
Is it trying to hibernate?
gosh, I hope not! I was in the middle of using it, playing solitaire and moving the mouse around a lot.
Have you checked the PSU? Maybe vacuum it out (or open up the back of the laptop, and vacuum the whole thing)?
I might have missed the beginning of this thread: when the screen goes black can you still ssh to the machine (you may need to enable ssh, and switch from DHCP to static IP for this test). If you can ssh, this will mean kernel is still happily running, if not, then kernel might have panicked. I would do what Mark suggests: clean it to avoid overheating (but don't do it yet, until you pinpoint the place where it fails). BIOS turns the machine off completely when temperature threshold is tripped, so tripping temperature sensor threshold is not your case as your screen backlight is still on. However, overheating video chip may do what you see. And it also may open some micro crack. I also would do the following: attach external screen, make them both ON, and see if only internal panel goes black or both of them do.
Tell us what your experiments reveal.
Valeri
++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++
On Mon, Jun 20, 2016 at 10:28:48AM -0400, m.roth@5-cent.us wrote:
Dr. Mikeal Hughes wrote:
Motherboard time. Netbook is probably a throw away issue. Cost more t to repair than buy new.
On Jun 20, 2016, at 7:58 AM, Fred Smith fredex@fcshome.stoneham.ma.us wrote:
On Mon, Jun 20, 2016 at 01:34:30PM +0300, Александр Кириллов wrote:
Can anyone of you provide further hints on what I should be looking for or at?
Is it trying to hibernate?
gosh, I hope not! I was in the middle of using it, playing solitaire and moving the mouse around a lot.
Have you checked the PSU? Maybe vacuum it out (or open up the back of the laptop, and vacuum the whole thing)?
mark
Had it open not too long ago, saw no dirt. fan moves plenty of air.
Fred Smith wrote:
On Mon, Jun 20, 2016 at 01:34:30PM +0300, Александр Кириллов wrote:
Can anyone of you provide further hints on what I should be looking for or at?
Is it trying to hibernate?
gosh, I hope not! I was in the middle of using it, playing solitaire and moving the mouse around a lot.
Ack! That's critical! I mean, if we don't play our required games of solitaire, the world will come to an end....
mark "I am *not* addicted to solitaire, I can quit any time I want...."
On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote:
On Mon, Jun 20, 2016 at 01:34:30PM +0300, Александр Кириллов wrote:
Can anyone of you provide further hints on what I should be looking for or at?
Is it trying to hibernate?
gosh, I hope not! I was in the middle of using it, playing solitaire and moving the mouse around a lot.
I recently had the opposite problem. I'd comback to a laptop I knew I had turned off and it was up and running.
Turns out the bios had a setting to automatically power up at 1:30 AM. Perhaps your bios has a "shut down at ..." setting?
jl
On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote:
On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote:
On Mon, Jun 20, 2016 at 01:34:30PM +0300, Александр Кириллов wrote:
Can anyone of you provide further hints on what I should be looking for or at?
Is it trying to hibernate?
gosh, I hope not! I was in the middle of using it, playing solitaire and moving the mouse around a lot.
I recently had the opposite problem. I'd comback to a laptop I knew I had turned off and it was up and running.
Turns out the bios had a setting to automatically power up at 1:30 AM. Perhaps your bios has a "shut down at ..." setting?
jl
thanks for the suggestion!
but I kinda doubt that's it, this has been highly rare, and doesn't do it when e.g. I'm at work and leave it on all day.
Fred
Fred Smith wrote:
On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote:
On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote:
On Mon, Jun 20, 2016 at 01:34:30PM +0300, Александр Кириллов wrote:
Can anyone of you provide further hints on what I should be looking for or at?
Is it trying to hibernate?
gosh, I hope not! I was in the middle of using it, playing solitaire and moving the mouse around a lot.
I recently had the opposite problem. I'd comback to a laptop I knew I had turned off and it was up and running.
Turns out the bios had a setting to automatically power up at 1:30 AM. Perhaps your bios has a "shut down at ..." setting?
jl
thanks for the suggestion!
but I kinda doubt that's it, this has been highly rare, and doesn't do it when e.g. I'm at work and leave it on all day.
Hooold on thar! I came into this thread really late (like, today). You're saying it's fine at work, but not at home?
mark
On Mon, Jun 20, 2016 at 04:13:35PM -0400, m.roth@5-cent.us wrote:
Fred Smith wrote:
On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote:
On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote:
On Mon, Jun 20, 2016 at 01:34:30PM +0300, Александр Кириллов wrote:
Can anyone of you provide further hints on what I should be looking for or at?
Is it trying to hibernate?
gosh, I hope not! I was in the middle of using it, playing solitaire and moving the mouse around a lot.
I recently had the opposite problem. I'd comback to a laptop I knew I had turned off and it was up and running.
Turns out the bios had a setting to automatically power up at 1:30 AM. Perhaps your bios has a "shut down at ..." setting?
jl
thanks for the suggestion!
but I kinda doubt that's it, this has been highly rare, and doesn't do it when e.g. I'm at work and leave it on all day.
Hooold on thar! I came into this thread really late (like, today). You're saying it's fine at work, but not at home?
No. I'm saying it's only happened once since I installed C7, not long after it was released. While I haven't kept records of dates and times, I don't think it was at any specific time.
I saw it 2 or 3 times previously, probably some Fedora version,... my tired old brain won't divulge that info right now.
It seems reasonable that it's some kind of hardware issue but I don't see anything in the logs I've thought to check.
I inquired, hoping some of you could suggest other places to look for info, in retrospect.
Fred Smith wrote:
On Mon, Jun 20, 2016 at 04:13:35PM -0400, m.roth@5-cent.us wrote:
Fred Smith wrote:
On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote:
On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote:
On Mon, Jun 20, 2016 at 01:34:30PM +0300, Александр Кириллов wrote:
<snip>
Hooold on thar! I came into this thread really late (like, today). You're saying it's fine at work, but not at home?
No. I'm saying it's only happened once since I installed C7, not long after it was released. While I haven't kept records of dates and times, I don't think it was at any specific time.
I saw it 2 or 3 times previously, probably some Fedora version,... my tired old brain won't divulge that info right now.
It seems reasonable that it's some kind of hardware issue but I don't see anything in the logs I've thought to check.
I inquired, hoping some of you could suggest other places to look for info, in retrospect.
Ok, then at that point, I like Valery's suggestion. Try looking at /var/log/Xorg.0.log
mark
On Mon, Jun 20, 2016 at 05:02:32PM -0400, m.roth@5-cent.us wrote:
Fred Smith wrote:
On Mon, Jun 20, 2016 at 04:13:35PM -0400, m.roth@5-cent.us wrote:
Fred Smith wrote:
On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote:
On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote:
On Mon, Jun 20, 2016 at 01:34:30PM +0300, Александр Кириллов wrote:
<snip> >> >> Hooold on thar! I came into this thread really late (like, today). >> You're saying it's fine at work, but not at home? > > No. I'm saying it's only happened once since I installed C7, not long > after it was released. While I haven't kept records of dates and times, > I don't think it was at any specific time. > > I saw it 2 or 3 times previously, probably some Fedora version,... my > tired old brain won't divulge that info right now. > > It seems reasonable that it's some kind of hardware issue but I don't > see anything in the logs I've thought to check. > > I inquired, hoping some of you could suggest other places to look for > info, in retrospect.
Ok, then at that point, I like Valery's suggestion. Try looking at /var/log/Xorg.0.log
OK, it just did it again. The system is still up, I just can't do anything on the built-in keyboard/screen, but I CAN use SSH to log in. Doing so, I've captured a bunch of stuff from journalctl that looks like its probably related, which I'll paste in here. I will also go look at the Xorg log files to see if they contain anything further of interest.
[later: xorg.0.log doesn't contain anything that appears related to this failure. the last thing in it is recognition of the USB wireless mouse I had plugged in some minutes prior to the failure (10-30 minutes, as best I can recall). It's hard to tell what is going on since Xorg.0.log does not display the actual time the reported events occurred.]
BTW, this is Centos-7, probably up to date, or at least if not, no more than a few days from there, running kernel 3.10.0-327.18.2.el7.x86_64. This system has some generic Intel video chipset, and is an Atom N570, dual core, 64-bit processor, running at a _screaming_ 1.6 GHz. Oh my! :)
I'm looking around in /proc to see if I can find out which generation of Intel video it has. I don't see it in /proc/cpuinfo, can someone advise me where to look for this info? LATER: this site: http://www.cpu-world.com/CPUs/Atom/Intel-Atom%20N570.html says its graphics engine is GMA-3150. lsmod shows that we have the i915 module loaded (is that correct for a GMA-3150 graphics chipset?) along with drm_kms_helper and drm.
I'll let it stay in its current (broken) state for a while in case any of you smart guys can suggest other places to look, or things to look for.
thanks in advance!
here's an excerpt from journalctl:
Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: ------------[ cut here ]------------ Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: WARNING: at drivers/gpu/drm/drm_irq.c:1141 drm_wait_one_vblank+0x19e/0x1b0 [drm]() Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: vblank wait timed out on crtc 1 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: Modules linked in: rfcomm fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun ccm nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT ipt_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw iptable_filter bnep arc4 ath9k ath9k_common ath9k_hw ath coretemp uvcvideo kvm mac80211 btusb videobuf2_vmalloc videobuf2_memops videobuf2_core videodev snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec cfg80211 bluetooth snd_hda_core snd_hwdep snd_seq snd_seq_device Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: acer_wmi iTCO_wdt sparse_keymap snd_pcm iTCO_vendor_support snd_timer rfkill snd sg wmi i2c_i801 pcspkr soundcore shpchp lpc_ich mfd_core acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables ext4 mbcache jbd2 dm_crypt drbg xts gf128mul sd_mod crc_t10dif crct10dif_generic crct10dif_common i915 i2c_algo_bit drm_kms_helper ahci libahci drm libata serio_raw i2c_core atl1c video dm_mirror dm_region_hash dm_log dm_mod Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: CPU: 0 PID: 3165 Comm: X Not tainted 3.10.0-327.22.2.el7.x86_64 #1 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: Hardware name: Acer AOD255E/JE02_PT_E, BIOS V3.16(DDR3) 04/22/2011 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: ffff880077c1b7c8 00000000623d88bd ffff880077c1b780 ffffffff816360fc Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: ffff880077c1b7b8 ffffffff8107b200 ffff88007775f800 0000000000000000 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: 0000000000000001 00000000000cc3cb ffff880035eac4b0 ffff880077c1b820 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: Call Trace: Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff816360fc>] dump_stack+0x19/0x1b Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff8107b200>] warn_slowpath_common+0x70/0xb0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff8107b29c>] warn_slowpath_fmt+0x5c/0x80 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff810a6966>] ? finish_wait+0x56/0x70 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa00b69be>] drm_wait_one_vblank+0x19e/0x1b0 [drm] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff810a6ae0>] ? wake_up_atomic_t+0x30/0x30 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa00b69ec>] drm_crtc_wait_one_vblank+0x1c/0x20 [drm] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa01338b8>] drm_plane_helper_commit+0x298/0x300 [drm_kms_helper] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa01339ba>] drm_plane_helper_update+0x9a/0xf0 [drm_kms_helper] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa01c6727>] intel_crtc_set_config+0xbc7/0xff0 [i915] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa00bfdb7>] drm_mode_set_config_internal+0x67/0x100 [drm] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa013c508>] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa013e3f5>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70 [drm_kms_helper] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa013e462>] drm_fb_helper_set_par+0x22/0x50 [drm_kms_helper] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa01d419a>] intel_fbdev_set_par+0x1a/0x60 [i915] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff813473d6>] ? fb_set_var+0x206/0x440 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff81347367>] fb_set_var+0x197/0x440 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff810b5db5>] ? check_preempt_curr+0x75/0xa0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff810b5df9>] ? ttwu_do_wakeup+0x19/0xd0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff810b5f8d>] ? ttwu_do_activate.constprop.84+0x5d/0x70 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff810c155c>] ? update_curr+0xcc/0x150 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff81353001>] fbcon_blank+0x1f1/0x2f0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff8101386e>] ? __switch_to+0x3de/0x4b0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff813c5ab8>] do_unblank_screen+0xb8/0x1f0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff813bb2ba>] complete_change_console+0x5a/0xe0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff813bc31b>] vt_ioctl+0xfdb/0x1200 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff81194fb7>] ? do_wp_page+0x3b7/0x800 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa00b4b63>] ? drm_ioctl+0x1a3/0x6a0 [drm] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa00b9200>] ? drm_setmaster_ioctl+0xe0/0xe0 [drm] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff813b06d9>] tty_ioctl+0x289/0xbc0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff8119755c>] ? handle_mm_fault+0x65c/0xf50 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff812226d5>] ? fsnotify+0x265/0x350 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff811f2545>] do_vfs_ioctl+0x2e5/0x4c0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff8128c42e>] ? file_has_perm+0xae/0xc0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff81641d01>] ? __do_page_fault+0xd1/0x450 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff811f27c1>] SyS_ioctl+0xa1/0xc0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff81646889>] system_call_fastpath+0x16/0x1b Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: ---[ end trace bee22ab73891691b ]--- Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started Getty on tty2. Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting Getty on tty2... Jun 30 12:47:50 aspirebox.fcshome.stoneham.ma.us sh[865]: abrt-dump-oops: Found oopses: 1 Jun 30 12:47:50 aspirebox.fcshome.stoneham.ma.us sh[865]: abrt-dump-oops: Creating problem directories Jun 30 12:47:50 aspirebox.fcshome.stoneham.ma.us sh[865]: abrt-dump-oops: Not going to make dump directories world readable because PrivateReports is on Jun 30 12:47:51 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: Duplicate: core backtrace Jun 30 12:47:51 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: DUP_OF_DIR: /var/spool/abrt/oops-2016-06-19-17:50:28-22260-0 Jun 30 12:47:51 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: Deleting problem directory oops-2016-06-30-12:47:50-12031-0 (dup of oops-2016-06-19-17:50:28-22260-0) Jun 30 12:47:51 aspirebox.fcshome.stoneham.ma.us abrt-dump-oops[12031]: Reported 1 kernel oopses to Abrt Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Successfully activated service 'org.freedesktop.problems' Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Successfully activated service 'org.freedesktop.problems' Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: Email address of sender was not specified. Would you like to do so now? If not, 'user@localhost' is to be used [y/N] Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: Email address of receiver was not specified. Would you like to do so now? If not, 'root@localhost' is to be used [y/N] Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: Sending an email... Jun 30 12:47:53 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: Email was sent to: root@localhost Jun 30 12:47:53 aspirebox.fcshome.stoneham.ma.us postfix/pickup[11700]: 4937BA04AC: uid=0 from=user@localhost Jun 30 12:47:53 aspirebox.fcshome.stoneham.ma.us postfix/cleanup[12061]: 4937BA04AC: message-id=57754d38.DS2U4iSNfSqbJwcF%user@localhost Jun 30 12:47:53 aspirebox.fcshome.stoneham.ma.us postfix/qmgr[2780]: 4937BA04AC: from=user@localhost.fcshome.stoneham.ma.us, size=524663, nrcpt=1 (queue active) Jun 30 12:47:53 aspirebox.fcshome.stoneham.ma.us postfix/local[12063]: 4937BA04AC: to=root@localhost.fcshome.stoneham.ma.us, orig_to=root@localhost, relay=local, delay=0.67, delays=0.48/0.08/0/0.11, dsn=2.0.0, status=sent (delivered to mailbox) Jun 30 12:47:53 aspirebox.fcshome.stoneham.ma.us postfix/qmgr[2780]: 4937BA04AC: removed Jun 30 12:48:10 aspirebox.fcshome.stoneham.ma.us kernel: ACPI: _SB_.PCI0.LPC_.AC__: ACPI_NOTIFY_BUS_CHECK event Jun 30 12:48:11 aspirebox.fcshome.stoneham.ma.us pulseaudio[3437]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us kernel: SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Created slice user-0.slice. Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting user-0.slice. Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started Session 30 of user root. Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting Session 30 of user root. Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us CROND[12091]: (root) CMD (/usr/lib64/sa/sa1 1 1) Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Removed slice user-0.slice. Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Stopping user-0.slice. Jun 30 12:51:56 aspirebox.fcshome.stoneham.ma.us sshd[12213]: Accepted password for fredex from 192.168.2.113 port 35223 ssh2 Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us systemd-logind[849]: New session 31 of user fredex. Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started Session 31 of user fredex. Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting Session 31 of user fredex. Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us sshd[12213]: pam_unix(sshd:session): session opened for user fredex by (uid=0) Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Successfully activated service 'org.freedesktop.problems' Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Successfully activated service 'org.freedesktop.problems' Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting Fingerprint Authentication Daemon... Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Successfully activated service 'net.reactivated.Fprint' Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Successfully activated service 'net.reactivated.Fprint' Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started Fingerprint Authentication Daemon. Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us fprintd[12341]: Launching FprintObject Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us fprintd[12341]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us fprintd[12341]: ** Message: entering main loop Jun 30 12:53:33 aspirebox.fcshome.stoneham.ma.us su[12340]: (to root) fredex on pts/0 Jun 30 12:53:33 aspirebox.fcshome.stoneham.ma.us su[12340]: pam_unix(su:session): session opened for user root by fredex(uid=1000) Jun 30 12:54:00 aspirebox.fcshome.stoneham.ma.us fprintd[12341]: ** Message: No devices in use, exit Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us kernel: SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Created slice user-0.slice. Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting user-0.slice. Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started Session 32 of user root. Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting Session 32 of user root. Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us CROND[12477]: (root) CMD (/usr/lib64/sa/sa1 1 1) Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Removed slice user-0.slice. Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Stopping user-0.slice. Jun 30 13:01:01 aspirebox.fcshome.stoneham.ma.us kernel: SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs Jun 30 13:01:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Created slice user-0.slice. Jun 30 13:01:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting user-0.slice. Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started Session 33 of user root. Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting Session 33 of user root. Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us CROND[12594]: (root) CMD (run-parts /etc/cron.hourly) Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us run-parts(/etc/cron.hourly)[12614]: starting 0anacron Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us anacron[12628]: Anacron started on 2016-06-30 Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us run-parts(/etc/cron.hourly)[12630]: finished 0anacron Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us run-parts(/etc/cron.hourly)[12633]: starting 0yum-hourly.cron Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us anacron[12628]: Will run job `cron.daily' in 20 min. Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us anacron[12628]: Jobs will be executed sequentially Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us run-parts(/etc/cron.hourly)[12638]: finished 0yum-hourly.cron Jun 30 13:05:54 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' Jun 30 13:05:54 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' Jun 30 13:05:54 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting PackageKit Daemon... Jun 30 13:05:54 aspirebox.fcshome.stoneham.ma.us PackageKit[12797]: daemon start Jun 30 13:05:55 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Successfully activated service 'org.freedesktop.PackageKit' Jun 30 13:05:55 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Successfully activated service 'org.freedesktop.PackageKit' Jun 30 13:05:55 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started PackageKit Daemon.
On Thu, Jun 30, 2016 at 02:53:05PM -0400, Fred Smith wrote:
On Mon, Jun 20, 2016 at 05:02:32PM -0400, m.roth@5-cent.us wrote:
Fred Smith wrote:
On Mon, Jun 20, 2016 at 04:13:35PM -0400, m.roth@5-cent.us wrote:
Fred Smith wrote:
On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote:
On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote: > On Mon, Jun 20, 2016 at 01:34:30PM +0300, Александр Кириллов wrote:
<snip> >> >> Hooold on thar! I came into this thread really late (like, today). >> You're saying it's fine at work, but not at home? > > No. I'm saying it's only happened once since I installed C7, not long > after it was released. While I haven't kept records of dates and times, > I don't think it was at any specific time. > > I saw it 2 or 3 times previously, probably some Fedora version,... my > tired old brain won't divulge that info right now. > > It seems reasonable that it's some kind of hardware issue but I don't > see anything in the logs I've thought to check. > > I inquired, hoping some of you could suggest other places to look for > info, in retrospect.
Ok, then at that point, I like Valery's suggestion. Try looking at /var/log/Xorg.0.log
OK, it just did it again. The system is still up, I just can't do anything on the built-in keyboard/screen, but I CAN use SSH to log in. Doing so, I've captured a bunch of stuff from journalctl that looks like its probably related, which I'll paste in here. I will also go look at the Xorg log files to see if they contain anything further of interest.
[later: xorg.0.log doesn't contain anything that appears related to this failure. the last thing in it is recognition of the USB wireless mouse I had plugged in some minutes prior to the failure (10-30 minutes, as best I can recall). It's hard to tell what is going on since Xorg.0.log does not display the actual time the reported events occurred.]
BTW, this is Centos-7, probably up to date, or at least if not, no more than a few days from there, running kernel 3.10.0-327.18.2.el7.x86_64. This system has some generic Intel video chipset, and is an Atom N570, dual core, 64-bit processor, running at a _screaming_ 1.6 GHz. Oh my! :)
I'm looking around in /proc to see if I can find out which generation of Intel video it has. I don't see it in /proc/cpuinfo, can someone advise me where to look for this info? LATER: this site: http://www.cpu-world.com/CPUs/Atom/Intel-Atom%20N570.html says its graphics engine is GMA-3150. lsmod shows that we have the i915 module loaded (is that correct for a GMA-3150 graphics chipset?) along with drm_kms_helper and drm.
I'll let it stay in its current (broken) state for a while in case any of you smart guys can suggest other places to look, or things to look for.
thanks in advance!
I've done a lot of searching for this error message, online:
kernel: vblank wait timed out on crtc 1
or
WARNING: at drivers/gpu/drm/drm_irq.c:1141 drm_wait_one_vblank
and find a lot of places where people have had reported the same thing (most were "crtc 0" instead of "crtc 1"). it seems to have happened to a lot of people, for several years, many on ubuntu, and some of them on a 4.x kernel. I think that most, if not all, of them were reporting using an Intel video chipset, so it is likely an Intel driver bug.
Most of them, however, did not report that they lost video output. In my case, the laptop console becomes useless. I cannot switch to a text console, and nothing I input on the keyboard makes any difference, other than that the screensaver seems to have turned the screen black if I leave it alone long enough, and touching the keyboard turns it gray (i.e., black with backlight on).
what I haven't found, so far, is any mitigation.
Some reports were that it occurs when switching to or from the X virtual console, but as far as I can see that isn't what triggers it in my case. I can't tell, actually, 'cause I'm just moving along doing random-seeming stuff when suddenly kaboom.
Some reports did show how to turn on drm debugging, boot with:
drm.debug=0x1e
since it happens to me so rarely, I'm not sure I could capture any useful info by doing that.
I'm still open to suggestions, if anyone has any. thanks!
Fred
here's an excerpt from journalctl:
Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: ------------[ cut here ]------------ Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: WARNING: at drivers/gpu/drm/drm_irq.c:1141 drm_wait_one_vblank+0x19e/0x1b0 [drm]() Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: vblank wait timed out on crtc 1 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: Modules linked in: rfcomm fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun ccm nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT ipt_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw iptable_filter bnep arc4 ath9k ath9k_common ath9k_hw ath coretemp uvcvideo kvm mac80211 btusb videobuf2_vmalloc videobuf2_memops videobuf2_core videodev snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec cfg80211 bluetooth snd_hda_core snd_hwdep snd_seq snd_seq_device Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: acer_wmi iTCO_wdt sparse_keymap snd_pcm iTCO_vendor_support snd_timer rfkill snd sg wmi i2c_i801 pcspkr soundcore shpchp lpc_ich mfd_core acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables ext4 mbcache jbd2 dm_crypt drbg xts gf128mul sd_mod crc_t10dif crct10dif_generic crct10dif_common i915 i2c_algo_bit drm_kms_helper ahci libahci drm libata serio_raw i2c_core atl1c video dm_mirror dm_region_hash dm_log dm_mod Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: CPU: 0 PID: 3165 Comm: X Not tainted 3.10.0-327.22.2.el7.x86_64 #1 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: Hardware name: Acer AOD255E/JE02_PT_E, BIOS V3.16(DDR3) 04/22/2011 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: ffff880077c1b7c8 00000000623d88bd ffff880077c1b780 ffffffff816360fc Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: ffff880077c1b7b8 ffffffff8107b200 ffff88007775f800 0000000000000000 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: 0000000000000001 00000000000cc3cb ffff880035eac4b0 ffff880077c1b820 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: Call Trace: Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff816360fc>] dump_stack+0x19/0x1b Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff8107b200>] warn_slowpath_common+0x70/0xb0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff8107b29c>] warn_slowpath_fmt+0x5c/0x80 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff810a6966>] ? finish_wait+0x56/0x70 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa00b69be>] drm_wait_one_vblank+0x19e/0x1b0 [drm] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff810a6ae0>] ? wake_up_atomic_t+0x30/0x30 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa00b69ec>] drm_crtc_wait_one_vblank+0x1c/0x20 [drm] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa01338b8>] drm_plane_helper_commit+0x298/0x300 [drm_kms_helper] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa01339ba>] drm_plane_helper_update+0x9a/0xf0 [drm_kms_helper] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa01c6727>] intel_crtc_set_config+0xbc7/0xff0 [i915] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa00bfdb7>] drm_mode_set_config_internal+0x67/0x100 [drm] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa013c508>] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa013e3f5>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70 [drm_kms_helper] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa013e462>] drm_fb_helper_set_par+0x22/0x50 [drm_kms_helper] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa01d419a>] intel_fbdev_set_par+0x1a/0x60 [i915] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff813473d6>] ? fb_set_var+0x206/0x440 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff81347367>] fb_set_var+0x197/0x440 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff810b5db5>] ? check_preempt_curr+0x75/0xa0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff810b5df9>] ? ttwu_do_wakeup+0x19/0xd0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff810b5f8d>] ? ttwu_do_activate.constprop.84+0x5d/0x70 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff810c155c>] ? update_curr+0xcc/0x150 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff81353001>] fbcon_blank+0x1f1/0x2f0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff8101386e>] ? __switch_to+0x3de/0x4b0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff813c5ab8>] do_unblank_screen+0xb8/0x1f0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff813bb2ba>] complete_change_console+0x5a/0xe0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff813bc31b>] vt_ioctl+0xfdb/0x1200 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff81194fb7>] ? do_wp_page+0x3b7/0x800 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa00b4b63>] ? drm_ioctl+0x1a3/0x6a0 [drm] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffffa00b9200>] ? drm_setmaster_ioctl+0xe0/0xe0 [drm] Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff813b06d9>] tty_ioctl+0x289/0xbc0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff8119755c>] ? handle_mm_fault+0x65c/0xf50 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff812226d5>] ? fsnotify+0x265/0x350 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff811f2545>] do_vfs_ioctl+0x2e5/0x4c0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff8128c42e>] ? file_has_perm+0xae/0xc0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff81641d01>] ? __do_page_fault+0xd1/0x450 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff811f27c1>] SyS_ioctl+0xa1/0xc0 Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: [<ffffffff81646889>] system_call_fastpath+0x16/0x1b Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us kernel: ---[ end trace bee22ab73891691b ]--- Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started Getty on tty2. Jun 30 12:47:49 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting Getty on tty2... Jun 30 12:47:50 aspirebox.fcshome.stoneham.ma.us sh[865]: abrt-dump-oops: Found oopses: 1 Jun 30 12:47:50 aspirebox.fcshome.stoneham.ma.us sh[865]: abrt-dump-oops: Creating problem directories Jun 30 12:47:50 aspirebox.fcshome.stoneham.ma.us sh[865]: abrt-dump-oops: Not going to make dump directories world readable because PrivateReports is on Jun 30 12:47:51 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: Duplicate: core backtrace Jun 30 12:47:51 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: DUP_OF_DIR: /var/spool/abrt/oops-2016-06-19-17:50:28-22260-0 Jun 30 12:47:51 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: Deleting problem directory oops-2016-06-30-12:47:50-12031-0 (dup of oops-2016-06-19-17:50:28-22260-0) Jun 30 12:47:51 aspirebox.fcshome.stoneham.ma.us abrt-dump-oops[12031]: Reported 1 kernel oopses to Abrt Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Successfully activated service 'org.freedesktop.problems' Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Successfully activated service 'org.freedesktop.problems' Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: Email address of sender was not specified. Would you like to do so now? If not, 'user@localhost' is to be used [y/N] Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: Email address of receiver was not specified. Would you like to do so now? If not, 'root@localhost' is to be used [y/N] Jun 30 12:47:52 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: Sending an email... Jun 30 12:47:53 aspirebox.fcshome.stoneham.ma.us abrt-server[12042]: Email was sent to: root@localhost Jun 30 12:47:53 aspirebox.fcshome.stoneham.ma.us postfix/pickup[11700]: 4937BA04AC: uid=0 from=user@localhost Jun 30 12:47:53 aspirebox.fcshome.stoneham.ma.us postfix/cleanup[12061]: 4937BA04AC: message-id=57754d38.DS2U4iSNfSqbJwcF%user@localhost Jun 30 12:47:53 aspirebox.fcshome.stoneham.ma.us postfix/qmgr[2780]: 4937BA04AC: from=user@localhost.fcshome.stoneham.ma.us, size=524663, nrcpt=1 (queue active) Jun 30 12:47:53 aspirebox.fcshome.stoneham.ma.us postfix/local[12063]: 4937BA04AC: to=root@localhost.fcshome.stoneham.ma.us, orig_to=root@localhost, relay=local, delay=0.67, delays=0.48/0.08/0/0.11, dsn=2.0.0, status=sent (delivered to mailbox) Jun 30 12:47:53 aspirebox.fcshome.stoneham.ma.us postfix/qmgr[2780]: 4937BA04AC: removed Jun 30 12:48:10 aspirebox.fcshome.stoneham.ma.us kernel: ACPI: _SB_.PCI0.LPC_.AC__: ACPI_NOTIFY_BUS_CHECK event Jun 30 12:48:11 aspirebox.fcshome.stoneham.ma.us pulseaudio[3437]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us kernel: SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Created slice user-0.slice. Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting user-0.slice. Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started Session 30 of user root. Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting Session 30 of user root. Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us CROND[12091]: (root) CMD (/usr/lib64/sa/sa1 1 1) Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Removed slice user-0.slice. Jun 30 12:50:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Stopping user-0.slice. Jun 30 12:51:56 aspirebox.fcshome.stoneham.ma.us sshd[12213]: Accepted password for fredex from 192.168.2.113 port 35223 ssh2 Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us systemd-logind[849]: New session 31 of user fredex. Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started Session 31 of user fredex. Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting Session 31 of user fredex. Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us sshd[12213]: pam_unix(sshd:session): session opened for user fredex by (uid=0) Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Activating service name='org.freedesktop.problems' (using servicehelper) Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Successfully activated service 'org.freedesktop.problems' Jun 30 12:51:57 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Successfully activated service 'org.freedesktop.problems' Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting Fingerprint Authentication Daemon... Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Successfully activated service 'net.reactivated.Fprint' Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Successfully activated service 'net.reactivated.Fprint' Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started Fingerprint Authentication Daemon. Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us fprintd[12341]: Launching FprintObject Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us fprintd[12341]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Jun 30 12:53:29 aspirebox.fcshome.stoneham.ma.us fprintd[12341]: ** Message: entering main loop Jun 30 12:53:33 aspirebox.fcshome.stoneham.ma.us su[12340]: (to root) fredex on pts/0 Jun 30 12:53:33 aspirebox.fcshome.stoneham.ma.us su[12340]: pam_unix(su:session): session opened for user root by fredex(uid=1000) Jun 30 12:54:00 aspirebox.fcshome.stoneham.ma.us fprintd[12341]: ** Message: No devices in use, exit Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us kernel: SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Created slice user-0.slice. Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting user-0.slice. Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started Session 32 of user root. Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting Session 32 of user root. Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us CROND[12477]: (root) CMD (/usr/lib64/sa/sa1 1 1) Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Removed slice user-0.slice. Jun 30 13:00:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Stopping user-0.slice. Jun 30 13:01:01 aspirebox.fcshome.stoneham.ma.us kernel: SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs Jun 30 13:01:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Created slice user-0.slice. Jun 30 13:01:01 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting user-0.slice. Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started Session 33 of user root. Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting Session 33 of user root. Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us CROND[12594]: (root) CMD (run-parts /etc/cron.hourly) Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us run-parts(/etc/cron.hourly)[12614]: starting 0anacron Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us anacron[12628]: Anacron started on 2016-06-30 Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us run-parts(/etc/cron.hourly)[12630]: finished 0anacron Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us run-parts(/etc/cron.hourly)[12633]: starting 0yum-hourly.cron Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us anacron[12628]: Will run job `cron.daily' in 20 min. Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us anacron[12628]: Jobs will be executed sequentially Jun 30 13:01:02 aspirebox.fcshome.stoneham.ma.us run-parts(/etc/cron.hourly)[12638]: finished 0yum-hourly.cron Jun 30 13:05:54 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' Jun 30 13:05:54 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' Jun 30 13:05:54 aspirebox.fcshome.stoneham.ma.us systemd[1]: Starting PackageKit Daemon... Jun 30 13:05:54 aspirebox.fcshome.stoneham.ma.us PackageKit[12797]: daemon start Jun 30 13:05:55 aspirebox.fcshome.stoneham.ma.us dbus-daemon[874]: dbus[874]: [system] Successfully activated service 'org.freedesktop.PackageKit' Jun 30 13:05:55 aspirebox.fcshome.stoneham.ma.us dbus[874]: [system] Successfully activated service 'org.freedesktop.PackageKit' Jun 30 13:05:55 aspirebox.fcshome.stoneham.ma.us systemd[1]: Started PackageKit Daemon.
-- ---- Fred Smith -- fredex@fcshome.stoneham.ma.us ----------------------------- God made him who had no sin to be sin for us, so that in him we might become the righteousness of God." --------------------------- Corinthians 5:21 --------------------------------- _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
-
anax -
Dr. Mikeal Hughes -
Frank Cox -
Fred Smith -
Jon LaBadie -
m.roth＠5-cent.us -
Valeri Galtsev -
Александр Кириллов