I was able to insert these noacpi options by editing the commented out
kopt= parameter and rerunning update-group. Booted with all ACPI
disabled.

I will see how it goes.

# kopt=root=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx ro noapic nolapic pci=noacpi acpi=off

So far it seems that the server is running OK, but only time will
tell.

i

On 2008-05-12, Ignoramus17662 <ignoramus17662@NOSPAM.17662.invalid> wrote:
> On 2008-05-12, Darren Salt <news@youmustbejoking.demon.cu.invalid> wrote:
>> I demand that Ignoramus4557 may or may not have written...
>>
>>> I was able to insmod netconsole.
>>
>>> root@server:~# modprobe netconsole \
>>> netconsole="1941@10.1.xxx.xxx/eth0,1941@192.168.xxx.xxx/00:14:xx:xx:xx:xx"
>>
>>> mypc:myusername:~ ==>nc -u -l 1941
>>
>>> However, I did not receive any kernel messages on the target machine.
>>
>>> That's despite having generated some kernel messages by inserting a
>>> superfluous module and verifying that with dmesg.
>>
>> The IP addresses say that you're using two separate logical networks. That's
>> fine, so long as the destination IP address is routable and the destination
>> MAC address is one hop away from the source machine (the server). Is this the
>> case?
>>
>> [snip]
>
> That could be it.
>
> I have modified the line in /boot/grub/menu.lst
>
> from
>
> defoptions=quiet splash
>
> to
>
> defoptions=quiet splash noapic nolapic pci=noacpi
>
> I will try this after hours tonight.
>
> I certainly do not need ACPI on this server.

--
Due to extreme spam originating from Google Groups, and their inattention
to spammers, I and many others block all articles originating
from Google Groups. If you want your postings to be seen by
more readers you will need to find a different means of
posting on Usenet.
http://improve-usenet.org/