LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-08-2019, 05:05 AM   #1
Twigster
LQ Newbie
 
Registered: Oct 2019
Location: France
Distribution: Slackware64 14.2
Posts: 11

Rep: Reputation: Disabled
Question My Dell D620 laptop hangs/freezes randomly on slackware64 14.2


Hello,

I recently removed windows XP() from my Dell latitude d620 laptop and installed slackware64 with multilib and xfce following the slackware wiki, with kernel 4.4.190

All went relatively ok, and I mainly browse the web on that machine(firefox 68 esr) but at random times (2 or 3 times a day) the laptop would freeze : my mouse led would shut down, the wifi led keeps flickering, the hardware network switch does nothing, etc). Only way out is to power down the machine and restart.

Sometimes the computer randomly reboots too.
Both these problems happen mainly on the web (because thats what i do the most) but it also happened reading a pdf with okular)

This is the first time I'm investigating a problem like that.

Here is syslog excerpt from such a crash that occurred today around 10:45 (i booted at 10:38)

Code:
ct  8 10:38:48 lagann kernel: [    0.000000] ACPI: RSDP 0x00000000000FC0C0 000014 (v00 DELL  )
Oct  8 10:38:48 lagann kernel: [    0.000000] ACPI: RSDT 0x00000000CF6819CC 000044 (v01 DELL   M07      27D70403 ASL  00000061)
Oct  8 10:38:48 lagann kernel: [    0.000000] ACPI: FACP 0x00000000CF682800 000074 (v01 DELL   M07      27D70403 ASL  00000061)
Oct  8 10:38:48 lagann kernel: [    0.000000] ACPI: DSDT 0x00000000CF683400 00519E (v01 INT430 SYSFexxx 00001001 INTL 20050624)
Oct  8 10:38:48 lagann kernel: [    0.000000] ACPI: FACS 0x00000000CF691C00 000040
Oct  8 10:38:48 lagann kernel: [    0.000000] ACPI: HPET 0x00000000CF682F00 000038 (v01 DELL   M07      00000001 ASL  00000061)
Oct  8 10:38:48 lagann kernel: [    0.000000] ACPI: APIC 0x00000000CF683000 000068 (v01 DELL   M07      27D70403 ASL  00000047)
Oct  8 10:38:48 lagann kernel: [    0.000000] ACPI: ASF! 0x00000000CF682C00 00005B (v16 DELL   M07      27D70403 ASL  00000061)
Oct  8 10:38:48 lagann kernel: [    0.000000] ACPI: MCFG 0x00000000CF682FC0 00003E (v16 DELL   M07      27D70403 ASL  00000061)
Oct  8 10:38:48 lagann kernel: [    0.000000] ACPI: SLIC 0x00000000CF68309C 000176 (v01 DELL   M07      27D70403 ASL  00000061)
Oct  8 10:38:48 lagann kernel: [    0.000000] ACPI: TCPA 0x00000000CF683300 000032 (v01 DELL   M07      27D70403 ASL  00000061)
Oct  8 10:38:48 lagann kernel: [    0.000000] ACPI: SSDT 0x00000000CF681A53 0004DC (v01 PmRef  CpuPm    00003000 INTL 20050624)
Oct  8 10:38:48 lagann kernel: [    0.007642] ACPI: 2 ACPI AML tables successfully acquired and loaded
Oct  8 10:38:48 lagann kernel: [    0.062000] perf_event_intel: PEBS disabled due to CPU errata
Oct  8 10:38:48 lagann kernel: [    0.064000] TSC synchronization [CPU#0 -> CPU#1]:
Oct  8 10:38:48 lagann kernel: [    0.064000] Measured 3743467600 cycles TSC warp between CPUs, turning off TSC clock.
Oct  8 10:38:48 lagann kernel: [    0.226135] ACPI: Dynamic OEM Table Load:
Oct  8 10:38:48 lagann kernel: [    0.226288] ACPI: SSDT 0xFFFF8800CB580CC0 000043 (v01 LMPWR  DELLLOM  00001001 INTL 20050624)
Oct  8 10:38:48 lagann kernel: [    0.227126] ACPI: Dynamic OEM Table Load:
Oct  8 10:38:48 lagann kernel: [    0.227277] ACPI: SSDT 0xFFFF8800CB586800 000202 (v01 PmRef  Cpu0Ist  00003000 INTL 20050624)
Oct  8 10:38:48 lagann kernel: [    0.227901] ACPI: Dynamic OEM Table Load:
Oct  8 10:38:48 lagann kernel: [    0.228006] ACPI: SSDT 0xFFFF8800CB633E00 0001C6 (v01 PmRef  Cpu0Cst  00003001 INTL 20050624)
Oct  8 10:38:48 lagann kernel: [    0.228775] ACPI: Dynamic OEM Table Load:
Oct  8 10:38:48 lagann kernel: [    0.229082] ACPI: SSDT 0xFFFF8800CB5F5E00 0000C4 (v01 PmRef  Cpu1Ist  00003000 INTL 20050624)
Oct  8 10:38:48 lagann kernel: [    0.229664] ACPI: Dynamic OEM Table Load:
Oct  8 10:38:48 lagann kernel: [    0.229816] ACPI: SSDT 0xFFFF8800CB60A000 000085 (v01 PmRef  Cpu1Cst  00003000 INTL 20050624)
Oct  8 10:38:49 lagann kernel: [    0.310402] pci 0000:00:1e.0: bridge has subordinate 04 but max busn 07
Oct  8 10:38:49 lagann kernel: [    0.323088] ACPI: Enabled 3 GPEs in block 00 to 1F
Oct  8 10:38:49 lagann kernel: [    0.360980] pnp 00:01: disabling [io  0x1000-0x1005] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct  8 10:38:49 lagann kernel: [    0.361132] pnp 00:01: disabling [io  0x1008-0x100f] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct  8 10:38:49 lagann kernel: [    0.361450] pnp 00:02: disabling [io  0x1006-0x1007] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct  8 10:38:49 lagann kernel: [    0.361591] pnp 00:02: disabling [io  0x100a-0x1059] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct  8 10:38:49 lagann kernel: [    0.361733] pnp 00:02: disabling [io  0x1060-0x107f] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct  8 10:38:49 lagann kernel: [    0.361874] pnp 00:02: disabling [io  0x1010-0x102f] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct  8 10:38:49 lagann kernel: [    0.419114] OCFS2 User DLM kernel interface loaded
Oct  8 10:38:49 lagann kernel: [    0.458805] scsi: <fdomain> Detection failed (no card)
Oct  8 10:38:49 lagann kernel: [    0.458926] qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 8.07.00.26-k.
Oct  8 10:38:49 lagann kernel: [    0.459107] Emulex LightPulse Fibre Channel SCSI driver 11.0.0.0.
Oct  8 10:38:49 lagann kernel: [    0.459195] Copyright(c) 2004-2015 Emulex.  All rights reserved.
Oct  8 10:38:49 lagann kernel: [    0.460235] GDT-HA: Storage RAID Controller Driver. Version: 3.05
Oct  8 10:38:49 lagann kernel: [    0.460382] 3ware Storage Controller device driver for Linux v1.26.02.003.
Oct  8 10:38:49 lagann kernel: [    0.460494] 3ware 9000 Storage Controller device driver for Linux v2.26.02.014.
Oct  8 10:38:49 lagann kernel: [    3.496530] EXT4-fs (sda2): couldn't mount as ext3 due to feature incompatibilities
Oct  8 10:38:49 lagann kernel: [    4.236639] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  8 10:38:49 lagann kernel: [    4.247821] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
Oct  8 10:38:49 lagann kernel: [    4.321981] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  8 10:38:49 lagann kernel: [    4.325178] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  8 10:38:49 lagann kernel: [    4.443837] kvm: disabled by bios
Oct  8 10:38:49 lagann kernel: [    4.456230] kvm: disabled by bios
Oct  8 10:38:49 lagann kernel: [    4.462564] coretemp coretemp.0: Using relative temperature scale!
Oct  8 10:38:49 lagann kernel: [    4.462598] coretemp coretemp.0: Using relative temperature scale!
Oct  8 10:38:49 lagann kernel: [    4.503213]  excluding 0xe0000000-0xe07fffff 0xe4000000-0xebffffff
Oct  8 10:38:49 lagann kernel: [    4.504111] iwl3945 0000:0c:00.0: can't disable ASPM; OS doesn't have ASPM control
Oct  8 10:38:49 lagann kernel: [    4.825437]  excluding 0xc0000-0xcffff 0xe0000-0xfffff
Oct  8 10:38:49 lagann kernel: [    4.825544]  excluding 0x60000000-0x60ffffff
Oct  8 10:38:49 lagann kernel: [    4.825636]  excluding 0xa0000000-0xa0ffffff
Oct  8 10:38:49 lagann kernel: [   13.132566] kvm: disabled by bios
Oct  8 10:38:49 lagann kernel: [   13.141930] kvm: disabled by bios
Oct  8 10:38:52 lagann ntpd[1320]: restrict: 'monitor' cannot be disabled while 'limited' is enabled
Oct  8 10:39:00 lagann console-kit-daemon[1342]: WARNING: Failed to let cgmanager know that it can remove the cgroup when it's empty, the error was: invalid request 
Oct  8 10:39:02 lagann pulseaudio[1774]: [pulseaudio] pid.c: Stale PID file, overwriting.
Oct  8 10:39:03 lagann pulseaudio[1774]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.35" (uid=1000 pid=1774 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=1269 comm="/usr/sbin/bluetoothd ")
Oct  8 11:03:08 lagann kernel: [    0.000000] ACPI: RSDP 0x00000000000FC0C0 000014 (v00 DELL  )
Oct  8 11:03:08 lagann kernel: [    0.000000] ACPI: RSDT 0x00000000CF6819CC 000044 (v01 DELL   M07      27D70403 ASL  00000061)
Oct  8 11:03:08 lagann kernel: [    0.000000] ACPI: FACP 0x00000000CF682800 000074 (v01 DELL   M07      27D70403 ASL  00000061)
Oct  8 11:03:08 lagann kernel: [    0.000000] ACPI: DSDT 0x00000000CF683400 00519E (v01 INT430 SYSFexxx 00001001 INTL 20050624)
Oct  8 11:03:08 lagann kernel: [    0.000000] ACPI: FACS 0x00000000CF691C00 000040
Oct  8 11:03:08 lagann kernel: [    0.000000] ACPI: HPET 0x00000000CF682F00 000038 (v01 DELL   M07      00000001 ASL  00000061)
Oct  8 11:03:08 lagann kernel: [    0.000000] ACPI: APIC 0x00000000CF683000 000068 (v01 DELL   M07      27D70403 ASL  00000047)
Oct  8 11:03:08 lagann kernel: [    0.000000] ACPI: ASF! 0x00000000CF682C00 00005B (v16 DELL   M07      27D70403 ASL  00000061)
Oct  8 11:03:08 lagann kernel: [    0.000000] ACPI: MCFG 0x00000000CF682FC0 00003E (v16 DELL   M07      27D70403 ASL  00000061)
Oct  8 11:03:08 lagann kernel: [    0.000000] ACPI: SLIC 0x00000000CF68309C 000176 (v01 DELL   M07      27D70403 ASL  00000061)
Oct  8 11:03:08 lagann kernel: [    0.000000] ACPI: TCPA 0x00000000CF683300 000032 (v01 DELL   M07      27D70403 ASL  00000061)
Oct  8 11:03:08 lagann kernel: [    0.000000] ACPI: SSDT 0x00000000CF681A53 0004DC (v01 PmRef  CpuPm    00003000 INTL 20050624)
Oct  8 11:03:08 lagann kernel: [    0.007431] ACPI: 2 ACPI AML tables successfully acquired and loaded
Oct  8 11:03:08 lagann kernel: [    0.063000] perf_event_intel: PEBS disabled due to CPU errata
Oct  8 11:03:08 lagann kernel: [    0.065000] TSC synchronization [CPU#0 -> CPU#1]:
Oct  8 11:03:08 lagann kernel: [    0.065000] Measured 4096278130 cycles TSC warp between CPUs, turning off TSC clock.
Oct  8 11:03:08 lagann kernel: [    0.227423] ACPI: Dynamic OEM Table Load:
Oct  8 11:03:08 lagann kernel: [    0.227576] ACPI: SSDT 0xFFFF8800CB580CC0 000043 (v01 LMPWR  DELLLOM  00001001 INTL 20050624)
Oct  8 11:03:08 lagann kernel: [    0.228365] ACPI: Dynamic OEM Table Load:
Oct  8 11:03:08 lagann kernel: [    0.228517] ACPI: SSDT 0xFFFF8800CB586800 000202 (v01 PmRef  Cpu0Ist  00003000 INTL 20050624)
Oct  8 11:03:08 lagann kernel: [    0.229145] ACPI: Dynamic OEM Table Load:
Oct  8 11:03:08 lagann kernel: [    0.230006] ACPI: SSDT 0xFFFF8800CB633C00 0001C6 (v01 PmRef  Cpu0Cst  00003001 INTL 20050624)
Oct  8 11:03:08 lagann kernel: [    0.231180] ACPI: Dynamic OEM Table Load:
Oct  8 11:03:08 lagann kernel: [    0.231331] ACPI: SSDT 0xFFFF8800CB5F5E00 0000C4 (v01 PmRef  Cpu1Ist  00003000 INTL 20050624)
Oct  8 11:03:08 lagann kernel: [    0.231911] ACPI: Dynamic OEM Table Load:
Oct  8 11:03:08 lagann kernel: [    0.232006] ACPI: SSDT 0xFFFF8800CB5FEF00 000085 (v01 PmRef  Cpu1Cst  00003000 INTL 20050624)
Oct  8 11:03:08 lagann kernel: [    0.310006] pci 0000:00:1e.0: bridge has subordinate 04 but max busn 07
Oct  8 11:03:08 lagann kernel: [    0.323087] ACPI: Enabled 3 GPEs in block 00 to 1F
Oct  8 11:03:08 lagann kernel: [    0.361018] pnp 00:01: disabling [io  0x1000-0x1005] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct  8 11:03:08 lagann kernel: [    0.361160] pnp 00:01: disabling [io  0x1008-0x100f] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct  8 11:03:08 lagann kernel: [    0.361476] pnp 00:02: disabling [io  0x1006-0x1007] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct  8 11:03:08 lagann kernel: [    0.361619] pnp 00:02: disabling [io  0x100a-0x1059] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct  8 11:03:08 lagann kernel: [    0.361760] pnp 00:02: disabling [io  0x1060-0x107f] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct  8 11:03:08 lagann kernel: [    0.361902] pnp 00:02: disabling [io  0x1010-0x102f] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct  8 11:03:08 lagann kernel: [    0.421109] OCFS2 User DLM kernel interface loaded
Oct  8 11:03:08 lagann kernel: [    0.460766] scsi: <fdomain> Detection failed (no card)
Oct  8 11:03:08 lagann kernel: [    0.460889] qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 8.07.00.26-k.
Oct  8 11:03:08 lagann kernel: [    0.461067] Emulex LightPulse Fibre Channel SCSI driver 11.0.0.0.
Oct  8 11:03:08 lagann kernel: [    0.461155] Copyright(c) 2004-2015 Emulex.  All rights reserved.
Oct  8 11:03:08 lagann kernel: [    0.462192] GDT-HA: Storage RAID Controller Driver. Version: 3.05
Oct  8 11:03:08 lagann kernel: [    0.462340] 3ware Storage Controller device driver for Linux v1.26.02.003.
Oct  8 11:03:08 lagann kernel: [    0.462452] 3ware 9000 Storage Controller device driver for Linux v2.26.02.014.
Oct  8 11:03:08 lagann kernel: [    3.496537] EXT4-fs (sda2): couldn't mount as ext3 due to feature incompatibilities
Oct  8 11:03:08 lagann kernel: [    4.370289] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  8 11:03:08 lagann kernel: [    4.386690] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
now messages :
Code:
Oct  8 10:39:20 lagann NetworkManager[1286]: <info>  [1570523960.8817] Config: added 'scan_ssid' value '1'
Oct  8 10:39:20 lagann NetworkManager[1286]: <info>  [1570523960.8818] Config: added 'key_mgmt' value 'WPA-PSK'
Oct  8 10:39:20 lagann NetworkManager[1286]: <info>  [1570523960.8819] Config: added 'auth_alg' value 'OPEN'
Oct  8 10:39:20 lagann NetworkManager[1286]: <info>  [1570523960.8819] Config: added 'psk' value '<hidden>'
Oct  8 10:39:21 lagann kernel: [   44.371242] wlan0: authenticate with fc:ec:da:a2:7c:8d
Oct  8 10:39:21 lagann kernel: [   44.372683] wlan0: send auth to fc:ec:da:a2:7c:8d (try 1/3)
Oct  8 10:39:21 lagann kernel: [   44.377114] wlan0: authenticated
Oct  8 10:39:21 lagann kernel: [   44.378279] wlan0: associate with fc:ec:da:a2:7c:8d (try 1/3)
Oct  8 10:39:21 lagann kernel: [   44.382550] wlan0: RX AssocResp from fc:ec:da:a2:7c:8d (capab=0x411 status=0 aid=6)
Oct  8 10:39:21 lagann kernel: [   44.383949] wlan0: associated
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.0877] device (wlan0): supplicant interface state: inactive -> authenticating
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.0879] device (wlan0): supplicant interface state: authenticating -> associating
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.1081] device (wlan0): supplicant interface state: associating -> completed
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.1082] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'AFR-OS'.
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.1095] device (wlan0): state change: config -> ip-config (reason 'none', internal state 'managed')
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.1110] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.1255] dhcp4 (wlan0): dhcpcd started with pid 2079
Oct  8 10:39:21 lagann dhcpcd[2079]: DUID 00:01:00:01:24:f9:ba:64:00:1b:77:d2:68:37
Oct  8 10:39:21 lagann dhcpcd[2079]: wlan0: IAID 77:d2:68:37
Oct  8 10:39:21 lagann dhcpcd[2079]: wlan0: rebinding lease of 192.168.1.62
Oct  8 10:39:21 lagann dhcpcd[2079]: wlan0: leased 192.168.1.62 for 86400 seconds
Oct  8 10:39:21 lagann dhcpcd[2079]: wlan0: adding route to 192.168.1.0/24
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9470] dhcp4 (wlan0):   address 192.168.1.62
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9470] dhcp4 (wlan0):   plen 24 (255.255.255.0)
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9470] dhcp4 (wlan0):   gateway 192.168.1.1
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9471] dhcp4 (wlan0):   lease time 86400
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9471] dhcp4 (wlan0):   nameserver '192.168.1.1'
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9471] dhcp4 (wlan0):   domain name 'home'
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9471] dhcp4 (wlan0): state changed unknown -> bound
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9488] device (wlan0): state change: ip-config -> ip-check (reason 'none', internal state 'managed')
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9503] device (wlan0): state change: ip-check -> secondaries (reason 'none', internal state 'managed')
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9509] device (wlan0): state change: secondaries -> activated (reason 'none', internal state 'managed')
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9512] manager: NetworkManager state is now CONNECTED_LOCAL
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9584] manager: NetworkManager state is now CONNECTED_SITE
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9587] policy: set 'AFR-OS' (wlan0) as default for IPv4 routing and DNS
Oct  8 10:39:21 lagann dhcpcd[2079]: wlan0: removing route to 192.168.1.0/24
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9627] device (wlan0): Activation: successful, device activated.
Oct  8 10:39:21 lagann dbus[1267]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Oct  8 10:39:21 lagann NetworkManager[1286]: <info>  [1570523961.9704] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct  8 10:39:21 lagann dbus[1267]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct  8 10:39:22 lagann nm-dispatcher: req:1 'up' [wlan0]: new request (0 scripts)
Oct  8 10:39:22 lagann nm-dispatcher: req:1 'up' [wlan0]: completed: no scripts
Oct  8 10:39:22 lagann nm-dispatcher: req:2 'connectivity-change': new request (0 scripts)
Oct  8 10:39:22 lagann nm-dispatcher: req:2 'connectivity-change': completed: no scripts
Oct  8 10:39:24 lagann ntpd[1320]: Listen normally on 4 wlan0 192.168.1.62:123
Oct  8 10:39:24 lagann ntpd[1320]: Listen normally on 5 wlan0 [fe80::21b:77ff:fed2:6837%3]:123
Oct  8 10:39:55 lagann kernel: [   78.391076] usb 1-5: new high-speed USB device number 7 using ehci-pci
Oct  8 10:39:55 lagann kernel: [   78.507521] usb 1-5: New USB device found, idVendor=090c, idProduct=1000
Oct  8 10:39:55 lagann kernel: [   78.507532] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  8 10:39:55 lagann kernel: [   78.507539] usb 1-5: Product: USB Flash Disk
Oct  8 10:39:55 lagann kernel: [   78.507545] usb 1-5: Manufacturer: General
Oct  8 10:39:55 lagann kernel: [   78.507551] usb 1-5: SerialNumber: 04EKW9DNHADXIL7W
Oct  8 10:39:55 lagann mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5" 
Oct  8 10:39:55 lagann mtp-probe: bus: 1, device: 7 was not an MTP device 
Oct  8 10:39:55 lagann kernel: [   79.089045] usb-storage 1-5:1.0: USB Mass Storage device detected
Oct  8 10:39:55 lagann kernel: [   79.089301] scsi host2: usb-storage 1-5:1.0
Oct  8 10:39:55 lagann kernel: [   79.089496] usbcore: registered new interface driver usb-storage
Oct  8 10:39:55 lagann kernel: [   79.091298] usbcore: registered new interface driver uas
Oct  8 10:39:58 lagann kernel: [   81.930071] scsi 2:0:0:0: Direct-Access     General  USB Flash Disk   1100 PQ: 0 ANSI: 4
Oct  8 10:39:58 lagann kernel: [   81.933586] sd 2:0:0:0: [sdb] 30515200 512-byte logical blocks: (15.6 GB/14.6 GiB)
Oct  8 10:39:58 lagann kernel: [   81.934670] sd 2:0:0:0: [sdb] Write Protect is off
Oct  8 10:39:58 lagann kernel: [   81.935681] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct  8 10:39:58 lagann kernel: [   81.948922] sd 2:0:0:0: [sdb] Attached SCSI removable disk
Oct  8 10:53:53 lagann root: ACPI group jack / action headphone is not defined
Oct  8 10:53:58 lagann root: ACPI group jack / action headphone is not defined
Oct  8 11:03:08 lagann syslogd 1.5.1: restart.
Oct  8 11:03:08 lagann kernel: klogd 1.5.1, log

I also looked at Xorg.log.old :
Code:
[    17.164] 
[    17.676] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 14)
[    17.676] (**) Option "xkb_rules" "evdev"
[    17.676] (**) Option "xkb_layout" "fr"
[    17.676] (**) Option "xkb_variant" "latin9"
[    17.676] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[    19.243] (II) intel(0): EDID vendor "AUO", prod id 15172
[    19.243] (II) intel(0): DDCModeFromDetailedTiming: 1280x800 Warning: We only handle separate sync.
[    19.243] (II) intel(0): Printing DDC gathered Modelines:
[    19.243] (II) intel(0): Modeline "1280x800"x0.0   71.11  1280 1328 1360 1440  800 803 809 823 -hsync -vsync (49.4 kHz eP)
[    19.243] (II) intel(0): Modeline "1280x800"x0.0   59.26  1280 1328 1360 1440  800 803 809 823 -hsync -vsync (41.2 kHz e)
And finally ~/.xsession-errors :
Code:
/usr/bin/startxfce4: X server already running on display :0
libpager-Message: Setting the pager rows returned false. Maybe the setting is not applied.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
system-config-printer-applet: failed to start NewPrinterNotification service
system-config-printer-applet: failed to start PrinterDriversInstaller service: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.48" is not allowed to own the service "com.redhat.PrinterDriversInstaller" due to security policies in the configuration file
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
ERROR:dbus.proxies:Introspect error on :1.0:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.50" (uid=1000 pid=1779 comm="/usr/bin/python2.7 /usr/bin/blueman-applet ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=1272 comm="/usr/sbin/bluetoothd ")
blueman-applet version 2.0.6 starting
Traceback (most recent call last):
  File "/usr/bin/blueman-applet", line 121, in <module>
    BluemanApplet()
  File "/usr/bin/blueman-applet", line 63, in __init__
    self.Plugins.Load()
  File "/usr/lib64/python2.7/site-packages/blueman/main/PluginManager.py", line 90, in Load
    __import__(self.module_path.__name__ + ".%s" % plugin, None, None, [])
  File "/usr/lib64/python2.7/site-packages/blueman/plugins/applet/DBusService.py", line 12, in <module>
    from blueman.main.applet.BluezAgent import AdapterAgent
  File "/usr/lib64/python2.7/site-packages/blueman/main/applet/BluezAgent.py", line 23, in <module>
    from blueman.bluez.Agent import Agent, AgentMethod
  File "/usr/lib64/python2.7/site-packages/blueman/bluez/Agent.py", line 48, in <module>
    class Agent(dbus.service.Object):
  File "/usr/lib64/python2.7/site-packages/blueman/bluez/Agent.py", line 56, in Agent
    @AgentMethod
  File "/usr/lib64/python2.7/site-packages/blueman/bluez/Agent.py", line 38, in AgentMethod
    if BlueZInterface.get_interface_version()[0] < 5:
  File "/usr/lib64/python2.7/site-packages/blueman/bluez/BlueZInterface.py", line 17, in get_interface_version
    introspection = dbus.Interface(obj, 'org.freedesktop.DBus.Introspectable').Introspect()
  File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.50" (uid=1000 pid=1779 comm="/usr/bin/python2.7 /usr/bin/blueman-applet ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=1272 comm="/usr/sbin/bluetoothd ")
