Announcement

Collapse
No announcement yet.

Kubuntu 14.04 reboot option, first shutdown and after a few seconds turn on computer

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Kubuntu 14.04 reboot option, first shutdown and after a few seconds turn on computer

    Hello everybody..

    In this ocation, i bring to you the following:

    On Kubuntu 13.04 64 bits, when I reboot the computer, it turn off the screen, the Kununtu logo appears, an after a few seconds, the computer reboots. All nice.

    But on Kubuntu 14.04 32 or 64 bits, whe I choose Restart computer, from the logout menú, the computer turn off the screen, then, te Kubuntu logo appears, but, the computer shutdowns!. An then, after 4 seconds, aprox, the computer turns on again by itself and boot normally.

    The "problem", consist on, when the computer shutdown after the Reboot option, something sound crackling, as if the disk where stopped by force or something. That sound is not present on normal reboot, or normal shutdown on Kubuntu 13.04

    Is this normal on this version of Kubuntu?, or is a bug, or something similar?

    My computer is a DELL Latitude E5420, with 6gb RAM, and 320Gb Hard Disk. I'm using Kubuntu 14.04 64 bits.

    Thanks in advance.

    #2
    Anything in the log files?

    Please Read Me

    Comment


      #3
      Originally posted by oshunluvr View Post
      Anything in the log files?
      Umm, well, when I open KSystem log, all appears normally, none error. But i'm not sure if Ksystem log show me the past reboot. Sorry, i'm an inexperienced user.

      Comment


        #4
        Go to /var/log and read the previous log files. Look at boot.log, syslog and syslog.1, kern.log and kern.log.1. You're looking for a message about restarting - obviously it would be near the end of the file. If nothing is there, look at ~/.xsession-errors.

        Also, when you start booting, hit the ESC key until text appears (the Kubuntu logo will go away) and read the messages. If you have trouble because of the speed at which they scroll by - try recording it with your cell phone and playing it back in slo-mo.

        Please Read Me

        Comment


          #5
          Thanks, i will try these now..

          Ok, here are the results:

          on Kern.log, i found some suspicius lines:

          May 20 10:29:03 GTRONICK kernel: [ 0.000000] ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tables! (20131115/tbfadt-395)
          May 20 10:29:03 GTRONICK kernel: [ 0.000000] ACPI BIOS Warning (bug): 32/64X FACS address mismatch in FADT - 0xCAFE4E40/0x00000000CAFE4D40, using 32 (20131115/tbfadt-522)
          .
          .
          .
          May 20 10:29:03 GTRONICK kernel: [ 0.000000] No NUMA configuration found
          .
          .
          .
          May 20 10:29:03 GTRONICK kernel: [ 0.228653] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
          May 20 10:29:03 GTRONICK kernel: [ 0.228658] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
          .
          .
          .
          May 20 10:29:03 GTRONICK kernel: [ 0.228672] ACPI: (supports S0 S3 S4 S5)
          May 20 10:29:03 GTRONICK kernel: [ 0.228674] ACPI: Using IOAPIC for interrupt routing
          May 20 10:29:03 GTRONICK kernel: [ 0.228692] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
          May 20 10:29:03 GTRONICK kernel: [ 0.229063] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in ACPI motherboard resources
          May 20 10:29:03 GTRONICK kernel: [ 0.235433] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
          May 20 10:29:03 GTRONICK kernel: [ 0.240704] ACPI: No dock devices found.
          May 20 10:29:03 GTRONICK kernel: [ 0.485570] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
          May 20 10:29:03 GTRONICK kernel: [ 0.485576] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
          May 20 10:29:03 GTRONICK kernel: [ 0.485611] \_SB_.PCI0:_OSC invalid UUID
          May 20 10:29:03 GTRONICK kernel: [ 0.485612] _OSC request data:1 1f 0
          May 20 10:29:03 GTRONICK kernel: [ 0.485616] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
          .
          .
          .
          May 20 12:00:20 GTRONICK kernel: [ 0.486495] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
          May 20 12:00:20 GTRONICK kernel: [ 0.486580] pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
          May 20 12:00:20 GTRONICK kernel: [ 0.486604] pci 0000:00:1a.0: reg 0x10: [mem 0xe3d50000-0xe3d503ff]
          May 20 12:00:20 GTRONICK kernel: [ 0.486699] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
          May 20 12:00:20 GTRONICK kernel: [ 0.486747] pci 0000:00:1a.0: System wakeup disabled by ACPI
          .
          .
          .
          May 20 12:00:20 GTRONICK kernel: [ 15.053666] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251)
          May 20 12:00:20 GTRONICK kernel: [ 15.053675] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
          May 20 12:00:20 GTRONICK kernel: [ 15.053680] ACPI Warning: 0x0000000000000540-0x000000000000054f SystemIO conflicts with Region \GPIO 1 (20131115/utaddress-251)
          May 20 12:00:20 GTRONICK kernel: [ 15.053684] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
          May 20 12:00:20 GTRONICK kernel: [ 15.053686] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20131115/utaddress-251)
          May 20 12:00:20 GTRONICK kernel: [ 15.053690] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
          May 20 12:00:20 GTRONICK kernel: [ 15.053692] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20131115/utaddress-251)
          May 20 12:00:20 GTRONICK kernel: [ 15.053696] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
          May 20 12:00:20 GTRONICK kernel: [ 15.053698] lpc_ich: Resource conflict(s) found affecting gpio_ich
          .
          .
          .

          On syslog:

          May 20 10:29:03 GTRONICK kernel: [ 0.123034] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
          .
          ay 20 10:29:03 GTRONICK kernel: [ 15.199984] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251)
          May 20 10:29:03 GTRONICK kernel: [ 15.199994] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
          May 20 10:29:03 GTRONICK kernel: [ 15.199999] ACPI Warning: 0x0000000000000540-0x000000000000054f SystemIO conflicts with Region \GPIO 1 (20131115/utaddress-251)
          May 20 10:29:03 GTRONICK kernel: [ 15.200004] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
          May 20 10:29:03 GTRONICK kernel: [ 15.200007] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20131115/utaddress-251)
          May 20 10:29:03 GTRONICK kernel: [ 15.200011] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
          May 20 10:29:03 GTRONICK kernel: [ 15.200013] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20131115/utaddress-251)
          May 20 10:29:03 GTRONICK kernel: [ 15.200018] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
          May 20 10:29:03 GTRONICK kernel: [ 15.200020] lpc_ich: Resource conflict(s) found affecting gpio_ich
          .
          .
          .
          May 20 10:29:03 GTRONICK bluetoothd[883]: Starting SDP server
          May 20 10:29:03 GTRONICK bluetoothd[883]: DIS cannot start: GATT is disabled
          May 20 10:29:03 GTRONICK bluetoothd[883]: Failed to init deviceinfo plugin
          May 20 10:29:03 GTRONICK bluetoothd[883]: Failed to init proximity plugin
          May 20 10:29:03 GTRONICK bluetoothd[883]: Failed to init time plugin
          May 20 10:29:03 GTRONICK bluetoothd[883]: Failed to init alert plugin
          May 20 10:29:03 GTRONICK bluetoothd[883]: Failed to init thermometer plugin
          May 20 10:29:03 GTRONICK bluetoothd[883]: Failed to init gatt_example plugin
          May 20 10:29:03 GTRONICK bluetoothd[883]: Bluetooth Management interface initialized
          .
          .
          .
          May 20 10:29:04 GTRONICK NetworkManager[920]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
          .
          .
          May 20 10:29:14 GTRONICK ModemManager[789]: <warn> (ttyUSB1): port attributes not fully set
          May 20 10:29:14 GTRONICK ModemManager[789]: <warn> (ttyUSB0): port attributes not fully set
          May 20 10:29:14 GTRONICK ModemManager[789]: <warn> (ttyUSB2): port attributes not fully set
          .
          .
          May 20 12:26:12 GTRONICK kernel: [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
          May 20 12:26:12 GTRONICK kernel: [ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
          May 20 12:26:12 GTRONICK kernel: [ 0.000000] Checking aperture...
          May 20 12:26:12 GTRONICK kernel: [ 0.000000] No AGP bridge found
          May 20 12:26:12 GTRONICK kernel: [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
          May 20 12:26:12 GTRONICK kernel: [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
          May 20 12:26:12 GTRONICK kernel: [ 0.000000] Memory: 5975888K/6186036K available (7338K kernel code, 1138K rwdata, 3388K rodata, 1332K init, 1440K bss, 210148K reserved)

          on ~/.xsession-errors.:

          Script for none started at run_im.
          Script for auto started at run_im.
          Script for default started at run_im.

          On boot, pressing ESC key:

          All seems to be OK, except for the last line. I nedd time to capture it because my phone's cammera is too bad. I will post these result here when i have that.

          Thanks for your help.
          Last edited by GTRONICK; May 20, 2014, 11:48 AM.

          Comment

          Working...
          X