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: <481A670F.1030709@sbcglobal.net>
Date:	Thu, 01 May 2008 17:57:51 -0700
From:	Ryan Roth <ryanroth@...global.net>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	bugme-daemon@...zilla.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [Bugme-new] [Bug 10586] New: High Number of Segfaults onMacBookStarting
 With 2.6.24.5 Kernel

Andrew Morton wrote:
> On Thu, 01 May 2008 17:04:36 -0700
> Ryan Roth <ryanroth@...global.net> wrote:
>
>   
>> Since this last boot I have only got these:
>>
>>     
>>> May 1 16:26:25 kernel: gnome-power-man[3112]: segfault at 0 ip 410fda 
>>> sp 7fff4712c870 error 4 in gnome-power-manager[400000+47000]
>>> May 1 16:26:25 kernel: gnome-power-man[3116]: segfault at 0 ip 410fda 
>>> sp 7fff2959cce0 error 4 in gnome-power-manager[400000+47000]
>>> May 1 16:26:25 kernel: gnome-power-man[3119]: segfault at 0 ip 410fda 
>>> sp 7fffc7671db0 error 4 in gnome-power-manager[400000+47000]
>>>       
>
> OK.
>
> Well I don't know what the heck to do about that.  It could be that we've
> gone and changed the contents of (say) an acpi /proc file, and this happens
> to cause your particular version of gnome-power-manager to take a different
> (and buggy) codepath, so it crashes.  Or something like this.
>
> I hate to do this to you, but our best hope for getting to the bottom of
> this is for you to run a git bisection search to find out what we did which
> triggered this.  http://www.kernel.org/doc/local/git-quick.html has some
> instructions.
>
> Or you could go the other route and work out where and why
> gnome-power-manager is crashing.
>
> You could try upgrading (or downgrading) your gnome-power-manager version,
> see if that affects things.
>
> Does the problem affect only gnome-power-manager?
>
>   

OK it looks like I was possibly (probably) barking up the wrong tree.  I 
was able to get gnome-phone-manager to give me some useful information 
and it turns out that gnome-power-management crashes if 
gnome-phone-manager is running first (which I had set to autorun) 
something to due with bluetooth errors.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