Re: Total crash in gdb!.. something is broken!.. Was: Re: FreeBSD with a Gigabyte GA-K8NSC?
Fcking great.. Waking up and noting that the box has rebooted it self during the night... Yay!!... No kernel dumps, nothing in message log.. Nada... (this was on the first box, that is the one first in this thread) What exactly does kernel dumps on /dev/mirror/gm0s1b mean? Not that it saves any kernel dumps at least.. But otoh I have no clue why it crashed at all and if it even did try to dump kernel or if it just blacked out as when i tried to debug clamd... -- Johan On Sep 24, 2006, at 14:23 , Johan Ström wrote: Okay, I got some problems here now... I'm trying to get clamav's clamd to work.. Failes with an abort in libc: It coredumps directly on start, trace: http://sial.org/pbot/19922 Truss output: www.stromnet.org/~johan/clamd.log Okay...something seems to be f*cked in the nss/ldap stuff.. Anyway,, when running with gdb --args /usr/local/sbin/clamd --debug it works fine!... No coredump or anything, untill i decide to kill clamd.. kill pidofclamd breaks into gdb, and when I run continue to process the signal and let it die, the whole fcking box dies! Screen goes black and reboot.. No panic messages or anything... I have reproduced this two times now on the box in the dmesg in earlier mail... Then i moved the disk to another box pretty similar, same chipset i thikn but not exactly same mobo.. tried the above commands, and bam exactly same problem.. screen just goes black and the box reboots... Dmesg from that box: if i can get the crap up running. now the fs is broken or some shit get this on boot, after started a few services: Starting jails:/usr: bad dir ino 32125198 at offset 512: mangled entry panic: ufs_dirbad: bad dir Uptime: 54s GEOM_MIRROR: Device gm0: provider mirror/gm0 destroyed GEOM_MIRROR: Device gm0 destroyed. Cannot dump. No dump device defined. Automatic reboot in 15 seconds... Ok, now i rebooted to singeluser mode and enalbed the dumpdev in rc.conf... , then saw it continune booting and i chcked for the line saying kernel dumps on /dev/mirror/gm0s1b... it was there... and then it booted further and got by the place it crashed before, but a minute later when i try to login to crashes on the same inode... AND STILL!.. it says Cannot dump. No dump device defined... WTF??... brokeness brokeness.. Okay, after some fscking its back up. dmesg from second box which i can crash with clamd...: Copyright (c) 1992-2006 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 6.1-RELEASE-p7 #0: Wed Sep 20 09:21:41 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ELFI Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3200+ (2210.09-MHz K8-class CPU) Origin = AuthenticAMD Id = 0xfc0 Stepping = 0 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PG E,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 AMD Features=0xe0500800SYSCALL,NX,MMX+,LM,3DNow+,3DNow real memory = 1073676288 (1023 MB) avail memory = 1024299008 (976 MB) ACPI APIC Table: Nvidia AWRDACPI ioapic0 Version 1.1 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: Nvidia AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff,0xcf0-0xcf3 on acpi0 pci0: ACPI PCI bus on pcib0 agp0: NVIDIA nForce3-250 AGP Controller mem 0xf000-0xf7ff at device 0.0 on pci0 isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 pci0: serial bus, SMBus at device 1.1 (no driver attached) ohci0: OHCI (generic) USB controller mem 0xfe02f000-0xfe02 irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: OHCI (generic) USB controller mem 0xfe02e000-0xfe02efff irq 22 at device 2.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: OHCI (generic) USB controller on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0: NVIDIA nForce3 250 USB 2.0 controller mem 0xfe02d000-0xfe02d0ff irq 23 at device 2.2 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: NVIDIA nForce3 250 USB 2.0 controller on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered nve0: NVIDIA nForce MCP7 Networking Adapter port 0xf000-0xf007 mem 0xfe02c000-0xfe02cfff irq 21 at device 5.0 on pci0 nve0: Ethernet address
Re: Total crash in gdb!.. something is broken!.. Was: Re: FreeBSD with a Gigabyte GA-K8NSC?
On 9/25/06, Johan Ström [EMAIL PROTECTED] wrote:
Fcking great.. Waking up and noting that the box has rebooted it self
during the night... Yay!!... No kernel dumps, nothing in message
log.. Nada... (this was on the first box, that is the one first in
this thread)
What exactly does
kernel dumps on /dev/mirror/gm0s1b
mean? Not that it saves any kernel dumps at least.. But otoh I have
no clue why it crashed at all and if it even did try to dump kernel
or if it just blacked out as when i tried to debug clamd...
--
Johan
It means that the system died and released the sphincter when it did.
If you have dumpdev='AUTO'
dumpdir='/var/crash'
in your rc.conf, then you can find the crash dump in ${dumpdir}, then
you can use kgdb to retrieve the backtrace from the dump.
Jiawei
--
If it looks like a duck, walks like a duck, and quacks like a duck,
then to the end user it's a duck, and end users have made it pretty
clear they want a duck; whether the duck drinks hot chocolate or
coffee is irrelevant.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PERC trouble?
Paul Saab [EMAIL PROTECTED] writes: this was fixed after 6.1-RELEASE. You need to grab the driver from -stable. What does it mean? That I could run 6.1-RELEASE but have some drivers from -stable or -current? -- One cannot sell the earth upon which the people walk Tacunka Witco ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PERC trouble?
Marko Lerota wrote: Paul Saab [EMAIL PROTECTED] writes: this was fixed after 6.1-RELEASE. You need to grab the driver from -stable. What does it mean? That I could run 6.1-RELEASE but have some drivers from -stable or -current? You can use the -stable driver on 6.1-RELEASE if you don't want to upgrade to -stable. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
chpass(1) patch for changing only crypted passwords
Dear colleagues, chpass is a bit broken since chpass.c:1.23 - it uses pw_equal which does not check crypted password field; so, you can not change _only_ crypt pass with chpass. Attached patch fixes this. Any thoughts/objections? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** Index: usr.bin/chpass/chpass.c === RCS file: /home/ncvs/src/usr.bin/chpass/chpass.c,v retrieving revision 1.27 diff -u -r1.27 chpass.c --- usr.bin/chpass/chpass.c 18 Jan 2004 21:46:39 - 1.27 +++ usr.bin/chpass/chpass.c 25 Sep 2006 07:42:25 - @@ -217,7 +217,12 @@ pw_fini(); if (pw == NULL) err(1, edit()); - if (pw_equal(old_pw, pw)) + /* +* pw_equal does not check for crypted passwords, so we +* should do it explicitly +*/ + if (pw_equal(old_pw, pw) + strcmp(old_pw-pw_passwd, pw-pw_passwd) == 0) errx(0, user information unchanged); } ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Total crash in gdb!.. something is broken!.. Was: Re: FreeBSD with a Gigabyte GA-K8NSC?
On Sep 25, 2006, at 8:36, Johan Ström wrote:
What exactly does
kernel dumps on /dev/mirror/gm0s1b
mean? Not that it saves any kernel dumps at least.. But otoh I have
no clue why it
It means exactly that. IIRC kernel dumps are created in swap space
and on the next boot are moved to ${dumpdir}. I'm pretty certain this
is explained nicely in the handbook[1].
AFAIK kernels can only be dumped on real devices, not on virtual
devices like /dev/mirror/*. In that case your setup is not going to
get you any dumps.
Besides that, it is probably not a very good idea to mirror your
swap. I am certain it is bad for performance, if it'd gain you
reliability is beyond my knowledge. This has been discussed before,
you probably want to check the archives.
[1] Which I didn't check as I'm about to be in a hurry...
--
Alban Hertroys
Priest to alien: We want to know, is there a higher
being?.
Alien: Well, actually that's why we're here,
we're sheer out of virgins.
!DSPAM:74,45178b3f7241469027555!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Total crash in gdb!.. something is broken!.. Was: Re: FreeBSD with a Gigabyte GA-K8NSC?
On Sep 25, 2006, at 08:45 , Jiawei Ye wrote:
On 9/25/06, Johan Ström [EMAIL PROTECTED] wrote:
Fcking great.. Waking up and noting that the box has rebooted it self
during the night... Yay!!... No kernel dumps, nothing in message
log.. Nada... (this was on the first box, that is the one first in
this thread)
What exactly does
kernel dumps on /dev/mirror/gm0s1b
mean? Not that it saves any kernel dumps at least.. But otoh I have
no clue why it crashed at all and if it even did try to dump kernel
or if it just blacked out as when i tried to debug clamd...
--
Johan
It means that the system died and released the sphincter when it did.
If you have dumpdev='AUTO'
dumpdir='/var/crash'
in your rc.conf, then you can find the crash dump in ${dumpdir}, then
you can use kgdb to retrieve the backtrace from the dump.
I got dumpdev=/dev/mirror/gm0s1b, savecore doesnt extract any dumps :/
Jiawei
--
If it looks like a duck, walks like a duck, and quacks like a duck,
then to the end user it's a duck, and end users have made it pretty
clear they want a duck; whether the duck drinks hot chocolate or
coffee is irrelevant.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Direct Rendering Manager problems
Dear colleagues, I've recently discovered some oddity with DRM on FreeBSD. Maybe it's a FAQ, but it seems to me that both on-demand kernel module loading and loading them in /boot/loader.conf is broken on recent RELENG_6. I've an ATI Radeon Mobility 9700 and self-built RELENG_6. When I started X, X.org server reports that no DRI available. Manual looking into /dev shows that no /dev/dri directory presents at all. Loading radeon.ko in /boot/loader.conf doesn't fix the problem. Also no DRM-related lines appears in dmesg output. But problem goes away after adding line device radeondrm to kernel configuration file, rebuilding kernel and rebooting the machine. Direct Rendering Manager initialises correctly, and node /dev/dri/card0 exists. Are there any suggestions for additional testing? -- Andrew Kolchoogin. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Total crash in gdb!.. something is broken!.. Was: Re: FreeBSD with a Gigabyte GA-K8NSC?
fOn Sep 25, 2006, at 09:55 , Alban Hertroys wrote:
On Sep 25, 2006, at 8:36, Johan Ström wrote:
What exactly does
kernel dumps on /dev/mirror/gm0s1b
mean? Not that it saves any kernel dumps at least.. But otoh I
have no clue why it
It means exactly that. IIRC kernel dumps are created in swap space
and on the next boot are moved to ${dumpdir}. I'm pretty certain
this is explained nicely in the handbook[1].
Probably is, yes I know what it means, I was just pretty upset at the
moment..;)
AFAIK kernels can only be dumped on real devices, not on virtual
devices like /dev/mirror/*. In that case your setup is not going to
get you any dumps.
In earlier FBSD (6.0 i think?) one got an ioctl error when trying to
dumpon to a gmirror device, but if I dont recall wrong this has been
changed since (I dont get an ioctl error anymore at least...)
Besides that, it is probably not a very good idea to mirror your
swap. I am certain it is bad for performance, if it'd gain you
reliability is beyond my knowledge. This has been discussed before,
you probably want to check the archives.
Performance yes, but I think I've read that it is best anyway, if
one of your disks dies, youd dont want to loose half your swap since
that would not be very good if there is anything swapped out to that
disk..
[1] Which I didn't check as I'm about to be in a hurry...
--
Alban Hertroys
Priest to alien: We want to know, is there a higher
being?.
Alien: Well, actually that's why we're here,
we're sheer out of virgins.
!DSPAM:259,45178b407241208415560!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Total crash in gdb!.. something is broken!.. Was: Re: FreeBSD with a Gigabyte GA-K8NSC?
Alban Hertroys wrote: Besides that, it is probably not a very good idea to mirror your swap. I am certain it is bad for performance, if it'd gain you reliability is beyond my knowledge. This has been discussed before, you probably want to check the archives. On the contrary, it is a very good idea indeed to mirror the swap partition if your aim is to make your machine resilient against disk failure. Losing the swap will kill a machine just as dead as losing a filesystem. The performance of a mirrored root drive is a bit slower on write but generally faster on read -- it tends to pretty much even out in the end. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. Flat 3 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW, UK signature.asc Description: OpenPGP digital signature
Re: chpass(1) patch for changing only crypted passwords
Dmitry Morozovsky [EMAIL PROTECTED] writes: chpass is a bit broken since chpass.c:1.23 - it uses pw_equal which does not check crypted password field; so, you can not change _only_ crypt pass with chpass. Attached patch fixes this. Looks fine to me, feel free to commit. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Automounter flags for pcfs?
The goal is to have a USB flash drive mounted via automounter in a way
that it auto-umounts after a while so I don't crash the system by
pluggin it out wile mounted. My amd.map looks like this:
/defaults type:=host;fs:=${autodir}/${rhost}/host;rhost:=${key};
* opts:=rw,grpid,resvport,vers=3,proto=udp,nosuid,nodev
flash-s1
type:=pcfs;dev:=/dev/da0s1;fs:=${autodir}/flash-s1;opts:=rw,longnames,-m664,-M777;
The problem is that opts are not passed to mount_msdosfs which results
in all files having execute bits set, etc. Using msdosfs instead of
pcfs makes amd fail with unknown file system.
So, how to do this? I'll accept anything that gets the proper flags to
mount_msdosfs.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: winbindd won't start
[2006/09/24 11:30:15, 0] libsmb/cliconnect.c:cli_session_setup_spnego(776) Kinit failed: Cannot contact any KDC for requested realm Failed to join domain! As far as I know, nothing has changed. Does anyone have any suggestions? Is your /etc/krb5.conf intact and correct? Do you have a valid ticket? (klist) Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Direct Rendering Manager problems
On Mon, Sep 25, 2006 at 12:42:44PM +0400, Andrew Kolchoogin wrote: Dear colleagues, I've recently discovered some oddity with DRM on FreeBSD. Maybe it's a FAQ, but it seems to me that both on-demand kernel module loading and loading them in /boot/loader.conf is broken on recent RELENG_6. That does not appear to be my experience; more details below. I've an ATI Radeon Mobility 9700 and self-built RELENG_6. When I started X, X.org server reports that no DRI available. Manual looking into /dev shows that no /dev/dri directory presents at all. Loading radeon.ko in /boot/loader.conf doesn't fix the problem. Also no DRM-related lines appears in dmesg output. But problem goes away after adding line device radeondrm to kernel configuration file, rebuilding kernel and rebooting the machine. Direct Rendering Manager initialises correctly, and node /dev/dri/card0 exists. Are there any suggestions for additional testing? Here is some relevant information from my current laptop. Note that its disk drive was moved from the previous laptop (same model, but used an nVidia video card), so I had merely commented out loading the nvidia module while I was working on switching to the radeon module (and hadn't yet got around to deleting the line). g1-18(6.2-P)[1] uname -a FreeBSD g1-18.catwhisker.org. 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #185: Sun Sep 24 06:36:42 PDT 2006 [EMAIL PROTECTED]:/common/S1/obj/usr/src/sys/LAPTOP_30W i386 g1-18(6.2-P)[2] ls -la /dev/dri/ total 1 dr-xr-xr-x 2 root wheel 512 Sep 24 10:19 . dr-xr-xr-x 5 root wheel 512 Dec 31 1969 .. crw-rw 1 root wheel0, 135 Sep 24 10:18 card0 g1-18(6.2-P)[3] kldstat Id Refs AddressSize Name 1 16 0xc040 6a00b8 kernel 23 0xc0aa1000 1adb8linux.ko 31 0xc0abc000 59f00acpi.ko 41 0xc487f000 6000 linprocfs.ko 51 0xc4a13000 2000 rtc.ko 61 0xc4c15000 1e000radeon.ko 71 0xc4c33000 e000 drm.ko g1-18(6.2-P)[4] cat /boot/loader.conf boot_verbose=YES debug.mpsafenet=1 hw.ata.atapi_dma=1 # nvidia_load=YES linux_load=YES g1-18(6.2-P)[5] grep -i driver /etc/X11/XF86Config Driver keyboard Driver mouse ### Available Driver options are:- Driver radeon g1-18(6.2-P)[6] grep 'ATI Technologies Inc Radeon' /var/log/Xorg.0.log (--) PCI:*(1:0:0) ATI Technologies Inc Radeon R250 Lf [FireGL 9000] rev 1, Mem @ 0xe000/27, 0xfcff/16, I/O @ 0xc000/8, BIOS @ 0x8000/17 g1-18(6.2-P)[7] So it looks to me as if X handles loading the radeon.ko module and that (in turn) creates the /dev/dri/* entries -- as expected. Peace, david -- David H. Wolfskill [EMAIL PROTECTED] Believe SORBS at your own risk: 63.193.123.122 has been static since Aug 1999. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpSqymItoWkW.pgp Description: PGP signature
Re: probs on 6.2-prerelease
Michael Vince wrote: Hey all, I don't know if this is pre 6.2 specific but I changed my /etc/tty for device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't login via regular KVM console, just don't get a login. The more alarming thing was that while it appeared everything was booting up from the boot up messages on the screen, I couldn't remotely log into the server in fact it appears the machine didn't bring up the Ethernet device as I couldn't even ping it. As soon as I switched the ttyd0 back to 'off' and rebooted it I could ssh back into the server etc. I have a regular kernel and 1 jail and samba on this machine. I know this isn't a yes I'm having problems response but thought it might be useful anyway. I'm running 6.2-pre on a Soekris Engineering Net4501 with ttyd0 enabled in /etc/ttys and I'm not having any problems with the system booting or logging in via serial console. SSH logins work fine and the network is brought-up as normal during boot. I've had this system in the same config (in regards to /etc/ttys) since the 6 was still the HEAD branch and I have yet to see problems with it. One difference here is that I don't have any virtual consoles enabled BUT ttyd0 (and pseudo-terminals), as this box doesn't have a video card, just a serial port. FreeBSD marconi.localnet 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Tue Sep 12 03:06:13 EDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MINIBSD6 i386 /etc/ttys: # # $FreeBSD: src/etc/etc.i386/ttys,v 1.10 2003/10/24 15:44:08 simokawa Exp $ # @(#)ttys5.1 (Berkeley) 4/17/89 ... console noneunknown off secure # ttyv0 /usr/libexec/getty Pc cons25 off insecure # Virtual terminals ttyv1 /usr/libexec/getty Pc cons25 off insecure ttyv2 /usr/libexec/getty Pc cons25 off insecure ttyv3 /usr/libexec/getty Pc cons25 off insecure ttyv4 /usr/libexec/getty Pc cons25 off insecure ttyv5 /usr/libexec/getty Pc cons25 off insecure ttyv6 /usr/libexec/getty Pc cons25 off insecure ttyv7 /usr/libexec/getty Pc cons25 off insecure ttyv8 /usr/X11R6/bin/xdm -nodaemon xterm off insecure # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyd0 /usr/libexec/getty std.9600 dialup on secure ttyd1 /usr/libexec/getty std.9600 dialup off secure ttyd2 /usr/libexec/getty std.9600 dialup off secure ttyd3 /usr/libexec/getty std.9600 dialup off secure # Dumb console dcons /usr/libexec/getty std.9600 vt100 off secure -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: winbindd won't start
C. Scott wrote: Last night I upgraded Samba on my FBSD 6.1 machine. Samba was working fine before the upgrade. Since the upgrade, I can not get winbindd to run. It writes this to the winbindd log before dying: [2006/09/24 11:17:30, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.23c started. Copyright The Samba Team 2000-2004 [2006/09/24 11:17:30, 0] nsswitch/winbindd_util.c:init_domain_list(518) Could not fetch our SID - did we join? [2006/09/24 11:17:30, 0] nsswitch/winbindd.c:main(1051) unable to initalize domain list [2006/09/24 11:17:47, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.23c started. Copyright The Samba Team 2000-2004 [2006/09/24 11:17:47, 0] nsswitch/winbindd_util.c:init_domain_list(518) Could not fetch our SID - did we join? [2006/09/24 11:17:47, 0] nsswitch/winbindd.c:main(1051) unable to initalize domain list Have you moved your Samba tdb files from /usr/local/private to /usr/local/etc/samba/? Hope this helps, Guy Helmer -- Guy Helmer, Ph.D. Chief System Architect Palisade Systems, Inc. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: probs on 6.2-prerelease
On Mon, Sep 25, 2006 at 09:08:26AM -0400, Michael Proto wrote: Michael Vince wrote: I don't know if this is pre 6.2 specific but I changed my /etc/tty for device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't login via regular KVM console, just don't get a login. The more alarming thing was that while it appeared everything was booting up from the boot up messages on the screen, I couldn't remotely log into the server in fact it appears the machine didn't bring up the Ethernet device as I couldn't even ping it. As soon as I switched the ttyd0 back to 'off' and rebooted it I could ssh back into the server etc. I have a regular kernel and 1 jail and samba on this machine. I know this isn't a yes I'm having problems response but thought it might be useful anyway. I'm running 6.2-pre on a Soekris Engineering Net4501 with ttyd0 enabled in /etc/ttys and I'm not having any problems with the system booting or logging in via serial console. SSH logins work fine and the network is brought-up as normal during boot. I've had this system in the same config (in regards to /etc/ttys) since the 6 was still the HEAD branch and I have yet to see problems with it. One difference here is that I don't have any virtual consoles enabled BUT ttyd0 (and pseudo-terminals), as this box doesn't have a video card, just a serial port. I can also report no problems running 6.2-pre on i686. I am running on several machines, using serial consoles, machines _with_ video cards, but mostly unused (one machine has a KVM connected, and it works fine, as well. No problems with video, no problems with network, no problems with ssh login, etc. -greg FreeBSD xxx.xxx.com 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #21: Tue Sep 19 19:37:00 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ i386 /etc/ttys: [...] ttyd0 /usr/libexec/getty std.9600 xterm on secure [...] /boot/loader.conf [...] console=comconsole [...] -- greg byshenk - [EMAIL PROTECTED] - Leiden, NL ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: probs on 6.2-prerelease
Hey all, I don't know if this is pre 6.2 specific but I changed my /etc/tty for device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't login via regular KVM console, just don't get a login. The more alarming thing was that while it appeared everything was booting up from the boot up messages on the screen, I couldn't remotely log into the server in fact it appears the machine didn't bring up the Ethernet device as I couldn't even ping it. As soon as I switched the ttyd0 back to 'off' and rebooted it I could ssh back into the server etc. I have a regular kernel and 1 jail and samba on this machine. This might just be a ports thing but on another 6.2 server I setup a jailed mail server with courier imap and I have noticed that it fails to build the courier-imap port with FAM support. I tried also installing the gamin FAM alternative which builds ok but I get signal 11 when I try to login to the imap server. Does anyone else have these problems? I've been having this for a very long time, if the serial port does not realy exist - i don't know the technical wording for this -, if the kernel detected the sio hardare, but it's not realy wired, then it the kernel will hang when getty will try to open it. danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: probs on 6.2-prerelease
On Mon, Sep 25, 2006 at 04:54:36PM +0300, Danny Braniss wrote: I don't know if this is pre 6.2 specific but I changed my /etc/tty for device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't login via regular KVM console, just don't get a login. The more alarming thing was that while it appeared everything was booting up from the boot up messages on the screen, I couldn't remotely log into the server in fact it appears the machine didn't bring up the Ethernet device as I couldn't even ping it. As soon as I switched the ttyd0 back to 'off' and rebooted it I could ssh back into the server etc. I have a regular kernel and 1 jail and samba on this machine. I've been having this for a very long time, if the serial port does not realy exist - i don't know the technical wording for this -, if the kernel detected the sio hardare, but it's not realy wired, then it the kernel will hang when getty will try to open it. Per chance is the sio* device the kernel detects mapped to acpi0? :-) (Also, taking freebsd-ports off this portion of the discussion; the 2nd part of the OP's thread pertains to freebsd-ports, but not this portion). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: winbindd won't start
I can successfully kinit [EMAIL PROTECTED] and klist shows the ticket. My
krb5.conf:
[libdefaults]
default_realm = YOUR.KERBEROS.REALM
[realms]
YOUR.KERBEROS.REALM = {
kdc = your.kerberos.server
}
[domain_realms]
.kerberos.server = YOUR.KERBEROS.REALM
That is the same config as before. Like I said, I just upgraded Samba, which
was working.
- Original Message -
From: Dominic Marks [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: freebsd-stable@freebsd.org
Sent: Monday, September 25, 2006 3:44:01 AM GMT-0800
Subject: Re: winbindd won't start
[2006/09/24 11:30:15, 0] libsmb/cliconnect.c:cli_session_setup_spnego(776)
Kinit failed: Cannot contact any KDC for requested realm
Failed to join domain!
As far as I know, nothing has changed. Does anyone have any suggestions?
Is your /etc/krb5.conf intact and correct? Do you have a valid
ticket? (klist)
Dominic
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: winbindd won't start
- Guy Helmer [EMAIL PROTECTED] wrote: C. Scott wrote: Last night I upgraded Samba on my FBSD 6.1 machine. Samba was working fine before the upgrade. Since the upgrade, I can not get winbindd to run. It writes this to the winbindd log before dying: [2006/09/24 11:17:30, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.23c started. Copyright The Samba Team 2000-2004 [2006/09/24 11:17:30, 0] nsswitch/winbindd_util.c:init_domain_list(518) Could not fetch our SID - did we join? [2006/09/24 11:17:30, 0] nsswitch/winbindd.c:main(1051) unable to initalize domain list [2006/09/24 11:17:47, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.23c started. Copyright The Samba Team 2000-2004 [2006/09/24 11:17:47, 0] nsswitch/winbindd_util.c:init_domain_list(518) Could not fetch our SID - did we join? [2006/09/24 11:17:47, 0] nsswitch/winbindd.c:main(1051) unable to initalize domain list Have you moved your Samba tdb files from /usr/local/private to /usr/local/etc/samba/? I did not orginally do that. I did move the files just now, and restarted Samba. Winbindd is now running! However, I am still unable to join the Domain Administrator's password: [2006/09/25 08:33:45, 0] libsmb/cliconnect.c:cli_session_setup_spnego(776) Kinit failed: Cannot contact any KDC for requested realm Failed to join domain! kinit works though!? eagle# kinit [EMAIL PROTECTED] [EMAIL PROTECTED]'s Password: kinit: NOTICE: ticket renewable lifetime is 1 week Thanks Hope this helps, Guy Helmer -- Guy Helmer, Ph.D. Chief System Architect Palisade Systems, Inc. ___ 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: winbindd won't start
- Guy Helmer [EMAIL PROTECTED] wrote: C. Scott wrote: Last night I upgraded Samba on my FBSD 6.1 machine. Samba was working fine before the upgrade. Since the upgrade, I can not get winbindd to run. It writes this to the winbindd log before dying: [2006/09/24 11:17:30, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.23c started. Copyright The Samba Team 2000-2004 [2006/09/24 11:17:30, 0] nsswitch/winbindd_util.c:init_domain_list(518) Could not fetch our SID - did we join? [2006/09/24 11:17:30, 0] nsswitch/winbindd.c:main(1051) unable to initalize domain list [2006/09/24 11:17:47, 1] nsswitch/winbindd.c:main(953) winbindd version 3.0.23c started. Copyright The Samba Team 2000-2004 [2006/09/24 11:17:47, 0] nsswitch/winbindd_util.c:init_domain_list(518) Could not fetch our SID - did we join? [2006/09/24 11:17:47, 0] nsswitch/winbindd.c:main(1051) unable to initalize domain list Have you moved your Samba tdb files from /usr/local/private to /usr/local/etc/samba/? :( I just saw this in UPDATING. I don't know how I missed that. Hope this helps, Guy Helmer -- Guy Helmer, Ph.D. Chief System Architect Palisade Systems, Inc. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Mystery symbols made up by C++ at _low_ optimization levels
Could someone with knowledge of compilers, please, look at the PR 103610? http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/103610 One of the source files, when compiled (with -O0 or -O1), grows a symbol, that is not referenced anywhere else... Depending on the optimizations, the symbol name and the line-number change from `.LC786' and 181 with -O0 below: loctest.o(.data+0x51c):/usr/ports/devel/icu/work/icu/source/test/intltest/loctest.cpp:181: undefined reference to `.LC786' loctest.o(.data+0x520):/usr/ports/devel/icu/work/icu/source/test/intltest/loctest.cpp:181: undefined reference to `.LC786' to `.LC779' and 185 with -O1... Compiling with -O2 gets rid of the problem, but not everyone likes to do that. I checked -- it does not come from any pre-processor magic. Any clues? To reproduce, build the devel/icu port with -O1 and -g. Thanks! -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
reporting unimplemented functions in linuxolator?
Hello,
When I use the NX client (net/linux-nx-client), I get lots of lines
in /var/log/messages:
Sep 23 21:01:54 kg-work kernel: linux: pid 19544
(nxproxy): ioctl fd=5, cmd=0x5411 ('T',17) is not imp lemented
Sep 23 21:02:25 kg-work last message repeated 4468 times
The NX client work fine, I just wonder if this should be reported somewhere?
My system:
[EMAIL PROTECTED] uname -a
FreeBSD kg-work.kg4.no 5.5-STABLE FreeBSD 5.5-STABLE #9: Tue Aug 22
17:26:30 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SS51G
i386
--
Regards,
Torfinn Ingolfsen,
Norway
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: chpass(1) patch for changing only crypted passwords
On Mon, 25 Sep 2006, Dag-Erling Sm?rgrav wrote: DS Dmitry Morozovsky [EMAIL PROTECTED] writes: DS chpass is a bit broken since chpass.c:1.23 - it uses pw_equal which DS does not check crypted password field; so, you can not change _only_ DS crypt pass with chpass. Attached patch fixes this. DS DS Looks fine to me, feel free to commit. Done, thanks. BTW, a question inspired by ru@: why pw_equal() skips password field? Its interface is unpublished, and the only consumers are [EMAIL PROTECTED]:/lh/src.current grep -Rl pw_equal . ./lib/libutil/libutil.h ./lib/libutil/pw_util.c ./release/picobsd/tinyware/passwd/pw_copy.c ./usr.bin/chpass/chpass.c and tyniware is false alarm ;) Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrading to 6.2 stable - failed to compile kernel
Hi, As a total newbie, I am pushing my (lack of) knowledge to the limit as a way of learning more about FreeBSD... I had v6.1 release installed and a custom kernel. After the binary upgrade to v6.2, I tried to recreate the PPS kernel from updated sources, but got: | ../../../dev/mii/ip1000phy.c | ../../../dev/mii/ip1000phy.c: In function `ip1000phy_probe': | ../../../dev/mii/ip1000phy.c:91: error: `MII_OUI_ICPLUS' undeclared (first use in this function) | ../../../dev/mii/ip1000phy.c:91: error: (Each undeclared identifier is reported only once | ../../../dev/mii/ip1000phy.c:91: error: for each function it appears in.) | ../../../dev/mii/ip1000phy.c:92: error: `MII_MODEL_ICPLUS_IP1000A' undeclared (first use in this function) | ../../../dev/mii/ip1000phy.c:93: error: `MII_STR_ICPLUS_IP1000A' undeclared (first use in this function) | *** Error code 1 | | Stop in /usr/src/sys/i386/compile/MINIMUM_PPS. Using this method: | config MINIMUM_PPS | cd ../compile/MINIMUM_PPS | make cleandepend | make depend | make | make install MINIMUM_PPS had compiled OK on 6.1 and this is the only way I have tried to create a custom kernel so far. I had run cvsup to register the existing 6.1 release, and then again to update to the latest 6.2 stable. I can post the supfiles, if it would help - it's also the first time I've used cvsup... As an experiment, I have just started a buildworld to see if that will fix the problem. That is likely to take a while on my AMD5x86 machine so, while i am waiting, I thought I would ask if anyone can see where I went wrong. Cheers ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ffs snapshot lockup
On Sep 22, 2006, at 4:36 PM, Kris Kennaway wrote: Start by enabling INVARIANTS, INVARIANT_SUPPORT, DEBUG_LOCKS and DEBUG_VFS_LOCKS, then run 'show lockedvnods' and 'alltrace' in DDB (spammy, need that serial console), or at least trace the running processes (show allpcpu) and those listed in lockedvnods. Then call doadump and save the core+kernel.debug when you reboot. Well, it happened again (as I was building the debugging kernel, no less)... but it only locked up one file system not the whole box. So my home dir was wedged, and everything trying to use anyone's home dir was wedged, but /usr and / were still responding. So now I do have the kernel in place and the serial console is already there and your notes on what to do are there, so next time it happens I'm ready!
Re: Upgrading to 6.2 stable - failed to compile kernel
From: FreeBSD Noob [EMAIL PROTECTED] Date: Mon, 25 Sep 2006 18:52:45 +0100 Sender: [EMAIL PROTECTED] Hi, As a total newbie, I am pushing my (lack of) knowledge to the limit as a way of learning more about FreeBSD... I had v6.1 release installed and a custom kernel. After the binary upgrade to v6.2, I tried to recreate the PPS kernel from updated sources, but got: | ../../../dev/mii/ip1000phy.c | ../../../dev/mii/ip1000phy.c: In function `ip1000phy_probe': | ../../../dev/mii/ip1000phy.c:91: error: `MII_OUI_ICPLUS' undeclared (first use in this function) | ../../../dev/mii/ip1000phy.c:91: error: (Each undeclared identifier is reported only once | ../../../dev/mii/ip1000phy.c:91: error: for each function it appears in.) | ../../../dev/mii/ip1000phy.c:92: error: `MII_MODEL_ICPLUS_IP1000A' undeclared (first use in this function) | ../../../dev/mii/ip1000phy.c:93: error: `MII_STR_ICPLUS_IP1000A' undeclared (first use in this function) | *** Error code 1 | | Stop in /usr/src/sys/i386/compile/MINIMUM_PPS. Using this method: | config MINIMUM_PPS | cd ../compile/MINIMUM_PPS | make cleandepend | make depend | make | make install MINIMUM_PPS had compiled OK on 6.1 and this is the only way I have tried to create a custom kernel so far. I had run cvsup to register the existing 6.1 release, and then again to update to the latest 6.2 stable. I can post the supfiles, if it would help - it's also the first time I've used cvsup... As an experiment, I have just started a buildworld to see if that will fix the problem. That is likely to take a while on my AMD5x86 machine so, while i am waiting, I thought I would ask if anyone can see where I went wrong. 1. Your mail address bounced my attempt at a private reply. 2. Building a kernel with config is not officially supported. It's at your risk and may not work in all cases. Build a kernel with: cd /usr/src make buildkernel 3. You need device mii if you have any network device that uses it and most do. 4. If you update sources, you need to build both world and kernel. (See /usr/src/UPDATING near the end.) If sources are not changes, just re-build the kernel. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgp4VeLhalm63.pgp Description: PGP signature pgp058tDjUjHQ.pgp Description: PGP signature
Re: ffs snapshot lockup
This problem sounds awfully like what I reported in a recent PR. Now I'm starting to have my doubts as to whether or not my hardware was indeed at fault... http://www.freebsd.org/cgi/query-pr.cgi?pr=103435 -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange spaces in ls -kls output, and dd(1) trouble
On Thu, 21 Sep 2006, Oliver Fromme wrote: snip Oh by the way, dd conv=sparse doesn't seem to work for me; it doesn't create a sparse file: $ dd if=/dev/zero of=test bs=512 count=1000 conv=sparse 1000+0 records in 1000+0 records out 512000 bytes transferred in 0.070895 secs (7221952 bytes/sec) $ ls -kls test 528 -rw-r--r-- 1 root nfswheel 512000 Sep 21 19:58 test It is a feature of dd that does not create sparse files if given a block size. Sean -- [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: Upgrading to 6.2 stable - failed to compile kernel
On Mon, 25 Sep 2006 11:34:42 -0700, Kevin Oberman [EMAIL PROTECTED] wrote: Thanks Kevin, 1. Your mail address bounced my attempt at a private reply. Sorry, I don't uderstand why - it is a timelimited address that should work! but it's a facility I don't use that often I did have a look through my log and didn't see a rejection that would tie up with your message. Hmmm. Just a thought: did the bounce message actually come from my mailserver? 2. Building a kernel with config is not officially supported. It's at your risk and may not work in all cases. Build a kernel with: cd /usr/src make buildkernel I was just fightened by all this make.conf stuff! If everything is in my kernel file in /usr/src/sys/i386/conf/MINIMUM_PPS, can I just ignore make.conf? 3. You need device mii if you have any network device that uses it and most do. Yes, it's included; | devicemiibus # MII bus support | # 'device ed' requires 'device miibus' | deviceed # NE[12]000, SMC Ultra, 3c503, DS8390 cards 4. If you update sources, you need to build both world and kernel. (See /usr/src/UPDATING near the end.) If sources are not changes, just re-build the kernel. I wasn't sure if that was necessary. I takes about 2 hours to build the kernel without modules, about 15 hours with modules - I've no idea how long buildworld is going to take... Thanks again. Geoff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to 6.2 stable - failed to compile kernel
I was just fightened by all this make.conf stuff! If everything is in my kernel file in /usr/src/sys/i386/conf/MINIMUM_PPS, can I just ignore make.conf? Your MINIMUM_PPS file contains the entire kernel configuration and unless you want to tweak additional options (compiler flags and optimization settings for example), there is no need to modify make.conf. I wasn't sure if that was necessary. I takes about 2 hours to build the kernel without modules, about 15 hours with modules - I've no idea how long buildworld is going to take... A buildworld takes considerably longer than a kernel build. If a kernel takes hours, a buildworld could be a few days... you must be using a very slow machine. A kernel build on my Centrino 1.6GHz takes only a few minutes. - Bartosz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
SMBus regression (Re: cvs commit: src/sys/dev/bktr bktr_i2c.c bktr_i2c.h src/sys/dev/ichsmb ichsmb.c...
Hello!
On Fri, 22 Sep 2006, John Baldwin wrote:
jhb 2006-09-22 19:19:16 UTC
FreeBSD src repository
Modified files:(Branch: RELENG_6)
sys/dev/bktr bktr_i2c.c bktr_i2c.h
sys/dev/ichsmb ichsmb.c
sys/dev/iicbus iicsmb.c
sys/dev/smbussmb.c smb.h smbconf.c smbconf.h smbus.c
smbus.h smbus_if.m
sys/pci alpm.c amdpm.c amdsmb.c intpm.c nfsmb.c
viapm.c
Log:
MFC: Minor overhaul of SMBus support including:
This commit has broken SMBus attachment at least on ICH4; boot messages
difference (diff -u old new) gives only 1 line missing:
ichsmb0: Intel 82801DC (ICH4) SMBus controller port 0xe000-0xe01f irq 17 at
device 31.3 on pci0
ichsmb0: [GIANT-LOCKED]
smbus0: System Management Bus on ichsmb0
-smb0: SMBus generic I/O on smbus0
So with the new SMBus modules smb0 no longer attaches to the smbus0 despite
having all 3 modules loaded as before:
[EMAIL PROTECTED] kldstat|grep smb
213 0xc07b9000 29ac smbus.ko
231 0xc07c 4ff8 ichsmb.ko
451 0xc6974000 3000 smb.ko
After reverting the contents of /sys/dev/{ichsmb,smbus} to the pre-commit
state (date=2006.09.22.19.19.00) and recompiling the modules (smbus, ichsmb,
smb) I've got working SMBus subsystem again. Please look into this problem.
Sincerely, Dmitry
--
Atlantis ISP, System Administrator
e-mail: [EMAIL PROTECTED]
nic-hdl: LYNX-RIPE
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
bge driver problem for BCM5754 on 6.2 stable
Hi, I install FreeBSD 6.1 on a new Dell Precision 390, which has an on-board BCM5754 GbE NIC that was not recognized. A quick look into the CVS shows that its support is added at if_bge.c rev. 1.91.2.15, later than what is found in 6.1. So I performed cvsup, rebuilt world and kernel with if_bge as a separate module. Loading the module after reboot put kernel to fatal trap 19. Furthermore, the device recognized by the module is wrong - BCM5787 instead of BCM5754. (I checked with pciconf that the on-board GbE does have the device ID of BCM5754.) Below is the fatal trap message - bge0: Broadcom unknown BCM5787, ASIC rev. 0xb002 mem 0xecef-0xecef irq 17 at device 0.0 on pci4 kernel trap 19 with interrupts disabled Fatal trap 19: non-maskable interrupt trap while in kernel mode instruction pointer = 0x20:0xc088c873 stack pointer = 0x28:0xe74caa48 frame pointer = 0x28:0xe74caa54 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= IOPL = 0 current process = 547 (kldload) [thread pid 547 tid 100071 ] Stopped at 0xc088c873 = pcireg_cfgwrite+0xa3: nop db I suspect some problem in if_bge for BCM5754 when merging the device driver source with HEAD after 6.1 release, but I do not have enough knowledge to debug the driver. I hope someone with knowledge of if_bge device driver source could help. Please let me know if other information is needed. Thanks. Sincerely, Edward ___ 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 auditd -- resolved
On Sat, 23 Sep 2006, Robert Watson wrote: Right now the id(1) command in -STABLE doesn't print audit properties of the process, but I've attached a patch that causes it to do so when id -a is run. If you could apply this patch and run id -a as root, that would be helpful. I've merged this patch to 6-STABLE, but we've renamed the flag -A so as not to conflict with a flag in Solaris. If you could let me know what the results of running id -A are, when running as root su'd from a number user that should be getting audited, that would be helpful. Thanks! Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Is there any good reason for get*by*_r()?
get*by*_r() are deprecated on most platforms and there use is highly non-portable, lots of different API's. Why are we adding compatability for deprecated functions? Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [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: probs on 6.2-prerelease
Danny Braniss wrote: Hey all, I don't know if this is pre 6.2 specific but I changed my /etc/tty for device ttyd0 to 'on' from 'off' and when I rebooted the pc I couldn't login via regular KVM console, just don't get a login. The more alarming thing was that while it appeared everything was booting up from the boot up messages on the screen, I couldn't remotely log into the server in fact it appears the machine didn't bring up the Ethernet device as I couldn't even ping it. As soon as I switched the ttyd0 back to 'off' and rebooted it I could ssh back into the server etc. I have a regular kernel and 1 jail and samba on this machine. This might just be a ports thing but on another 6.2 server I setup a jailed mail server with courier imap and I have noticed that it fails to build the courier-imap port with FAM support. I tried also installing the gamin FAM alternative which builds ok but I get signal 11 when I try to login to the imap server. Does anyone else have these problems? I've been having this for a very long time, if the serial port does not realy exist - i don't know the technical wording for this -, if the kernel detected the sio hardare, but it's not realy wired, then it the kernel will hang when getty will try to open it. danny OK good then its not just me, yes I haven't checked if the serial port is actually enabled in the bios, still I think its quite ordinary to have a machine basically fully hang up just because theres no active serial port. With no network or serial (unless you can enable/find it hardware side) I had to boot from the Freebsd install cdrom in fix it mode and mount the installed setup and revert the tty change. Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Patch: sym(4) VTOBUS FAILED panics on amd64, amd64/89550
Attached is a simpler patch, after some feedback from Stefan over general niceness. It removes the amd64 special case by splitting the target member (an array of struct sym_tcb) of sym_hcb out into a separately allocated structure. This way there is never a need to allocate anything bigger than a page and the whole problem goes away with minimal change, less wasted memory and fewer outright hacks. I did spend some time looking at ripping out the custom allocator entirely, and got as far as it building and one of the cache tests failing. I don't think I'm going to spend the time to track down why; if anyone wants to pick it up then let me know. Regards, Jan Mikkelsen sym_hipd.c-smaller-hcb.diff Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
