[Bug 35274] Re: NetVista 6824 becomes unresponsive after some time, OK after reboot

[Alex Perry]

Just want to add that as of 01/08, this bug is still causing a problem.

I'm currently using a Netvista 8303HCU with Gutsy, 2.6.22-14-i386.
Adding 'acpi=off noapic' to the grub menu entry resolves the issue.

I have added some output lines from my kern.log which may be of some
use, and attached is the entire log file.

Jan 25 09:55:11 perry kernel: [   40.706610] ACPI: Interpreter disabled.
Jan 25 09:55:11 perry kernel: [   40.706614] Linux Plug and Play Support v0.97 (c) Adam Belay
Jan 25 09:55:11 perry kernel: [   40.706626] pnp: PnP ACPI: disabled
Jan 25 09:55:11 perry kernel: [   40.706630] PnPBIOS: Scanning system for PnP BIOS support...
Jan 25 09:55:11 perry kernel: [   40.706640] PnPBIOS: Found PnP BIOS installation structure at 0xc00f6290
Jan 25 09:55:11 perry kernel: [   40.706643] PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x9f45, dseg 0x400
Jan 25 09:55:11 perry kernel: [   40.708833] PnPBIOS: 19 nodes reported by PnP BIOS; 19 recorded by driver
Jan 25 09:55:11 perry kernel: [   40.708887] PCI: Probing PCI hardware
Jan 25 09:55:11 perry kernel: [   40.708894] PCI: Probing PCI hardware (bus 00)
Jan 25 09:55:11 perry kernel: [   40.709264] * The chipset may have PM-Timer Bug. Due to workarounds for a bug,
Jan 25 09:55:11 perry kernel: [   40.709266] * this clock source is slow. If you are sure your timer does not have
Jan 25 09:55:11 perry kernel: [   40.709268] * this bug, please use "acpi_pm_good" to disable the workaround
Jan 25 09:55:11 perry kernel: [   40.709310] PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
Jan 25 09:55:11 perry kernel: [   40.709313] PCI quirk: region 1180-11bf claimed by ICH4 GPIO

** Attachment added: "Kernel Log File"
   http://launchpadlibrarian.net/11587114/kern.log

** Also affects: linux-source-2.6.22 (Ubuntu)
   Importance: Undecided
       Status: New

-- 
NetVista 6824 becomes unresponsive after some time, OK after reboot
https://bugs.launchpad.net/bugs/35274
You received this bug notification because you are a member of Kernel
Bugs, which is a direct subscriber.