You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(200) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(162) |
Feb
(338) |
Mar
(493) |
Apr
(706) |
May
(729) |
Jun
(316) |
Jul
(435) |
Aug
(325) |
Sep
(355) |
Oct
(314) |
Nov
(336) |
Dec
(330) |
2003 |
Jan
(320) |
Feb
(387) |
Mar
(362) |
Apr
(216) |
May
(391) |
Jun
(292) |
Jul
(369) |
Aug
(334) |
Sep
(429) |
Oct
(339) |
Nov
(340) |
Dec
(344) |
2004 |
Jan
(641) |
Feb
(611) |
Mar
(603) |
Apr
(308) |
May
(321) |
Jun
(355) |
Jul
(291) |
Aug
(508) |
Sep
(482) |
Oct
(490) |
Nov
(574) |
Dec
(408) |
2005 |
Jan
(568) |
Feb
(500) |
Mar
(485) |
Apr
(357) |
May
(219) |
Jun
(370) |
Jul
(336) |
Aug
(300) |
Sep
(388) |
Oct
(257) |
Nov
(298) |
Dec
(313) |
2006 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Andi K. <ak...@su...> - 2005-12-13 05:58:46
|
On Tue, Dec 13, 2005 at 12:35:25AM -0500, Brown, Len wrote: > Andi, > this shipped already in 2.6.15-rc5, per > http://bugzilla.kernel.org/show_bug.cgi?id=5221 Ok, my apologies Len. I must have looked in a rc4 kernel by mistake. -Andi |
From: Dave J. <da...@re...> - 2005-12-13 05:43:50
|
On Tue, Dec 13, 2005 at 06:28:34AM +0100, Andi Kleen wrote: > > Hallo, > > I have the following patch in my x86-64 tree because it was needed > to boot without acpi=off on several of the machines here. > Without it the ACPI device setup code would always create a loop > in the ACPI device tree and eventually some other code walking > it would hang the machine. > > The patch has been around for a long time - it was originally > done by Thomas Renninger - and has even been shipped in SUSE 10.0 > so it was well tested > (which was 2.6.13 based, there the problem only hit occasionally, > in 2.6.14+ it seems to happen more frequently for some reason) > > I think it was queued in the ACPI trees too and acked by the > ACPI poeople. > > I know Len skipped the ACPI update for .15 for some reason, > but could we perhaps merge this safe patch. It would help > my test machines at least :) It got merged on Dec 1st. Dave |
From: Brown, L. <len...@in...> - 2005-12-13 05:35:44
|
Andi, this shipped already in 2.6.15-rc5, per http://bugzilla.kernel.org/show_bug.cgi?id=3D5221 thanks, -Len=20 >-----Original Message----- >From: Andi Kleen [mailto:ak...@su...]=20 >Sent: Tuesday, December 13, 2005 12:29 AM >To: tor...@os...; ak...@os...; Brown, Len;=20 >tr...@su...; acp...@li... >Subject: ACPI boot fix for 2.6.15 > > >Hallo, > >I have the following patch in my x86-64 tree because it was needed >to boot without acpi=3Doff on several of the machines here.=20 >Without it the ACPI device setup code would always create a loop >in the ACPI device tree and eventually some other code walking >it would hang the machine. > >The patch has been around for a long time - it was originally=20 >done by Thomas Renninger - and has even been shipped in SUSE 10.0 >so it was well tested >(which was 2.6.13 based, there the problem only hit occasionally, >in 2.6.14+ it seems to happen more frequently for some reason) > >I think it was queued in the ACPI trees too and acked by the >ACPI poeople. > >I know Len skipped the ACPI update for .15 for some reason, >but could we perhaps merge this safe patch. It would help >my test machines at least :) > >---- > >From: tr...@su... > >Avoid endless loops in ACPI device tree. > >Cc: Len...@in... > >Signed-off-by: Andi Kleen <ak...@su...> > >Index: linux/drivers/acpi/scan.c >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >--- linux.orig/drivers/acpi/scan.c >+++ linux/drivers/acpi/scan.c >@@ -1110,7 +1110,7 @@ acpi_add_single_object(struct acpi_devic > * > * TBD: Assumes LDM provides driver hot-plug capability. > */ >- result =3D acpi_bus_find_driver(device); >+ acpi_bus_find_driver(device); >=20 > end: > if (!result) > > |
From: Andi K. <ak...@su...> - 2005-12-13 05:28:40
|
Hallo, I have the following patch in my x86-64 tree because it was needed to boot without acpi=off on several of the machines here. Without it the ACPI device setup code would always create a loop in the ACPI device tree and eventually some other code walking it would hang the machine. The patch has been around for a long time - it was originally done by Thomas Renninger - and has even been shipped in SUSE 10.0 so it was well tested (which was 2.6.13 based, there the problem only hit occasionally, in 2.6.14+ it seems to happen more frequently for some reason) I think it was queued in the ACPI trees too and acked by the ACPI poeople. I know Len skipped the ACPI update for .15 for some reason, but could we perhaps merge this safe patch. It would help my test machines at least :) ---- From: tr...@su... Avoid endless loops in ACPI device tree. Cc: Len...@in... Signed-off-by: Andi Kleen <ak...@su...> Index: linux/drivers/acpi/scan.c =================================================================== --- linux.orig/drivers/acpi/scan.c +++ linux/drivers/acpi/scan.c @@ -1110,7 +1110,7 @@ acpi_add_single_object(struct acpi_devic * * TBD: Assumes LDM provides driver hot-plug capability. */ - result = acpi_bus_find_driver(device); + acpi_bus_find_driver(device); end: if (!result) |
From: <phu...@wi...> - 2005-12-13 02:08:23
|
> Maybe i'm completely out of target but what about, as said here by > Nate Lawson http://lists.freebsd.org/pipermail/freebsd-acpi/2004-November/000835.html > , to "power down the USB host controller when idle"? Might be OK, provided the USB host controller *can* be powered down *and* we won't need to wake up due to someone touching the USB mouse or keyboard :) |
From: Marco C. <mar...@gm...> - 2005-12-12 16:10:48
|
Hi again, > 2. Disable the busmaster. The kernel looks at the current busmaster > activity and then chooses if it wants to disable busmaster and enter C3. Maybe i'm completely out of target but what about, as said here by Nate Lawson http://lists.freebsd.org/pipermail/freebsd-acpi/2004-November/0= 00835.html , to "power down the USB host controller when idle"? Regards, Marco Calviani |
From: Phillip S. <ps...@cf...> - 2005-12-12 16:07:28
|
Caching is never _completely_ hidden from the kernel. I am not as familiar with the internals of the linux kernel as I am with NT, but I imagine it would have to be similar. On NT drivers issuing hardware DMA transfers must call functions in the HAL to facilitate the process. On Intel platforms, the hardware generally maintains cache coherency across multiple processors and bus masters, but this is not true on all platforms. Many non Intel platforms' caches do not support bus snooping ( as indeed, there may not even BE a bus that is shared between all processors and bus masters and memory modules ) so it is up to the HAL functions to make sure the caches stay coherent by flushing the pages being written to the device prior to the DMA starting, and invalidating the pages being read after the DMA completes. Seeing as how Linux is supported on an even wider range of even more exotic systems ( think NUMA ), I have to believe that it has similar features. Maybe it is just that the implementations of these support functions on Intel platforms is defined to be a NOOP because it is assumed that the hardware will always maintain coherency, but it seems there is at least one time where this is not the case ( entering C3 ). If this code is just disabled on Intel platforms, maybe it could be reworked so that it maintains a list of all DMA transactions that are currently in progress, then before entering C3, all the pages involved in DMA writes would be flushed, and when exiting from C3, all the pages involved in DMA reads would be invalidated. It sounds like you were talking about flushing and invalidating the ENTIRE cache when entering/exiting from C3. That would slow things down quite a bit, but doing it only to the pages that are actually involved in active DMA transfers should be fine. Janosch Machowinski wrote: > > Normally a cache should be completely hidden from the system, so a > driver can never determine the actually state of the cache. Only way to > sync the cache is to completely flush it. > |
From: Marco C. <mar...@gm...> - 2005-12-12 16:02:52
|
Hi Janosh, first of all thanks for your interest in this issue > Okay, I read through this stuff once again. I would say, that busmaster > activity is a direct write into memory. While the processor is in C3, it > can not keep it's cache in sync with the memory. So there are two > solutions to this problem for uniprocessor systems: > 1. Either you flush the cache before entering C3. This takes a relative > long period of time (according to ACPI 3.0 spec) so it should not be the > prefered method. > 2. Disable the busmaster. The kernel looks at the current busmaster > activity and then chooses if it wants to disable busmaster and enter C3. What are the possible consequences of disabling the busmaster? Does this affects also other box component (i.d. i've read somewhere that the busmaster is related to DMA access)? And how is it possible to do so? Many thanks in advance, Marco Calviani |
From: Janosch M. <sc...@tz...> - 2005-12-12 12:51:55
|
Marco Calviani wrote: > Is this an hardware limitation or a software one? > If i understood well this occur because the active bus polling that is > required to maintain communication with usb devices deny the CPU from > switching to C3, and even if there are no usb device connected but the > modules are loaded the polling prevent the switch. > Will it be possible to increase the polling time, so that maybe the > CPU can enter that state? > Okay, I read through this stuff once again. I would say, that busmaster activity is a direct write into memory. While the processor is in C3, it can not keep it's cache in sync with the memory. So there are two solutions to this problem for uniprocessor systems: 1. Either you flush the cache before entering C3. This takes a relative long period of time (according to ACPI 3.0 spec) so it should not be the prefered method. 2. Disable the busmaster. The kernel looks at the current busmaster activity and then chooses if it wants to disable busmaster and enter C3. After reading through the spec again, I would revoke my first comment and say that with a bit of policytuning you could enter C3 even with a USB mouse plugged in. |
From: Janosch M. <sc...@tz...> - 2005-12-12 12:47:43
|
Phillip Susi wrote: > I'm kind of confused as to why this is a problem myself. Yes, the CPU > cache does not snoop the busmaster activity and so the cache can become > out of sync with ram, but isn't it the job of the driver that initiates > the dma transfer to invalidate those cache lines once the transfer is > complete to bring the cache back into sync? Normally a cache should be completely hidden from the system, so a driver can never determine the actually state of the cache. Only way to sync the cache is to completely flush it. |
From: Marco C. <mar...@gm...> - 2005-12-12 09:22:13
|
Hi list, 2005/12/12, Janosch Machowinski <sc...@tz...>: > No this is not Possibe. In C3 the processor disables his cache. If you > have busmaster activity, there are direct writes into the cache (if I > remeber right). So if you allow C3 and Busmaster, you will get into some > serious truble and loose data. Is this an hardware limitation or a software one? If i understood well this occur because the active bus polling that is required to maintain communication with usb devices deny the CPU from switching to C3, and even if there are no usb device connected but the modules are loaded the polling prevent the switch. Will it be possible to increase the polling time, so that maybe the CPU can enter that state? Regards, Marco Calviani |
From: Starikovskiy, A. Y <ale...@in...> - 2005-12-12 08:40:24
|
Do you have RTC driver compiled and loaded? CONFIG_RTC in kernel .config? =20 Regards, Alex ________________________________ From: acp...@li... [mailto:acp...@li...] On Behalf Of Ronald Wielink Sent: Monday, December 12, 2005 12:30 AM To: acp...@li... Subject: [ACPI] unable to set alam using echo to /proc/acpi/alarm =09 =09 Dear all, when I try setting the alarm to wake up my pc I get the following result: =09 [root@mithrandir acpi]# pwd /proc/acpi [root@mithrandir acpi]# cat alarm 2005-12-00 00:00:00 [root@mithrandir acpi]# echo 2005-12-15 17:18:19 > alarm [root@mithrandir acpi]# cat alarm 2005-12-00 17:18:19 [root@mithrandir acpi]# =09 BTW, nothing happens at the echo'd date/time. Could someone please give me a clue where to start looking? I'm running fedora core 4, my mobo is an ASUS P5S800-VM, the documentation on the motherboard states that ACPI is supported. There is an option to turn acpi 2.0 on, but no difference... =09 Any help is greatly appreciated! =09 Regards, =09 Ronald =09 |
From: Phillip S. <ps...@cf...> - 2005-12-12 03:42:22
|
I'm kind of confused as to why this is a problem myself. Yes, the CPU cache does not snoop the busmaster activity and so the cache can become out of sync with ram, but isn't it the job of the driver that initiates the dma transfer to invalidate those cache lines once the transfer is complete to bring the cache back into sync? Janosch Machowinski wrote: > > No this is not Possibe. In C3 the processor disables his cache. If you > have busmaster activity, there are direct writes into the cache (if I > remeber right). So if you allow C3 and Busmaster, you will get into some > serious truble and loose data. > |
From: Janosch M. <sc...@tz...> - 2005-12-12 00:33:16
|
Marco Calviani wrote: > Hi acpi-devel list, > I have a problem regarding C3 states and usb. When i'm plugging in a= ny > usb devices, the my busmaster activity starts couting preventing the > cpu to go to C3 state. Obviously if i unload all usb-related modules, > C3 state goes in, my battery lives longer and the laptop stays quiter; > unfortunately i need an usb-mouse (and possibly also an external USB dr= ive. > I've read somewhere that this is a specific ACPI standard behaviuor > but i'm asking if this can be modified in some way, i.d. is it > possible, with some workarounds, to enter C3 state also with the usb > modules? No this is not Possibe. In C3 the processor disables his cache. If you=20 have busmaster activity, there are direct writes into the cache (if I=20 remeber right). So if you allow C3 and Busmaster, you will get into some=20 serious truble and loose data. >=20 > PS: i'm using a Travelmate 8005 laptop with a 1.8GHz dothan centrino > and debian sid. i'm running kernel 2.6.12.6 >=20 > Thank you very much for your interest, > Marco Calviani >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log = files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=CCk > _______________________________________________ > Acpi-devel mailing list > Acp...@li... > https://lists.sourceforge.net/lists/listinfo/acpi-devel |
From: Alan C. <al...@lx...> - 2005-12-11 23:37:45
|
On Gwe, 2005-12-09 at 21:41 -0500, Jeff Garzik wrote: > Do you even know if this special case is applicable outside of Dell ICH5 > boxes? And I thought your previous messages were referring to ICH6? Some older thinkpads seem to support this. Also some laptops generate pnpbios changes. The different methods alone argue for a generic interface h |
From: Sebastian H. <ac...@ko...> - 2005-12-11 21:59:55
|
hello Martin... * martin <ma...@kn...> [2005-12-11 20:54 +0100]: > Does the absence of a patch against kernel 2.6.14 in the download=20 > section mean that the patch is already in the kernel or that this kernel= =20 > is not supported? 2.6.14 ships with a very recent version of ACPI and there is no official patch of the latest code for that kernel. if you are interested in backporting, the power of git is at your fingertips... cheers, Sebastian --=20 _ ascii ribbon campaign .oOo. GCSd-s:+aC++ULB+++W++M+PS+++Y+ ( ) X Es ist mein fester Glauben, dass es falsch ist, einen festen / \ Glauben zu haben. |
From: Ronald W. <ron...@gm...> - 2005-12-11 21:29:33
|
Dear all, when I try setting the alarm to wake up my pc I get the following result: [root@mithrandir acpi]# pwd /proc/acpi [root@mithrandir acpi]# cat alarm 2005-12-00 00:00:00 [root@mithrandir acpi]# echo 2005-12-15 17:18:19 > alarm [root@mithrandir acpi]# cat alarm 2005-12-00 17:18:19 [root@mithrandir acpi]# BTW, nothing happens at the echo'd date/time. Could someone please give me = a clue where to start looking? I'm running fedora core 4, my mobo is an ASUS P5S800-VM, the documentation on the motherboard states that ACPI is supported. There is an option to turn acpi 2.0 on, but no difference... Any help is greatly appreciated! Regards, Ronald |
From: Marco C. <mar...@gm...> - 2005-12-11 20:10:57
|
Hi acpi-devel list, I have a problem regarding C3 states and usb. When i'm plugging in any usb devices, the my busmaster activity starts couting preventing the cpu to go to C3 state. Obviously if i unload all usb-related modules, C3 state goes in, my battery lives longer and the laptop stays quiter; unfortunately i need an usb-mouse (and possibly also an external USB drive. I've read somewhere that this is a specific ACPI standard behaviuor but i'm asking if this can be modified in some way, i.d. is it possible, with some workarounds, to enter C3 state also with the usb modules? PS: i'm using a Travelmate 8005 laptop with a 1.8GHz dothan centrino and debian sid. i'm running kernel 2.6.12.6 Thank you very much for your interest, Marco Calviani |
From: martin <ma...@kn...> - 2005-12-11 19:45:25
|
Hi, Sorry for a probably stupid question - this is all too new for me: Does the absence of a patch against kernel 2.6.14 in the download section mean that the patch is already in the kernel or that this kernel is not supported? Thanks in advance, Martin |
From: Kelly <uiq...@ne...> - 2005-12-11 16:09:50
|
A Must Watch ALERT Monday Dec 12th Cash Now Corporation, Symbol: CHNW Price: .23 Up 0.14 (127.27%) on Thursday Dec 8th alone Active (strong) Volume Has Been Pretty Good. PR Program This Weekend Apprising Potential Investors of This One. A new PR campiagn will start Thursday. Get in before this starts for the best gains News Great news just released. This should really start to move! The News 1) Payday Loan and Check-Cashing Leader Cash Now Offering Financing on Premium Autos for Those With Credit Challenges Market Wire (Thu, Dec 8) 2)Payday Loan Leader Cash Now Re-Launches Infomercials, Fueling Expansion of Licensees and Further Organic Growth Market Wire (Wed 10:00am) 3) Payday Loan Leader Cash Now Strengthens Infrastructure to Handle Increase in Business -- 'Scaling for the Future' Market Wire (Wed 10:00am) DiscI_imer: Statements regarding fi_ancial matters in this pr_ss re1ease other than historical facts are ``f0rw_rd-lO0king statements'' within the meaning of se(tion 27 A of the S_curities A(t of 193 3, Se(tion 21 E of the Se(urities Ex(hange A(t of 1934, and as that term is defined in the Pr_vate Se(urities Litig_tion Ref orm A(t of 1995. The (ompany intends that such statements about the (ompany's future expe(tations, in(luding future revenues and e_rnings, and all other f0rward-l0Oking statements, be subje(t to the safe har bors created thereby. Since these statements (future ope rational results and s ales) involve ri sks and un(ertainties and are subject to (hange at any time, the (ompany's actu al re sults may differ materi ally from ex pected results. |
From: Olaf C. <oo...@gm...> - 2005-12-11 12:05:27
|
On 12/8/05, Pavel Machek <pa...@uc...> wrote: > Olaf Conradi wrote: > > But, for some reason, the trip points get reset every now and then > > (usually within 30 mintes or so, don't know the exact interval). > > > > Does anyone know what causes the trip point setting to be reset? > > BIOS does it from time to time to provide hysteresis. Patch to > optionaly make trip points read-only w.r.t. BIOS would be welcome. I've been looking at the acpi spec but to me it's not clear how a user can give their thermal management preferences. Should it be through Set Cooling Policy (SCP) only? Is a user still allowed to fiddle with trip points, or is it for plugin devices only. The spec says SCP is optional (and my DSDT has a very limited implementation, it just stores the preference and does not act on it). Looking at the disassembled AML it shouldn't be too hard to implement it. Is /proc/acpi/thermal_zone/THRM/cooling_mode the interface to set SCP? Cheers, -Olaf |
From: Ron A. <ron...@ne...> - 2005-12-11 09:35:41
|
Hi, I own a Uniwill 255II3, and occasionally my system thinks the battery is almost empty (XP has the same problem on this laptop BTW). Looking at the syslog I get about every minute: Dec 11 09:51:05 raarts-ttec kernel: ACPI-0412: *** Error: Handler for [EmbeddedControl] returned AE_TIME Dec 11 09:51:05 raarts-ttec kernel: ACPI-0508: *** Error: Method execution failed [\_SB_.PCI0.BAT0._BST] (Node c145c9e0), AE_TIME I found out about DSDT's, and determined that mine must contain errors, I need to fix it, and boot my system with the fixed table. I dumped my current DSDT, decompiled mine using iasl and looked at it. This is where I am now. I have looked at the ACPI spec, and this spec is 631 pages. Do I have to learn this language to fix the fact that my system occasionally thinks it has an empty battery? Maybe someone can give me a hint on how to handle it? I made it available here: http://www.netland.nl/download/dsdt.dsl (temporary link). Another question (sorry): I also own some Apple iBooks. When I close the lid, they go into a state where the laptop only preserves its RAM image, and when I open the lid the system is back within 3 seconds. An iBook can stay this way for a week, before the battery wears out. Can I get this to work on this Uniwill laptop with Intel Pentium M processor and 82852/82855 GM/GME/PM/GMV chipset? Will it last just as long as the iBook? I am disappointed by the fact that these Intel laptops continuously spin up their cooling fan, this is very annoying. People I talk to seem to take this for granted, but The iBooks I have used to far were totally quiet, and the fan almost never needed to kick in. So I am trying every trick in the book to let it run cooler. Thanks, Ron Arts |
From: Goldsmith <ogt...@ha...> - 2005-12-11 00:36:30
|
A Must Watch ALERT Monday Dec 12th Cash Now Corporation, Symbol: CHNW Price: .23 Up 0.14 (127.27%) on Thursday Dec 8th alone Active (strong) Volume Has Been Pretty Good. PR Program This Weekend Apprising Potential Investors of This One. A new PR campiagn will start Thursday. Get in before this starts for the best gains News Great news just released. This should really start to move! The News 1) Payday Loan and Check-Cashing Leader Cash Now Offering Financing on Premium Autos for Those With Credit Challenges Market Wire (Thu, Dec 8) 2)Payday Loan Leader Cash Now Re-Launches Infomercials, Fueling Expansion of Licensees and Further Organic Growth Market Wire (Wed 10:00am) 3) Payday Loan Leader Cash Now Strengthens Infrastructure to Handle Increase in Business -- 'Scaling for the Future' Market Wire (Wed 10:00am) DiscI_imer: Statements regarding fi_ancial matters in this pr_ss re1ease other than historical facts are ``f0rw_rd-lO0king statements'' within the meaning of se(tion 27 A of the S_curities A(t of 193 3, Se(tion 21 E of the Se(urities Ex(hange A(t of 1934, and as that term is defined in the Pr_vate Se(urities Litig_tion Ref orm A(t of 1995. The (ompany intends that such statements about the (ompany's future expe(tations, in(luding future revenues and e_rnings, and all other f0rward-l0Oking statements, be subje(t to the safe har bors created thereby. Since these statements (future ope rational results and s ales) involve ri sks and un(ertainties and are subject to (hange at any time, the (ompany's actu al re sults may differ materi ally from ex pected results. |
From: <mr...@in...> - 2005-12-11 00:35:13
|
Andrew Morton <ak...@os...> writes: > You may need to raise a bug at bugzilla.kernel.org (against ACPI) for thi= s. Done. > Please mention that nocst isn't documented in > Documentation/kernel-parameters.txt, too. Did that too. --=20 M=E5ns Rullg=E5rd mr...@in... |
From: Andrew M. <ak...@os...> - 2005-12-10 23:54:50
|
You may need to raise a bug at bugzilla.kernel.org (against ACPI) for this. Please mention that nocst isn't documented in Documentation/kernel-parameters.txt, too. Begin forwarded message: Date: Mon, 05 Dec 2005 22:30:20 +0000 From: M=E5ns Rullg=E5rd <mr...@in...> To: lin...@vg... Subject: 2.6.11 and later freeze without processor.nocst=3D1 Kernel versions 2.6.11 and later refuse to boot on my Asus P4V8X-X board without the processor.nocst=3D1 option on the kernel command line. Earlier versions work without any issues. Is there any information I can supply to help fix this? The kernel log from booting looks like this: Linux version 2.6.14 (root@agrajag) (gcc version 3.3.6 (Gentoo 3.3.6, ssp-3= .3.6-1.0, pie-8.7.8)) #2 PREEMPT Sat Dec 3 18:59:29 GMT 2005 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000001ff30000 (usable) BIOS-e820: 000000001ff30000 - 000000001ff40000 (ACPI data) BIOS-e820: 000000001ff40000 - 000000001fff0000 (ACPI NVS) BIOS-e820: 000000001fff0000 - 0000000020000000 (reserved) BIOS-e820: 00000000ff7c0000 - 0000000100000000 (reserved) 511MB LOWMEM available. found SMP MP-table at 000ff780 On node 0 totalpages: 130864 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 126768 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 DMI 2.3 present. ACPI: RSDP (v002 ACPIAM ) @ 0x000fa3a0 ACPI: XSDT (v001 A M I OEMXSDT 0x05000418 MSFT 0x00000097) @ 0x1ff30100 ACPI: FADT (v003 A M I OEMFACP 0x05000418 MSFT 0x00000097) @ 0x1ff30290 ACPI: MADT (v001 A M I OEMAPIC 0x05000418 MSFT 0x00000097) @ 0x1ff30390 ACPI: OEMB (v001 A M I AMI_OEM 0x05000418 MSFT 0x00000097) @ 0x1ff40040 ACPI: DSDT (v001 A0017 A0017001 0x00000001 INTL 0x02002026) @ 0x00000000 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:3 APIC version 20 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x81] disabled) ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 1, version 3, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 30000000 (gap: 20000000:df7c0000) Built 1 zonelists Kernel command line: root=3D/dev/md0 acpi_irq_balance console=3Duart,io,0x3= f8,38400n8 processor.nocst=3D1 mapped APIC to ffffd000 (fee00000) mapped IOAPIC to ffffc000 (fec00000) Initializing CPU#0 CPU 0 irqstacks, hard=3Dc03a5000 soft=3Dc03a4000 PID hash table entries: 2048 (order: 11, 32768 bytes) Detected 2400.463 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Early serial console at I/O port 0x3f8 (options '38400n8') Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 515012k/523456k available (1956k kernel code, 7884k reserved, 568k = data, 152k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4812.32 BogoMIPS (lpj=3D96= 24645) Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 0000= 441d 00000000 00000000 CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000 00004= 41d 00000000 00000000 monitor/mwait feature present. using mwait in idle threads. CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 256K CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080 0000441d 00= 000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU0: Intel P4/Xeon Extended MCE MSRs (12) available CPU0: Thermal monitoring enabled mtrr: v2.0 (20020519) CPU: Intel(R) Celeron(R) CPU 2.40GHz stepping 04 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. ENABLING IO-APIC IRQs ..TIMER: vector=3D0x31 pin1=3D2 pin2=3D-1 softlockup thread 0 started up. NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=3D1 PCI: Using configuration type 1 ACPI: Subsystem revision 20050902 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) Boot video device is 0000:01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 *11 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *10 11 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 7 10 11 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10 11 14 15) *0, disabled. SCSI subsystem initialized PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=3Drouteirq". If it helps, post a r= eport PCI: Bridge: 0000:00:01.0 IO window: disabled. MEM window: de700000-dfafffff PREFETCH window: da600000-de5fffff PCI: Setting latency timer of device 0000:00:01.0 to 64 Machine check exception polling timer started. SGI XFS with ACLs, no debug enabled Initializing Cryptographic API PCI: Bypassing VIA 8237 APIC De-Assert Message ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB] ACPI: Sleep Button (CM) [SLPB] **** Freeze here without nocst=3D1 **** ACPI: CPU0 (power states: C1[C1]) ACPI: Processor [CPU1] (supports 16 throttling states) serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq =3D 4) is a 16550A mice: PS/2 mouse device common for all mice io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered libata version 1.12 loaded. sata_via version 1.1 ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 16 PCI: Via IRQ fixup for 0000:00:0f.0, from 10 to 0 sata_via(0000:00:0f.0): routed to hard irq line 0 --=20 M=E5ns Rullg=E5rd mr...@in... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to maj...@vg... More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |