|  |  | 
  
    |  |  | 
 
  |   |  | 
  
    |  |  | 
  
    |  |  | 
  
    |   xen-devel
Re: [Xen-devel] Re: Continuing problems booting 
| Jeremy Fitzhardinge wrote:
> static int
> __setup_irq(unsigned int irq, struct irq_desc *desc, struct irqaction *new)
> {
>     struct irqaction *old, **old_ptr;
>     const char *old_name = NULL;
>     unsigned long flags;
>     int shared = 0;
>     int ret;
> 
>     if (!desc)
>         return -EINVAL;
> 
>     if (desc->chip == &no_irq_chip)
>         return -ENOSYS;
> ...
I can try sprinkle in some printk's to figure ...
> which gets called from request_irq.  So that means that the desc is
> getting allocated but the chip hasn't been set up.  Are you using sparse
> irqs?
It's enabled, yes (config is derived from default fedora one ...)
>> The kernel initializes legacy interrupts anyway.  I think you don't need
>> to do more to handle apic-less machines, no?
> 
> I guess not, if its only using irqs < 16.  How old is this machine
> anyway; do you really mean its a literal i386?
Pentium III (~2001), /proc/interrupts on bare metal looks like this:
           CPU0
  0:     617526    XT-PIC-XT        timer
  1:        286    XT-PIC-XT        i8042
  2:          0    XT-PIC-XT        cascade
  3:          3    XT-PIC-XT
  4:          1    XT-PIC-XT
  5:          1    XT-PIC-XT        Intel 440MX Modem, Intel 440MX
  6:          1    XT-PIC-XT
  7:          1    XT-PIC-XT
  8:          1    XT-PIC-XT        rtc0
  9:          5    XT-PIC-XT        acpi
 10:         50    XT-PIC-XT        yenta, firewire_ohci
 11:      13186    XT-PIC-XT        uhci_hcd:usb1, eth0
 12:       6131    XT-PIC-XT        i8042
 14:      56351    XT-PIC-XT        ata_piix
 15:          0    XT-PIC-XT        ata_piix
NMI:          0   Non-maskable interrupts
LOC:          0   Local timer interrupts
RES:          0   Rescheduling interrupts
CAL:          0   Function call interrupts
TLB:          0   TLB shootdowns
TRM:          0   Thermal event interrupts
SPU:          0   Spurious interrupts
ERR:          0
MIS:          0
> But the info I'm using to set up the legacy interrupts comes from acpi
> tables, I think, so perhaps its misprogramming the legacy interrupts,
> whereas before they just happened to work in their default config (???).
As the *registration* fails already I don't think it is misprogramming.
cheers,
  Gerd
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 | 
 
| <Prev in Thread] | Current Thread | [Next in Thread> |  | 
Re: [Xen-devel] Re: Continuing problems booting, Jeremy FitzhardingeRe: [Xen-devel] Re: Continuing problems booting, (continued)
Re: [Xen-devel] Re: Continuing problems booting, Jeremy Fitzhardinge
Re: [Xen-devel] Re: Continuing problems booting, Gerd Hoffmann
Re: [Xen-devel] Re: Continuing problems booting, Jeremy Fitzhardinge
Re: [Xen-devel] Re: Continuing problems booting,
Gerd Hoffmann <=
Re: [Xen-devel] Re: Continuing problems booting, Gerd Hoffmann
Re: [Xen-devel] Re: Continuing problems booting, Jeremy Fitzhardinge
Re: [Xen-devel] Re: Continuing problems booting, Gerd Hoffmann
Re: [Xen-devel] Re: Continuing problems booting, Jeremy Fitzhardinge
Re: [Xen-devel] Re: Continuing problems booting, Gerd Hoffmann
Re: [Xen-devel] Re: Continuing problems booting, Jeremy Fitzhardinge
Re: [Xen-devel] Re: Continuing problems booting, Gerd Hoffmann
Re: [Xen-devel] Re: Continuing problems booting, Pasi Kärkkäinen
 |  |  | 
  
    |  |  |