(no subject)
Newsgroups: mailing.freebsd.stable Subject: Re: FreeBSD 7.0 WITHOUT Heimdal References: [EMAIL PROTECTED] From: [EMAIL PROTECTED] (J. Porter Clark) Organization: http://www.angelfire.com/ego/porterclark/ X-No-Archive: Yes [EMAIL PROTECTED] (Marcin Cieslak) writes: J. Porter Clark wrote: gnome-vfs won't compile with WITHOUT_KERBEROS=yes for some reason or other. Ugh. Another reason to have permanent WITHOUT_GNOMEVFS=yes in /etc/make.conf ;-) That worked well on one system I have, and I appreciate the tip. However, another one has gcdmaster, which depends on libgnomeuimm, which depends on gnomevfsmm... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 WITHOUT Heimdal
[EMAIL PROTECTED] (Dimitry Andric) writes: On 2008-04-10 13:24, Gunnar Flygt wrote: In earlier version of FreeBSD I've been able to NOT include the heimdal delivered with the system, by providing the flag NO_KERBEROS=yes in /etc/make.conf In 7.0 there is no detection of such a flag. All the NO_XXX flags have been obsoleted, use WITHOUT_KERBEROS=yes instead. See src.conf(5) for more information. gnome-vfs won't compile with WITHOUT_KERBEROS=yes for some reason or other. Ugh. -- J. Porter Clark [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.1-STABLE panic using revoked pty
on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: Enhanced floppy controller at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources (port) speaker0: PC speaker at port 0x61 on isa0 unknown: PNP0f13 can't assign resources (irq) unknown: PNP0501 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0401 can't assign resources (port) unknown: PNP0700 can't assign resources (port) Timecounters tick every 1.000 msec acd0: DVDR PIONEER DVD-RW DVR-108/1.10 at ata0-master UDMA66 Waiting 5 seconds for SCSI devices to settle firewire0: New S400 device ID:0010b920007ad726 sa0 at ahd1 bus 0 target 5 lun 0 sa0: SONY SDT-11000 0200 Removable Sequential Access SCSI-2 device sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da0 at ahd0 bus 0 target 0 lun 0 da0: FUJITSU MAP3367NP 0108 Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 35046MB (71775284 512 byte sectors: 255H 63S/T 4467C) da1 at ahd0 bus 0 target 1 lun 0 da1: FUJITSU MAP3367NP 0108 Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled da1: 35046MB (71775284 512 byte sectors: 255H 63S/T 4467C) da2 at sbp0 bus 0 target 0 lun 0 da2: Maxtor OneTouch Fixed Direct Access SCSI-4 device da2: 50.000MB/s transfers da2: 286103MB (585938944 512 byte sectors: 255H 63S/T 36473C) cd0 at ata0 bus 0 target 0 lun 0 cd0: PIONEER DVD-RW DVR-108 1.10 Removable CD-ROM SCSI-0 device cd0: 66.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! Trying to mount root from ufs:/dev/da0s1a WARNING: / was not properly dismounted -- J. Porter Clark [EMAIL PROTECTED] NASA/MSFC Flight Ground Computers Branch (EI31) Phone (256)544-3661 Fax (256)544-6193 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Quality of FreeBSD
On Tue, Jul 26, 2005 at 02:30:49PM +0100, Joao Barros wrote: I dual boot between XP and FreeBSD and even use VMWare to boot FreeBSD with the real partition. Nice having FreeBSD compiling something in the background while using XP :) That's pretty cool... That is a keyboard problem (the pointer device in the keyboard) I had one exchanged on this C840 and 2 others on a C610. I'll pass that on to the maintenance guy. This is an outsourced (i.e., rented) machine. (They'd be appalled to know that it runs any non-Microsoft software. Don't nobody tell!!!) I *think* I tested networking and attached storage with firewire. If you care to email me with your problems I can try see if it happens to me too. Because the hard drive is only 20 GB, I have an external drive connected to the IEEE 1394 port. (The USB ports on this laptop are unacceptably pokey.) Most of the problems are probably related to my attempts at hot-plugging (so to speak) this interface. The first time I connect the drive up to the box, I get this sort of thing: firewire0: New S400 device ID:0090a9506600 da0 at sbp0 bus 0 target 0 lun 0 kernel: da0: WDC FireWire/USB2.0 0417 Fixed Simplified Direct Access SCSI-4 device kernel: da0: 50.000MB/s transfers kernel: da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) fwohci0: BUS reset fwohci0: node_id=0xc000ffc0, gen=2, CYCLEMASTER mode kernel: firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me) kernel: firewire0: bus manager 0 (me) I can then mount a partition from the drive: mount /dev/da0s2d ~/ext_bsd Sometimes I have a problem--and I can't duplicate it right now--in that if I umount the drive, then remove the plug, then reinsert it, I can't remount it immediately. Attempting to mount the drive will block for a few minutes. If I wait several minutes, it will remount immediately, or I can speed that up by removing and reinserting the plug a second time, which is what I usually do. The main problem I have is possibly related to an intermittent connection...which has been aggravated by the many insertions and reinsertions. Sometimes, out of the blue, I'll get an error like this: kernel: Interrupt storm detected on irq11: nvidia0 cbb*; throttling interrupt source kernel: fwohci0: BUS reset It's usually precipitated by my moving the laptop off my lap onto a table or otherwise wiggling the cable, which seems to be unpredictably sensitive. (It never happens if there is no I/O going on at the time.) I have no idea why it mentions the nvidia0 device. When this happens, any I/O on the Firewire drive will hang indefinitely. I can't fix it at that point; about all I can do is reboot. fwcontrol -r doesn't help any. If I reboot the system, I always have problems syncing it; it complains about unwritten buffers or vnodes, and eventually I have to manually reset it. When I come back up, I have fsck problems not only with the Firewire partitions but also /usr and others. You can say that I created the problem myself by manhandling the little plug or by even trying to insert it and remove it hot. (Nobody said I could, nobody said I couldn't.) But I can do this with Windows XP with no problems. I also don't have any problems caused by wiggling the apparently very sensitive cable with XP. I also didn't have the wiggling-cable problem under 4.X, although it's possible that mechanical degradation since that time is at fault. (The hanging mount problem did occur under 4.X.) I haven't posted this as a bug report because (a) I haven't had much luck with bug reports sniff and (b) I'm sure the answer would be fix your hardware. -- J. Porter Clark [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Quality of FreeBSD
The VIA SATA onboard controller on my server works (and has worked) flawlessly. I have two identical 80G Maxtor SATA drives connected to it and have had absolutely no problems and excellent performance. Even my Dell Inspirion 5100--with a few hiccups--has made great progress and is mostly functional. The ATA (definitely not SATA) controller on my Dell Latitude C840 laptop has READ_DMA, WRITE_DMA problems, maybe 2-3 times a day unless I turn off DMA. It hangs for 3-4 seconds, logs errors, then proceeds. It isn't heavily loaded. I tried using Soren's ATA mkIII patches, and now it likes to panic about that same frequency instead of hanging, so I'm going back to the stock RELENG_5 config next chance I get. It's one of these: atapci0: Intel ICH3 UDMA100 controller port 0xbfa0-0xbfaf,0x376,0x170-0x177,0x 3f6,0x1f0-0x1f7 at device 31.1 on pci0 -- J. Porter Clark [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Quality of FreeBSD
On 7/25/05, J. Porter Clark [EMAIL PROTECTED] wrote: The ATA (definitely not SATA) controller on my Dell Latitude C840 laptop has READ_DMA, WRITE_DMA problems, maybe 2-3 times a day unless I turn off DMA. It hangs for 3-4 seconds, logs errors, then proceeds. It isn't heavily loaded. I tried using Soren's ATA mkIII patches, and now it likes to panic about that same frequency instead of hanging, so I'm going back to the stock RELENG_5 config next chance I get. It's one of these: atapci0: Intel ICH3 UDMA100 controller port 0xbfa0-0xbfaf,0x376,0x170-0x177,0x 3f6,0x1f0-0x1f7 at device 31.1 on pci0 Your going back to stock RELENG_5 from what? RELENG_5 with Soren's patches. I have that very same laptop running FreeBSD from 5.0 up to 5.4 with absolutely no DMA problems using it. Note: I did exchange the HDD from 20 to 60GB, different brands. Might be a clue. My laptop has this: ad0: 19077MB IC25N020ATCS04 0 CA2OA72A at ata0-master UDMA100 Typical errors: Jul 23 15:00:33 auricle kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=20586350 Jul 25 09:01:52 auricle kernel: ad0: TIMEOUT - READ_MUL retrying (2 retries left) LBA=1731115 I had been running 4.X on this box with no DMA problems until I put 5.3 on it many months ago. It also boots Windows XP, and I don't have any obvious disk problems with that. Do you have trouble with the touchpad occasionally going nuts? I had mine replaced, and it still does it. With any OS I care to boot. I have some Firewire-related problems, too, but I won't go into them right now. -- J. Porter Clark [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
