FreeBSD 8.0: RAID-1 using gpart, gvinum and gmirror
Hello, I'm going to make my partition mirrored using the geom utilities, but however I've noticed that I cannot use the same way I used to do it under 7.2 and 8.0-RC1. Here's the situation - I tried a lot of times to make my root partition mirrored using gvinum, but each time when I boot in the new partition I'm unable to boot from it.. So instead of using gvinum for the root partition I've decided to use gmirror - and it works! I did it the following way - two NOT identical disks are added to the system. - 1 slices on the first disk - 2 slices on the second one (the 1st slice is the size of the root partition which is on the 1st slice on the 1st disk) Right after a fresh minimal install, I go to single-user mode and create the mirror: # gmirror label -vb round-robin gm0 /dev/ad0s1a Installing bootstap code on the second disk (in case I need to boot later from it): # fdisk -BI /dev/ad4s1 # bsdlabel -wB /dev/ad4s1 # newfs -O2 /dev/ad4s1 # newfs -O2 -U /dev/ad4s2 And then inserting the second component of the mirror: # gmirror insert gm0 /dev/ad4s1 And this is how I was doing a mirror for the root partition. For the other partitions - /usr, /var, /tmp, swap I used gvinum following a different articles, howtos and eventually it worked. The complete scenario of how I did the mirror for the other partitions is here (sorry, it's too long to just copy/paste it in the lists): http://www.daemonforums.org/showpost.php?p=27010&postcount=3 If I can say it with little words - the way mirroring works for the other partitions was to overlap all the other partitions with one big vinum partition. My problem now is that I cannot do this anymore, because I need to use gpart instead for creating the partitions, and using gpart I cannot create a vinum partition that will overlap the other partitions, so I cannot make any mirror for the other partitions. Is there any other way of doing this? I'm out of ideas now, perhaps you could help me out with this :) Thanks and regards, Marin -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD local r00t zeroday
Jeremy Chadwick wrote: On Tue, Dec 01, 2009 at 06:04:05PM +0700, ~Lst wrote: Hello all, What d'you think about this ? http://seclists.org/fulldisclosure/2009/Nov/371 Are you actually asking for an opinions of a security hole, or are you just trying to bring it to our attention? An official statement was already issued to freebsd-security about 10 hours ago: http://lists.freebsd.org/pipermail/freebsd-security/2009-December/005369.html Where is detailed instruction? I can not find ... I can't apply the patch: # cd /usr/src/libexec/rtld-elf/ [r...@mymachin /usr/src/libexec/rtld-elf]# patch http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD local r00t zeroday
Andrey S. Rybak wrote: > Where is detailed instruction? I can not find ... > I can't apply the patch: > > # cd /usr/src/libexec/rtld-elf/ > [r...@mymachin /usr/src/libexec/rtld-elf]# patch Hmm... Looks like a unified diff to me... > The text leading up to this was: > -- > |Index: rtld.c > |=== > |--- rtld.c (revision 199977) > |+++ rtld.c (working copy) > -- > Patching file rtld.c using Plan A... > Hunk #1 failed at 366. > 1 out of 1 hunks failed--saving rejects to rtld.c.rej > done > > What is wrong? The version of the patch you are trying to apply is for 8.0-RELEASE and you are probably using 7.2 Here is a version I crafted for 7.2 (use at your own risk, works for me): http://people.freebsd.org/~manolis/rtld72.patch ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: loader(8) readin failed on 7.2R and later including 8.0R
On Tuesday 01 December 2009 12:13:39 pm Hiroki Sato wrote: > Hi, > > This may be a rare case, but I post this with the hope for ideas from > people here. > > I have experienced a strange loader(8) error. After upgrading one of > my boxes from 7.1R to 7.2R, an error appeared on "boot" command of > loader(8) like this: > > | FreeBSD/i386 bootstrap loader, Revision 1.1 > | (h...@cmaster.allbsd.org, Mon Nov 30 04:01:24 JST 2009) > | Loading /boot/defaults/loader.conf > | /boot/kernel/kernel text=0x8b6c04 > | readin failed > | > | elf32_loadimage: read failed > | /boot/kernel/kernel text=0x8b6c04 > | readin failed > | > | elf32_loadimage: read failed > | Unable to load a kernel! > > (Actually the above error message was displayed when I upgraded it to > 8.0R. The message was the same when I tried 7.2R.) > > Replacing the /boot/loader with 7.1R's one, 7.2R's kernel worked > fine. > > Next, I tried to upgrade it to 8.0R. As I explained earlier, the > 8.0R's loader did not work either, so I replaced it with 7.1R again. > However, 7.1R loader(8) + 8.0R kernel displayed the following error > and did not work: > > | OK load /boot/kernel/kernel > | /boot/kernel/kernel text=0x8db9a4 data=0xdd134+0xa5e84 syms=[0x4+0x99390+0x4+0xd2201 > | elf32_loadimage: could not read symbols - skipped! > > While the "load" command seemed to finish, the box got stuck just > after entering "boot" command. > > Curious to say, I have got this symptom only on a specific box in > more than ten different boxes I upgraded so far; it is based on an > old motherboard Supermicro P4DPE[*]. > > [*] http://www.supermicro.com/products/motherboard/Xeon/E7500/P4DPE.cfm > > Any workaround? Booting from release CDROMs (7.2R and 8.0R) also > fail. On the box "7.1R" or "7.1R's loader + 7.2R kernel" worked > fine. It is possible something in changes of loader(8) between 7.1R > and 7.2R is the cause, but I am still not sure what it is... It may be related to the loader switching to using memory > 1MB for its malloc(). Maybe try building the loader with 'LOADER_NO_GPT_SUPPORT=yes' in /etc/src.conf? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Freebsd 8.0 system freeze
Hi, I recently upgraded from 7.2-STABLE to 8.0-RELEASE, and I'm encountering frequent system freezes (hang ups), which end in a reboot. There is no indication of any panic, no messages are generated and no core dump files (sysctl kern.coredump=1). System runs on IBM T43 with intel wireless chipset, iwi modules are loaded during boot via /boot/loader.conf. legal.intel_iwi.license_ack=1 if_iwi_load="YES" wlan_load="YES" firmware_load="YES" iwi_bss_load="YES" iwi_ibss_load="YES" iwi_monitor_load="YES Typically msg. look something like that or similar (iwi0 line gets repeated twice or 3 times): Dec 1 22:02:12 local kernel: wlan0: link state changed to DOWN Dec 1 22:02:19 local kernel: wlan0: link state changed to UP Dec 1 22:02:19 local kernel: iwi0: need multicast update callback Dec 1 22:02:30 local kernel: wlan0: link state changed to DOWN Dec 1 22:04:14 local syslogd: kernel boot file is /boot/kernel/kernel Is anyone else seeing this? ATM I am at work using bge0 interface and system runs without freezing so far. Could this situation be attributed to iwi driver or maybe wlandev? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 8.0 system freeze
On Wed, Dec 02, 2009 at 04:22:13PM +, Peter Pieczora wrote: > I recently upgraded from 7.2-STABLE to 8.0-RELEASE, and I'm encountering > frequent system freezes (hang ups), which end in a reboot. > > There is no indication of any panic, no messages are generated and no core > dump files (sysctl kern.coredump=1). Are you sure? The crash dumps may be being generated (hard to say for certain), but usually savecore will pick them up by analysing swap when the system comes up next. However, out-of-the-box, FreeBSD will not make a crash dump in swap, because /etc/defaults/rc.conf contains dumpdev="NO". If you change this to "AUTO", it will automatically pick the device associated with swap based on /etc/fstab (or you can set it yourself). Taken from the rc.conf man page: dumpdev (str) Indicates the device (usually a swap partition) to which a crash dump should be written in the event of a system crash. If the value of this variable is ``AUTO'', the first suitable swap device listed in /etc/fstab will be used as dump device. Otherwise, the value of this variable is passed as the argument to dumpon(8). To disable crash dumps, set this variable to ``NO''. Finally, you should be aware of the below issue. It's been a while since I've tested for its existence (we're now into the RELENG_8 days, not 6), but it may still apply -- I haven't checked. http://www.freebsd.org/cgi/query-pr.cgi?pr=118255&cat= http://www.mail-archive.com/freebsd-stable@freebsd.org/msg92323.html -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | > > System runs on IBM T43 with intel wireless chipset, iwi modules are loaded > during boot via /boot/loader.conf. > > legal.intel_iwi.license_ack=1 > if_iwi_load="YES" > wlan_load="YES" > firmware_load="YES" > iwi_bss_load="YES" > iwi_ibss_load="YES" > iwi_monitor_load="YES > > Typically msg. look something like that or similar (iwi0 line gets repeated > twice or 3 times): > > Dec 1 22:02:12 local kernel: wlan0: link state changed to DOWN > Dec 1 22:02:19 local kernel: wlan0: link state changed to UP > Dec 1 22:02:19 local kernel: iwi0: need multicast update callback > Dec 1 22:02:30 local kernel: wlan0: link state changed to DOWN > Dec 1 22:04:14 local syslogd: kernel boot file is /boot/kernel/kernel > > Is anyone else seeing this? > > ATM I am at work using bge0 interface and system runs without freezing so > far. > Could this situation be attributed to iwi driver or maybe wlandev? > > > > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 8.0: RAID-1 using gpart, gvinum and gmirror
Why are you using gvinum for RAID 1 instead of gmirror? The gmirror method for mirroring the boot partition is already well documented... On 2009-12-02 12:35:17PM +0200, Marin Atanasov wrote: > Hello, > > I'm going to make my partition mirrored using the geom utilities, but > however I've noticed that I cannot use the same way I used to do it under > 7.2 and 8.0-RC1. > > Here's the situation - I tried a lot of times to make my root partition > mirrored using gvinum, but each time when I boot in the new partition I'm > unable to boot from it.. So instead of using gvinum for the root partition > I've decided to use gmirror - and it works! > > I did it the following way - two NOT identical disks are added to the > system. > > - 1 slices on the first disk > - 2 slices on the second one (the 1st slice is the size of the root > partition which is on the 1st slice on the 1st disk) > > Right after a fresh minimal install, I go to single-user mode and create the > mirror: > > # gmirror label -vb round-robin gm0 /dev/ad0s1a > > Installing bootstap code on the second disk (in case I need to boot later > from it): > # fdisk -BI /dev/ad4s1 > # bsdlabel -wB /dev/ad4s1 > # newfs -O2 /dev/ad4s1 > # newfs -O2 -U /dev/ad4s2 > > And then inserting the second component of the mirror: > # gmirror insert gm0 /dev/ad4s1 > > And this is how I was doing a mirror for the root partition. For the other > partitions - /usr, /var, /tmp, swap I used gvinum following a different > articles, howtos and eventually it worked. The complete scenario of how I > did the mirror for the other partitions is here (sorry, it's too long to > just copy/paste it in the lists): > http://www.daemonforums.org/showpost.php?p=27010&postcount=3 > > If I can say it with little words - the way mirroring works for the other > partitions was to overlap all the other partitions with one big vinum > partition. > > My problem now is that I cannot do this anymore, because I need to use gpart > instead for creating the partitions, and using gpart I cannot create a vinum > partition that will overlap the other partitions, so I cannot make any > mirror for the other partitions. > > Is there any other way of doing this? > > I'm out of ideas now, perhaps you could help me out with this :) > > Thanks and regards, > Marin > > -- > Marin Atanasov Nikolov > dnaeon AT gmail DOT com > daemon AT unix-heaven DOT org > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- === Peter C. Lai | Bard College at Simon's Rock Systems Administrator| 84 Alford Rd. Information Technology Svcs. | Gt. Barrington, MA 01230 USA peter AT simons-rock.edu | (413) 528-7428 === ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: iwn(4) 5100 - Estimation for MFC of r198429?
On Tue, Dec 01, 2009 at 07:39:37PM -0500, Glen Barber wrote: > Hi, > > I've been using the iwn(4) driver contributed by Bernhard Schmidt with > my Intel 5100 AGN card on 8-STABLE since he announced the > availability. It was committed to -CURRENT as of r198429. There is > no mention of MFC in the commit log. Are there plans to MFC this > driver to 8-STABLE for a wider testing base? Hear, hear. I've got a 5100 AGN in a laptop. I'd like to test it as well, without switching to -CURRENT. If I just got the files mentioned in the commit* and add/replace them in my source tree, it looks like it should work. Or am I missing something? Roland * http://svn.freebsd.org/viewvc/base?view=revision&revision=198429 -- 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) pgp0N8oYyXIAE.pgp Description: PGP signature
Re: iwn(4) 5100 - Estimation for MFC of r198429?
On Wed, Dec 2, 2009 at 12:24 PM, Roland Smith wrote: > On Tue, Dec 01, 2009 at 07:39:37PM -0500, Glen Barber wrote: >> Hi, >> >> I've been using the iwn(4) driver contributed by Bernhard Schmidt with >> my Intel 5100 AGN card on 8-STABLE since he announced the >> availability. It was committed to -CURRENT as of r198429. There is >> no mention of MFC in the commit log. Are there plans to MFC this >> driver to 8-STABLE for a wider testing base? > > Hear, hear. > > I've got a 5100 AGN in a laptop. I'd like to test it as well, without > switching to -CURRENT. > > If I just got the files mentioned in the commit* and add/replace them in my > source tree, it looks like it should work. Or am I missing something? > That should be sufficient. > Roland > > * http://svn.freebsd.org/viewvc/base?view=revision&revision=198429 > -- > 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) > -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: iwn(4) 5100 - Estimation for MFC of r198429?
On Wednesday 02 December 2009 18:24:58 Roland Smith wrote: > On Tue, Dec 01, 2009 at 07:39:37PM -0500, Glen Barber wrote: > > Hi, > > > > I've been using the iwn(4) driver contributed by Bernhard Schmidt with > > my Intel 5100 AGN card on 8-STABLE since he announced the > > availability. It was committed to -CURRENT as of r198429. There is > > no mention of MFC in the commit log. Are there plans to MFC this > > driver to 8-STABLE for a wider testing base? > > Hear, hear. > > I've got a 5100 AGN in a laptop. I'd like to test it as well, without > switching to -CURRENT. > > If I just got the files mentioned in the commit* and add/replace them in my > source tree, it looks like it should work. Or am I missing something? > > Roland > > * http://svn.freebsd.org/viewvc/base?view=revision&revision=198429 Yep, that should work, though it is probably better and easier if you use the svn version. It also contains several fixes. Installation instructions: http://forums.freebsd.org/showpost.php?p=47627&postcount=16 -- Bernhard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 8.0 system freeze
On Wednesday 02 December 2009 17:22:13 Peter Pieczora wrote: > Hi, > > I recently upgraded from 7.2-STABLE to 8.0-RELEASE, and I'm encountering > frequent system freezes (hang ups), which end in a reboot. > > There is no indication of any panic, no messages are generated and no core > dump files (sysctl kern.coredump=1). > > System runs on IBM T43 with intel wireless chipset, iwi modules are loaded > during boot via /boot/loader.conf. > > legal.intel_iwi.license_ack=1 > if_iwi_load="YES" > wlan_load="YES" > firmware_load="YES" > iwi_bss_load="YES" > iwi_ibss_load="YES" > iwi_monitor_load="YES > > Typically msg. look something like that or similar (iwi0 line gets repeated > twice or 3 times): > > Dec 1 22:02:12 local kernel: wlan0: link state changed to DOWN > Dec 1 22:02:19 local kernel: wlan0: link state changed to UP > Dec 1 22:02:19 local kernel: iwi0: need multicast update callback > Dec 1 22:02:30 local kernel: wlan0: link state changed to DOWN > Dec 1 22:04:14 local syslogd: kernel boot file is /boot/kernel/kernel > > Is anyone else seeing this? > > ATM I am at work using bge0 interface and system runs without freezing so > far. Could this situation be attributed to iwi driver or maybe wlandev? I've seen something which might be related. Using a iwn(4) device for some time my -CURRENT box locks up completely, no reboot, no panic, no ctrl+alt+esc.. The last message I see is from net80211 sending a power notification wakeup message after returning form a background scan. Still digging around, trying to find the cause. -- Bernhard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 8.0-RC USB/FS problem
On 22.11.2009 10:47 Hans Petter Selasky wrote: > Other operating systems do a port bus reset when the device has a problem. On > FreeBSD we just try a software reset via the control endpoint. I guess that > it > is a device problem you are seeing. The USB stack in FreeBSD is faster than > the old one, and maybe the faster queueing of mass storage requests trigger > some hidden bugs in your device. > > When the problem happens try: > > sysctl hw.usb.umass.debug=-1 I have observed USB lock-ups with several external drive enclosures that used to work with the old USB stack (and continue to work when connected to a Windows notebook, for example). (BTW: System is AMD X2 with Nvidia chip-set and i386 kernel.) In my case, hw.usb.debug=6 makes the drive work at some 4MB/s for any amount of data transfered, while hw.usb.debug=5 (and an ylower value) lets the drive pause for about 1 Minute per 100MB transfered. I wanted to test whether short delays inserted in the places with DPRINTFN(6, ...) make a difference, but will not get to it before the weekend. Regards, STefan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: 8.0-RC USB/FS problem
I noticed that your machine also has an AMD CPU. Hopefully this may NOT imply something to the hardware. I will find more systems especially Intel CPUs to do further test. -Original Message- From: Stefan Esser [mailto:s...@freebsd.org] Sent: Monday, November 30, 2009 12:18 PM To: Hans Petter Selasky Cc: freebsd-...@freebsd.org; b...@freebsd.org; freebsd-stable@freebsd.org; Guojun Jin Subject: Re: 8.0-RC USB/FS problem On 22.11.2009 10:47 Hans Petter Selasky wrote: > Other operating systems do a port bus reset when the device has a problem. On > FreeBSD we just try a software reset via the control endpoint. I guess that it > is a device problem you are seeing. The USB stack in FreeBSD is faster than > the old one, and maybe the faster queueing of mass storage requests trigger > some hidden bugs in your device. > > When the problem happens try: > > sysctl hw.usb.umass.debug=-1 I have observed USB lock-ups with several external drive enclosures that used to work with the old USB stack (and continue to work when connected to a Windows notebook, for example). (BTW: System is AMD X2 with Nvidia chip-set and i386 kernel.) In my case, hw.usb.debug=6 makes the drive work at some 4MB/s for any amount of data transfered, while hw.usb.debug=5 (and an ylower value) lets the drive pause for about 1 Minute per 100MB transfered. I wanted to test whether short delays inserted in the places with DPRINTFN(6, ...) make a difference, but will not get to it before the weekend. Regards, STefan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: em interface slow down on 8.0R
We've run into a snag on this problem. The 82547 is a LOM only interface and my validation engineer has only found two old systems that have it, and neither of them will even install FreeBSD 8 they are so old :( I might suggest that you continue using the 7.2 driver with that hardware if it was working. To me this is further data on the need to have a frozen legacy version of em but the problem is which code to use and how to approach it. Can you give me more specifics on the box you have this installed on?? Regards, Jack On Mon, Nov 30, 2009 at 5:29 PM, Hiroki Sato wrote: > Jack Vogel wrote > in <2a41acea0911301119j1449be58y183f2fe1d1112...@mail.gmail.com>: > > jf> I will look into this Hiroki, as time goes the older hardware does not > jf> always > jf> get test cycles like one might wish. > > Thanks! Please let me know if you need more information. > > -- Hiroki > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 8.0 system freeze
Hi, You're absolutely right, adding dumpdev="AUTO" solved generating dump files. I may be totally wrong, but it seems that wlan0 causes system panic: I remember when using ndis device (linksys pcmcia wifi card) similar situation took place. Thanks for your help. > local dumped core - see /var/crash/vmcore.3 Wed Dec 2 19:20:24 GMT 2009 FreeBSD local 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 panic: page fault GNU gdb 6.1.1 [FreeBSD]... Unread portion of the kernel message buffer: wlan0: ieee80211_new_state_locked: pending SCAN -> AUTH transition lost Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xc5e931d5 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0f78b0c stack pointer = 0x28:0xe52deb7c frame pointer = 0x28:0xe52dec34 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (iwi0 taskq) trap number = 12 panic: page fault cpuid = 0 Uptime: 2m25s Physical memory: 1518 MB ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 8.0 system freeze
On Wed, Dec 2, 2009 at 17:22, Peter Pieczora wrote: > Hi, > > I recently upgraded from 7.2-STABLE to 8.0-RELEASE, and I'm encountering > frequent system freezes (hang ups), which end in a reboot. > > There is no indication of any panic, no messages are generated and no core > dump files (sysctl kern.coredump=1). > > System runs on IBM T43 with intel wireless chipset, iwi modules are loaded > during boot via /boot/loader.conf. > > legal.intel_iwi.license_ack=1 > if_iwi_load="YES" > wlan_load="YES" > firmware_load="YES" > iwi_bss_load="YES" > iwi_ibss_load="YES" > iwi_monitor_load="YES > > Typically msg. look something like that or similar (iwi0 line gets repeated > twice or 3 times): > > Dec 1 22:02:12 local kernel: wlan0: link state changed to DOWN > Dec 1 22:02:19 local kernel: wlan0: link state changed to UP > Dec 1 22:02:19 local kernel: iwi0: need multicast update callback > Dec 1 22:02:30 local kernel: wlan0: link state changed to DOWN > Dec 1 22:04:14 local syslogd: kernel boot file is /boot/kernel/kernel > > Is anyone else seeing this? > > ATM I am at work using bge0 interface and system runs without freezing so far. > Could this situation be attributed to iwi driver or maybe wlandev? I see similar behaviour. stable/8 before the release worked normal. Since a few days I have apps segfaulting frequently (firefox, pidgin, mplayer, ...) and have freezes. I configured Kernel debugging and added a dumpdev but had no luck in getting a dump so far only freezes. I let the system run frozen for more then five minutes to see if it's just dumping in the background (I think one cannot see that while in X). One time the system froze while loading vboxdrv, another time when I started mplayer. But it happens on other occasions too. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 8.0 system freeze
On Wed, Dec 02, 2009 at 09:34:28PM +, Peter Pieczora wrote: > You're absolutely right, adding dumpdev="AUTO" solved generating dump files. > > I may be totally wrong, but it seems that wlan0 causes system panic: > I remember when using ndis device (linksys pcmcia wifi card) similar > situation > took place. > > Thanks for your help. > > > > local dumped core - see /var/crash/vmcore.3 > > Wed Dec 2 19:20:24 GMT 2009 > > FreeBSD local 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC > 2009 > r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > panic: page fault > > GNU gdb 6.1.1 [FreeBSD]... > > Unread portion of the kernel message buffer: > wlan0: ieee80211_new_state_locked: pending SCAN -> AUTH transition lost > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xc5e931d5 > fault code= supervisor read, page not present > instruction pointer = 0x20:0xc0f78b0c > stack pointer = 0x28:0xe52deb7c > frame pointer = 0x28:0xe52dec34 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (iwi0 taskq) > trap number = 12 > panic: page fault > cpuid = 0 > Uptime: 2m25s > Physical memory: 1518 MB You're welcome! (I often wonder if dumpdev should be set to "AUTO" by default these days, but that discussion is for elsewhere and another time...) With regards to providing kernel dump/crash details: relevant Handbook details on this process are below. They're dated circa RELENG_5_3, but I think they still apply today for getting proper data out of vmcore. http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-post-mortem.html http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html As I understand it, the basic requirements are: 1) "makeoptions DEBUG=-g" in your kernel configuration file 2) /usr/obj properly populated with the built kernel + modules + etc. that you're running at the time of the crash. (/boot/kernel/* isn't enough to accomplish this) Easiest way to achieve the latter is to go through the 11-step procedure listed in /usr/src/Makefile, then afterwards, **do not** clear /usr/obj on your own (some admins have a tendency to do this -- it makes debugging a kernel panic a pain). To decrease confusion, you might nuke everything in /var/crash *except* the file called "minfree" -- keep that! You'll also (obviously) need the box in a stable state -- meaning use local Ethernet and not iwi(4) for the time being. Someone else will have to help with post-analysis of the dump; kernel debugging has never been my forte aside from the "backtrace" (stack trace) part. :-) Filing a PR about this problem would also be a great thing to do, as it's good to have an official bug report developers and users can refer to. If you file a PR, please provide the number here for reference. Good luck! -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 8.0 system freeze
On Wed, 2 Dec 2009 14:17:20 -0800 Jeremy Chadwick wrote: > You're welcome! (I often wonder if dumpdev should be set to "AUTO" by > default these days, but that discussion is for elsewhere and another > time...) See http://lists.freebsd.org/pipermail/svn-src-stable-8/2009-September/000224.html for a discussion of the pros and cons of having crash dumps enabled by default. -- Bruce Cran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: em interface slow down on 8.0R
Update: the claim to be unable to install was hasty, I went in and looked into myself and was able to get an install. Here's what I've found so far: First, the 82547EI will fail due to Invalid Mac Address, so I guess you hacked around this problem yourself? I had someone here test all legacy adapters for this problem and I was told nothing else was exhibiting it besides the 82542, obviously this is false :) In any case I will be making an official patch to fix that problem soon. Second, once I had the device working I do indeed see substandard performance, I am continuing to debug, but wanted you to know that I have reproduced this. Jack On Wed, Dec 2, 2009 at 12:49 PM, Jack Vogel wrote: > We've run into a snag on this problem. The 82547 is a LOM only interface > and my validation engineer has only found two old systems that have it, > and neither of them will even install FreeBSD 8 they are so old :( > > I might suggest that you continue using the 7.2 driver with that hardware > if it was working. > > To me this is further data on the need to have a frozen legacy version of > em but the problem is which code to use and how to approach it. > > Can you give me more specifics on the box you have this installed on?? > > Regards, > > Jack > > > > On Mon, Nov 30, 2009 at 5:29 PM, Hiroki Sato wrote: > >> Jack Vogel wrote >> in <2a41acea0911301119j1449be58y183f2fe1d1112...@mail.gmail.com>: >> >> jf> I will look into this Hiroki, as time goes the older hardware does not >> jf> always >> jf> get test cycles like one might wish. >> >> Thanks! Please let me know if you need more information. >> >> -- Hiroki >> > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 8 GPT install, how?
Looking at the release notes it seems FreeBSD 8 now supports booting from a GPT formatted partition but going through the installer it seems, please correct me if I'm wrong, that its still no possible to actually install using a standard disk1 to a clean machine with a large disk? I've found a number things articles on how to achieve this on previous versions, but they are all quite complex and was hoping there was a nice easy way on 8.0 given the improvements listed in the release notes. Any pointers? Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: route(8) and show/sticky/... Re: 8.0-RELEASE completed...
Kurt Jaeger wrote: Hi! Just a quick note in case there are people here who aren't subscribed to the freebsd-announce@ mailing list. We have completed the 8.0-RELEASE cycle. Details about the release are available from the main web site, in particular the announcement itself is available here: http://www.freebsd.org/releases/8.0R/announce.html Thanks! One question: http://www.freebsd.org/releases/8.0R/relnotes-detailed.html says: -- The route(8) utility now supports show, weights, and sticky commands. For more details, see the route(8) manual page. -- I do not have those things in my man page or route(8) command ? I have one more question about relnotes-detailed.html --- "Specific CPU binding by using cpuset(1) has been implemented. Note that the current implementation allows the superuser inside of the jail to change the CPU bindings specified." --- Is it true? I don't have 8.0-RELEASE installed, but I think it was fixed in 7-STABLE right after the 7.2-RELEASE PR kern/134050 was reported by me Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 8 GPT install, how?
On Thu, 3 Dec 2009, Steven Hartland wrote: > Looking at the release notes it seems FreeBSD 8 now supports booting > from a GPT formatted partition but going through the installer it > seems, please correct me if I'm wrong, that its still no possible to > actually install using a standard disk1 to a clean machine with a > large disk? > > I've found a number things articles on how to achieve this on > previous versions, but they are all quite complex and was hoping > there was a nice easy way on 8.0 given the improvements listed in the > release notes. Unfortunately not, although work is in progress on teaching sysinstall about gpart. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Could you please fix this ?
Hello everybody,
I was facing one big problem, i have a notebook, which is an Acer
Aspire 5920. If you like i can send to you my messages file.
Which is:
Intel(R) Core(TM)2 Duo CPU T5550 @ 1.83GHz (1833.48-MHz 686-class CPU)
Intel(R) PRO/Wireless 3945ABG
Broadcom NetLink Gigabit Ethernet Controller
2 Gigs RAM
160 Gigs SATA
The point was:
With ACPI disabled, i managed to boot but without WIFI; and with ACPI
enabled, the boot process hanged up all times.
I fixed this adding
if (device_get_unit(dev)==2){
pci_write_config(dev, PCIR_COMMAND, PCIM_CMD_MEMEN |
PCIM_CMD_PORTEN, 1);
pci_enable_busmaster(dev);
pci_write_config(dev, PCIR_IOBASEL_1, 0xf0, 1);
pci_write_config(dev, PCIR_MEMBASE_1, 0xf020, 2);
pci_write_config(dev, PCIR_MEMLIMIT_1, 0xf020, 2);
pci_write_config(dev, PCIR_PMBASEL_1, 0xfff1, 2);
}
if (device_get_unit(dev)==3){
pci_write_config(dev, PCIR_COMMAND, PCIM_CMD_MEMEN |
PCIM_CMD_PORTEN, 1);
pci_enable_busmaster(dev);
pci_write_config(dev, PCIR_IOBASEL_1, 0xf0, 1);
pci_write_config(dev, PCIR_MEMBASE_1, 0xf030, 2);
pci_write_config(dev, PCIR_MEMLIMIT_1, 0xf030, 2);
pci_write_config(dev, PCIR_PMBASEL_1, 0xfff1, 2);
}
to /usr/src/sys/dev/acpica/acpi_pcib_pci.c running on a 8.0-RELEASE
I was able to fix it by my way but many people cant do it, so, i would
really appreciate if you can add this piece of code.
Thanks, kind regards
Leonardo
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: em interface slow down on 8.0R
On 1 Dec 2009, at 12:05, Elliot Finley wrote: > On Mon, Nov 30, 2009 at 6:29 PM, Hiroki Sato wrote: > Jack Vogel wrote > in <2a41acea0911301119j1449be58y183f2fe1d1112...@mail.gmail.com>: > > jf> I will look into this Hiroki, as time goes the older hardware does not > jf> always > jf> get test cycles like one might wish. > > > Here's some more info to throw into the mix. I have several new boxes > running 8-Stable (a few hours after release). > > Leaving all sysctl at default, I get around 400mbps testing with netperf or > iperf. If I set the following on the box running 'netserver' or 'iperf -s': > > kern.ipc.maxsockbuf=16777216 > net.inet.tcp.recvspace=1048576 > > then I can get around 926mbps. But then if I make those same changes on the > box running the client side of netperf or iperf the performance drops back > down to around 400mbps. > > All boxes have the same hardware. they have two 4-port Intel NICS in them. > > e...@pci0:5:0:1: class=0x02 card=0x10a48086 chip=0x10a48086 rev=0x06 > hdr=0x00 > vendor = 'Intel Corporation' > device = '82571EB Gigabit Ethernet Controller' > class = network > subclass = ethernet > > any pointers on further network tuning to get bidirectional link saturation > would be much appreciated. These boxes are not in production yet, so anyone > that would like to have access to troubleshoot, just ask. I've CC'd Lawrence Stewart in on this thread, as he's been doing work on the TCP stack lately and might have insight into what you might be running into. Lawrence -- there's a bit of a back thread with configuration and problem details in the stable@ archives. Robert___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
8.0R TCP connection stall with large Send-Q
Hello, Recently I updated my main PC from 7.2(7-STABLE around Oct 8th actually) to 8.0R (amd64). After that, I noticed that the Apache HTTP server (2.2.13) on the PC started to behave strangely. When I tried to see a page on the PC with a lot of thumbnails (more than 30 or 40 maybe), the page stopped loading and many thumbnail images were missing (not downloaded properly). It never happened until upgrade (of course I recompiled httpd and related libraries). After some investigation, I noticed that TCP connections stalled with large Send-Q. % netstat -n (just after a browser hit a page with many thumbnails) Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp6 0 14767 2001:200:905:131.802001:200:905:15f.1369 ESTABLISHED tcp6 0 13793 2001:200:905:131.802001:200:905:15f.1368 ESTABLISHED tcp6 0 13148 2001:200:905:131.802001:200:905:15f.1367 ESTABLISHED tcp6 0 16749 2001:200:905:131.802001:200:905:15f.1366 ESTABLISHED tcp6 0 15136 2001:200:905:131.802001:200:905:15f.1365 ESTABLISHED tcp6 0 17390 2001:200:905:131.802001:200:905:15f.1364 ESTABLISHED (omit other lines) Soon the state changed to FIN_WAIT_1, and never gone until I close the web browser. The example is IPv6, but it also happened with IPv4. It seems that the size of queues are almost the same as the size of thumbnail files. Also I cannot csup the source tree on this PC now, because the connection stall in the same way. Qpopper stalls when my mailbox contains some emails (I'm not sure about the exact threshold). Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0897 133.5.7.92.110 202.228.xxx.xxx.38167 ESTABLISHED tcp4 0 18053 133.5.6.4.5400359.106.xxx.xxx.5999ESTABLISHED On the other hand, I can SCP dozens of photos to the PC without problems, and downloading a single large file from the PC via HTTP is also fine. I copied some HTML pages with many thumbnails to other PC running 8.0-RC2 (i386), but I couldn't reproduce the problem. The former PC uses vge and latter uses rl, so it might be a NIC driver issue?? I'll try to replace NIC cards when I have time vge0: flags=8843 metric 0 mtu 1500 options=1b ether 00:02:2a:dd:05:41 inet 133.5.6.4 netmask 0xff00 broadcast 133.5.6.255 inet6 fe80::202:2aff:fedd:541%vge0 prefixlen 64 scopeid 0x1 media: Ethernet autoselect (100baseTX ) status: active vge1: flags=8843 metric 0 mtu 1500 options=1b ether 00:02:2a:dd:0c:31 inet 133.5.7.92 netmask 0xff00 broadcast 133.5.7.255 inet6 fe80::202:2aff:fedd:c31%vge1 prefixlen 64 scopeid 0x2 inet6 2001:200:905:1407:202:2aff:fedd:c31 prefixlen 64 autoconf media: Ethernet autoselect (100baseTX ) status: active vge2: flags=8843 metric 0 mtu 1500 options=1b ether 00:02:2a:dd:00:7d inet 133.69.133.98 netmask 0xfff0 broadcast 133.69.133.111 inet6 fe80::202:2aff:fedd:7d%vge2 prefixlen 64 scopeid 0x3 inet6 2001:200:905:1314::80 prefixlen 64 inet6 2001:200:905:1314:202:2aff:fedd:7d prefixlen 64 autoconf media: Ethernet autoselect (100baseTX ) status: active v...@pci0:6:1:0:class=0x02 card=0x01101106 chip=0x31191106 rev=0x11 hdr=0x00 vendor = 'VIA Technologies Inc' device = ''Velocity' Gigabit Ethernet Controllers (VT6120/VT6121/VT6122)' class = network subclass = ethernet v...@pci0:6:2:0:class=0x02 card=0x01101106 chip=0x31191106 rev=0x11 hdr=0x00 vendor = 'VIA Technologies Inc' device = ''Velocity' Gigabit Ethernet Controllers (VT6120/VT6121/VT6122)' class = network subclass = ethernet v...@pci0:6:3:0:class=0x02 card=0x01101106 chip=0x31191106 rev=0x11 hdr=0x00 vendor = 'VIA Technologies Inc' device = ''Velocity' Gigabit Ethernet Controllers (VT6120/VT6121/VT6122)' class = network subclass = ethernet % netstat -ni NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll vge0 1500 00:02:2a:dd:05:41 2124119 0 2158388 3 0 vge0 1500 133.5.6.0/24 133.5.6.4 1958844 - 2157884 - - vge0 1500 fe80:1::202:2 fe80:1::202:2aff:0 -1 - - vge1 1500 00:02:2a:dd:0c:31 1005409 032166 0 0 vge1 1500 133.5.7.0/24 133.5.7.92 431605 -11761 - - vge1 1500 fe80:2::202:2 fe80:2::202:2aff:0 - 1452 - - vge1 1500 2001:200:905: 2001:200:905:14070 -16518 - - vge2 1500 00:02:2a:dd:00:7d 563715 0 855146 2 0 vge2 1500 133.69.133.96 133.69.133.98 445915 - 3658 - - vge2 1500 fe80:3::202:2 fe80:3::202:2aff:0 - 1875 - - vge2 1500
Re: FreeBSD 8.0: RAID-1 using gpart, gvinum and gmirror
Hi, Well, as I said before I'm using gmirror for the root partition - that's the easiest part, but... The reason that I don't want to use gmirror for the other partitions is that I'm using two not identical disks, so I want to mirror them using gvinum instead, which will give me also possibility to extend the volumes if I need so - adding/removing plexes from it, etc, which I think is more flexible than just using gmirror. I've done this setup on 8.0-RC1, and I must say it works very well - root is mirrored via gmirror and /usr, /var, /tmp, swap are mirrored via gvinum. When I need more space I just extend the volumes. But as I pointed the way gpart is working I'm not able to create a partition that overlaps the other partitions. Do you know how this can be done? Thanks and regards, Marin On Wed, Dec 2, 2009 at 7:16 PM, Peter C. Lai wrote: > Why are you using gvinum for RAID 1 instead of gmirror? The gmirror method > for mirroring the boot partition is already well documented... > > On 2009-12-02 12:35:17PM +0200, Marin Atanasov wrote: > > Hello, > > > > I'm going to make my partition mirrored using the geom utilities, but > > however I've noticed that I cannot use the same way I used to do it under > > 7.2 and 8.0-RC1. > > > > Here's the situation - I tried a lot of times to make my root partition > > mirrored using gvinum, but each time when I boot in the new partition I'm > > unable to boot from it.. So instead of using gvinum for the root > partition > > I've decided to use gmirror - and it works! > > > > I did it the following way - two NOT identical disks are added to the > > system. > > > > - 1 slices on the first disk > > - 2 slices on the second one (the 1st slice is the size of the root > > partition which is on the 1st slice on the 1st disk) > > > > Right after a fresh minimal install, I go to single-user mode and create > the > > mirror: > > > > # gmirror label -vb round-robin gm0 /dev/ad0s1a > > > > Installing bootstap code on the second disk (in case I need to boot later > > from it): > > # fdisk -BI /dev/ad4s1 > > # bsdlabel -wB /dev/ad4s1 > > # newfs -O2 /dev/ad4s1 > > # newfs -O2 -U /dev/ad4s2 > > > > And then inserting the second component of the mirror: > > # gmirror insert gm0 /dev/ad4s1 > > > > And this is how I was doing a mirror for the root partition. For the > other > > partitions - /usr, /var, /tmp, swap I used gvinum following a different > > articles, howtos and eventually it worked. The complete scenario of how I > > did the mirror for the other partitions is here (sorry, it's too long to > > just copy/paste it in the lists): > > http://www.daemonforums.org/showpost.php?p=27010&postcount=3 > > > > If I can say it with little words - the way mirroring works for the other > > partitions was to overlap all the other partitions with one big vinum > > partition. > > > > My problem now is that I cannot do this anymore, because I need to use > gpart > > instead for creating the partitions, and using gpart I cannot create a > vinum > > partition that will overlap the other partitions, so I cannot make any > > mirror for the other partitions. > > > > Is there any other way of doing this? > > > > I'm out of ideas now, perhaps you could help me out with this :) > > > > Thanks and regards, > > Marin > > > > -- > > Marin Atanasov Nikolov > > dnaeon AT gmail DOT com > > daemon AT unix-heaven DOT org > > ___ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org > " > > -- > === > Peter C. Lai | Bard College at Simon's Rock > Systems Administrator| 84 Alford Rd. > Information Technology Svcs. | Gt. Barrington, MA 01230 USA > peter AT simons-rock.edu | (413) 528-7428 > === > > -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
