>It should be easy to decide which one it is... One printk before
>ioremap and one phys_to_virt. Compared to number of printk's you must
>have already done....
I had not done this one (I got lazy after numerous reboots), but I tried =
ioremap((unsigned long) phys, size);
is the culprit.=20
>phys =3D 0xdef * 64K ~=3D 256 * 64K * 16 =3D 4K * 64K =3D 256M. Do you h=
>least 256MB ram? If not I can see why phys_to_virt would fail...
I have 256 MB precisely. But the upper 32 MB are used by the vga chipset.=
a VIA Twister-K which uses the normal memory for his grafic memory. So I =
to pass mem=3D224M.
But this brought me an idea and I tried several options:
2.4.18+acpi-patch, no mem=3D, grub without --disable-auto-linux-mem-opt
now everything with grub --disable-auto-linux-mem-opt:
2.4.18+acpi-patch, mem=3D224M -> AE_NO_MEMORY
2.4.18+acpi-patch, mem=3D256M -> kernel panic
2.4.18+acpi-patch, no mem=3D -> ACPI detected, system hangs
2.5.24, mem=3D224M -> ACPI detected, system hangs
2.5.21, no mem=3D -> ACPI detected, system hangs
2.4.18, mem=3D224M -> AE_NO_MEMORY
2.4.18, no mem=3D -> ACPI detected, system hangs
So this AE_NO_MEMORY comes whenever I pass an mem=3D224M or when grub aut=
it (how nasty in combination with this error!). As it's gone in 2.5.21-24=
this is a severe bug in the 2.4.18 kernel, that does something wrong toge=
with mem=3D224M, however not an error of the acpi-system.
The system hangs in 2.5.21/24 and 2.4.18 without mem=3D224M:
Unfortunately they do not have something to do with the unstable state of=
2.5. kernels (as I thought before), but seem to be a generic problem of t=
ACPI subsystem, because 2.4.18 with or without the acpi-patch have the sa=
problem, if the mem=3D problem is curcumvented.
Here is what I get as debug messages from 2.4.18+patch:
tbxface-0100  Acpi_load_tables: ACPI Tables successfully loaded
Parsing Methods: ..................... [lots of dots]................
Table [DSDT] - 376 Objects with 42 Devices 105 Methods 14 Regions
Parsing Methods: [no dots]
Tables [SSDT] - 0 Objects with 0 Devices 0 Methods 0 Regions
ACPI Namespace successfully loaded at root c0316e7c
Then nothing happens and the system reacts only to the power button (no s=
reboot, no SYSRQ, nothing). I even had to manually copy the printout, as=20
nothing gets saved to kern.log. Linux 2.4.18 (without acpi-patch) is simi=
it stops with "ACPI: Core subsystem version ".
I tried recompiling with [x] CPU enumeration only. That does work (!), bu=
soon as I turn on the full ACPI again, even without any options like AC=20
Adapter, CPU or Thermal, I get the hang again. So there is something wron=
with the ACPI system, just that I don't have a clear error message this t=
As other laptops with VIA Twister-K chipset were reported to work, I don'=
think it's a general incompatibility with this chipset, but what else can=
this be? As soon as the first problem (mem=3D224M) is solved, we have the=
Any ideas? I won't give up as long as I have something to try out...