0f c1 03 ff c8 78
11 65 48 8b 04 25 c0 a7 00 00 48 89 43 18
RIP [] mutex_lock_interruptible+0xe/0x40
RSP
CR2: 00a1
---[ end trace 369d4585fbe82a05 ]---
Fixing recursive fault but reboot is needed!
--
Cal Peake
On Mon, 13 Aug 2007, Joe Perches wrote:
> On Tue, 2007-08-14 at 00:29 -0400, Cal Peake wrote:
> > Prolly /[^a-z0-9]/i would the safest bet. Also don't forget to escape
> > double quotes (e.g. "Jonathan \"Jon\" Doe" <[EMAIL PROTECTED]>).
>
> A-
ail = "${name} \<${email}\>";
> }
> return $formatted_email;
> }
>
> Anyone know what chars require the name be quoted?
> I've got: "," "@" "<" ">" ?
Prolly /[^a-z0-9]/i would the safest bet. Also don'
r the lapic
Andi, just noticed that the comment above needs to be updated now.
--
Cal Peake
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
e? This describes what, but it should
> also describe
> > why; after all if somebody made this error they may not know they why.
>
> I'm open to suggestions..
Point to or quote from: http://c-faq.com/malloc/mallocnocast.html ?
--
Cal Peake
-
To unsubscribe from this lis
of a per cpu flag to handle this.
> If any CPU has C1E enabled disabled lapic use.
>
> Thanks to Cal Peake for debugging.
> Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Acked-by: Cal Peake <[EMAIL PROTECTED]>
--
Cal Peake
-
To unsubscribe from this list: send the lin
On Wed, 8 Aug 2007, Andi Kleen wrote:
> Not sure why the MSR varies between cores though.
Yeah that boggled me too.
> It's better to just make it a global instead.
Haven't gotten to figuring out how to do *that* yet... but here's a
cleanup for the detection function:
Fr
return 1 from the function. So when we call the above function from
init_amd we prolly need to do a
set_bit(X86_FEATURE_LAPIC_TIMER_BROKEN, c->x86_capability);
for each core if any of them happen to return true upon checking for a
broken timer.
Andi, does that seem right?
--
Cal Peak
LBA48 NCQ (depth 0/32)
ata1.00: configured for UDMA/100
Might be dependent on the controller and/or the driver. Got a nVidia MCP51
using sata_nv here.
--
Cal Peake
roller has a
driver. If so, enable it, enable SCSI cdrom support, and disable the old
IDE stuff. If all goes well you should get /dev/sr0 which will be your new
cdrom device.
Cheers,
--
Cal Peake
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On Fri, 3 Aug 2007, Ben Collins wrote:
> nolapic_timer does not fix it for me. Only nolapic and acpi=off works. I
> commented on that thread as well now, thanks.
Interesting. However, I don't have NO_HZ so maybe that plays on it...
--
Cal Peake
-
To unsubscribe from this list: se
d <http://marc.info/?t=11857327166&r=1&w=2>. Short version:
nolapic_timer should fix things for the moment. Long term: some AMD kernel
code needs to be fixed up to deal with a broken local APIC.
Cheers,
--
Cal Peake
-
To unsubscribe from this list: send the line "unsubscribe l
On Thu, 2 Aug 2007, Linus Torvalds wrote:
> On Thu, 2 Aug 2007, Cal Peake wrote:
> >
> > Figured I should have sent that right after I hit the send key...
> >
> > processor : 0
> > vendor_id : AuthenticAMD
> > cpu family : 15
> > model
On Thu, 2 Aug 2007, Chuck Ebbert wrote:
> On 08/02/2007 03:42 PM, Cal Peake wrote:
> > On Thu, 2 Aug 2007, Chuck Ebbert wrote:
> >
> >> Try the 'nolapic_timer' option.
> >
> > Ah, thank you Chuck! This looks to have fixed the stalling/hangin
On Thu, 2 Aug 2007, Chuck Ebbert wrote:
> On 08/02/2007 01:50 PM, Cal Peake wrote:
> > This problem seems to be getting worse. With the latest linus tree, after
> > the initial hang where the power button is needed to bring the system back
> > to life, the boot pro
e keyboard interrupt firing off is doing something to help
it. The system seems OK though after booting is finished.
Upon shutdown it actually stalls out without help from the shift key.
Any thoughts on this, or tips to help debug it further?
thx, Cal
On Mon, 30 Jul 2007, Cal Peake wrote:
&g
nd broken configs to be examined? :)
--
Cal Peake
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[EMAIL PROTECTED] is prolly
the best bet with a CC to l-k.
Also, please see Documentation/SubmittingPatches, particularly section 12
about signing off your work.
cheers,
--
Cal Peake
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messa
2370/2371 Laptop
AMD Turion 64 X2 TL-50/TL-52
nVidia MCP51 chipset
Here a small matrix of my tests:
2.6.20.15 SMP : OK
2.6.21.5 SMP: hang
2.6.21.5 UP w/o APIC: OK
2.6.22.1 UP : hang
2.6.22.1 UP w/o IO-APIC : hang
2.6.22.1 UP w/o APIC : OK
2.6.22.
21.5-smp hangs.
Frank, can you try a non-SMP build with ACPI and see if you still have the
problem?
I've tried so many different option combos I don't remember if I've done
one with SMP and w/o ACPI but I'll try that sometime today. Haven't tried
ACPI debugging yet eit
Update the inotify entry in MAINTAINERS to be consistent with the rest of
the file.
Signed-off-by: Cal Peake <[EMAIL PROTECTED]>
--- ./MAINTAINERS~orig 2006-12-12 11:44:01.0 -0500
+++ ./MAINTAINERS 2006-12-12 12:08:02.0 -0500
@@ -1504,8 +1504,10 @@
S: Main
According to Dmitry in <http://lkml.org/lkml/2006/10/17/280>, the input
list is subscribers only. I'm assuming here that both are but a
confirmation would be nice... :)
From: Cal Peake <[EMAIL PROTECTED]>
Annotate the MAINTAINERS file to reflect the subscribers only nat
On Mon, 5 Sep 2005, Mathieu wrote:
> the bioses released by phoenix seem a little broken. try a 2.6.13
> kernel with the option ec_burst=1.
I agree with the broken phoenix part but be careful playing with ec_burst.
When it was set to default pre-2.6.13-rc6 it caused my laptop to overheat
and tr
Linus,
I think I remember reading one time that you have permissions on the
snapshots/ dir on kernel.org? Any chance all the pre-2.6.13 stuff can be
pushed to the old/ dir?
Also, 2.6.13-git1 didn't get generated right (it's empty!) but the log is
fine (300k worth). Hopefully someone can fix th
On Fri, 5 Aug 2005, Andreas Steinmetz wrote:
> AFAIK it works when agp is built into the kernel. You will get problems
> when it is built as a module. In the module case you may want to try if
> loading the module before resuming helps.
Strange. I've had it built as a module from day one and neve
On Thu, 4 Aug 2005, Andrew Morton wrote:
> Michal Schmidt <[EMAIL PROTECTED]> wrote:
> >
> > Does resuming from swsuspend work for anyone with amd64-agp loaded?
>
> It would seem not ;)
Must have missed the OP. Yes I can resume fine from swsusp with amd64-agp.
System is an Averatec 3270 (Mobile
On Fri, 29 Jul 2005, Mickey Stein wrote:
> This is regarding *-rc4 and *-rc4-git1: I slapped together my favorite config
> and gave it a test run. It had a bit of a problem and ground to a halt after
> spewing these into the log.
>
> If I can find the time tomorrow morning, I'll leave parport_pc
On Fri, 29 Jul 2005, Linus Torvalds wrote:
> Thanks. Just out of interest, does this patch fix it instead?
Indeed it does, thanks Linus!
-cp
>
> diff --git a/include/asm-i386/bitops.h b/include/asm-i386/bitops.h
> --- a/include/asm-i386/bitops.h
> +++ b/include/asm-i386/bitops.h
> @@ -335,
On Thu, 28 Jul 2005, Andrew Morton wrote:
> The procfs inode IDR tree is scrogged. I'd be suspecting a random memory
> scribble. I'd suggest that you enable CONFIG_DEBUG_SLAB,
> CONFIG_DEBUG_PAGEALLOC, CONFIG_DEBUG_everything_else and retest.
>
> If that doesn't show anything, try eliminating s
Hi,
Getting this nastiness when probing snd-cs46xx:
Unable to handle kernel paging request at virtual address 000a75a8
printing eip:
c01afe52
*pde =
Oops: [#1]
Modules linked in: snd_cs46xx gameport snd_rawmidi snd_seq_device
snd_ac97_codec snd_pcm snd_timer snd soundcore snd_page
30 matches
Mail list logo
