linux-kernel - Re: mutex

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: <dd18b0c30804091440x6e029daes8dd5f4dd848f5154@mail.gmail.com>
Date:	Wed, 9 Apr 2008 21:40:42 +0000
From:	"Justin Mattock" <justinmattock@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	"Linux Kernel" <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Ingo Molnar" <mingo@...e.hu>,
	"Peter Zijlstra" <a.p.zijlstra@...llo.nl>
Subject: Re: mutex_unlock

On Wed, Apr 9, 2008 at 8:40 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
>
> On Wednesday, 9 of April 2008, Justin Mattock wrote:
>  > Hello with testing out git(very cool); my first test was with
>  > 2.6.25-rc8-00194-g4cac04d ran vary smoothly;
>  > then I decided to pull the latest git (2.6.25-rc8-00208-g7180c4c)and
>  > see what I might find.
>  > upon reboot the system starts up giving me this:
>  >
>  > Starting up
>  > Decompressing Linux Done
>  > Booting the kernel
>  > __   <-------blinking
>  >
>  > I waited a few seconds or minutes but nothing;
>  > after reading earlier posts about something with a mutex_unlock maybe
>  > this was what I was experiencing.
>  > when loading a live cd and recompiling the same kernel, I noticed
>  > under kernel hacking;
>  >
>  > RT Mutex debugging
>  > Built in scriptable tester for rt-mutexes
>  > Spinlock and rw-lock debugging
>  > Mutex debugging basic checks
>  > Lock debugging detect incorrect freeing of live locks
>  > Lock debugging prove locking correctness
>  > lock usage statistics
>  > Lock dependency engine debugging
>  > spinlock debugging sleep-inside-spinlock checking
>  > Locking API boot-time self-tests
>  >
>  > With not knowing what I was doing I chose yes to all of these options,
>  > then reboot -f,
>  > The system booted up properly,
>  >
>  > Is there a way where I can find out if this was what was going on?
>  > could this be something different?
>
>  Hm, interesting.
>
>  It looks like our locking debugging code may hide some issues ...
>
>  Thanks,
>  Rafael
>

Maybe; weird  having something like that happen.(maybe it was
something like what appletouch is doing i.g. could not do mode request
error. The problem  is it very seldom, every X amount of boots)  I can
go back in the kernel and see if I can find out what option really
caused the system to boot properly(hopefully). Also with suspend; I
update to the latest openGl to see if suspend works, but it seems to
be worst with the latest release, i.g. a few days ago I update xorg to
7.3 with sid, suspend would give me a blank screen but no reboot(I
should of left my mouse on the terminal, then once the blank screen
shows up issue dmesg > suspend), now with the latest update with
openGL(today) I receive a blank screen and a reboot.
Maybe openGl needs to have DRI enabled? in order for this to work...

-- 
Justin P. Mattock
--
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/