Re: Intel 6300ESB SATA and TIMEOUT - WRITE_DMA
Roger O. Svenning wrote: On 14/09/2005, at 17:36, Roger O. Svenning wrote: You should try 6.0-beta4 as that contains the solution to whatever ATA problems you might have on 5.x. Let me know how that goes. Søren Schmidt [EMAIL PROTECTED] cvsup running as I'm writing this Would I waste my time trying to enable raid on this controller? Depends, its software RAID, so support relies on ataraid supporting the on-disk metadata format, but you can try to setup a RAID on the disks, it will get picked up if known.. Søren Schmidt [EMAIL PROTECTED] Ok, 6.0-beta4 built and installed successfully. I'm sorry to report I still get the timeouts. On the other hand it does recognize the (old) raid arrays now. Oh well, replacing the SATA cable fixed it, I'm terribly sorry about that :( On the upside the SATA Raid seem to work nicely on 6.0-beta4 so the upgrade did not turn out to be a waste of time. Thanks a lot for the help Søren NP! I'm just happy it works for you.. -- -Søren ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: network settings
Bachilo Dmitry wrote: > В сообщении от Воскресенье 18 Сентябрь 2005 22:10 eoghan написал(a): > > You should write all the stuff to /etc/rc.conf (see man rc.conf for that), but > in my opinion if you actually did /stand/sysinstall many times, your rc.conf > "got cancer" if i can say so, because it writes the changes all the time in > rc.conf not deleting previous. You should just write once something like: > > ifconfig_xl0="inet netmask "' > defaultrouter="" > > and write down to the /etc/resolve.conf: > > nameserver > > > or simply write down to /etc/rc.conf: > ifconfig_xl0="DHCP" Thanks for the info. i did have a look through the rc.conf and it sure does look like its written the settings many times. Does anyone have a sample of a clean rc.conf? Also, my network assign ip's to each pc on the network. I noticed in the conf the ip was specified, which can change... is there any way of doing this in the rc.conf? Eoghan ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: network settings
В сообщении от Понедельник 19 Сентябрь 2005 16:37 eoghan написал(a): > Bachilo Dmitry wrote: > > В сообщении от Воскресенье 18 Сентябрь 2005 22:10 eoghan написал(a): > > > > You should write all the stuff to /etc/rc.conf (see man rc.conf for > > that), but > > > in my opinion if you actually did /stand/sysinstall many times, your > > rc.conf > > > "got cancer" if i can say so, because it writes the changes all the > > time in > > > rc.conf not deleting previous. You should just write once something > > like: > > > > ifconfig_xl0="inet netmask "' > > defaultrouter="" > > > > and write down to the /etc/resolve.conf: > > > > nameserver > > > > > > or simply write down to /etc/rc.conf: > > ifconfig_xl0="DHCP" > > Thanks for the info. i did have a look through the rc.conf and it sure > does look like its written the settings many times. Does anyone have a > sample of a clean rc.conf? Also, my network assign ip's to each pc on > the network. I noticed in the conf the ip was specified, which can > change... is there any way of doing this in the rc.conf? > Eoghan Here's mine /etc/rc.conf from work's router (shorted): defaultrouter="192.168.65.4" gateway_enable="YES" hostname="storage.solink.office" ifconfig_rl0="inet 192.168.1.1 netmask 255.255.255.0" ifconfig_rl1="inet 192.168.66.166 netmask 255.255.240.0" inetd_enable="YES" keymap="ru.koi8-r" keyrate="fast" linux_enable="YES" mousechar_start="3" moused_enable="YES" saver="logo" scrnmap="koi8-r2cp866" sshd_enable="YES" usbd_enable="YES" And here is mine from notebook: font8x14="cp866-8x14" font8x16="cp866b-8x16" font8x8="cp866-8x8" hostname="notebook.bochasnet.academ.local" ifconfig_rl0="DHCP" keymap="ru.koi8-r" keyrate="fast" linux_enable="YES" mousechar_start="3" moused_enable="YES" saver="logo" scrnmap="koi8-r2cp866" sshd_enable="YES" usbd_enable="YES" As you can see on the first one i heve static IP and default router specified, and on the second i have dynamic parameters. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Issues with installing FreeBSD 5.4 from a DOS partition
Now, I'm somewhat new to FreeBSD, but I've really enjoyed it as an OS so far, and found it to be quite fast, stable, and well laid out. Some things I've found difficult to get used to but I'm by and large quite impressed. Anyway, I set up 5.3 a while back from a DOS partition using the 5.3 boot disks, as I'm using an older 450 mhz pentium III which refused to boot from the CD drive for whatever reason. This went well, but some ports were having issues compiling, and a few other things so I decided to upgrade to 5.4, full clean install. First of all, I don't know if this is just a problem with my hardware, but it seems to me that the 'Install from ftp' option is broken in 5.4 and above - on both the computers I tried, they would hang on a 'part length 0' error most of the way through installing the docs dist - always at the same place, from whatever ftp I downloaded it from. On attempting to install version 6 the same way, I had the same problem on both pcs, in a slightly different portion of the install. So I decided to go the DOS partition route, as it seemed to be the best alternative. This is what I chose to do with 5.3 as well. My method in 5.3 was to first download the 5.3 disc 1 iso image from ftp.freebsd.org, extract the image to the DOS partition and install. However, as you are probably aware, the premade images in 5.4 and above are on two discs instead of just needing the one. Well, this ends up presenting a problem. Also in 5.4, there was a change in the INDEX file of the packages, and it will prompt you as to which CD has the package you want to install, and to please put that CD in. As you might imagine, it's difficult to switch cds when you are in fact installing off of a DOS partition. The fact that it's a DOS partition also makes it difficult to mount the drive beforehand, go into the packages directory and run 'make index'. What I ended up doing to resolve this was to go into the INDEX file in the /packages directory, and switch all the pipes at the end of each line to point to CD_DRIVE 0 instead of the 1 or 2 which they were pointed at. This fixed the problem, and 5.4 installed normally. Now, I didn't see any sort of mention of this anywhere in any docs I could find. The official install instructions didn't say anything about this in the section on installing from a DOS partition, or in the errata, etc. I also couldn't find any docs on how to edit the INDEX file and so on, so it's half luck that I even found a viable solution. I realize that almost all installs these days are going to be straight from an Atapi cd drive, and loading the OS only occurs very rarely, but this hardware is fine for me, and both the ftp and DOS partition are supposedly supported install options - it would be nice if they still worked out of the box, and that issues like what I had happen are at least mentioned somewhere with a workaround. I mean, even just an explanation of how to edit the cdrom.inf and INDEX files to get the install to fly would be great. Or a copy of edited versions somewhere on the ftp with a little note "if you want to install all the cd packages from a DOS partition, do this!". On the other hand, pain of the install aside I couldn't be much happier with the OS now that it's up. -Ben Racine ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: network settings
Bachilo Dmitry wrote: > В сообщении от Понедельник 19 Сентябрь 2005 16:37 eoghan написал(a): > Here's mine /etc/rc.conf from work's router (shorted): > > defaultrouter="192.168.65.4" > gateway_enable="YES" > hostname="storage.solink.office" > ifconfig_rl0="inet 192.168.1.1 netmask 255.255.255.0" > ifconfig_rl1="inet 192.168.66.166 netmask 255.255.240.0" > inetd_enable="YES" > keymap="ru.koi8-r" > keyrate="fast" > linux_enable="YES" > mousechar_start="3" > moused_enable="YES" > saver="logo" > scrnmap="koi8-r2cp866" > sshd_enable="YES" > usbd_enable="YES" > > And here is mine from notebook: > > font8x14="cp866-8x14" > font8x16="cp866b-8x16" > font8x8="cp866-8x8" > hostname="notebook.bochasnet.academ.local" > ifconfig_rl0="DHCP" > keymap="ru.koi8-r" > keyrate="fast" > linux_enable="YES" > mousechar_start="3" > moused_enable="YES" > saver="logo" > scrnmap="koi8-r2cp866" > sshd_enable="YES" > usbd_enable="YES" > > > As you can see on the first one i heve static IP and default router specified, > and on the second i have dynamic parameters. Great! Thanks for the help. Will have a look once I get home. Eoghan ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ELF binary type "0" not known.
On Fri, Sep 16, 2005 at 11:56:09AM +, Wouter van Rooij wrote: > I have this error message when i'm wanting to start mozilla for example. Do > some of you know whats wrong and what I can do to get it working again? > > Wouter van Rooij Hey Wouter, you should have just asked me ;-) -Guido ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic in propagate_priority w/ postgresql under heavy load
Vinod Kashyap wrote: > You seem to be booting off of a 9000 (twa) controller and not 7000/8000 > (twe). > It could be because of a 9000 firmware bug that you are not being able > to > get the dump. The firmware wrongly interprets physical address 0x0 as > invalid > during dumps, and fails the operations. This bug will be fixed in > future > firmware releases. Ok, it's been a while, here is an update on this. I ran a heavily instrumented kernel for two weeks on the server, it did not crash in that time. I then took out the witness and kdb/ddb stuff, because the decreased performance was a bit of a nuisance, however i retained the ability to obtain a crash dump. I had to limit physical memory, put it on 1.8GB in loader.conf:hw.physmem because swap and physmem are both 2GB. Tested with 'reboot -d' gave me a core dump. Without the debug stuff in the kernel, it crashed within 2 days, same story: postgresql process, function propagate_priority. However, no dump was written to disk :( Furthermore, i've been seeing the same crash (in propagate_priority) on another box in mysql processes. Both servers seem to panic every 2-3 days. I have another server of the exact same hardware configuration, but it is mainly idling most of the time. Haven't seen that one crash yet. I am thinking now that it is a bug in the twa driver, so i'll have to dig in to that. Furthermore, it seems to have to do with some sort of concurrency issue or otherwise timing-sensitive issue, because slowing the kernel down with debug code seems to avoid the panic. But, as i am completely new to the freebsd kernel and don't even know what turnstiles are, i imagine i will have a hard time. So if anyone can offer some help, please :) Ok, thanks for your attention, Koen -- K.F.J. Martens, Sonologic, http://www.sonologic.nl/ Networking, hosting, embedded systems, unix, artificial intelligence. Public PGP key: http://www.metro.cx/pubkey-gmc.asc Wondering about the funny attachment your mail program can't read? Visit http://www.openpgp.org/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Adding new option to ktrace
Hi, I am able to backport kern_ktr.c and related files and ktrdump to versions older than 5.0 specially 4.1 with non-SMP configuration file kern_ktr.c file is compiled successfully. But with SMP configuration file it is giving an assembly errors as follows : cc -c -O -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../../BSD4.1/sys -I../../../include -I../../../../BSD4.1/include -DNILA -D_KERNEL -DNILA -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../kern/kern_ktr.c ../../kern/kern_ktr.c:290: warning: no previous prototype for `ktr_tracepoint' /tmp/ccW68912.s: Assembler messages: /tmp/ccW68912.s:218: Error: Rest of line ignored. First ignored character is `"'. /tmp/ccW68912.s:218: Error: Rest of line ignored. First ignored character is `"'. I am not getting this error ? what is this meant ? On 9/7/05, Robert Watson <[EMAIL PROTECTED]> wrote: > > On Wed, 7 Sep 2005, Nikhil Dharashivkar wrote: > > >I went through the ktr and ktrdump options. I compiled the kernel > > with options ktr. I found that ktr support is mostly for lock and > > schedule. We can trace drivers using mask KTR_DEV and some CTR* > > statements in dirver. > > But This ktr support is from freebsd 5. I am aslo using freebsd 4.10 > > and older. For this case, do I need to port KTR code for older version ? > > or is there any other solution ? > > KTR(9) was a facility added as part of the SMPng work to the 5.x branch, > and has not been backported to the 4.x branch at this point. It would not > be difficult to either backport it, or to add a light-weight trace ring > buffer of similar nature to fix, especially as 4.x doesn't have in-kernel > parellelism. > > Robert N M Watson > > > > > > > > On 9/6/05, Robert Watson <[EMAIL PROTECTED]> wrote: > >> On Tue, 6 Sep 2005, Nikhil Dharashivkar wrote: > >> > >>> Yes, it is ok if i loose data in ktrace queue when crash occurs. > >>> Basically, I want to give an Disk IO trace support to ktrace on FreeBSD. > >>> So, what I am thinking to use struct dio in dastrategy routine to > >>> trace the IO. I 'll use this struct to generate ktr_request. Throught > >>> ktr_writerequest it will be written in ktrace.out . > >>> Is it possible ? > >> > >> Try taking a look at KTR(9) and ktrdump(8) for information on ktr, the > >> in-kernel trace facility. ktrace(1) is almost entirely about tracing > >> process level system call behavior, and not structured for kernel event > >> tracing except in that context. I think you'll find KTR(9) is much more > >> what you're looking for, and among other things, you can extract the > >> results from both live kernels and kernel crash dumps. > >> > >> Robert N M Watson > >> > >> > >>> > >>> > >>> > >>> On 9/6/05, Peter Jeremy <[EMAIL PROTECTED]> wrote: > On Tue, 2005-Sep-06 10:33:53 +0530, Nikhil Dharashivkar wrote: > > Thanks for replying me. Basically what happend, while testing > > scsi driver on freebsd, at some point it crashes. So, there is no way > > to know how much IO is performed. To know the IO state just before the > > driver fails, i selected ktrace to print IO information whatever i ll > > get from dastrategy routine. > > It's not clear how ktrace is going to help here. The ktrXXX(9) > functions place ktr_request events in a queue. A kernel thread then > dumps the queue entries into a file via the normal buffer cache. The > data on disk is typically about 30 seconds behind real time. If the > system crashes, you will lose any events that are still in the buffer > cache or ktr_todo queue. > > Another problem is that since ktrace generates disk I/O, it is likely > to disturb your testing. > > A better approach would seem to be to build a circular buffer and > store the I/O requests in the buffer. When the system crashes, you > can look at the last entries in the buffer. > > -- > Peter Jeremy > > >>> > >>> > >>> -- > >>> Thanks and Regards, > >>> Nikhil. > >>> ___ > >>> freebsd-hackers@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > >>> To unsubscribe, send any mail to "[EMAIL PROTECTED]" > >>> > >> > > > > > > -- > > Thanks and Regards, > > Nikhil. > > > -- Thanks and Regards, Nikhil. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: syscons and SC_NO_CUTPASTE issue
- Original Message - From: "Simon 'corecode' Schubert" <[EMAIL PROTECTED]> To: "Mike Adewole" <[EMAIL PROTECTED]> Cc: Sent: Sunday, September 11, 2005 10:01 AM Subject: Re: syscons and SC_NO_CUTPASTE issue > On 08.09.2005, at 11:25, Mike Adewole wrote: > > I propose that: > > (d) the next release of the generic kernel should be compiled with > > SC_NO_CUTPASTE > why? I find cut+paste really useful per default. > besides, can't this be controlled with a sysctl? > cheers > > simon > the problem with the default setting is that it makes mouse support in a TUI environment nearly impossible without patching/recompiling the kernel. For instance, adding mouse support to sysinstall would be easier if cut and paste is delegated to the dialog utility (or other TUI environment) instead of being implemented directly by syscons. sysctl would be the perfect solution but I assumed it may be too big a change for some people. cheers Mike ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
(no subject)
___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
