Re: vinum troubles on 5.3
Hi, On Thu, Nov 11, 2004 at 10:44:10PM -0500, Brian Szymanski wrote: > After a long and happy time with vinum under 4.8 -> 4.10, I'm finding > things very broken in 5.3. The config I'm trying to accomplish is > relatively simple, just a root mirrored volume configuration which worked > under 4.x. A root mirrored configuration isn't that straightforward, imo :) But it should work. > Using vinum, I lose state information for the drive on ad2 after reboot - > M2 is shown in "vinum l" output only as "referenced"... That is to be expected, as you discovered below... > Browsing some mailing lists I found that gvinum is the way to go these > days, so I changed to using geom_vinum/gvinum, and the information is > retained across boot, but when I try to boot to the root volume, it says > that the drive is not UFS. When I boot on another partition to look at the > situation, I found that there were no entries in /dev for /dev/ad0s1a. I > wanted to create a ad0s1a entry with mknod, but of course we've got devfs > now, so that didn't work. I'm stumped and not sure how to proceed. Any > ideas? That's strange. What is the output of fdisk ad0 bsdlabel ad0s1 Maybe something in GEOM gets confused... If the disappearing device node problem is fixed, gvinum should work in this case. > I originally was trying a complex configuration like so: > drive A 200G > drive B 200G > drive C 100G > drive D 100G > > I set the concat of drive all of drives C+D to be a volume makeshift, and > added drive definition like so: > drive MS /dev/gvinum/makeshift > > Then, the idea was to do a raid5 of drives A, B, and "drive" MS. I don't know if this is even possible. It's an interesting idea but even if it works, recovery is totally non-trivial when either drive C or drive D goes away. Plus, you'll surely take a huge performance hit because of the two vinum layers you have to go through for every single access. RAID-5 is normally used when you need redundancy but can't afford to shell out the cash for mirroring. If you don't care about loss of data you are better off using stripe, if you are absolutely paranoid about your data you are better off mirroring [1]. If you do need RAID-5 though, you have to do it properly, which means evenly-sized disks. Do make sure they're not all from the same manufacturing batch also... > Unfortunately this caused a panic, which is less surprising. Does anyone > know of another way to accomplish the same thing (Raid5 over two disks and > 2 half sized disks concatenated together?) or a similar result? The best you can do is have 100G of drives A & B participate in a 4 x 100G RAID-5, then use the other 2 x 100G in a separate volume. You *could* theoretically concat 2 plexes in one volume, where one plex is RAID-5 and the other mirror or some such, but as said above, it's not easy to recover from a drive failure in that case, defeating the point of RAID imho. HTH, --Stijn [1] all my opinion; there are lots of opinions on what type of RAID is best in what situation. My point is mainly that you really need to consider what you are trying to accomplish by using RAID. -- "Linux has many different distributions, meaning that you can probably find one that is exactly what you want (I even found one that looked like a Unix system)." -- Mike Meyer, from a posting at [EMAIL PROTECTED] pgpwIegHTc3N4.pgp Description: PGP signature
Re: Freeze in 5.3 Release Install
I also had something similar on a hp machine (single proc) right after the [giant-lock] message.. I haven't look into it yet. On 11/12/04 5:18 AM, "Adrian Wontroba" <[EMAIL PROTECTED]> wrote: > On Thu, Nov 11, 2004 at 06:40:47PM -0500, Mark Jacobs wrote: >> Probe1-6 are listed after this, all with the same error 22 >> After the probe6 message the machine hangs. > > I had something similar - 5.3 probe time kernel freezes on a machine > which had been running 4.10 quite happily. > > Resolved it by setting "PNP OS" to YES in the BIOS. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Freeze in 5.3 Release Install
On Thu, Nov 11, 2004 at 06:40:47PM -0500, Mark Jacobs wrote: > Probe1-6 are listed after this, all with the same error 22 > After the probe6 message the machine hangs. I had something similar - 5.3 probe time kernel freezes on a machine which had been running 4.10 quite happily. Resolved it by setting "PNP OS" to YES in the BIOS. -- Adrian Wontroba ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
vinum troubles on 5.3
Howdy... After a long and happy time with vinum under 4.8 -> 4.10, I'm finding things very broken in 5.3. The config I'm trying to accomplish is relatively simple, just a root mirrored volume configuration which worked under 4.x. drive M1 device /dev/ad0s1e drive M2 device /dev/ad2s1e volume root plex org concat sd length 19600m drive M1 plex org concat sd length 19600m drive M2 Using vinum, I lose state information for the drive on ad2 after reboot - M2 is shown in "vinum l" output only as "referenced"... Browsing some mailing lists I found that gvinum is the way to go these days, so I changed to using geom_vinum/gvinum, and the information is retained across boot, but when I try to boot to the root volume, it says that the drive is not UFS. When I boot on another partition to look at the situation, I found that there were no entries in /dev for /dev/ad0s1a. I wanted to create a ad0s1a entry with mknod, but of course we've got devfs now, so that didn't work. I'm stumped and not sure how to proceed. Any ideas? I originally was trying a complex configuration like so: drive A 200G drive B 200G drive C 100G drive D 100G I set the concat of drive all of drives C+D to be a volume makeshift, and added drive definition like so: drive MS /dev/gvinum/makeshift Then, the idea was to do a raid5 of drives A, B, and "drive" MS. Unfortunately this caused a panic, which is less surprising. Does anyone know of another way to accomplish the same thing (Raid5 over two disks and 2 half sized disks concatenated together?) or a similar result? Any help would be most appreciated. Cheers, Brian Szymanski [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ULE Scheduler available in 5.3-RELEASE?
On Thursday, 11. November 2004 16:42, Ronald Klop wrote: > On Thu, 11 Nov 2004 09:29:08 -0600, Thomas T. Veldhouse <[EMAIL PROTECTED]> > > wrote: > > I just read in the release notes that 5.3-RELEASE has the new ULE > > scheduler available, but that 4BSD is the default scheduler. I thought > > I read messages in freebsd-current indicating that the option to use ULE > > was completely removed from the 5.3 or even the RELENG_5 branch? So, is > > ULE really available? > > Not in RELENG_5 and not in RELENG_5_3. There are issues with it. If it is > fixed it will come back. > > See this line in /usr/src/sys/kern/sched_ule.c: > #error "The SCHED_ULE scheduler is broken. Please use SCHED_4BSD" ... which of course you can just patch out. :) I'm still using ULE on my (UP) machine, works fine for me. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgp5FXsD7ht0V.pgp Description: PGP signature
Re: Freeze in 5.3 Release Install
I rebooted again tonight with verbose logging and the last messages on the console were; (probe0:sbp0:0:0:0): error 22 (probe0:sbp0:0:0:0): Unretryable Error Probe1-6 are listed after this, all with the same error 22 After the probe6 message the machine hangs. Mark Jacobs ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pccard modem and ethernet don't work together
In message: <[EMAIL PROTECTED]> Ronald Klop <[EMAIL PROTECTED]> writes: : On Wed, 10 Nov 2004 01:56:09 -0700 (MST), M. Warner Losh <[EMAIL PROTECTED]> : wrote: : : > In message: <[EMAIL PROTECTED]> : > Ronald Klop <[EMAIL PROTECTED]> writes: : > : I posted the same text as below to current@ on 20 Oct, but got no : > answer. : > : Is there somebody here who knows more about this or can tell me where : > to : > : look further? : > : I got a 'me too' message from somebody who googled my previous : > question, : > : so there are more people with this problem. : > : > I ment to reply, but got busy with the release. I'll see if I can : > recreate the problem. : > : > Warner : : Thanks in advance. : I am still looking around myself and am wondering if I need to run pccardd? : I thought it was replaced by devd, but it is still in the system. : Does pccardd have more functionality than devd and is it possible that it : can solve my problem? : Or am I looking in the wrong direction? pccardd won't help. The problem is almost certainly some kind of resource allocation issue that's casuing the cards to fail. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ULE Scheduler available in 5.3-RELEASE?
> Brooks Davis wrote: > >>On Thu, Nov 11, 2004 at 09:29:08AM -0600, Thomas T. Veldhouse wrote: >> >> >>>I just read in the release notes that 5.3-RELEASE has the new ULE >>>scheduler available, but that 4BSD is the default scheduler. I thought >>>I read messages in freebsd-current indicating that the option to use ULE >>>was completely removed from the 5.3 or even the RELENG_5 branch? So, is >>>ULE really available? >>> >>> >> >>ULE is not available in 5.3 or RELENG_5 due to problems that were >>unfixed at the time of the release. >> >>-- Brooks >> >> >> > Perhaps the release notes should be updated? > > Here is a quote > (http://www.freebsd.org/releases/5.3R/relnotes-i386.html#NEW): > > "The ULE scheduler has been added as an additional scheduler. Note that > the conventional one, which is called 4BSD, is still used as the default > scheduler in the GENERIC kernel. For the average user, interactivity is > reported to be better in many cases. This means less ``skipping'' and > ``jerking'' in interactive applications while the machine is very busy. > This will not prevent problems due to overloaded disk subsystems, but it > does help with overloaded CPUs. On SMP machines, ULE has per-CPU run > queues which allow for CPU affinity, CPU binding, and advanced > HyperThreading support, as well as providing a framework for more > optimizations in the future. As fine-grained kernel locking continues, > the scheduler will be able to make more efficient use of the available > parallel resources." > > Thanks in advance. > > -- > Thomas T. Veldhouse > Key Fingerprint: 07C7 BF05 4176 F50B A083 4542 0118 1315 761F D300 > Spammers please contact me at [EMAIL PROTECTED] > I beleive the errata document takes precedance over the release notes. In which case... (http://www.freebsd.org/releases/5.3R/errata.html#OPEN-ISSUES) "(1 Nov 2004) The ULE scheduler described in the release notes has been completely disabled to discourage its use because it has stability problems." -- Mark Magiera ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd 5.3 have any problem with vinum ?
Matthias Schuendehuette wrote: I'm not sure if this is a problem of (g)vinum or if FreeBSD has other problems in this area. just logged a kern bug on this And we all have to consider that gvinum is in a relatively early development phase (IMHO) - it is basically working, that is, it's possible to continue an existing 'classic' vinum installation with gvinum but it's still not fully functional in all depth. (minor deletes) I guess my issue is that there should be something in the release notes/updating that says "gvinum raid5 is not fully funtional at this time". I would argue that if can't survive a disk failure, it's not really RAID5. You might as well just go stripe and at least get the disk space back. If I hadn't sat down and tested this, I wouldn't have known it was broke till I had a drive failure which is not a good time to find out. I like (in general) where this is heading, but we seem to be inbetween relieable s/w raid5 solutions in FreeBSD. jim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd 5.3 have any problem with vinum ?
Hello, Am Mittwoch, 10. November 2004 22:31 schrieben Sie: > ok, your instructions worked like a charm. So i'm running my nice 4 > member SCSI gvinum raid5 array (with softupdates turned on), and it's > zipping along. Fine! :-) > Now I need to test just how robust this is. Ouhh... ;-) > camcontrol is too nice. I want to test a more real world failure. > I'm running dbench and just pull one of the drives. My expectation > is that I should see a minor pause, and then the array continue in > some slower, degraded mode. That was mine too... > What I get is a kernel trap 12 (boom!). > I reboot, and it will not mount the degraded set till I replace the > drive. > > I turned off softupdates, and had the same thing happen. Is this a > bogus test? Is it reasonable to expect that a scsi drive failure > should of been tolerated w/o crashing? No, of course not. I have more or less the same problems here. Once I came so far as to delete the crashed subdisk but when I tried to delete the (not existing anymore) vinumdrive, my kernel also crashed... Well, to be honest, I once tried to pull the plug on one of my disks with 'classic' vinum and I got a kernel panic as well. OK, this happened a few years ago and I never tried that again... I'm not sure if this is a problem of (g)vinum or if FreeBSD has other problems in this area. And we all have to consider that gvinum is in a relatively early development phase (IMHO) - it is basically working, that is, it's possible to continue an existing 'classic' vinum installation with gvinum but it's still not fully functional in all depth. But I think, there's all the potential to get there. I have the impression that Lukas is *very* interested in his baby and I have a good overall feeling so far. But he's the only one developing gvinum AFAIK... And - my primary interest is the LVM functionality of (g)vinum. IMHO if you *really* have valuable data to protect, you can afford a hardware RAID-controller (*and* a tape drive :-). Anything else is wrong economy. But the current disk layout possibilities with up to four slices and at max 28 BSD-partitions are far to inflexible for todays large disks. So from this point of view I'm already fairly happy with gvinum as it is today. Which doesn't mean that I'm not trying to help to get gvinum to the place and state where it deserves to be... :-) -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vnode_pager_putpages errors and DOS?
Igor Sysoev wrote: On Thu, 11 Nov 2004, Igor Sysoev wrote: I've attached an updated version of the patch for 'vnode_pager.c'. On my test system it resolved the issue. Please let us know whether it works for you as well. Sorry for the late response: I was ill and have no access to the test machine. I applied the patch to the clean 4.10. The result is the same: the process could not be killed, the file system access is very limited and the system became unresponsible. Sorry, I applied the patch, but forget to rebuild kernel :). It seems that patch resolves the problem - the program exits and the system is working. I run it several times. I would also run buildworld on this system to ensure that the program did not affect VM. make -j 32 buildworld ran without problems. Good to hear that it works for you, too. So, one long-standing bug less. However, the real challenge could turn out to be finding a committer for RELENG_4, now that everybody is working on RELENG_5 and above. I have a number of PRs in GNATS already that are slowly rotting away since apparently nobody is willing to deal with them, even though they all have patches attached. So I stopped submitting PRs for now. Wasted time, unfortunately. Uwe -- Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers [EMAIL PROTECTED] | http://www.escapebox.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vnode_pager_putpages errors and DOS?
On Thu, 11 Nov 2004, Igor Sysoev wrote: > > > I've attached an updated version of the patch for 'vnode_pager.c'. On > > > my test system it resolved the issue. Please let us know whether it > > > works for you as well. > > > > Sorry for the late response: I was ill and have no access to the test > > machine. > > I applied the patch to the clean 4.10. The result is the same: the process > > could not be killed, the file system access is very limited and the system > > became unresponsible. > > Sorry, I applied the patch, but forget to rebuild kernel :). > > It seems that patch resolves the problem - the program exits and the system > is working. I run it several times. I would also run buildworld on this > system to ensure that the program did not affect VM. make -j 32 buildworld ran without problems. Igor Sysoev http://sysoev.ru/en/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vnode_pager_putpages errors and DOS?
On Thu, 11 Nov 2004, Igor Sysoev wrote: > On Fri, 5 Nov 2004, Uwe Doering wrote: > > > Igor Sysoev wrote: > > > [...] > > > I've tried your patch from second email (it requires to include > > > for devsw and D_DISK): the system also became unresponsible. > > > > > > The main problem is that I could not kill the offending process - it > > > stuck in biowr state. > > > > In the meantime I've investigated this further. The two patches I > > provided so far certainly have their merits, since they deal with some > > unwanted side effects. However, I found that the root cause for the > > eventual system lock-up lies elsewhere. > > > > In an earlier email I already pointed out that function > > vnode_pager_generic_putpages() actually doesn't care whether the write > > operation failed or not. It always returns VM_PAGER_OK. > > > > Now, in case the write operation succeeds the file system code takes > > care that the formerly dirty pages associated with the i/o buffer get > > marked clean. On the other hand, if the write attempt fails, for > > instance in an out-of-disk-space situation, the pages are left dirty. > > At this point the syncer enters an infinite loop, trying to flush the > > same dirty pages to disk over and over again. > > > > The fix is actually quite simple. In case of a write error we have to > > make sure ourselves that the associated pages get marked clean. We do > > this by returning VM_PAGER_BAD instead of VM_PAGER_OK. These two result > > codes are functionally identical, with the exception that VM_PAGER_BAD > > additionally marks the respective page clean. For the details, please > > have a look at the caller function vm_pageout_flush() in 'vm_pageout.c'. > > > > What this modification means is that in case of a write error the > > affected pages remain intact in memory until they get recycled, but we > > lose their contents as far as the copy on disk is concerned. I believe > > this is acceptable (and possibly even originally intended) because > > giving up on syncing is about the best thing we can do in this > > situation, anyway. And it is certainly a much better choice than > > halting the whole system due to an infinite loop. > > > > I've attached an updated version of the patch for 'vnode_pager.c'. On > > my test system it resolved the issue. Please let us know whether it > > works for you as well. > > Sorry for the late response: I was ill and have no access to the test machine. > I applied the patch to the clean 4.10. The result is the same: the process > could not be killed, the file system access is very limited and the system > became unresponsible. Sorry, I applied the patch, but forget to rebuild kernel :). It seems that patch resolves the problem - the program exits and the system is working. I run it several times. I would also run buildworld on this system to ensure that the program did not affect VM. Igor Sysoev http://sysoev.ru/en/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Heimdal version in system is ancient!
On Wed, Nov 10, 2004 at 07:37:11PM -0800, Joe Kelsey wrote: > Why is the version of Heimdal in the base system 0.5.1? > > The port has 0.6.1 in /usr/ports/security/heimdal. > > How are we supposed to do any useful work when the system version of a > product is in direct conflict with a port version? If the system version is sufficient for your needs, use it. If you require the version in the ports, use that. There is no "direct conflict", they install to different locations. > How do I get the latest version of Heimdal into the system? Install the port and change your $PATH. The system version doesn't include everything that the port has so you'll likely want to do that anyway. -T -- One monk said to the other, "The fish has flopped out of the net! How will it live?" The other said, "When you have gotten out of the net, I'll tell you." ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vnode_pager_putpages errors and DOS?
On Fri, 5 Nov 2004, Uwe Doering wrote: > Igor Sysoev wrote: > > [...] > > I've tried your patch from second email (it requires to include > > for devsw and D_DISK): the system also became unresponsible. > > > > The main problem is that I could not kill the offending process - it > > stuck in biowr state. > > In the meantime I've investigated this further. The two patches I > provided so far certainly have their merits, since they deal with some > unwanted side effects. However, I found that the root cause for the > eventual system lock-up lies elsewhere. > > In an earlier email I already pointed out that function > vnode_pager_generic_putpages() actually doesn't care whether the write > operation failed or not. It always returns VM_PAGER_OK. > > Now, in case the write operation succeeds the file system code takes > care that the formerly dirty pages associated with the i/o buffer get > marked clean. On the other hand, if the write attempt fails, for > instance in an out-of-disk-space situation, the pages are left dirty. > At this point the syncer enters an infinite loop, trying to flush the > same dirty pages to disk over and over again. > > The fix is actually quite simple. In case of a write error we have to > make sure ourselves that the associated pages get marked clean. We do > this by returning VM_PAGER_BAD instead of VM_PAGER_OK. These two result > codes are functionally identical, with the exception that VM_PAGER_BAD > additionally marks the respective page clean. For the details, please > have a look at the caller function vm_pageout_flush() in 'vm_pageout.c'. > > What this modification means is that in case of a write error the > affected pages remain intact in memory until they get recycled, but we > lose their contents as far as the copy on disk is concerned. I believe > this is acceptable (and possibly even originally intended) because > giving up on syncing is about the best thing we can do in this > situation, anyway. And it is certainly a much better choice than > halting the whole system due to an infinite loop. > > I've attached an updated version of the patch for 'vnode_pager.c'. On > my test system it resolved the issue. Please let us know whether it > works for you as well. Sorry for the late response: I was ill and have no access to the test machine. I applied the patch to the clean 4.10. The result is the same: the process could not be killed, the file system access is very limited and the system became unresponsible. Igor Sysoev http://sysoev.ru/en/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Freeze in 5.3 Release Install
On Thursday 11 November 2004 10:17 am, Charles Ulrich wrote: > Mark Jacobs said: > > I downloaded the 5.3 release cd and successfully used it to install on my IBM > > T42 laptop. > > > > Today I attempted to upgrade the machine that was running 4.10 stable to 5.3 > > using the same cd. The install is hanging during the probe of devices right > > after it announces ACD1: DVDR at ata1-slave > > UDMA33. > > > > The attempted install failed twice at the same point. A hard reboot of the > > machine is required. > > If there is an empty IDE channel on your system, FreeBSD will hang for awhile > on it while it tries to probe a drive. Perhaps try waiting a little longer... > I waited for 5-10 minutes the first time. The second time I left it hanging when I went to bed. I will look at it when I get home from work. I bet its still hung. My configuration is ata0 master, hard drive. ata0-slave empty. ata 1-master is DVD CDROM. ATA1-Slave is described above. FreeBSD 4.10 stable does not have any problems with this configuration. -- Mark Jacobs Time Customer Service, Tampa FL Technical Services Time Warner - I die like a true rebel. Don't waste any time mourning---organize! My Will is easy to decide For there is nothing to divide My kin don't need to fuss and moan 'Moss does not cling to a rolling stone.' My body?--Oh!--If I could choose I would to ashes it reduce And let the merry breezes blow My dust to where some flowers grow. Perhaps some fading flower then Would come to life and bloom again. This is my last and final Will. Good luck to all of you. Joe Hill 1879 - 1914, American labour leader and songwriter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ULE Scheduler available in 5.3-RELEASE?
On Thu, 11 Nov 2004 09:29:08 -0600, Thomas T. Veldhouse <[EMAIL PROTECTED]> wrote: I just read in the release notes that 5.3-RELEASE has the new ULE scheduler available, but that 4BSD is the default scheduler. I thought I read messages in freebsd-current indicating that the option to use ULE was completely removed from the 5.3 or even the RELENG_5 branch? So, is ULE really available? Not in RELENG_5 and not in RELENG_5_3. There are issues with it. If it is fixed it will come back. See this line in /usr/src/sys/kern/sched_ule.c: #error "The SCHED_ULE scheduler is broken. Please use SCHED_4BSD" Ronald. -- Ronald Klop, Amsterdam, The Netherlands ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pccard modem and ethernet don't work together
On Wed, 10 Nov 2004 01:56:09 -0700 (MST), M. Warner Losh <[EMAIL PROTECTED]> wrote: In message: <[EMAIL PROTECTED]> Ronald Klop <[EMAIL PROTECTED]> writes: : I posted the same text as below to current@ on 20 Oct, but got no answer. : Is there somebody here who knows more about this or can tell me where to : look further? : I got a 'me too' message from somebody who googled my previous question, : so there are more people with this problem. I ment to reply, but got busy with the release. I'll see if I can recreate the problem. Warner Thanks in advance. I am still looking around myself and am wondering if I need to run pccardd? I thought it was replaced by devd, but it is still in the system. Does pccardd have more functionality than devd and is it possible that it can solve my problem? Or am I looking in the wrong direction? Ronald. -- Ronald Klop, Amsterdam, The Netherlands ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ULE Scheduler available in 5.3-RELEASE?
Brooks Davis wrote: On Thu, Nov 11, 2004 at 09:29:08AM -0600, Thomas T. Veldhouse wrote: I just read in the release notes that 5.3-RELEASE has the new ULE scheduler available, but that 4BSD is the default scheduler. I thought I read messages in freebsd-current indicating that the option to use ULE was completely removed from the 5.3 or even the RELENG_5 branch? So, is ULE really available? ULE is not available in 5.3 or RELENG_5 due to problems that were unfixed at the time of the release. -- Brooks Perhaps the release notes should be updated? Here is a quote (http://www.freebsd.org/releases/5.3R/relnotes-i386.html#NEW): "The ULE scheduler has been added as an additional scheduler. Note that the conventional one, which is called 4BSD, is still used as the default scheduler in the GENERIC kernel. For the average user, interactivity is reported to be better in many cases. This means less ``skipping'' and ``jerking'' in interactive applications while the machine is very busy. This will not prevent problems due to overloaded disk subsystems, but it does help with overloaded CPUs. On SMP machines, ULE has per-CPU run queues which allow for CPU affinity, CPU binding, and advanced HyperThreading support, as well as providing a framework for more optimizations in the future. As fine-grained kernel locking continues, the scheduler will be able to make more efficient use of the available parallel resources." Thanks in advance. -- Thomas T. Veldhouse Key Fingerprint: 07C7 BF05 4176 F50B A083 4542 0118 1315 761F D300 Spammers please contact me at [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
Re: ULE Scheduler available in 5.3-RELEASE?
On Thu, Nov 11, 2004 at 09:29:08AM -0600, Thomas T. Veldhouse wrote: > I just read in the release notes that 5.3-RELEASE has the new ULE > scheduler available, but that 4BSD is the default scheduler. I thought > I read messages in freebsd-current indicating that the option to use ULE > was completely removed from the 5.3 or even the RELENG_5 branch? So, is > ULE really available? ULE is not available in 5.3 or RELENG_5 due to problems that were unfixed at the time of the release. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpHDg42IWgeI.pgp Description: PGP signature
ULE Scheduler available in 5.3-RELEASE?
I just read in the release notes that 5.3-RELEASE has the new ULE scheduler available, but that 4BSD is the default scheduler. I thought I read messages in freebsd-current indicating that the option to use ULE was completely removed from the 5.3 or even the RELENG_5 branch? So, is ULE really available? -- Thomas T. Veldhouse Key Fingerprint: 07C7 BF05 4176 F50B A083 4542 0118 1315 761F D300 Spammers please contact me at [EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
Re: Freeze in 5.3 Release Install
Mark Jacobs said: > I downloaded the 5.3 release cd and successfully used it to install on my IBM > T42 laptop. > > Today I attempted to upgrade the machine that was running 4.10 stable to 5.3 > using the same cd. The install is hanging during the probe of devices right > after it announces ACD1: DVDR at ata1-slave > UDMA33. > > The attempted install failed twice at the same point. A hard reboot of the > machine is required. If there is an empty IDE channel on your system, FreeBSD will hang for awhile on it while it tries to probe a drive. Perhaps try waiting a little longer... -- Charles Ulrich Ideal Solution, LLC - http://www.idealso.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PC card problems on 5.3-R: "CIS is too long -- truncating""pccard0:Orinoco Gold, SMC 2532W-B
I am using a Toshiba Tecra 730XCDT, a 150MHz Pentium laptop. It has a ToPIC 95B Cardbus controller. The BIOS can place the controller into "PCIC-compatible" or "Cardbus/16-bit" modes. In Cardbus mode, my 3com 3c3FE575CT 100mbit card works fine. However my two wireless cards, an Orinoco Gold and an SMC 2532W-B, give the following message upon insertion: CIS is too long -- truncating pccard0: card has no functions cbb0: PC Card card activation failed "pccardc dumpcis" says "0 slots found" In PCIC-compatible mode, FreeBSD does not recognize the card controller. The wi cards work OK under PCIC mode in NetBSD 1.6.2. The 3com card does not. NetBSD does not seem to work with them in cardbus mode. Thanks in advance for any help Joe Koberg joe at osoft dot us ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.3 - named 0.00% CPU usage
I believe this has to do with named being a threaded process (try hitting the capital 'H' in top and you will see more then one named). You could search ther archives on freebsd-current for the discussion, but it has to do with no way show it properly so it was turned off for now. Non thread process will show fine. Ken - Original Message - From: "Michael Riexinger" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 11, 2004 9:48 AM Subject: FreeBSD 5.3 - named 0.00% CPU usage Hi, on 2 different machines (same hardware) with FreeBSD 5.3-RELEASE, named is reporting 0.00% cpu usage in top. But on the cpu states, there is always activity and named is the only process that consumes much cpu time. Other processes show cpu usage well in top. Is that a common/known problem? Kind regards, Michael Riexinger systems engineer -- claranet gmbh internet service provider tel +49 (0) 69 - 40 80 18 - 300 email: [EMAIL PROTECTED] http://www.claranet.de/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 5.3 - named 0.00% CPU usage
Hi, on 2 different machines (same hardware) with FreeBSD 5.3-RELEASE, named is reporting 0.00% cpu usage in top. But on the cpu states, there is always activity and named is the only process that consumes much cpu time. Other processes show cpu usage well in top. Is that a common/known problem? Kind regards, Michael Riexinger systems engineer -- claranet gmbh internet service provider tel +49 (0) 69 - 40 80 18 - 300 email: [EMAIL PROTECTED] http://www.claranet.de/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3 mdmfs or mdconfig problem
This host has 192 MB of RAM and 512 MB of swap.
/sbin/mdmfs -i 4096 -s $1md $2 (*)
>>> You don't have enough RAM in your system to do that.
>> I'm running mdmfs WITHOUT "-M" flag.
Ronald Klop wrote:
> Maybe I'm missing something, but tmpmfs works malloc-based by default:
> /etc/rc.d/initdiskless: mount_md() { /sbin/mdmfs -i 4096 -s $1 -M md $2 }
I removed "-M" from the mount_md() function definition
in /etc/rc.d/initdiskless file, please see [*].
When I run "mdmfs -i 4096 -s 1m md /mnt" command, mdmfs runs
"mdconfig -a -t swap -s 1m", but the /mnt is still malloc-backed:
FreeBSD i386 5.3-STABLE Nov 11 07:00:00 UTC 2004
panic: kmem_malloc(4096): kmem_map too small: 63737856 total allocated
pgpz3zjrEDllP.pgp
Description: PGP signature
Re: perl 5.8.5 on freebsd 4.10
Thanks for the reply Robert! cd /usr/ports/lang/perl5.8 make install clean Sorry, I should have said I was using ports. I cvsuped the ports yesterday. But did you run: "make test"? This runs the tests, you would need to do this before the "make clean" With perl which includes excellent self tests I always check these. Failed 1 test script out of 826, 99.88% okay. ### Since not all tests were successful, you may want to run some of And of course that was the crypto test I refered to (I pasted it again below) that failed. What I expected was (Like I get on 4.9 and 5.3 using make test in /usr/lang/ports/perl5.8): t/pod/special_seqsok t/x2p/s2p.ok All tests successful. u=5.85156 s=1.98438 cu=368.914 cs=38.2969 scripts=826 tests=85559 Looks like a bug in 4.10, but I am not expert especially on crypto! I just wanted to check this with the group as it may point to a larger problem that this behaves differently on 4.10 from 4.9 and 5.3. Thanks, Ken error output repasted. t/op/context..ok t/op/cproto...ok t/op/crypt# Failed at op/crypt.t line 45 # got '$2a$04$cXSIoNruOcY4zQvBHgLd4OwIn/hpnHpszYR0VrbT0MGHtj8UgV4jS' # expected '$2a$04$cQSEYKwMGkhlyuPmbY2YY.5Fo0iMDAVDOlSr8SElFfCwc8SPUJW7.' FAILED at test 4 t/op/defins...ok ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Pam Authorization Problem
On Wednesday 10 November 2004 20:13, Christian Meutes wrote: > I recognized a strange behavior of PAM. My Plan was to do Authorization > through pam_unix.so and pam_ldap.so > I have the following configuration for this: > --- > account requiredpam_login_access.so > account sufficient/usr/local/lib/pam_ldap.so > account requiredpam_unix.so > --- > > when the user neither exist in ldap nor in /etc/passwd then the > auhtorization is nevertheless successful... this behavior isnt what i huh? as in a user that more or less does *not* exist on your system can log in? do you have any other authentication modules that the system falls to? > expected. > > i want to do authorization through pam_ldap.so and pam_unix.so > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: perl 5.8.5 on freebsd 4.10
Ken Menzel wrote: I need perl 5.8 to use xerces xml parser (xml.apache.org) on Freebsd5.3 perl5.8 the t/op/crypt test passes fine but not on 4.10 is this OK or normal? Any ideas or comments? t/op/cproto...ok t/op/crypt# Failed at op/crypt.t line 45 # got '$2a$04$cXSIoNruOcY4zQvBHgLd4OwIn/hpnHpszYR0VrbT0MGHtj8UgV4jS' # expected '$2a$04$cQSEYKwMGkhlyuPmbY2YY.5Fo0iMDAVDOlSr8SElFfCwc8SPUJW7.' FAILED at test 4 t/op/defins...ok freebsd4# uname -a FreeBSD freebsd4.icarz.com 4.10-RELEASE-p2 FreeBSD 4.10-RELEASE-p2 #15: Mon Aug 2 16:14:59 EDT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ICARZ i386 cd /usr/ports/lang/perl5.8 make install clean or portupgrade perl5* Both of those work fine for me. -- Robert Blayzor, BOFH INOC, LLC rblayzor\@(inoc.net|gmail.com) PGP: http://www.inoc.net/~dev/ Key fingerprint = 1E02 DABE F989 BC03 3DF5 0E93 8D02 9D0B CB1A A7B0 My Other machine is your Linux Box ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
panic after "kldunload fdc"
Hi, I'm running FreeBSD 5.3-STABLE #0: Tue Nov 9 04:08:35 CET 2004 root@:/usr/obj/usr/src/sys/RENE which was cvsupped at Monday, 16:00 UTC and got this panic after doing # kldload fdc # kldload msdosfs_iconv # kldunload msdosfs_iconv # kldunload fdc (all handwritten) : kernel trap 12: page fault while in kernel mode fault virtual address = 0xdeadc0de fault code = supervisor read, page not present ip = 0x8:0xc04fc8a8 sp = 0x10:0xca4aeafc fp = 0x10:0xca4aeafc cs = base 0x0, limit 0x, 0x1b, DPL 0, pres 1, def32 1, gran 1 eflags = interrupt enabled, resume, iopl = 0 curproc = 22038 (fdc1) @ 322645184 = strlen+8: cmpb $0, 0(%edx) trace strlen+8 (3735929054, 3393907688, 0, 3237834112, 3393907504) kvprintf+1657 (3227482785, 3226128960, 3393907688, 10, 3393907760) vsnprintf+60 (3227795008, 256, 3227482785, 3393907756, 256) panic+97 (3227482785, 3735929054, 3227487812, 239, 0) _mtx_lock_flags+105 (3256915884, 0, 3227487812, 239 ,0) msleep+1266 (3256915772, 3256915884, 76, 3252604499, 1000) _end @ 3252596686 (3256915712, 3227482736, 3252594400, 3242784056, 3393908020) _end @ 3252594424 (3256915712, 3393908040, 3227475519, 803, 3239611520) fork_exit+198 (3252594400, 3256915712, 3393908040) fork_trampoline+8 () eip = 0 esp = 3393908092 ebp = 0 acpi is disabled, fdc1 instead of fdc0 was attached (which makes no sense as I only have one floppy drive, but fdc0 returned "cannot allocate io port", probably because acpi is off) I have a debug kernel, but no crashdump, panic at DDB gives panic: from debugger Uptime: but hangs hard after that point I have this config: --- kernel config --- ident RENE makeoptions DEBUG=-g machine i386 cpu I686_CPU options CPU_FASTER_5X86_FPU options CLK_USE_I8254_CALIBRATION # dmesg says we have this chip device apic options SCHED_4BSD options KDB options KDB_TRACE options DDB options DDB_NUMSYM #optionsGDB # remote GDB support options WITNESS options WITNESS_SKIPSPIN options WITNESS_KDB options INVARIANTS options INVARIANT_SUPPORT options PREEMPTION options ADAPTIVE_GIANT options INET#InterNETworking, mandatory options INET6 #IPv6 communications protocols #optionsIPSEC #optionsIPSEC_ESP options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options KTRACE options PQ_CACHESIZE=32 #32kB L2 Cache options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions device isa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd options KBD_INSTALL_CDEV device psm # PS/2 mouse # syscons is the default console driver, resembling an SCO console device sc options SC_TWOBUTTON_MOUSE device vga # VGA video card driver options FB_INSTALL_CDEV device npx # Floating point support - do not disable. options DEVICE_POLLING # improve fxp0 performance options HZ=1000 # for DEVICE_POLLING, interrrupt rate device loop# Network loopback device ether # Ethernet support device pty # Pseudo-ttys (telnet,xterm etc) device bpf # needed for DHCP options XBONEHACK # same address pairs over multiple gif intf options PPP_BSDCOMP options PPP_DEFLATE options PPP_FILTER device splash #screensaver/splash screen device pmtimer --- /etc/rc.conf --- apm_enable="NO" hostname="82-168-140-74-bbxl.xdsl.tiscali.nl" ifconfig_fxp0="DHCP" linux_enable="YES" moused_enable="YES" moused_flags="" moused_type="auto" #saver="blank" # njl broke my acpi at 2004-11-08 ? dumpdev="/dev/ad0s1b" #devel/fam rpcbind_enable="YES" inetd_enable="YES" --- /boot/loader.conf --- mem_load="YES" io_load="YES" random_load="YES" #intpm_load="YES" speaker_load="YES" snd_cs4281_load="YES" #cd9660_iconv_load="YES" #fdc_load="YES" #msdosfs_iconv_load="YES" if_fxp_load="YES" vesa_load="YES" debug.mpsafevm=1 pgpBSDRkTASpN.pgp Description: PGP signature
Re: pw and adduser different checks ?
At 08.54 11/11/2004, Phil Kernick wrote: >> /usr/sbin/pw useradd -ntest [EMAIL PROTECTED] -d/home/test -g1000 -s/bin/sh >> -u1000 >> pw: invalid character `@' at position 4 in gecos field >> >> Who is right of both the program ? :-) >> >> IMHO I find usefull to have the @ in the gecos field because it is an easy >> way to associate login <-> email in multidomain enviroment. >> But probably there is some drawback I am not aware of ... >> Any explanation ? > >The problem is pw being unreasonably restrictive. > >In the same way, you can't use pw to add a user with a $ in their name, >which is necessary for samba. If having such chars is not an hazard or a risk why some committer don't modify pw to let it to use them ? Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://utenti.gufi.org/~gmarco/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
