Invalid PBLK length

Invalid PBLK length

[Jens Haug]

Hi,

I'm trying to find out why C2/C3 and throttling is not supported 
on my Asus L2000D (aka Medion 9688).

In dmesg, acpi tells me about an invalid PBLK length of 5 and
an unsupoprted address space of 127.

Ok, I can see in the code (processor.c) that in the function
acpi_processor_get_inf the value of object.processor.pblk_lenght
is checked, and in case it's smaller than 6 this error is thrown.
If it's 6 or greater, then addresses for C2 and C3 are assigned.
But why can't PBLK be 5 and only C2 be used? Couldn't we just 
disable C3 and still assign the address for C2 as pblk_address+4?
I think it was done that way in prpower.c Revision 32. That gave
me a working C2.  
BTW, how can I make my FADT human readable? It isn't shown by 
acpidmp, and I'd like to be able to check some values myself.

I also see in dmesg that there's an unsupported address space
of 127 in acpi_processor_get_performance_control because
reg->space_id != ACPI_ADR_SPACE_SYSTEM_IO. But I don't know
enough C to understand where this comes from. Could somebody
please give me a hint?

TIA


Jens

-- 
Jens Haug
IKFF Universität Stuttgart              Tel. 0711/685-6422
Pfaffenwaldring 9                       Fax  0711/685-6356
70550 Stuttgart	                haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.org



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

Re: Invalid PBLK length

[Matthew Wilcox]

On Wed, Dec 18, 2002 at 02:26:05PM +0100, Jens Haug wrote:
> I'm trying to find out why C2/C3 and throttling is not supported 
> on my Asus L2000D (aka Medion 9688).
> 
> In dmesg, acpi tells me about an invalid PBLK length of 5 and
> an unsupoprted address space of 127.

That's two ...
http://sourceforge.net/mailarchive/message.php?msg_id=2138093
OK, the other one's an ASUS too, but seems to be a different model (S1300A).

> BTW, how can I make my FADT human readable? It isn't shown by 
> acpidmp, and I'd like to be able to check some values myself.

Use the iasl compiler/decompiler.

BTW, Andy, any chance the precompiled one could be compiled against glibc
2.2 instead of 2.3?  Not everybody likes to be quite so bleeding-edge ;-)

> I also see in dmesg that there's an unsupported address space
> of 127 in acpi_processor_get_performance_control because
> reg->space_id != ACPI_ADR_SPACE_SYSTEM_IO. But I don't know
> enough C to understand where this comes from. Could somebody
> please give me a hint?

ACPI tells you which address space a given address is in:

#define ACPI_ADR_SPACE_SYSTEM_MEMORY    (ACPI_ADR_SPACE_TYPE) 0
#define ACPI_ADR_SPACE_SYSTEM_IO        (ACPI_ADR_SPACE_TYPE) 1
#define ACPI_ADR_SPACE_PCI_CONFIG       (ACPI_ADR_SPACE_TYPE) 2
#define ACPI_ADR_SPACE_EC               (ACPI_ADR_SPACE_TYPE) 3
#define ACPI_ADR_SPACE_SMBUS            (ACPI_ADR_SPACE_TYPE) 4
#define ACPI_ADR_SPACE_CMOS             (ACPI_ADR_SPACE_TYPE) 5
#define ACPI_ADR_SPACE_PCI_BAR_TARGET   (ACPI_ADR_SPACE_TYPE) 6
#define ACPI_ADR_SPACE_DATA_TABLE       (ACPI_ADR_SPACE_TYPE) 7

processor.c is telling you it only handles ioport (inb/outb) address
spaces.  But 127 is not a valid address space value, so you're going
to have to get an updated BIOS from your vendor.  There's really no
reasonable way to fix this.

On the other hand, I do think it's worth incorporating my suggestion
to fill in C2 if we have it.  Maybe under the CONFIG_ACPI_BROKEN_AML or
whatever it was going to be called.

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

Re: Invalid PBLK length

[Adachi, Kenichi]

