public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Stefan Sabolowitsch <Stefan.Sabolowitsch@felten-group.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Alexander Duyck <alexander.h.duyck@intel.com>
Subject: Re: get a kernel crash with kernel 3.10.0-1.el6.elrepo.x86_64
Date: Fri, 5 Jul 2013 20:21:06 +0200	[thread overview]
Message-ID: <20130705182106.GA29025@pd.tnic> (raw)
In-Reply-To: <CDFC5EEC.A5BF%Stefan.Sabolowitsch@felten-group.com>

On Fri, Jul 05, 2013 at 09:30:53AM +0000, Stefan Sabolowitsch wrote:
> Hi all,
> I get a kernel crash with 3.10.0-1.el6.elrepo.x86_64 (on two machines the
> same problem).
> Never seen on v3.8.x / v3.9x
> 
> Any idea ?
> 
> Thx
> Stefan
> 
> -#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
> 
> abrt_version:   2.0.8
> cmdline:        ro root=/dev/mapper/vg_ipd2-lv_root rd_NO_LUKS rd_NO_MD
> SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_ipd2/lv_swap
> rd_NO_DM LANG=de_DE.UTF-8  KEYBOARDTYPE=pc KEYTABLE=de
> rd_LVM_LV=vg_ipd2/lv_root rhgb quiet
> kernel:         3.10.0-1.el6.elrepo.x86_64
> time:           Do 04 Jul 2013 16:18:29 GMT
> 
> sosreport.tar.xz: Binary file, 1665652 bytes
> 
> backtrace:
> :WARNING: at drivers/dma/ioat/dca.c:697 ioat3_dca_init+0x1f2/0x200
> [ioatdma]()
> :ioatdma 0000:00:16.0: APICID_TAG_MAP set incorrectly by BIOS, disabling
> DCA

It basically says that your BIOS is b0rked
(f3c78f8515dd4cb9e26040ebb54cf589d21137ee) and disables the Direct Cache
Access.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

      reply	other threads:[~2013-07-05 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05  9:30 get a kernel crash with kernel 3.10.0-1.el6.elrepo.x86_64 Stefan Sabolowitsch
2013-07-05 18:21 ` Borislav Petkov [this message]

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=20130705182106.GA29025@pd.tnic \
    --to=bp@alien8.de \
    --cc=Stefan.Sabolowitsch@felten-group.com \
    --cc=alexander.h.duyck@intel.com \
    --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