Bug 14012 - latest git fried my x86_64 imac
latest git fried my x86_64 imac
Status: CLOSED INSUFFICIENT_DATA
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64
All Linux
: P1 normal
Assigned To: platform_x86_64@kernel-bugs.osdl.org
:
Depends on:
Blocks: 13615
  Show dependency treegraph
 
Reported: 2009-08-19 22:16 UTC by Rafael J. Wysocki
Modified: 2009-08-26 21:07 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.31-rc
Tree: Mainline
Regression: Yes


Attachments

Description Rafael J. Wysocki 2009-08-19 22:16:04 UTC
Subject    : latest git fried my x86_64 imac
Submitter  : "Justin P. Mattock" <justinmattock@gmail.com>
Date       : 2009-08-13 07:20
References : http://marc.info/?l=linux-kernel&m=125014080427090&w=4

This entry is being used for tracking a regression from 2.6.30.  Please don't
close it until the problem is fixed in the mainline.
Comment 1 Tony Breeds 2009-08-19 22:50:38 UTC
This certainly isn't a powerpc problem based on the stack dump and the subject.  I don't think I have permissions to modify the component or the assignee.
Comment 2 Rafael J. Wysocki 2009-08-26 21:06:18 UTC
On Wednesday 26 August 2009, Justin P. Mattock wrote:
> Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.30.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=14012
> > Subject		: latest git fried my x86_64 imac
> > Submitter	: Justin P. Mattock<justinmattock@gmail.com>
> > Date		: 2009-08-13 07:20 (13 days old)
> > References	: http://marc.info/?l=linux-kernel&m=125014080427090&w=4
> >
> >
> >
> >    
> if I revert this commit:
> af6af30c0fcd77e621638e53ef8b176bca8bd3b4
> I can get a normal bootup.
> 
> As for this  bug, it seems I'm the only
> hitting this. The system is a fresh LFS build
> x86_64.
> In regards to keeping this open
> not sure, I don't have a problem with closing this
> and taking the blame as something I did during my build
> of the system, then if this becomes more frequent
> then open a new bug.

Note You need to log in before you can comment on or make changes to this bug.