kbuildsycoca4 running...
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/asemmar/.kde/share/config/activitymanager-pluginsrc
[Child 2175, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /tmp/firefox-68.0.2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358




thunar-volman: Unsupported USB device type "usb".
thunar-volman: Unsupported USB device type "usb-storage".

(xfwm4:1608): xfwm4-WARNING **: Unmanaged net_wm_state (window 0x56005c7, atom "None")
I do not fully understand what goes wrong in my xsession. I do not use any bluetooth device. And even if blueman has an issue, I hardly see how it makes the whole machine hang.

My feeble linux skills do not allow me to see an obvious issue or message from the kernel. Maybe I do not look straight or do not look at the right place.

Please, would you help me figuring out where to look to solve this mystery? I like slackware's hands on approach, and this is a good way for me to learn more about linux.

Cheers
 
Old 10-08-2019, 06:41 PM   #2
abga
Senior Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 1,201

Rep: Reputation: 634Reputation: 634Reputation: 634Reputation: 634Reputation: 634Reputation: 634
The HW could be faulty and the RAM should be the first to test.
Here in this recent thread you'll get what it needs to test the RAM (link to the memtest86+ on SlackBuilds) together with some useful info:
https://www.linuxquestions.org/quest...em-4175661557/

P.S. I just recall that I used one of those D620 (heavy piece of sh ... almost broke my shoulder/neck with it) with a company I worked many years ago and during many business trips I managed to block the heatsink with dust (was totally clogged). It would just hang and crash (turn off too) randomly and had to send it in service.

Worth monitoring your CPU temperature on that system. Ways to do it on Linux:
https://superuser.com/questions/4362...ck-temperature

Last edited by abga; 10-08-2019 at 06:54 PM. Reason: P.S.
 
Old 10-08-2019, 06:50 PM   #3
tramtrist
Member
 
Registered: Jul 2018
Location: Cincinnati USA
Distribution: Slackware
Posts: 129

Rep: Reputation: 77
D620 was one of my favorite laptops of all time. I had about half a dozen over the years.
Beware the NVIDIA card versions as they always went bad eventually after use. You can put the board in the oven to fix it for a while (seriously). Intel video was the way to go.

Definitely test the memory first..
 
Old 10-09-2019, 05:46 PM   #4
Twigster
LQ Newbie
 
Registered: Oct 2019
Location: France
Distribution: Slackware64 14.2
Posts: 11

Original Poster
Rep: Reputation: Disabled
Hello,

I forgot to mention that I used it with Windows XP the last three years, with the same memory and ssd and without issues. Nonetheless i just spent an hour running memtest86+ and badblocks from a live usb. Therefore that leads me to believe that the problem is software related.

Also this laptop has a intel video chip (and i didnt install any driver package on top of the slackware installer)

And it does not heat up. In fact it sometimes hangs minutes after booting, but never did so when i was compiling slackbuilds.

Last edited by Twigster; 10-09-2019 at 05:47 PM.
 
Old 10-09-2019, 08:09 PM   #5
abga
Senior Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 1,201

Rep: Reputation: 634Reputation: 634Reputation: 634Reputation: 634Reputation: 634Reputation: 634
@Twigster

In the short log snippets from your original post I couldn't find anything wrong and that's why I suggested to check the RAM & cpu temp.
Your problem could be SW related and I'd focus on the kernel & BIOS for now.

There is one particular error in your kernel log:
Code:
Oct  8 11:03:08 lagann kernel: [    4.386690] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
That shouldn't cause the hangs/reboots and according to this thread can be resolved with a BIOS update:
https://bugs.launchpad.net/ubuntu/+s...ux/+bug/995456

There is a kernel bug, apparently unresolved, affecting a few (newer) CPU implementations:
https://bugzilla.kernel.org/show_bug.cgi?id=193011
Related to this I also found references on the net presenting issues with older kernels and older CPUs - like your Intel Core 2 Duos (I presume you have such a CPU in your old D620):
https://ubuntuforums.org/archive/ind...t-2086676.html

As a workaround/possible solution - try adding the following kernel boot parameter in your boot loader configuration - kernel append line:
Code:
processor.max_cstate=1
Some other hints, try disabling the Power Management and also the Pulg&Play from the BIOS.

The entire kernel boot log (dmesg) together with the output of lspci could help the investigation further.
Please use https://pastebin.com/ for the kernel log and try to edit out serial numbers and MAC addresses for privacy reasons.

Last edited by abga; 10-09-2019 at 08:13 PM. Reason: typo
 
Old 10-10-2019, 08:18 AM   #6
Twigster
LQ Newbie
 
Registered: Oct 2019
Location: France
Distribution: Slackware64 14.2
Posts: 11

Original Poster
Rep: Reputation: Disabled
Alright sorry about the poor copy paste blocks.

i booted again on systemrescuecd because i needed to use gparted, and managed to make the computer hang twice in a row when starting gparted. It could be something wrong with some of my hardware, although I'm puzzled by badblocks not picking anything. Maybe it's not suited to testing SSD drives?

here is some smartctl data : patebin, I'm not sure why I do not get a SMART Error log there. But I guess it means the disk is faulty?

my CPU is a core 2 T5500 : pastebin
here is dmesg when doing a fresh boot: pastebin
lspci : pastebin

I now have the following append line in lilo.conf :
Code:
append=" vt.default_utf8=0 processor.max_cstate=1"
I couldnt understand much from the bug report threads you posted, apart from that they are related to much older kernels than 4.4.190.

Last edited by Twigster; 10-10-2019 at 08:51 AM. Reason: added requested informations
 
Old 10-10-2019, 11:13 AM   #7
svim
LQ Newbie
 
Registered: Feb 2015
Distribution: Slackware 14.2-64bit
Posts: 24

Rep: Reputation: Disabled
I have a mostly-retired Latitude D630 that still gets used on occasion (running 14.2 32-bit though). You referred to issues that might be tied to the SSD, have you gone through your BIOS settings to be in accordance with that? If there's a SATA option in the BIOS and there's a AHCI or ATA selection, is AHCI the chosen one? (on mine, the default was ATA but back when I added a SSD that setting needed to be changed to AHCI)
 
Old 10-10-2019, 12:16 PM   #8
abga
Senior Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 1,201

Rep: Reputation: 634Reputation: 634Reputation: 634Reputation: 634Reputation: 634Reputation: 634
Quote:
Originally Posted by Twigster View Post
Alright sorry about the poor copy paste blocks.

i booted again on systemrescuecd because i needed to use gparted, and managed to make the computer hang twice in a row when starting gparted. It could be something wrong with some of my hardware, although I'm puzzled by badblocks not picking anything. Maybe it's not suited to testing SSD drives?

here is some smartctl data : patebin, I'm not sure why I do not get a SMART Error log there. But I guess it means the disk is faulty?

my CPU is a core 2 T5500 : pastebin
here is dmesg when doing a fresh boot: pastebin
lspci : pastebin

I now have the following append line in lilo.conf :
Code:
append=" vt.default_utf8=0 processor.max_cstate=1"
I couldnt understand much from the bug report threads you posted, apart from that they are related to much older kernels than 4.4.190.
Thanks for providing all the info. I couldn't spot anything wrong in these outputs and on your harddrive (SSD), usually if something is going wrong with it, you'll get some errors in the kernel log (not a rule). Try following svim's suggestion and check/set your harddrive controller to work in AHCI mode - it should be already in that mode, if not available it might come with a BIOS update - see next paragraph.

According to your dmesg log, you run an old BIOS:
Code:
Dell Inc. Latitude D620                   /0FT292, BIOS A08 04/03/2007
Maybe it's the one that was available when the system was sold and nobody updated it ever since.
There is a new BIOS available for you machine and I'd strongly suggest to update it. BIOS updates are meant to improve the system functionality/stability.
Support page for your system:
https://www.dell.com/support/home/us...e-d620/drivers
The new BIOS update - Dell Latitude D620 System BIOS, A10 - Released 19 May 2008
https://www.dell.com/support/home/us...=latitude-d620
And a short HowTo to update it if you cannot load a Windows on that system for the BIOS update procedure:
https://www.dell.com/support/article...nments?lang=en

The kernel bug report, as mentioned already, covers newer CPUs and a wide range of kernels. The other link, specific for your CPU (Core 2) was indeed focusing on an older kernel than 4.4.190, mentioned that too. It was just a speculation and a suggestion on my side, considering that this known issue with the C-States might be the cause for your system becoming unstable.
A short presentation on C-States (use google to learn more):
https://gist.github.com/wmealing/2dd2b543c4d3cff6cab7

From your last post learned that you've found a way to reproduce the problem by launching gparted, however, I couldn't understand if the processor.max_cstate=1 was already enabled before that. So, I don't know if processor.max_cstate=1 was effective or not.
I'd suggest to remove processor.max_cstate=1 for the moment, proceed with the BIOS update, set your HDD controller on AHCI and observe how the system behaves. If and only if the system still hangs/reboots, try processor.max_cstate=1 again.


P.S. You should also check if the SSD is properly inserted & fixed in the HardDrive slot. Connections problems might cause a lot of weird things to happen.

Last edited by abga; 10-10-2019 at 12:43 PM. Reason: P.S.
 
Old 10-10-2019, 05:40 PM   #9
Twigster
LQ Newbie
 
Registered: Oct 2019
Location: France
Distribution: Slackware64 14.2
Posts: 11

Original Poster
Rep: Reputation: Disabled
Unhappy

Unfortunately, I did not find any AHCI option in the BIOS. The only SATA-related thing is Device-Initiated Power Management, which is set to enabled.
abga, when it comes to CPU power management, the only thing that's there is Intel Speedstep, which is also set to enabled.

Computer still froze with both options disabled, and BIOS flashed to the latest version(thanks for the links) + processor_max_cstate=1


Here is dmesg now

Also you can ditch my observation about gparted freezing the computer, turns out it was an outlier that i have not been able to reproduce 100% of the time, unfortunately.

It could be something wrong with my disk and I'll physically reinstall it tomorrow and check the contacts. I happen to have a spare lying around, is there an easy way to mirror my current installation to the other disk without running the slackware installer, the multilib set up and all my installed slackbuilds?

Last edited by Twigster; 10-10-2019 at 05:51 PM.
 
Old 10-10-2019, 06:37 PM   #10
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,435

Rep: Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446
Check the BIOS again, usually in Advanced Tab under Storage. There will be a listing to operate your hard drive controller(s) with either ATA or SATA-AHCI compatibility or 1) Your SSD wouldn't work at all and 2) XP would have been unlikely to work.

