On Fri, Jul 07, 2006 at 09:22:59PM -0700, Willie Wonka wrote: [... stuff about cron jobs ...] definitely this is not my issue as it happens at any time of day. Also, this is truly a hard lock -- no disk activity, no response of any kind from any stimulus I can come up with. In fact, if the machine is in a state where the screen is automatically turned off (power saving mode) the screen will not reactivate. > > ACPI hmm.. Let's see output of 'dmesg | grep ACPI' andrew@basement:~$ dmesg | grep ACPI BIOS-e820: 000000000dfec000 - 000000000dfef000 (ACPI data) BIOS-e820: 000000000dfff000 - 000000000e000000 (ACPI NVS) ACPI: RSDP (v000 ASUS ) @ 0x000f8070 ACPI: RSDT (v001 ASUS A7N266VM 0x42302e31 MSFT 0x31313031) @ 0x0dfec000 ACPI: FADT (v001 ASUS A7N266VM 0x42302e31 MSFT 0x31313031) @ 0x0dfec100 ACPI: BOOT (v001 ASUS A7N266VM 0x42302e31 MSFT 0x31313031) @ 0x0dfec040 ACPI: MADT (v001 ASUS A7N266VM 0x42302e31 MSFT 0x31313031) @ 0x0dfec080 ACPI: DSDT (v001 ASUS A7N266VM 0x00001000 MSFT 0x0100000b) @ 0x00000000 ACPI: PM-Timer IO Port: 0xe408 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl edge) ACPI: BIOS IRQ0 pin2 override ignored. ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ9 used by override. Using ACPI (MADT) for SMP configuration information ACPI: bus type pci registered ACPI: Subsystem revision 20060127 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Interrupt Link [LNKA] (IRQs 16 18) *5 ACPI: PCI Interrupt Link [LNKB] (IRQs 16 18) *0, disabled. ACPI: PCI Interrupt Link [LNKC] (IRQs 16 18) *0, disabled. ACPI: PCI Interrupt Link [LNKD] (IRQs 16 18) *5 ACPI: PCI Interrupt Link [LNKE] (IRQs 19) *11 ACPI: PCI Interrupt Link [LNKF] (IRQs 20 21 22) *5 ACPI: PCI Interrupt Link [LNKU] (IRQs 20 21 22) *10 ACPI: PCI Interrupt Link [LNKI] (IRQs 20 21 22) *10 ACPI: PCI Interrupt Link [LNKJ] (IRQs 20 21 22) *5 ACPI: PCI Interrupt Link [LNKK] (IRQs 20 21 22) *11 ACPI: PCI Interrupt Link [LNKM] (IRQs 20 21 22) *0, disabled. ACPI: PCI Root Bridge [PCI0] (0000:00) ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI2._PRT] pnp: PnP ACPI init pnp: PnP ACPI: found 17 devices PnPBIOS: Disabled by ACPI PNP PCI: Using ACPI for IRQ routing ACPI wakeup devices: ACPI: (supports S0 S1 S3 S4 S5) ACPI: PCI Interrupt Link [LNKI] enabled at IRQ 22 ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LNKI] -> GSI 22 (level, high) -> IRQ 177 ACPI: PCI Interrupt Link [LNKU] enabled at IRQ 21 ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LNKU] -> GSI 21 (level, high) -> IRQ 185 ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKU] -> GSI 21 (level, high) -> IRQ 185 ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 18 ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [LNKD] -> GSI 18 (level, high) -> IRQ 193 ACPI: PCI Interrupt Link [LNKK] enabled at IRQ 20 ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LNKK] -> GSI 20 (level, high) -> IRQ 201 ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 19 ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKE] -> GSI 19 (level, high) -> IRQ 209 andrew@basement:~$ > > Do you use an 'acpi=force' kernel boot option in GRUB/Lilo ?? > I do on this ~1999 PII, 350MHz 100FSB, 192MB RAM; nope. there is some acpi setting in the BIOS that is turned on, can't remember what it is exactly, will post in after next reboot. meanwhile, I found I had apcid turned on from some acpi stuff I was playing with a few months ago. I've update-rc.d remove'd it and haven't had a problem in a day and a half (knock wood). I"m going to go at this thing from the ground up again starting with all BIOS settings and... heh... logging my actions, there's a novel thought. > > > [ anecdotal rantings ensue] ... > [ /anecdotal rantings end ] > well. that's quite a tale. All I can say is, if the keyboard doesn't seem to work right, maybe next time try a new keyboard first? he he. on that note, i've heard several tales of keyboards being resurrected by putting them through the dishwasher... I'd google it first, but if you have a dead keyboard, it certainly wouldn't hurt. I'm sure it'll void the warranty though. A
Attachment:
signature.asc
Description: Digital signature