7.0-RELEASE panic
Hi, Apologies for the somewhat-generic subject line, not sure what else to call it. I have a new, fairly generic i386 box, with a fresh install of 7.0-RELEASE using pretty much the default options. I'm using a generic kernel with the addition of "options GEOM_BDE". I have had a couple of panics with it over a day or two; I can't pinpoint what is causing it, it has panicked when I'm not there and nothing seems to be going on. I recompiled the kernel shortly after install, so don't know if it will panic on the generic kernel alone. There is a vmcore in /var/crash, and I followed the instructions at http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneld ebug-gdb.html However, I'm not sure if kgdb is telling me I have a physical memory problem, or if it is telling me it's not working properly, (or more likely I'm not using it properly): odin2008# kgdb kernel.debug /var/crash/vmcore.1 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Cannot access memory at address 0x2fd9 (kgdb) where #0 0x in ?? () (kgdb) quit odin2008# more /var/crash/info.1 Dump header from device /dev/ad4s1b Architecture: i386 Architecture Version: 2 Dump Length: 207388672B (197 MB) Blocksize: 512 Dumptime: Sat May 31 15:31:52 2008 Hostname: odin2008.asgard.movesmountains.com Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Panic String: page fault Dump Parity: 797791774 Bounds: 1 Dump Status: good Oddly, I'm also seeing typos in /var/log/messages, which may or may not be related - e.g. May 30 0:14:53 odin2008 savecore: rebot after panic: age fault May 3 10:14:3 odin2008 savecore: wrting core to vmcore.0 May 30 10:16:03 odin2008 sck: /dev/ad4s1: 8 files, 7 used, 253808 free 40 frag, 31721 blocks, 0.0% frgmentation) fsck isn't showing any problems. Can anyone advise me what to do from here? Does this look like a hardware problem? Any help appreciated! Yours, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-RELEASE && panic after ~4 hours
On Wed, Mar 26, 2008 at 05:35:05PM +, Alphons Fonz van Werven wrote: > Sam Leffler wrote: > >> I am aware only of issues with USB adapters being removed while >> wpa_supplicant is running. > > Actually, there's more I'm afraid. > > iwi: Don't know because I don't use that one. But it's a "cousin" of wpi and > if I'm not mistaken it was the same person who initiated development of > both drivers. You did not specifically name any problems, but I most decidedly cannot confirm brokenness with iwi, as it stands now. Earlier I also used to get firmware crashes (but I not only use WPA2, but also a hidden SSID, which may complicate matters even more) But these are gone with recent -CURRENT (and yes, this is 8-CURRENT in this case), I use it without probs right now. FWIW, I also had good results with ral(4) (but did not try ural(4)). -- Regards: Szilveszter ADAM Budapest Hungary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-RELEASE && panic after ~4 hours
Vince wrote: there are some patches I missed? Entirely possible, I'm running these versions Thanks Vince, I'll check it out tomorrow (as well as gathering debug info for the rum driver, btw), as it's getting quite late now. At the moment, I have FreeBSD on my laptop but I can't do much with it because I need the WiFi stuff (either wpi or rum, whichever works) for Internet access. But I've been using FreeBSD over the wire for years so there will be a small party when I can finally use my favorite OS again :-) Later, Alphons -- All right, that does it Bill [Donahue]. I'm pretty sure that killing Jesus is not very Christian. -- pope Benedict XVI, South Park episode #158 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-RELEASE && panic after ~4 hours
Alphons "Fonz" van Werven wrote: Vince wrote: under 7-current Just noted the -current thingy. I'm running 7-release, with or without a patch by Andrew (2 kernels available). If it works with 7-current, perhaps there are some patches I missed? Alphons Entirely possible, I'm running these versions http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/wpi/?only_with_tag=RELENG_7 Doesnt look like the wpa_supplicant code has changed since 7-RELEASE http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/wpa/wpa_supplicant/?only_with_tag=RELENG_7 http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/wpa_supplicant/?only_with_tag=RELENG_7 or the underlying 80211 code http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/net80211/?only_with_tag=RELENG_7 Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-RELEASE && panic after ~4 hours
Alphons "Fonz" van Werven wrote: Vince wrote: Not true. under 7-current for me wpa works on my wpi adapter. Care to elaborate on what you did? Because in my and some other people's cases we can't get wpi to work with wpa_supplicant no matter what we try. Alphons (as can be seen in some previous threads) Nothing special. Oh and Thats 7-STABLE not current (sorry was following 7 as current for ages and forgot its finally stable :) All i need to do is ifconfig wpi0 up then wpa_supplicant -i wpi0 -c /etc/wpa_supplicant.conf I can send my wpa_supplicant.conf if you like (but later as my wife is using that laptop booted into windows.) The laptop is a Dell Inspiron 640m Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-RELEASE && panic after ~4 hours
Vince wrote: under 7-current Just noted the -current thingy. I'm running 7-release, with or without a patch by Andrew (2 kernels available). If it works with 7-current, perhaps there are some patches I missed? Alphons -- All right, that does it Bill [Donahue]. I'm pretty sure that killing Jesus is not very Christian. -- pope Benedict XVI, South Park episode #158 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-RELEASE && panic after ~4 hours
Matthias Apitz wrote: Hello, Over the longs last weekend I've installed FreeBSD 7.0-REL on my laptop and around 200 ports; I point this out to say that the laptop run without any reboot from Friday morning to Monday evening at home in my WEP based Wifi-zone; on Thursday and today I'm working in my office from around 9 o'clock and each day after 4 hours the system panic'ed: Mar 25 09:02:43 rebelion syslogd: kernel boot file is /boot/kernel/kernel Mar 25 13:00:03 rebelion savecore: reboot after panic: clist reservation botch Mar 26 09:11:04 rebelion syslogd: kernel boot file is /boot/kernel/kernel Mar 26 13:22:29 rebelion savecore: reboot after panic: page fault the main difference between home and work is: WEP at home and WPA2 at work; as well I see in messages a lot of: Mar 26 08:24:51 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 08:25:01 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 08:25:11 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 08:25:20 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 08:25:31 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 08:25:40 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 08:42:05 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 09:48:58 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 10:54:08 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 12:04:13 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 12:21:17 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 12:37:43 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 12:54:17 rebelion kernel: iwi0: firmware stuck in state 4, resetting Before I was for more than a year on 6.2-REL and without any panic which was not caused by pulling out the PCMCIA UMTS card; so I think it is not a hardware issue; Any comments? Please see http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html and file a PR. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-RELEASE && panic after ~4 hours
Vince wrote: Not true. under 7-current for me wpa works on my wpi adapter. Care to elaborate on what you did? Because in my and some other people's cases we can't get wpi to work with wpa_supplicant no matter what we try. Alphons (as can be seen in some previous threads) -- All right, that does it Bill [Donahue]. I'm pretty sure that killing Jesus is not very Christian. -- pope Benedict XVI, South Park episode #158 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-RELEASE && panic after ~4 hours
Alphons "Fonz" van Werven wrote: Sam Leffler wrote: I am aware only of issues with USB adapters being removed while wpa_supplicant is running. Actually, there's more I'm afraid. iwi: Don't know because I don't use that one. But it's a "cousin" of wpi and if I'm not mistaken it was the same person who initiated development of both drivers. wpi: No panics, but just doesn't work with wpa_supplicant at all (fails to associate). This is a known problem and people are working on it. Not true. under 7-current for me wpa works on my wpi adapter. I have had one panic but havent been able to replicate it yet, (i'm only blaming the wireless because it hasnt paniced on wired. Vince Neither of these are USB adapters. rum: Works but panics after a while. PR has been filed, but seems to be stuck at feedback status (anyone know more about this one?). Alphons ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-RELEASE && panic after ~4 hours
Sam Leffler wrote: I am aware only of issues with USB adapters being removed while wpa_supplicant is running. Actually, there's more I'm afraid. iwi: Don't know because I don't use that one. But it's a "cousin" of wpi and if I'm not mistaken it was the same person who initiated development of both drivers. wpi: No panics, but just doesn't work with wpa_supplicant at all (fails to associate). This is a known problem and people are working on it. Neither of these are USB adapters. rum: Works but panics after a while. PR has been filed, but seems to be stuck at feedback status (anyone know more about this one?). Alphons -- All right, that does it Bill [Donahue]. I'm pretty sure that killing Jesus is not very Christian. -- pope Benedict XVI, South Park episode #158 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-RELEASE && panic after ~4 hours
Alphons "Fonz" van Werven wrote: Matthias Apitz wrote: the main difference between home and work is: WEP at home and WPA2 at work; Which WiFi board are you using? Several drivers are known to cause panics when used with WPA. I am aware only of issues with USB adapters being removed while wpa_supplicant is running. This is a race in the usb code that I have worked around in the forthcoming vap code (not sure if the technique I used can be ported to RELENG_7). Regardless, for any issue to be pursued the usual info is required; the device identity, a stack trace, and if possible, debug msgs from the kernel prior to a problem (wlandebug enables net80211 msgs and every driver has a debug msg knob that may or may not require building a kernel w/ msgs enabled). iwi has most recently been tended by Andrew Thompson who is traveling so may not follow up for a bit (if sufficient info is provided). Sam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-RELEASE && panic after ~4 hours
El día Wednesday, March 26, 2008 a las 01:47:01PM +, Alphons Fonz van Werven escribió: > Matthias Apitz wrote: > > >the main difference between home and work is: WEP at home and WPA2 at > >work; > > Which WiFi board are you using? Several drivers are known to cause panics > when > used with WPA. sorry for not mention that: iwi0: mem 0xc8305000-0xc8305fff irq 18 at device 5.0 on pci6 iwi0: Ethernet address: 00:13:ce:a1:e6:81 iwi0: [ITHREAD] when it will crash tomorrow again, I will try it some days without Wifi and plug-in Ethernet; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html A: Because it messes up the order in which people normally read text. Q: Why is it such a bad thing? A: Top-posting. Q: What is the most annoying thing on Usenet and in e-mail? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 7.0-RELEASE && panic after ~4 hours
Matthias Apitz wrote: the main difference between home and work is: WEP at home and WPA2 at work; Which WiFi board are you using? Several drivers are known to cause panics when used with WPA. Alphons -- All right, that does it Bill [Donahue]. I'm pretty sure that killing Jesus is not very Christian. -- pope Benedict XVI, South Park episode #158 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7.0-RELEASE && panic after ~4 hours
Hello, Over the longs last weekend I've installed FreeBSD 7.0-REL on my laptop and around 200 ports; I point this out to say that the laptop run without any reboot from Friday morning to Monday evening at home in my WEP based Wifi-zone; on Thursday and today I'm working in my office from around 9 o'clock and each day after 4 hours the system panic'ed: Mar 25 09:02:43 rebelion syslogd: kernel boot file is /boot/kernel/kernel Mar 25 13:00:03 rebelion savecore: reboot after panic: clist reservation botch Mar 26 09:11:04 rebelion syslogd: kernel boot file is /boot/kernel/kernel Mar 26 13:22:29 rebelion savecore: reboot after panic: page fault the main difference between home and work is: WEP at home and WPA2 at work; as well I see in messages a lot of: Mar 26 08:24:51 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 08:25:01 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 08:25:11 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 08:25:20 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 08:25:31 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 08:25:40 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 08:42:05 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 09:48:58 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 10:54:08 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 12:04:13 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 12:21:17 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 12:37:43 rebelion kernel: iwi0: firmware stuck in state 4, resetting Mar 26 12:54:17 rebelion kernel: iwi0: firmware stuck in state 4, resetting Before I was for more than a year on 6.2-REL and without any panic which was not caused by pulling out the PCMCIA UMTS card; so I think it is not a hardware issue; Any comments? matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[EMAIL PROTECTED]> - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Don't top-post, read RFC1855 http://www.faqs.org/rfcs/rfc1855.html A: Because it messes up the order in which people normally read text. Q: Why is it such a bad thing? A: Top-posting. Q: What is the most annoying thing on Usenet and in e-mail? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"