Bug 6595 - alpha cpu: irq 22: nobody cared (try booting with the "irqpoll" option)
Summary: alpha cpu: irq 22: nobody cared (try booting with the "irqpoll" option)
Status: CLOSED CODE_FIX
Alias: None
Product: Timers
Classification: Unclassified
Component: Other (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: john stultz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-22 05:14 UTC by Thomas Steudten
Modified: 2006-08-25 08:46 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.17-rc2
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Thomas Steudten 2006-05-22 05:14:28 UTC
Most recent kernel where this bug did not occur:
Distribution: self
Hardware Environment: alpha board sx164
Software Environment:
Problem Description:
kernel: irq 22: nobody cared (try booting with the "irqpoll" option)
kernel: fffffc001b5eb9f8 0000000000000000 fffffc0000350ea4 fffffc000069c5c0 
kernel:        fffffc000069c5c0 fffffc000069e610 0000000000000000 0000000000000000 
kernel:        fffffc0000350608 fffffc000069c5c0 0000000000000016 fffffc000069e610 
kernel:        fffffc001b5ebb28 fffffc0000736150 fffffc00006a2020 fffffc8900000001 
kernel:        0000000def9e738c 1a00000000000000 fffffc0000350594 fffffc000069c5c0 
kernel:        0000000000000016 fffffc000069e610 fffffc001b5ebb28 fffffc0000736150 
kernel: Trace:
kernel: [<fffffc0000350ea4>] note_interrupt+0x114/0x360
kernel: [<fffffc0000350608>] __do_IRQ+0x128/0x140
kernel: [<fffffc0000350594>] __do_IRQ+0xb4/0x140
kernel: [<fffffc0000316120>] handle_irq+0x60/0xd0
kernel: [<fffffc000031f008>] pyxis_device_interrupt+0x118/0x130
kernel: [<fffffc00003164c8>] do_entInt+0x118/0x190
kernel: [<fffffc00003112b0>] ret_from_sys_call+0x0/0x10
kernel: [<fffffc0000350594>] __do_IRQ+0xb4/0x140
kernel: [<fffffc000031f060>] i8259a_mask_and_ack_irq+0x0/0xa0
kernel: [<fffffc0000350418>] handle_IRQ_event+0x48/0x110
kernel: [<fffffc0000350594>] __do_IRQ+0xb4/0x140
kernel: [<fffffc0000316120>] handle_irq+0x60/0xd0
kernel: [<fffffc000031f048>] isa_device_interrupt+0x28/0x40
kernel: [<fffffc000031ef58>] pyxis_device_interrupt+0x68/0x130
kernel: [<fffffc00003164c8>] do_entInt+0x118/0x190
kernel: [<fffffc00003112b0>] ret_from_sys_call+0x0/0x10
kernel: [<fffffc0000457fe0>] udelay+0x0/0x40
kernel: [<fffffc0000457fcc>] __delay+0xc/0x20
kernel: [<fffffc000037d71c>] vfs_write+0x10c/0x200
kernel: [<fffffc000037d958>] sys_write+0x68/0xc0
kernel: [<fffffc0000311294>] entSys+0xa4/0xc0
kernel: 
kernel: handlers:
kernel: [<fffffc00003503c0>] (no_action+0x0/0x10)
kernel: Disabling IRQ #22


Steps to reproduce: don't know. this comes randomly.
The system must be rebooted to be accessable again.
cat /proc/interrupts:
  1:         29          XT-PIC   i8042
  2:          0          XT-PIC   cascade
  3:         13          XT-PIC   serial
  4:       2629          XT-PIC   serial
  5:      47373          XT-PIC   NE2000
  7:   10523508          XT-PIC   parport0
  8:     831086             RTC  +timer
 12:        138          XT-PIC   i8042
 14:         22          XT-PIC  +ide0
 22:      18935           PYXIS   timer-cascade
 23:          0           PYXIS   isa-cascade
 24:     278651           PYXIS   eth0
 26:         15           PYXIS   aic7xxx
 27:      55800           PYXIS   aic7xxx
Comment 1 Thomas Steudten 2006-08-25 08:46:52 UTC
looks like this is fixed.. - 2.6.17.7 works for me on alpha.

Note You need to log in before you can comment on or make changes to this bug.