some sort of PCI interrupt problem after loading 5.4beta

snejt · **Joined:** Wed Feb 28, 2007 9:43 am **Posts:** 7

ok better start with a bit of history: !8!

Been using Zenwalk for a couple of years and have found it really EXCELLENT - so excellent I;ve even got a bit lazy and maybe haven't been doing as much 'skills honing' as I should. My last properly working version was 4.8 but just before the end of last year I messed it up with trying to load too much video-viewing software from the repo for my 10-year-old system (dual-booted with WIndows me):

X86 AMD Athlon ~1009Mhz;
BIOS version Award Medallion v.6.0;
256Mb RAM;
80Gb HD dual-booted with Windows me (zenwalk spread over 3 partitions totalling 40Gb);
GIGABYTE GA GF/280(GeForce2 MX) graphics
Creative SB Live
Realtek RTL8139(A)-based PCI Ethernet Adaptor

... then backtracking and deleting half of it until it froze completely and I was beyond the point of no return, so I saw 5.4(beta) was on offer and thought I'd give that a go. I seemed to work ok whilst I was logged in as root, but whenever I went into simple user modeand tried to do anything involving any kind of processor load (like trying to start firefox) it would sort of half-freeze with xfce icons disappearing off the screen whenever I clicked and a message

Code:

 Message from syslogd@name at Fri Jan 23 11.42.44 2009 ... (none) Kernel DIsabling IRQ#10 

appearing in the root terminal, after which nothing would be possible including exit.ing .

ok so I looked at the log files and in DMESG found the following

Code:

weird, boot CPU(#0) not listed by the BIOS

and..

Code:

 ACPI: I/O resource vt596_smbus [0xe800-0xe807] conflicts with ACPI region SM00 [0xe800-0xe806] 

and in MESSAGES i found...

Code:

 Jan 26 10:57:17 (none) kernel: xfce4-mixer-plu[2650]: segfault at dfc ip b726cfcc sp bfb26ce8 error 4 in libc-2.7.so[b71fe000+145000] 

and...

Code:

 Jan 29 10:03:49 (none) kernel: xfce4-settings-[1704]: segfault at 4 ip b7475eea sp bff05790 error 4 in libSM.so.6.0.0[b7474000+7000] 

So I saw this might be some sort of xfce problem and decide to download the Zenwalk-gnome-5.4beta. ISO and try that. Sure enough the same problems quickly returned (when I go from root to ordinary user mode), this tiime in MESSAGES I get:

Code:

 Jan 30 20:16:15 (none) kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
Jan 30 20:16:15 (none) kernel: pci 0000:00:04.4: quirk: region e400-e4ff claimed by vt82c586 ACPI
Jan 30 20:16:15 (none) kernel: pci 0000:00:04.4: quirk: region e200-e27f claimed by vt82c686 HW-mon
Jan 30 20:16:15 (none) kernel: pci 0000:00:04.4: quirk: region e800-e80f claimed by vt82c686 SMB 

and...

Code:

 Jan 30 20:16:15 (none) kernel: PCI: Using ACPI for IRQ routing
Jan 30 20:16:15 (none) kernel: system 00:00: iomem range 0x0-0x9ffff could not be reserved
Jan 30 20:16:15 (none) kernel: system 00:00: iomem range 0xf0000-0xfffff could not be reserved
Jan 30 20:16:15 (none) kernel: system 00:00: iomem range 0x100000-0xfffffff could not be reserved
Jan 30 20:16:15 (none) kernel: system 00:00: iomem range 0xfffe0000-0xffffffff could not be reserved
Jan 30 20:16:15 (none) kernel: system 00:02: ioport range 0x3f0-0x3f1 has been reserved
Jan 30 20:16:15 (none) kernel: system 00:02: ioport range 0x4d0-0x4d1 has been reserved
Jan 30 20:16:15 (none) kernel: system 00:03: ioport range 0xe800-0xe80f has been reserved
Jan 30 20:16:15 (none) kernel: pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
Jan 30 20:16:15 (none) kernel: pci 0000:00:01.0:   IO window: disabled 

in short I'm in it a bit beyond my depth, but it seems I've got some interrupt routing problem connect with i/o and the PCI card (IRQ10 in particular). output of lspci -v is:

Code:

 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 02)
   Subsystem: ASUSTeK Computer Inc. A7V Mainboard
   Flags: bus master, medium devsel, latency 0
   Memory at e4000000 (32-bit, prefetchable) [size=64M]
   Capabilities: [a0] AGP version 2.0
   Capabilities: [c0] Power Management version 2
   Kernel driver in use: agpgart-via
   Kernel modules: via-agp

00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (prog-if 00 [Normal decode])
   Flags: bus master, 66MHz, medium devsel, latency 0
   Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
   Memory behind bridge: d6000000-d7dfffff
   Prefetchable memory behind bridge: d7f00000-e3ffffff
   Capabilities: [80] Power Management version 2

00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
   Subsystem: ASUSTeK Computer Inc. A7V Mainboard
   Flags: bus master, stepping, medium devsel, latency 0
   Kernel driver in use: parport_pc
   Kernel modules: parport_pc

00:04.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10) (prog-if 8a [Master SecP PriP])
   Flags: bus master, medium devsel, latency 32
   [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
   [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
   [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
   [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
   I/O ports at d800 [size=16]
   Capabilities: [c0] Power Management version 2
   Kernel driver in use: pata_via

00:04.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10) (prog-if 00 [UHCI])
   Subsystem: First International Computer, Inc. VA-502 Mainboard
   Flags: bus master, medium devsel, latency 32, IRQ 9
   I/O ports at d400 [size=32]
   Capabilities: [80] Power Management version 2
   Kernel driver in use: uhci_hcd
   Kernel modules: uhci-hcd

00:04.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10) (prog-if 00 [UHCI])
   Subsystem: First International Computer, Inc. VA-502 Mainboard
   Flags: bus master, medium devsel, latency 32, IRQ 9
   I/O ports at d000 [size=32]
   Capabilities: [80] Power Management version 2
   Kernel driver in use: uhci_hcd
   Kernel modules: uhci-hcd

00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
   Subsystem: ASUSTeK Computer Inc. A7V Mainboard
   Flags: medium devsel, IRQ 9
   Capabilities: [68] Power Management version 2
   Kernel modules: via686a, i2c-viapro

00:09.0 Communication controller: Conexant Systems, Inc. HCF V90 56k Data/Fax/Voice/Spkp PCI Modem (rev 08)
   Subsystem: Conexant Systems, Inc. HCF V90 56k Data/Fax/Voice/Spkp PCI Modem
   Flags: bus master, medium devsel, latency 32, IRQ 255
   Memory at d5800000 (32-bit, non-prefetchable) [disabled] [size=64K]
   I/O ports at a400 [disabled] [size=8]
   Capabilities: [40] Power Management version 2

00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
   Subsystem: Creative Labs CT4830 SBLive! Value
   Flags: bus master, medium devsel, latency 32, IRQ 11
   I/O ports at a000 [size=32]
   Capabilities: [dc] Power Management version 1
   Kernel driver in use: EMU10K1_Audigy
   Kernel modules: snd-emu10k1

00:0a.1 Input device controller: Creative Labs SB Live! Game Port (rev 07)
   Subsystem: Creative Labs Gameport Joystick
   Flags: bus master, medium devsel, latency 32
   I/O ports at 9800 [size=8]
   Capabilities: [dc] Power Management version 1
   Kernel driver in use: Emu10k1_gameport
   Kernel modules: emu10k1-gp

00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
   Subsystem: Belkin F5D5000 PCI Card/Desktop Network PCI Card
   Flags: bus master, medium devsel, latency 32, IRQ 10
   I/O ports at 9400 [size=256]
   Memory at d5000000 (32-bit, non-prefetchable) [size=256]
   Capabilities: [50] Power Management version 2
   Kernel driver in use: 8139too
   Kernel modules: 8139cp, 8139too

00:11.0 Mass storage controller: Promise Technology, Inc. PDC20265 (FastTrak100 Lite/Ultra100) (rev 02)
   Subsystem: Promise Technology, Inc. Ultra100
   Flags: bus master, medium devsel, latency 32, IRQ 10
   I/O ports at 9000 [size=8]
   I/O ports at 8800 [size=4]
   I/O ports at 8400 [size=8]
   I/O ports at 8000 [size=4]
   I/O ports at 7800 [size=64]
   Memory at d4800000 (32-bit, non-prefetchable) [size=128K]
   [virtual] Expansion ROM at 20000000 [disabled] [size=64K]
   Capabilities: [58] Power Management version 1
   Kernel driver in use: pata_pdc202xx_old

01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1) (prog-if 00 [VGA controller])
   Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
   Memory at d6000000 (32-bit, non-prefetchable) [size=16M]
   Memory at d8000000 (32-bit, prefetchable) [size=128M]
   Expansion ROM at d7ff0000 [disabled] [size=64K]
   Capabilities: [60] Power Management version 2
   Capabilities: [44] AGP version 2.0
   Kernel modules: nvidiafb, rivafb 

output from lsmod is:

Code:

 Module                  Size  Used by
pcmcia                 19828  0 
pcmcia_core            17300  1 pcmcia
iptable_mangle          1408  0 
iptable_nat             2568  0 
nf_nat                  8728  1 iptable_nat
nf_conntrack_ipv4       6284  3 iptable_nat,nf_nat
nf_conntrack           27216  3 iptable_nat,nf_nat,nf_conntrack_ipv4
iptable_filter          1280  0 
ip_tables               6544  3 iptable_mangle,iptable_nat,iptable_filter
x_tables                6148  2 iptable_nat,ip_tables
video                  11024  0 
output                  1280  1 video
fuse                   30876  2 
fan                     2048  0 
battery                 6532  0 
ac                      2308  0 
i2c_viapro              4628  0 
i2c_core               10388  1 i2c_viapro
usb_storage            53256  0 
snd_emu10k1            92164  1 
snd_rawmidi            10496  1 snd_emu10k1
snd_ac97_codec         65312  1 snd_emu10k1
ac97_bus                1024  1 snd_ac97_codec
snd_pcm                34436  2 snd_emu10k1,snd_ac97_codec
snd_seq_device          3340  2 snd_emu10k1,snd_rawmidi
snd_timer              11016  2 snd_emu10k1,snd_pcm
snd_page_alloc          3976  2 snd_emu10k1,snd_pcm
snd_util_mem            1536  1 snd_emu10k1
snd_hwdep               3588  1 snd_emu10k1
8139too                14212  0 
emu10k1_gp              1664  0 
snd                    26168  9 snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm,snd_seq_device,snd_timer,snd_hwdep
mii                     2816  1 8139too
gameport                5004  2 emu10k1_gp
via686a                 7180  0 
soundcore               3016  1 snd
hwmon                   1308  1 via686a
uhci_hcd               13836  0 
thermal                 9884  0 
parport_pc             22716  0 
parport                19412  1 parport_pc
via_agp                 4480  1 
button                  3600  0 
processor              22316  2 thermal
agpgart                16052  1 via_agp
sg                     16948  0 
evdev                   5252  3 

I've been wading around in this for a couple of weeks and have clearly got a bit beyond my depth. I even tried going back to good ol' zenwallk 4.8 but even a spanking new installation of that crashes now. Could loading the 5.4 have permanently rerouted the interrupts somehow? I seem to remember reading something about that somewhere on one of the forums. I've got copies of the full DMESG and MESSAGES logs. Needless to say, if anbodies got any suggestion on what I might do to get a working system back they really would be most welcome!

Borromini · **Posted:** Sat Jan 31, 2009 11:57 am

Boy that is one exhaustive start post

.

Code:

weird, boot CPU(#0) not listed by the BIOS

Looks very interesting, I'm googling it, can't find anything for the moment.

Code:

 ACPI: I/O resource vt596_smbus [0xe800-0xe807] conflicts with ACPI region SM00 [0xe800-0xe806] 

Looking into that too.

Code:

 Jan 26 10:57:17 (none) kernel: xfce4-mixer-plu[2650]: segfault at dfc ip b726cfcc sp bfb26ce8 error 4 in libc-2.7.so[b71fe000+145000] 

Code:

 Jan 29 10:03:49 (none) kernel: xfce4-settings-[1704]: segfault at 4 ip b7475eea sp bff05790 error 4 in libSM.so.6.0.0[b7474000+7000] 

I wouldn't pay too much attention to those. It's an error message from glibc, it has nothing to do with your dmesg errors.

Try booting your kernel with the 'routeirq' parameter, and check dmesg output then. In addition, you might also want to disable ACPI support (a bit drastic, I know) with the 'noacpi' parameter. Try both (separately and at the same time) and compare dmesg output to see if they solve your problem.

Those are various options you could try, instead of the rather drastic noacpi, to get stuff back to working:

Code:

acpi=ht the most like "acpi=off", disables all of ACPI except what is needed to enumerate processors. If acpi=off works and acpi=ht fails, then the issue is in the ACPI table parsing code itself, or perhaps the SMP code.
pci=noacpi Disables ACPI for PCI root bus enumeration. Disables ACPI for IRQ routing.
acpi=noirq Disables ACPI for IRQ routing.
pnpacpi=off Disables the ACPI component of the Linux Plug and Play code.
noapic Disables the IO-APIC for IRQ routing.
nolapic Disables the Local-APIC and the IO-APIC.

snejt · **Joined:** Wed Feb 28, 2007 9:43 am **Posts:** 7

Thanks Borromini, your interest is very appreciated.

I'm trying the boot parameters you suggested, but so far with PCI=routeirq and PCI=noacpci I'm still getting the 'weird, boot CPU(#0) not listed by the BIOS' in DMESG and also the

Code:

 pci 0000:00:04.4: quirk: region e400-e4ff claimed by vt82c586 ACPI
pci 0000:00:04.4: quirk: region e200-e27f claimed by vt82c686 HW-mon
pci 0000:00:04.4: quirk: region e800-e80f claimed by vt82c686 SMB 

lines, tho its true I don't know if they fix the system yet as for I have to play around in user mode for a while. I'll also try some of the options listed at the bottom of your post ...

Borromini · **Posted:** Sat Jan 31, 2009 3:46 pm

All you need to do is append those options (without PCI=) your kernel's boot configuration line. At least, that's how it is for routeirq and noacpi. I don't know about the rest of gthem.

snejt · **Joined:** Wed Feb 28, 2007 9:43 am **Posts:** 7

Well booting with just the 'routeirq' parameter as root I seem to have a working system (no crashes as yet and I've tried almost everything) and that's basically all I need $:-\$

I gave 'noacpci', 'noapic', 'nolapic' and checked the dmesg logs (which still give the info shown in my first post.) - none of them seem to stop a crash pretty soon after I go into ordinary user mode, whether its my normal or a fictitious created for test.

I'm reckoning it must be something to do with my systerm spec which really is quite old. Its puzzling tho, why it works as root and not as a user as I don't know enough about Zenwalk/Linux internals to understand why.

.Whenever I log in as ordinary user the desktop takes an aeon to appear (if it appears at all) and the icons start sliding off the screen soon after. In fact its rather like when I tried Ubuntu with only 128MB RAM a couple of years back and quickly gave up. I'm wondering whether the Zenwalk GNOME version needs more RAM than the XFCE (I've got 256MB at the moment) and whether I should think about going back to the XFCE version. Would this involve a complete re-install (the only way I know) or is there a way I can change desktops 'on the fly'? Sorry I'm a newbie here.

Anyways, at least I've got a system which is more than I had before ..

Thks

some sort of PCI interrupt problem after loading 5.4beta

Who is online