Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[problem] debian on thinkpad always stuck, freeze

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
howard15
Posts: 6
Joined: 2017-02-10 14:11

[problem] debian on thinkpad always stuck, freeze

#1 Post by howard15 »

Hi all,

I installed debian 9 with cinnamon desktop environment on thinkpad t460p, wifi is intel 8260, graphic card is intel 530 (I also have Nvidia 940MX, but when I installed nvidia driver, it could not log in, so uninstalled nvidia driver, only use intel graphic card). I installed linux-firmware for intel 8260. It always is stuck suddenly, screen is frozen, mouse and keyboard are useless except fn+space can adjust keboard light.

I doubt that it is the wireless card driver problem, because when I use wired cable, it seems ok, I installed linux-firmware for intel wireless card 8260 as:
firmware-iwlwifi/testing,testing,now 20161130-2 all [installed]

did any one meet this before? Thank you

howard15
Posts: 6
Joined: 2017-02-10 14:11

Re: [problem] debian on thinkpad always stuck, freeze

#2 Post by howard15 »

attachment is the syslog file, it happened between 09:59-10:22, anyone can help me?

Feb 10 09:56:27 debian rtkit-daemon[1367]: Watchdog thread running.
Feb 10 09:56:27 debian rtkit-daemon[1367]: Canary thread running.
Feb 10 09:56:27 debian systemd[1]: Started RealtimeKit Scheduling Policy Service.
Feb 10 09:56:27 debian dbus[629]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Feb 10 09:56:27 debian systemd[1]: Starting Daemon for power management...
Feb 10 09:56:27 debian rtkit-daemon[1367]: Successfully made thread 1366 of process 1366 (n/a) owned by '1000' high priority at nice level -11.
Feb 10 09:56:27 debian rtkit-daemon[1367]: Supervising 1 threads of 1 processes of 1 users.
Feb 10 09:56:27 debian dbus[629]: [system] Successfully activated service 'org.freedesktop.UPower'
Feb 10 09:56:27 debian systemd[1]: Started Daemon for power management.
Feb 10 09:56:27 debian dbus-daemon[1139]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
Feb 10 09:56:27 debian systemd[1121]: Starting Virtual filesystem service...
Feb 10 09:56:27 debian dbus-daemon[1139]: Successfully activated service 'org.gtk.vfs.Daemon'
Feb 10 09:56:27 debian systemd[1121]: Started Virtual filesystem service.
Feb 10 09:56:27 debian dbus-daemon[1139]: Activating service name='ca.desrt.dconf'
Feb 10 09:56:27 debian dbus-daemon[1139]: Successfully activated service 'ca.desrt.dconf'
Feb 10 09:56:27 debian dbus-daemon[1139]: Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service'
Feb 10 09:56:27 debian systemd[1121]: Starting Virtual filesystem service - disk device monitor...
Feb 10 09:56:27 debian dbus[629]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 10 09:56:27 debian systemd[1]: Starting Disk Manager...
Feb 10 09:56:27 debian udisksd[1409]: udisks daemon version 2.1.8 starting
Feb 10 09:56:27 debian dbus[629]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 10 09:56:27 debian systemd[1]: Started Disk Manager.
Feb 10 09:56:27 debian udisksd[1409]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 10 09:56:27 debian dbus-daemon[1139]: Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Feb 10 09:56:27 debian systemd[1121]: Started Virtual filesystem service - disk device monitor.
Feb 10 09:56:27 debian dbus-daemon[1139]: Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service'
Feb 10 09:56:27 debian systemd[1121]: Starting Virtual filesystem service - Apple File Conduit monitor...
Feb 10 09:56:27 debian gvfs-afc-volume-monitor[1416]: Volume monitor alive
Feb 10 09:56:27 debian dbus-daemon[1139]: Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Feb 10 09:56:27 debian systemd[1121]: Started Virtual filesystem service - Apple File Conduit monitor.
Feb 10 09:56:27 debian dbus-daemon[1139]: Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service'
Feb 10 09:56:27 debian systemd[1121]: Starting Virtual filesystem service - digital camera monitor...
Feb 10 09:56:27 debian dbus-daemon[1139]: Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Feb 10 09:56:27 debian systemd[1121]: Started Virtual filesystem service - digital camera monitor.
Feb 10 09:56:27 debian dbus-daemon[1139]: Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service'
Feb 10 09:56:27 debian systemd[1121]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Feb 10 09:56:27 debian dbus-daemon[1139]: Activating service name='org.gnome.OnlineAccounts'
Feb 10 09:56:27 debian rtkit-daemon[1367]: Supervising 1 threads of 1 processes of 1 users.
Feb 10 09:56:27 debian rtkit-daemon[1367]: Successfully made thread 1430 of process 1366 (n/a) owned by '1000' RT at priority 5.
Feb 10 09:56:27 debian rtkit-daemon[1367]: Supervising 2 threads of 1 processes of 1 users.
Feb 10 09:56:27 debian rtkit-daemon[1367]: Supervising 2 threads of 1 processes of 1 users.
Feb 10 09:56:27 debian goa-daemon[1429]: goa-daemon version 3.22.4 starting
Feb 10 09:56:27 debian rtkit-daemon[1367]: Successfully made thread 1431 of process 1366 (n/a) owned by '1000' RT at priority 5.
Feb 10 09:56:27 debian rtkit-daemon[1367]: Supervising 3 threads of 1 processes of 1 users.
Feb 10 09:56:27 debian dbus-daemon[1139]: Activating service name='org.gnome.Identity'
Feb 10 09:56:27 debian dbus-daemon[1139]: Successfully activated service 'org.gnome.Identity'
Feb 10 09:56:27 debian dbus-daemon[1139]: Successfully activated service 'org.gnome.OnlineAccounts'
Feb 10 09:56:27 debian dbus-daemon[1139]: Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Feb 10 09:56:27 debian systemd[1121]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Feb 10 09:56:27 debian dbus-daemon[1139]: Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service'
Feb 10 09:56:27 debian systemd[1121]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Feb 10 09:56:27 debian dbus-daemon[1139]: Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Feb 10 09:56:27 debian systemd[1121]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Feb 10 09:56:27 debian dbus[629]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Feb 10 09:56:27 debian systemd[1]: Starting Manage, Install and Generate Color Profiles...
Feb 10 09:56:27 debian avahi-daemon[639]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::6255:dd31:1318:e086.
Feb 10 09:56:27 debian avahi-daemon[639]: New relevant interface wlp3s0.IPv6 for mDNS.
Feb 10 09:56:27 debian avahi-daemon[639]: Registering new address record for fe80::6255:dd31:1318:e086 on wlp3s0.*.
Feb 10 09:56:27 debian dbus[629]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Feb 10 09:56:27 debian systemd[1]: Started Manage, Install and Generate Color Profiles.
Feb 10 09:56:27 debian bluetoothd[633]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSource
Feb 10 09:56:27 debian bluetoothd[633]: Endpoint registered: sender=:1.37 path=/MediaEndpoint/A2DPSink
Feb 10 09:56:27 debian kernel: [ 14.949828] Bluetooth: RFCOMM TTY layer initialized
Feb 10 09:56:27 debian kernel: [ 14.949831] Bluetooth: RFCOMM socket layer initialized
Feb 10 09:56:27 debian kernel: [ 14.949833] Bluetooth: RFCOMM ver 1.11
Feb 10 09:56:28 debian x-session-manager[1131]: WARNING: t+1.07845s: Failed to start app: Unable to start application: Failed to execute child process "/usr/lib/polkit-gnome-authentication-agent-1" (No such file or directory)
Feb 10 09:56:28 debian wpa_supplicant[764]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-40 noise=9999 txrate=400000
Feb 10 09:56:28 debian /cinnamon-killer-daemon: Bound Cinnamon restart to <Control><Alt>Escape.
Feb 10 09:56:28 debian /cinnamon-killer-daemon: Bound Cinnamon restart to <Control><Alt>Escape.
Feb 10 09:56:28 debian dbus-daemon[1139]: Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service'
Feb 10 09:56:28 debian systemd[1121]: Starting Virtual filesystem metadata service...
Feb 10 09:56:28 debian dbus-daemon[1139]: Successfully activated service 'org.gtk.vfs.Metadata'
Feb 10 09:56:28 debian systemd[1121]: Started Virtual filesystem metadata service.
Feb 10 09:56:28 debian dbus[629]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper)
Feb 10 09:56:28 debian dbus-daemon[1139]: Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service'
Feb 10 09:56:28 debian dbus-daemon[1139]: Activation via systemd failed for unit 'dbus-org.bluez.obex.service': Unit dbus-org.bluez.obex.service not found.
Feb 10 09:56:28 debian org.blueman.Mechanism[629]: Unable to init server: Could not connect: Connection refused
Feb 10 09:56:28 debian org.blueman.Mechanism[629]: Unable to init server: Could not connect: Connection refused
Feb 10 09:56:28 debian blueman-mechanism: Starting blueman-mechanism
Feb 10 09:56:28 debian dbus[629]: [system] Successfully activated service 'org.blueman.Mechanism'
Feb 10 09:56:28 debian blueman-mechani[1519]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Feb 10 09:56:28 debian blueman-mechanism: loading Network
Feb 10 09:56:28 debian blueman-mechanism: loading Rfcomm
Feb 10 09:56:28 debian blueman-mechanism: loading RfKill
Feb 10 09:56:28 debian blueman-mechanism: loading Ppp
Feb 10 09:56:29 debian dbus-daemon[1139]: Activating service name='org.gnome.GConf'
Feb 10 09:56:29 debian dbus-daemon[1139]: Successfully activated service 'org.gnome.GConf'
Feb 10 09:56:33 debian systemd[1]: Started Daemon for generating UUIDs.
Feb 10 09:56:33 debian dbus-daemon[1139]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service'
Feb 10 09:56:33 debian systemd[1121]: Starting GNOME Terminal Server...
Feb 10 09:56:33 debian dbus-daemon[1139]: Successfully activated service 'org.gnome.Terminal'
Feb 10 09:56:33 debian systemd[1121]: Started GNOME Terminal Server.
Feb 10 09:56:33 debian kernel: [ 20.989197] nouveau 0000:02:00.0: DRM: evicting buffers...
Feb 10 09:56:33 debian kernel: [ 20.989199] nouveau 0000:02:00.0: DRM: waiting for kernel channels to go idle...
Feb 10 09:56:33 debian kernel: [ 20.989220] nouveau 0000:02:00.0: DRM: suspending client object trees...
Feb 10 09:56:33 debian kernel: [ 20.991925] nouveau 0000:02:00.0: DRM: suspending kernel object tree...
Feb 10 09:56:35 debian kernel: [ 22.401352] nouveau 0000:02:00.0: DRM: resuming kernel object tree...
Feb 10 09:56:35 debian kernel: [ 22.484526] nouveau 0000:02:00.0: priv: HUB0: 6013d4 badf573f (1f408200)
Feb 10 09:56:35 debian kernel: [ 22.544037] nouveau 0000:02:00.0: priv: HUB0: 10ecc0 ffffffff (1f40822c)
Feb 10 09:56:35 debian kernel: [ 22.544672] nouveau 0000:02:00.0: DRM: resuming client object trees...
Feb 10 09:56:37 debian ModemManager[643]: <info> Creating modem with plugin 'Generic' and '1' ports
Feb 10 09:56:37 debian ModemManager[643]: <warn> Could not grab port (tty/ttyS1): 'Cannot add port 'tty/ttyS1', unhandled serial type'
Feb 10 09:56:37 debian ModemManager[643]: <warn> Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:16.3': Failed to find primary AT port
Feb 10 09:56:48 debian systemd-timesyncd[555]: Synchronized to time server 174.123.154.242:123 (2.debian.pool.ntp.org).
Feb 10 09:56:49 debian kernel: [ 36.828557] nouveau 0000:02:00.0: DRM: evicting buffers...
Feb 10 09:56:49 debian kernel: [ 36.828560] nouveau 0000:02:00.0: DRM: waiting for kernel channels to go idle...
Feb 10 09:56:49 debian kernel: [ 36.828583] nouveau 0000:02:00.0: DRM: suspending client object trees...
Feb 10 09:56:49 debian kernel: [ 36.831403] nouveau 0000:02:00.0: DRM: suspending kernel object tree...
Feb 10 09:56:58 debian blueman-mechanism: Exiting
Feb 10 09:59:47 debian kernel: [ 214.262249] tun: Universal TUN/TAP device driver, 1.6
Feb 10 09:59:47 debian kernel: [ 214.262251] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4420] manager: (tun0): new Tun device (/org/freedesktop/NetworkManager/Devices/4)
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4509] devices added (path: /sys/devices/virtual/net/tun0, iface: tun0)
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4509] device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found.
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4510] device (tun0): state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4524] keyfile: add connection in-memory (100936a5-20e2-4a4d-a1ae-3c8a2cc336b0,"tun0")
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4528] device (tun0): state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4534] device (tun0): Activation: starting connection 'tun0' (100936a5-20e2-4a4d-a1ae-3c8a2cc336b0)
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4572] device (tun0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4578] device (tun0): state change: prepare -> config (reason 'none') [40 50 0]
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4581] device (tun0): state change: config -> ip-config (reason 'none') [50 70 0]
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4587] device (tun0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4612] device (tun0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4621] device (tun0): state change: secondaries -> activated (reason 'none') [90 100 0]
Feb 10 09:59:47 debian NetworkManager[636]: <info> [1486738787.4666] device (tun0): Activation: successful, device activated.
Feb 10 09:59:47 debian dbus[629]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Feb 10 09:59:47 debian systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 10 09:59:47 debian dbus[629]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 10 09:59:47 debian systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 10 09:59:47 debian nm-dispatcher: req:1 'up' [tun0]: new request (1 scripts)
Feb 10 09:59:47 debian nm-dispatcher: req:1 'up' [tun0]: start running ordered scripts...
Feb 10 09:59:47 debian systemd[1]: Reloading OpenBSD Secure Shell server.
Feb 10 09:59:47 debian systemd[1]: Reloaded OpenBSD Secure Shell server.
Feb 10 09:59:47 debian systemd[1]: Reloading.
Feb 10 09:59:47 debian systemd[1]: apt-daily.timer: Adding 9h 21min 49.830897s random time.
Feb 10 09:59:47 debian systemd[1]: Reloading OpenBSD Secure Shell server.
Feb 10 09:59:47 debian systemd[1]: Reloaded OpenBSD Secure Shell server.
Feb 10 09:59:47 debian systemd[1]: Reloading.
Feb 10 09:59:47 debian systemd[1]: apt-daily.timer: Adding 9h 10min 52.670173s random time.
Feb 10 10:11:55 debian systemd[1]: Starting Cleanup of Temporary Directories...
Feb 10 10:11:55 debian systemd[1]: Started Cleanup of Temporary Directories.
Feb 10 10:13:05 debian NetworkManager[636]: <info> [1486739585.2850] devices removed (path: /sys/devices/virtual/net/tun0, iface: tun0)
Feb 10 10:13:05 debian NetworkManager[636]: <info> [1486739585.2910] device (tun0): state change: activated -> unmanaged (reason 'unmanaged') [100 10 3]
Feb 10 10:13:05 debian dbus[629]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Feb 10 10:13:05 debian systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 10 10:13:05 debian dbus[629]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 10 10:13:05 debian systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 10 10:13:05 debian nm-dispatcher: req:1 'down' [tun0]: new request (1 scripts)
Feb 10 10:13:05 debian nm-dispatcher: req:1 'down' [tun0]: start running ordered scripts...
Feb 10 10:21:13 debian kernel: [ 0.000000] Linux version 4.9.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170124 (Debian 6.3.0-5) ) #1 SMP Debian 4.9.6-3 (2017-01-28)
Feb 10 10:21:13 debian kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-1-amd64 root=UUID=c9863009-1752-438e-9f3d-65027b4cf594 ro intel_idle.max_cstate=1 quiet
Feb 10 10:21:13 debian kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Feb 10 10:21:13 debian kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Feb 10 10:21:13 debian kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Feb 10 10:21:13 debian kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Feb 10 10:21:13 debian kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Feb 10 10:21:13 debian kernel: [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Feb 10 10:21:13 debian kernel: [ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
Feb 10 10:21:13 debian kernel: [ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
Feb 10 10:21:13 debian kernel: [ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Feb 10 10:21:13 debian kernel: [ 0.000000] x86/fpu: Using 'eager' FPU context switches.
Feb 10 10:21:13 debian kernel: [ 0.000000] e820: BIOS-provided physical RAM map:
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000008bfff] usable
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x000000000008c000-0x00000000000fffff] reserved
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000008bdd5fff] usable
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x000000008bdd6000-0x000000008bdd6fff] ACPI NVS
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x000000008bdd7000-0x000000008be00fff] reserved
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x000000008be01000-0x00000000961eafff] usable
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x00000000961eb000-0x000000009623bfff] type 20
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x000000009623c000-0x0000000097eaefff] reserved
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x0000000097eaf000-0x0000000097faefff] ACPI NVS
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x0000000097faf000-0x0000000097ffefff] ACPI data
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x0000000097fff000-0x0000000097ffffff] usable
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x0000000098000000-0x00000000980fffff] reserved
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x0000000098600000-0x000000009c7fffff] reserved
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x00000000f80fa000-0x00000000f80fafff] reserved
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x00000000f80fd000-0x00000000f80fdfff] reserved
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Feb 10 10:21:13 debian kernel: [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000003617fffff] usable

User avatar
bw123
Posts: 4015
Joined: 2011-05-09 06:02
Has thanked: 1 time
Been thanked: 28 times

Re: [problem] debian on thinkpad always stuck, freeze

#3 Post by bw123 »

Why don't you add some more details about your thinkpad, like how much RAM, is it stock or have you upgraded the memory?

a link to the specs and hardware details for your t460p might help, do a websearch and find some info for the readers, it might help solve it quicker.

https://en.wikipedia.org/wiki/E820
resigned by AI ChatGPT

User avatar
Thorny
Posts: 542
Joined: 2011-02-27 13:40

Re: [problem] debian on thinkpad always stuck, freeze

#4 Post by Thorny »

howard15 wrote:attachment is the syslog file, it happened between 09:59-10:22, anyone can help me?
I notice that you are using the intel_idle.max_cstate=1 parameter on the command line when booting your system (at 10:21:13). Why is that? That command line parameter is used to stop "Bay Trail" processors from freezing but it probably isn't appropriate for a core i5 processor which is what my search for T460p turned up.

Even if it was a "Bay Trail" processor, the kernel you are using shouldn't need that parameter.

Perhaps you tried that as a freezing solution but forgot to remove it when it didn't help. I wonder if your system would run any better if you removed that parameter from the GRUB boot line? It would be a good idea to tell us anything else that you may have tried while trying to stop the freezing.


