mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: Borislav Petkov <borislav.petkov@amd.com>
Cc: Mark Hounschell <dmarkh@cfl.rr.com>,
	Andreas Herrmann <andreas.herrmann3@amd.com>,
	john stultz <johnstul@us.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: PROBLEM: Can't boot a (HZ = 1000) kernel using an AMD Phenom-II processor
Date: Fri, 06 Feb 2009 09:11:06 -0500	[thread overview]
Message-ID: <498C44FA.1010106@compro.net> (raw)
In-Reply-To: <20090206135248.GB23459@aftab>

Borislav Petkov wrote:
> Hi,
> 
> On Thu, Feb 05, 2009 at 12:19:37PM -0500, Mark Hounschell wrote:
>> A tickless kernel didn't change anything. I did get a serial console connected
>> and below is what I got. I don't see much usefull. Attached is the config.
> 
> Nope, not really. It happens really early in the process for initcalls.
> By the way, is the system then completely locked up or you can enter
> characters from the keyboard?
> 

No. When it happens the keyboard is dead.

>> Press any key to continue.
>> root (hd0,0)
>>  Filesystem type is ext2fs, partition type 0x83
>> kernel /vmlinuz-2.6.26.8-1000Hz  root=/dev/sda5 hwprobe=-modules.pata apm=off s
>> elinux=0 noresume splash=silent debug initcall_debug log_buf_len=10M console=tt
>> yS0,19200n8 vga=normal
>>    [Linux-bzImage, setup=0x2e00, size=0x1827c0]
>> initrd /initrd-2.6.26.8-1000Hz
>>    [Linux-initrd @ 0x37622000, 0x9cdf42 bytes]
>>
>> Initializing cgroup subsys cpuset
>> Linux version 2.6.26.8-1000Hz (root@harley) (gcc version 4.3.1 20080507
>> (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #5 SMP PREEMPT Wed Feb9
> 
> Is this actually a Suse distribution kernel (with a lot of patches on it) or a stock one?
> 

I don't use SuSE's kernels, just the dist. Every thing I'll be using while your
helping me will be
stock and not tainted.

>> BIOS-provided physical RAM map:
>>  BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
>>  BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
>>  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
>>  BIOS-e820: 0000000000100000 - 00000000bffe0000 (usable)
>>  BIOS-e820: 00000000bffe0000 - 00000000bffe3000 (ACPI NVS)
>>  BIOS-e820: 00000000bffe3000 - 00000000bfff0000 (ACPI data)
>>  BIOS-e820: 00000000bfff0000 - 00000000c0000000 (reserved)
>>  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
>>  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
>>  BIOS-e820: 0000000100000000 - 0000000140000000 (usable)
>> x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
>> Warning only 4GB will be used.
>> Use a HIGHMEM64G enabled kernel.
>> 3200MB HIGHMEM available.
>> 896MB LOWMEM available.
>> found SMP MP-table at [c00f3f00] 000f3f00
>> Entering add_active_range(0, 0, 1048576) 0 entries of 256 used
>> Zone PFN ranges:
>>   DMA             0 ->     4096
>>   Normal       4096 ->   229376
>>   HighMem    229376 ->  1048576
>> Movable zone start PFN for each node
>> early_node_map[1] active PFN ranges
>>     0:        0 ->  1048576
>> On node 0 totalpages: 1048576
>>   DMA zone: 32 pages used for memmap
>>   DMA zone: 0 pages reserved
>>   DMA zone: 4064 pages, LIFO batch:0
>>   Normal zone: 1760 pages used for memmap
>>   Normal zone: 223520 pages, LIFO batch:31
>>   HighMem zone: 6400 pages used for memmap
>>   HighMem zone: 812800 pages, LIFO batch:31
>>   Movable zone: 0 pages used for memmap
>> DMI 2.5 present.
>> ACPI: RSDP 000F7FB0, 0024 (r2 RX780 )
>> ACPI: XSDT BFFE3080, 0044 (r1 RX780  AWRDACPI 42302E31 AWRD        0)
>> ACPI: FACP BFFE8C80, 00F4 (r3 RX780  AWRDACPI 42302E31 AWRD        0)
>> ACPI: DSDT BFFE3200, 5A71 (r1 RX780  AWRDACPI     1000 MSFT  100000E)
>> ACPI: FACS BFFE0000, 0040
>> ACPI: HPET BFFE8E40, 0038 (r1 RX780  AWRDACPI 42302E31 AWRD       98)
>> ACPI: MCFG BFFE8E80, 003C (r1 RX780  AWRDACPI 42302E31 AWRD        0)
>> ACPI: APIC BFFE8D80, 0084 (r1 RX780  AWRDACPI 42302E31 AWRD        0)
>> ATI board detected. Disabling timer routing over 8254.
>> ACPI: PM-Timer IO Port: 0x4008
>> ACPI: Local APIC address 0xfee00000
>> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
>> ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
>> ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
>> ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
>> ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
>> ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
>> ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
>> ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
>> ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
>> IOAPIC[0]: apic_id 4, version 33, address 0xfec00000, GSI 0-23
>> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
>> ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
>> ACPI: IRQ0 used by override.
>> ACPI: IRQ2 used by override.
>> ACPI: IRQ9 used by override.
>> Enabling APIC mode:  Flat.  Using 1 I/O APICs
>> ACPI: HPET id: 0x10b9a201 base: 0xfed00000
>> Using ACPI (MADT) for SMP configuration information
>> Allocating PCI resources starting at c2000000 (gap: c0000000:20000000)
>> SMP: Allowing 4 CPUs, 0 hotplug CPUs
>> PERCPU: Allocating 38788 bytes of per cpu data
>> NR_CPUS: 32, nr_cpu_ids: 4
>> Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 1040384
>> Kernel command line: root=/dev/sda5 hwprobe=-modules.pata apm=off selinux=0
>> noresume splash=silent debug initcall_debug log_buf_len=10M console=ttyS0,19200l
>> log_buf_len: 16777216
>> mapped APIC to ffffb000 (fee00000)
>> mapped IOAPIC to ffffa000 (fec00000)
>> Enabling fast FPU save and restore... done.
>> Enabling unmasked SIMD FPU exception support... done.
>> Initializing CPU#0
>> Preemptible RCU implementation.
>> PID hash table entries: 4096 (order: 12, 16384 bytes)
>> Detected 3360.327 MHz processor.
> 
> Is your CPU overclocked?
> 

It is as of yesterday. I am not a gamer though.

>> Console: colour VGA+ 80x25
>> console [ttyS0] enabled
>> Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
>> Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
>> Memory: 3080904k/4194304k available (1751k kernel code, 63472k reserved, 730k
>> data, 216k init, 2228096k highmem)
>> virtual kernel memory layout:
>>     fixmap  : 0xffe15000 - 0xfffff000   (1960 kB)
>>     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
>>     vmalloc : 0xf8800000 - 0xff7fe000   ( 111 MB)
>>     lowmem  : 0xc0000000 - 0xf8000000   ( 896 MB)
>>       .init : 0xc0373000 - 0xc03a9000   ( 216 kB)
>>       .data : 0xc02b5ca2 - 0xc036c6d0   ( 730 kB)
>>       .text : 0xc0100000 - 0xc02b5ca2   (1751 kB)
>> Checking if this processor honours the WP bit even in supervisor mode...Ok.
>> CPA: page pool initialized 1 of 1 pages preallocated
>> SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
> 
> Ok, here are two things you could try:
> 
> Disable CONFIG_HIGH_RES_TIMERS (high resolution timers support in
> "Processor type and features"), boot with "apic=debug" and send me the
> output. I'd like to see how the lapic timer gets programmed. It would
> be better for that exercise to get the latest stable kernel, 2.6.28.3,
> imho.
> 
> The other thing you could do is get x86info tools from here:
> http://www.codemonkey.org.uk/projects/x86info/. However, get either a
> daily snapshot or a checkout from the git repository and build it on
> your system. Then do
> 
> x86info -a > x86info.txt
> 
> lsmsr -V3 -a > lsmsr.txt
> 
> and send me those text files - we might be able to get a clue what's going on
> from them.
> 
> Thanks.
> 

Ok, I'll do the rest of what you asked tonight.

Regards
Mark

  reply	other threads:[~2009-02-06 14:11 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 12:38 Mark Hounschell
2009-01-19  8:48 ` Mark Hounschell
2009-01-19 12:41   ` Bartlomiej Zolnierkiewicz
2009-01-19 14:45     ` Mark Hounschell
2009-01-19 23:05       ` Mark Hounschell
2009-01-19 14:22 ` Borislav Petkov
2009-01-19 14:54   ` Mark Hounschell
2009-01-19 23:14     ` Mark Hounschell
2009-01-20  0:25 ` john stultz
2009-01-20  9:08   ` Mark Hounschell
2009-01-20  9:37     ` Andreas Herrmann
2009-01-20 21:08       ` Mark Hounschell
2009-01-23  9:34         ` Mark Hounschell
2009-01-23 13:04           ` Andreas Herrmann
2009-01-23 14:47             ` Borislav Petkov
2009-01-23 22:24               ` Mark Hounschell
2009-01-23 22:46             ` Mark Hounschell
2009-01-26 18:26               ` Mark Hounschell
2009-01-27 16:38                 ` Borislav Petkov
2009-01-28  0:30                   ` Mark Hounschell
2009-01-28  0:33                     ` Mark Hounschell
2009-01-31  9:15                       ` Mark Hounschell
2009-02-02 17:05                         ` Borislav Petkov
2009-02-03  9:17                           ` Mark Hounschell
2009-02-03 15:11                             ` Borislav Petkov
2009-02-03 19:15                               ` Mark Hounschell
2009-02-05 17:19                                 ` Mark Hounschell
2009-02-06 13:52                                   ` Borislav Petkov
2009-02-06 14:11                                     ` Mark Hounschell [this message]
2009-02-06 17:55                                       ` Mark Hounschell
2009-02-06 22:20                                         ` Mark Hounschell
2009-02-09 14:18                                           ` Borislav Petkov
2009-02-09 15:29                                             ` Mark Hounschell
2009-02-18 13:11                                               ` Mark Hounschell
2009-02-18 14:18                                                 ` Borislav Petkov
2009-02-18 16:57                                                   ` Mark Hounschell
2009-02-18 17:42                                                     ` Borislav Petkov
2009-02-18 21:16                                                       ` Mark Hounschell
2009-02-19 10:37                                                         ` Mark Hounschell
2009-02-19 14:11                                                           ` Andreas Herrmann
2009-02-19 15:16                                                             ` Mark Hounschell
2009-02-19 15:19                                                               ` Borislav Petkov
2009-02-19 15:54                                                                 ` Mark Hounschell
2009-02-20 11:53                                                                   ` Andreas Herrmann
2009-02-20 12:34                                                                     ` Ingo Molnar
2009-02-20 21:51                                                                       ` Andreas Herrmann
2009-02-20 15:43                                                                     ` Mark Hounschell
2009-02-20 16:08                                                                       ` Andreas Herrmann
2009-02-20 16:38                                                                         ` Andreas Herrmann
2009-02-20 17:09                                                                           ` Mark Hounschell
2009-02-20 17:40                                                                             ` Mark Hounschell
2009-02-20 18:22                                                                               ` Andreas Herrmann
2009-02-20 18:28                                                                                 ` Mark Hounschell
2009-02-20 19:54                                                                                   ` Mark Hounschell
2009-02-20 20:27                                                                                     ` Mark Hounschell
2009-02-20 22:28                                                                                       ` Andreas Herrmann
2009-02-21  1:14                                                                                         ` Mark Hounschell
2009-02-21 13:20                                                                                           ` Mark Hounschell
2009-02-20 17:06                                                                         ` Mark Hounschell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=498C44FA.1010106@compro.net \
    --to=markh@compro.net \
    --cc=andreas.herrmann3@amd.com \
    --cc=borislav.petkov@amd.com \
    --cc=dmarkh@cfl.rr.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome