kernel: spurious 8259A interrupt: IRQ7

FreeBSD, Gentoo, openSUSE, CentOS, Ubuntu, Debian
Post Reply
blindfisch
Posts: 52
Joined: 2002-08-17 00:55
 

kernel: spurious 8259A interrupt: IRQ7

Post by blindfisch »

hallo,

ich habe folgende meldung in /var/log/messages stehen, danach ist der server abgesemmelt
Jan 17 18:20:10 server1 kernel: spurious 8259A interrupt: IRQ7.

was heisst diese melldung?
captaincrunch
Userprojekt
Userprojekt
Posts: 7066
Joined: 2002-10-09 14:30
Location: Dorsten
Contact:
 

Re: kernel: spurious 8259A interrupt: IRQ7

Post by captaincrunch »

Nach zwei Minuten googeln kam folgendes zum Vorschein :
A device with part number 8259A, which is a programmable interrrupt controller used with many devices to
interface with the system bus, has generated a unexpected Interrrupt. Asked for service without a real request.
ie. Noise.........

what lies around this line in the log file may give you a clue as to =
what device is actually generating the
interrrupt. If it only happens at boot time, it is possible that the =
device driver has a bug in it's
initialization routine that generates a spurious interrrupt to the OS. =
It should be reported appropriately.

If it happens all the time while the system is running, you have a bad =
hardware problem or something is
loose or improperly connected.
First ID the real source of the interrupt. The 8259A could be on many devices or it may be on the MB. (more than one present.)
(listman. redhat.com, aber auch massive Diskussionen auf der Kenrle-ML)

Wenn du mehr willst : http://www.google.de/search?q=%22spurio ... uche&meta=
Da wirst du dann zwar mal ein bisschen (selber) lesen müssen, aber das soll ja schließlich auch ein bisschen bilden ... :wink:
DebianHowTo
echo "[q]sa[ln0=aln256%Pln256/snlbx]sb729901041524823122snlbxq"|dc
blindfisch
Posts: 52
Joined: 2002-08-17 00:55
 

Re: kernel: spurious 8259A interrupt: IRQ7

Post by blindfisch »

ok, ich hab mir mal einige links reingezogen, da steht fast überall das dies unbedenklich ist


jedenfalls ist das die letzte meldung gewesen bevor der server sich einfach aufgehangen hat. ping etc. geht noch, laut portscan ist port 22, 80 etc. auch offen - nur einloggen oder dienste nutzen geht nicht
blindfisch
Posts: 52
Joined: 2002-08-17 00:55
 

Re: kernel: spurious 8259A interrupt: IRQ7

Post by blindfisch »

könnte evtl. das etwas damit zutun haben?


