Re: 2.4.5-ac8 hardlocks when going to standby
On Thu, Jun 07, 2001 at 01:00:15PM +0200, Mikael Pettersson wrote:
> On Wed, 6 Jun 2001 22:42:53 +0200, Remi Turk wrote:
>
> Try the patch below. Reboot. Run 'apm -S' (or --standby) at the
> console. Did you see output from both send_event and apic_pm_callback?
> If so, repeat by pressing your power-switch-as-standby button. You
> should see the same output -- if not, something APM-related is broken.
apm --standby works fine now:
send_event: event 9
apic_pm_callback: rqst 0 data 3
nmi_pm_callback: rqst 0 data 3
and on resume:
send_event: event 11
apic_pm_callback: rqst 1 data 0
nmi_pm_callback: rqst 1 data 0
apm --suspend also does what it should (and already did):
send_event: event 10
apic_pm_callback: rqst 0 data 3
nmi_pm_callback: rqst 0 data 3
and on resume:
send_event: event 3
apic_pm_callback: rqst 1 data 0
nmi_pm_callback: rqst 1 data 0
My "standbybutton" still hardlocks however.
Should I dig up some more info about my mainboard/BIOS?
> FYI, the patch below to apm.c:send_event() [w/o the printk] prevents
> my ASUS P3B-F from hanging hard if I invoke apm standby in a UP-APIC
> enabled kernel. (Actually, standby doesn't do much on my box since
> it wakes up after 1 second or so. I don't know why, perhaps a hub->nic
> link beat? 'suspend' works ok, however. Oh, and I have to disable
Try "sleep 2; apm --standby" or paste the newline with your mouse.
It works for me - my keyboard probably still sends data when my
system is already going into standby.
> RedHat's worthless 'kudzu' crap, otherwise 'suspend' won't work.)
It slows down booting a few seconds, and besides, I usually
know it when I add hardware, so kudzu is one of the first
packages I remove when installing.
>
> /Mikael
>
> case APM_USER_SUSPEND:
> + case APM_SYS_STANDBY:
> + case APM_USER_STANDBY:
> /* map all suspends to ACPI D3 */
> if (pm_send_all(PM_SUSPEND, (void *)3)) {
> if (event == APM_CRITICAL_SUSPEND) {
> @@ -932,6 +935,7 @@
> break;
> case APM_NORMAL_RESUME:
> case APM_CRITICAL_RESUME:
> + case APM_STANDBY_RESUME:
> /* map all resumes to ACPI D0 */
It locked when suspending so I don't expect the added
"case APM_STANDBY_RESUME" to make any difference.
printk() doesn't seem to be logical too, and I tried the
"case APM_SYS_STANDBY" and "case APM_SYS_SUSPEND" yesterday
(didn't make a difference) so it looks like the mdelay()
does it.
--
Linux 2.4.6-pre1 #1 Wed Jun 6 18:25:37 CEST 2001
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5-ac8 hardlocks when going to standby
On Thu, Jun 07, 2001 at 01:00:15PM +0200, Mikael Pettersson wrote:
On Wed, 6 Jun 2001 22:42:53 +0200, Remi Turk wrote:
Try the patch below. Reboot. Run 'apm -S' (or --standby) at the
console. Did you see output from both send_event and apic_pm_callback?
If so, repeat by pressing your power-switch-as-standby button. You
should see the same output -- if not, something APM-related is broken.
apm --standby works fine now:
send_event: event 9
apic_pm_callback: rqst 0 data 3
nmi_pm_callback: rqst 0 data 3
and on resume:
send_event: event 11
apic_pm_callback: rqst 1 data 0
nmi_pm_callback: rqst 1 data 0
apm --suspend also does what it should (and already did):
send_event: event 10
apic_pm_callback: rqst 0 data 3
nmi_pm_callback: rqst 0 data 3
and on resume:
send_event: event 3
apic_pm_callback: rqst 1 data 0
nmi_pm_callback: rqst 1 data 0
My standbybutton still hardlocks however.
Should I dig up some more info about my mainboard/BIOS?
FYI, the patch below to apm.c:send_event() [w/o the printk] prevents
my ASUS P3B-F from hanging hard if I invoke apm standby in a UP-APIC
enabled kernel. (Actually, standby doesn't do much on my box since
it wakes up after 1 second or so. I don't know why, perhaps a hub-nic
link beat? 'suspend' works ok, however. Oh, and I have to disable
Try sleep 2; apm --standby or paste the newline with your mouse.
It works for me - my keyboard probably still sends data when my
system is already going into standby.
RedHat's worthless 'kudzu' crap, otherwise 'suspend' won't work.)
It slows down booting a few seconds, and besides, I usually
know it when I add hardware, so kudzu is one of the first
packages I remove when installing.
/Mikael
case APM_USER_SUSPEND:
+ case APM_SYS_STANDBY:
+ case APM_USER_STANDBY:
/* map all suspends to ACPI D3 */
if (pm_send_all(PM_SUSPEND, (void *)3)) {
if (event == APM_CRITICAL_SUSPEND) {
@@ -932,6 +935,7 @@
break;
case APM_NORMAL_RESUME:
case APM_CRITICAL_RESUME:
+ case APM_STANDBY_RESUME:
/* map all resumes to ACPI D0 */
It locked when suspending so I don't expect the added
case APM_STANDBY_RESUME to make any difference.
printk() doesn't seem to be logical too, and I tried the
case APM_SYS_STANDBY and case APM_SYS_SUSPEND yesterday
(didn't make a difference) so it looks like the mdelay()
does it.
--
Linux 2.4.6-pre1 #1 Wed Jun 6 18:25:37 CEST 2001
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5-ac8 hardlocks when going to standby
On Wed, Jun 06, 2001 at 07:03:09PM +0200, Remi Turk wrote:
>
> By applying the following patch (lookalike)?
>
> arch/i386/kernel/apm.c:send_event():
>
> case APM_SYS_SUSPEND:
> case APM_CRITICAL_SUSPEND:
> case APM_USER_SUSPEND:
> + case APM_USER_STANDBY:
> + case APM_SYS_STANDBY:
> /* map all suspends to ACPI D3 */
> if (pm_send_all(PM_SUSPEND, (void
> *)3)) {
Well, I tried this one (did I understand correctly wat
you meant???) and it didn't make any difference.
--
Linux 2.4.6-pre1 #1 Wed Jun 6 18:25:37 CEST 2001
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5-ac8 hardlocks when going to standby
On Wed, Jun 06, 2001 at 07:03:09PM +0200, Remi Turk wrote:
By applying the following patch (lookalike)?
arch/i386/kernel/apm.c:send_event():
case APM_SYS_SUSPEND:
case APM_CRITICAL_SUSPEND:
case APM_USER_SUSPEND:
+ case APM_USER_STANDBY:
+ case APM_SYS_STANDBY:
/* map all suspends to ACPI D3 */
if (pm_send_all(PM_SUSPEND, (void
*)3)) {
Well, I tried this one (did I understand correctly wat
you meant???) and it didn't make any difference.
--
Linux 2.4.6-pre1 #1 Wed Jun 6 18:25:37 CEST 2001
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5-ac8 hardlocks when going to standby
On Tue, Jun 05, 2001 at 09:37:52PM +0100, Alan Cox wrote: > > 2.4.5-ac[4678] all lock hard (no sysreq) when pushing my > > power-button (setup from the bios to go to standby) or > > when running apm --standby. (apm version 3.0final, RH6.2) > > apm --suspend works the way it should. > > > > 2.4.5/2.4.6-pre1 don't hardlock. > > Are you using the same build options for both > What machine is this - laptop ? It's not a laptop. Tbird 950 + Abit KT7 (KT133) UP APIC is enabled in -ac[4678] and emu10k1 is the in-kernel version instead of the one from CVS in -ac8 - which shouldn't matter because -ac[467] ran with the CVS-version. 2.4.6-pre1 runs emu10k1 from CVS. I'll compile -ac8 without UP-APIC, but I don't think I'll have time to mail the results until tommorow. --- 2.4.5-ac8-configTue Jun 5 23:05:55 2001 +++ 2.4.6-pre1-config Tue Jun 5 23:05:57 2001 @@ -20,10 +20,9 @@ CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_NOHIGHMEM=y CONFIG_MTRR=y -CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y -CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y +CONFIG_X86_LOCAL_APIC=y CONFIG_NET=y CONFIG_PCI=y CONFIG_PCI_GOANY=y @@ -129,9 +128,7 @@ CONFIG_VGA_CONSOLE=y CONFIG_VIDEO_SELECT=y CONFIG_SOUND=m -CONFIG_SOUND_EMU10K1=m CONFIG_USB=m CONFIG_USB_DEVICEFS=y CONFIG_USB_UHCI=m -CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y -- Linux 2.4.6-pre1 #2 Tue Jun 5 18:08:24 CEST 2001 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.5-ac8 hardlocks when going to standby
Hi, 2.4.5-ac[4678] all lock hard (no sysreq) when pushing my power-button (setup from the bios to go to standby) or when running apm --standby. (apm version 3.0final, RH6.2) apm --suspend works the way it should. 2.4.5/2.4.6-pre1 don't hardlock. lspci -vvxxx output and .config are attached. Any ideas? -- Linux 2.4.6-pre1 #2 Tue Jun 5 18:08:24 CEST 2001 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 02) Subsystem: ABIT Computer Corp.: Unknown device a401 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 05 03 06 00 10 22 02 00 00 06 00 08 00 00 10: 08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 7b 14 01 a4 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- FastB2B- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 05 83 07 00 30 22 00 00 04 06 00 00 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 00 f0 00 00 00 20: 00 d4 f0 d5 00 d6 f0 d6 00 00 00 00 00 00 00 00 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 0c 00 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22) Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] [size=256K] Capabilities: [d0] AGP version 1.0 Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2 Command: RQ=0 SBA- AGP- 64bit- FW- Rate= Capabilities: [dc] Power Management version 1 Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 86 80 00 78 07 00 b0 02 21 00 00 03 00 00 00 00 10: 08 00 00 d6 00 00 00 d5 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 b0 10 00 01 30: 00 00 00 00 d0 00 00 00 00 00 00 00 0b 01 00 00 CONFIG_X86=y CONFIG_ISA=y CONFIG_UID16=y CONFIG_EXPERIMENTAL=y CONFIG_MODULES=y CONFIG_KMOD=y CONFIG_MK7=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_USE_3DNOW=y CONFIG_X86_PGE=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_NOHIGHMEM=y CONFIG_MTRR=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_NET=y CONFIG_PCI=y CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_NAMES=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_PM=y CONFIG_APM=y CONFIG_APM_RTC_IS_GMT=y CONFIG_PARPORT=y CONFIG_PARPORT_PC=y CONFIG_PARPORT_PC_FIFO=y CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_LOOP=m CONFIG_MD=y CONFIG_BLK_DEV_LVM=m CONFIG_PACKET=m CONFIG_PACKET_MMAP=y CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NETLINK_DEV=y CONFIG_NETFILTER=y CONFIG_UNIX=y CONFIG_INET=y CONFIG_SYN_COOKIES=y CONFIG_IP_NF_CONNTRACK=y CONFIG_IP_NF_IPTABLES=y CONFIG_IP_NF_MATCH_LIMIT=y CONFIG_IP_NF_MATCH_MARK=y CONFIG_IP_NF_MATCH_MULTIPORT=y CONFIG_IP_NF_MATCH_TOS=y CONFIG_IP_NF_MATCH_STATE=y CONFIG_IP_NF_MATCH_UNCLEAN=m CONFIG_IP_NF_MATCH_OWNER=m CONFIG_IP_NF_FILTER=y CONFIG_IP_NF_TARGET_REJECT=y CONFIG_IP_NF_NAT=y CONFIG_IP_NF_NAT_NEEDED=y CONFIG_IP_NF_MANGLE=y CONFIG_IP_NF_TARGET_TOS=y CONFIG_IP_NF_TARGET_MARK=y CONFIG_IP_NF_TARGET_LOG=y CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_BLK_DEV_IDECD=y CONFIG_BLK_DEV_IDEFLOPPY=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_SHARE_IRQ=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_IDEDMA_PCI_AUTO=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_BLK_DEV_VIA82CXXX=y CONFIG_IDEDMA_AUTO=y CONFIG_BLK_DEV_IDE_MODES=y CONFIG_SCSI=y CONFIG_BLK_DEV_SD=y CONFIG_SD_EXTRA_DEVS=40 CONFIG_SCSI_IMM=m CONFIG_NETDEVICES=y CONFIG_DUMMY=m CONFIG_PLIP=m CONFIG_PPP=m CONFIG_PPP_ASYNC=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_BSDCOMP=m CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_SERIAL=y CONFIG_SERIAL_CONSOLE=y CONFIG_UNIX98_PTYS=y
2.4.5-ac8 hardlocks when going to standby
Hi, 2.4.5-ac[4678] all lock hard (no sysreq) when pushing my power-button (setup from the bios to go to standby) or when running apm --standby. (apm version 3.0final, RH6.2) apm --suspend works the way it should. 2.4.5/2.4.6-pre1 don't hardlock. lspci -vvxxx output and .config are attached. Any ideas? -- Linux 2.4.6-pre1 #2 Tue Jun 5 18:08:24 CEST 2001 00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 02) Subsystem: ABIT Computer Corp.: Unknown device a401 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 8 Region 0: Memory at d000 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 2.0 Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2 Command: RQ=0 SBA- AGP- 64bit- FW- Rate=none Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 05 03 06 00 10 22 02 00 00 06 00 08 00 00 10: 08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 7b 14 01 a4 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: d400-d5ff Prefetchable memory behind bridge: d600-d6ff BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B- Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 05 83 07 00 30 22 00 00 04 06 00 00 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 00 f0 00 00 00 20: 00 d4 f0 d5 00 d6 f0 d6 00 00 00 00 00 00 00 00 30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 0c 00 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22) Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 00: 06 11 86 06 87 00 10 02 22 00 01 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 06 11 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 10) (prog-if 8a [Master SecP PriP]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 Region 4: I/O ports at d000 [size=16] Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 71 05 07 00 90 02 10 8a 01 01 00 20 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 00 00 00 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 10) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32, cache line size 08 Interrupt: pin D routed to IRQ 10 Region 4: I/O ports at d400 [size=32] Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 38 30 07 00 10 02 10 00 03 0c 08 20 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 d4 00 00 00 00 00 00 00 00 00 00 25 09 34 12 30: 00 00 00 00 80 00 00 00 00 00 00 00 0a 04 00 00 00:07.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 10) (prog-if 00 [UHCI]) Subsystem: Unknown device 0925:1234 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32, cache line size 08 Interrupt: pin
Re: 2.4.5-ac8 hardlocks when going to standby
On Tue, Jun 05, 2001 at 09:37:52PM +0100, Alan Cox wrote: 2.4.5-ac[4678] all lock hard (no sysreq) when pushing my power-button (setup from the bios to go to standby) or when running apm --standby. (apm version 3.0final, RH6.2) apm --suspend works the way it should. 2.4.5/2.4.6-pre1 don't hardlock. Are you using the same build options for both What machine is this - laptop ? It's not a laptop. Tbird 950 + Abit KT7 (KT133) UP APIC is enabled in -ac[4678] and emu10k1 is the in-kernel version instead of the one from CVS in -ac8 - which shouldn't matter because -ac[467] ran with the CVS-version. 2.4.6-pre1 runs emu10k1 from CVS. I'll compile -ac8 without UP-APIC, but I don't think I'll have time to mail the results until tommorow. --- 2.4.5-ac8-configTue Jun 5 23:05:55 2001 +++ 2.4.6-pre1-config Tue Jun 5 23:05:57 2001 @@ -20,10 +20,9 @@ CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_NOHIGHMEM=y CONFIG_MTRR=y -CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y -CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y +CONFIG_X86_LOCAL_APIC=y CONFIG_NET=y CONFIG_PCI=y CONFIG_PCI_GOANY=y @@ -129,9 +128,7 @@ CONFIG_VGA_CONSOLE=y CONFIG_VIDEO_SELECT=y CONFIG_SOUND=m -CONFIG_SOUND_EMU10K1=m CONFIG_USB=m CONFIG_USB_DEVICEFS=y CONFIG_USB_UHCI=m -CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y -- Linux 2.4.6-pre1 #2 Tue Jun 5 18:08:24 CEST 2001 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