I didn't check code, but if that said address space type 127 does mean "Functi
onal Fixed Hardware (0x7F)", then your processor expects that OS processor dri
ver knows the specific address to control voltage scaling state transition. Us
ually it's done by accessing MSRs. This has been true for AMD PowerNow! and Tr
ansmeta LongRun, and Intel's new Geyserville I/F which will be unveiled on Ban
ias in the near future. These are mostly under NDA, therefore I can't be speci
fic, however there're several public documents which explain this stuff a bit 
more.

So if my guess is correct, your BIOS is not bad. To enable processor performan
ce control on your machine, Linux needs inputs from CPU vendors. 

> 
> > I also see in dmesg that there's an unsupported address space
> > of 127 in acpi_processor_get_performance_control because
> > reg->space_id != ACPI_ADR_SPACE_SYSTEM_IO. But I don't know
> > enough C to understand where this comes from. Could somebody
> > please give me a hint?
> 
> ACPI tells you which address space a given address is in:
> 
> #define ACPI_ADR_SPACE_SYSTEM_MEMORY    (ACPI_ADR_SPACE_TYPE) 0
> #define ACPI_ADR_SPACE_SYSTEM_IO        (ACPI_ADR_SPACE_TYPE) 1
> #define ACPI_ADR_SPACE_PCI_CONFIG       (ACPI_ADR_SPACE_TYPE) 2
> #define ACPI_ADR_SPACE_EC               (ACPI_ADR_SPACE_TYPE) 3
> #define ACPI_ADR_SPACE_SMBUS            (ACPI_ADR_SPACE_TYPE) 4
> #define ACPI_ADR_SPACE_CMOS             (ACPI_ADR_SPACE_TYPE) 5
> #define ACPI_ADR_SPACE_PCI_BAR_TARGET   (ACPI_ADR_SPACE_TYPE) 6
> #define ACPI_ADR_SPACE_DATA_TABLE       (ACPI_ADR_SPACE_TYPE) 7
> 
> processor.c is telling you it only handles ioport (inb/outb) address
> spaces.  But 127 is not a valid address space value, so you're going
> to have to get an updated BIOS from your vendor.  There's really no
> reasonable way to fix this.
> 


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

Re: Invalid PBLK length

[Matthew Wilcox]

On Thu, Dec 19, 2002 at 12:17:40AM +0900, Adachi, Kenichi wrote:
> I didn't check code, but if that said address space type 127 does mean "Functi
> onal Fixed Hardware (0x7F)", then your processor expects that OS processor dri
> ver knows the specific address to control voltage scaling state transition. Us
> ually it's done by accessing MSRs. This has been true for AMD PowerNow! and Tr
> ansmeta LongRun, and Intel's new Geyserville I/F which will be unveiled on Ban
> ias in the near future. These are mostly under NDA, therefore I can't be speci
> fic, however there're several public documents which explain this stuff a bit 
> more.

you're right.  Andy, could we add something like this?

diff -u -p -r1.6 actypes.h
--- drivers/acpi/include/actypes.h      10 Dec 2002 22:02:09 -0000      1.6
+++ drivers/acpi/include/actypes.h      18 Dec 2002 15:28:47 -0000
@@ -579,6 +579,7 @@ typedef u8                              
 #define ACPI_ADR_SPACE_CMOS             (ACPI_ADR_SPACE_TYPE) 5
 #define ACPI_ADR_SPACE_PCI_BAR_TARGET   (ACPI_ADR_SPACE_TYPE) 6
 #define ACPI_ADR_SPACE_DATA_TABLE       (ACPI_ADR_SPACE_TYPE) 7
