[Bug 204876] New: Kernel hangs during the beginnig of the installation - while loading APIC. nForce 570-SLI Asus motheboard
https://bugzilla.novell.com/show_bug.cgi?id=204876 Summary: Kernel hangs during the beginnig of the installation - while loading APIC. nForce 570-SLI Asus motheboard Product: openSUSE 10.2 Version: Alpha 4 Platform: IA64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: user72@go2.pl QAContact: qa@suse.de It is not possible to install without manually adding "noapic" boot param. Installator hangs in every install option except "safe". Also apic=debug causes system to stop responding.
From the text-mode install screen: ENABLING IO-APIC IRQS TIMER: vector 0x31 apic1=0 pin1=0 apic2=-1 pin2=01 MP_BIOS bug: 8254 timer not connected to IO-APIC ..trying to set up timer (IRQ0) through the 8259A ...failed ..trying to set up timer as Virtual Wire IRQ ...failed ..trying to set up timer as ExtINT IRQ failed :( kernel_panic - not syncing: IO-APIC timer doesn't work! Boot with apic=debug and send a report. Then try booting with 'noapic' option -- Actually I was not able to generate report cause system stops to respond even with apic=debug. I have installed Suse 10.2 Alpha4 with 'noapic'.
My Hardware: Motherboard: Asus M2N-Sli Deluxe (nForce 570 Sli) CPU: Athlon 64 3000+ Orleans (socket AM2) Ram: 2x512 Kingston DDR2 533Mhz Dual (verified with memtest86 and Prime95) GPU: 1x 7600GS 500/14000MHz Galaxy; Zalman edition HDD: 2xSata without RAID Please let me know whether to send more information. Mark -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204876 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |user72@go2.pl ------- Comment #1 from gregkh@novell.com 2006-09-12 04:00 MST ------- Are you installing the 32 or 64bit kernel/version? I really don't think you are using ia64 processors, AMD doesn't make them... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204876 user72@go2.pl changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |user72@go2.pl Platform|IA64 |x86 ------- Comment #2 from user72@go2.pl 2006-09-12 05:14 MST ------- I am running >>>32-bit Suse<<< on 64-bit Athlon 3000 from AMD. I am changing hardware to x86, because I use 32-bit Suse. Let me know if I should change to sth else or feel free to correct. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204876 ------- Comment #3 from user72@go2.pl 2006-09-12 10:57 MST ------- Please someone delete this bug as it is the same to 171517. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204876 fhassel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|user72@go2.pl | Platform|x86 |x86-64 Resolution| |DUPLICATE ------- Comment #4 from fhassel@novell.com 2006-09-21 07:45 MST ------- The hardware should still be x86_64. As requested I mark the bug as duplicate of bug 171517. *** This bug has been marked as a duplicate of bug 171517 *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com