Re: Boot loader cant identify ntfs?
Phil Kernick wrote: > .byte os_bsd-. # BSD/OS That one could be dumped aswell, couldn't it? mkb. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Diskless boot problem
On 5/20/05, Doug White <[EMAIL PROTECTED]> wrote: > Please try to avoid sending your message bodies base64 encoded :) My mail > client got really confused by it and didn't quote the message properly. > > Also stripping hackers cc:. I'd like to, but Gmail doesn't offer this option. Sorry :( > On Thu, 19 May 2005, [ISO-8859-2] S³awek ¯ak wrote: > > > Hi, > > > I have a problem with booting Dell 2850 over network. The machine reads > > kernel over net, boots upto mounting / from NFS and then crashes. > > What is the NFS server? It seems to think the NFS handle we pulled the > kernel with is no longer valid. FreeBSD 5.3/5.4-STABLE. > Does PXE and the system itself end up pulling different IP addresses? No. The IP is the same. /S -- Sławek Żak / UNIX Systems Administrator ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Finally a Patch that works!
I did not know that this feature of FreeBSD-stable needed patched. It seems to be working fine for me. No bugs or crabs. Thanks for the info. I will be sure to patch my penis as soon as possible. On Friday 20 May 2005 2:13 pm, Israel wrote: > Penis Growth Patches are here! > http://www.legahe.com/ss/ > New Penis Enlargement Patches! > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Jaimie Garner Onsite PCS inc. 323 SE RIverside AV Grants Pass, OR 97526 541.471.1343 866.471.1343 [EMAIL PROTECTED] www.onistepcs.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Finally a Patch that works!
Jaimie Garner wrote: > I did not know that this feature of FreeBSD-stable needed patched. It seems > to [...] Godsdammit! Do you have to answer to spam that otherwise is filtered out by a typical spamfilter? I haven't seen this until I read your reply. mkb. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Finally a Patch that works!
Sorry I couldn't resist. Is there a way to report the spam or can some add it to a black list on the mailing list? I would volunteer for the job of moderating spam and removing it if it is possible. On Saturday 21 May 2005 5:59 am, Matthias Buelow wrote: > Jaimie Garner wrote: > > I did not know that this feature of FreeBSD-stable needed patched. It > > seems to > > [...] > > Godsdammit! Do you have to answer to spam that otherwise is filtered out > by a typical spamfilter? I haven't seen this until I read your reply. > > mkb. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Jaimie Garner Onsite PCS inc. 323 SE RIverside AV Grants Pass, OR 97526 541.471.1343 866.471.1343 [EMAIL PROTECTED] www.onistepcs.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sysinstall on boot.flp enters boot loop with md device
Hello, Trying to install 5.4 on a box that had previously run 5.3 just fine and before that 5.2. I wanted to do a fresh install vs. an upgrade and unfortunately this box can not boot from CD, the install is also headless. I created the floppies, then mounted boot.flp and put a boot.config file on it with "-h" contained within. I then booted the install, got through the point where i had to reinsert the boot.flp disk, after the two kern*.flp disks, and the system went in to a loop. Here's the repeating error: spec_getpages:(md0) I/O read failure: (error=5) bp 0xc94fb9ec vp 0xc1d42d68 size: 36864, resid: 36864, a_count: 36864, valid: 0x0 nread: 0, reqpage: 0, pindex: 459, pcount: 9 vm_fault: pager read error, pid 1 (sysinstall) At first i thought it was a media issue or a download issue, but i've verified the md5 signature of the image, which came off a 5.4-RELEASE cd-rom, and have recreated four boot.flp floppies with the same result. My dmesg is below. Any input welcome. Thanks. Dave. dmesg: Uncompressing ... done Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS 638kB/392192kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Sun May 8 05:59:07 UTC 2005) Loading /boot/defaults/loader.conf /kernel text=0x444168 \ Insert disk labelled "Kernel floppy 1" and press any key... | Insert disk labelled "Kernel floppy 2" and press any key... data=0x7d5c8+0x4fc78 syms=[0x4+0x5b390+0x4+0x706c9] Insert boot floppy and press Enter /acpi.ko text=0x414fc data=0x1dc4+0x112c syms=[0x4+0x7670+0x4+0x9d05] zf_read: fill error Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (397.33-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 402653184 (384 MB) avail memory = 380243968 (362 MB) ACPI-0159: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES ACPI: table load failed: AE_NO_ACPI_TABLES npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xfcd0-0xfcdf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0xfce0-0xfcff irq 11 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 4.3 (no driver attached) ed0: port 0xf8e0-0xf8ff irq 3 at device 13.0 on pci0 ed0: Ethernet address: 00:20:78:1a:5d:ab ed0: if_start running deferred for Giant ed0: type NE2000 (16 bit) rl0: port 0xf400-0xf4ff mem 0xfedffc00-0xfedffcff irq 10 at device 14.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:e0:7d:d9:a1:58 orm0: at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) uhid0: American Power Conversion Back-UPS RS 1500 FW:8.g8 .D USB FW:g8, rev 1.10/1.06, addr 2, iclass 3/0 Timecounter "TSC" frequency 397331331 Hz quality 800 Timecounters tick every 10.000 msec md0: Preloaded image 3719168 bytes at 0xc0a34270 ad0: 4104MB [8895/15/63] at ata0-master UDMA33 ad2: 4028MB [8184/16/63] at ata1-master UDMA33 Mounting root from ufs:/dev/md0 spec_getpages:(md0) I/O read failure: (error=5) bp 0xc94fb9ec vp 0xc1d42d68 size: 36864, resid: 36864, a_count: 36864, valid: 0x0 nread: 0, reqpage: 0, pindex:
EHCI device
I have a motherboard here that reports USB controllers thusly in dmesg (5.4-stable): usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0xf7002000-0xf7002fff irq 5 at device 3.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ohci2: mem 0xf7003000-0xf7003fff irq 12 at device 3.2 on pci0 usb2: OHCI version 1.0, legacy support usb2: on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xf7004000-0xf7004fff irq 11 at device 3.3 on pci0 usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: SiS EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered When I plug my digital camera in, I get this report: umass0: HEWLETT-PACKARD HP PhotoSmart R607, rev 2.00/0.01, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 24MB (50305 512 byte sectors: 64H 32S/T 24C) Looking at the transfer speed, it only registers as USB 1 device, right? On Windows XP (on different machine) it's recognized as USB 2 compliant, but I can't really say if it actually works faster. Can it be made to work as USB2 on FreeBSD? [Insert the usual complaint about not being able to umount detached USB devices here :( ] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.4RELEASE: problem with my ST34311A UDMA666 controller
Hello, On one of my computers, the 5.4 RELEASE bootonly disc don't want to write on my hdd. The same hdd is ok whith other computer. I have the same log whith 2 another hdd : atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ... ad0: 4104MB [8895/15/63] at ata0-master UDMA66 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63 ad0: FAILURE - READ_DMA status=51 error=48 LBA=63 It's my first attempt to install freebsd on this computer. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RELENG_5 panic
# uname -a
FreeBSD robinpb.homeip.net 5.4-STABLE FreeBSD 5.4-STABLE #0: Tue May 17
00:30:47 EDT 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/fastipsec i386
# kgdb kernel.debug /usr/local/var/adm/crash/vmcore.44
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
#0 doadump () at pcpu.h:160
160 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) bt full
#0 doadump () at pcpu.h:160
No locals.
#1 0xc04dd58c in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410
first_buf_printf = 1
#2 0xc04ddccd in panic (fmt=0xc066e594 "%s") at
/usr/src/sys/kern/kern_shutdown.c:566
bootopt = 260
newpanic = 0
buf = "page fault", '\0'
#3 0xc0641e92 in trap_fatal (frame=0xc7ac0bc8, eva=36) at
/usr/src/sys/i386/i386/trap.c:817
code = 16
type = 12
ss = 16
esp = 0
softseg = {ssd_base = 0, ssd_limit = 1048575, ssd_type = 27, ssd_dpl
= 0, ssd_p = 1,
ssd_xx = 0, ssd_xx1 = 0, ssd_def32 = 1, ssd_gran = 1}
#4 0xc0642535 in trap (frame=
{tf_fs = 24, tf_es = -1066598384, tf_ds = -1066532848, tf_edi =
-1053916800, tf_esi = -1049515008, tf_ebp = -945025988, tf_isp = -945026060,
tf_ebx = -1053916800, tf_edx = -1053937024, tf_ecx = 56, tf_eax = 0,
tf_trapno = 12, tf_err = 0, tf_eip = -1068480504, tf_cs = 8, tf_eflags =
65683, tf_esp = -1053914880, tf_ss = 582}) at
/usr/src/sys/i386/i386/trap.c:255
p = (struct proc *) 0xc12e754c
sticks = 3241036032
i = 0
ucode = 0
type = 12
code = 0
eva = 36
#5 0xc062da3a in calltrap () at /usr/src/sys/i386/i386/exception.s:140
No locals.
#6 0x0018 in ?? ()
No symbol table info available.
#7 0xc06d0010 in ipq ()
No symbol table info available.
#8 0xc06e0010 in sc_buffer.3 ()
No symbol table info available.
#9 0xc12e8180 in ?? ()
No symbol table info available.
#10 0xc171ac00 in ?? ()
No symbol table info available.
#11 0xc7ac0c3c in ?? ()
No symbol table info available.
#12 0xc7ac0bf4 in ?? ()
No symbol table info available.
#13 0xc12e8180 in ?? ()
No symbol table info available.
#14 0xc12e3280 in ?? ()
No symbol table info available.
#15 0x0038 in ?? ()
No symbol table info available.
#16 0x in ?? ()
No symbol table info available.
#17 0x000c in ?? ()
No symbol table info available.
#18 0x in ?? ()
No symbol table info available.
#19 0xc0504808 in turnstile_wait (ts=0xc12e3280, lock=0xc06d022c,
owner=0xc171ac00)
at /usr/src/sys/kern/subr_turnstile.c:243
tc = (struct turnstile_chain *) 0xc06cb770
td1 = (struct thread *) 0xc12e8180
#20 0xc04d2b7f in _mtx_lock_sleep (m=0xc06d022c, td=0xc12e8180, opts=0,
file=0x0, line=0)
at /usr/src/sys/kern/kern_mutex.c:552
ts = (struct turnstile *) 0x0
owner = (struct thread *) 0xc171ac00
v = 0
#21 0xc058a592 in tcp_isn_tick (xtp=0x0) at
/usr/src/sys/netinet/tcp_subr.c:1380
projected_offset = 0
#22 0xc04ed069 in softclock (dummy=0x0) at
/usr/src/sys/kern/kern_timeout.c:279
c_func = (void (*)(void *)) 0xc058a4d0
c_arg = (void *) 0x0
c_flags = 14
c = (struct callout *) 0x0
bucket = (struct callout_tailq *) 0xc39ba4a8
steps = 14
depth = 2
mpcalls = 2
gcalls = 0
wakeup_cookie = 14
#23 0xc04c460a in ithread_loop (arg=0xc12fd500) at
/usr/src/sys/kern/kern_intr.c:547
ih = (struct intrhand *) 0xc12e2c80
p = (struct proc *) 0xc12e754c
count = 0
warming = 5000
warned = 0
#24 0xc04c32c2 in fork_exit (callout=0xc04c4550 , arg=0x0,
frame=0x0)
at /usr/src/sys/kern/kern_fork.c:791
p = (struct proc *) 0xc12e754c
#25 0xc062da9c in fork_trampoline () at
/usr/src/sys/i386/i386/exception.s:209
No locals.
(kgdb)
---
Robin P. Blanchard
Systems Integration Specialist
Georgia Center for Continuing Education
fon: 706.542.2404 <-> fax: 706.542.6546
---
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problems with portupgrade
I'm trying to upgrade spamassassin, but portupgrade is stubling on every dependant port. It appears it wants to re-install each port, which of course doesn't work. It generates the make deinstall first error message. portupgrade -m -DFORCE_PKG_REGISTER seems to have gotten around the problem, but I'm curious as to what's causing this. Anyone have any ideas? This is 4.11-RELEASE if that matters... -- Jim C. Nasby, Database Consultant [EMAIL PROTECTED] Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.4-RC2 freezing - ATA related?
On 21/05/2005, at 0:52, Peter Jeremy wrote: On Fri, 2005-May-20 14:53:09 -0600, Elliot Finley wrote: From: "Peter Jeremy" <[EMAIL PROTECTED]> On Fri, 2005-May-20 08:25:58 -0600, Elliot Finley wrote: I took the -L option off of my dump command in my daily dump script. I've gone two days without locking up which is unusual. I think that may be what was tickling the bug that was locking me up. Sometime you might like to do a 'dd if=/dev/ar0 of=/dev/null bs=32k' just to confirm that you don't have any unreadable blocks (though this seems unlikely). came up clean. transfer went 40MB/s. That seem to leave the finger pointing at the ATA driver. Paging Søren: Are you have to help Elliot? No, my only advise is to use the ATA mkIII patches or better yet - current.. - Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with portupgrade
Jim C. Nasby wrote: I'm trying to upgrade spamassassin, but portupgrade is stubling on every dependant port. It appears it wants to re-install each port, which of course doesn't work. It generates the make deinstall first error message. portupgrade -m -DFORCE_PKG_REGISTER seems to have gotten around the problem, but I'm curious as to what's causing this. Anyone have any ideas? This is 4.11-RELEASE if that matters... Did you perhaps upgrade your Perl earlier? so that perhaps the existing installed dependant ports are Perl packages for 5.6.1, but you now have 5.6.2 and portupgrade thinks your dependant packages should be for that - but it can't install them because the older versions for 5.6.1 are in place. Barry ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.4RELEASE: problem with my ST34311A UDMA666 controller
Hello, try and switch the mode to PIO. You can use atacontrol when the system is running. Try and set the PIO in the BIOS to boot without DMA. Cheers, Vladimir On Sat, 21 May 2005, Remi Degruson wrote: Hello, On one of my computers, the 5.4 RELEASE bootonly disc don't want to write on my hdd. The same hdd is ok whith other computer. I have the same log whith 2 another hdd : atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ... ad0: 4104MB [8895/15/63] at ata0-master UDMA66 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63 ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63 ad0: FAILURE - READ_DMA status=51 error=48 LBA=63 It's my first attempt to install freebsd on this computer. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[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: Problems with portupgrade
On Sat, May 21, 2005 at 02:47:28PM -0500, Barry Pederson wrote: > Jim C. Nasby wrote: > >I'm trying to upgrade spamassassin, but portupgrade is stubling on every > >dependant port. It appears it wants to re-install each port, which of > >course doesn't work. It generates the make deinstall first error > >message. portupgrade -m -DFORCE_PKG_REGISTER seems to have gotten around > >the problem, but I'm curious as to what's causing this. Anyone have any > >ideas? > > > >This is 4.11-RELEASE if that matters... > > Did you perhaps upgrade your Perl earlier? so that perhaps the existing > installed dependant ports are Perl packages for 5.6.1, but you now have > 5.6.2 and portupgrade thinks your dependant packages should be for that > - but it can't install them because the older versions for 5.6.1 are in > place. I did recently go from 5.8 to 5.6. So that means all my perl stuff needs to re-install? That doesn't really make any sense... -- Jim C. Nasby, Database Consultant [EMAIL PROTECTED] Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 5.3 forgets some of my users
Hello there, there is a strange thing FreeBSD 5.3 randomly frogets some of my users. Sometimes I see in the first column of the ps aux output the uid number instead of the login name, but next when I run it, there is the login name. Besides, I tried to chown a directory to an existing user, but the I get an error message, that there wasn't such user. I immediately checked passwd, group and master.passwd files in /etc but the entry for that user was present there. The pw userdel was unable to delete that user, so I had to manually remove it from those three files and create it again. It worked then, but a bit later there was the same result. I'm quite annoyed now. This state isn't safe enough, I have to do something to get around with this. Do You have similar experiences? Or do You now some kinda workaround? Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with portupgrade
On Sat, 21 May 2005 15:49:03 -0500 "Jim C. Nasby" <[EMAIL PROTECTED]> wrote: > On Sat, May 21, 2005 at 02:47:28PM -0500, Barry Pederson wrote: > > Jim C. Nasby wrote: > > >I'm trying to upgrade spamassassin, but portupgrade is stubling on every > > >dependant port. It appears it wants to re-install each port, which of > > >course doesn't work. It generates the make deinstall first error > > >message. portupgrade -m -DFORCE_PKG_REGISTER seems to have gotten around > > >the problem, but I'm curious as to what's causing this. Anyone have any > > >ideas? > > > > > >This is 4.11-RELEASE if that matters... > > > > Did you perhaps upgrade your Perl earlier? so that perhaps the existing > > installed dependant ports are Perl packages for 5.6.1, but you now have > > 5.6.2 and portupgrade thinks your dependant packages should be for that > > - but it can't install them because the older versions for 5.6.1 are in > > place. > > I did recently go from 5.8 to 5.6. So that means all my perl stuff needs > to re-install? That doesn't really make any sense... See /usr/ports/UPDATING for perl entries and possible workarounds to reinstalling perl dependent ports. -- IOnut Unregistered ;) FreeBSD "user" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with portupgrade
Jim C. Nasby wrote: On Sat, May 21, 2005 at 02:47:28PM -0500, Barry Pederson wrote: >> Did you perhaps upgrade your Perl earlier? so that perhaps the existing installed dependant ports are Perl packages for 5.6.1, but you now have 5.6.2 and portupgrade thinks your dependant packages should be for that - but it can't install them because the older versions for 5.6.1 are in place. I did recently go from 5.8 to 5.6. So that means all my perl stuff needs to re-install? That doesn't really make any sense... Yeah, that'll do it. A lot of those Perl modules are not pure Perl, and contain compiled shared libraries (try; find /usr/local/lib/perl5 -name "*.so"). It's kind of a pain - I'm not at all a Perl fan myself, but have fought with it just to get SpamAssassin running. Too bad they don't handle it the way Python modules are handled, where the same port of a Python module can be installed multiple times for multiple versions of Python. Anyhow, /usr/ports/UPGRADING talks about upgrading all Perl dependencies. This page also quotes the same info http://www.freshports.org/lang/perl5.8 Barry ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: drive failure during rebuild causes page fault
On 21/05/2005, at 1:10, Joe Rhett wrote: On Thu, May 19, 2005 at 08:21:13AM +0200, Søren Schmidt wrote: On 19/05/2005, at 2.20, Joe Rhett wrote: Soren, I've just retested all of this with 5.4-REL and most of the problems listed here are solved. The only problems appear to be related to these ghost arrays that appear when it finds a drive that was taken offline earlier. For example, pull a drive and then reboot the system. This depends heavily on the metadata format used, some of them simply doesn't have the info to avoid this and some just ignores the problem. .... You need to overwrite the metadata (se above) which are located in different places again depending on metadata format. So where is it located with the sil3114 controler? (same as 3112, but with 4 ports...) Depends on what BIOS you have on there, several exists for the SiI chips, -current or mkIII would tell you which. Just null out the last 63 sectors on the disks and you should be fine since all possible formats are in that range... Is there anything I can do with userland utilities? ATA mkIII is exactly about getting ata-raid rewritten from the old cruft that originally was written before even ATA-ng was done, so yes I'd expect it to behave better but not necessarily solve all your problems as some of them might be "features" of the metadata So what do I need to know to determine the problem? The metadata format for one, thats the most important factor for getting this to work, but some of them has no generation or anything so its hard if not impossible to avoid this problem. - Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ggate failure in 5.4-STABLE
I have a setup where I mirror disk using a remote ggate disk and a local disk. If the system is entirel quiescent, the rebuild will occur flawlessly, but if the system is in use, I often get the following during a rebuild (on the ggate client): GEOM_MIRROR: Request failed (error=5). ggate2[WRITE(offset=95143855104, length=8192)] GEOM_MIRROR: Device m2: provider ggate2 disconnected. GEOM_MIRROR: Device m2: rebuilding provider ggate2 stopped. GEOM_MIRROR: Request failed (error=5). ggate2[WRITE(offset=95143863296, length=8192)] Now... on both the server and the client, the ggate processes are still running. On the server, there are no kernel log messages. Specifically, there are no disk media errors. I gather ggate has no error recovery at all. Could a corrupted network packet be causing this? What do you all suspect the overall bit rate of inexpensive GigE hubs is? Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.4-RC2 freezing - ATA related?
* Søren Schmidt ([EMAIL PROTECTED]) wrote: > No, my only advise is to use the ATA mkIII patches or better yet - > current.. In a similar vein, I'm seeing the same WRITE_DMA timeouts and system lockups using ATA mkIII patches as I did using the standard RELENG_5 driver, on two seperate systems. I'm getting the WRITE_DMA retries on a multi-gmirror Athlon system using a PCI SATA card; the two PATA drives on the system are fine: FreeBSD 5.4-STABLE #0: Thu Apr 28 06:31:53 BST 2005 atapci1: port 0xcc00-0xcc0f,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc07 mem 0xe7062000-0xe70621ff irq 11 at device 12.0 on pci0 ad4: 381554MB [775221/16/63] at ata2-master SATA150 ad6: 381554MB [775221/16/63] at ata3-master SATA150 .. ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=401743679 ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=781421759 It seems harmless, but results in writes freezing for several seconds every couple of hundred MB (annoying with 360G of storage as you might imagine). It normally favours a single drive, but seems to bounce between ad4 and 6 for no apparant reason. Replacing the SATA card and cables has no effect. Attempting to drop the drives to PIO with atacontrol doesn't seem to do anything either (they remain at SATA150). The other system where I see the lockups (I used to get READ/WRITE_DMA timeouts with the lockup many moons ago, which seems to have started after a system update, but for the past 6+ months or so I just get the lockup) is an old BP6 (dual Celeron), on two different channels on two different drive: FreeBSD 5.4-STABLE #2: Tue Apr 26 17:59:25 BST 2005 atapci1: port 0xd800-0xd8ff,0xd400-0xd403,0xd000-0xd007 irq 18 at device 19.0 on pci0 atapci2: port 0xe400-0xe4ff,0xe000-0xe003,0xdc00-0xdc07 irq 18 at device 19.1 on pci0 ad4: 76319MB at ata2-master UDMA66 ad6: 114473MB at ata3-master UDMA66 Setting these drives to PIO4 resolves the stability problems (which again only occurs under heavy disk activity, almost always on writes), but makes the system crawl. I'm planning on migrating it to gmirror, which I expect will make it behave more like the Athlon, but obviously I'd like to be able to use DMA reliably without resorting to RAID-1 everywhere. Save me Søren! -- Thomas 'Freaky' Hurst http://hur.st/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.4-RC2 freezing - ATA related?
On 22/05/2005, at 2:36, Thomas Hurst wrote: * Søren Schmidt ([EMAIL PROTECTED]) wrote: No, my only advise is to use the ATA mkIII patches or better yet - current.. In a similar vein, I'm seeing the same WRITE_DMA timeouts and system lockups using ATA mkIII patches as I did using the standard RELENG_5 driver, on two seperate systems. I'm getting the WRITE_DMA retries on a multi-gmirror Athlon system using a PCI SATA card; the two PATA drives on the system are fine: FreeBSD 5.4-STABLE #0: Thu Apr 28 06:31:53 BST 2005 atapci1: port 0xcc00-0xcc0f, 0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc07 mem 0xe7062000-0xe70621ff irq 11 at device 12.0 on pci0 ad4: 381554MB [775221/16/63] at ata2-master SATA150 ad6: 381554MB [775221/16/63] at ata3-master SATA150 .. ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=401743679 ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=781421759 It seems harmless, but results in writes freezing for several seconds every couple of hundred MB (annoying with 360G of storage as you might imagine). It normally favours a single drive, but seems to bounce between ad4 and 6 for no apparant reason. Replacing the SATA card and cables has no effect. Attempting to drop the drives to PIO with atacontrol doesn't seem to do anything either (they remain at SATA150). The other system where I see the lockups (I used to get READ/WRITE_DMA timeouts with the lockup many moons ago, which seems to have started after a system update, but for the past 6+ months or so I just get the lockup) is an old BP6 (dual Celeron), on two different channels on two different drive: FreeBSD 5.4-STABLE #2: Tue Apr 26 17:59:25 BST 2005 atapci1: port 0xd800-0xd8ff,0xd400-0xd403,0xd000-0xd007 irq 18 at device 19.0 on pci0 atapci2: port 0xe400-0xe4ff,0xe000-0xe003,0xdc00-0xdc07 irq 18 at device 19.1 on pci0 ad4: 76319MB at ata2-master UDMA66 ad6: 114473MB at ata3-master UDMA66 Setting these drives to PIO4 resolves the stability problems (which again only occurs under heavy disk activity, almost always on writes), but makes the system crawl. I'm planning on migrating it to gmirror, which I expect will make it behave more like the Athlon, but obviously I'd like to be able to use DMA reliably without resorting to RAID-1 everywhere. Save me Søren! You have picked some of the most dreaded HW out there thats for sure, so I'm not sure I can do that :) Anyhow, you should try a recent -current since some of the race/ timeout problems thats possible in 5.x has been fixed there. - Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[RELENG_4] buildkernel failure with MAKEOBJDIRPREFIX
Hello,
I tried to rebuild a debug kernel to analyze one of my problem(*),
and, I faced to another problem. Now this is the main problem for me.
The problem I have now is that 'make buildkernel' does not refer to
${MAKEOBJDIRPREFIX} set in /etc/make.conf. The reason I will use
MAKEOBJDIRPREFIX is that my /usr/obj does not have enough space to
build the debug kernel with DEBUG=-g.
I set MAKEOBJDIRPREFIX=/other/big/directory in /etc/make.conf and ran
'make buildkernel' in /usr/src. And got an error "/usr/src: file
system full". Because /usr/src is another partition and has as small
space as /usr/obj. /usr/src is 400MB and /usr/obj is 500MB which are
enouch to build normal RELENG_4 world.
I noticed that modules are built in /usr/src/sys/modules not in
${MAKEOBJDIRPREFIX}/usr/src/sys/modules. Of cource, kernel.debug is
created in ${MAKEOBJDIRPREFIX}/usr/src/sys/CONFIG/kernel.debug.
I think this is a bug of make, *.mk or other Makefiles in /sys but I
cannot fix it.
(*) When running /usr/sbin/ppp to connect to the provider with PPPoE,
the system gets panic with 'fatal trap 12' after several days of
uptime. I have seen this panic twice in these 10 days.
--
NAKAJI Hiroyuki
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EHCI device
On Sat, 21 May 2005 23:34, Ivan Voras wrote: > When I plug my digital camera in, I get this report: > > umass0: HEWLETT-PACKARD HP PhotoSmart R607, rev 2.00/0.01, addr 2 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 1.000MB/s transfers > da0: 24MB (50305 512 byte sectors: 64H 32S/T 24C) > > Looking at the transfer speed, it only registers as USB 1 device, right? > On Windows XP (on different machine) it's recognized as USB 2 > compliant, but I can't really say if it actually works faster. Can it be > made to work as USB2 on FreeBSD? The speed reported by CAM is not the actual speed the device will run at. Test the speed of copying a few files to/from the camera and see what it really is (although it's not like flash is very fast anyway) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpG31uKmqW3c.pgp Description: PGP signature
Re: em and bge driver MPSAFE?
Mipam wrote this message on Wed, May 11, 2005 at 16:39 +0200: > Perhaps lame to ask, > But are the em and bge driver MPSAFE? > I couldn't find notes about being mpsafe in the man pages of these > drivers? I was about to point you to: http://www.freebsd.org/projects/busdma/ But realized that you probably wanted status on 5.x, and not HEAD... a quick look at the code shows that both em and bge are MPSAFE... I can tell because of no references to Giant or GIANT, and that it using XX_LOCK and has functions ending in _locked in them... Maybe we need to expand the busdma project to include which driver status for 5.x and HEAD? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
