Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: couldn't get size 0x800000000000000e after kernel upgrade

  1. #1
    Join Date
    Jan 2017
    Beans
    31

    couldn't get size 0x800000000000000e after kernel upgrade

    I ran "apt update && apt upgrade".
    My kernel got updated to GNU/Linux 5.0.0-23-generic x86_64 and now when booting I'm having an error message:
    [ 1.494511] Couldn't get size 0x800000000000000e

    Intel NUC7i5BNK (latest bios: BNKBL357.86A.0080) with Ubuntu Server 18.04.2 LTS with Secure Boot disabled.

    Any one know how to fix this?
    Last edited by panja; August 1st, 2019 at 07:32 PM.

  2. #2
    Join Date
    Jan 2017
    Beans
    31

    Re: couldn't get size 0x800000000000000e after kernel upgrade

    Any one?

  3. #3
    Join Date
    Dec 2006
    Location
    Hamburg, Germany
    Beans
    149
    Distro
    Lubuntu 19.04 Disco Dingo

    Re: couldn't get size 0x800000000000000e after kernel upgrade

    Have you tried with the enabled Secure Boot?
    Dell Latitude E7440 (since Dec 2017). CPU: Intel Core i7-4600U, 2 cores, 4 threads; HDD: PM851 256 GB SSD; RAM: 8 GB DDR3L; Graphics: Intel HD 4400
    Dual-boot /dev/sda5: Lubuntu 19.04, /dev/sda6: Arch Linux

  4. #4
    Join Date
    Jan 2017
    Beans
    31

    Re: couldn't get size 0x800000000000000e after kernel upgrade

    Yes, I've tried it with Secure Boot enabled.
    This gives me the same problem unfortunately.

  5. #5
    Join Date
    Jun 2007
    Location
    Arizona U.S.A.
    Beans
    4,276

    Re: couldn't get size 0x800000000000000e after kernel upgrade

    [ 1.494511] Couldn't get size 0x800000000000000e
    Does your system still boot?

  6. #6
    Join Date
    Jan 2017
    Beans
    31

    Re: couldn't get size 0x800000000000000e after kernel upgrade

    It boots and I can use it without problems.
    It's just not really nice to see error messages.

    I'm using this machine in the living room as a retro game machine.
    Normally it boots up without any prompts or screens but now I have this error message.

    It's just not right...

  7. #7
    Join Date
    Jun 2007
    Location
    Arizona U.S.A.
    Beans
    4,276

    Re: couldn't get size 0x800000000000000e after kernel upgrade

    I've seen the same 'couldn't get size' message several times on some computers in the past (but admittedly not for a long while, though). As long as there is no noticable effect on operation, you should consider it 'informational' and just live with it it. With some future update, it will probably go away.

    You probably know this, but if you run journalctl -b you will see the journal messages generated on startup for the most recent boot. Lots of similar scary chatter in there, some even labeled with ERROR and WARNING. Sometimes some push through the splash barrier.

    I just ran that on this computer looking for 'error' in the output:
    Code:
    [dmn@sydney ~]$ journalctl -b | grep -i error
    Aug 02 06:26:45 sydney kernel: RAS: Correctable Errors collector initialized.
    Aug 02 06:26:45 sydney kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190509/psargs-330)
    Aug 02 06:26:45 sydney kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
    Aug 02 06:26:45 sydney kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190509/psargs-330)
    Aug 02 06:26:45 sydney kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
    Aug 02 06:26:46 sydney snapd[569]: stateengine.go:108: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial tcp: lookup api.snapcraft.io: no such host
    Aug 02 06:26:54 sydney lightdm[598]: Error opening audit socket: Protocol not supported
    Aug 02 06:27:20 sydney pulseaudio[903]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
    
    ---and there is more----
    None of this appeared on the screen on startup. Scary, but don't be too alarmed.
    Last edited by Dennis N; August 2nd, 2019 at 04:24 PM.

  8. #8
    Join Date
    Jul 2007
    Location
    Magic City of the Plains
    Beans
    Hidden!
    Distro
    Xubuntu 19.10 Eoan Ermine

    Re: couldn't get size 0x800000000000000e after kernel upgrade

    journalctrl -b
    Should be journalctl -b

  9. #9
    Join Date
    Jun 2007
    Location
    Arizona U.S.A.
    Beans
    4,276

    Re: couldn't get size 0x800000000000000e after kernel upgrade

    Should be journalctl -b
    Thanks; and corrected.

  10. #10
    Join Date
    Jan 2017
    Beans
    31

    Re: couldn't get size 0x800000000000000e after kernel upgrade

    Thanks guys!

    I do know it’s more an informational message than anything else and normally I won’t be bothered much. But it’s a living room machine which is used by daughters and wife as well. They do get scared with messages like this. 😂

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •