Dave Jones wrote:
If memory serves correctly, that was circa 2.6.10, back in these commits..
commit a068ea13d1db406e15c346e93530343f6e70184c
Author: Len Brown <[EMAIL PROTECTED]>
Date: Sun Oct 10 05:21:08 2004 -0400
[ACPI] If BIOS disabled the LAPIC, believe it by default.
"lapic" is
Dave Jones wrote:
If memory serves correctly, that was circa 2.6.10, back in these commits..
commit a068ea13d1db406e15c346e93530343f6e70184c
Author: Len Brown [EMAIL PROTECTED]
Date: Sun Oct 10 05:21:08 2004 -0400
[ACPI] If BIOS disabled the LAPIC, believe it by default.
lapic is
Chuck,
On Thu, 2007-09-13 at 12:38 -0400, Chuck Ebbert wrote:
> On 09/10/2007 03:44 PM, Andi Kleen wrote:
> >> Yes, it has an hpet. And I tried every combination of options I could
> >> think of.
> >
> >> But, even stranger, x86_64 works (only i386 fails.)
> >
> > x86-64 has quite different
Chuck,
On Thu, 2007-09-13 at 12:38 -0400, Chuck Ebbert wrote:
On 09/10/2007 03:44 PM, Andi Kleen wrote:
Yes, it has an hpet. And I tried every combination of options I could
think of.
But, even stranger, x86_64 works (only i386 fails.)
x86-64 has quite different time code (at least
On Sat, Sep 15, 2007 at 01:08:25PM +0100, Matthew Garrett wrote:
> On Sat, Sep 15, 2007 at 04:08:02AM -0700, Andrew Morton wrote:
>
> > I believe that about two years ago we broke something which caused quite a
> > large number of people to need noapic. Is that the case with any of your
> >
On Sat, Sep 15, 2007 at 01:08:25PM +0100, Matthew Garrett wrote:
On Sat, Sep 15, 2007 at 04:08:02AM -0700, Andrew Morton wrote:
I believe that about two years ago we broke something which caused quite a
large number of people to need noapic. Is that the case with any of your
On Saturday, 15 September 2007 09:39, Andrew Morton wrote:
> On 06 Sep 2007 13:31:50 +0200 Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> > Chuck Ebbert <[EMAIL PROTECTED]> writes:
> >
> > > Some systems lock up without the noapic option.
> >
> > Please find patterns: cpu type, chipsets, mainboard
On Sat, Sep 15, 2007 at 04:08:02AM -0700, Andrew Morton wrote:
> I believe that about two years ago we broke something which caused quite a
> large number of people to need noapic. Is that the case with any of your
> machines? Do you know if they run 2.6.ancient without noapic?
My recollection
On Sat, 15 Sep 2007 12:58:27 +0200 Ingo Oeser <[EMAIL PROTECTED]> wrote:
> On Saturday 15 September 2007, Andrew Morton wrote:
> > There are 48 bugs in bugzilla which mention "noapic"
> >
> >
On Saturday 15 September 2007, Andrew Morton wrote:
> There are 48 bugs in bugzilla which mention "noapic"
>
>
On 06 Sep 2007 13:31:50 +0200 Andi Kleen <[EMAIL PROTECTED]> wrote:
> Chuck Ebbert <[EMAIL PROTECTED]> writes:
>
> > Some systems lock up without the noapic option.
>
> Please find patterns: cpu type, chipsets, mainboard vendors etc.
There are 48 bugs in bugzilla which mention "noapic"
On 06 Sep 2007 13:31:50 +0200 Andi Kleen [EMAIL PROTECTED] wrote:
Chuck Ebbert [EMAIL PROTECTED] writes:
Some systems lock up without the noapic option.
Please find patterns: cpu type, chipsets, mainboard vendors etc.
There are 48 bugs in bugzilla which mention noapic
On Saturday 15 September 2007, Andrew Morton wrote:
There are 48 bugs in bugzilla which mention noapic
On Sat, 15 Sep 2007 12:58:27 +0200 Ingo Oeser [EMAIL PROTECTED] wrote:
On Saturday 15 September 2007, Andrew Morton wrote:
There are 48 bugs in bugzilla which mention noapic
On Sat, Sep 15, 2007 at 04:08:02AM -0700, Andrew Morton wrote:
I believe that about two years ago we broke something which caused quite a
large number of people to need noapic. Is that the case with any of your
machines? Do you know if they run 2.6.ancient without noapic?
My recollection is
On Saturday, 15 September 2007 09:39, Andrew Morton wrote:
On 06 Sep 2007 13:31:50 +0200 Andi Kleen [EMAIL PROTECTED] wrote:
Chuck Ebbert [EMAIL PROTECTED] writes:
Some systems lock up without the noapic option.
Please find patterns: cpu type, chipsets, mainboard vendors etc.
On 09/10/2007 03:44 PM, Andi Kleen wrote:
>> Yes, it has an hpet. And I tried every combination of options I could
>> think of.
>
>> But, even stranger, x86_64 works (only i386 fails.)
>
> x86-64 has quite different time code (at least until the dyntick patches
> currently in mm)
>
> Obvious
On 09/10/2007 03:44 PM, Andi Kleen wrote:
Yes, it has an hpet. And I tried every combination of options I could
think of.
But, even stranger, x86_64 works (only i386 fails.)
x86-64 has quite different time code (at least until the dyntick patches
currently in mm)
Obvious thing would
On 09/10/2007 03:44 PM, Andi Kleen wrote:
>> Yes, it has an hpet. And I tried every combination of options I could
>> think of.
>
>> But, even stranger, x86_64 works (only i386 fails.)
>
> x86-64 has quite different time code (at least until the dyntick patches
> currently in mm)
>
> Obvious
>
> Yes, it has an hpet. And I tried every combination of options I could
> think of.
>
> But, even stranger, x86_64 works (only i386 fails.)
x86-64 has quite different time code (at least until the dyntick patches
currently in mm)
Obvious thing would be to diff the boot messages and see if
On 09/08/2007 01:17 AM, Prakash Punnoor wrote:
> On the day of Friday 07 September 2007 Chuck Ebbert hast written:
>> On 09/06/2007 07:31 AM, Andi Kleen wrote:
>>> Chuck Ebbert <[EMAIL PROTECTED]> writes:
Some systems lock up without the noapic option.
>>> Please find patterns: cpu type,
On 09/08/2007 01:17 AM, Prakash Punnoor wrote:
On the day of Friday 07 September 2007 Chuck Ebbert hast written:
On 09/06/2007 07:31 AM, Andi Kleen wrote:
Chuck Ebbert [EMAIL PROTECTED] writes:
Some systems lock up without the noapic option.
Please find patterns: cpu type, chipsets, mainboard
Yes, it has an hpet. And I tried every combination of options I could
think of.
But, even stranger, x86_64 works (only i386 fails.)
x86-64 has quite different time code (at least until the dyntick patches
currently in mm)
Obvious thing would be to diff the boot messages and see if
On 09/10/2007 03:44 PM, Andi Kleen wrote:
Yes, it has an hpet. And I tried every combination of options I could
think of.
But, even stranger, x86_64 works (only i386 fails.)
x86-64 has quite different time code (at least until the dyntick patches
currently in mm)
Obvious thing would
On the day of Friday 07 September 2007 Chuck Ebbert hast written:
> On 09/06/2007 07:31 AM, Andi Kleen wrote:
> > Chuck Ebbert <[EMAIL PROTECTED]> writes:
> >> Some systems lock up without the noapic option.
> >
> > Please find patterns: cpu type, chipsets, mainboard vendors etc.
>
> This is the
Chuck Ebbert wrote:
> On 09/06/2007 07:31 AM, Andi Kleen wrote:
> > Chuck Ebbert <[EMAIL PROTECTED]> writes:
> >> Some systems lock up without the noapic option.
> >
> > Please find patterns: cpu type, chipsets, mainboard vendors etc.
>
> This is the first one I've actually had in front of me:
>
>
On 09/06/2007 07:31 AM, Andi Kleen wrote:
> Chuck Ebbert <[EMAIL PROTECTED]> writes:
>
>> Some systems lock up without the noapic option.
>
> Please find patterns: cpu type, chipsets, mainboard vendors etc.
>
This is the first one I've actually had in front of me:
HP TX1000 notebook
On 09/06/2007 07:31 AM, Andi Kleen wrote:
Chuck Ebbert [EMAIL PROTECTED] writes:
Some systems lock up without the noapic option.
Please find patterns: cpu type, chipsets, mainboard vendors etc.
This is the first one I've actually had in front of me:
HP TX1000 notebook
Nvidia
Chuck Ebbert wrote:
On 09/06/2007 07:31 AM, Andi Kleen wrote:
Chuck Ebbert [EMAIL PROTECTED] writes:
Some systems lock up without the noapic option.
Please find patterns: cpu type, chipsets, mainboard vendors etc.
This is the first one I've actually had in front of me:
HP TX1000
On the day of Friday 07 September 2007 Chuck Ebbert hast written:
On 09/06/2007 07:31 AM, Andi Kleen wrote:
Chuck Ebbert [EMAIL PROTECTED] writes:
Some systems lock up without the noapic option.
Please find patterns: cpu type, chipsets, mainboard vendors etc.
This is the first one I've
Chuck Ebbert <[EMAIL PROTECTED]> writes:
> Some systems lock up without the noapic option.
Please find patterns: cpu type, chipsets, mainboard vendors etc.
> I found one
> that will freeze while trying to set up the timer interrupt.
> Passing 'nolapic' makes it freeze just after:
>
>
Chuck Ebbert [EMAIL PROTECTED] writes:
Some systems lock up without the noapic option.
Please find patterns: cpu type, chipsets, mainboard vendors etc.
I found one
that will freeze while trying to set up the timer interrupt.
Passing 'nolapic' makes it freeze just after:
Setting up
Some systems lock up without the noapic option. I found one
that will freeze while trying to set up the timer interrupt.
Passing 'nolapic' makes it freeze just after:
Setting up timer through ExtINT... works
Sometimes it will boot up and then freeze during the startup
scripts. Passing the
Some systems lock up without the noapic option. I found one
that will freeze while trying to set up the timer interrupt.
Passing 'nolapic' makes it freeze just after:
Setting up timer through ExtINT... works
Sometimes it will boot up and then freeze during the startup
scripts. Passing the
34 matches
Mail list logo
