ACPI freezes my Biostar TF-520 (Was: Help me troubleshoot this problem
Rick Sewill wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Having said the above, if you suspect an acpi or apic problem, > the URL: http://fedoraproject.org/wiki/KernelCommonProblems > says, > "acpi=off is a big hammer, and if that works, narrowing down by trying > pci=noacpi instead may yield clues" > It also says, "nolapic and noapic are sometimes useful" > > > > > A quick update. I tried the acpi=no option and so far, so good. I have even > > brought it back into X windows and ran some yum updates to apply some > > stress. I'll leave it in this state until tomorrow evening just to make > > sure. Then I'll try the smaller hammers. > > > > Question showing my ignorance of what acpi is. If pci=noacpi works or does > > not work, what clues is that giving me? > > > > I didn't respond earlier because we've reached my level of ignorance too. > > If I were you, I might try to narrow the problem a little further. > > Eventually I would write a Bugzilla bug report telling the maintainers > the symptoms, what I had done, including things that didn't work as well > as things that seemed to work. > A followup on my previous thread. I worked through a number of the suggestions in the KernelCommonProblems. The two kernel options that kept the system from freezing were acpi=off and clocksource=jiffies. The system either froze or crashed with any other options, including no options. Here is the grub.conf I used to keep track of the experiments: title Fedora 13 (original) --crashed-- (2.6.33.6-147.fc13.i686.PAE) root (hd0,0) kernel /vmlinuz-2.6.33.6-147.fc13.i686.PAE ro root=/dev/mapper/vg00-root1 rd_LVM_LV=vg00/root1 rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nouveau.modeset=0 rdblacklist=nouveau debug nmi_watchdog=2 initrd /initramfs-2.6.33.6-147.fc13.i686.PAE.img title Fedora 13 acpi=off --works-- (2.6.33.6-147.fc13.i686.PAE) root (hd0,0) kernel /vmlinuz-2.6.33.6-147.fc13.i686.PAE ro root=/dev/mapper/vg00-root1 rd_LVM_LV=vg00/root1 rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nouveau.modeset=0 rdblacklist=nouveau debug nmi_watchdog=2 acpi=off initrd /initramfs-2.6.33.6-147.fc13.i686.PAE.img title Fedora 13 pci=noacpi --froze-- (2.6.33.6-147.fc13.i686.PAE) root (hd0,0) kernel /vmlinuz-2.6.33.6-147.fc13.i686.PAE ro root=/dev/mapper/vg00-root1 rd_LVM_LV=vg00/root1 rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nouveau.modeset=0 rdblacklist=nouveau debug nmi_watchdog=2 pci=noacpi initrd /initramfs-2.6.33.6-147.fc13.i686.PAE.img title Fedora 13 nolapic --froze-- (2.6.33.6-147.fc13.i686.PAE) root (hd0,0) kernel /vmlinuz-2.6.33.6-147.fc13.i686.PAE ro root=/dev/mapper/vg00-root1 rd_LVM_LV=vg00/root1 rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nouveau.modeset=0 rdblacklist=nouveau debug nmi_watchdog=2 nolapic initrd /initramfs-2.6.33.6-147.fc13.i686.PAE.img title Fedora 13 noapic --froze-- (2.6.33.6-147.fc13.i686.PAE) root (hd0,0) kernel /vmlinuz-2.6.33.6-147.fc13.i686.PAE ro root=/dev/mapper/vg00-root1 rd_LVM_LV=vg00/root1 rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nouveau.modeset=0 rdblacklist=nouveau debug nmi_watchdog=2 noapic initrd /initramfs-2.6.33.6-147.fc13.i686.PAE.img title Fedora 13 nolapic_timer --froze-- (2.6.33.6-147.fc13.i686.PAE) root (hd0,0) kernel /vmlinuz-2.6.33.6-147.fc13.i686.PAE ro root=/dev/mapper/vg00-root1 rd_LVM_LV=vg00/root1 rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nouveau.modeset=0 rdblacklist=nouveau debug nmi_watchdog=2 nolapic_timer initrd /initramfs-2.6.33.6-147.fc13.i686.PAE.img title Fedora 13 nohz=off --froze-- (2.6.33.6-147.fc13.i686.PAE) root (hd0,0) kernel /vmlinuz-2.6.33.6-147.fc13.i686.PAE ro root=/dev/mapper/vg00-root1 rd_LVM_LV=vg00/root1 rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nouveau.modeset=0 rdblacklist=nouveau debug nmi_watchdog=2 nohz=off initrd /initramfs-2.6.33.6-147.fc13.i686.PAE.img title Fedora 13 highres=off --froze-- (2.6.33.6-147.fc13.i686.PAE) root (hd0,0) kernel /vmlinuz-2.6.33.6-147.fc13.i686.PAE ro root=/dev/mapper/vg00-root1 rd_LVM_LV=vg00/root1 rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nouveau.modeset=0 rdblacklist=nouveau debug nmi_watchdog=2 highres=off initrd /initramfs-2.6.33.6-147.fc13.i686.PAE.img title Fedora 13 nohz=off highres=off --froze-- (2.6.33.6-147.fc13.i686.PAE) root (hd0,0) kernel /vmlinuz-2.6.33.6-147.fc13.i686.PAE ro root=/dev/mapper/vg00-root1 rd_LVM_LV=vg00/root1 rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8
Re: Help me troubleshoot this problem
On 07/07/2010 01:47 PM, Darr wrote: >>> Question showing my ignorance of what acpi is. If pci=noacpi works >>> or does not work, what clues is that giving me? >>> >> >> I didn't respond earlier because we've reached my level of ignorance >> too. > > > ACPI is the successor/combination of plug& play, advanced > power management, et al... > > If you have disabled ACPI and it did not make a difference, I > would say the clue it's giving you is ACPI is not causing the error. > > > APIC, on the other hand, has to do with interrupt timing. Do you > see any options in your BIOS for enabling/disabling/changing > APIC's slices or timing? > > Are you overclocking your RAM or CPU[s]? > Specifying apci=off in grub seems to have worked. Now I've booted with pci=noacpi, and so far it seems to be working. I'll let it run overnight with the X screensaver on to see if it cares to lock up. Then I'll try the nolapic and noapic options. Then I'll figure out what to try next. I looked in the BIOS but did not see any options for fine tuning timing or slices. I'll look again next time I reboot. How should I manipulate slices or timing if I find that capability? And no, I'm not overclocking, at least not intentionally :). Thanks for the questions. Please keep them coming. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
>> Question showing my ignorance of what acpi is. If pci=noacpi works >> or does not work, what clues is that giving me? >> > > I didn't respond earlier because we've reached my level of ignorance > too. ACPI is the successor/combination of plug & play, advanced power management, et al... If you have disabled ACPI and it did not make a difference, I would say the clue it's giving you is ACPI is not causing the error. APIC, on the other hand, has to do with interrupt timing. Do you see any options in your BIOS for enabling/disabling/changing APIC's slices or timing? Are you overclocking your RAM or CPU[s]? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Having said the above, if you suspect an acpi or apic problem, the URL: http://fedoraproject.org/wiki/KernelCommonProblems says, "acpi=off is a big hammer, and if that works, narrowing down by trying pci=noacpi instead may yield clues" It also says, "nolapic and noapic are sometimes useful" > > A quick update. I tried the acpi=no option and so far, so good. I have even > brought it back into X windows and ran some yum updates to apply some stress. > I'll leave it in this state until tomorrow evening just to make sure. Then > I'll try the smaller hammers. > > Question showing my ignorance of what acpi is. If pci=noacpi works or does > not work, what clues is that giving me? > I didn't respond earlier because we've reached my level of ignorance too. If I were you, I might try to narrow the problem a little further. Eventually I would write a Bugzilla bug report telling the maintainers the symptoms, what I had done, including things that didn't work as well as things that seemed to work. If I had a workaround, I wouldn't expect much help from a maintainer because I would assume they have other problems to solve where a workaround is not known. If my Bugzilla bug report happened to be in an area a maintainer was already digging in, the maintainer might take an interest and ask me to do things to help gather more information. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkw0eoUACgkQyc8Kn0p/AZR50wCcDs5oxFPA5YEY7WxUzXnx5y1w YQQAnRj/zLTrSXXOVqxTsHfkP2golkvs =LcJc -END PGP SIGNATURE- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
JD wrote: > On 07/05/2010 06:44 PM, awrobinson...@nc.rr.com wrote: > > Rick Sewill wrote: > >> On 07/05/2010 06:15 PM, awrobinson...@nc.rr.com wrote: > >>> Geoffrey Leach wrote: > On 07/05/2010 03:28:20 PM, awrobinson...@nc.rr.com wrote: > > Geoffrey Leach wrote: > >> On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: > >>> I am trying to install Fedora on a PC I built. I had Windows XP > >>> running on it for more than a year without any apparent problems. > > > Hardware: > > > > Motherboard: BIOSTAR TFORCE TF520-A2 AM2 NVIDIA nForce 520 MCP ATX > > AMD > > Processor: AMD Athlon 64 X2 4200+ Brisbane 2.2GHz Socket AM2 65W > > Dual-Core Processor > > Video Card: MSI NX8400GS-TD256E GeForce 8400 GS 256MB 64-bit GDDR2 > > PCI > > Express > > Memory: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > > Dual Channel > > Memory: A-DATA 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > > Dual Channel > > (6 GB total) > > Hard drive: SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s > > 3.5" > > >>> > >> May I suggest looking at the URL: > >> http://fedoraproject.org/wiki/KernelCommonProblems > >> > >> It is where I would start when trying to debug Fedora panic/crash problems. > >> > >> > From this webpage, in the "Crashes/Hangs" section, they seem to suggest > >> setting kernel boot parameters to try to narrow the problem or work > >> around the problem. > >> > >> For more information on kernel boot parameters, the web page says, > >> "The full list of kernel options is in the file > >> /usr/share/doc/kernel-doc-/Documentation/kernel-parameters.txt, > >> which is installed with the kernel-doc package" > >> > >> I assume one can find the correct kernel-parameters.txt file either > >> looking in the local file system assuming Fedora is usable -or- > >> searching the internet for "kernel-parameters.txt" > >> If one finds it with an internet search, please make sure the > >> kernel-parameters.txt more or less match the correct version of the > >> Fedora kernel. > >> > >> Having said the above, if you suspect an acpi or apic problem, > >> the URL: http://fedoraproject.org/wiki/KernelCommonProblems > >> says, > >> "acpi=off is a big hammer, and if that works, narrowing down by trying > >> pci=noacpi instead may yield clues" > >> It also says, "nolapic and noapic are sometimes useful" > >> A quick update. I tried the acpi=no option and so far, so good. I have even brought it back into X windows and ran some yum updates to apply some stress. I'll leave it in this state until tomorrow evening just to make sure. Then I'll try the smaller hammers. Question showing my ignorance of what acpi is. If pci=noacpi works or does not work, what clues is that giving me? Thanks! Andrew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
I recently installed F13 on a system with nForce 4 chipset. It consistently failed when trying to boot x86_64. Both from USB stick and from live CD. I didn't try x86_64 install DVD. Instead I fell back to a USB memory stick with i686 live instead, and it worked just fine. I see you are also trying with a nForce based motherboard. Have you tried x86_64 or i686? I don't really think you are seeing the same problem that I have, as my system fails before getting up the graphical interface from the live environment. It fails with filesystem decompression errors, both from CD and memory stick. -- birger -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
On 07/05/2010 09:04 PM, JD wrote: > On 07/05/2010 08:23 PM, Kam Leo wrote: >> On Mon, Jul 5, 2010 at 8:08 PM, JD wrote: >>> On 07/05/2010 07:28 PM, awrobinson...@nc.rr.com wrote: JDwrote: > On 07/05/2010 06:44 PM, awrobinson...@nc.rr.com wrote: >> Rick Sewill wrote: >>> On 07/05/2010 06:15 PM, awrobinson...@nc.rr.com wrote: Geoffrey Leach wrote: > On 07/05/2010 03:28:20 PM, awrobinson...@nc.rr.com wrote: >> Geoffrey Leach wrote: >>> On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: I am trying to install Fedora on a PC I built. I had Windows XP running on it for more than a year without any apparent problems. > >> Hardware: >> >> Motherboard: BIOSTAR TFORCE TF520-A2 AM2 NVIDIA nForce 520 >> MCP ATX >> AMD >> Processor: AMD Athlon 64 X2 4200+ Brisbane 2.2GHz Socket AM2 65W >> Dual-Core Processor >> Video Card: MSI NX8400GS-TD256E GeForce 8400 GS 256MB 64-bit >> GDDR2 >> PCI >> Express >> Memory: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 >> 6400) >> Dual Channel >> Memory: A-DATA 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 >> 6400) >> Dual Channel >> (6 GB total) >> Hard drive: SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA >> 3.0Gb/s >> 3.5" > > Have you booted it into single user mode? > I have not. At least, I haven't since I was trouble shooting issues with disk drives that are no longer in the system. What would I do in single user mode to trouble shoot the current problem? >>> See if it will freeze!! >> If problems still persist other things to check: >> >> 1. Revert to default BIOS settings >> 2. Dusted off your computer >> 3. Re-seat all connections >> 4. Verify all fans are in working order >> 5. Run with external peripherals, e.g. USB drives. disconnected > You might also try these HW test programs: > http://www.testmyhardware.com/ > > Unfortunately, it is for windows. It is not clear to me how > any exhaustive hardware test can be conducted while windows is booted. > > You can also try to download and build inquisitor from source: > ftp://ftp.altlinux.org/pub/distributions/ALTLinux/Sisyphus/files/SRPMS/inquisitor-standalone-3.1-alt0.svn1418.src.rpm > > > > Unfortunately, the fedora distro does no provide this very important > tool. > You might try to download the CD image directly. It is a live debian CD with inquisitor built-in. http://www.inquisitor.ru/download.html Good luck. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
On 07/05/2010 08:23 PM, Kam Leo wrote: > On Mon, Jul 5, 2010 at 8:08 PM, JD wrote: >> On 07/05/2010 07:28 PM, awrobinson...@nc.rr.com wrote: >>> JDwrote: On 07/05/2010 06:44 PM, awrobinson...@nc.rr.com wrote: > Rick Sewill wrote: >> On 07/05/2010 06:15 PM, awrobinson...@nc.rr.com wrote: >>> Geoffrey Leach wrote: On 07/05/2010 03:28:20 PM, awrobinson...@nc.rr.com wrote: > Geoffrey Leach wrote: >> On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: >>> I am trying to install Fedora on a PC I built. I had Windows XP >>> running on it for more than a year without any apparent problems. > Hardware: > > Motherboard: BIOSTAR TFORCE TF520-A2 AM2 NVIDIA nForce 520 MCP ATX > AMD > Processor: AMD Athlon 64 X2 4200+ Brisbane 2.2GHz Socket AM2 65W > Dual-Core Processor > Video Card: MSI NX8400GS-TD256E GeForce 8400 GS 256MB 64-bit GDDR2 > PCI > Express > Memory: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > Dual Channel > Memory: A-DATA 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > Dual Channel > (6 GB total) > Hard drive: SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s > 3.5" Have you booted it into single user mode? >>> I have not. At least, I haven't since I was trouble shooting issues with >>> disk drives that are no longer in the system. What would I do in single >>> user mode to trouble shoot the current problem? >>> >>> >> See if it will freeze!! > If problems still persist other things to check: > > 1. Revert to default BIOS settings > 2. Dusted off your computer > 3. Re-seat all connections > 4. Verify all fans are in working order > 5. Run with external peripherals, e.g. USB drives. disconnected You might also try these HW test programs: http://www.testmyhardware.com/ Unfortunately, it is for windows. It is not clear to me how any exhaustive hardware test can be conducted while windows is booted. You can also try to download and build inquisitor from source: ftp://ftp.altlinux.org/pub/distributions/ALTLinux/Sisyphus/files/SRPMS/inquisitor-standalone-3.1-alt0.svn1418.src.rpm Unfortunately, the fedora distro does no provide this very important tool. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
On Mon, Jul 5, 2010 at 8:08 PM, JD wrote: > On 07/05/2010 07:28 PM, awrobinson...@nc.rr.com wrote: >> JD wrote: >>> On 07/05/2010 06:44 PM, awrobinson...@nc.rr.com wrote: Rick Sewill wrote: > On 07/05/2010 06:15 PM, awrobinson...@nc.rr.com wrote: >> Geoffrey Leach wrote: >>> On 07/05/2010 03:28:20 PM, awrobinson...@nc.rr.com wrote: Geoffrey Leach wrote: > On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: >> I am trying to install Fedora on a PC I built. I had Windows XP >> running on it for more than a year without any apparent problems. >>> Hardware: Motherboard: BIOSTAR TFORCE TF520-A2 AM2 NVIDIA nForce 520 MCP ATX AMD Processor: AMD Athlon 64 X2 4200+ Brisbane 2.2GHz Socket AM2 65W Dual-Core Processor Video Card: MSI NX8400GS-TD256E GeForce 8400 GS 256MB 64-bit GDDR2 PCI Express Memory: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Memory: A-DATA 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel (6 GB total) Hard drive: SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s 3.5" >>> >>> Have you booted it into single user mode? >>> >> I have not. At least, I haven't since I was trouble shooting issues with >> disk drives that are no longer in the system. What would I do in single user >> mode to trouble shoot the current problem? >> >> > > See if it will freeze!! If problems still persist other things to check: 1. Revert to default BIOS settings 2. Dusted off your computer 3. Re-seat all connections 4. Verify all fans are in working order 5. Run with external peripherals, e.g. USB drives. disconnected -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
On 07/05/2010 07:28 PM, awrobinson...@nc.rr.com wrote: > JD wrote: >>On 07/05/2010 06:44 PM, awrobinson...@nc.rr.com wrote: >>> Rick Sewill wrote: On 07/05/2010 06:15 PM, awrobinson...@nc.rr.com wrote: > Geoffrey Leach wrote: >> On 07/05/2010 03:28:20 PM, awrobinson...@nc.rr.com wrote: >>> Geoffrey Leach wrote: On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: > I am trying to install Fedora on a PC I built. I had Windows XP > running on it for more than a year without any apparent problems. >> >>> Hardware: >>> >>> Motherboard: BIOSTAR TFORCE TF520-A2 AM2 NVIDIA nForce 520 MCP ATX >>> AMD >>> Processor: AMD Athlon 64 X2 4200+ Brisbane 2.2GHz Socket AM2 65W >>> Dual-Core Processor >>> Video Card: MSI NX8400GS-TD256E GeForce 8400 GS 256MB 64-bit GDDR2 >>> PCI >>> Express >>> Memory: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) >>> Dual Channel >>> Memory: A-DATA 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) >>> Dual Channel >>> (6 GB total) >>> Hard drive: SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s >>> 3.5" >> >> Have you booted it into single user mode? >> > I have not. At least, I haven't since I was trouble shooting issues with disk > drives that are no longer in the system. What would I do in single user mode > to trouble shoot the current problem? > > See if it will freeze!! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
JD wrote: > On 07/05/2010 06:44 PM, awrobinson...@nc.rr.com wrote: > > Rick Sewill wrote: > >> On 07/05/2010 06:15 PM, awrobinson...@nc.rr.com wrote: > >>> Geoffrey Leach wrote: > On 07/05/2010 03:28:20 PM, awrobinson...@nc.rr.com wrote: > > Geoffrey Leach wrote: > >> On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: > >>> I am trying to install Fedora on a PC I built. I had Windows XP > >>> running on it for more than a year without any apparent problems. > > > Hardware: > > > > Motherboard: BIOSTAR TFORCE TF520-A2 AM2 NVIDIA nForce 520 MCP ATX > > AMD > > Processor: AMD Athlon 64 X2 4200+ Brisbane 2.2GHz Socket AM2 65W > > Dual-Core Processor > > Video Card: MSI NX8400GS-TD256E GeForce 8400 GS 256MB 64-bit GDDR2 > > PCI > > Express > > Memory: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > > Dual Channel > > Memory: A-DATA 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > > Dual Channel > > (6 GB total) > > Hard drive: SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s > > 3.5" > > > > Have you booted it into single user mode? > I have not. At least, I haven't since I was trouble shooting issues with disk drives that are no longer in the system. What would I do in single user mode to trouble shoot the current problem? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
On 07/05/2010 06:44 PM, awrobinson...@nc.rr.com wrote: > Rick Sewill wrote: >> On 07/05/2010 06:15 PM, awrobinson...@nc.rr.com wrote: >>> Geoffrey Leach wrote: On 07/05/2010 03:28:20 PM, awrobinson...@nc.rr.com wrote: > Geoffrey Leach wrote: >> On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: >>> I am trying to install Fedora on a PC I built. I had Windows XP >>> running on it for more than a year without any apparent problems. > Hardware: > > Motherboard: BIOSTAR TFORCE TF520-A2 AM2 NVIDIA nForce 520 MCP ATX > AMD > Processor: AMD Athlon 64 X2 4200+ Brisbane 2.2GHz Socket AM2 65W > Dual-Core Processor > Video Card: MSI NX8400GS-TD256E GeForce 8400 GS 256MB 64-bit GDDR2 > PCI > Express > Memory: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > Dual Channel > Memory: A-DATA 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > Dual Channel > (6 GB total) > Hard drive: SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s > 3.5" I wasn't able to discover anyything about Fedora compatibility with your Biostar MB, so you might well be in unexplored territory. It appears that the hardware compatibility lists for Fedora are no longer maintained, alas. The Nvidia FOSS driver for X (NV) might be a problem for you. I suggest you stay at runlevel 3 until your problems are resolved. If R/L 5 causes you a problem after that, try the proprietary driver. I've found that it works well. You didn't say where your Fedora came from. Are you sure that it's clean? >>> Pretty sure. I used the netinstall CD for both 13 and 12. I checked the >>> md256sum for the Fedora 13 iso. I downloaded both from the Fedora site, so >>> they came from a Fedora-specific mirror. And there is the fact that I got >>> the same behaviour from both. >>> >>> Again, please keep the questions coming. I really want to resolve this. >>> >> May I suggest looking at the URL: >> http://fedoraproject.org/wiki/KernelCommonProblems >> >> It is where I would start when trying to debug Fedora panic/crash problems. >> >> > From this webpage, in the "Crashes/Hangs" section, they seem to suggest >> setting kernel boot parameters to try to narrow the problem or work >> around the problem. >> >> For more information on kernel boot parameters, the web page says, >> "The full list of kernel options is in the file >> /usr/share/doc/kernel-doc-/Documentation/kernel-parameters.txt, >> which is installed with the kernel-doc package" >> >> I assume one can find the correct kernel-parameters.txt file either >> looking in the local file system assuming Fedora is usable -or- >> searching the internet for "kernel-parameters.txt" >> If one finds it with an internet search, please make sure the >> kernel-parameters.txt more or less match the correct version of the >> Fedora kernel. >> >> Having said the above, if you suspect an acpi or apic problem, >> the URL: http://fedoraproject.org/wiki/KernelCommonProblems >> says, >> "acpi=off is a big hammer, and if that works, narrowing down by trying >> pci=noacpi instead may yield clues" >> It also says, "nolapic and noapic are sometimes useful" >> >> You need to look at kernel-parameters.txt to see what these parameters >> do before using them. Please don't try a parameter just to try it. >> Using a kernel boot parameter could make matters worse. >> >> If you suspect a video problem...and I believe they are trying to phase >> out support for the kernel boot parameter, "nomodeset"--I believe they >> have already phased out support for Intel, but still have some code >> support for AMD which you have, I would still try that boot parameter to >> see what happens. You will need to search the internet to find out >> about the parameter "nomodeset". I don't consider using "nomodeset" as >> a solution, but rather as a way to gather a data point or work around a >> problem. >> >> I would suggest trying one kernel boot parameter at a time, with the >> hope of better isolating what is happening if a parameter seems to work. >> >> If you discover a kernel boot parameter that acts as a workaround, it >> may or may not provide a clue, to start isolating what is happening. >> >> I would also look at the /var/log/messages for clues what was happening >> a little before the failure/panic...you may hate me for suggesting >> looking at /var/log/messages, sometimes there is nothing there and >> sometimes there is too much there. >> >> If you find a kernel boot parameter that works around the problem, >> you will need to decide whether or not to write a bugzilla bug report. >> If you do not find a kernel boot parameter, you may still wish to write >> a bugzilla bug report. A bugzilla bug report is the way, I believe, >> for communcating problems with the maintainers. I hope they ask you for >> information, and I hope they suggest how to get what t
Re: Help me troubleshoot this problem
On 07/05/2010 03:07 PM, awrobinson...@nc.rr.com wrote: > JD wrote: >>On 07/05/2010 01:27 PM, awrobinson...@nc.rr.com wrote: >>> I am trying to install Fedora on a PC I built. I had Windows XP running on >>> it for more than a year without any apparent problems. I put a new hard >>> drive in the box and tried Fedora 13 and now Fedora 12. It seems to freeze >>> at random or panic. I suspect hardware or a driver. I've been pulling >>> cards, but it seems to happen regardless of what combination I have in the >>> box. I've tried Gnome, KDE, and now init 3, but it seems to happen with the >>> same frequency. I left it on last night and found these messages on the >>> screen this morning: >>> >>> [] apic_timer_interrupt+0x31/0x38 >>> [drm:drm_fb_helper_panic] *ERROR* panic occurred, switching back to text >>> console >>> ---[ cut here ]-- >>> WARNING: at arch/x86/kernel/smp.c:117 native_smp_send_reschedule+0x23/0x46() >>> Hardware name: TF520-A2+06a/0x01 >>> Modules linked in hwmon_vid sunrpc cpufreq_ondemand powernow_k8 ip6t_REJECT >>> nf_conntrack_ipv6 ip5table_filter ip6_tables ipv6 dm_multipath uinput >>> snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq >>> snd_seq_device snd_pcm snd_timer ppdev parport_pc snd parport soundcore >>> r8169 snd_page_alloc i2c_nforce2 k8temp mii ata_generic pata_acpi pata_amd >>> nouveau ttm drm_kms_helper drm i2c_algo_bit i2c_core [last uploaded: >>> i2c_dev] >>> Pid: 1517, comm: abrtd Tainted: G D 2.6.32.14-127.fc12.i686.PAE #1 >>> Call Trace: >>> [] warn_slowpath_common >>> [] ? native_smp_send_reschedule+0x23/0x46 >>> [] warn_slow_path_null+0x12/0x15 >>> [] native_smp_sned_reschedule+0x23/0x46 >>> [] resched_task_0x5c/0x5f >>> [] check_preempt_curr_idle+0x13/0x15 >>> [] check_preempt_curr+0x15/0x18 >>> [] try_to_wake_up+0x14/0x34 >>> [] default_wake_function+0x14/0x34 >>> [] __wake_up_comon_0x39/0x61 >>> [] __wake_up+0x23/0x40 >>> [] printk_tick+0x37/0x3a >>> [] update_process_times+0x37/0x48 >>> [] __run_hrtimer_0xa0/0xef >>> [] ? tick_sched_timer_0x0,0xa0 >>> [] hrtimer_interrupt_0xe0/0x1d5 >>> [] smp_apic_timer_interrupt_0x68/0x7b >>> [] apic_timer_interrupt_0x31/0x38 >>> [] ? panic+0xc7/0xe7 >>> [] oops_end+0x97/0xa6 >>> [] no_context+0x13b/ox145 >>> [] __bad_area_nosemaphore+0xec/0xf4 >>> [] ? do_page_fault+0x0/0x29f >>> [] bad_area_nosemaphore+0x13/0x15 >>> [] do_page_fault_0x139/0x29f >>> [] ? do_page_fault_0x0/0x29f >>> [] error_code+0x73/0x78 >>> [] ? run_timer_softirq+0xd8/0x1f0 >>> [] __do_softirq_0xb1/0x157 >>> [] do_softirq_0x36/0x41 >>> [] irq_exit_0x2e/0x61 >>> [] smp_apic_timer_interrupt+0x6d/0x7b >>> [] apic_timer_interrupt_0x31/0x38 >>> ---[ end trace 65e050a46d3d088c ]--- >>> >>> I typed these from the screen, so I cannot swear for the accuracy of every >>> character. I've looked for these type of messages in the message log and >>> the /var/log directory, but haven't found them. I don't see any indications >>> of why it freezes in the message log when it does. I looked for core files >>> in a few places but found none. >>> >>> I doubt I've given enough info to pinpoint the source of the problem. So my >>> questions revolve around how to troubleshoot this problem. Where would I >>> look for usable information? What experiments could I try that might point >>> to the source of the problem? Would a core file help? If so, how do I get >>> the system to generate one? How do I figure this one out? >>> >>> Thanks! >>> >>> Andrew Robinson >>> >> Is the panic output the same every time? i.e. is it always the apic timer? >> If it is, it sounds like you might have a hardware proplem on the >> motherboard. >> >> By the way, which fedora version have you installed? >> If not F13, have you tried F13, and then done a full update? >> -- > Since I have not been able to capture the output of the panics, I don't know > if it fails in the same place every time. That was intended to be one of my > questions. How do I capture the panic output? When it just freezes, how do I > find info on why? > > Yes, I tried Fedora 13 first. When I ran into the problems, I tried Fedora > 12. When I experienced the same freezes and panics, I decided it was not > version specific. > > Thanks. Please keep the questions coming. > > Andrew I would start by eliminating as many davices as you can, but still be able to boot linux and have a console. One thing you might try is eliminate the graphics card and use the serial port which you connect, via a null modem cable to a second PC - where you can then run minicom on the second port's pc to capture the failing pc's output. minicom allows you to capture everything into a file. If you do not have any PCI cards and all your devices are built into the motherboard, you might then try to disable them in BIOS if your BIOS provides such a feature. For examle, some BIOS'es let you disable USB chipsets, or disable the raid and use the plain or plain sata. H
Re: Help me troubleshoot this problem
Rick Sewill wrote: > On 07/05/2010 06:15 PM, awrobinson...@nc.rr.com wrote: > > > > Geoffrey Leach wrote: > >> On 07/05/2010 03:28:20 PM, awrobinson...@nc.rr.com wrote: > >>> > >>> Geoffrey Leach wrote: > On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: > > I am trying to install Fedora on a PC I built. I had Windows XP > > running on it for more than a year without any apparent problems. > >> > >>> > >>> Hardware: > >>> > >>> Motherboard: BIOSTAR TFORCE TF520-A2 AM2 NVIDIA nForce 520 MCP ATX > >>> AMD > >>> Processor: AMD Athlon 64 X2 4200+ Brisbane 2.2GHz Socket AM2 65W > >>> Dual-Core Processor > >>> Video Card: MSI NX8400GS-TD256E GeForce 8400 GS 256MB 64-bit GDDR2 > >>> PCI > >>> Express > >>> Memory: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > >>> Dual Channel > >>> Memory: A-DATA 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > >>> Dual Channel > >>> (6 GB total) > >>> Hard drive: SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s > >>> 3.5" > >> > >> I wasn't able to discover anyything about Fedora compatibility with > >> your Biostar MB, so you might well be in unexplored territory. It > >> appears that the hardware compatibility lists for Fedora are no longer > >> maintained, alas. > >> > >> The Nvidia FOSS driver for X (NV) might be a problem for you. I suggest > >> you stay at runlevel 3 until your problems are resolved. If R/L 5 > >> causes you a problem after that, try the proprietary driver. I've found > >> that it works well. > >> > >> You didn't say where your Fedora came from. Are you sure that it's > >> clean? > >> > > > > Pretty sure. I used the netinstall CD for both 13 and 12. I checked the > > md256sum for the Fedora 13 iso. I downloaded both from the Fedora site, so > > they came from a Fedora-specific mirror. And there is the fact that I got > > the same behaviour from both. > > > > Again, please keep the questions coming. I really want to resolve this. > > > > May I suggest looking at the URL: > http://fedoraproject.org/wiki/KernelCommonProblems > > It is where I would start when trying to debug Fedora panic/crash problems. > > >From this webpage, in the "Crashes/Hangs" section, they seem to suggest > setting kernel boot parameters to try to narrow the problem or work > around the problem. > > For more information on kernel boot parameters, the web page says, > "The full list of kernel options is in the file > /usr/share/doc/kernel-doc-/Documentation/kernel-parameters.txt, > which is installed with the kernel-doc package" > > I assume one can find the correct kernel-parameters.txt file either > looking in the local file system assuming Fedora is usable -or- > searching the internet for "kernel-parameters.txt" > If one finds it with an internet search, please make sure the > kernel-parameters.txt more or less match the correct version of the > Fedora kernel. > > Having said the above, if you suspect an acpi or apic problem, > the URL: http://fedoraproject.org/wiki/KernelCommonProblems > says, > "acpi=off is a big hammer, and if that works, narrowing down by trying > pci=noacpi instead may yield clues" > It also says, "nolapic and noapic are sometimes useful" > > You need to look at kernel-parameters.txt to see what these parameters > do before using them. Please don't try a parameter just to try it. > Using a kernel boot parameter could make matters worse. > > If you suspect a video problem...and I believe they are trying to phase > out support for the kernel boot parameter, "nomodeset"--I believe they > have already phased out support for Intel, but still have some code > support for AMD which you have, I would still try that boot parameter to > see what happens. You will need to search the internet to find out > about the parameter "nomodeset". I don't consider using "nomodeset" as > a solution, but rather as a way to gather a data point or work around a > problem. > > I would suggest trying one kernel boot parameter at a time, with the > hope of better isolating what is happening if a parameter seems to work. > > If you discover a kernel boot parameter that acts as a workaround, it > may or may not provide a clue, to start isolating what is happening. > > I would also look at the /var/log/messages for clues what was happening > a little before the failure/panic...you may hate me for suggesting > looking at /var/log/messages, sometimes there is nothing there and > sometimes there is too much there. > > If you find a kernel boot parameter that works around the problem, > you will need to decide whether or not to write a bugzilla bug report. > If you do not find a kernel boot parameter, you may still wish to write > a bugzilla bug report. A bugzilla bug report is the way, I believe, > for communcating problems with the maintainers. I hope they ask you for > information, and I hope they suggest how to get what they ask for. > I would encourage you to write a bugzilla bug rep
Re: Help me troubleshoot this problem
On 07/05/2010 06:15 PM, awrobinson...@nc.rr.com wrote: > > Geoffrey Leach wrote: >> On 07/05/2010 03:28:20 PM, awrobinson...@nc.rr.com wrote: >>> >>> Geoffrey Leach wrote: On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: > I am trying to install Fedora on a PC I built. I had Windows XP > running on it for more than a year without any apparent problems. >> >>> >>> Hardware: >>> >>> Motherboard: BIOSTAR TFORCE TF520-A2 AM2 NVIDIA nForce 520 MCP ATX >>> AMD >>> Processor: AMD Athlon 64 X2 4200+ Brisbane 2.2GHz Socket AM2 65W >>> Dual-Core Processor >>> Video Card: MSI NX8400GS-TD256E GeForce 8400 GS 256MB 64-bit GDDR2 >>> PCI >>> Express >>> Memory: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) >>> Dual Channel >>> Memory: A-DATA 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) >>> Dual Channel >>> (6 GB total) >>> Hard drive: SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s >>> 3.5" >> >> I wasn't able to discover anyything about Fedora compatibility with >> your Biostar MB, so you might well be in unexplored territory. It >> appears that the hardware compatibility lists for Fedora are no longer >> maintained, alas. >> >> The Nvidia FOSS driver for X (NV) might be a problem for you. I suggest >> you stay at runlevel 3 until your problems are resolved. If R/L 5 >> causes you a problem after that, try the proprietary driver. I've found >> that it works well. >> >> You didn't say where your Fedora came from. Are you sure that it's >> clean? >> > > Pretty sure. I used the netinstall CD for both 13 and 12. I checked the > md256sum for the Fedora 13 iso. I downloaded both from the Fedora site, so > they came from a Fedora-specific mirror. And there is the fact that I got the > same behaviour from both. > > Again, please keep the questions coming. I really want to resolve this. > May I suggest looking at the URL: http://fedoraproject.org/wiki/KernelCommonProblems It is where I would start when trying to debug Fedora panic/crash problems. >From this webpage, in the "Crashes/Hangs" section, they seem to suggest setting kernel boot parameters to try to narrow the problem or work around the problem. For more information on kernel boot parameters, the web page says, "The full list of kernel options is in the file /usr/share/doc/kernel-doc-/Documentation/kernel-parameters.txt, which is installed with the kernel-doc package" I assume one can find the correct kernel-parameters.txt file either looking in the local file system assuming Fedora is usable -or- searching the internet for "kernel-parameters.txt" If one finds it with an internet search, please make sure the kernel-parameters.txt more or less match the correct version of the Fedora kernel. Having said the above, if you suspect an acpi or apic problem, the URL: http://fedoraproject.org/wiki/KernelCommonProblems says, "acpi=off is a big hammer, and if that works, narrowing down by trying pci=noacpi instead may yield clues" It also says, "nolapic and noapic are sometimes useful" You need to look at kernel-parameters.txt to see what these parameters do before using them. Please don't try a parameter just to try it. Using a kernel boot parameter could make matters worse. If you suspect a video problem...and I believe they are trying to phase out support for the kernel boot parameter, "nomodeset"--I believe they have already phased out support for Intel, but still have some code support for AMD which you have, I would still try that boot parameter to see what happens. You will need to search the internet to find out about the parameter "nomodeset". I don't consider using "nomodeset" as a solution, but rather as a way to gather a data point or work around a problem. I would suggest trying one kernel boot parameter at a time, with the hope of better isolating what is happening if a parameter seems to work. If you discover a kernel boot parameter that acts as a workaround, it may or may not provide a clue, to start isolating what is happening. I would also look at the /var/log/messages for clues what was happening a little before the failure/panic...you may hate me for suggesting looking at /var/log/messages, sometimes there is nothing there and sometimes there is too much there. If you find a kernel boot parameter that works around the problem, you will need to decide whether or not to write a bugzilla bug report. If you do not find a kernel boot parameter, you may still wish to write a bugzilla bug report. A bugzilla bug report is the way, I believe, for communcating problems with the maintainers. I hope they ask you for information, and I hope they suggest how to get what they ask for. I would encourage you to write a bugzilla bug report, unless the problem is a hardware failure, in which case, I don't know what to do. Sometimes, if a problem is a hardware failure, nothing can be done. Sometimes, if a problem is a hardware failure, the software can be more graceful when the
Re: Help me troubleshoot this problem
On Mon, Jul 5, 2010 at 4:15 PM, wrote: > > Geoffrey Leach wrote: >> On 07/05/2010 03:28:20 PM, awrobinson...@nc.rr.com wrote: >> > >> > Geoffrey Leach wrote: >> > > On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: >> > > > I am trying to install Fedora on a PC I built. I had Windows XP >> > > > running on it for more than a year without any apparent problems. >> >> > >> > Hardware: >> > >> > Motherboard: BIOSTAR TFORCE TF520-A2 AM2 NVIDIA nForce 520 MCP ATX >> > AMD >> > Processor: AMD Athlon 64 X2 4200+ Brisbane 2.2GHz Socket AM2 65W >> > Dual-Core Processor >> > Video Card: MSI NX8400GS-TD256E GeForce 8400 GS 256MB 64-bit GDDR2 >> > PCI >> > Express >> > Memory: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) >> > Dual Channel >> > Memory: A-DATA 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) >> > Dual Channel >> > (6 GB total) >> > Hard drive: SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s >> > 3.5" >> >> I wasn't able to discover anyything about Fedora compatibility with >> your Biostar MB, so you might well be in unexplored territory. It >> appears that the hardware compatibility lists for Fedora are no longer >> maintained, alas. >> >> The Nvidia FOSS driver for X (NV) might be a problem for you. I suggest >> you stay at runlevel 3 until your problems are resolved. If R/L 5 >> causes you a problem after that, try the proprietary driver. I've found >> that it works well. >> >> You didn't say where your Fedora came from. Are you sure that it's >> clean? >> > > Pretty sure. I used the netinstall CD for both 13 and 12. I checked the > md256sum for the Fedora 13 iso. I downloaded both from the Fedora site, so > they came from a Fedora-specific mirror. And there is the fact that I got the > same behaviour from both. > > Again, please keep the questions coming. I really want to resolve this. > Try adding noapic to grub. Other options and suggestions are available at http://fedoraproject.org/wiki/KernelCommonProblems -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
Geoffrey Leach wrote: > On 07/05/2010 03:28:20 PM, awrobinson...@nc.rr.com wrote: > > > > Geoffrey Leach wrote: > > > On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: > > > > I am trying to install Fedora on a PC I built. I had Windows XP > > > > running on it for more than a year without any apparent problems. > > > > > Hardware: > > > > Motherboard: BIOSTAR TFORCE TF520-A2 AM2 NVIDIA nForce 520 MCP ATX > > AMD > > Processor: AMD Athlon 64 X2 4200+ Brisbane 2.2GHz Socket AM2 65W > > Dual-Core Processor > > Video Card: MSI NX8400GS-TD256E GeForce 8400 GS 256MB 64-bit GDDR2 > > PCI > > Express > > Memory: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > > Dual Channel > > Memory: A-DATA 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > > Dual Channel > > (6 GB total) > > Hard drive: SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s > > 3.5" > > I wasn't able to discover anyything about Fedora compatibility with > your Biostar MB, so you might well be in unexplored territory. It > appears that the hardware compatibility lists for Fedora are no longer > maintained, alas. > > The Nvidia FOSS driver for X (NV) might be a problem for you. I suggest > you stay at runlevel 3 until your problems are resolved. If R/L 5 > causes you a problem after that, try the proprietary driver. I've found > that it works well. > > You didn't say where your Fedora came from. Are you sure that it's > clean? > Pretty sure. I used the netinstall CD for both 13 and 12. I checked the md256sum for the Fedora 13 iso. I downloaded both from the Fedora site, so they came from a Fedora-specific mirror. And there is the fact that I got the same behaviour from both. Again, please keep the questions coming. I really want to resolve this. > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
On 07/05/2010 03:28:20 PM, awrobinson...@nc.rr.com wrote: > > Geoffrey Leach wrote: > > On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: > > > I am trying to install Fedora on a PC I built. I had Windows XP > > > running on it for more than a year without any apparent problems. > > Hardware: > > Motherboard: BIOSTAR TFORCE TF520-A2 AM2 NVIDIA nForce 520 MCP ATX > AMD > Processor: AMD Athlon 64 X2 4200+ Brisbane 2.2GHz Socket AM2 65W > Dual-Core Processor > Video Card: MSI NX8400GS-TD256E GeForce 8400 GS 256MB 64-bit GDDR2 > PCI > Express > Memory: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > Dual Channel > Memory: A-DATA 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) > Dual Channel > (6 GB total) > Hard drive: SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s > 3.5" I wasn't able to discover anyything about Fedora compatibility with your Biostar MB, so you might well be in unexplored territory. It appears that the hardware compatibility lists for Fedora are no longer maintained, alas. The Nvidia FOSS driver for X (NV) might be a problem for you. I suggest you stay at runlevel 3 until your problems are resolved. If R/L 5 causes you a problem after that, try the proprietary driver. I've found that it works well. You didn't say where your Fedora came from. Are you sure that it's clean? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
Geoffrey Leach wrote: > On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: > > I am trying to install Fedora on a PC I built. I had Windows XP > > running on it for more than a year without any apparent problems. I > > put a new hard drive in the box and tried Fedora 13 and now Fedora > > 12. > [snip] > > Andrew, you have not provided nearly enough info. > > First, stick with Fedora 13. That's what most of us will be using. > > First, what harware are you running? MB, CPU, GPU, memory (how much) in > particular. > > Second, what HD are you using? > > Third, where did you get your Fedora? D/L, DVD, ... > > You might wish to try Memtest86+ (http://www.memtest.org) > and the DVD validator that came with the dvd, if that's the case. You > might also want to try the mfg's disk diagnostics as well. Start from > scratch. > > You're getting a kernel panic, so it's likely that there's something in > your hardware that is inappropiate for the kernel that was installed. > Hardware: Motherboard: BIOSTAR TFORCE TF520-A2 AM2 NVIDIA nForce 520 MCP ATX AMD Processor: AMD Athlon 64 X2 4200+ Brisbane 2.2GHz Socket AM2 65W Dual-Core Processor Video Card: MSI NX8400GS-TD256E GeForce 8400 GS 256MB 64-bit GDDR2 PCI Express Memory: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Memory: A-DATA 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel (6 GB total) Hard drive: SAMSUNG EcoGreen F2 HD103SI 1TB 5400 RPM SATA 3.0Gb/s 3.5" Internal Power supply: RAIDMAX Blackstone series RX-700AC 700W Continuous Power ATX12V V2.3 I would like to end up with Fedora 13. Since I saw the same problems with both versions, I figured the version of Fedora was not the problem. Do you know if the panic info gets saved somewhere? Thanks! Please keep the questions coming. Andrew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
JD wrote: > On 07/05/2010 01:27 PM, awrobinson...@nc.rr.com wrote: > > I am trying to install Fedora on a PC I built. I had Windows XP running on > > it for more than a year without any apparent problems. I put a new hard > > drive in the box and tried Fedora 13 and now Fedora 12. It seems to freeze > > at random or panic. I suspect hardware or a driver. I've been pulling > > cards, but it seems to happen regardless of what combination I have in the > > box. I've tried Gnome, KDE, and now init 3, but it seems to happen with the > > same frequency. I left it on last night and found these messages on the > > screen this morning: > > > > [] apic_timer_interrupt+0x31/0x38 > > [drm:drm_fb_helper_panic] *ERROR* panic occurred, switching back to text > > console > > ---[ cut here ]-- > > WARNING: at arch/x86/kernel/smp.c:117 native_smp_send_reschedule+0x23/0x46() > > Hardware name: TF520-A2+06a/0x01 > > Modules linked in hwmon_vid sunrpc cpufreq_ondemand powernow_k8 ip6t_REJECT > > nf_conntrack_ipv6 ip5table_filter ip6_tables ipv6 dm_multipath uinput > > snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq > > snd_seq_device snd_pcm snd_timer ppdev parport_pc snd parport soundcore > > r8169 snd_page_alloc i2c_nforce2 k8temp mii ata_generic pata_acpi pata_amd > > nouveau ttm drm_kms_helper drm i2c_algo_bit i2c_core [last uploaded: > > i2c_dev] > > Pid: 1517, comm: abrtd Tainted: G D 2.6.32.14-127.fc12.i686.PAE #1 > > Call Trace: > > [] warn_slowpath_common > > [] ? native_smp_send_reschedule+0x23/0x46 > > [] warn_slow_path_null+0x12/0x15 > > [] native_smp_sned_reschedule+0x23/0x46 > > [] resched_task_0x5c/0x5f > > [] check_preempt_curr_idle+0x13/0x15 > > [] check_preempt_curr+0x15/0x18 > > [] try_to_wake_up+0x14/0x34 > > [] default_wake_function+0x14/0x34 > > [] __wake_up_comon_0x39/0x61 > > [] __wake_up+0x23/0x40 > > [] printk_tick+0x37/0x3a > > [] update_process_times+0x37/0x48 > > [] __run_hrtimer_0xa0/0xef > > [] ? tick_sched_timer_0x0,0xa0 > > [] hrtimer_interrupt_0xe0/0x1d5 > > [] smp_apic_timer_interrupt_0x68/0x7b > > [] apic_timer_interrupt_0x31/0x38 > > [] ? panic+0xc7/0xe7 > > [] oops_end+0x97/0xa6 > > [] no_context+0x13b/ox145 > > [] __bad_area_nosemaphore+0xec/0xf4 > > [] ? do_page_fault+0x0/0x29f > > [] bad_area_nosemaphore+0x13/0x15 > > [] do_page_fault_0x139/0x29f > > [] ? do_page_fault_0x0/0x29f > > [] error_code+0x73/0x78 > > [] ? run_timer_softirq+0xd8/0x1f0 > > [] __do_softirq_0xb1/0x157 > > [] do_softirq_0x36/0x41 > > [] irq_exit_0x2e/0x61 > > [] smp_apic_timer_interrupt+0x6d/0x7b > > [] apic_timer_interrupt_0x31/0x38 > > ---[ end trace 65e050a46d3d088c ]--- > > > > I typed these from the screen, so I cannot swear for the accuracy of every > > character. I've looked for these type of messages in the message log and > > the /var/log directory, but haven't found them. I don't see any indications > > of why it freezes in the message log when it does. I looked for core files > > in a few places but found none. > > > > I doubt I've given enough info to pinpoint the source of the problem. So my > > questions revolve around how to troubleshoot this problem. Where would I > > look for usable information? What experiments could I try that might point > > to the source of the problem? Would a core file help? If so, how do I get > > the system to generate one? How do I figure this one out? > > > > Thanks! > > > > Andrew Robinson > > > Is the panic output the same every time? i.e. is it always the apic timer? > If it is, it sounds like you might have a hardware proplem on the > motherboard. > > By the way, which fedora version have you installed? > If not F13, have you tried F13, and then done a full update? > -- Since I have not been able to capture the output of the panics, I don't know if it fails in the same place every time. That was intended to be one of my questions. How do I capture the panic output? When it just freezes, how do I find info on why? Yes, I tried Fedora 13 first. When I ran into the problems, I tried Fedora 12. When I experienced the same freezes and panics, I decided it was not version specific. Thanks. Please keep the questions coming. Andrew -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
On 07/05/2010 01:27:01 PM, awrobinson...@nc.rr.com wrote: > I am trying to install Fedora on a PC I built. I had Windows XP > running on it for more than a year without any apparent problems. I > put a new hard drive in the box and tried Fedora 13 and now Fedora > 12. [snip] Andrew, you have not provided nearly enough info. First, stick with Fedora 13. That's what most of us will be using. First, what harware are you running? MB, CPU, GPU, memory (how much) in particular. Second, what HD are you using? Third, where did you get your Fedora? D/L, DVD, ... You might wish to try Memtest86+ (http://www.memtest.org) and the DVD validator that came with the dvd, if that's the case. You might also want to try the mfg's disk diagnostics as well. Start from scratch. You're getting a kernel panic, so it's likely that there's something in your hardware that is inappropiate for the kernel that was installed. Good luck. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Help me troubleshoot this problem
On 07/05/2010 01:27 PM, awrobinson...@nc.rr.com wrote: > I am trying to install Fedora on a PC I built. I had Windows XP running on it > for more than a year without any apparent problems. I put a new hard drive in > the box and tried Fedora 13 and now Fedora 12. It seems to freeze at random > or panic. I suspect hardware or a driver. I've been pulling cards, but it > seems to happen regardless of what combination I have in the box. I've tried > Gnome, KDE, and now init 3, but it seems to happen with the same frequency. I > left it on last night and found these messages on the screen this morning: > > [] apic_timer_interrupt+0x31/0x38 > [drm:drm_fb_helper_panic] *ERROR* panic occurred, switching back to text > console > ---[ cut here ]-- > WARNING: at arch/x86/kernel/smp.c:117 native_smp_send_reschedule+0x23/0x46() > Hardware name: TF520-A2+06a/0x01 > Modules linked in hwmon_vid sunrpc cpufreq_ondemand powernow_k8 ip6t_REJECT > nf_conntrack_ipv6 ip5table_filter ip6_tables ipv6 dm_multipath uinput > snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq > snd_seq_device snd_pcm snd_timer ppdev parport_pc snd parport soundcore r8169 > snd_page_alloc i2c_nforce2 k8temp mii ata_generic pata_acpi pata_amd nouveau > ttm drm_kms_helper drm i2c_algo_bit i2c_core [last uploaded: i2c_dev] > Pid: 1517, comm: abrtd Tainted: G D 2.6.32.14-127.fc12.i686.PAE #1 > Call Trace: > [] warn_slowpath_common > [] ? native_smp_send_reschedule+0x23/0x46 > [] warn_slow_path_null+0x12/0x15 > [] native_smp_sned_reschedule+0x23/0x46 > [] resched_task_0x5c/0x5f > [] check_preempt_curr_idle+0x13/0x15 > [] check_preempt_curr+0x15/0x18 > [] try_to_wake_up+0x14/0x34 > [] default_wake_function+0x14/0x34 > [] __wake_up_comon_0x39/0x61 > [] __wake_up+0x23/0x40 > [] printk_tick+0x37/0x3a > [] update_process_times+0x37/0x48 > [] __run_hrtimer_0xa0/0xef > [] ? tick_sched_timer_0x0,0xa0 > [] hrtimer_interrupt_0xe0/0x1d5 > [] smp_apic_timer_interrupt_0x68/0x7b > [] apic_timer_interrupt_0x31/0x38 > [] ? panic+0xc7/0xe7 > [] oops_end+0x97/0xa6 > [] no_context+0x13b/ox145 > [] __bad_area_nosemaphore+0xec/0xf4 > [] ? do_page_fault+0x0/0x29f > [] bad_area_nosemaphore+0x13/0x15 > [] do_page_fault_0x139/0x29f > [] ? do_page_fault_0x0/0x29f > [] error_code+0x73/0x78 > [] ? run_timer_softirq+0xd8/0x1f0 > [] __do_softirq_0xb1/0x157 > [] do_softirq_0x36/0x41 > [] irq_exit_0x2e/0x61 > [] smp_apic_timer_interrupt+0x6d/0x7b > [] apic_timer_interrupt_0x31/0x38 > ---[ end trace 65e050a46d3d088c ]--- > > I typed these from the screen, so I cannot swear for the accuracy of every > character. I've looked for these type of messages in the message log and the > /var/log directory, but haven't found them. I don't see any indications of > why it freezes in the message log when it does. I looked for core files in a > few places but found none. > > I doubt I've given enough info to pinpoint the source of the problem. So my > questions revolve around how to troubleshoot this problem. Where would I look > for usable information? What experiments could I try that might point to the > source of the problem? Would a core file help? If so, how do I get the system > to generate one? How do I figure this one out? > > Thanks! > > Andrew Robinson > Is the panic output the same every time? i.e. is it always the apic timer? If it is, it sounds like you might have a hardware proplem on the motherboard. By the way, which fedora version have you installed? If not F13, have you tried F13, and then done a full update? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Help me troubleshoot this problem
I am trying to install Fedora on a PC I built. I had Windows XP running on it for more than a year without any apparent problems. I put a new hard drive in the box and tried Fedora 13 and now Fedora 12. It seems to freeze at random or panic. I suspect hardware or a driver. I've been pulling cards, but it seems to happen regardless of what combination I have in the box. I've tried Gnome, KDE, and now init 3, but it seems to happen with the same frequency. I left it on last night and found these messages on the screen this morning: [] apic_timer_interrupt+0x31/0x38 [drm:drm_fb_helper_panic] *ERROR* panic occurred, switching back to text console ---[ cut here ]-- WARNING: at arch/x86/kernel/smp.c:117 native_smp_send_reschedule+0x23/0x46() Hardware name: TF520-A2+06a/0x01 Modules linked in hwmon_vid sunrpc cpufreq_ondemand powernow_k8 ip6t_REJECT nf_conntrack_ipv6 ip5table_filter ip6_tables ipv6 dm_multipath uinput snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer ppdev parport_pc snd parport soundcore r8169 snd_page_alloc i2c_nforce2 k8temp mii ata_generic pata_acpi pata_amd nouveau ttm drm_kms_helper drm i2c_algo_bit i2c_core [last uploaded: i2c_dev] Pid: 1517, comm: abrtd Tainted: G D 2.6.32.14-127.fc12.i686.PAE #1 Call Trace: [] warn_slowpath_common [] ? native_smp_send_reschedule+0x23/0x46 [] warn_slow_path_null+0x12/0x15 [] native_smp_sned_reschedule+0x23/0x46 [] resched_task_0x5c/0x5f [] check_preempt_curr_idle+0x13/0x15 [] check_preempt_curr+0x15/0x18 [] try_to_wake_up+0x14/0x34 [] default_wake_function+0x14/0x34 [] __wake_up_comon_0x39/0x61 [] __wake_up+0x23/0x40 [] printk_tick+0x37/0x3a [] update_process_times+0x37/0x48 [] __run_hrtimer_0xa0/0xef [] ? tick_sched_timer_0x0,0xa0 [] hrtimer_interrupt_0xe0/0x1d5 [] smp_apic_timer_interrupt_0x68/0x7b [] apic_timer_interrupt_0x31/0x38 [] ? panic+0xc7/0xe7 [] oops_end+0x97/0xa6 [] no_context+0x13b/ox145 [] __bad_area_nosemaphore+0xec/0xf4 [] ? do_page_fault+0x0/0x29f [] bad_area_nosemaphore+0x13/0x15 [] do_page_fault_0x139/0x29f [] ? do_page_fault_0x0/0x29f [] error_code+0x73/0x78 [] ? run_timer_softirq+0xd8/0x1f0 [] __do_softirq_0xb1/0x157 [] do_softirq_0x36/0x41 [] irq_exit_0x2e/0x61 [] smp_apic_timer_interrupt+0x6d/0x7b [] apic_timer_interrupt_0x31/0x38 ---[ end trace 65e050a46d3d088c ]--- I typed these from the screen, so I cannot swear for the accuracy of every character. I've looked for these type of messages in the message log and the /var/log directory, but haven't found them. I don't see any indications of why it freezes in the message log when it does. I looked for core files in a few places but found none. I doubt I've given enough info to pinpoint the source of the problem. So my questions revolve around how to troubleshoot this problem. Where would I look for usable information? What experiments could I try that might point to the source of the problem? Would a core file help? If so, how do I get the system to generate one? How do I figure this one out? Thanks! Andrew Robinson -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
