linux-kernel - Re: BUG: spinlock lockup while performing FS operations

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAA9_cmfSTgF5WxcAFMa+TgfN1166a=XZziToF1mSyP2LqX9ctQ@mail.gmail.com>
Date:	Thu, 6 Oct 2011 17:39:03 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	Валерий <paramonov@...sia.ru>
Cc:	linux-kernel@...r.kernel.org, neilb@...e.de,
	linux-raid@...r.kernel.org, axboe@...nel.dk, duaneg@...da.com
Subject: Re: BUG: spinlock lockup while performing FS operations

On Thu, Oct 6, 2011 at 5:50 AM, Валерий <paramonov@...sia.ru> wrote:
> Hi!
>
> Faced with this problem. There are RAID5, assembled by mdadm (/dev/md127),
> which is divided into 2 partitions (md127p1 and md127p2). In both reiserfs.
> The
> second partition is exported via NFS. Everything works, the array is intact
> and
> fully synchronized. SMART says disks are healthy. But when copy too many
> files
> all hangs and saves only the reset. After a reset of course runs fsck, and
> then
> synchronize the array.
>
> I have a brand new computer. Sleaze is not set. Motherboard gigabyte
> 870-UD3,
> Power Supply FSP 700W, memory 16Gb Kingston, CPU Phenom II X6 1090T.
>
> I  reported an error  on  bugs.gentoo.org:
> https://bugs.gentoo.org/show_bug.cgi?id=385047
> Was  compiling a custom kernel  with support for  debugging and  debug
> messages are  received.
> Duane Griffin  then  sent me  upstream.
>
> Now I have have BUG spinlock lockup on screen:
>
> Nov 26 13:34:46 localhost kernel: BUG: spinlock lockup on CPU#2, mc/7609,
> ffff880419c37200
> Oct  4 15:55:50 localhost kernel: BUG: spinlock lockup on CPU#3,
> flush-9:127/2391, ffff880419c37200
>
> Full log from /var/log/messages:

This is the full log?  I see other /var/log/messages excerpts from the
gentoo bugzilla.  Just wondering if there were any other warnings in
the log that precede the failure?

Can you attach the kernel configuration file to that bugzilla as well.

It sounds like you can reproduce it reliably.  Is this a recent
upgrade, or a new install?  If it was working before an upgrade we
might be able to bisect.

--
Dan
--
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/