Re: Problems with zfsboot loader if raidz present on any drive
On Sun, Dec 7, 2008 at 9:22 AM, Doug Rabson [EMAIL PROTECTED] wrote: On 7 Dec 2008, at 03:19, Pegasus Mc Cleaft wrote: Hello Hackers, Recently and friend and I have been trying to get the new gptzfsboot working on our machines and ran into a interesting problem. Initially I was building the world without the environment variable LOADER_ZFS_SUPPORT=YES in the /etc/make.conf and this, of course, didnt work very well. Every time the machine booted, it would throw 2 lines after the pin-wheel and then reboot. I couldent read what the lines were it went so fast. My friend had a bit more luck and got his machine working OK with a single drive and later a mirror drive added. I added the environment variable and rebuilt everything and installed. This time, I could see the bios drives and a further 2 lines of ZFS something and a reboot... No matter what I tried, I couldent get the machine to boot up to a point where I could try and fix the problem, so I started pulling devices out and found the following: If there is a raidz pool on any drive (not necessarily the one that you are trying to boot from) the loader dies and reboots the machine. My friend, as an experiment created 3 gpt partitions (in addition to the single partition that he had been previously booted from) on his single drive and made a raidz pool for testing. His machine showed the same condition as mine, however he was able to capture the message before the machine rebooted: message ZFS: can only boot from disk or mirror vdevs ZFS: inconsistent nvlist contents The zfsboot code in current doesn't support raidz or raidz2. I have been working on adding that support but its not ready yet. The code works in my test harness but crashes instantly when I put it in the boot code :(. I should have time to finish debugging it soon. After installing my system yesterday on a single disk with gptzfsboot, I connected my old raidz and I only got cyclic reboots. I knew instantly it had something to do with the raidz. Disconnecting 2 out of the 4 disks of the raidz would allow the system to boot as the raidz would not present itself as ONLINE. As a temporary workaround for this problem I disabled those 2 disks on the BIOS, the system boots fine and the kernel is able to find them later. Doug, when you feel comfortable to share any patches, I'm willing to test :-) -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Introducing me!!
On Tue, Apr 22, 2008 at 2:47 PM, Ryan French [EMAIL PROTECTED] wrote: Hi All, My name is Ryan French. I am a Google Summer of Code participant this year, and for my project I will be implementing MPLS in FreeBSD. I am in my 5th year of university at the University of Waikato in New Zealand, and this year I am working on obtaining my PostGraduate Diploma in Computer Science (equivalent to the first year of a masters degree). I'm really looking forward to working on this project, as it is also part of my coursework for this year. I'm still in the process of getting through all the introduction stuff to the GSoC, but once that has been done I'm going to continue working on this project and hopefully come up with something that I can be real proud of over the next few months. Hi Ryan, Congratulations on being selected as a participant :-) I have a friend, Nuno Antunes, that started implementing MPLS in FreeBSD but then he went to the dark side (kidding) and continued the work on DragonFlyBSD. I talked to him today after seeing your application being selected to know how far he went. He based his work on the ayame project and nist switch and he has a semi functional patch here: http://leaf.dragonflybsd.org/~nant/wip/mpls-20071109.patch The sad news is that he doesn't have time to continue the implementation, so I'm hopping you make us all proud ;-) -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Patch RFC: Promise SATA300 TX4 hardware bug workaround.
On 11/20/07, Thierry Herbelot [EMAIL PROTECTED] wrote: Le Tuesday 20 November 2007, Ari Suutari a écrit : I have Promise TX2 (PDC20575). It didn't work with 7.0 betas before, but with this patch things run as well as they did on 6.x. Ari S. Hello, Has anyone an idea why the Promise controllers seemed to work correctly under 6.x, then have issues with 7.0 ? (more precisely : was the existing bug not triggered by the 6.x kernel ?) Apparently not all Promise controllers are/were affected. I've been running CURRENT since Pawel committed ZFS with an onboard Promise: atapci0: Promise PDC20319 SATA150 controller port 0xb000-0xb03f,0xb400-0xb40f,0xb800-0xb87f mem 0xfc024000-0xfc024fff,0xfc00-0xfc01 irq 23 at device 4.0 on pci4 ar0: 305245MB Promise Fasttrak RAID0 (stripe 64 KB) status: READY ar1: 305245MB Promise Fasttrak RAID0 (stripe 64 KB) status: READY [EMAIL PROTECTED]:4:4:0: class=0x010400 card=0x80f51043 chip=0x3319105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20319(??) FastTrak SATA150 TX4 Controller' class = mass storage subclass = RAID The only problem I have and I'm filling a pr for that, is when booting from CD with the controller enabled, the BTX loader just reboots. -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HP SmartArray ( CISS ) and CAMCONTROL
Hi, I'm porting bio(4) from OpenBSD to FreeBSD and lost access to a ciss card after switching jobs. I'm starting with support for amr as I own one. Would you be willing to test patches for ciss later on? On 6/11/07, Mark Saad [EMAIL PROTECTED] wrote: Hello Hackers@ I have been searching around and I can not find an answer to a problem of mine . Does anyone know if its possible to make camcontrol show the drive health for drives in a HP SMART Array . Currently it will show the Array heath by running camcontrol devlist -v . jumpstart# camcontrol devlist -v scbus0 on ciss0 bus 0: COMPAQ RAID 1 VOLUME OK at scbus0 target 0 lun 0 (pass0,da0) COMPAQ RAID 1 VOLUME OK at scbus0 target 1 lun 0 (pass1,da1) scbus1 on ciss0 bus 32: scbus-1 on xpt0 bus 0: at scbus-1 target -1 lun -1 (xpt0) -- Mark Saad [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] add header pppoe: in ng_pppoe.c printfs
On 8/5/06, Joao Barros [EMAIL PROTECTED] wrote: On 8/4/06, Gleb Smirnoff [EMAIL PROTECTED] wrote: On Fri, Aug 04, 2006 at 04:48:49PM +0100, Joao Barros wrote: J On 8/4/06, Gleb Smirnoff [EMAIL PROTECTED] wrote: J On Thu, Aug 03, 2006 at 03:35:04PM +0100, Joao Barros wrote: J J Being this a cryptic message to say the least and to probably save J J someone some time when presented with this message I attach a patch J J that adds the header pppoe: in every printf that didn't have it, J J making it consistent with the rest of the file. J J I've attached a patch that cleans a bit logging in ng_pppoe. It changes J all printf(9) to log(9). The latter is better since it spams console J less, if event occurs many times per second. Also I've made the messages J more clear - prepended node ID where possible, function name when it J starts with ng_pppoe, or just ng_pppoe. J J Can you please try out this patch and tell whether you like it. If you J do I will commit it soon. J J Hi, J J I've looked at the patch and it looks ok. J It serves the purpose: make the messages more clear with the added J bonus of more info. J Thanks for taking the time to look into this :-) Since I don't use ng_pppoe now much, I'd appreciate if you do at brief test of this patch, before I commit it. I patched and recompiled the kernel. After booting I notice that no messages from ppp are logged by syslog (messages|ppp.log) If I restart ppp the messages are all logged. I can't say if this was happening because after setting ppp up I didn't reboot the machine. I didn't browse the startup scripts but maybe syslog is not started before pppoe. Now it will take more than 17 hours for the session limit to be exceeded and only then I can say how your patch worked out. I'll make an update then. Ok, here's the new output just before the connection was dropped (earlier than usual): Aug 5 07:28:50 ultra5 kernel: ng_pppoe[5]: session in wrong state Aug 5 07:28:50 ultra5 last message repeated 3 times Looks fine to me :-) -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: syslog bug ? (was Re: [PATCH] add header pppoe: in ng_pppoe.c printfs)
On 8/5/06, Luigi Rizzo [EMAIL PROTECTED] wrote: On Sat, Aug 05, 2006 at 12:42:12AM +0100, Joao Barros wrote: ... I patched and recompiled the kernel. After booting I notice that no messages from ppp are logged by syslog (messages|ppp.log) What is your OS version ? FreeBSD ultra5.bsdtech.org 6.1-RELEASE-p1 FreeBSD 6.1-RELEASE-p1 #1: Fri Aug 4 23:18:19 WEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ultra5 sparc64 Your problem is likely because ppp starts before the syslog daemon, the initial message fails and then you get nothing anymore. I guessed that much but I still haven't verified the init scripts. -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] add header pppoe: in ng_pppoe.c printfs
On 8/4/06, Gleb Smirnoff [EMAIL PROTECTED] wrote: On Thu, Aug 03, 2006 at 03:35:04PM +0100, Joao Barros wrote: J Being this a cryptic message to say the least and to probably save J someone some time when presented with this message I attach a patch J that adds the header pppoe: in every printf that didn't have it, J making it consistent with the rest of the file. I've attached a patch that cleans a bit logging in ng_pppoe. It changes all printf(9) to log(9). The latter is better since it spams console less, if event occurs many times per second. Also I've made the messages more clear - prepended node ID where possible, function name when it starts with ng_pppoe, or just ng_pppoe. Can you please try out this patch and tell whether you like it. If you do I will commit it soon. Hi, I've looked at the patch and it looks ok. It serves the purpose: make the messages more clear with the added bonus of more info. Thanks for taking the time to look into this :-) -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] add header pppoe: in ng_pppoe.c printfs
On 8/4/06, Gleb Smirnoff [EMAIL PROTECTED] wrote: On Fri, Aug 04, 2006 at 04:48:49PM +0100, Joao Barros wrote: J On 8/4/06, Gleb Smirnoff [EMAIL PROTECTED] wrote: J On Thu, Aug 03, 2006 at 03:35:04PM +0100, Joao Barros wrote: J J Being this a cryptic message to say the least and to probably save J J someone some time when presented with this message I attach a patch J J that adds the header pppoe: in every printf that didn't have it, J J making it consistent with the rest of the file. J J I've attached a patch that cleans a bit logging in ng_pppoe. It changes J all printf(9) to log(9). The latter is better since it spams console J less, if event occurs many times per second. Also I've made the messages J more clear - prepended node ID where possible, function name when it J starts with ng_pppoe, or just ng_pppoe. J J Can you please try out this patch and tell whether you like it. If you J do I will commit it soon. J J Hi, J J I've looked at the patch and it looks ok. J It serves the purpose: make the messages more clear with the added J bonus of more info. J Thanks for taking the time to look into this :-) Since I don't use ng_pppoe now much, I'd appreciate if you do at brief test of this patch, before I commit it. I patched and recompiled the kernel. After booting I notice that no messages from ppp are logged by syslog (messages|ppp.log) If I restart ppp the messages are all logged. I can't say if this was happening because after setting ppp up I didn't reboot the machine. I didn't browse the startup scripts but maybe syslog is not started before pppoe. Now it will take more than 17 hours for the session limit to be exceeded and only then I can say how your patch worked out. I'll make an update then. -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
[PATCH] add header pppoe: in ng_pppoe.c printfs
Hi, I recently switched ISPs which in turn led me from a cablemodem to an ADSL modem. After setting PPPoE up I started noticing this messages in the daily run outputs that that nice guy Charlie root sends me at 3am: Aug 3 08:24:54 ultra5 kernel: session in wrong state I was a bit suspicious of anything PPPoE related and a little search confirmed that, pointing directly at ng_pppoe.c Being this a cryptic message to say the least and to probably save someone some time when presented with this message I attach a patch that adds the header pppoe: in every printf that didn't have it, making it consistent with the rest of the file. I also noticed this message appears right before the ISP closes the connection due to time limit. I'm CCing those I see were the last ones to commit to this file and will file a PR if asked to. -- Joao Barros ng_pppoe.c.patch Description: Binary data ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sysinstall: Write the FreeBSD version at the top of the display
On 7/12/06, Gábor Kövesdán [EMAIL PROTECTED] wrote: Joao Barros wrote: Hi all, I was browsing the list of projects and ideas and stumbled upon one that's rather simple and which would have been useful in the past: Write the FreeBSD version at the top of the display (or somewhere similar visible) - so lazy users know what they are installing (version: release, stable, snapshot + arch: i386, amd64, etc) even when the CD is unlabeled. I'm changing the title of the Main menu using sysctlbyname to: FreeBSD kern.osrelease hw.machine_arch - sysinstall Main Menu The result would be: FreeBSD 7.0-CURRENT i386 - sysinstall Main Menu Screenshot of the result: http://img55.imageshack.us/img55/980/sysintall17vv.png If this is what is pretended I'll post the patch. I think this is pretended, but anyway, it's a nice feature, so I suggest you send-pr-ing the patch by all. Hi, Here's the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=100309 -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Sysinstall: Write the FreeBSD version at the top of the display
Hi all, I was browsing the list of projects and ideas and stumbled upon one that's rather simple and which would have been useful in the past: Write the FreeBSD version at the top of the display (or somewhere similar visible) - so lazy users know what they are installing (version: release, stable, snapshot + arch: i386, amd64, etc) even when the CD is unlabeled. I'm changing the title of the Main menu using sysctlbyname to: FreeBSD kern.osrelease hw.machine_arch - sysinstall Main Menu The result would be: FreeBSD 7.0-CURRENT i386 - sysinstall Main Menu Screenshot of the result: http://img55.imageshack.us/img55/980/sysintall17vv.png If this is what is pretended I'll post the patch. -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel source hacking
On 11/5/05, Robert Watson [EMAIL PROTECTED] wrote: On Fri, 4 Nov 2005, Joao Barros wrote: On 11/4/05, Robert Watson [EMAIL PROTECTED] wrote: On Thu, 3 Nov 2005, M. Warner Losh wrote: : Also, is there a page with other tasks for kernel neophytes like me? I : looked for some such page but I couldn't find any. phk used to have a /jkh/ page, or Junior Kernel Hacker page. Don't know if that's still that way or not. Now that we have a FreeBSD Developer wiki, it may make sense to move the page there so it can be more easily reached and maintained by a broader set of developers? Could you please provide the link for the Wiki? Thanks. A test wiki for developer use has been set up here: http://wikitest.FreeBSD.org/ Its primary use so far has been to host content for the Google Summer of Code students, although other content is also starting to make it onto the Wiki. I think the primary reason it's still considered experimental is that it is hosted outside the FreeBSD.org cluster. Robert N M Watson I was there earlier when you mentioned a link to the MySQL section on the latest MySQL performance on FreeBSD thread on stable@ (I think) but never got around to see the rest of the wiki. Thank you and Wesley for the reply. -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel source hacking
On 11/4/05, Robert Watson [EMAIL PROTECTED] wrote: On Thu, 3 Nov 2005, M. Warner Losh wrote: : Also, is there a page with other tasks for kernel neophytes like me? I : looked for some such page but I couldn't find any. phk used to have a /jkh/ page, or Junior Kernel Hacker page. Don't know if that's still that way or not. Now that we have a FreeBSD Developer wiki, it may make sense to move the page there so it can be more easily reached and maintained by a broader set of developers? Could you please provide the link for the Wiki? Thanks. Robert N M Watson -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Driver Development Books?
On 10/11/05, Pete [EMAIL PROTECTED] wrote: Hello, I have what may seem to be a silly question, but I cannot find any other decent resources on the web. . The problem that I am having right now is that I have a fairly nice graphics card which, for the moment is only supported on Windows Operating systems, and old 2.4 Linux kernels. So far there has not been much positive outlook in porting the drivers to *BSD or any of the 2.6 kernels that I know of, let alone 64-bit drivers for non-Win OSes. So I guess that makes my question fairly simple then; I know that driver code is written in C (which I am learning currently) but thats about all I know. I'm probably not far off when I say that I need more to go on. Yet, from looking at Amazon.com I have not been able to find any books on writing driver code, which is really frustrating. One of my security related books, Rootkits, tells me about how to write drivers for a completely different reason so I know a bit more about how they work but again the code involved does not interface hardware to the OS, just injects a custom application. The other tool that I will probably use is Jungo, which is a nice-looking application which automates a skeletal version of the driver you need, but again, I would not know how to fill it out. Any help is appreciated. -Pete I started porting a pseudo driver from OpenBSD and had the same issues. You could find more info here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/index.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/newbus-api.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/driverbasics-char.html#AEN8703 And this come in very handy: FreeBSD Source Code Tour: http://snapshots.jp.freebsd.org/tour/ A nice website provided by Robert Watson (Thanks!!!): http://fxr.watson.org/ Looking at existing code is also good, like the simple led driver by phk@ There was also a thread where John Baldwin described the parts of a driver but I can't seem to find it. -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Importing bio aka RAID Management Framework from OpenBSD
Hi all, I proposed to import bio aka RAID Management Framework from OpenBSD. I have studied how bio is implemented in OpenBSD and here is a quick resume of the 3 components that make bio: - bio - ioctl tunnel pseudo-device /dev/bio.c biovar.h The bio driver provides userland applications ioctl access to devices otherwise not found as /dev nodes. The /dev/bio device node operates by delegating ioctl(2) calls to a requested device driver. Only drivers which have registered with the bio device can be accessed via this inter- face. - ciss, amr - supported device drivers - bioctl - RAID management interface RAID device drivers which support management functionality can register their services with the bio(4) driver. bioctl then can be used to main- tain RAID volumes. After analysing the structure of /src my initial idea was: new /src/sys/contrib/dev/bio/bio.c biovar.h new /src/sys/modules/bio/makefile new /src/contrib/bio/bioctl.c edit amr and ciss to register themselves on bio 1st: are these the correct places to be putting this files? 2nd: the drivers need to register to bio, this one being a kernel module. If bio is not compiled in that can represent a problem. Ideas? References: Theo De Raadt initial presentation of bio: http://marc.theaimsgroup.com/?l=openbsd-miscm=112630095818062 bio manpage: http://www.openbsd.org/cgi-bin/man.cgi?query=biosektion=4arch=i386apropos=0manpath=OpenBSD+Current bioctl manpage: http://www.openbsd.org/cgi-bin/man.cgi?query=bioctlsektion=8arch=i386apropos=0manpath=OpenBSD+Current -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: Re: Linksys WRT54G with freebsd
On 9/23/05, Scott Long [EMAIL PROTECTED] wrote: Bruno Ducrot wrote: On Fri, Sep 23, 2005 at 01:50:45PM +0200, Florent Thoumie wrote: Le Vendredi 23 septembre 2005 à 12:16 +0200, Bachilo Dmitry a écrit : Forwarding to FreeBSD hackers. (Because i am hacking WRT right now and only Linux flashes work) -- ?? ?? -- Subject: Re: Linksys WRT54G with freebsd Date: ?? 23 2005 17:06 From: Thierry Herbelot [EMAIL PROTECTED] To: freebsd-current@freebsd.org Cc: Marcos Biscaysaqu - ThePacific.net [EMAIL PROTECTED] Le Friday 23 September 2005 11:08, vous avez écrit : On the other hand, it's the wireless thing. If not needed, this should be fun to do a port, somehow, even though it's a wireless router. The cool factor of porting FreeBSD to the WRT54G cannot be underestimated, but Linux ports were enormously helped by the opening of the sources of the Linksys Linux port (which is absent for FreeBSD) and the big number of willing developpers (just have a look at the *number* of different Linux ports to the WRT). The latest 6.0 release would be an excellent target, with its brand-new support for WPA and virtual APs ... who volunteers ? The Linksys WRT54g wireless router is based on a Broadcom CPU (derived from MIPS) and FreeBSD/mips seems to be a dead project :-( Indeed. It's targeted to SGI platforms anyway. Maybe there is a need to start a new port if there is enough people interrested? There has been talk of doing this in the past year from some people, but I don't know if it got very far. If you're inspired, go for it! There are plenty of docs on the web about how to attach a serial port header and bootstrap it. And, don't underestimate the mips32 work that is already in the tree; it's likely a good starting point. And, it's more than just a 'coolness' factor. I'd really like to have pf running on mine, that way I could rid of the clunky machine doing static NAT + firewall on my DSL line. Scott m0n0wall or it's version on steroids pfsense would be real cool to have on a WRT54g 8) THe linux firewall capabilities are soo last century =-) Except for some nice projects/patches that do Layer 7 and allow filtering or queueing on specific traffic. ALTQ applied to marked packets would be lovely :) This would be very nice to have, except everyone (Daniel Hartmeier included) tells it's a bad ideia to have protocol inspection at the firewall level well, going off topic but couldn't resist ;) -- Joao Barros ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