/var/log/warn
Jan 16 18:04:18 server1 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000044
Jan 16 18:04:18 server1 kernel: printing eip:
Jan 16 18:04:18 server1 kernel: c01ec5a7
Jan 16 18:04:18 server1 kernel: *pde = 00000000
Jan 16 18:04:18 server1 kernel: Oops: 0000
Jan 16 18:04:18 server1 kernel: CPU: 0
Jan 16 18:04:18 server1 kernel: EIP: 0010:[unregister_md_personality+75/96]
Jan 16 18:04:18 server1 kernel: EFLAGS: 00010202
Jan 16 18:04:18 server1 kernel: eax: 00000000 ebx: f0b600e0 ecx: 00000000 edx: 00000040
Jan 16 18:04:18 server1 kernel: esi: f0b600e0 edi: 00000000 ebp: f0b60118 esp: f7081ef4
Jan 16 18:04:18 server1 kernel: ds: 0018 es: 0018 ss: 0018
Jan 16 18:04:18 server1 kernel: Process sendmail (pid: 5880, stackpage=f7081000)
Jan 16 18:04:18 server1 kernel: Stack: f0b60134 c02051c8 f0b600e0 f0b600e0 f7576cb0 f7ffa1a0 f75e74a0 c02f4fe4
Jan 16 18:04:18 server1 kernel: f0b60114 00000296 c02f4fa0 c01ab6bd f7d5f060 00000296 c1feb5a0 f0b600e0
Jan 16 18:04:18 server1 kernel: f7576cb0 c021ad68 f0b600e0 00000000 f7576cb0 f7576b80 ea7e068c f7576cb0
Jan 16 18:04:18 server1 kernel: Call Trace: [ip_build_xmit_slow+844/1236] [ide_intr+209/272] [raw_rcv_skb+132/296] [ipv6:__insmod_ipv6_S.text_L97456+1580/1592] [autorun_devices+302/572]
Jan 16 18:04:18 server1 kernel: [get_disk_info+142/304] [fput+156/224] [sys_close+72/84] [generic_file_open+15/56] [system_call+51/64]
Jan 16 18:04:18 server1 kernel:
Jan 16 18:04:18 server1 kernel: Code: 8b 42 04 c1 e0 03 83 c0 08 29 43 78 ff 0a 0f 94 c0 84 c0 74
Jan 16 18:04:33 server1 kernel: <1>Unable to handle kernel NULL pointer dereference at virtual address 00000044
Jan 16 18:04:33 server1 kernel: printing eip:
Jan 16 18:04:33 server1 kernel: c01ec5a7
Jan 16 18:04:33 server1 kernel: Oops: 0000
Jan 16 18:04:33 server1 kernel: CPU: 0
Jan 16 18:04:33 server1 kernel: EIP: 0010:[unregister_md_personality+75/96]
Jan 16 18:04:33 server1 kernel: EFLAGS: 00010202
Jan 16 18:04:33 server1 kernel: eax: 00000000 ebx: ef49e040 ecx: ef49e040 edx: 00000040
Jan 16 18:04:33 server1 kernel: esi: f757b430 edi: f7ffa1a0 ebp: f75f22c0 esp: ea237f20
Jan 16 18:04:33 server1 kernel: ds: 0018 es: 0018 ss: 0018
Jan 16 18:04:33 server1 kernel: Process ifconfig (pid: 5901, stackpage=ea237000)
Jan 16 18:04:33 server1 kernel: Stack: ef49e040 c021a8a6 ef49e040 ef49e040 ea7ec9de ef49e040 c021ad68 ef49e040
Jan 16 18:04:33 server1 kernel: 00000000 f757b430 f757b300 ea7e068c f757b430 ef49e040 f757b430 c01ea37e
Jan 16 18:04:33 server1 kernel: f757b430 f757b300 c01ea85e f757b430 f6f9c3c0 c0132fe4 f757b300 f6f9c3c0
Jan 16 18:04:33 server1 kernel: Call Trace: [tcp_check_req+626/796] [ipv6:udpv6_connect+822/828] [raw_rcv_skb+132/296] [ipv6:__insmod_ipv6_S.text_L97456+1580/1592] [autorun_devices+302/572]
Jan 16 18:04:33 server1 kernel: [get_disk_info+142/304] [fput+156/224] [sys_close+72/84] [generic_file_open+15/56] [system_call+51/64]
Jan 16 18:04:33 server1 kernel:
Jan 16 18:04:33 server1 kernel: Code: 8b 42 04 c1 e0 03 83 c0 08 29 43 78 ff 0a 0f 94 c0 84 c0 74
Jan 16 18:04:45 server1 kernel: <1>Unable to handle kernel NULL pointer dereference at virtual address 00000044
Jan 16 18:04:45 server1 kernel: printing eip:
Jan 16 18:04:45 server1 kernel: c01ec5a7
Jan 16 18:04:45 server1 kernel: Oops: 0000
Jan 16 18:04:45 server1 kernel: CPU: 0
Jan 16 18:04:45 server1 kernel: EIP: 0010:[unregister_md_personality+75/96]
Jan 16 18:04:45 server1 kernel: EFLAGS: 00010202
Jan 16 18:04:45 server1 kernel: eax: 00000000 ebx: f7fe0aa0 ecx: f70eb000 edx: 00000040
Jan 16 18:04:45 server1 kernel: esi: f7fe0aa0 edi: 00000000 ebp: f7fe0ad8 esp: f41b3ef4
Jan 16 18:04:45 server1 kernel: ds: 0018 es: 0018 ss: 0018
Jan 16 18:04:45 server1 kernel: Process sshd (pid: 5301, stackpage=f41b3000)
Jan 16 18:04:45 server1 kernel: Stack: 0000000a c02051c8 f7fe0aa0 f7fe0aa0 f75269b0 f7ffa1a0 f7529540 f757e9f0
Jan 16 18:04:45 server1 kernel: f7fe0ad4 eb11a0c0 eb11a408 00000000 00000282 00000001 f75f7220 f7fe0aa0
Jan 16 18:04:45 server1 kernel: f75269b0 c021ad68 f7fe0aa0 000001f4 f75269b0 f7526880 ea7e068c f75269b0
Jan 16 18:04:45 server1 kernel: Call Trace: [ip_build_xmit_slow+844/1236] [raw_rcv_skb+132/296] [ipv6:__insmod_ipv6_S.text_L97456+1580/1592] [autorun_devices+302/572] [get_disk_info+142/304]
Jan 16 18:04:45 server1 kernel: [fput+156/224] [sys_close+72/84] [generic_file_open+15/56] [system_call+51/64]
Jan 16 18:04:45 server1 kernel:
Jan 16 18:04:45 server1 kernel: Code: 8b 42 04 c1 e0 03 83 c0 08 29 43 78 ff 0a 0f 94 c0 84 c0 74
Jan 16 18:04:45 server1 last message repeated 2 times
Jan 16 18:12:02 server1 kernel: spurious 8259A interrupt: IRQ7.
Jan 16 19:19:50 server1 sshd[713]: PAM pam_set_item: NULL pam handle passed
Jan 16 19:19:58 server1 sshd[713]: fatal: Read from socket failed: Connection reset by peer
Jan 16 19:19:54 server1 sshd[713]: PAM pam_set_item: NULL pam handle passed
Jan 16 20:54:05 server1 sshd[816]: fatal: Timeout before authentication for ::ffff:203.204.175.158.
Jan 16 22:33:21 server1 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000104
Jan 16 22:33:21 server1 kernel: printing eip:
Jan 16 22:33:21 server1 kernel: f799a6e1
Jan 16 22:33:21 server1 kernel: *pde = 00000000
Jan 17 06:32:50 server1 kernel: spurious 8259A interrupt: IRQ7.
captaincrunch
Userprojekt
Userprojekt
Posts: 7066
Joined: 2002-10-09 14:30
Location: Dorsten
Contact:
 

Re: kernel: spurious 8259A interrupt: IRQ7

Post by captaincrunch »

Das sieht schon eher nach dem Problem aus. Ist das dein Rootie ? Sieht nämlich schon irgendwie nach Hardwareproblemchen aus.
DebianHowTo
echo "[q]sa[ln0=aln256%Pln256/snlbx]sb729901041524823122snlbxq"|dc
blindfisch
Posts: 52
Joined: 2002-08-17 00:55
 

Re: kernel: spurious 8259A interrupt: IRQ7

Post by blindfisch »

ne, ist ne private kiste

den ram hab ich schon getauscht, trotzdem die gleichen fehler
Post Reply