lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-Id: <200709080712.51339.a1426z@gawab.com>
Date:	Sat, 8 Sep 2007 07:12:51 +0300
From:	Al Boldi <a1426z@...ab.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Why do so many machines need "noapic"?

Chuck Ebbert wrote:
> On 09/06/2007 07:31 AM, Andi Kleen wrote:
> > Chuck Ebbert <cebbert@...hat.com> writes:
> >> Some systems lock up without the noapic option.
> >
> > Please find patterns: cpu type, chipsets, mainboard vendors etc.
>
> This is the first one I've actually had in front of me:
>
>   HP TX1000 notebook
>   Nvidia C51/MCP51 mobile chipset
>
> Booting with "noapic" gives some very strange results. This is two
> snapshots of /proc/interrupts taken one second apart. It almost looks
> like timer interrupts are occurring on IRQ 0 and IRQ7 on different
> CPUs:
>
>            CPU0       CPU1
>   0:     446096       6224    XT-PIC-XT        timer
>   1:        342          6    XT-PIC-XT        i8042
>   2:          0          0    XT-PIC-XT        cascade
>   5:       3099        865    XT-PIC-XT        sata_nv
>   7:       8145     494718    XT-PIC-XT        ehci_hcd:usb2
>   8:          0          0    XT-PIC-XT        rtc0
>   9:        323          9    XT-PIC-XT        acpi
>  10:        136         36    XT-PIC-XT        HDA Intel
>  11:      43884       1091    XT-PIC-XT        ohci_hcd:usb1, eth0
>  12:        104         19    XT-PIC-XT        i8042
>  14:       1011         25    XT-PIC-XT        libata
>  15:          0          0    XT-PIC-XT        libata
> NMI:          0          0
> LOC:       6212     445951
> ERR:     403241
> MIS:          0

You may want to try to reconfigure your bios to reserve irq 5/7 for isa only.

Then post /proc/interrupts again.


Thanks!

--
Al

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