Re: atacontrol commands fault at NForce4
On Tue, 23 Aug 2005, S?ren Schmidt wrote: SS> > [EMAIL PROTECTED]:/usr/src# atacontrol mode 0 SS> > atacontrol: Invalid device 0 SS> > SS> > the same for other channel-related commands such as SS> > SS> > [EMAIL PROTECTED]:/usr/src# atacontrol detach 1 SS> > atacontrol: Invalid channel 1 SS> > SS> SS> I miss the FreeBSD version, but if its recent you should "man atacontrol". SS> SS> quick hints: SS> atacontrol mode ad0 SS> atacontrol detach ata1 Yes, I miss these changes, possibly somewhere between ataNGII and ataNGIII (at least, between contemporary RELENG_5 and RELENG_6). Thanks, and sorry for the noise. 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]"
Re: USB camera
Kevin Oberman wrote: Date: Tue, 23 Aug 2005 17:36:21 +0300 From: Oleg Korecky <[EMAIL PROTECTED]> Sender: [EMAIL PROTECTED] Did sombody know how I able grab video stream from USB camera ? Sorry for my bad english! As of today, the only video input available for FreeBSD is a video capture card using bktr(4). Also you can grab video from Firewire devices, but not in realtime. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0-BETA3: 'kldunload linux' --> panic
On 8/23/05, Rene Ladan <[EMAIL PROTECTED]> wrote: > > On a i386 UP ? > CFLAGS=-O2 -pipe (should be safe) > Yes, my box is a x86 UP system, my CFLAGS=-O -pipe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
1024x768 in console
Hi, All! At first, sorry for my bad english ;) Does anybody know how to make 1024x768 (and 1280x1024) resolusion available in console (at 5.4-STABLE). I have tried some patches for CURRENT, but they didn't work. --- bio3k ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6024H-T / X6DHT-G / Marvell H2 SATA
fbsd wrote: Hello All, For 5.4, FreeBSD AMD64 (and i386) is not able to recognize my diamond-max 160G SATA drives on a Supermicro 6024H-T / X6DHT-G board with the default Marvell H2 SATA ctrl'r. There are SATA drivers for RH, FC3 and Windows from Supermicro: ftp://ftp.supermicro.com/driver/Diskimag/Adaptec/Marvell/H2/ Is there any way to get FreeBSD to run on this machine? It runs on windows so it does not appear to be hardware or BIOS config. It's a dual XEON (Nocona) 3.2G board with the Intel E7520 chipset. Thank you, Sejo Marvell does not release programming specs for their SATA chips, nor do they sell them for use as stand-along SATA controllers. The drivers that are on the Supermicro site are for Adaptec's software RAID solution that uses the Marvell chips. These drivers are binary only, unfortunately. It's a shame, because the Marvell chips are actually pretty good. My challenge for someone to reverse engineer them is still open. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /dev/midi and /dev/sequencer
On 8/24/05, Ben Paley <[EMAIL PROTECTED]> wrote: > Hello, > > I'm running 5.4-STABLE, cvsupped and everything rebuilt Mon Aug 22. > > Does anyone know what's happening with MIDI? I've got no /dev/midi > or /dev/sequencer and don't know if it's even possible to turn them on in the > kernel at the moment. > > I've also managed to compile and run Rosegarden-4 - it claims to work with > arts instead of ALSA but I'm not having any luck starting it with sequencer > or midi... any ideas? > > Thanks, > Ben There is slow work being done by one developer to reestablish midi. A set of patches was posted here for 5.4, and they aparently worked. I couldn't get them to compile on CURRENT, though. I was not able to locate a site on it, and the patch was posted to this list on Apr 26 by conrads(a)cox.net . He may be able to find you a later patch set from "Mat". ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6024H-T / X6DHT-G / Marvell H2 SATA
Hello All, For 5.4, FreeBSD AMD64 (and i386) is not able to recognize my diamond-max 160G SATA drives on a Supermicro 6024H-T / X6DHT-G board with the default Marvell H2 SATA ctrl'r. There are SATA drivers for RH, FC3 and Windows from Supermicro: ftp://ftp.supermicro.com/driver/Diskimag/Adaptec/Marvell/H2/ Is there any way to get FreeBSD to run on this machine? It runs on windows so it does not appear to be hardware or BIOS config. It's a dual XEON (Nocona) 3.2G board with the Intel E7520 chipset. Thank you, Sejo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
if_bridge for 5-STABLE ready for testing
Hi, You can find the patch here http://people.freebsd.org/~thompsa/if_bridge-5stable.diff 1) Apply the patch # cd /usr; patch -p0 < if_bridge-5stable.diff 2) Add 'device if_bridge' to your kernel config (or use the module) 3) Do the "buildworld, buildkernel, installkernel, installworld"-dance Feel free to test and report any problems. configuration is the same as in current, see if_bridge(4) for details. cheers, Andrew ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0-BETA3: 'kldunload linux' --> panic
On Tue, Aug 23, 2005 at 05:07:14PM -0700, Iva Hesy wrote: > On 8/23/05, Rene Ladan <[EMAIL PROTECTED]> wrote: > > The following panic can reliably be reproduced on a GENERIC 6.0-BETA3 > > kernel when loading linux support via /etc/rc.conf (linux_enable="YES") > > and then issuing "kldunload linux". > > > No, I have a BETA3 box too, and can unload linux kernel module after > booting with linux_enable="YES"... On a i386 UP ? CFLAGS=-O2 -pipe (should be safe) Rene -- GPG fingerprint = 5FFA 3959 3377 C697 8428 24D0 BF3E F4A9 AE33 5DCC "It won't fit on the line." -- me, 2001 pgpcBTHmJY9Ok.pgp Description: PGP signature
Re: 6.0-BETA3: 'kldunload linux' --> panic
On 8/23/05, Rene Ladan <[EMAIL PROTECTED]> wrote: > The following panic can reliably be reproduced on a GENERIC 6.0-BETA3 > kernel when loading linux support via /etc/rc.conf (linux_enable="YES") > and then issuing "kldunload linux". > No, I have a BETA3 box too, and can unload linux kernel module after booting with linux_enable="YES"... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
new 6.0BETA2 lors
Hi, I've stumbled over some new LORs with 6.0BETA2 (attached). They are still relevant. Regards, Rene -- GPG fingerprint = 5FFA 3959 3377 C697 8428 24D0 BF3E F4A9 AE33 5DCC "It won't fit on the line." -- me, 2001 lock order reversal -- NEW 1st 0xc0760d00 Giant (Giant) @ /usr/src/sys/fs/devfs/devfs_vnops.c:1435 2nd 0xc14ee018 fxp0 (network driver) @ /usr/src/sys/dev/fxp/if_fxp.c:1187 KDB: stack backtrace: kdb_backtrace(c06ff483,c14ee018,c14c9450,c06ecd3d,c06ed001) at 0xc055997e = kdb_backtrace+0x2e witness_checkorder(c14ee018,9,c06ed001,4a3,c07057aa) at 0xc0566033 = witness_checkorder+0x6c3 _mtx_lock_flags(c14ee018,0,c06ed001,4a3,c14ecc00) at 0xc053120a = _mtx_lock_flags+0x8a fxp_start(c14ecc00,12b,0,c14ecc00) at 0xc0486d94 = fxp_start+0x34 if_start(c14ecc00,0,c07057aa,195,3) at 0xc05bd419 = if_start+0x99 ether_output_frame(c14ecc00,c1547900,6,cefe8bc4,c1547900) at 0xc05bec68 = ether_output_frame+0x218 ether_output(c14ecc00,c1547900,cefe8c0c,0,cefe8c0c) at 0xc05bea3e = ether_output+0x47e bpfwrite(c1d3e100,c21a2b00,0,59b,c1d3e100) at 0xc05b6f9f = bpfwrite+0xef devfs_write_f(c1640678,c21a2b00,c1627a80,0,c1c63300) at 0xc04e8184 = devfs_write_f+0xd4 dofilewrite(c1c63300,7,c1640678,c21a2b00,) at 0xc0568655 = dofilewrite+0x85 kern_writev(c1c63300,7,c21a2b00,c21a2b00,0) at 0xc0568475 = kern_writev+0x65 writev(c1c63300,cefe8d04,c,422,3) at 0xc05683e6 = writev+0x46 syscall(3b,3b,3b,bfbfecdc,bfbfee40) at 0xc06ba190 = syscall+0x2c0 Xint0x80_syscall() at 0xc06a6ebf = Xint0x80_syscall+0x1f --- syscall (121, FreeBSD ELF32, writev), eip = 0x280cbe6f, esp = 0xbfbfecac, ebp = 0xbfbfee08 --- lock order reversal -- NEW 1st 0xc07ad1c0 ifnet (ifnet) @ /usr/src/sys/net/if.c:1188 2nd 0xc14dfb44 ral0 (network driver) @ /usr/src/sys/dev/ral/if_ral.c:2128 KDB: stack backtrace: kdb_backtrace(c06ff483,c14dfb44,c15a9280,c06ecd3d,c06f0be1) at 0xc055997e = kdb_backtrace+0x2e witness_checkorder(c14dfb44,9,c06f0be1,850,c076f278) at 0xc0566033 = witness_checkorder+0x6c3 _mtx_lock_flags(c14dfb44,0,c06f0be1,850,c14dfb44) at 0xc053120a = _mtx_lock_flags+0x8a ral_watchdog(c15b3000,0,c0705351,4a4,c0760d00) at 0xc04b9040 = ral_watchdog+0x40 if_slowtimo(0,0,c06fca75,107,c05bb500) at 0xc05bb567 = if_slowtimo+0x67 softclock(0,0,c06f8fdd,251,ca6a9d00) at 0xc054a23e = softclock+0x24e ithread_loop(c13e4400,ca6a9d38,c06f8dd4,30d,0) at 0xc0523832 = ithread_loop+0x162 fork_exit(c05236d0,c13e4400,ca6a9d38) at 0xc0522871 = fork_exit+0xc1 fork_trampoline() at 0xc06a6ecc = fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xca6a9d6c, ebp = 0 --- lock order reversal -- NEW 1st 0xc2261900 inp (rawinp) @ /usr/src/sys/netinet/raw_ip.c:286 2nd 0xc14ee018 fxp0 (network driver) @ /usr/src/sys/dev/fxp/if_fxp.c:1187 KDB: stack backtrace: kdb_backtrace(c06ff483,c14ee018,c14c9450,c06ecd3d,c06ed001) at 0xc055997e = kdb_backtrace+0x2e witness_checkorder(c14ee018,9,c06ed001,4a3,c07057aa) at 0xc0566033 = witness_checkorder+0x6c3 _mtx_lock_flags(c14ee018,0,c06ed001,4a3,c14ecc00) at 0xc053120a = _mtx_lock_flags+0x8a fxp_start(c14ecc00,12b,0,c14ecc00) at 0xc0486d94 = fxp_start+0x34 if_start(c14ecc00,0,c07057aa,195,2) at 0xc05bd419 = if_start+0x99 ether_output_frame(c14ecc00,c1a5a400,6,c14f4d90,cf16aabc) at 0xc05bec68 = ether_output_frame+0x218 ether_output(c14ecc00,c1a5a400,c14f4d90,c22594a4,c05660e6) at 0xc05bea3e = ether_output+0x47e ip_output(c1a5a400,0,cf16ab1c,22,0) at 0xc05e90f7 = ip_output+0x7d7 rip_output(c1a5a400,c19752c8,7032742,300,c1a5a400) at 0xc05eb565 = rip_output+0x315 rip_send(c19752c8,0,c1a5a400,c15a94b0,0) at 0xc05ec3b3 = rip_send+0xd3 sosend(c19752c8,c15a94b0,cf16ac34,c1a5a400,0) at 0xc05832b1 = sosend+0x701 kern_sendit(c1c9f300,4,cf16acb4,0,0) at 0xc0589b7f = kern_sendit+0x13f sendit(c1c9f300,4,cf16acb4,0,905643c) at 0xc0589a09 = sendit+0x1a9 sendto(c1c9f300,cf16ad04,18,422,6) at 0xc0589d0b = sendto+0x5b syscall(8f5003b,3b,bfbf003b,bfbfac00,1c) at 0xc06ba190 = syscall+0x2c0 Xint0x80_syscall() at 0xc06a6ebf = Xint0x80_syscall+0x1f --- syscall (133, FreeBSD ELF32, sendto), eip = 0x2837fd4f, esp = 0xbfbfab8c, ebp = 0xbfbfabc8 --- pgpIUCwlINNRU.pgp Description: PGP signature
Re: RELEASE to STABLE upgrade, ports problem
Uhhh, nevermind. A quick ipfw list told me what the "problem" was. Thank you all for resisting the urge to bash/flame/berate me. It's been awhile since I've built a new machine. Kinda forgot all the nuances. Kevin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RELEASE to STABLE upgrade, ports problem
I just updated from 5.4-RELEASE to 5.4-STABLE last night. Now, when I try to build from ports, it tries to fetch the file, and the ftp server returns: "Forbidden". It does the same thing when I tried "make fetchindex" in /usr/ports. I think I've seen this in the past, but can't remember where, or the fix. Any help would be greatly appreciated. -- Kevin Glick ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB camera
> Date: Tue, 23 Aug 2005 17:36:21 +0300 > From: Oleg Korecky <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > >Did sombody know how I able grab video stream from USB camera ? > >Sorry for my bad english! Far better than my Russian! I'm afraid FreeBSD currently lacks support for USB video devices. There has been discussion of both porting V4L to BSD or creating a BSD video system, but I have yet to see any indication of when or if either will actually be available. As of today, the only video input available for FreeBSD is a video capture card using bktr(4). These devices are fairly inexpensive (at leat in the US) at about $25. Less on ebay. But you then need a camera offering composite video out and these can be a bit harder to come by. -- 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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
thanks for commiting (MFC ffs_softdep.c 1.182, softdep.h 1.18) to RELENG_5 and 6. When in 4?
Hello! Would some kind soul MFC ffs_softdep.c 1.182, softdep.h 1.18 into RELENG_4 as well? This bug is also present in FreeBSD 4.x. Found it ever since 4.7. Thanks in advance. Toma ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atacontrol commands fault at NForce4
On 23/08/2005, at 19:19, Dmitry Morozovsky wrote: Hi there Soeren, using parallel ATA drive at our new TYAN motherboard I see [EMAIL PROTECTED]:/usr/src# atacontrol mode 0 atacontrol: Invalid device 0 the same for other channel-related commands such as [EMAIL PROTECTED]:/usr/src# atacontrol detach 1 atacontrol: Invalid channel 1 I miss the FreeBSD version, but if its recent you should "man atacontrol". quick hints: atacontrol mode ad0 atacontrol detach ata1 - 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: /dev/midi and /dev/sequencer
On Tue, Aug 23, 2005 at 12:47:36PM -0400, Dan Ponte wrote: > On Tue, Aug 23, 2005 at 04:59:39PM +0100, Ben Paley <[EMAIL PROTECTED]> was > witnessed plotting the following conspiracy: > > Hello, > > > > I'm running 5.4-STABLE, cvsupped and everything rebuilt Mon Aug 22. > > > > Does anyone know what's happening with MIDI? I've got no /dev/midi > > or /dev/sequencer and don't know if it's even possible to turn them on in > > the > > kernel at the moment. > > > > I've also managed to compile and run Rosegarden-4 - it claims to work with > > arts instead of ALSA but I'm not having any luck starting it with sequencer > > or midi... any ideas? > > > > Thanks, > > Ben > As of now, FreeBSD has no support for MIDI. We once had it, but not > anymore. > -Dan > -- > Dan Ponte > http://www.theamigan.net/ > When a fly lands on the ceiling, does it do a half roll or a half > loop? You can try Eric A. Welsh's set of Gravis Ultrasound MIDI patches (/usr/ports/audio/eawpats) which pulls in Timidity++. This way you have at least software MIDI playback. The patchset sounds quite good (better than the native MIDI of my sound card). Regards, Rene -- GPG fingerprint = 5FFA 3959 3377 C697 8428 24D0 BF3E F4A9 AE33 5DCC "It won't fit on the line." -- me, 2001 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
atacontrol commands fault at NForce4
Hi there Soeren, using parallel ATA drive at our new TYAN motherboard I see [EMAIL PROTECTED]:/usr/src# atacontrol mode 0 atacontrol: Invalid device 0 the same for other channel-related commands such as [EMAIL PROTECTED]:/usr/src# atacontrol detach 1 atacontrol: Invalid channel 1 additional info: [EMAIL PROTECTED]:/usr/src# grep ata /var/run/dmesg.boot atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe800-0xe80f at device 6.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd400-0xd40f mem 0xfebfc000-0xfebfcfff irq 21 at device 7.0 on pci0 ata2: on atapci1 ata3: on atapci1 atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc000-0xc00f mem 0xfebfb000-0xfebfbfff irq 22 at device 8.0 on pci0 ata4: on atapci2 ata5: on atapci2 ad0: 76319MB at ata0-master UDMA100 [EMAIL PROTECTED]:/usr/src# uname -a FreeBSD gwhy.rinet.ru 6.0-BETA3 FreeBSD 6.0-BETA3 #0: Mon Aug 22 10:50:05 MSD 2005 [EMAIL PROTECTED]:/usr/obj/lh/src/sys/GWH_AMD64 amd64 [EMAIL PROTECTED]:/usr/src# atacontrol list ATA channel 0: Master: ad0 ATA/ATAPI revision 5 Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: no device present Slave: no device present ATA channel 3: Master: no device present Slave: no device present ATA channel 4: Master: no device present Slave: no device present ATA channel 5: Master: no device present Slave: no device present 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]"
Re: /dev/midi and /dev/sequencer
On Tue, Aug 23, 2005 at 04:59:39PM +0100, Ben Paley <[EMAIL PROTECTED]> was witnessed plotting the following conspiracy: > Hello, > > I'm running 5.4-STABLE, cvsupped and everything rebuilt Mon Aug 22. > > Does anyone know what's happening with MIDI? I've got no /dev/midi > or /dev/sequencer and don't know if it's even possible to turn them on in the > kernel at the moment. > > I've also managed to compile and run Rosegarden-4 - it claims to work with > arts instead of ALSA but I'm not having any luck starting it with sequencer > or midi... any ideas? > > Thanks, > Ben As of now, FreeBSD has no support for MIDI. We once had it, but not anymore. -Dan -- Dan Ponte http://www.theamigan.net/ When a fly lands on the ceiling, does it do a half roll or a half loop? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/dev/midi and /dev/sequencer
Hello, I'm running 5.4-STABLE, cvsupped and everything rebuilt Mon Aug 22. Does anyone know what's happening with MIDI? I've got no /dev/midi or /dev/sequencer and don't know if it's even possible to turn them on in the kernel at the moment. I've also managed to compile and run Rosegarden-4 - it claims to work with arts instead of ALSA but I'm not having any luck starting it with sequencer or midi... any ideas? Thanks, Ben ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Firewire + 5-STABLE + devd?
On Tue, 2005-08-23 at 11:18 -0400, Christopher Sean Hilton wrote: > On Tue, Aug 23, 2005 at 07:58:56AM -0400, Christopher Sean Hilton wrote: > > Hi, > > > > I'm trying to get my hotplug utility, which works well with usb > > devices, to work with firewire devices under 5-STABLE. But when I devd > > doesn't seem to do anything with firewire devices and when I cat > > /dev/devctl I get get nothing on firewire. Is there a sysctl I can > > tune or do I need to upgrade to the 6-{RELEASE,CURRENT} branch? > > > > Also, will devd generate events for the attachment of a da[0-9] > device? No. Unfortunately, CAM is not newbus-ified, and thus will not send devctl events. ATA disks will in 6.X and higher, though. > Right now it seems as though it doesn't and that is > problematic. The issue is this. If I attach my usb pendrive to my > computer it gets devices umass0 and da0. But if I attach a firewire > device first then my usb pendrive is umass0, da1. So, if events aren't > generated to say that da1 has become available then I have to figure > out what umass0 is connected to. Yep. You should be able to work backwards through the CAM subsystem to obtain this information. Take a look at the output of ``camcontrol devlist -v''. The information is there, and you can use libcam to get it. Joe > > Thanks in advance > Chris > -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Firewire + 5-STABLE + devd?
On Tue, Aug 23, 2005 at 07:58:56AM -0400, Christopher Sean Hilton wrote: > Hi, > > I'm trying to get my hotplug utility, which works well with usb > devices, to work with firewire devices under 5-STABLE. But when I devd > doesn't seem to do anything with firewire devices and when I cat > /dev/devctl I get get nothing on firewire. Is there a sysctl I can > tune or do I need to upgrade to the 6-{RELEASE,CURRENT} branch? > Also, will devd generate events for the attachment of a da[0-9] device? Right now it seems as though it doesn't and that is problematic. The issue is this. If I attach my usb pendrive to my computer it gets devices umass0 and da0. But if I attach a firewire device first then my usb pendrive is umass0, da1. So, if events aren't generated to say that da1 has become available then I have to figure out what umass0 is connected to. Thanks in advance Chris -- Chris Hilton chris-at-vindaloo-dot-com "All I was doing was trying to get home from work!" -- Rosa Parks pgpaTSPO5LWaJ.pgp Description: PGP signature
USB camera
Did sombody know how I able grab video stream from USB camera ? Sorry for my bad english! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BTX failure [Was: Re: pxeboot problems with BETA2]
Am Mittwoch, 17. August 2005 21:29 CEST schrieb John Baldwin: > On Wednesday 17 August 2005 10:43 am, Emanuel Strobl wrote: > > Am Dienstag, 16. August 2005 19:52 CEST schrieb Brooks Davis: > > > On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote: > > > > Hello, > > > > > > > > I just wanted to ask if somebody had success with providing pxe > > > > boot service under 6-BETA2. > > > > I have two clients, one NET4501 wich just reboots after fetching > > > > pxeldr via TFTP and a Laptop which just hangs when NFS-loading > > > > kernel. > > > > > > > > I'm about to investigate further, but maybe someone can confirm > > > > that in general PXE booting with BETA2 is working... Or not... > > > > > > I'm PXE booting systems with RELENG_6 as of 7/27. I'll probably do > > > an update some time this week. > > > > Ok, I read som files and found -DBTX_SERIAL. This gives me the > > following dump before the box reboots: > > uilding the boot loader arguments > > Relocating the loader and the BTX > > Starting the BTX loader > > > > int=0006 err= efl=00010202 eip=00023c21 > > eax= ebx=000384e0 ecx=000384e0 edx=0001 > > esi=1000 edi=0029 ebp=00086770 esp=00086758 > > cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 > > cs:eip=0f 4f c2 a3 c8 7d 03 00-8d 41 0c c7 41 04 fd 44 > >ff 55 89 39 c6 44 39 ff-fe 83 c4 0c 5b 5e 5f 5d > > ss:esp=b4 7d 03 00 29 00 00 00-00 10 00 00 00 00 00 00 > >83 57 02 00 02 00 00 00-a0 67 08 00 98 1c 02 00 > > BTX halted > > > > Any clue? Regarding cvsweb nothing changed recently, and I had net4501 > > boxes pxebooting fine with FreeBSD 5.3. > > Hmm. Int 6 is an invalid opcode exception: I have no ideay why, but over night I recompiled my PXEROOT system (BETA3 now) and the problem vanished. I can't see any changes in the cvsweb, so I have absolutely no idea what the problem was. Hardware is exactly the same. What have I missed? Thanks, -Harry > > 0F4FC2cmovg eax,edx > 0003 A3C87D0300mov [0x37dc8],eax > 0008 8D410Clea eax,[ecx+0xc] > 000B C74104FD44FF55mov dword [ecx+0x4],0x55ff44fd > 0012 8939 mov [ecx],edi > 0014 C64439FFFEmov byte [ecx+edi-0x1],0xfe > 0019 83C40Cadd esp,byte +0xc > 001C 5Bpop ebx > 001D 5Epop esi > 001E 5Fpop edi > 001F 5Dpop ebp > > I'm guessing that there's been a stack overflow or some such. Your eip > is in the loader. You can try using the loader.sym from your loader > binary to look up that eip address. In the loader here on my laptop > it's in the write function: > > % nm /usr/obj/usr/src/sys/boot/i386/loader/loader.sym | sort > ... > 00023b9c T readdirfd > 00023c14 T write > 00023d18 T lseek > > If you want to be able to use gdb, then rebuild libstand with debugging > (make DEBUG_FLAGS=-g) and rebuild all of /sys/boot with debugging (make > DEBUG_FLAGS=-g). You can then > use /usr/obj/usr/src/sys/boot/i386/pxeldr/pxeboot for your pxeboot and > you can run gdb on /usr/obj/usr/src/sys/boot/i386/loader/loader.sym and > you can do listings of the addresses for eip, etc. pgpj0zK68sjPU.pgp Description: PGP signature
calcru: runtime went backwards and hard lockup in 5.4-STABLE
hey folks.. Im running on a compaq proliant dual 733Mhz computer with 1 gig o memory.. I was running 5.4-STABLE a few weeks ago with no problem.. I did a make world about a week ago, and now I see lots of messages in syslog.. Aug 22 17:20:40 monsterjam kernel: calcru: runtime went backwards from 77810370 usec to 77203 321 usec for pid 48 (swi5: clock sio) Aug 22 17:20:40 monsterjam kernel: calcru: runtime went backwards from 17036511 usec to 16595 708 usec for pid 71 (schedcpu) Aug 22 17:20:40 monsterjam kernel: calcru: runtime went backwards from 77810370 usec to 77203 365 usec for pid 48 (swi5: clock sio) Aug 22 17:20:40 monsterjam kernel: calcru: runtime went backwards from 17036511 usec to 16595 708 usec for pid 71 (schedcpu) Aug 22 17:20:40 monsterjam kernel: calcru: runtime went backwards from 77810370 usec to 77203 463 usec for pid 48 (swi5: clock sio) and I see http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#CALCRU-NEGATIVE but this info seems to only apply to 4.x. Is this really a problem? how can I squelch it? the other reason I ask is because ive had 2 HARD lockups since upgrading. I have since compiled a debugging kernel.. (in my kernel config) makeoptionsDEBUG=-g options GDB options DDB options KDB (this look right?) I have a serial connection hooked up to this server and I cannot even break into the debugger when it hangs. regards, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6.0-BETA3: 'kldunload linux' --> panic
The following panic can reliably be reproduced on a GENERIC 6.0-BETA3 kernel when loading linux support via /etc/rc.conf (linux_enable="YES") and then issuing "kldunload linux". I'll leave the crash dump around. % kgdb -n 95 [...] Unread portion of the kernel message buffer: panic: witness_destroy: lock (sleep mutex) linux osname is not initialized cpuid = 0 KDB: enter: panic Dumping 191 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 191MB (48880 pages) 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt f #0 doadump () at pcpu.h:165 No locals. #1 0xc0475ae6 in db_fncall (dummy1=0, dummy2=0, dummy3=1999, dummy4=0xcf021a38 "\200Ø\235À") at /usr/src/sys/ddb/db_command.c:489 fn_addr = -1066784304 args = {0, -821945852, -1064888387, -1062909536, 28, -821945852, -1069058507, 32, -1063899200, 2} nargs = 0 retval = 547703424 t = 0 #2 0xc0475862 in db_command (last_cmdp=0xc09dcf84, cmd_table=0x0, aux_cmd_tablep=0xc095a0c0, aux_cmd_tablep_end=0xc095a0dc) at /usr/src/sys/ddb/db_command.c:349 cmd = (struct command *) 0xc0963140 t = 0 modif = "\200Ø\235À\000\000\000\000T\032\002Ï\r\000\000\000à\034§À\r\000\000\000\001\000\000\000t\032\002ÏÆæ\211À I¥À\aK\000 d\035§À\000_€À\200Ø\235Àx\000\000\000\200Ø\235À\000\000\000\000\230\032\002Ï1\177GÀbê\222À°{GÀ\000\000\000\000\020\000\000\000\000\000\000\000\200Ø\235ÀÆqGÀ\200Ø\235À8Ð\235Àx\000\000\000ü\032\002Ï" addr = 0 count = 1999 have_addr = 0 result = 0 #3 0xc0475975 in db_command_loop () at /usr/src/sys/ddb/db_command.c:455 No locals. #4 0xc0477ae5 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_main.c:221 jb = {{_jb = {-821945604, -821945632, -821945552, 1, 0, -1069057402, 0, 0, 0, 0, -821945552, -1066657536}}} prev_jb = (void *) 0x0 bkpt = 0 #5 0xc06c19ae in kdb_trap (type=0, code=0, tf=0xcf021b98) at /usr/src/sys/kern/subr_kdb.c:473 did_stop_cpus = 1 handled = -821945448 #6 0xc08c2468 in trap (frame= {tf_fs = 8, tf_es = 40, tf_ds = -821952472, tf_edi = 256, tf_esi = 1, tf_ebp = -821945376, tf_isp = -821945404, tf_ebx = -821945316, tf_edx = 0, tf_ecx = -1056755712, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1066658176, tf_cs = 32, tf_eflags = 646, tf_esp = -1064104898, tf_ss = -1064113900}) at /usr/src/sys/i386/i386/trap.c:601 td = (struct thread *) 0xc24db300 p = (struct proc *) 0xc24fc830 sticks = 3473021836 i = 0 ucode = 0 type = 3 code = 0 eva = 0 #7 0xc08ac43a in calltrap () at /usr/src/sys/i386/i386/exception.s:139 No locals. #8 0x0008 in ?? () No symbol table info available. #9 0x0028 in ?? () No symbol table info available. #10 0xcf020028 in ?? () No symbol table info available. #11 0x0100 in ?? () No symbol table info available. #12 0x0001 in ?? () No symbol table info available. #13 0xcf021be0 in ?? () No symbol table info available. #14 0xcf021bc4 in ?? () No symbol table info available. #15 0xcf021c1c in ?? () No symbol table info available. #16 0x in ?? () No symbol table info available. #17 0xc1033000 in ?? () No symbol table info available. #18 0x0012 in ?? () No symbol table info available. #19 0x0003 in ?? () No symbol table info available. #20 0x in ?? () No symbol table info available. #21 0xc06c1680 in kdb_enter (msg=0x0) at cpufunc.h:60 No locals. #22 0xc06a337e in panic (fmt=0xc09323ad "%s: lock (%s) %s is not initialized") at /usr/src/sys/kern/kern_shutdown.c:537 td = (struct thread *) 0xc24db300 bootopt = 256 newpanic = 1 ap = 0xcf021c1c "µ}\216Àè\232\224ÀþÈ2ÂÀæ2Â\020Î2ÂL\034\002ÏX\230iÀÀæ2ÂíÈ\222À" buf = "witness_destroy: lock (sleep mutex) linux osname is not initialized", '\0' #23 0xc06cd5a9 in witness_destroy (lock=0xc232e6c0) at /usr/src/sys/kern/subr_witness.c:567 w = (struct witness *) 0xc232e6c0 __func__ = "witness_destroy" #24 0xc0699858 in mtx_destroy (m=0xc232e6c0) at /usr/src/sys/kern/kern_mutex.c:875 No locals. #25 0xc0691b60 in linker_file_sysuninit (lf=0x0) at /usr/src/sys/kern/kern_linker.c:238 start = (struct sysinit **) 0xc232ce10 stop = (struct sysinit **) 0xc232ce18 sipp = (struct sysinit **) 0xc232ce10 xipp = (struct sysinit **) 0x0 save = (struct sysinit *) 0x0 #26 0xc0692384 in linker_file_unload (file=0xc222eb00, flags=0) at /usr/src/sys/kern/kern_linker.c:539 mod = 0x0 next = 0x0 ml = 0x0 nextml = 0x0 cp = (struct common_symbol *) 0x0 error = 0 i = 0 #27 0xc0692c3a in kern_kldunload (td=0xc222eb00, fileid=0, flags=0) at /usr/src/sys/kern/kern_linker.c:828 lf = 0xc222eb00 error = 2 #28 0xc0692cdc in kldunloadf (td=0x0, uap=0x0) at /
Firewire + 5-STABLE + devd?
Hi, I'm trying to get my hotplug utility, which works well with usb devices, to work with firewire devices under 5-STABLE. But when I devd doesn't seem to do anything with firewire devices and when I cat /dev/devctl I get get nothing on firewire. Is there a sysctl I can tune or do I need to upgrade to the 6-{RELEASE,CURRENT} branch? $ uname -a FreeBSD endaba.vindaloo.com 5.4-STABLE FreeBSD 5.4-STABLE #0: \ Thu Jun 9 16:25:22 EDT 2005 \ [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENDABA i386 Thanks in advance Chris -- Chris Hilton chris-at-vindaloo-dot-com "All I was doing was trying to get home from work!" -- Rosa Parks pgp5IP9nRY6Qh.pgp Description: PGP signature
Re: Install from USB flash drive? Sort of...
Brandon Fosdick <[EMAIL PROTECTED]> wrote: > So I had this "brilliant" idea that I was going to install FreeBSD > on my new amd64 system using a 512MB flash drive since I didn't feel > like digging out a CD-ROM. I ended up installing from CD anyway, but > I thought I'd share my experience in case anyone else knows how to do > this. > [...] > The next morning it occured to me that I probably could have just > copied the files from an install CD. Right. Or from an FTP site. > [...] > Determined to press on I tried the "install from existing file > system" option, w hich I had never noticed before. That didn't work > since I had no idea what path to give it, or even if the flash drive > had been mounted. It depends on the FreeBSD version. Older versions mounted it on /dist, if I remember correctly, but newer ones mount it directly on /. > Thinking that maybe I had built a bad release I decided to try > copying from the disc1 iso. The iso is listed at 515MB which is > almost small enough. The packages are about 70MB and they're not > strictly necessary so I thought it would work. So I mounted the iso > and proceeded to copy the files out, since iso's mount read only and > I needed to delete stuff. You can copy directly from the ISO to your flash drive, excluding the things that you don't need (i.e. packages). There's no need to make an additional copy on your HD. For example: # cd /cdrom; find . | grep -v /packages | cpio -dump /flash > To my surprise it turned into 1.1GB when copied onto a "real" > filesystem. Obviously that's a problem. Depends on how you copy things. Using cp(1) for recursive copies is almost always a bad idea, because you will get duplicates of all hardlinked files. That's why your copy grew to 1.1GB. For recursive copies, use cpio, tar, pax, cpdup or similar tools. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "C++ is over-complicated nonsense. And Bjorn Shoestrap's book a danger to public health. I tried reading it once, I was in recovery for months." -- Cliff Sarginson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: polling in 4.11 vs 5.4
> I hope this is the right place that I post to! > > > > When I enabled polling in 5.4 and 4.11, I found that CPU load > in 5.4 is much higher than 4.11. For example, suppose HZ is 5000, in 5.4 > the idle CPU is about 87%, but in 4.11, the idle CPU is about 99.9%. Is > this right? Or the statistic is wrong in 4.11? > > BTW, ACPI is disabled under 5.4. > > BTW, I found that context switch in 5.4 is much higher than 5.4 while > enabling polling. (Using systat -vmstat 1) > > I'm looking forward your reply. The polling code hasn't been changed since 4.11. I've posted a patch to resolve giant lock issue in it, but it wasn't merged. I don't have enough time by now to rewrite it according the opinions mentioned. But the cost of context switch is definitely higher on 5.x HZ == 5000 is too much i think. 1000 is quite enough for network-intensive applications. > > Any response is welcome! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"