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]
Date:	Mon, 03 Mar 2008 13:38:04 +0100
From:	Jiri Olsa <olsajiri@...il.com>
To:	Jiri Kosina <jkosina@...e.cz>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Nadia Derbey <Nadia.Derbey@...l.net>,
	peifferp@...il.com
Subject: Re: [BUG] soft lockup detected with ipcs

Jiri Kosina wrote:
> On Mon, 3 Mar 2008, Jiri Olsa wrote:
> 
>> ipcs.kernel.out.1 is the kernel log from the time strace ipcs was done.
>> ipcs.kernel.out.2 is from the next run of ipcs that stuck,
>> there's no overlay between those logs.
>> When the kernel freeze I'm getting logs with the spinlock lockup.. and it's repeating.
> 
> Thanks. Have you tried turning lockdep off, if that still triggers?
> 
> Aparently the first BUG leaves the spin lock locked, and all subsequent 
> accessess to it lock the machine hard. We'll need to see what goes wrong 
> inside lockdep.
> 
> Could you please run
> 
> 	addr2line -e vmlinux c0133034
> 
> (passing the path to the vmlinux binary of the crashing kernel to the -e 
> parameter).
> 

I've rebuilt the kernel meanwhile, so dont know how accurate this output is:

/home/jirka/xxx/kernel/linux-2.6-stable/include/asm/atomic_32.h:97

Anyway, I'll run the test again with your patch, and then we can run the addrline again...
I'll try to turn the lockdep off as well.
--
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/

Powered by blists - more mailing lists