From: Quartexx <quartex73@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)
Date: Fri, 27 May 2011 16:26:50 +0200 [thread overview]
Message-ID: <BANLkTinhiLfyEPidRvvciM7ZiKih9jZzFg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinbUL0GJFJ_OcTWBAzbEs8-DR6n2w@mail.gmail.com>
adding:
this of course happens on dom0 (I forgot to specify) and I see these
messages in log at boot:
# grep interr /var/log/messages
May 26 01:03:14 xenhost-rack1 kernel: [ 3.552913] ACPI: Using
IOAPIC for interrupt routing
May 26 01:03:47 xenhost-rack1 kernel: [ 53.087139] hrtimer:
interrupt took 189967875 ns
May 27 06:08:43 xenhost-rack1 kernel: [ 3.571617] ACPI: Using
IOAPIC for interrupt routing
May 27 06:09:16 xenhost-rack1 kernel: [ 66.241242] hrtimer:
interrupt took 149989194 ns
Maybe it's not related to BUG that I hit. (but that hrtimer line does
not seem good.)
Some hardware info:
description: System
product: S3420GP
vendor: Intel Corporation
version: ....................
serial: ............
width: 64 bits
capabilities: smbios-2.5 dmi-2.5 vsyscall64 vsyscall32
configuration: administrator_password=disabled boot=normal chassis=server fr
ontpanel_password=disabled keyboard_password=disabled power-on_password=disabled
uuid=0FD8E440-1952-11E0-B578-001E6702C2CA
*-core
description: Motherboard
product: S3420GP
vendor: Intel Corporation
physical id: 0
*-memory
description: System Memory
physical id: 2e
slot: System board or motherboard
size: 16GiB
*-cpu:0
description: CPU
product: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz
vendor: Intel Corp.
physical id: 3b
bus info: cpu@0
version: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz
slot: CPU1
size: 2400MHz
capacity: 4GHz
width: 64 bits
clock: 133MHz
*-storage
description: RAID bus controller
product: 9690SA SAS/SATA-II RAID PCIe
vendor: 3ware Inc
physical id: 0
bus info: pci@0000:01:00.0
logical name: scsi0
version: 01
width: 64 bits
clock: 33MHz
capabilities: storage pm msi pciexpress bus_master cap_list rom
emulated
configuration: driver=3w-9xxx latency=0
resources: irq:16 memory:b0000000-b1ffffff(prefetchable) memory:
b3a00000-b3a00fff ioport:2000(size=256) memory:b3a20000-b3a3ffff(prefetchable)
I experienced controller reset but last lsi firmware seems to fix that
next prev parent reply other threads:[~2011-05-27 14:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 13:46 BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36) Quartexx
2011-05-27 14:26 ` Quartexx [this message]
2011-06-11 11:17 ` quartex
2011-06-11 11:26 ` blktap problem: " Pasi Kärkkäinen
2011-06-11 11:35 ` Quartexx
2011-06-11 12:53 ` Quartexx
2011-06-13 0:17 ` Daniel Stodden
2011-06-13 15:46 ` Quartexx
2011-06-14 8:36 ` Jan Beulich
2011-06-14 19:44 ` Daniel Stodden
2011-06-24 18:25 ` Jeremy Fitzhardinge
2011-06-24 20:01 ` Daniel Stodden
2011-07-01 11:13 ` Pasi Kärkkäinen
2011-07-01 18:08 ` Daniel Stodden
2011-07-19 12:47 ` Pasi Kärkkäinen
2011-07-19 17:01 ` Daniel Stodden
2011-07-19 17:03 ` Daniel Stodden
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=BANLkTinhiLfyEPidRvvciM7ZiKih9jZzFg@mail.gmail.com \
--to=quartex73@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).