Re: Going to BSD 8 from RELENG_7
> Date: Mon, 17 Aug 2009 09:18:11 +0200 > From: Bartosz Stec > Sender: owner-freebsd-sta...@freebsd.org > > Johan Hendriks pisze: > > Be aware that if you go from 7 to 8 you will need to rebuild all your > > installed ports. > > ALso if you do a buildworld from 7 to 8 do not do the make delete-old > > and the make delete-old-libs before you have rebuild your ports. > > If you do the make delete-old and make delete-old-libs runs, all ports > > depending on the FreeBSD 7 libs will not work any more. << read: most > > likely all your ports. > > If you have changed for example your Shell for root to a ports based > > shell like bash and you do the make delete-old-libs you can not log in > > anymore, because bash depends on the 7 libs wich are not there anymore. > > > > And as usual MAKE A GOOD BACKUP > > > > Regards, > > Johan > > > > > > > As I remember when I did upgrade from FreBSD 6.4 to 7.0, I ran > 'portupgrade -afi' after thar, BUT as I remember all my ports in fact > works before they were upgraded. If I understand correctly, the reason > of this was not making delete-old and delete-old-libs? > > So should following upgrade procedure be painless? > > 0. Backup! > 1. cvsup 8.0-stable > 2. make buildworld && make buildkernel > 3. make installkernel > 4. reboot and jump to single user mode > 5. make installworld && mergemastger > 6. take a deep breath & reboot > 7. portupgrade -afi > 8. make delete-old && make delete-old-libs > 9. reboot > 10. Hooray! > > My concern is - will my ports works after point 6. ? Quite important > thing when machine can't be offline by hours during portupgrade -afi You can compress 2 and 3 into: make buildworld && make kernel. To save a LOT of time on SMP systems, use -jN where N is at least (numcpus + 1). IF you get an error with -j, build again without '-jN' and with '-DNO_CLEAN" to quickly find the real error. Do a delete-old. Hold off on delete-old-libs for a bit. (It's generally the old header files which bite, but keeping libs is "safe".) The problem is that, when you start updating ports, you will eventually (and probably pretty quickly) end up with a port that links to two libraries which, in turn, link to a "common" library, but one links to the old and one to the new. When this happens, the real-time loader (rtld) will object strongly and one or more ports are rendered un-runnable. libmap.conf(5) can usually be used as a temporary way to get things working again, but it does not always work. Version numbers are only bumped because there is a reason (I hope). I suggest that you install packages (-P) for any ports that are not using special options. It can save hours of time. Also, use script or something else to keep a copy of the output of the portupgrade. It can be very handy in fixing any problems that crop up. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ 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: Netowrk Card BCE not working
We are having the same issue on 8.0-BETA2 with a Dell R610. Google shows users with Dell M610 (blade server), and T610 (tower server) models having this problem as well. Please fix for 7.2-RELEASE and patch in time for 8.0-RELEASE! Umar wrote: > > Dear Members! > > I have recently Install FreeBSD 7.2 amd64 on DELL R610. > > After successfuly installation network cards are not working and i got > error > > bce0: /usr/src/dev/bce/if_bce.c(1386): Unable to write CTX memory: > cid_addr = 0x008, offset = 0x0080 > > Would you please help me what should I do? > > Regards, > > Umar > -- View this message in context: http://www.nabble.com/Netowrk-Card-BCE-not-working-tp24995981p25013231.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ 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: READ_BIG w/DVD-pata motion? (kern/133122)
Gavin Atkinson wrote: > On Mon, 2009-08-17 at 10:58 -0400, Charles Owens wrote: > >> Just under a month ago I added a comment to this bug, to share that >> we're seeing this issue consistently with one of the HP appliance >> platforms that we support (with both FreeBSD 7.0 and 7.1). This bug >> (marked as "serious") is still in the "open" state, with as yet no >> sign >> that anyone is working on it. Does anyone have a sense as to when it >> might be given a good look? >> > > A few bits of information are missing from that PR, it would be useful > if you could add the following to it: > > - A full verbose dmesg > - two outputs of "vmstat -i", say 10 seconds apart, both before and > after the problems start. > > FWIW, I'm not convinced that your problem is the same as the submitter's > problem - he's complaining only on issues when he hits the last block of > the CD, and you're having problems with slow reads throughout the whole > CD. If you're not using a "JMicron JMB363 SATA300 controller" it's > likely your issue is different to kern/133122 and it would be worth > creating a new PR with a full description of exactly what symptoms you > see, and the above information. > > Gavin > Thanks... we'll work on submitting a new PR as you've suggested. Charles ___ 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: READ_BIG w/DVD-pata motion? (kern/133122)
On Mon, 2009-08-17 at 10:58 -0400, Charles Owens wrote: > Just under a month ago I added a comment to this bug, to share that > we're seeing this issue consistently with one of the HP appliance > platforms that we support (with both FreeBSD 7.0 and 7.1). This bug > (marked as "serious") is still in the "open" state, with as yet no > sign > that anyone is working on it. Does anyone have a sense as to when it > might be given a good look? A few bits of information are missing from that PR, it would be useful if you could add the following to it: - A full verbose dmesg - two outputs of "vmstat -i", say 10 seconds apart, both before and after the problems start. FWIW, I'm not convinced that your problem is the same as the submitter's problem - he's complaining only on issues when he hits the last block of the CD, and you're having problems with slow reads throughout the whole CD. If you're not using a "JMicron JMB363 SATA300 controller" it's likely your issue is different to kern/133122 and it would be worth creating a new PR with a full description of exactly what symptoms you see, and the above information. Gavin ___ 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"
READ_BIG w/DVD-pata motion? (kern/133122)
Hello, Just under a month ago I added a comment to this bug, to share that we're seeing this issue consistently with one of the HP appliance platforms that we support (with both FreeBSD 7.0 and 7.1). This bug (marked as "serious") is still in the "open" state, with as yet no sign that anyone is working on it. Does anyone have a sense as to when it might be given a good look? http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/133122 Thanks much, Charles -- **Charles Owens** *Great Bay Software* ___ 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 7.1 (and 7.2) Breaks re and rl Network Interface Drivers
On Mon, 9 Mar 2009 17:33:06 +0900 Pyun YongHyeon wrote about Re: FreeBSD 7.1 Breaks re and rl Network Interface Drivers: PY> > I cannot say if the actual issue I had with 7.1-stable has gone PY> > away, too, because this only occured after a longer time of PY> > operation. However, up to now everything looks nice. PY> Ok, if you find any re(4) instability feel free to contact me. Ok, took some time, but here I am. :-) It seems I have two different version of the Jetway mainboard here (one with 25W total power consumption and one with 12W I guess). Anyway, my version of 7.1 with your patches is running fine on this board: --- Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-STABLE #0: Tue Mar 24 12:46:03 CET 2009 r...@xenon:/usr/tmp/usr/obj/usr/work/current/src/sys/FIREFLY Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: VIA C7-D Processor 1500MHz (1500.02-MHz 686-class CPU) Origin = "CentaurHauls" Id = 0x6d0 Stepping = 0 Features=0xa7c9baff Features2=0x4001 VIA Padlock Features=0xffcc real memory = 1055784960 (1006 MB) avail memory = 1023750144 (976 MB) kbd1 at kbdmux0 cryptosoft0: on motherboard padlock0: on motherboard acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3ede (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci_link2: BIOS IRQ 5 for 0.9.INTA is invalid pci_link2: BIOS IRQ 5 for 0.16.INTC is invalid pci_link2: BIOS IRQ 5 for 0.17.INTC is invalid pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: mem 0xf400-0xf7ff,0xfb00-0xfbff irq 11 at device 0.0 on pci1 re0: port 0xf000-0xf0ff mem 0xfdfff000-0xfdfff0ff irq 10 at device 9.0 on pci0 re0: Chip rev. 0x1800 re0: MAC rev. 0x miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:30:18:a7:8a:1c re0: [FILTER] re1: port 0xf200-0xf2ff mem 0xfdffe000-0xfdffe0ff irq 10 at device 11.0 on pci0 re1: Chip rev. 0x1800 re1: MAC rev. 0x miibus1: on re1 rgephy1: PHY 1 on miibus1 rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re1: Ethernet address: 00:30:18:a7:8a:1d re1: [FILTER] atapci0: port 0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f,0xf400-0xf4ff irq 11 at device 15.0 on pci0 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f at device 15.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] ata1: on atapci1 ata1: [ITHREAD] uhci0: port 0xf900-0xf91f irq 11 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xf800-0xf81f irq 11 at device 16.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xf700-0xf71f irq 11 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xf600-0xf61f irq 11 at device 16.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xfdffd000-0xfdffd0ff irq 10 at device 16.4 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered isab0: at device 17.0 on pci0 isa0: on isab0 pci0: at device 17.5 (no driver attached) acpi_tz0: on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse Explorer, device ID 4 cpu0: on acpi0 acpi_throttle0: on cpu0 pmtimer0 on isa0 orm0: at iomem 0xc-0xcf7ff pnpid ORM on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter "TSC" frequency 1500015037 Hz quality 800 Timecounters tick every 1.000 msec ad0: 3
Re: Fwd: How do I mount an external ntfs formatted harddisk manually and through /etc/fstab?
On Sun, 2009-08-16 at 19:32 +0200, Jens Rasmus Liland wrote: > Hi, > > Sorry for the late reply - I went on vacation for a while. > > I think 'mount_ntfs-3g' did the trick in terms of mounting /dev/da0s1 > manually. But I tried to add > > /dev/da0s1 /homewd ntfs-3gro 0 0 > > ... but then the computer panicked, and went into single user mode. I think > it happened because the ntfs-3g module is loaded later with the > fusefs-stuff. How to get around this one? Make sure you have recompiled fusefs, ntfs-3g and any other ports that they rely on since you last upgraded your kernel/world. The fusefs kernel module seems to be quite sensitive to changes in the kernel itself. Gavin ___ 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: Going to BSD 8 from RELENG_7
On 14/08/09 11:12 AM, Dan Allen wrote: I cvsup and build RELENG_7 many times a week. This has served me well (except for the ZFS boot problem I had that went in and was backed out) for quite a while. I like to track a STABLE release. When BSD 7 went to 7.1 and to 7.2, it all just happened automatically with the way I do things. Now I am interested on one of my BSD machines to try 8.0. I need to change my cvsup target from RELENG_7 to CURRENT I believe. Is that true? When will STABLE become 8.0? Since I see you are updating from 7 to 8 and are running ZFS, you may be bitten by the fact that ZFS will not work after you install the new kernel. See the last comment here: http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html Ari --> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A ___ 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: Going to BSD 8 from RELENG_7
Ruben de Groot pisze: On Mon, Aug 17, 2009 at 09:18:11AM +0200, Bartosz Stec typed: And as usual MAKE A GOOD BACKUP Regards, Johan As I remember when I did upgrade from FreBSD 6.4 to 7.0, I ran 'portupgrade -afi' after thar, BUT as I remember all my ports in fact works before they were upgraded. If I understand correctly, the reason of this was not making delete-old and delete-old-libs? So should following upgrade procedure be painless? 0. Backup! 1. cvsup 8.0-stable 2. make buildworld && make buildkernel 3. make installkernel 4. reboot and jump to single user mode 5. make installworld && mergemastger 6. take a deep breath & reboot 7. portupgrade -afi 8. make delete-old && make delete-old-libs 9. reboot 10. Hooray! My concern is - will my ports works after point 6. ? Quite important thing when machine can't be offline by hours during portupgrade -afi What do you want to hear? "Yes, all will be fine" ? There's never such guarantee. If it means that much to you, MAKE A GOOD BACKUP. And be prepared to restore it. And if the machine really can't be offline for some hours, you should have a fallback machine anyway which you could use to test it on. cheers, Ruben Oh well, I don't want to hear any guarantees :) . Simple 'It should be OK' or 'You will probably get into troubles with this procedure so use test machine first' would be great. Fortunately Johan Hendriks already gave me answer that explained everything: If the old libs are still there all ports will work after the reboot. So a reboot should do no harm. To test this, try it First on a spare box. this way you will see the problems, or issues if they arise. Also make sure your hardware is fully supported by FreeBSD 8, I always put in a livecd and try all my drive's and mirrors and so on. Also be aware that the libusb port is in the base system on 8. And i do not know if they work on a 8 system with the libusb port installed. But it sounds like a server so there should be little ports that needs libusb. Thank you Johan. -- Bartosz Stec ___ 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: Going to BSD 8 from RELENG_7
On Mon, Aug 17, 2009 at 09:18:11AM +0200, Bartosz Stec typed: > > > >And as usual MAKE A GOOD BACKUP > > > >Regards, > >Johan > > > As I remember when I did upgrade from FreBSD 6.4 to 7.0, I ran > 'portupgrade -afi' after thar, BUT as I remember all my ports in fact > works before they were upgraded. If I understand correctly, the reason > of this was not making delete-old and delete-old-libs? > > So should following upgrade procedure be painless? > > 0. Backup! > 1. cvsup 8.0-stable > 2. make buildworld && make buildkernel > 3. make installkernel > 4. reboot and jump to single user mode > 5. make installworld && mergemastger > 6. take a deep breath & reboot > 7. portupgrade -afi > 8. make delete-old && make delete-old-libs > 9. reboot > 10. Hooray! > > My concern is - will my ports works after point 6. ? Quite important > thing when machine can't be offline by hours during portupgrade -afi What do you want to hear? "Yes, all will be fine" ? There's never such guarantee. If it means that much to you, MAKE A GOOD BACKUP. And be prepared to restore it. And if the machine really can't be offline for some hours, you should have a fallback machine anyway which you could use to test it on. cheers, Ruben ___ 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: Going to BSD 8 from RELENG_7
Johan Hendriks pisze: Be aware that if you go from 7 to 8 you will need to rebuild all your installed ports. ALso if you do a buildworld from 7 to 8 do not do the make delete-old and the make delete-old-libs before you have rebuild your ports. If you do the make delete-old and make delete-old-libs runs, all ports depending on the FreeBSD 7 libs will not work any more. << read: most likely all your ports. If you have changed for example your Shell for root to a ports based shell like bash and you do the make delete-old-libs you can not log in anymore, because bash depends on the 7 libs wich are not there anymore. And as usual MAKE A GOOD BACKUP Regards, Johan As I remember when I did upgrade from FreBSD 6.4 to 7.0, I ran 'portupgrade -afi' after thar, BUT as I remember all my ports in fact works before they were upgraded. If I understand correctly, the reason of this was not making delete-old and delete-old-libs? So should following upgrade procedure be painless? 0. Backup! 1. cvsup 8.0-stable 2. make buildworld && make buildkernel 3. make installkernel 4. reboot and jump to single user mode 5. make installworld && mergemastger 6. take a deep breath & reboot 7. portupgrade -afi 8. make delete-old && make delete-old-libs 9. reboot 10. Hooray! My concern is - will my ports works after point 6. ? Quite important thing when machine can't be offline by hours during portupgrade -afi -- Bartosz Stec ___ 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"