There are only two ways to get AHCI-SATA support in XP (1) boot on an ATA system and install chipset specific drivers fro SATA-AHCI support, or (2) slipstream the appropriate drivers into the install media or use the F6-Floppy "install additional drivers" function. To my knowledge no XP version including Service Packs ever included SATA-AHCI drivers. So your BIOS, assuming you never reset it, is almost certainly set to "ATA". That will also almost certainly be "hinky" with an SSD.
 
Old 10-10-2019, 06:45 PM   #11
abga
Senior Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 1,201

Rep: Reputation: 634Reputation: 634Reputation: 634Reputation: 634Reputation: 634Reputation: 634
Quote:
Originally Posted by Twigster View Post
It could be something wrong with my disk and I'll physically reinstall it tomorrow and check the contacts. I happen to have a spare lying around, is there an easy way to mirror my current installation to the other disk without running the slackware installer, the multilib set up and all my installed slackbuilds?
Sorry to hear that none of the suggested fixes worked. I hoped that the BIOS update would sort things out ... but apparently it's not the case. Your actual dmesg after the BIOS update looks OK too.
Intel Speedstep shouldn't cause anything bad, leave it activated, but the other option for your HDD - "Device-Initiated Power Management" try disabling it.

I don't know about any method to clone a live system but only use an external tool like Clonezilla / Acronis (commercial & really good) to make a whole HDD image.
https://clonezilla.org/
https://www.acronis.com/en-us/homeco...ue-image-2020/
"Try it free for 30 days!"
 
Old 10-10-2019, 07:06 PM   #12
abga
Senior Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 1,201

Rep: Reputation: 634Reputation: 634Reputation: 634Reputation: 634Reputation: 634Reputation: 634
@Twigster (& @enorbet)

It doesn't seem you can change the SATA mode on the D620 (only on the D630):
https://www.dell.com/community/Lapto...0/td-p/2413185
If you replace the SSD with an older spinner and the system becomes stable, stick with that old HDD then, use the SSD as an external drive in an USB enclosure or for another system/project.

I looked over the net to get some BIOS setup screenshots, found none useful, then I went for the official DELL documentation, again nothing related to BIOS setup. There is a service manual available, useful for disassembly...
https://www.dell.com/support/home/us...tude-d620/docs

Last edited by abga; 10-10-2019 at 07:33 PM. Reason: typo - enorbet - and I always believed it's "e norbeRt" + extra typo (I'm tired...)
 
Old 10-10-2019, 07:08 PM   #13
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,435

Rep: Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446
Quote:
Originally Posted by Twigster View Post
It could be something wrong with my disk and I'll physically reinstall it tomorrow and check the contacts. I happen to have a spare lying around, is there an easy way to mirror my current installation to the other disk without running the slackware installer, the multilib set up and all my installed slackbuilds?
Please see my previous post regarding your BIOS storage options. I also do recommend a BIOS update if you haven't done that already. I know that's scary for some but if you read the manufacturer's instructions there are very few steps and it is quite foolproof as well as seriously beneficial.

Regarding cloning, I would download and burn Clonezilla. DD can also do the job but the learning curve for anyone who needed to ask if it is even possible is substantial for "dd" and very short and easy for Clonezilla, plus it is effected from a live boot, from outside the system you would be cloning, always a better option. It is possible to simply tar your system to a backup file but that would require more steps to make it bootable. Clonezilla clones bit for bit for every sector including MBR and if your system is instead UEFI that is covered, too. Bottom Line - Clonezilla can copy and create an exact, fully functional twin.
 
Old 10-11-2019, 08:23 AM   #14
Twigster
LQ Newbie
 
Registered: Oct 2019
Location: France
Distribution: Slackware64 14.2
Posts: 11

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by abga View Post
Sorry to hear that none of the suggested fixes worked. I hoped that the BIOS update would sort things out ... but apparently it's not the case. Your actual dmesg after the BIOS update looks OK too.
Hello, it turns out I did not manage to change the cstate :
Code:
cat /sys/module/intel_idle/parameters/max_cstate 
9
where
Code:
/etc/lilo.conf
has the following line :
Code:
#cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0 processor.max_cstate=1"
What I did was update the file then run lilo :
Code:
#lilo
Added Linux  *
and then rebooted the machine.
Unfortunately I do not own any 2.5" HDD and only have a spare SSD. Would
Code:
dd if=/dev/<old disk> of=/dev/<new disk> conv=sync,noerror status=progress
do the trick? (newer drive larger than old drive)

Quote:
Originally Posted by enorbet View Post
Check the BIOS again, usually in Advanced Tab under Storage. There will be a listing to operate your hard drive controller(s) with either ATA or SATA-AHCI compatibility or 1) Your SSD wouldn't work at all and 2) XP would have been unlikely to work.

There are only two ways to get AHCI-SATA support in XP (1) boot on an ATA system and install chipset specific drivers fro SATA-AHCI support, or (2) slipstream the appropriate drivers into the install media or use the F6-Floppy "install additional drivers" function. To my knowledge no XP version including Service Packs ever included SATA-AHCI drivers. So your BIOS, assuming you never reset it, is almost certainly set to "ATA". That will also almost certainly be "hinky" with an SSD.
Apparently the motherboard in the D620 does not support AHCI

Last edited by Twigster; 10-11-2019 at 08:34 AM.
 
Old 10-11-2019, 11:05 PM   #15
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,435

Rep: Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446Reputation: 2446
Odds are that's the problem with only 2 possible solutions - Replace either the laptop or the drive. You could check the SSD stats to see if the manufacturer claims it is stable under ATA but it is unlikely.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Problems with HP 3500c scanner and Dell D620 laptop runing Ubuntu 9.10 wa3fkg Linux - Laptop and Netbook 1 12-03-2009 09:37 AM
SuSE on Dell D620 laptop cvzyl SUSE / openSUSE 4 04-08-2008 06:53 AM
FC5 and Laptop Dell Latitude D620 zillah Linux - General 3 11-06-2006 11:51 PM
Dell d620 graphics support bagpussnz Linux - Laptop and Netbook 2 05-10-2006 03:04 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:23 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration