it still should
be listed and let the tracking team know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=31702
Subject : ath5k phy2: failed to wakeup the MAC Chip
Submitter : Justin P. Mattock
Date: 2011-03-22 19:15 (40 days old)
seems fixed
-03-03 5:47 (59 days old)
Message-ID :
References : http://marc.info/?l=linux-kernel&m=129913127722786&w=2
appologizes for not responding last week on this. Anyways I looked at
the machine with the latest, and this is fixed over here(attached dmesg
to the bug report)
:
References : http://marc.info/?l=linux-kernel&m=129913127722786&w=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
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers&qu
: 2010-09-28 22:30 (52 days old)
Message-ID :
References : http://marc.info/?l=linux-kernel&m=128571307018635&w=2
yep still there..
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a
-ID :
References : http://marc.info/?l=linux-kernel&m=128571307018635&w=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 the line "unsubscribe kernel-testers" in
the body
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 is on the
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 is on the
)
Message-ID :
References : http://marc.info/?l=linux-kernel&m=128571307018635&w=2
as far as I know this is still here.. I can pull the latest to see
if it's been fixed, as well as the wireless tree to see.
Justin P. Mattock
--
To unsubscribe from this list: send the line "
it still should
be listed and let the tracking team know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16337
Subject : general protection fault: [#1] SMP
Submitter : Justin P. Mattock
Date: 2010-07-03 22:59 (58 days old)
Message-ID
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 kernel-testers" in
the body of
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 of a message
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
team
know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16337
Subject : general protection fault: [#1] SMP
Submitter : Justin P. Mattock
Date: 2010-07-03 22:59 (30 days old)
Message-ID :<4c2fc0e3.6050...@gmail.com>
Refe
physical RAM map:
o.k. so im not going insane then... problem over here is the machine is
responding as if nothing like that occurs. 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
On 02/24/2010 06:37 AM, Jan Beulich wrote:
"Justin P. Mattock" 03.02.10 02:43>>>
Could you try this simple patch (against plain 2.6.33-rc8)?
Thanks, Jan
--- a/arch/x86/include/asm/fixmap.h
+++ b/arch/x86/include/asm/fixmap.h
@@ -82,6 +82,9 @@ enum fixed_a
it still should
be listed and let the tracking team know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14487
Subject : PANIC: early exception 08 rip 246:10 error 810251b5
cr2 0
Submitter : Justin P. Mattock
Date: 2009-10-23 16:45 (122
still should
be listed and let the tracking team know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14487
Subject : PANIC: early exception 08 rip 246:10 error 810251b5
cr2 0
Submitter : Justin P. Mattock
Date: 2009-10-23 16:45 (108 days
On 02/04/10 01:57, Jan Beulich wrote:
"Justin P. Mattock" 04.02.10 10:48>>>
I see:
ohci.registers = (void *)fix_to_virt(FIX_OHCI1394_BASE);
then I think it calls:
set_fixmap_nocache(FIX_OHCI1394_BASE, ohci_base);
I'm guessing somewhere with the fix_to_virt might be
On 02/04/10 01:57, Jan Beulich wrote:
"Justin P. Mattock" 04.02.10 10:48>>>
I see:
ohci.registers = (void *)fix_to_virt(FIX_OHCI1394_BASE);
then I think it calls:
set_fixmap_nocache(FIX_OHCI1394_BASE, ohci_base);
I'm guessing somewhere with the fix_to_virt might be
On 02/04/10 01:35, Jan Beulich wrote:
"Justin P. Mattock" 04.02.10 10:17>>>
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?
No, afaict it is the ohci1394_dma=early
On 02/04/10 01:11, Jan Beulich wrote:
"Justin P. Mattock" 04.02.10 10:04>>>
a quick google on this showed somewhere
at bootmem.c any ideas on this or where
this might be caused besides fixmap?
(or is fixmap the main location?);
__native_set_fixmap() -> set_pte_vaddr()
On 02/04/10 00:54, Jan Beulich wrote:
"Justin P. Mattock" 04.02.10 00:05>>>
[ 0.00] 01 - 014000 page 2M
[ 0.00] kernel direct mapping tables up to 14000 @ b000-11000
[ 0.00] init_ohci1394_dma: initializing OHCI-1394 at 05:00.0
[ 0.0
] Call Trace:
then the rest shown on the picture on the bug report.
Out of memory?
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
hen
maybe 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
On 02/03/10 01:18, Jan Beulich wrote:
"Justin P. Mattock" 03.02.10 02:43>>>
The only thing I can think of at this point
is maybe the CFLAGS I used to build this system.
(as for the x86_32 working and x86_64 failing not sure);
I'm curious to see if anybody else is hitti
008...@vpn.id2.novell.com>
Signed-off-by: Ingo Molnar
The only thing I can think of at this point
is maybe the CFLAGS I used to build this system.
(as for the x86_32 working and x86_64 failing not sure);
I'm curious to see if anybody else is hitting this?
Justin P. Mattock
--
To unsub
her post it /is/ a regression, at least on
x86-64 and definitely between 2.6.27 (good) and 2.6.32 (bad).)
I'll go with the bisect in the morning(late over here),
and then go from there.(just pissed at myself
for not thinking to do this at the beginning).
Justin P. Mattock
--
To unsubscribe f
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"
what I get from it, then
go from there.
(man!! let this be a lesson for me);
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 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 entirel
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).
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
of
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
of regressions introduced between 2.6.31 and 2.6.32.
The following bug
still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14487
Subject : PANIC: early exception 08 rip 246:10 error 810251b5
cr2 0
Submitter : Justin P. Mattock
Date: 2009-10-23 16:45 (101 days old)
References
still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14487
Subject : PANIC: early exception 08 rip 246:10 error 810251b5
cr2 0
Submitter : Justin P. Mattock
Date: 2009-10-23 16:45 (94 days old)
References
still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14487
Subject : PANIC: early exception 08 rip 246:10 error 810251b5
cr2 0
Submitter : Justin P. Mattock
Date: 2009-10-23 16:45 (80 days old)
References
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
ore waking up
then every other cycle afterwards reacts as it should.
Threw in kernels 2.6.30,31 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 unsubscr
Kristoffer Ericson wrote:
On Sun, 22 Nov 2009 15:19:54 +0100
"Rafael J. Wysocki" 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 h
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
=commit;h=d9adc2e031bd22d5d9607a53a8d3b30e0b675f39
References : http://marc.info/?l=linux-kernel&m=125504031328941&w=4
Handled-By : Alexey Starikovskiy
Patch : http://bugzilla.kernel.org/attachment.cgi?id=23347
still there.
Justin P. Mattock
--
To unsubscribe f
ll 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
://bugzilla.kernel.org/show_bug.cgi?id=14487
Subject : PANIC: early exception 08 rip 246:10 error 810251b5
cr2 0
Submitter : Justin P. Mattock
Date: 2009-10-23 16:45 (30 days old)
References : http://lkml.org/lkml/2009/10/23/252
yes It's still
Kristoffer Ericson wrote:
On Sat, 21 Nov 2009 09:38:22 -0800
"Justin P. Mattock" wrote:
Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the cu
3384&w=4
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 reverting this one
to see, then we can go from there.
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
atus - Wait up to 32ms for the status 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
erspace thing going on
causing 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 m
Kristoffer Ericson wrote:
On Tue, 17 Nov 2009 10:07:09 -0800
"Justin P. Mattock" wrote:
Kristoffer Ericson wrote:
Im still hitting this so basicly using 2.6.30 until it get sorted. Will try and
make
some time to test the different commits. Last time I waited for it to
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 k
his 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
://bugzilla.kernel.org/show_bug.cgi?id=14487
Subject : PANIC: early exception 08 rip 246:10 error 810251b5
cr2 0
Submitter : Justin P. Mattock
Date: 2009-10-23 16:45 (25 days old)
References : http://lkml.org/lkml/2009/10/23/252
This one has me a bit
say that doing a bisect on this
was more than I had anticipated.
(still need to go through and revert commits,
to see if I can find exactly where).
So yes this should still be open.
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the bo
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://vger.kernel.org/majordomo-info.html
patch
has been pushed to the main tree..
cheers
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
eah 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 majo
e 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 majordomo info at http
uot;,
(but could be wrong)that ends up being 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 "unsub
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
--
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
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. Wysocki wrote:
This message has been generated automatically as a
another system, I used
ubuntu
and it seems to not be as bad, but still 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
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" wrote:
This m
st 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 to majord...@vg
3384&w=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 the line &quo
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:
This
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
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
://bugzilla.kernel.org/show_bug.cgi?id=14012
Subject : latest git fried my x86_64 imac
Submitter : Justin P. Mattock
Date: 2009-08-13 07:20 (13 days old)
References : http://marc.info/?l=linux-kernel&m=125014080427090&w=4
if I revert thi
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
ted. Although I'm not sure what the setup is with macmini,
I've a macbook pro ati chipset.
regards;
--
Justin P. Mattock <[EMAIL PROTECTED]>
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
70 matches
Mail list logo
