Re: [Bugme-new] [Bug 10455] New: Kernel lockup when iwl3945 modules is loaded after a few hours

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

 



On Tue, 15 Apr 2008 10:39:17 +0200 "Bart Van Assche" <bart.vanassche@xxxxxxxxx> wrote:

> On Tue, Apr 15, 2008 at 10:32 AM, Andrew Morton
> <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
> >
> >  > Latest working kernel version: (not known)
> >  > Earliest failing kernel version: 2.6.25-rc9
> >
> >  hm, why?  Has this machine never run earlier kernels?
> 
> 2.6.22-14 works fine on the same hardware. This is the kernel provided
> by Ubuntu.

OK, thanks, so it's a regression but we don't know if it's a post-2.6.25
regression.

> >  > Apr 14 21:06:00 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19
> >  > (level, low) -> IRQ 19
> >  > Apr 14 21:06:00 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0
> >  > disabled
> >
> >  Yes, that does look like an ACPI problem.  But one would expect it to kill
> >  the interface immediately, not several hours later.
> >
> >  Can you send the /proc/interrupts contents?
> 
> Here it is:
> 
>            CPU0       CPU1
>   0:     996478          0   IO-APIC-edge      timer
>   1:         30          0   IO-APIC-edge      i8042
>   8:          7          0   IO-APIC-edge      rtc
>   9:      57710          0   IO-APIC-fasteoi   acpi
>  12:        132          0   IO-APIC-edge      i8042
>  14:      31294      11519   IO-APIC-edge      ata_piix
>  15:      69158          0   IO-APIC-edge      ata_piix
>  16:      85016          0   IO-APIC-fasteoi   uhci_hcd:usb4,
> i915@pci:0000:00:02.0
>  18:      15921          0   IO-APIC-fasteoi   uhci_hcd:usb3
>  19:          0          0   IO-APIC-fasteoi   uhci_hcd:usb2
>  21:      79770      60509   IO-APIC-fasteoi   eth0
>  22:       5811          0   IO-APIC-fasteoi   HDA Intel
>  23:          3          0   IO-APIC-fasteoi   uhci_hcd:usb1, ehci_hcd:usb5
> NMI:          0          0   Non-maskable interrupts
> LOC:        509     996926   Local timer interrupts
> RES:      29774      84400   Rescheduling interrupts
> CAL:         62      28154   function call interrupts
> TLB:        868       1262   TLB shootdowns
> TRM:          0          0   Thermal event interrupts
> SPU:          0          0   Spurious interrupts
> ERR:          0
> MIS:          0

hm, OK.

I'd suggest that you raise a separate report against
acpi_config-interrupts@xxxxxxxxxxxxxxxxxxxx for this one - it does appear
to be unrelated, I think.

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux