Re: [osol-discuss] S10U2 weirdness

2006-07-13 Thread Peter Tribble
On Thu, 2006-07-13 at 01:41, Alan Hargreaves wrote: > Peter, could I possibly get you to log a support call on this so we can > get the appropriate escalation path in place to get a fix done. > > Provide the bug-id, a pointer to this thread on the jive server and note > that a PTS-Kernel Enginee

Re: [osol-discuss] S10U2 weirdness

2006-07-12 Thread Dana H. Myers
Alan Hargreaves wrote: > Peter, could I possibly get you to log a support call on this so we can > get the appropriate escalation path in place to get a fix done. > > Provide the bug-id, a pointer to this thread on the jive server and note > that a PTS-Kernel Engineer (me), specifically asked for

Re: [osol-discuss] S10U2 weirdness

2006-07-12 Thread Alan Hargreaves
Peter, could I possibly get you to log a support call on this so we can get the appropriate escalation path in place to get a fix done. Provide the bug-id, a pointer to this thread on the jive server and note that a PTS-Kernel Engineer (me), specifically asked for this to be escalated. alan.

Re: [osol-discuss] S10U2 weirdness

2006-07-12 Thread Alan Hargreaves
The obvious next question is, is anyone backporting this to the s10 kernel patch? alan. Dana H. Myers wrote: [EMAIL PROTECTED] wrote: BTW: thermal zone handling was introduced in Nevada build 40 as part of: 6363985 acpica: Metropolis SMB Alerts result in high background system load Metropol

Re: [osol-discuss] S10U2 weirdness

2006-07-12 Thread Dana H. Myers
[EMAIL PROTECTED] wrote: > > BTW: thermal zone handling was introduced in Nevada build 40 as part of: > > 6363985 acpica: Metropolis SMB Alerts result in high background system load > > Metropolis, of course, is the W2100z > > > (The "thermal" event can happen in overtemp conditions and some >

Re: [osol-discuss] S10U2 weirdness

2006-07-12 Thread Casper . Dik
BTW: thermal zone handling was introduced in Nevada build 40 as part of: 6363985 acpica: Metropolis SMB Alerts result in high background system load Metropolis, of course, is the W2100z (The "thermal" event can happen in overtemp conditions and some other conditions; if the _TMP method is nev

Re: [osol-discuss] S10U2 weirdness

2006-07-12 Thread Casper . Dik
>Could be. At least, I ran frkit, installed acpidrv, and the problem >vanished. Haven't even rebooted yet. Yes, most probably it then. The driver does attach immediately when it is installed; "batstat -t" will show you the thermal zones configured in the system. If there was a thermal interrupt

Re: [osol-discuss] S10U2 weirdness

2006-07-12 Thread Peter Tribble
On Wed, 2006-07-12 at 09:54, [EMAIL PROTECTED] wrote: > >The only hint from /var/adm/messages is: > > > >Jul 11 16:24:32 platinum unix: [ID 954099 kern.info] NOTICE: IRQ16 is > >being shared by drivers with different interrupt levels. > >Jul 11 16:24:32 platinum This may result in reduced system pe

Re: [osol-discuss] S10U2 weirdness

2006-07-12 Thread Casper . Dik
>The only hint from /var/adm/messages is: > >Jul 11 16:24:32 platinum unix: [ID 954099 kern.info] NOTICE: IRQ16 is >being shared by drivers with different interrupt levels. >Jul 11 16:24:32 platinum This may result in reduced system performance. > >But whether that's relevant is another matter. T

[osol-discuss] S10U2 weirdness

2006-07-12 Thread Peter Tribble
Yesterday I upgraded a W2100z from S10U1 to S10U2. No obvious problems, but some weird behaviour is now cropping up: The machine has a load average of 1 when idle: load averages: 0.87, 0.89, 0.89 89 processes: 87 sleeping, 1 running, 1 on cpu CPU states: 47.5% idle, 0.8% user, 51.7% kernel,