+#define ACPI_ADR_SPACE_FIXED_HARDWARE  (ACPI_ADR_SPACE_TYPE) 127
 
 
 /*


-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

Re: Invalid PBLK length

[Adachi, Kenichi]

I didn't check code, but if that said address space type 127 does mean "Functi
onal Fixed Hardware (0x7F)", then your processor expects that OS processor dri
ver knows the specific address to control performance state transition. In thi
s context, FFHardware is usually MSR. This has been true for AMD PowerNow! and
 Transmeta LongRun, and Intel's new Geyserville I/F which will be unveiled on 
Banias in the near future. These are mostly under NDA, therefore I can't be sp
ecific, however there're several public documents which explain this stuff a b
it more.

So if my guess is correct, your BIOS is not bad. To enable processor performan
ce state control on your machine, Linux needs inputs from CPU vendors. 

> 
> > I also see in dmesg that there's an unsupported address space
> > of 127 in acpi_processor_get_performance_control because
> > reg->space_id != ACPI_ADR_SPACE_SYSTEM_IO. But I don't know
> > enough C to understand where this comes from. Could somebody
> > please give me a hint?
> 
> ACPI tells you which address space a given address is in:
> 
> #define ACPI_ADR_SPACE_SYSTEM_MEMORY    (ACPI_ADR_SPACE_TYPE) 0
> #define ACPI_ADR_SPACE_SYSTEM_IO        (ACPI_ADR_SPACE_TYPE) 1
> #define ACPI_ADR_SPACE_PCI_CONFIG       (ACPI_ADR_SPACE_TYPE) 2
> #define ACPI_ADR_SPACE_EC               (ACPI_ADR_SPACE_TYPE) 3
> #define ACPI_ADR_SPACE_SMBUS            (ACPI_ADR_SPACE_TYPE) 4
> #define ACPI_ADR_SPACE_CMOS             (ACPI_ADR_SPACE_TYPE) 5
> #define ACPI_ADR_SPACE_PCI_BAR_TARGET   (ACPI_ADR_SPACE_TYPE) 6
> #define ACPI_ADR_SPACE_DATA_TABLE       (ACPI_ADR_SPACE_TYPE) 7
> 
> processor.c is telling you it only handles ioport (inb/outb) address
> spaces.  But 127 is not a valid address space value, so you're going
> to have to get an updated BIOS from your vendor.  There's really no
> reasonable way to fix this.
> 


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

Re: Invalid PBLK length

[Jens Haug]

> > Ok, I can see in the code (processor.c) that in the function
> > acpi_processor_get_inf the value of object.processor.pblk_lenght
> > is checked, and in case it's smaller than 6 this error is thrown.
> > If it's 6 or greater, then addresses for C2 and C3 are assigned.
> > But why can't PBLK be 5 and only C2 be used? Couldn't we just 
> > disable C3 and still assign the address for C2 as pblk_address+4?
> > I think it was done that way in prpower.c Revision 32. That gave
> > me a working C2.  
> 
> Well, specs issue?

Yes, I see. I hadn't found that, but Matthew pointed me to the
right chapter of the specs.

> > BTW, how can I make my FADT human readable? It isn't shown by 
> > acpidmp, and I'd like to be able to check some values myself.
> 
> ./acpidmp FACS | ./acpitbl
> 
> Note that it is FACS (the signature of the table), not FADT (I don't know
> why the sig. and the name of this table are not the same).

But this FACS doesn't give me much information (since it's only
the signature, I guess).
It sais:

Signature:		FACS
Length:			64
Hardware Signature:	0x00000000
Firmware Waking Vector: 0x00000000
Global Lock:		0x00000000
Flags:			0x00000000

I'm curious what I'll find in the FADT. I mean, 5 clearly is 
neither 0 nor 6, so there might be some other really heavy bugs.
I'll get me the 


Jens

-- 
Jens Haug
IKFF Universität Stuttgart              Tel. 0711/685-6422
Pfaffenwaldring 9                       Fax  0711/685-6356
70550 Stuttgart	                haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.org



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

Re: Invalid PBLK length

[Ducrot Bruno]

On Wed, Dec 18, 2002 at 04:36:36PM +0100, Jens Haug wrote:

> > Note that it is FACS (the signature of the table), not FADT (I don't know
> > why the sig. and the name of this table are not the same).
> 
> But this FACS doesn't give me much information (since it's only
> the signature, I guess).
> It sais:
> 
> Signature:		FACS
> Length:			64
> Hardware Signature:	0x00000000
> Firmware Waking Vector: 0x00000000
> Global Lock:		0x00000000
> Flags:			0x00000000
> 

Ouch!  Sorry.  FACP is the signature of FADT in fact.
FACS is the sig. of the FACS table, which contains the global lock and
other things.

./acpidmp FACP | ./acpitbl

Should give something like:

Signature:        FACP
Length:           116
Revision:         0x01
Checksum:         0x48
OEMID:            TOSCPL
OEM Table ID:     888M1
OEM Revision:     0x06040001
Creator ID:       PTL
Creator Revision: 0x00000001
FIRMWARE_CTRL:    0x0fefffc0
DSDT:             0x0fefa060
INT_MODEL:        0x00
SCI_INT:          9
SMI_CMD:          0x000000b2
ACPI_ENABLE:      0xf0
ACPI_DISABLE:     0xf1
S4BIOS_REQ:       0xf2
PM1a_EVT_BLK:     0x00001000
PM1b_EVT_BLK:     0x00000000
PM1a_CNT_BLK:     0x00001004
PM1b_CNT_BLK:     0x00000000
PM2_CNT_BLK:      0x00001020
PM_TMR_BLK:       0x00001008
GPE0_BLK:         0x00001028
GPE1_BLK:         0x0000102c
PM1_EVT_LEN:      4
PM1_CNT_LEN:      2
PM2_CNT_LEN:      1
PM_TM_LEN:        4
GPE0_BLK_LEN:     4
GPE1_BLK_LEN:     4
GPE1_BASE:        16
P_LVL2_LAT:       10
P_LVL3_LAT:       1001
FLUSH_SIZE:       0
FLUSH_STRIDE:     0
DUTY_OFFSET:      1
DUTY_WIDTH:       3
DAY_ALRM:         0x0d
MON_ALRM:         0x08
CENTURY:          0x32
Flags:            0x00000025


You can, as an alternative, give something like that:

cat /proc/acpi/fadt | ./acpitbl 


Cheers,

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
This SF.NET email is sponsored by: Order your Holiday Geek Presents Now!
Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap,
MP3 Players,  XBox Games,  Flying Saucers,  WebCams,  Smart Putty.
T H I N K G E E K . C O M       http://www.thinkgeek.com/sf/

Re: Invalid PBLK length

[Jens Haug]

> I didn't check code, but if that said address space type 127 does mean "Functi
> onal Fixed Hardware (0x7F)", then your processor expects that OS processor dri
> ver knows the specific address to control voltage scaling state transition. Us
> ually it's done by accessing MSRs. This has been true for AMD PowerNow! and Tr
> ansmeta LongRun, and Intel's new Geyserville I/F which will be unveiled on Ban
> ias in the near future. These are mostly under NDA, therefore I can't be speci
> fic, however there're several public documents which explain this stuff a bit 
> more.
> 
> So if my guess is correct, your BIOS is not bad. To enable processor performan
> ce control on your machine, Linux needs inputs from CPU vendors. 

My processor is an AMD Mobile Athlon, so it has AMD PowerNow! 
technology. I don't know much about this stuff, but your guess
sounds very reasonable to me.
What's the right way to make this work? Read the AMD specs or
push AMD to release more specs?


Jens

-- 
Jens Haug
IKFF Universität Stuttgart              Tel. 0711/685-6422
Pfaffenwaldring 9                       Fax  0711/685-6356
70550 Stuttgart	                haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.org



-------------------------------------------------------
This SF.NET email is sponsored by: Order your Holiday Geek Presents Now!
Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap,
MP3 Players,  XBox Games,  Flying Saucers,  WebCams,  Smart Putty.
T H I N K G E E K . C O M       http://www.thinkgeek.com/sf/

RE: Invalid PBLK length

[Grover, Andrew]

> From: Matthew Wilcox [mailto:willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org] 
> you're right.  Andy, could we add something like this?
> +#define ACPI_ADR_SPACE_FIXED_HARDWARE  (ACPI_ADR_SPACE_TYPE) 127

Yes, thanks.

Regards -- Andy

PS about the iasl glibc thing - you do know you can compile your own from
the acpica-unix source release, right?


-------------------------------------------------------
This SF.NET email is sponsored by: Order your Holiday Geek Presents Now!
Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap,
MP3 Players,  XBox Games,  Flying Saucers,  WebCams,  Smart Putty.
T H I N K G E E K . C O M       http://www.thinkgeek.com/sf/

Re: Invalid PBLK length

[Jens Haug]

> Ouch!  Sorry.  FACP is the signature of FADT in fact.
> FACS is the sig. of the FACS table, which contains the global lock and
> other things.

Ok, I see.

> ./acpidmp FACP | ./acpitbl
> 
> Should give something like:
(...)
> OEMID:            TOSCPL
> OEM Table ID:     888M1

This is ASUS and L2000D for me.

> S4BIOS_REQ:       0xf2

This is 0x00 for me. I had checked that before (when you
wrote about s4bios the last time).

> PM1a_EVT_BLK:     0x00001000

0x0000e400.
Now I only have to find out what that means. Guess I'll have
to read some specs.

> PM1b_EVT_BLK:     0x00000000

Same here.

> PM1a_CNT_BLK:     0x00001004

0x0000e404.

> PM1b_CNT_BLK:     0x00000000

Same here.

> PM2_CNT_BLK:      0x00001020

0x00000000.

> PM_TMR_BLK:       0x00001008

0x0000e408.

> GPE0_BLK:         0x00001028

0x0000e420

> GPE1_BLK:         0x0000102c

0x0000e430.

> PM1_EVT_LEN:      4
> PM1_CNT_LEN:      2

Same here.

> PM2_CNT_LEN:      1

0.

> PM_TM_LEN:        4
> GPE0_BLK_LEN:     4
> GPE1_BLK_LEN:     4
> GPE1_BASE:        16

Same here.

> P_LVL2_LAT:       10

Is this the latency for C2? This is 90 for me.

> P_LVL3_LAT:       1001

1900.

> FLUSH_SIZE:       0
> FLUSH_STRIDE:     0
> DUTY_OFFSET:      1
> DUTY_WIDTH:       3
> DAY_ALRM:         0x0d

Same.

> MON_ALRM:         0x08
> CENTURY:          0x32

Both 0x00.

> Flags:            0x00000025

0x000000a6.


I'll look this up in the specs and see what I can learn. Well,
at least I'm gonna try to find this in the specs. 


Jens

-- 
Jens Haug
IKFF Universität Stuttgart              Tel. 0711/685-6422
Pfaffenwaldring 9                       Fax  0711/685-6356
70550 Stuttgart	                haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.org



-------------------------------------------------------
This SF.NET email is sponsored by: Order your Holiday Geek Presents Now!
Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap,
MP3 Players,  XBox Games,  Flying Saucers,  WebCams,  Smart Putty.
T H I N K G E E K . C O M       http://www.thinkgeek.com/sf/

Invalid PBLK length

[Axel Müller]

Hello,
I have installed the acpi-20021212 Patch on my Asus L2400D Laptop with a 
2.4.20 Kernel (AMD Athlon XP mobile, SiS chipset, latest Bios version from 
Asus).
First the good things:
- I can monitor battery and temperature status
- I get acpi events with acpid (powerbutton, ac_adapter)
- I can send the laptop sleeping with echo 1 > /proc/acpi/sleep, but the 
processor does not really awake after pressing a key; the performance is 
quit sluggish

bad things:
- no processor throttling
- only CPU state C1
I think this is caused by the Invalid PBLK length (Invalid PBLK length [5])
reported in /var/log/dmesg. I think this issue was discussed in this list 
before, but I did not see any conclusions/solutions. Therefore the CPU is 
always in the most power consuming mode and the fan runs the most time as 
the temperature is above 70°C. However, I installed then athcool from 
http://members.jcom.home.ne.jp/jacobi/linux/softwares.html
to disconnect the Northbridge when STPGNT is detected. To my surprise it 
worked. Temperature is decreased to 60°C and power consumption decreases so 
I can use the laptop more than 1 hour (I thought that STPGNT is only send 
when processor is in C2 state, but concerning acpi output this is not 
supported).
How can I get rid of this Invalid PBLK message and how can I use the sleep 
mode?

  Axel

--
Dipl.Phys. Axel Müller (axel.mueller-qenKrGB1/YlH8HOlP0F5JqhivhuVJJ3m@public.gmane.org)
Institut für Werkstoffe der Elektrotechnik IWE
Universität Karlsruhe
Tel. 0721/608-7569   Fax  0721/608-7492
http://www.iwe.uni-karlsruhe.de



-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en

Re: Invalid PBLK length

[Jens Haug]

> I have installed the acpi-20021212 Patch on my Asus L2400D Laptop with a 
> 2.4.20 Kernel (AMD Athlon XP mobile, SiS chipset, latest Bios version from 
> Asus).
> First the good things:
> - I can monitor battery and temperature status
> - I get acpi events with acpid (powerbutton, ac_adapter)
> - I can send the laptop sleeping with echo 1 > /proc/acpi/sleep, but the 
> processor does not really awake after pressing a key; the performance is 
> quit sluggish
> 
> bad things:
> - no processor throttling
> - only CPU state C1
> I think this is caused by the Invalid PBLK length (Invalid PBLK length [5])
> reported in /var/log/dmesg. I think this issue was discussed in this list 
> before, but I did not see any conclusions/solutions. 

Short term dirty hack:
http://sourceforge.net/mailarchive/message.php?msg_id=2138093
Long term solution:
Add a feature to ACPI (like CONFIG_ACPI_BROKEN_AML) which will make
the kernel complain about a buggy BIOS but at the same time offer
some workarounds. This goes towards bug to bug compatibility with M$.
I think this is planned already, but development for this hasn't
started yet.

> Therefore the CPU is 
> always in the most power consuming mode and the fan runs the most time as 
> the temperature is above 70°C. However, I installed then athcool from 
> http://members.jcom.home.ne.jp/jacobi/linux/softwares.html
> to disconnect the Northbridge when STPGNT is detected. To my surprise it 
> worked. 

I'm really surprised, too. I have the little brother of your notebook
(the L2000D, see my page http://mitglied.lycos.de/chamo3/md9688.html),
and tried something similar called VCool which didn't work. :-/

> How can I get rid of this Invalid PBLK message and how can I use the sleep 
> mode?

I have no idea why S1 doesn't work for you - I have the same hardware
and it always worked (with every version of ACPI).
Maybe it's a question of video driver or kernel setup? We can check
these non-acpi issues in private mail if you want to.


Jens

-- 
Jens Haug
IKFF Universität Stuttgart              Tel. 0711/685-6422
Pfaffenwaldring 9                       Fax  0711/685-6356
70550 Stuttgart	                haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.org



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

RE: Invalid PBLK length

[Grover, Andrew]

> From: Axel Müller [mailto:axel.mueller-qenKrGB1/YlH8HOlP0F5JqhivhuVJJ3m@public.gmane.org] 
> I think this is caused by the Invalid PBLK length (Invalid 
> PBLK length [5])
> reported in /var/log/dmesg. I think this issue was discussed 
> in this list 
> before, but I did not see any conclusions/solutions. 
> Therefore the CPU is 
> always in the most power consuming mode and the fan runs the 
> most time as 
> the temperature is above 70°C. However, I installed then athcool from 
> http://members.jcom.home.ne.jp/jacobi/linux/softwares.html
> to disconnect the Northbridge when STPGNT is detected. To my 

Hmmm. Sigh. Ok, we'll try relaxing the PBLK length thing, and see what
happens.

Regards -- Andy


-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp