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>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200709251515.51876.rjw@sisk.pl>
Date:	Tue, 25 Sep 2007 15:15:51 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Mikhail Kshevetskiy <mikhail.kshevetskiy@...il.com>,
	linux-kernel@...r.kernel.org, Dave Jones <davej@...hat.com>,
	Chuck Ebbert <cebbert@...hat.com>
Subject: Re: 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents

On Tuesday, 25 September 2007 14:52, Rafael J. Wysocki wrote:
> On Tuesday, 25 September 2007 14:28, Thomas Gleixner wrote:
> > On Tue, 2007-09-25 at 14:20 +0200, Rafael J. Wysocki wrote:
> > > > > > As i can see from the log, you are booting on computer with dualcore AMD
> > > > > > processor. Do you have C1E feature enabled? 
> > > 
> > > That's possible, how to check?
> > > 
> > > > > > i386 kernel disable lapic on dualcore AMD with C1E support (see 
> > > > > > http://lkml.org/lkml/2007/3/29/199). x86_64 kernel do not have this
> > > > > > patch still (it's required for tickless kernel only).
> > > > > 
> > > > > Well it is required for non tickless mode as well.
> > > > > 
> > > > > >  As result, if
> > > > > > you run x86_64 kernel with hrt patch on such computer, the system
> > > > > > will stall during boot on lapic timer calibration.
> > > > > 
> > > > > Thanks for the reminder. I have a look into this.
> > > > 
> > > > Can you please boot mainline and provide the output of:
> > > > 
> > > > # cat /proc/interrupts; sleep 10; cat /proc/interrupts
> > > 
> > > albercik:~ # cat /proc/interrupts; sleep 10; cat /proc/interrupts
> > >            CPU0       CPU1
> > >   0:    1159492          0  local-APIC-edge      timer
> > > LOC:          0    1158220   Local interrupts
> > >
> > >   0:    1161996          0  local-APIC-edge      timer
> > > LOC:          0    1160723   Local interrupts
> > 
> > Hmm. That's strange. It looks like the local apic timer is not used, but
> > x86_64 definitely lacks the above check.
> 
> Ouch, sorry.  This is from the kernel booted with "noapictimer".
> 
> I'll get the correct output in a little while.

OK, this one is from -rc7 with no extra command line:

albercik:~ # cat /proc/interrupts; sleep 10; cat /proc/interrupts
           CPU0       CPU1
  0:      27311          0  local-APIC-edge      timer
  1:          1         77   IO-APIC-edge      i8042
  8:          0          0   IO-APIC-edge      rtc
 12:          0        148   IO-APIC-edge      i8042
 14:         19        683   IO-APIC-edge      ide0
 16:        178      12443   IO-APIC-fasteoi   sata_sil, HDA Intel
 19:        111      15197   IO-APIC-fasteoi   ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
 20:          0          3   IO-APIC-fasteoi   tifm_7xx1, yenta, sdhci:slot0, ohci1394
 21:          0        113   IO-APIC-fasteoi   acpi
NMI:          0          0
LOC:      27270      27119
ERR:          2
           CPU0       CPU1
  0:      29815          0  local-APIC-edge      timer
  1:          1         77   IO-APIC-edge      i8042
  8:          0          0   IO-APIC-edge      rtc
 12:          0        148   IO-APIC-edge      i8042
 14:         20        772   IO-APIC-edge      ide0
 16:        178      12451   IO-APIC-fasteoi   sata_sil, HDA Intel
 19:        112      17199   IO-APIC-fasteoi   ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
 20:          0          3   IO-APIC-fasteoi   tifm_7xx1, yenta, sdhci:slot0, ohci1394
 21:          0        117   IO-APIC-fasteoi   acpi
NMI:          0          0
LOC:      29774      29623
ERR:          2
albercik:~ #

Greetings,
Rafael

-
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