panic: semexit - semid not allocated in FreeBSD 6.3
Hi, I am using FreeBSD 6.3 amd64, I am getting the following crash semexit - semid not allocated cpuid = 7 Cannot dump. No dump device defined Sleeping thread (tid 101800, pid 4107) owns a non-sleepable lock It seems that this problem was reported and fixed in FreeBSD 7.1 http://lists.freebsd.org/pipermail/freebsd-hackers/2009-January/027317.html Is there any fix for FreeBSD 6.3? Thanks. Ibrahim ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Email sent from "at" command going to the wrong account
Hi, The "at" command sends an email with the output of the scheduled job. I've experienced inconsistent results when running jobs, receiving emails in accounts not associated with the user currently logged in. To reproduce in FreeBSD 7.2-RELEASE-p2 Case #1 login as user a (new shell through ssh) echo "echo 1" | at now --> user a will receive an email containing "1" - this is as expected Case #2 login as user a (new shell through ssh) login as user b exit echo "echo 1" | at now --> user b will receive an email containing "1" - this is not as expected, since I am user a again A look at the source for "at" reveals that "at" is getting the mailname from getlogin(). Running a small test program that outputs getlogin(), confirms the above behavior: A log-in and out of another account makes getlogin() return that account's name, even though the shell has been closed and we are back to the original shell and the original user a. Is this the intended behavior? Any hints would be appreciated. Best regards, Holger Kunst ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Email sent from "at" command going to the wrong account
On Mon, 14 Dec 2009, Holger Kunst wrote: Hi, The "at" command sends an email with the output of the scheduled job. I've experienced inconsistent results when running jobs, receiving emails in accounts not associated with the user currently logged in. To reproduce in FreeBSD 7.2-RELEASE-p2 Case #1 login as user a (new shell through ssh) echo "echo 1" | at now --> user a will receive an email containing "1" - this is as expected Case #2 login as user a (new shell through ssh) login as user b How are you accomplishing this? exit echo "echo 1" | at now --> user b will receive an email containing "1" - this is not as expected, since I am user a again A look at the source for "at" reveals that "at" is getting the mailname from getlogin(). Running a small test program that outputs getlogin(), confirms the above behavior: A log-in and out of another account makes getlogin() return that account's name, even though the shell has been closed and we are back to the original shell and the original user a. Is this the intended behavior? Any hints would be appreciated. -- Nate Eldredge n...@thatsmathematics.com ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Regarding enabling IOAPIC on Intel Dual core processor based boards having Broadcom controller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Ravi Shankar wrote: > Hi, > > We are using Freebsd6.2 bases OS on our LV 5200 Series Intel Dual Core Xeon > bases processor(Wolfdale-DP-ULV). In the carrier board hosting the processor > we have BCM5703 controller. > Currently we are using only one core in 32 bit mode and planning to use dual > core where we need to enable IOAPIC. When IOAPIC is not enabled I see the > bcm/bge driver is attached to IRQ10 and everything works fine, but when I > enable IOAPIC I still see the boot msgs show that bge is attached to irq10 > but the Broadcom controller does not come up. I found interrupt storm on > irq17 ( remember without IOAPIC enable there are not IRQ assignments beyond > IRQ16),looks like the controller is interrupting on 17 while driver waits on > 10. > > When I stop and loader and assign it manually using config command "set > hw.pci8.9.INTA.irq=”17”" , everything works fine. Would be great if some one > can throw some light on this IRQ mapping when IOAPIC is enabled and possible > fix ( Software or BIOS?) > > NOTE: Other devices ( Intel controller (em driver)) are working fine only > this BCM5703 is having issues with IOAPIC Is it possible for you to use some newer FreeBSD release, i.e. 6.3 or 6.4, or 7.x even 8.x and see if that would solve your problem? Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAksmj5sACgkQi+vbBBjt66AJvwCeJVlT301Ulu54C+UwvdNXjTxY KCkAn19OqPOpfeifzkRdf2zooRar9UrK =i1Dc -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
