kernel: spurious 8259A interrupt: IRQ7

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,
I have a toshiba laptop with a miniPCI EL-2511MP PLUS 802.11/b card in it.
I am running kernel 2.6.5-1.358 with all of the updates as of today.

I am a bit confused (understatement)

I just lost ethernet connectivity and had to power cycle the laptop.  I
was getting so many messages written to /var/log/messages that the system
was unresponsive.  I was using XMMS listening to radio station.

Messages start with:
May 11 10:10:31 mktg6nt kernel: spurious 8259A interrupt: IRQ7.
May 11 10:41:27 mktg6nt kernel: eth1: error -110 reading info frame. Frame
dropped.
May 11 10:41:27 mktg6nt kernel: eth1: Error -110 writing Tx descriptor to BAP
May 11 10:41:29 mktg6nt last message repeated 349 times
May 11 10:41:29 mktg6nt kernel: hermes @ MEM 0x21ea1000: Timeout waiting
for command completion.
May 11 10:41:29 mktg6nt kernel: hermes @ MEM 0x21ea1000: Error -16 issuing
command.
May 11 10:41:29 mktg6nt kernel: eth1: Error -110 writing Tx descriptor to BAP
May 11 10:41:30 mktg6nt last message repeated 63 times
May 11 10:41:30 mktg6nt kernel: eth1: Ereth1: Error -110 writing Tx
descriptor to BAP
May 11 10:41:30 mktg6nt kernel: eth1: Error -110 writing Tx descriptor to BAP
May 11 10:41:31 mktg6nt last message repeated 81 times
May 11 10:41:31 mktg6nt kernel: eth1: Error -110 writing Tx eth1: Error
-110 writing Tx descriptor to BAP
May 11 10:41:31 mktg6nt kernel: eth1: Error -110 writing Tx descriptor to BAP
May 11 10:41:31 mktg6nt last message repeated 81 times
May 11 10:41:31 mktg6nt kernel: eth1: Error -110 writing Tx eth1: Error
-110 writing Tx descriptor to BAP


What I am really confused about are the following output from dmesg.

eth0: Station identity 001f:0009:0001:0004
eth0: Looks like an Intersil firmware version 1.4.9
eth0: Ad-hoc demo mode supported
eth0: IEEE standard IBSS ad-hoc mode supported
eth0: WEP supported, 104-bit key
eth0: MAC address 00:02:6F:04:64:6A
eth0: Station name "Prism  I"
eth0: ready
8139too Fast Ethernet driver 0.9.27
divert: allocating divert_blk for eth1
eth1: RealTek RTL8139 at 0x3000, 00:02:3f:8f:19:0e, IRQ 10
eth1:  Identified 8139 chip type 'RTL-8100B/8139D'

BUT I have this from ifconfig:

mktg6nt: ifconfig -a
eth1      Link encap:Ethernet  HWaddr 00:02:6F:04:64:6A
          inet addr:192.9.200.42  Bcast:192.9.200.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4129 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1028 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:826960 (807.5 Kb)  TX bytes:177917 (173.7 Kb)
          Interrupt:11 Base address:0x8000 Memory:e0500000-e0500fff


and in my modprobe.conf:
alias eth0 8139too
alias eth1 orinoco_pci


I am writting this with my laptop, so it came back up clean.  I just do
not understand the differences in the eth0/eth1 being reversed in the
dmesg output from the ifconfig output.

Should I change the modprobe.conf to have the orinoco_pci aliased to eth0
and the builtin 8139too aliased to eth0?

What is the 8259A interupt?  It seems like the builtin sound card.

Thanks.
-- 
Brian Millett
Enterprise Consulting Group  "Shifts in paradigms
(314) 205-9030           often cause nose bleeds."
bpmATec-groupDOTcom                     Greg Glenn





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux