I've been having a lot of problems with my Ultra 133 TX2 controller,
that if I boot my system a just doesn't touch it for a while, the system
suspends to complete standby, even though the ext3 data is committed
every 5 secs. causing disk activity and thus should disallow standby
behaviour (at least that's the way it works on my onboard controller).
This has been a problem for ages and I sinerely thought it had been
fixed in the 2.4.19 kernel, and so it seemed for a while, until it
happened again(guess i had to figure out to trigger it once again)
it seems the best way to spot it is to leave the system alone completely,
after a boot - then just wait for an apm standby event to happen.
Any thoughts on this problem?
Best regards
Thomas
-- Send gratis SMS og brug gratis e-mail p? Everyday.com --
On Thu, 2002-08-15 at 11:21, Thomas Munck Steenholdt wrote:
> I've been having a lot of problems with my Ultra 133 TX2 controller,
> that if I boot my system a just doesn't touch it for a while, the system
> suspends to complete standby, even though the ext3 data is committed
> every 5 secs. causing disk activity and thus should disallow standby
> behaviour (at least that's the way it works on my onboard controller).
Lots of BIOSes are not bright enough to monitor a second IDE controller.
You should be able to frob in the APM/ACPI bios and add its IRQ line to
the monitor list
> On Thu, 2002-08-15 at 11:21, Thomas Munck Steenholdt wrote:
> > I've been having a lot of problems with my Ultra 133 TX2 controller,
> > that if I boot my system a just doesn't touch it for a while, the
> system
> > suspends to complete standby, even though the ext3 data is committed
> > every 5 secs. causing disk activity and thus should disallow standby
> > behaviour (at least that's the way it works on my onboard controller).
>
> Lots of BIOSes are not bright enough to monitor a second IDE controller.
> You should be able to frob in the APM/ACPI bios and add its IRQ line to
> the monitor list
That would be in the BIOS right (or could it be done from linux) ?
Like i mentioned, my system is an IBM, which means tailored for users,
which means that it(this particular system) won't let me add IRQ's to
monitor, at least not from within the BIOS setup.
I can select to monitor "Hard Disks" "Serial Ports" that kind
of granularity... But at least, what you are telling me, suggests to me
that actually this is probably a problem in my BIOS rather than the kernel.
Would apm=off bypass this kind of thing?
-- Send gratis SMS og brug gratis e-mail p? Everyday.com --
On Thu, 2002-08-15 at 12:11, Thomas Munck Steenholdt wrote:
> That would be in the BIOS right (or could it be done from linux) ?
If you know the chipset and the docs are around then its actually
normally very easy to poke from Linux too. Depends on the chipset
> Would apm=off bypass this kind of thing?
It may do yes
> On Thu, 2002-08-15 at 12:11, Thomas Munck Steenholdt wrote:
> > That would be in the BIOS right (or could it be done from linux) ?
>
> If you know the chipset and the docs are around then its actually
> normally very easy to poke from Linux too. Depends on the chipset
>
> > Would apm=off bypass this kind of thing?
>
> It may do yes
>
OK, I'll try the apm=off first to see if that resolves my problem...
are there any examples/places to look if i decided to update the
APM monitor list from linux? Anywhere I could get an idea of how that
could be done?
I don't know the chipset atm.
Thanks
Thomas
-- Send gratis SMS og brug gratis e-mail p? Everyday.com --
> On Thu, 2002-08-15 at 12:11, Thomas Munck Steenholdt wrote:
> > That would be in the BIOS right (or could it be done from linux) ?
>
> If you know the chipset and the docs are around then its actually
> normally very easy to poke from Linux too. Depends on the chipset
>
> > Would apm=off bypass this kind of thing?
>
> It may do yes
>
OK, I'll try the apm=off first to see if that resolves my problem...
are there any examples/places to look if i decided to update the
APM monitor list from linux? Anywhere I could get an idea of how that
could be done?
I don't know the chipset atm.
Thanks
Thomas
-- Send gratis SMS og brug gratis e-mail p? Everyday.com --
On Thu, 2002-08-15 at 13:27, Thomas Munck Steenholdt wrote:
> OK, I'll try the apm=off first to see if that resolves my problem...
> are there any examples/places to look if i decided to update the
> APM monitor list from linux? Anywhere I could get an idea of how that
> could be done?
> I don't know the chipset atm.
lspci will tell you the chipset identifiers. Generally the first few
listed devices are the chipset itself (00:00.0 is the north bridge, then
the other stuff follows).
On Thu, 2002-08-15 at 15:27, Alan Cox wrote:
> On Thu, 2002-08-15 at 13:27, Thomas Munck Steenholdt wrote:
> > OK, I'll try the apm=off first to see if that resolves my problem...
> > are there any examples/places to look if i decided to update the
> > APM monitor list from linux? Anywhere I could get an idea of how that
> > could be done?
> > I don't know the chipset atm.
>
> lspci will tell you the chipset identifiers. Generally the first few
> listed devices are the chipset itself (00:00.0 is the north bridge, then
> the other stuff follows).
>
lspci:--8<-------------
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge
(rev 03)
00:02.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:02.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:02.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:02.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:03.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 05)
00:10.0 Unknown mass storage controller: Promise Technology, Inc. 20269
(rev 02)
00:14.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX]
(rev a1)
01:01.0 VGA compatible controller: S3 Inc. Trio 64 3D (rev 01)
-->8---------------
This is what I have - but anyway, the apm=off option seems to work for
the 2.4.19 kernel, so I guess i'll leave it at that for the time being.
I suspect that the option will work with the distribution kernel as
well.
If the task of poke'ing an additional IRQ into the APM monitor list is
simply just doing a pokeb or pokew at the right port somewhere, then I
just might have a look at it... I really don't know where to start
tough.
Anyway, thanks alot :-) at least now i'm pretty sure what's causing my
problems, and happy that i did NOT go out after another ATA133
controller, just to try that out - the result would likely have been the
same and a lot of money would have been wasted.
Thanks again
Thomas