Linux mint boot error: "1.55 No irq handler for vector" sluggish system.

Amit15 · 08-19-2018, 02:47 PM

I installed Linux mint 19 xfce on hp pavilion g4-1303au notebook(Legacy Bios).
It was running fine for first few weeks after that sometimes when watching videos on youtube it would freeze(video gets stucked and audio repeats where it got freezed) and nothing would work not even the mouse cursor.
Sometimes after booting and before getting to login screen the screen would go blank screen and I had to restart again.
No on booting I get "No irq handler for vector" displayed for few seconds.

Code:

~$ inxi -Fxz
System:    Host: Notebook Kernel: 4.15.0-32-generic x86_64 bits: 64 gcc: 7.3.0
           Desktop: Xfce 4.12.3 (Gtk 2.24.31) Distro: Linux Mint 19 Tara
Machine:   Device: laptop System: Hewlett-Packard product: HP Pavilion g4 Notebook PC v: 0691130000204610000610100 serial: N/A
           Mobo: Hewlett-Packard model: 3564 v: 21.47 serial: N/A BIOS: Insyde v: F.6D date: 01/24/2014
Battery    BAT0: charge: 30.1 Wh 77.7% condition: 38.7/38.7 Wh (100%)
           model: Hewlett-Packard Primary status: Charging
CPU:       Dual core AMD A4-3330MX APU with Radeon HD Graphics (-MCP-) arch: Fusion rev.0 cache: 2048 KB
           flags: (lm nx sse sse2 sse3 sse4a svm) bmips: 8784
           clock speeds: max: 2200 MHz 1: 827 MHz 2: 926 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Sumo [Radeon HD 6480G] bus-ID: 00:01.0
           Display Server: x11 (X.Org 1.19.6 ) drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
           Resolution: 1366x768@60.00hz
           OpenGL: renderer: AMD SUMO (DRM 2.50.0 / 4.15.0-32-generic, LLVM 6.0.0)
           version: 3.3 Mesa 18.0.5 Direct Render: Yes
Audio:     Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller driver: snd_hda_intel bus-ID: 00:14.2
           Card-2 Advanced Micro Devices [AMD/ATI] BeaverCreek HDMI Audio [Radeon HD 6500D and 6400G-6600G series]
           driver: snd_hda_intel bus-ID: 00:01.1
           Sound: Advanced Linux Sound Architecture v: k4.15.0-32-generic
Network:   Card-1: Qualcomm Atheros AR9485 Wireless Network Adapter driver: ath9k bus-ID: 01:00.0
           IF: wlo1 state: up mac: <filter>
           Card-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
           driver: r8169 v: 2.3LK-NAPI port: 2000 bus-ID: 02:00.0
           IF: eno1 state: down mac: <filter>
           Card-3: Atheros usb-ID: 006-004
           IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Drives:    HDD Total Size: 1000.2GB (3.6% used)
           ID-1: /dev/sda model: HGST_HTS541010A9 size: 1000.2GB temp: 48C
Partition: ID-1: / size: 624G used: 34G (6%) fs: ext4 dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 57.0C mobo: N/A gpu: 60.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 174 Uptime: 2:27 Memory: 2155.3/7450.9MB Init: systemd runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191) inxi: 2.3.56

Logs:

Quote:

Aug 19 23:47:38 ntpdate: the NTP socket is in use, exiting
Aug 19 22:58:00 lightdm: PAM adding faulty module: pam_kwallet5.so
Aug 19 22:48:12 bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
Aug 19 22:48:10 pulseaudio: [pulseaudio] pid.c: Daemon already running.
Aug 19 22:48:10 pulseaudio: [pulseaudio] pid.c: Daemon already running.
Aug 19 22:48:10 pulseaudio: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
Aug 19 22:48:02 bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
Aug 19 22:48:01 kernel: usb 6-1: device not accepting address 3, error -62
Aug 19 22:48:01 lightdm: PAM adding faulty module: pam_kwallet5.so
Aug 19 22:47:57 ntpdate: the NTP socket is in use, exiting
Aug 19 22:47:56 lightdm: PAM adding faulty module: pam_kwallet5.so
Aug 19 22:47:55 ntpd: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
Aug 19 22:47:53 wpa_supplicant: dbus: Failed to construct signal
Aug 19 22:47:50 kernel: usb 6-1: device descriptor read/64, error -110
Aug 19 22:47:29 kernel: do_IRQ: 1.55 No irq handler for vector

business_kid · 08-19-2018, 03:05 PM

That's what - 6 years old?

try opening 2 terminals
1. In one, run 'sudo dmesg |less'
2. In the other, run 'cat >>error.txt <<eof