By the way, the "testing" version isn't Debian 9 yet, that happens when Debian 9, Stretch is released. It's still in the testing phase and things can still break.

howard15
Posts: 6
Joined: 2017-02-10 14:11

Re: [problem] debian on thinkpad always stuck, freeze

#5 Post by howard15 »

details about my laptop:

Processor Intel Core i5-6440HQ MB
graphic cards: NVIDIA GeForce 940MX 2GB + intel 530
Camera 720p HD Camera
Hard drive 500GB HD 7200RPM SATA3 + Transcend 128GB SATA III 6Gb/s MTS400 42 mm M.2 SSD Solid State Drive (TS128GMTS400)
Total memory 4GB DDR4 2133 SoDIMM + Kingston Technology HyperX Impact 8GB 2133MHz DDR4 CL13 SODIMM Laptop Memory HX421S13IB/8
Pointing device Fingerprint Reader
WiFi wireless LAN adapters Intel 8260AC+BT 2x2 vPro
TPM Setting Software TPM Enabled

Linux debian 4.9.0-1-amd64 #1 SMP Debian 4.9.6-3 (2017-01-28) x86_64 GNU/Linux

I use intel_idle.max_cstate=1 because I found freeze problem on linux mint 18 forum
Last edited by howard15 on 2017-02-14 02:17, edited 1 time in total.

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: [problem] debian on thinkpad always stuck, freeze

#6 Post by stevepusser »

So it's a Skylake processor with Intel 530 integrated graphics. Do you have any non-free intel-microcode and firmware packages installed to see if those make any difference?
MX Linux packager and developer

User avatar
fireExit
Posts: 559
Joined: 2014-11-20 11:22

Re: [problem] debian on thinkpad always stuck, freeze

#7 Post by fireExit »

http://www.geforce.co.uk/hardware/noteb ... x/features
howard15 wrote:graphic card is intel 530 (I also have Nvidia 940MX
Nvidia optimus.

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: [problem] debian on thinkpad always stuck, freeze

#8 Post by stevepusser »

Should split the freeze and Nvidia problems into separate threads.
MX Linux packager and developer

howard15
Posts: 6
Joined: 2017-02-10 14:11

Re: [problem] debian on thinkpad always stuck, freeze

#9 Post by howard15 »

Thorny wrote:
howard15 wrote:attachment is the syslog file, it happened between 09:59-10:22, anyone can help me?
I notice that you are using the intel_idle.max_cstate=1 parameter on the command line when booting your system (at 10:21:13). Why is that? That command line parameter is used to stop "Bay Trail" processors from freezing but it probably isn't appropriate for a core i5 processor which is what my search for T460p turned up.

Even if it was a "Bay Trail" processor, the kernel you are using shouldn't need that parameter.

Perhaps you tried that as a freezing solution but forgot to remove it when it didn't help. I wonder if your system would run any better if you removed that parameter from the GRUB boot line? It would be a good idea to tell us anything else that you may have tried while trying to stop the freezing.


By the way, the "testing" version isn't Debian 9 yet, that happens when Debian 9, Stretch is released. It's still in the testing phase and things can still break.
Hi Thorny,
I use intel_idle.max_cstate=1 because I found freeze problem on linux mint 18 forum,
I removed this parameter, the problem is still there.

howard15
Posts: 6
Joined: 2017-02-10 14:11

Re: [problem] debian on thinkpad always stuck, freeze

#10 Post by howard15 »

stevepusser wrote:Should split the freeze and Nvidia problems into separate threads.
I just want to solve the freeze problem, I do not need use Nvidia card.

howard15
Posts: 6
Joined: 2017-02-10 14:11

Re: [problem] debian on thinkpad always stuck, freeze

#11 Post by howard15 »

stevepusser wrote:So it's a Skylake processor with Intel 530 integrated graphics. Do you have any non-free intel-microcode and firmware packages installed to see if those make any difference?
I installed firmware-linux-nonfree and firmware-iwlwifi, problem still exists

User avatar
airborne_rodent
Posts: 14
Joined: 2011-08-25 13:02
Location: France

Re: [problem] debian on thinkpad always stuck, freeze

#12 Post by airborne_rodent »

Can you relate this to any specific software? For example, are you running firefox when the freeze occures? (There's a not-well-reported firefox problem lurking around with exactly this symptoms).
(\__/)
(='.'=) This is Bunny. Copy and paste Bunny into your
(")_(") signature to help him gain world domination

Post Reply