Darrel Lawrence wrote:
Barry Gershenfeld wrote:
This sounds like a shared interrupt problem. The sound card and the
ethernet
card are either using the same interrupt or the same memory space.
This isn't
supposed to happen with PCI but it looks like it is in your case.
Regarding what Neil said...you can try cat/proc/iomem
The following are /proc/interrupts and /proc/iomem on the current
configuration. I am not sure what I am looking at with the iomem output.
/proc/iomem shows you a map of memory space. The addresses are the start
and stop boundaries of a block of memory used by a device to communicate
with the system. These blocks are fixed in place and the addresses are
absolute addresses. For example, see the BIOS > 000f0000-000fffff :
System ROM. This will be the same for every PC. Other parts may vary,
but the video BIOS (ROM) is usually the same also.
Darreln
[EMAIL PROTECTED]:~$ cat /proc/interrupts
CPU0 0: 445931 XT-PIC-XT timer
1: 1192 XT-PIC-XT i8042
2: 0 XT-PIC-XT cascade
5: 218993 XT-PIC-XT bttv0, Bt87x audio
6: 5 XT-PIC-XT floppy
7: 13191 XT-PIC-XT EMU10K1
8: 3 XT-PIC-XT rtc
9: 0 XT-PIC-XT acpi
10: 10225 XT-PIC-XT eth1
11: 0 XT-PIC-XT eth0
12: 82159 XT-PIC-XT i8042
14: 18499 XT-PIC-XT ide0
15: 15659 XT-PIC-XT ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0
This part looks good. You have a separate IRQ for both the ethernet
cards and the sound card. Leave the system as is for further testing.
The interrupt load for the video capture card (bttv0) is up a bit. I'm
guessing it does just frame capture and no hardware compression.
This must be an older motherboard because it doesn't have the APIC
(Advanced Programmable Interrupt Controller) interrupts.
[EMAIL PROTECTED]:~$ cat /proc/iomem
00000000-0009fbff : System RAM
00000000-00000000 : Crash kernel
0009fc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000cffff : Video ROM
000f0000-000fffff : System ROM
00100000-1ffeffff : System RAM
00100000-002f2373 : Kernel code
002f2374-003d36d3 : Kernel data
1fff0000-1fff2fff : ACPI Non-volatile Storage
1fff3000-1fffffff : ACPI Tables
30000000-3000ffff : 0000:00:0c.0
e0000000-e7ffffff : PCI Bus #01
e0000000-e7ffffff : 0000:01:00.0
e8000000-ebffffff : 0000:00:00.0
ec000000-edffffff : PCI Bus #01
ec000000-ecffffff : 0000:01:00.0
ed000000-ed00ffff : 0000:01:00.0
ef000000-ef000fff : 0000:00:09.1
ef000000-ef000fff : Bt87x audio
ef001000-ef001fff : 0000:00:0b.0
ef001000-ef001fff : orinoco_pci
ef002000-ef0020ff : 0000:00:0c.0
ef002000-ef0020ff : 8139too
ef003000-ef003fff : 0000:00:09.0
ef003000-ef003fff : bttv0
ffff0000-ffffffff : reserved
[EMAIL PROTECTED]:~$
This shows that the wireless PCI card is using the orinoco driver. What
is the output of lspci? You can use that to match with the /proc/iomem
map to see what device is using which part of the memory range.
Gus
--
KPLUG-Newbie@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
