with the latest, and this is fixed over here(attached dmesg
to the bug report)
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
days old)
seems fixed with the current over here.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
old)
Message-ID :aanlktik9to0rkq2frqqfb2wnu0kyj7czybek2jbp3...@mail.gmail.com
References : http://marc.info/?l=linux-kernelm=129913127722786w=2
think this one os closed now.. but a new one has been opened:
https://bugzilla.kernel.org/show_bug.cgi?id=31702
Justin P. Mattock
...@gmail.com
Date: 2010-09-28 22:30 (52 days old)
Message-ID :aanlktim5wcgkpvekoko_ynmf9pg8mvlfqofbnufpf...@mail.gmail.com
References : http://marc.info/?l=linux-kernelm=128571307018635w=2
yep still there..
Justin P. Mattock
--
To unsubscribe from this list: send
:30 (20 days old)
Message-ID :aanlktim5wcgkpvekoko_ynmf9pg8mvlfqofbnufpf...@mail.gmail.com
References : http://marc.info/?l=linux-kernelm=128571307018635w=2
yeah it's still here...(I can try and play with this, but who knows..)
Justin P. Mattock
--
To unsubscribe from this list: send
.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 10/10/2010 12:41 PM, Rafael J. Wysocki wrote:
On Sunday, October 10, 2010, Justin P. Mattock wrote:
On 10/10/2010 10:51 AM, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry
On 10/10/2010 12:41 PM, Rafael J. Wysocki wrote:
On Sunday, October 10, 2010, Justin P. Mattock wrote:
On 10/10/2010 10:51 AM, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry
old)
Message-ID :4c2fc0e3.6050...@gmail.com
References : http://marc.info/?l=linux-kernelm=127819798215589w=2
only have seen this once..on the other hand (If im correct)maciej or
pauli where able to reproduce this.. I say leave open then go from there.
Justin P. Mattock
On 08/02/2010 06:34 AM, Rafael J. Wysocki wrote:
On Monday, August 02, 2010, Justin P. Mattock wrote:
On 08/01/2010 06:52 AM, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current
: 2010-07-25 17:06 (8 days old)
Yes, I just managed to reproduce this with 2.6.35-final, and will
update the bugzilla entry with the wire-capture needed.
ahh.. cool.. lets get this bug fixed...
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body
: 2010-07-25 17:06 (8 days old)
Yes, I just managed to reproduce this with 2.6.35-final, and will
update the bugzilla entry with the wire-capture needed.
Oops just realized your talking about another bug. nevermind.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe
://www.tux.org/lkml/
Ive played around with the machine that originally hit this. but still
cant seem to reproduce or trigger this.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo
. atheros has one of these as
well(like I posted)
how to reproduce such a beast of a bug...
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
yeah still here.. worst is I'm able to see this with
suse11.2 as well as with my custom system.
so please leave open.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers
remote debugging
via ohci1394_dma.
I did see a call trace as I was debugging
which might be related to having one
system using the patch, and the other not.
but still need to look at that.
(only saw this once out of numerous boots
(could be a rarity)).
Justin P. Mattock
--
To unsubscribe from
be the best approach with this.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
the main location?);
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
() - set_pte_vaddr_pud() -
fill_pte() - spp_getpage() - alloc_bootmem_pages() - panic().
Jan
so something is using __native_set_fixmap
that's hitting some memory address then
set_fixmap_nocache(ohci1394_dma=early)
fires off hitting the same?
Justin P. Mattock
--
To unsubscribe from this list: send
this is what I'm hitting.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
if anybody else is hitting this?
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 02/01/10 11:57, Stefan Richter wrote:
Justin P. Mattock wrote:
On 02/01/10 04:54, Dan Carpenter wrote:
On Sun, Jan 31, 2010 at 05:39:22PM -0800, Justin P. Mattock wrote:
On 01/31/10 16:43, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
On 02/01/10 14:27, Stefan Richter wrote:
Justin P. Mattock wrote:
(as for yesterdays 0x(just experimenting)Google gives me
no info on the differences between 8f's to 16f's, I was under the
impression that it's x86_32 and x86_64 for the pci address).
As Dan noted
On 02/01/10 21:45, Stefan Richter wrote:
Justin P. Mattock wrote:
So(correct me if I'm wrong), I'm generating a 64 bit register
and the kernel is looking for a 32 bit register causing the crash.
No, the class = read_pci_config(); if (class == ...) ... parts of the
code are entirely innocent
On 02/01/10 22:55, Stefan Richter wrote:
Justin P. Mattock wrote:
As for anything changed in the kernel
(2.6.31 - present), tough to say
from what I remember I had created a new fresh
lfs system using these CFLAGS:
CFLAGS=-mtune=core2 -march=core2 -O2 -pipe -fomit-frame-pointer
CXXFLAGS
around at times.
(and wont be side tracked with the other issue I was looking at);
So yeah please keep it open, and hopefully somebody
see's what is happening and maybe has a solution, or
by chance maybe I can figure something.
Justin P. Mattock
--
To unsubscribe from this list: send the line
(80 days old)
References : http://lkml.org/lkml/2009/10/23/252
I've played around with this. and
and much confused at what needs to happen.
(please feedback on what might be happening);
In any case I can have another try at finding a fix
so please leave open.
Justin P. Mattock
before doing anything
but showed the same results, leading me to beleive maybe
I have some userspace issue(libx86)going on.
I'll try reverting that commit to see.
Thanks
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord
On 12/01/09 12:27, Alan Jenkins wrote:
Justin P. Mattock wrote:
On 12/01/09 11:59, Alan Jenkins wrote:
Hi
Suspend to disk is (sometimes) hanging for me in 2.6.32-rc. I finally
got around to bisecting it, which blamed the following commit by Mel:
5f8dcc2 page-allocator: split per-cpu list
yes It's still there.. I'm wondering because
there's not much feedback on this maybe I should take
a hint! or maybe it's something people just don't
understand, and don't have time for.. In any case
I'm still looking at it(although had to look at other
reports as well).
Justin P. Mattock
there.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Johannes Berg wrote:
On Sat, 2009-11-21 at 09:38 -0800, Justin P. Mattock wrote:
I did a bisect yesterday on this, and the results
seemed to have worked over here by reverting:
75e6c3b72b3ab01c47629f3fbd0fed4e6550bf3a
cfg80211: lower dynamic PS timeout to 100ms
if Kristoffer can try
Kristoffer Ericson wrote:
On Sun, 22 Nov 2009 15:19:54 +0100
Rafael J. Wysockir...@sisk.pl wrote:
On Sunday 22 November 2009, Johannes Berg wrote:
On Sat, 2009-11-21 at 09:38 -0800, Justin P. Mattock wrote:
I did a bisect yesterday on this, and the results
seemed to have
this? i.g. running the latest git(on a macbook)
with a from scratch system with nothing of that sort,
or at least cant reproduce your error.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More
port to get a certain value
* (masked with 0x0f), returning zero if the value is obtained.
maybe your hitting a different value because of binutls.
(keep in mind I have the latest binutils running on the macbook,
but nothing switched to gold during compilation time)
Justin P. Mattock
Soeren Sonnenburg wrote:
On Sat, 2009-11-21 at 01:58 -0800, Justin P. Mattock wrote:
Soeren Sonnenburg wrote:
On Sat, 2009-11-21 at 09:56 +0100, Soeren Sonnenburg wrote:
On Wed, 2009-11-18 at 18:59 -0800, Dmitry Torokhov wrote:
On Tue, Nov 17, 2009 at 05:06:47AM
there.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
:
75e6c3b72b3ab01c47629f3fbd0fed4e6550bf3a
cfg80211: lower dynamic PS timeout to 100ms
if Kristoffer can try reverting this one
to see, then we can go from there.
In the process of doing that as we speak.
Justin P. Mattock
cool..
Justin P. Mattock
--
To unsubscribe from this list: send the line
to see if I hit it quicker (and thus finding the error commit).
So in short, its still valid and I will try and make time to fix it :)
o.k. so it is something that is enough to
cause an inconvenience.
Justin P. mattock
--
To unsubscribe from this list: send the line unsubscribe kernel
might be seeing something different(not sure though)
because of having the computer as a router etc..
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
the latest to see, and
the warning message is there.
so yes this bug report should be open
until this is fixed.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
is I'm able to
run dma early in case of an emergency).
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
).
At this point the best thing to do is to see what the
response is from the two gentlemen who where really
hitting this and seem to be running into issues
then go from there.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message
gets rid of the warning
for people crying wolf!! but probably would not close
the bugreport until the patch makes it into the main
kernel.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More
yeah this happens on the first go of
echo mem /sys/power/state
for both of my imac's I have here.
(on the second try, this message does not appear)
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord
something completely wrong,
although a couple of times it did actually work and go right to the word
I had in mind,
but most of the time this things just causes irritation.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord
Not sure where this stands. Right now all three machines I have seem
to be having no issues with the kayboard
(xserver 1.6.*) I can go and build the latest xserver(1.7) to see if I
hit something.
justin P. Mattock
On Oct 11, 2009, at 4:01 PM, Rafael J. Wysocki r...@sisk.pl wrote
present.(I'm thinking , if this
is what
others are experiencing it must be something in userspace)
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
Rafael J. Wysocki wrote:
On Monday 12 October 2009, Justin P. Mattock wrote:
Lin Ming wrote:
On Mon, 2009-10-12 at 11:14 +0800, Justin Mattock wrote:
On Sun, Oct 11, 2009 at 3:22 PM, Rafael J. Wysockir...@sisk.pl wrote:
This message has been generated
somebody who's really hitting this bug
then the results would be better if this is the area that causing
this bug.(from here the only issue I'm seeing is spinning
history commands in the terminal from time to time,
nothing of any unusable keys like others are reporting).
Justin P. Mattock
=linux-kernelm=125378723723384w=4
I attached my bisect log to the bug report, but did not individually test
some of the commits in the log to see if it finds the issue.
(I can try later on and see).
so for now I say yes keep it open.
Justin P. Mattock
--
To unsubscribe from this list: send
that a try.
then I guess just leave this open(bugreport) until this patch
http://bugzilla.kernel.org/show_bug.cgi?id=14379#c1
gets pushed into the main tree then close the bugreport.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message
Rafael J. Wysocki wrote:
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
Randy Dunlap wrote:
On Thu, 27 Aug 2009 21:45:01 +0200 Rafael J. Wysocki wrote:
On Thursday 27 August 2009, Justin P. Mattock wrote:
Rafael J. Wysocki wrote:
On Wednesday 26 August 2009, Justin P. Mattock wrote:
Rafael J. Wysocki wrote
my build
of the system, then if this becomes more frequent
then open a new bug.
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
be improved!
Justin Madru
Well I guess the problem has been bisected.
regards;
Justin P. Mattock
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
setup here is the latest xserver from intrepid
readeon, and s2ram app. echo mem /sys/power/state gives
me a black screen, then an instant reboot. s2ram recovers
as expected. Although I'm not sure what the setup is with macmini,
I've a macbook pro ati chipset.
regards;
--
Justin P. Mattock [EMAIL
57 matches
Mail list logo
