public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: wzab <wzab@ise.pw.edu.pl>
To: linux-kernel@vger.kernel.org
Subject: Kernel panic on HT machine - full logs with debug from a few boots (some successful)
Date: Sun, 05 Jun 2011 22:22:17 +0200	[thread overview]
Message-ID: <4DEBE579.1070508@ise.pw.edu.pl> (raw)
In-Reply-To: <4DEB4EF2.5050102@elektron.elka.pw.edu.pl>

[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]

Hi,
I tried to find the source of the problem I experience, supposing, that 
it may affect also other users of machine with Hyper-Threaded CPU.

I've recompiled the kernel with debugging support.
If I remember correctly, machine was booted 5 times. Two of restarts
were successful and even GDM started.

Attached (in gzipped form to spare bandwidth) are logs from serial 
console (with overwritten MAC addresses of NICs), and configuration of 
the kernel.

Crash seems to happen in random places:
1. [    9.589453] BUG: unable to handle kernel paging request at
     0045e22f
     [    9.590022] IP: [<c02e3fb2>] acpi_evaluate_object+0xf1/0x1f2
     [    9.590022] *pde = 00000000
     [    9.590022] Oops: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
     [    9.590022] last sysfs file:
      /sys/devices/platform/serial8250/tty/ttyS0/uevent
     [    9.590022] Modules linked in: snd_page_alloc processor(+) unix

2.  [   15.995196] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
     [   16.064443] agpgart-intel 0000:00:00.0: Intel 865 Chipset
     [   16.133686] BUG: sleeping function called from invalid context 
at kernel/mutex.c:278
     [   16.133693] BUG: unable to handle kernel NULL pointer 
dereference at   (null)
     [   16.133702] IP: [<001d9726>] 0x1d9725
     [   16.133711] *pde = 00000000
     [   16.133716] Oops: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
     [   16.133724] last sysfs file: 
/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:12/PNP0303:00/uevent

As crash occurs only with HT on and doesn't happen on another machine 
with 2 cores, it seems that maybe the problem is associated with 
incorrect allocation of resources or locking for HT enabled CPU...

-- 
Regards,
Wojtek

[-- Attachment #2: panic5.log.gz --]
[-- Type: application/x-gzip, Size: 55310 bytes --]

[-- Attachment #3: .config.gz --]
[-- Type: application/x-gzip, Size: 24319 bytes --]

  reply	other threads:[~2011-06-05 20:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-04 20:04 Random kernel panics when booting 2.6.39.1 wzabolot@elektron.elka.pw.edu.pl
2011-06-04 20:07 ` wzabolot@elektron.elka.pw.edu.pl
2011-06-04 21:41 ` Machine panicking with 2.6.39.1 boots correctly with acpi=off wzabolot@elektron.elka.pw.edu.pl
2011-06-04 22:01   ` acpi=off switches off also HT support, maybe it is something SMP related? wzabolot@elektron.elka.pw.edu.pl
2011-06-05  9:40     ` Kernel panic with 2.6.39.1 - switching off HT in BIOS helps wzabolot@elektron.elka.pw.edu.pl
2011-06-05 20:22       ` wzab [this message]
2011-06-11 15:23         ` kmemcheck error and panic when booting 2.6.39.1 , however acpi=off allows to boot wzab
2011-06-11 15:28           ` Forgotten attachment " wzab
2011-06-11 16:15           ` wzab
2011-07-06 22:13             ` Tech

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=4DEBE579.1070508@ise.pw.edu.pl \
    --to=wzab@ise.pw.edu.pl \
    --cc=linux-kernel@vger.kernel.org \
    /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