Take whatever looks interesting from dmesg (like what's throwing that error) and paste it into the other. Then type eof in the second terminbal, and errors.txt will be saved to your homedir. Post it, we can have a look, snigger or make suggestions :-)). At least we'll know more.

Amit15 · 08-19-2018, 03:35 PM

Quote:

Originally Posted by business_kid

That's what - 6 years old?

The laptop? Yeah.

Quote:

try opening 2 terminals
1. In one, run 'sudo dmesg |less'
2. In the other, run 'cat >>error.txt <<eof

Take whatever looks interesting from dmesg (like what's throwing that error) and paste it into the other. Then type eof in the second terminbal, and errors.txt will be saved to your homedir. Post it, we can have a look, snigger or make suggestions :-)). At least we'll know more.

Hmm, I took all which had irq in it and something which showed warnings.
And I forgot to mention above sometimes even some webpages get stuck like scrolling or anything else doesn't work but if I switch tab the web which got stuck starts working. Same with youtube sometimes like only video gets stucked and audio goes on, it gets to normal if revert back from fullscreen.

Also I don't think heating is the issue for this freeze

Code:

~$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +54.5°C  (high = +70.0°C)
                       (crit = +115.0°C, hyst = +115.0°C)

acpitz-virtual-0
Adapter: Virtual device
temp1:        +59.0°C  

radeon-pci-0008
Adapter: PCI adapter
temp1:        +54.0°C  (crit = +120.0°C, hyst = +90.0°C)

business_kid · 08-20-2018, 06:39 AM

That caught some stuff all right.

It looks as if it's very unhappy with the Calgary chipset, the ACPI, and something in the video. This smells (to me) of generic drivers being loaded and your stuff being definitely non generic. Others will hopefully comment. If the generic driver is loaded, it hogs the system and others can't load.

In any system that wasn't going to overwrite your efforts, I'd start the (now awful) job of rolling my own kernel. You might manage some improvements with kernel boot options, blacklisting the vesa module, and any generic ones in use ('lsmod' to see them).

Amit15 · 08-20-2018, 08:42 AM

Quote:

Originally Posted by business_kid

That caught some stuff all right.

It looks as if it's very unhappy with the Calgary chipset, the ACPI, and something in the video. This smells (to me) of generic drivers being loaded and your stuff being definitely non generic. Others will hopefully comment. If the generic driver is loaded, it hogs the system and others can't load.

Could you explain me what does "This smells (to me) of generic drivers being loaded and your stuff being definitely non generic." means?

Quote:

In any system that wasn't going to overwrite your efforts, I'd start the (now awful) job of rolling my own kernel. You might manage some improvements with kernel boot options, blacklisting the vesa module, and any generic ones in use ('lsmod' to see them).

So, I need my own kernel specific to my device? Damn never done any stuff related to kernel writing. Could you give me some pointers where to get started.

business_kid · 08-20-2018, 09:59 AM

Quote:

Originally Posted by Amit15

Could you explain me what does "This smells (to me) of generic drivers being loaded and your stuff being definitely non generic." means?

I ran into this problem with a poorly supported motherboard chipset. Back then it was something like 'generic pci support' was loaded, and claimed the chipset. But the chipset didn't work properly with 'generic' support. I rolled a kernel with no generic pci support, and my actual chipset compiled in, not a module. It was the infamous Via MPV3 chipset. Well, everyone is allowed one of those.

I'm not going to try holding your hand through a kernel configuration because I'm not half up to date enough. Like when I went into hospital, the Meltdown / Spectre mess was breaking out. Out only recently, I haven't a clue about how it worked out. What was a simple enough kernel config menu is now very very long, and more complex. Help is behind development. Tomsrtbt (http://www.toms.net/rb) made a 1.82MB floppy with a kernel, and a busybox system on it. Now it's about 5 Megs per kernel at least. Even allowing the 32/64 thing, that's a 60% increase.

Go for the boot options or module blacklisting or aliasing. You may be able to solve things that way.

EDIT: I had a look at the tomsrtbt kernel. It's 811K. It's 2.0 or 2.2, very far back, but that would be 1.6M in 64bit, vs 5Megs today. It's the scale of things. I'm even having difficulty coming from 4.9.45 to 4.14.55.

Amit15 · 08-20-2018, 10:42 AM

Quote:

Originally Posted by business_kid

Go for the boot options or module blacklisting or aliasing. You may be able to solve things that way.

What do you mean by boot options?
And for module blacklisting or aliasing vesa how do I do it?

Code:

~$ ls /etc/modprobe.d/
alsa-base.conf                  blacklist-modem.conf
amd64-microcode-blacklist.conf  blacklist-oss.conf
blacklist-ath_pci.conf          blacklist-rare-network.conf
blacklist.conf                  dkms.conf
blacklist-firewire.conf         intel-microcode-blacklist.conf
blacklist-framebuffer.conf      iwlwifi.conf

and in which file do I put the blacklist code.