Re: kernel panic FreeBSD 7.0 - Xorg
On Monday 12 of May 2008 22:22:12 Roland Smith wrote: It might also be a hardware problem. Testing the RAM would be a good place to start. I bought new RAM and tested it with 'memtest' and now is OK (no error was found). Hover I still got kernel panic when I do: # Xorg -configure # Xorg -config /root/xorg.conf.new what is going on? What else can cause such behavior. As I mentioned previously Debian works great on this computer. Maybe it is a bug in Xorg? Maybe someone else had or have such problems with Xorg? I want to work on FreeBSD 7.0, but this problem is very strange. When I work on FreeBSD 6.3 I hadn't such problems - it simply work. Thank you in advance for any help. Best wishes, Zbigniew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic FreeBSD 7.0 - Xorg
On Monday 12 of May 2008 22:22:12 Roland Smith wrote: It might also be a hardware problem. Testing the RAM would be a good place to start. Yes. You are right. I tested my memory with 'memtest' and got one error: Tst Pass Failing AddressGood BadErr-Bits Count 50 00022c8af50 - 556.6 MB efff 1000 1 After this error 'memtest' hang, keyboard was frozen and only pressed the restart button help. So, I will buy new memory. Thank you very much for help Roland and Mel. Thank you. Roland Best wishes, Zbigniew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel panic FreeBSD 7.0 - Xorg
Hello! I decide to go on FreeBSD 7.0-RELEASE. Before I used 6.3-RELEASE. But now I cannot get working Xorg. I almost get the kernel panic. I install fresh 7.0-RELEASE and update ports by portsnam and everything compiled by ports system. After instalign 'xorg' ports I do the following steps as root: Xorg -configure X -config /root/xorg.conf.new and I got black monitor and after few seconds the system reboots. Then I go to single user and do fsck -p (Similar was when I logon as root and typed startx) After that, I boot the system and I saw on the monitor the following (the exactly output is in file messages attached in this e-mail): savecore: reboot after panic: vm_fault: fault on nofault entry, addr: e56e8000 savecore: writing core to vmcore.2 and then I examine the file xorg.conf.org (I attached the file) and I saw that I have there the following line: Driver radeon In FreeBSD 6.3-RELEASE I had there Driver ati so I change it to ati and do X -config /root/xorg.conf.new but with no result - kernel panic again. What going on here? After fsck -p i decide to use vesa driver. I could only obtain the resolution 1024x678, but my monitor use 1280x1024. I have the following monitor: Philips 190P Could someone help me, please? If you need more information I send it to you. Thank you in advance. Here are additional information: # uname -a FreeBSD komp1.dom 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 I have the following motherboard: A-7N400SL F5 (from first screen after computer started) and also 3/29/2005-nVidia-nForce-6AG1BG0QC-00. The attached files: 1. messages (from /var/log/messages) 2. xorg.conf.new (from /root/xorg.conf.new) Thank you in advance for any help and I'm sorry for my English. Best wishes, Zbigniew May 12 11:38:29 komp1 syslogd: kernel boot file is /boot/kernel/kernel May 12 11:38:29 komp1 kernel: Copyright (c) 1992-2008 The FreeBSD Project. May 12 11:38:29 komp1 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 May 12 11:38:29 komp1 kernel: The Regents of the University of California. All rights reserved. May 12 11:38:29 komp1 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. May 12 11:38:29 komp1 kernel: FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 May 12 11:38:29 komp1 kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC May 12 11:38:29 komp1 kernel: Timecounter i8254 frequency 1193182 Hz quality 0 May 12 11:38:29 komp1 kernel: CPU: AMD Athlon(tm) XP 2000+ (1660.38-MHz 686-class CPU) May 12 11:38:29 komp1 kernel: Origin = AuthenticAMD Id = 0x681 Stepping = 1 May 12 11:38:29 komp1 kernel: Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE May 12 11:38:29 komp1 kernel: AMD Features=0xc0400800SYSCALL,MMX+,3DNow!+,3DNow! May 12 11:38:29 komp1 kernel: real memory = 2147418112 (2047 MB) May 12 11:38:29 komp1 kernel: avail memory = 2091872256 (1994 MB) May 12 11:38:29 komp1 kernel: ACPI APIC Table: Nvidia AWRDACPI May 12 11:38:29 komp1 kernel: ioapic0 Version 1.1 irqs 0-23 on motherboard May 12 11:38:29 komp1 kernel: kbd1 at kbdmux0 May 12 11:38:29 komp1 kernel: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) May 12 11:38:29 komp1 kernel: hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 19:59:27) May 12 11:38:29 komp1 kernel: acpi0: Nvidia AWRDACPI on motherboard May 12 11:38:29 komp1 kernel: acpi0: [ITHREAD] May 12 11:38:29 komp1 kernel: acpi0: Power Button (fixed) May 12 11:38:29 komp1 kernel: acpi0: reservation of 0, a (3) failed May 12 11:38:29 komp1 kernel: acpi0: reservation of 10, 7fef (3) failed May 12 11:38:29 komp1 kernel: Timecounter ACPI-fast frequency 3579545 Hz quality 1000 May 12 11:38:29 komp1 kernel: acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 May 12 11:38:29 komp1 kernel: cpu0: ACPI CPU on acpi0 May 12 11:38:29 komp1 kernel: acpi_button0: Power Button on acpi0 May 12 11:38:29 komp1 kernel: pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff,0xcf0-0xcf3 on acpi0 May 12 11:38:29 komp1 kernel: pci0: ACPI PCI bus on pcib0 May 12 11:38:29 komp1 kernel: Correcting nForce2 C1 CPU disconnect hangs May 12 11:38:29 komp1 kernel: agp0: NVIDIA nForce2 AGP Controller on hostb0 May 12 11:38:29 komp1 kernel: pci0: memory, RAM at device 0.1 (no driver attached) May 12 11:38:29 komp1 kernel: pci0: memory, RAM at device 0.2 (no driver attached) May 12 11:38:29 komp1 kernel: pci0: memory, RAM at device 0.3 (no driver attached) May 12 11:38:29 komp1 kernel: pci0: memory, RAM at device 0.4 (no driver attached) May 12 11:38:29 komp1 kernel: pci0: memory, RAM at device 0.5 (no driver attached) May 12 11:38:29 komp1 kernel: isab0: PCI-ISA bridge at device 1.0 on pci0 May 12 11:38:29 komp1 kernel: isa0: ISA bus on isab0 May 12 11:38:29 komp1 kernel: pci0: serial bus, SMBus at device 1.1 (no
Re: kernel panic FreeBSD 7.0 - Xorg
On Mon, May 12, 2008 at 12:51:26PM +0200, Zbigniew Komarnicki wrote: Hello! I decide to go on FreeBSD 7.0-RELEASE. Before I used 6.3-RELEASE. But now I cannot get working Xorg. I almost get the kernel panic. I install fresh 7.0-RELEASE and update ports by portsnam and everything compiled by ports system. After instalign 'xorg' ports I do the following steps as root: How *exactly* did you upgrade your ports? Sometimes old libraries hang around causing trouble. Xorg -configure X -config /root/xorg.conf.new Why would you do that? If you haven't changed the hardware, there is no need to change xorg.conf. and I got black monitor and after few seconds the system reboots. Then I go to single user and do Check the X logfile (/var/log/Xorg.0.log). Any clues in there? savecore: reboot after panic: vm_fault: fault on nofault entry, addr: e56e8000 savecore: writing core to vmcore.2 This can also help you debug. Load it up in the kernel debugger; kgdb /boot/kernel/kernel.symbols vmcore.2 Then inside the debugger, give the 'bt' command. and then I examine the file xorg.conf.org (I attached the file) and I saw that I have there the following line: Driver radeon In FreeBSD 6.3-RELEASE I had there Driver ati so I change it to ati and do X -config /root/xorg.conf.new but with no result - kernel panic again. What going on here? What kind of graphics card do you have? What does 'pciconf -lv' say? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp4FWXUz6p3n.pgp Description: PGP signature
Re: kernel panic FreeBSD 7.0 - Xorg
On Monday 12 of May 2008 16:24:44 Roland Smith wrote: How *exactly* did you upgrade your ports? Sometimes old libraries hang around causing trouble. I simply download the iso file for boot only: 7.0-RELEASE-i386-bootonly.iso Then burn on CD and then install fresh 7.0-RELEASE on hard disk - minimal system. Next I used portsnap to download ports: portsnap fetch [...] Then go to /usr/ports/x11/xorg and: make install clean After that, when I log as normal user and typed: startx got the first kernel panic. Then I used: Xorg -configure X -config /root/xorg.conf.new and again I got kernel panic, and also as mention previous, for drivers ati and radeon, too. Xorg -configure X -config /root/xorg.conf.new Why would you do that? If you haven't changed the hardware, there is no need to change xorg.conf. Because I hadn't the old version xorg.conf from 6.3. I simply format these partitions and forgotten make a backup of /etc especially /etc/X11. and I got black monitor and after few seconds the system reboots. Then I go to single user and do Check the X logfile (/var/log/Xorg.0.log). Any clues in there? I do obtain nothing in /var/log/Xorg.0.log. I only obtain result when I use vesa driver and it is about 10 kB text. But there no any errors form the vesa drivers. From the drivers radon or ati nothing was written, because was kernel panic. savecore: reboot after panic: vm_fault: fault on nofault entry, addr: e56e8000 savecore: writing core to vmcore.2 Now I have vmcore.8 This can also help you debug. Load it up in the kernel debugger; kgdb /boot/kernel/kernel.symbols vmcore.2 Then inside the debugger, give the 'bt' command. I coudn't do that because I obtain the following information (I do not remember exactly) Couldn't find file vmcore.2 I went to the /boot/kernel/ and there really no such file. What kind of graphics card do you have? What does 'pciconf -lv' say? I have: Radeon 9200 SE Series'. It is correctly recognized in xorg.conf.new, but if I remember in 6.3 the driver was ati for such card not radeon. Here is the output: [EMAIL PROTECTED]:0:0:0:class=0x06 card=0x chip=0x01e010de rev=0xc1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce2 AGP Controller' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:0:1:class=0x05 card=0x0c1710de chip=0x01eb10de rev=0xc1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce2 Memory Controller 1' class = memory subclass = RAM [EMAIL PROTECTED]:0:0:2:class=0x05 card=0x0c1710de chip=0x01ee10de rev=0xc1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce2 Memory Controller 4' class = memory subclass = RAM [EMAIL PROTECTED]:0:0:3:class=0x05 card=0x0c1710de chip=0x01ed10de rev=0xc1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce2 Memory Controller 3' class = memory subclass = RAM [EMAIL PROTECTED]:0:0:4:class=0x05 card=0x0c1710de chip=0x01ec10de rev=0xc1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce2 Memory Controller 2' class = memory subclass = RAM [EMAIL PROTECTED]:0:0:5:class=0x05 card=0x0c1710de chip=0x01ef10de rev=0xc1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce2 Memory Controller 5' class = memory subclass = RAM [EMAIL PROTECTED]:0:1:0:class=0x060100 card=0x0c111458 chip=0x008010de rev=0xa3 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce MCP2S PCI to ISA Bridge' class = bridge subclass = PCI-ISA [EMAIL PROTECTED]:0:1:1:class=0x0c0500 card=0x0c111458 chip=0x008410de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce MCP2S PCI System Management' class = serial bus subclass = SMBus [EMAIL PROTECTED]:0:2:0:class=0x0c0310 card=0x50041458 chip=0x008710de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce MCP2A USB Controller' class = serial bus subclass = USB [EMAIL PROTECTED]:0:2:1:class=0x0c0310 card=0x50041458 chip=0x008710de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce MCP2A USB Controller' class = serial bus subclass = USB [EMAIL PROTECTED]:0:2:2:class=0x0c0320 card=0x50041458 chip=0x008810de rev=0xa2 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce MCP2A USB Controller' class = serial bus subclass = USB [EMAIL PROTECTED]:0:6:0:class=0x040100 card=0xa0021458 chip=0x008a10de rev=0xa1 hdr=0x00 vendor = 'Nvidia Corp' device = 'nForce AC'97 Audio Codec Interface' class = multimedia subclass = audio [EMAIL PROTECTED]:0:8:0:class=0x060400 card=0x chip=0x008b10de rev=0xa3 hdr=0x01 vendor = 'Nvidia Corp' device = 'nforce MCP2A PCI Bridge' class
Re: kernel panic FreeBSD 7.0 - Xorg
On Mon, May 12, 2008 at 08:34:17PM +0200, Zbigniew Komarnicki wrote: On Monday 12 of May 2008 16:24:44 Roland Smith wrote: How *exactly* did you upgrade your ports? Sometimes old libraries hang around causing trouble. I simply download the iso file for boot only: 7.0-RELEASE-i386-bootonly.iso Then burn on CD and then install fresh 7.0-RELEASE on hard disk - minimal system. Next I used portsnap to download ports: portsnap fetch [...] Did you do a 'portsnap extract' as well? Fetching alone isn't enough. got the first kernel panic. Then I used: Xorg -configure X -config /root/xorg.conf.new and again I got kernel panic, and also as mention previous, for drivers ati and radeon, too. You should definitely use the radeon driver for this hardware. savecore: reboot after panic: vm_fault: fault on nofault entry, addr: e56e8000 savecore: writing core to vmcore.2 Now I have vmcore.8 This can also help you debug. Load it up in the kernel debugger; kgdb /boot/kernel/kernel.symbols vmcore.2 Then inside the debugger, give the 'bt' command. I coudn't do that because I obtain the following information (I do not remember exactly) Couldn't find file vmcore.2 I went to the /boot/kernel/ and there really no such file. Saved cores are kept in /var/crash by default. See dumpdir in /etc/defaults/rc.conf. Try kgdb /boot/kernel/kernel.symbols /var/crash/vmcore.8 What kind of graphics card do you have? What does 'pciconf -lv' say? I have: Radeon 9200 SE Series'. It is correctly recognized in xorg.conf.new, but if I remember in 6.3 the driver was ati for such card not radeon. [EMAIL PROTECTED]:2:0:0: class=0x03 card=0x596412ab chip=0x59641002 rev=0x01 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'Radeon 9200 Radeon 9200 SE Series' class = display subclass = VGA In file: /var/log/dmesg.today I found at the end of file the following entries: pid 23201 (conftest), uid 0: exited on signal 11 (core dumped) pid 34580 (conftest), uid 0: exited on signal 12 (core dumped) Hmm. Signal 12 is non-existant system call invoked. That's one I've never seen before. This was when I run startx as normal user without file xorg.conf in /etc/X11/xorg.conf. So the Xorg server must such file generated on the fly - and the result of course was kernel panic. Why Xorg do kernel panic? It has access to system internals via /dev/mem and /dev/io. So it can potentially screw things up pretty badly. It might also be a hardware problem. Testing the RAM would be a good place to start. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp09RV72KXgN.pgp Description: PGP signature
Re: kernel panic FreeBSD 7.0 - Xorg
On Monday 12 May 2008 22:22:12 Roland Smith wrote: On Mon, May 12, 2008 at 08:34:17PM +0200, Zbigniew Komarnicki wrote: On Monday 12 of May 2008 16:24:44 Roland Smith wrote: In file: /var/log/dmesg.today I found at the end of file the following entries: pid 23201 (conftest), uid 0: exited on signal 11 (core dumped) pid 34580 (conftest), uid 0: exited on signal 12 (core dumped) Hmm. Signal 12 is non-existant system call invoked. That's one I've never seen before. It's generated by some configure script (conftest), normally nothing to worry about. It's easy to get if you have a jail 'running' 6.x and you haven't set OSREL and/or UNAME_R correctly. Also, some configure scripts just try to invoke linux/posix/apple_syscall_foo to see if it's there. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic FreeBSD 7.0 - Xorg
On Monday 12 of May 2008 22:22:12 Roland Smith wrote: How *exactly* did you upgrade your ports? Sometimes old libraries hang around causing trouble. I used portsnap to download ports: portsnap fetch [...] Did you do a 'portsnap extract' as well? Fetching alone isn't enough. Yes of course. I first use 'portsnap update', but the portsnap told me that the ports was not created by portsnap and gave me what to do next. So I do it and everythings go on succesfull after that. You should definitely use the radeon driver for this hardware. I use on this computer also Debian lenny and everythings works well also Xorg. But in xorg.conf on Debian I have ati driver not radeon. The Xorg have the following version on Debian: X.Org X Server 1.4.0.90 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20080131-4) Current Operating System: Linux komp1 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 Build Date: 29 April 2008 08:24:00PM Saved cores are kept in /var/crash by default. See dumpdir in /etc/defaults/rc.conf. Try kgdb /boot/kernel/kernel.symbols /var/crash/vmcore.8 I will try it. Thank you. Why Xorg do kernel panic? It has access to system internals via /dev/mem and /dev/io. So it can potentially screw things up pretty badly. I understand. It might also be a hardware problem. Testing the RAM would be a good place to start. I check it. I run memtest today. It is strange why on Debian it works but here not? Thank you very much Roland. Roland Best wishes, Zbigniew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
