Re: Wrong date for DEVFS entries
On Thu, 6 Feb 2003, Andrey A. Chernov wrote: > On Wed, Feb 05, 2003 at 23:44:08 +0100, [EMAIL PROTECTED] wrote: > > > > >2) Feb 6 01:36 (boot time) > > >3) Feb 6 04:36 (+3 TZ future jump) > > > > These timestamps have been touched, and the clock has made a 3 hour > > jump either forward or backward at some point. > > > > The problem is the clock jump, not DEVFS. > > Clock jump happens as it supposed when adjkerntz(8) corrects machine clock > back to GMT via various CPU_* sysctl's. Could touched DEVFS stamps be > fixed back to something useful in the same sysctl code too? This should be well known to devfs users. devfs sets at least some of the times before adjkerntz can run, and nothing fixes them, so these times are wrong by the timezone difference. The problem is more obvious East of Europe since the timezone difference is positive and large. The bug has less noticable effects West of Greenwich since the difference is negative so the wrong timestamps are in the past. For me the difference is +10 or +11 hours so there is a 10 or 11 hour window after booting in which `ls -l /dev' and some periodic scripts report strangeness. There are related problems for boottime. These are hacked around in tc_setclock() by adjusting boottime when the time is changed. This works right when the time is changed soon after booting by adjkerntz or ntpdate but wrong after that. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Wrong date for DEVFS entries
In message <[EMAIL PROTECTED]>, Bruce Evans writes: >On Thu, 6 Feb 2003, Andrey A. Chernov wrote: > >> On Wed, Feb 05, 2003 at 23:44:08 +0100, [EMAIL PROTECTED] wrote: >> > >> > >2) Feb 6 01:36 (boot time) >> > >3) Feb 6 04:36 (+3 TZ future jump) >> > >> > These timestamps have been touched, and the clock has made a 3 hour >> > jump either forward or backward at some point. >> > >> > The problem is the clock jump, not DEVFS. >> >> Clock jump happens as it supposed when adjkerntz(8) corrects machine clock >> back to GMT via various CPU_* sysctl's. Could touched DEVFS stamps be >> fixed back to something useful in the same sysctl code too? > >This should be well known to devfs users. > >devfs sets at least some of the times before adjkerntz can run, and nothing >fixes them, so these times are wrong by the timezone difference. This is not any different from any other filesystem. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Wrong date for DEVFS entries
On Thu, Feb 06, 2003 at 11:27:36 +0100, [EMAIL PROTECTED] wrote: > In message <[EMAIL PROTECTED]>, Bruce Evans writes: > >On Thu, 6 Feb 2003, Andrey A. Chernov wrote: > > > >> On Wed, Feb 05, 2003 at 23:44:08 +0100, [EMAIL PROTECTED] wrote: > >> > > >> > >2) Feb 6 01:36 (boot time) > >> > >3) Feb 6 04:36 (+3 TZ future jump) > >> > > >> > These timestamps have been touched, and the clock has made a 3 hour > >> > jump either forward or backward at some point. > >> > > >> > The problem is the clock jump, not DEVFS. > >> > >> Clock jump happens as it supposed when adjkerntz(8) corrects machine clock > >> back to GMT via various CPU_* sysctl's. Could touched DEVFS stamps be > >> fixed back to something useful in the same sysctl code too? > > > >This should be well known to devfs users. > > > >devfs sets at least some of the times before adjkerntz can run, and nothing > >fixes them, so these times are wrong by the timezone difference. > > This is not any different from any other filesystem. No, it IS different - no real filesystems mounted at this point yet, so no real timestamps damaged. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Wrong date for DEVFS entries
In message <[EMAIL PROTECTED]>, "Andrey A. Chernov" writes:
>> This is not any different from any other filesystem.
>
>No, it IS different - no real filesystems mounted at this point yet, so no
>real timestamps damaged.
Think diskless NFS, think MD(4) based root, think...
The only problem is that we set the kernel time wrong from the RTC.
We should stop doing that, rather than invent bandaids and hacks to
restore the damage it does.
I avoid it entirely by using UTC time in my RTC, but this is not an
option for machines which have to boot broken-as-designed OSs.
The most practical way to do it right would be to have adjkerntz
update a file under /boot/ ("/boot/timezone.hint") which the loader
reads in and passes to the kernel, so that the kernel can set the
time right from the RTC based on that. This doesn't work well for
machines which are turned off for long periods of time unless the
file contains predicted DST transitions for the next year or so.
The most correct solution would be for the loader (preferably) or
the kernel to know about timezones, including DST, so that it
would also work correct for a machine which has been powered off
for half a year. (I'd prefer the loader because we don't need
this code once userland can take over.)
I don't know if modern bios's know about timezones and DST, I've
seen some that has setup functions for it, but I don't know
if there is any way to find the information they store and I don't
think such features are widespread.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
X compilation problems
Hello,
I trully suspect that for some reason this is specific to my box, but
I'm not quite sure if it is nor why it is. I hope this is the
appropriated place to ask, and if I'm mistaken, please correct me.
Since the last port update for XFree86-libraries, I've been unable to
get that port (x11/XFree86-4-libraries) compiled. I insistently get this
error:
cc -c -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../include
-I/usr/ports/x11/XFree86-4-libraries/work/xc/include
-I/usr/ports/x11/XFree86-4-libraries/work/xc/include/GL
-I/usr/ports/x11/XFree86-4-libraries/work/xc
-I/usr/ports/x11/XFree86-4-libraries/work/xc/exports/include -DCSRG_BASED
-DFUNCPROTO=15 -DNARROWPROTO -DNDEBUG -O2 -pipe -march=k6-2 mipmap.c -o
unshared/mipmap.o
{standard input}: Assembler messages:
{standard input}:7683: Error: value of -129 too large for field of 1 bytes at 20035
*** Error code 1
I'm running 5.0-CURRENT built yesterday (02/06), but I have seen this
happening since the update from revision 5 to 6 of the port (I'm not
sure about the exact date, but I think it happened about a week or so
ago.) Has anyone seen this? How do I fix it?
Thanks,
Fred
--
"A truly wise woman never plays leapfrog with a unicorn."
msg51870/pgp0.pgp
Description: PGP signature
Re: Wrong date for DEVFS entries
On Thu, Feb 06, 2003 at 11:44:29 +0100, [EMAIL PROTECTED] wrote: > > Think diskless NFS, think MD(4) based root, think... They are read-only at this rc stage, so something could be damaged are access times only. > I avoid it entirely by using UTC time in my RTC, but this is not an > option for machines which have to boot broken-as-designed OSs. Yes, the main reason not running BIOS clock at UTC is other OSes like M$ ones installed in the same machine. > I don't know if modern bios's know about timezones and DST, I've > seen some that has setup functions for it, but I don't know > if there is any way to find the information they store and I don't > think such features are widespread. I saw this too, but it is totally useless, even M$ can't handle such BIOSes. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Wrong date for DEVFS entries
On Thu, 6 Feb 2003, Andrey A. Chernov wrote: > On Thu, Feb 06, 2003 at 11:27:36 +0100, [EMAIL PROTECTED] wrote: > > In message <[EMAIL PROTECTED]>, Bruce Evans writes: > > >On Thu, 6 Feb 2003, Andrey A. Chernov wrote: > > > > > >> On Wed, Feb 05, 2003 at 23:44:08 +0100, [EMAIL PROTECTED] wrote: > > >> > > > >> > >2) Feb 6 01:36 (boot time) > > >> > >3) Feb 6 04:36 (+3 TZ future jump) > > >> > > > >> > These timestamps have been touched, and the clock has made a 3 hour > > >> > jump either forward or backward at some point. > > >> > > > >> > The problem is the clock jump, not DEVFS. > > >> > > >> Clock jump happens as it supposed when adjkerntz(8) corrects machine clock > > >> back to GMT via various CPU_* sysctl's. Could touched DEVFS stamps be > > >> fixed back to something useful in the same sysctl code too? > > > > > >This should be well known to devfs users. > > > > > >devfs sets at least some of the times before adjkerntz can run, and nothing > > >fixes them, so these times are wrong by the timezone difference. > > > > This is not any different from any other filesystem. > > No, it IS different - no real filesystems mounted at this point yet, so no > real timestamps damaged. More precisely: some are mounted, but they are mounted read-only (modulo the bug that adjkerntz is run a little after mounting filesystems read-write). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current, IBM A30p & 2 external FW-disks
On Wed, 5 Feb 2003, Michael Reifenberger wrote: ... > > I have improved recovery code after timeout in -current. > > Could you try that? > > Is scheduled for this evening. > Thanks so far! > ... > > > > - fwcontorl -g 20 > > > > - sysctl hw.firewire.sbp.max_speed=0 > > > > - change SBP_QUEUE_LEN in sbp.c to 1 and rebuld module. > > > > - sysctl machdep.cpu_idle_hlt=0 > > > > - sysctl debug.sbp_debug=1 and send me a dmesg. Ok, I did some extensive tests overnight. Essentially I still had `fwcontorl -g 20` and SBP_QUEUE_LEN=1 and maxopenings=1 and `debug.sbp_debug=1`. hw.firewire.sbp.max_speed started at 0 and got 2 at the end. After treating two `iozone -s 51200m -r1024k` on the platters overnight without problems I started with a plain sbp.c and no `fwcontorl -g 20`. I get constant rates of 13MB/s on each disk. No problems so far. Seems you got it. Thanks! BTW: switching on debug.firewire_debug gives zillions of 'kick'... Is this just a notification about the code-path? Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
alpha tinderbox failure
-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree -- >>> stage 2: rebuilding the object tree -- >>> stage 2: build tools -- >>> stage 3: cross tools -- >>> stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- >>> stage 4: building libraries -- >>> stage 4: make dependencies -- >>> stage 4: building everything.. -- >>> Kernel build for GENERIC started on Thu Feb 6 03:17:47 PST 2003 -- >>> Kernel build for GENERIC completed on Thu Feb 6 03:48:32 PST 2003 -- >>> Kernel build for LINT started on Thu Feb 6 03:48:33 PST 2003 -- ===> vinum "Makefile", line 4450: warning: duplicate script for target "geom_bsd.o" ignored /h/des/src/sys/dev/lmc/if_lmc.c:32:2: warning: #warning "The lmc driver is broken and is not compiled with LINT" /h/des/src/sys/dev/pdq/pdq.c: In function `pdq_initialize': /h/des/src/sys/dev/pdq/pdq.c:1606: warning: cast discards qualifiers from pointer target type /h/des/src/sys/pci/meteor.c:149:2: warning: #warning "The meteor driver is broken and is not compiled with LINT" /h/des/src/sys/pci/simos.c:30:2: warning: #warning "The simos driver is broken and is not compiled with LINT" /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_open': /h/des/src/sys/dev/gfb/gfb_pci.c:268: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:268: (Each undeclared identifier is reported only once /h/des/src/sys/dev/gfb/gfb_pci.c:268: for each function it appears in.) cc1: warnings being treated as errors /h/des/src/sys/dev/gfb/gfb_pci.c:275: warning: passing arg 1 of `genfbopen' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_close': /h/des/src/sys/dev/gfb/gfb_pci.c:284: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:285: warning: passing arg 1 of `genfbclose' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_read': /h/des/src/sys/dev/gfb/gfb_pci.c:293: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:294: warning: passing arg 1 of `genfbread' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_write': /h/des/src/sys/dev/gfb/gfb_pci.c:302: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:303: warning: passing arg 1 of `genfbwrite' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_ioctl': /h/des/src/sys/dev/gfb/gfb_pci.c:311: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:312: warning: passing arg 1 of `genfbioctl' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_mmap': /h/des/src/sys/dev/gfb/gfb_pci.c:320: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:321: warning: passing arg 1 of `genfbmmap' from incompatible pointer type *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
urgently needed
Dear Friend, I am Mr dudley rogers, the secretary of Commercial Farmers union branch in the region of matabeleland,Zimbabwe. After the last general elections in my country where the incumbent president MR. Robert Mugabe won the presidential election, the government has adopted a very aggressive land reforms programme. This programme is solely aimed at taking the land owned by white African farmers for redistribution to black Africans. This programme has attracted worldwide condemnation from world leaders including British prime minister,MR Tony Blair and also forced several white farmers to flee the country for fear of victimization and physical abuse. Few months ago, our headquartes in Harare was attacked and looted by black protesters and in the process burnt down the whole building. Fortunately,they did not get access to the documents of our union funds which belong to the co- operation. This cash is kept in UBS PRIVATE BANK IN SWITZERLAND.We are worried that the money is no longer safe because our president ,ROBERT MUGABE might freeze the account if he gets to know about it. Now I have the funds deposit documents in my hands Once I can get your commitment and sincerity of investing this funds on our behalf then I would proceed to get the funds transfered into your nominated bank account anywhere in the world.You do not have anything to worry about as I would undertake all charges i have already perfected all avenues to get the money into your account. i have the mandate from Mr Max Crawford,the president of the union to get the funds out as fast as possible.You would be compensated for all your effort once we have gotten the funds to your account. Please get back to me if you can be of assistance and I would want our correspondence to be via email as most phone lines of white farmers are bugged by the government. I expect your confidentiality and your promptresponse to this mail so as to proceed. dudley rogers - HKNETMAIL.COM Free WEB MAIL Service by HKNET To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: tired of crashes
On Wed, Feb 05, 2003 at 10:40:09AM -0800, Kris Kennaway <[EMAIL PROTECTED]> wrote: > > --- > > panic: ufs_dirbad: bad dir > > cpuid = 1; lapic.id = 0100 > > boot() called on cpu#1 > > I get those on the bento cluster when the disk is starting to fail. > dd'ing /dev/zero over it usually gives it some more life by forcing it > to remap bad blocks as it goes. The disk has been in use for ~1 year and both primary and grown defect lists are the same as in the beginning. So far haven't observed any signs of dying disk. Also no other disk activity has been problematic, I have several times copied over the disk contents (~5GB) to other disk to re-newfs the filesystem. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.7-amd cannot mount exports from 5.0-RELEASE
Hi, It works here for both cases. I've done intensive testing, and I just cannot reproduce this bug. The list here just looks normal as it should be: localhost:/ on /a/localhost (nfs, nodev, nosuid) 127.0.0.1:/ on /a/127.0.0.1 (nfs, nodev, nosuid) levais:/ on /a/levais (nfs, nodev, nosuid) levais:/usr on /a/levais/usr (nfs, nodev, nosuid) 192.168.0.66:/ on /a/192.168.0.66 (nfs, nodev, nosuid) 192.168.0.66:/usr on /a/192.168.0.66/usr (nfs, nodev, nosuid) Can you send me both - tcpdump / ethereal dump of the failing request - amd, mountd configs (amd.*, /etc/exports) - a description of the mounted filesystems - how it fails ? what is the error message ? - run mountd in debug mode and keep the output ? Thank you very much Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
New technologies in FreeBSD 5.x vs. 4.x
Hi, I'm about to write an article on FreeBSD for PC Magazine Romania and I would like to concentrate on the new technologies introduced in FreeBSD 5.x. Where can I find a (preferrably detailed) list of the new technologies introduced with FreeBSD 5.x ? I would also like, if possible, to get in touch with a few of the main developers that took charge of coding them. Thank you very much, Adrian Penisoara Ady (@freebsd.ady.ro, @rofug.ro) ROFUG founder To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New technologies in FreeBSD 5.x vs. 4.x
[ Bcc'd to -current following initial crosspost. Followups to -hackers or directly to Mr. Penisoara. ] On Thu, Feb 06, 2003 at 03:17:15PM +0200, Adrian Penisoara wrote: > > Where can I find a (preferrably detailed) list of the new technologies > introduced with FreeBSD 5.x ? Greetings Adrian, The most significant new features are listed in the Release Announcement[0]. There is greater detail available in the Release Notes under "What's New"[1]. > I would also like, if possible, to get in touch with a few of the main > developers that took charge of coding them. You can contact the person listed as MAINTAINER in the Makefile for the part of the source tree you are concerned with. If there is no MAINTAINER listed, a quick trip through CVSWeb[2] will reveal who has been the most active committer to that section of the tree. I would, of course, recommend courtesy and patience when approaching FreeBSD develoeprs for an interview. Most of them are quite busy. [0] - http://www.freebsd.org/releases/5.0R/announce.html [1] - http://www.freebsd.org/releases/5.0R/relnotes-i386.html [2] - http://www.freebsd.org/cgi/cvsweb.cgi/ Good luck, Brandon D. Valentine -- [EMAIL PROTECTED] http://www.geekpunk.net "We've been raised on replicas of fake and winding roads, and day after day up on this beautiful stage we've been playing tambourine for minimum wage, but we are real; I know we are real." -- David Berman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
xmms looping forever
Hi! I recently upgraded my machine from 4.7-stable to 5.0-release. The upgrade went almost smoothly. I say almost because so many things changed between 4.x and -current that I missed a few. :) But overall, I'm quite happy with the results. I had problems with almost all my apps, at first. Third part applications that weren't recompiled during the buildworld (ports) had linking problems. Take wget, for example: anarcat@lenny[~]% wget /usr/libexec/ld-elf.so.1: /usr/local/lib/libintl.so.4: Undefined symbol "stpcpy" anarcat@lenny[~]% Recopmiling wget solves the problem. Some folks pointed out to me this might be due to the fact I forgot to include COMPAT4X=yes in my make.conf. At first I had considered upgrading from -release to -current (because I'm a careless freak), so I already had my /usr/src cvsup'd to yesterday's current. So I builded world over that and installed it. Of course, that didn't solve the linking problem. But it made another problem appear. My dear user-friendly xmms now fails to start. This machine is used by the whole family here and I got really embarrassed over this. :) xmms seemed to pop an empty window, and sucked all the CPU time available on my AMD Druon 1GHz: CPU states: 14.4% user, 0.0% nice, 84.4% system, 1.2% interrupt, 0.0% idle Mem: 116M Active, 56M Inact, 92M Wired, 600K Cache, 92M Buf, 862M Free Swap: 498M Total, 1452K Used, 496M Free ... 891 anarcat1150 15820K 7060K RUN 0:05 82.69% 18.31% xmms ... So I told my self, "eh, that's -current for you!" ;) And I thought that -release wasn't so bad after all and that the upgrade didn't give me anything good anyways. So I downgraded to -release. Without success. xmms hangs as before. But it used to work on -release!!! How is that possible? Using SIGINFO, I've witnessed the following: load: 1.12 cmd: xmms 9744 [*Giant] 0.33u 0.85s 1% 7144k load: 1.19 cmd: xmms 9744 [*Giant] 0.41u 1.06s 1% 7144k load: 1.19 cmd: xmms 9744 [running] 0.41u 1.09s 1% 7144k load: 1.19 cmd: xmms 9744 [*Giant] 0.41u 1.12s 1% 7144k load: 1.19 cmd: xmms 9744 [running] 0.41u 1.14s 1% 7144k But I'm able to see this only when it system is loaded (with the compilation of a port, for example). So I suspect xmms is somehow looping over the giant lock, for some reason. truss gives me the following: sigprocmask(0x3,0x28144710,0x0) = 0 (0x0) SIGNAL 27 SIGNAL 27 gettimeofday(0x281678b8,0x0) = 0 (0x0) sigprocmask(0x3,0x28167924,0x0) = 0 (0x0) sigreturn(0xbfbff4a0)= 0 (0x0) sigreturn(0xbfbff330)= 135891072 (0x8198880) sigreturn(0xbfbff330)= 135891072 (0x8198880) sigreturn(0xbfbff330)= 135891072 (0x8198880) And ktrace: 26035 xmms CALL mmap(0,0x4788,0x3,0x1000,0x,0,0,0) 26035 xmms RET mmap 686489600/0x28eb 26035 xmms CALL munmap(0x28eb,0x4788) 26035 xmms RET munmap 0 26035 xmms CALL mprotect(0x28e3c000,0x62000,0x5) 26035 xmms RET mprotect 0 26035 xmms CALL sigprocmask(0x3,0x28144710,0) 26035 xmms RET sigprocmask 0 26035 xmms PSIG SIGPROF caught handler=0x28159510 mask=0x0 code=0x0 26035 xmms CALL gettimeofday(0x281678b8,0) 26035 xmms RET gettimeofday 0 26035 xmms CALL sigprocmask(0x3,0x28167924,0) 26035 xmms RET sigprocmask 0 26035 xmms CALL sigreturn(0xbfbff4a0) 26035 xmms RET sigreturn JUSTRETURN 26035 xmms PSIG SIGSEGV caught handler=0x28159510 mask=0x0 code=0xc 26035 xmms CALL sigreturn(0xbfbff330) 26035 xmms RET sigreturn JUSTRETURN 26035 xmms PSIG SIGSEGV caught handler=0x28159510 mask=0x0 code=0xc I include my dmesg at the end of this mail, in the meantime, here are the pcm sysctls that might be relevant: root@lenny[/usr/home/anarcat]# sysctl hw.snd hw.snd.targetirqrate: 32 hw.snd.report_soft_formats: 1 hw.snd.verbose: 1 hw.snd.unit: 0 hw.snd.maxautovchans: 2 hw.snd.pcm0.buffersize: 4096 hw.snd.pcm0.vchans: 1 I also tried: root@lenny[/usr/home/anarcat]# sysctl hw.snd hw.snd.targetirqrate: 32 hw.snd.report_soft_formats: 1 hw.snd.verbose: 1 hw.snd.unit: 0 hw.snd.maxautovchans: 0 hw.snd.pcm0.buffersize: 4096 hw.snd.pcm0.vchans: 0 I had odd crashes with xmms before, but *crashes*, no hangs. :) I am available for testing and debugging, and I am eager to solve this problem, since xmms is a must here, right now. I'd be forced to downgrade to 4.7-stable (!) but I feel I'll have the same results. :) A. Copyright (c) 1992-2003 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.0-RELEASE #2: Wed Feb 5 22:17:29 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LENNY Preloaded elf kernel "/boot/kernel/kernel" at 0xc05e9000. Preloaded elf module "/boot/kernel
Re: xmms looping forever
> I had problems with almost all my apps, at first. Third part > applications that weren't recompiled during the buildworld (ports) had > linking problems. Take wget, for example: > > anarcat@lenny[~]% wget > /usr/libexec/ld-elf.so.1: /usr/local/lib/libintl.so.4: Undefined symbol "stpcpy" > anarcat@lenny[~]% > > Recopmiling wget solves the problem. Have you tried simply recompiling xmms? I have been using xmms on -CURRENT and -RELEASE for about a month with 0 problems. -Don To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xmms looping forever
On Thu Feb 06, 2003 at 10:30:52AM -0500, Don wrote: > > I had problems with almost all my apps, at first. Third part > > applications that weren't recompiled during the buildworld (ports) had > > linking problems. Take wget, for example: > > > > anarcat@lenny[~]% wget > > /usr/libexec/ld-elf.so.1: /usr/local/lib/libintl.so.4: Undefined symbol "stpcpy" > > anarcat@lenny[~]% > > > > Recopmiling wget solves the problem. > Have you tried simply recompiling xmms? I have been using xmms on -CURRENT > and -RELEASE for about a month with 0 problems. Yep. Trice. I've been using it on -RELEASE without any problems too! Then the upgrade, then problems, even on -release. There's got to be something I'm missing here. A. -- From the age of uniformity, from the age of solitude, from the age of Big Brother, from the age of doublethink - greetings! msg51882/pgp0.pgp Description: PGP signature
RE: vnode locking question.
On 05-Feb-2003 Julian Elischer wrote: > > Is there ever a case when a vnode is locked for longer than the duration > of the syscall that locked it? Shouldn't be. That would be a bug I believe. Userland threads should never hold any kernel locks. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Linux networking emulation broken?
Hi again, After noticing a huge delay between host names resolution and the beginning of pages loading with Opera (6.11/Linux), I noticed that it is trying to connect to 4.0.0.0:111 instead of the usual 127.0.0.1:111. I worked it around by setting up 4.0.0.0/32 as an alias on lo0, but this obviously shouldn't be happening. The Opera port was installed back when I still ran 4.7-STABLE and was working fine up to the two most recent updates (I try building kernel/world every week for testing), so I don't think it's an Opera fault per se. Any ideas? Fred -- "Death is only a state of mind. Only it doesn't leave you much time to think about anything else." msg51884/pgp0.pgp Description: PGP signature
rsync --daemon problems
When I start the rsync daemon under 5-RELEASE, I can only connect to it on the localhost. Trying to connect to it from any remote host fails. Trying to telnet to the 873 port fails as well. Everything is on a local lan connection without any type of fire-walling going on, also using the default install of 5.0 -- David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: se7500+dual xeon?
It's been a known issue for quite some time that the SMP in 4.x is broken with the SE7500CW2 boards (Linux and XP appear to function correctly) and as far as I know a fix was never found. I have not tried fooling around with FreeBSD 5.x on it however. Last I heard it appeared to be related to an incorrect APIC id problem of some kind, but I am not technically proficient enough (at that level) to know any more than that. I would assume that this is related to that same problem, but someone please correct me if I'm mistaken. Regards, James On Wed, 5 Feb 2003, Victor Ponomarev wrote: > Hi All. > > It's seems that smp kernel configuration doesn't work correctly on > Intel SE7500WV2 motherboard > with 2 xeon processors in 5.0-RELEASE. > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic copying from USB drive
Hi, just got the following kernel panic when the USB hard drive I was copying from at the time ran out of batteries and powered off: umass0: ARCHOS ARCHOS USB2.0 (P4a), rev 2.00/11.01, addr 2 umass0: BBB reset failed, TIMEOUT da1 at umass-sim0 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI-0 device da1: 1.000MB/s transfers da1: 19077MB (39070080 512 byte sectors: 255H 63S/T 2432C) umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: at uhub2 port 2 (addr 2) disconnected (da1:umass-sim0:0:0:0): lost device umass0: detached Fatal trap 12: page fault while in kernel mode cpuid = 3; lapic.id = 0300 fault virtual address = 0x72 fault code = supervisor read, page not present instruction pointer = 0x8:0xc02c6417 stack pointer = 0x10:0xe910c9bc frame pointer = 0x10:0xe910c9d4 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 35 (usb1) kernel: type 12 trap, code=0 Stopped at vm_object_pip_add+0x37: movzwl 0x72(%esi),%eax db> trace vm_object_pip_add(0,1,1,e910ca98,e910ca88) at vm_object_pip_add+0x37 vm_fault(c082f000,deadc000,1,0,c63b60f0) at vm_fault+0x169 trap_pfault(e910cb80,0,deadc10a,51e,deadc10a) at trap_pfault+0x1b6 trap(18,c0370010,c0370010,0,caac6d00) at trap+0x3e5 calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc01cddc7, esp = 0xe910cbc0, ebp = 0xe910cbfc --- device_get_nameunit(caac6800,caac6d00,6,0,caac683c) at device_get_nameunit+0x7 usb_transfer_complete(caac6800,2,caac6864,e910cc58) at usb_transfer_complete+0x133 uhci_abort_xfer(caac6800,6,e910cc68,c0180b39,caac6800) at uhci_abort_xfer+0x99 uhci_device_ctrl_abort(caac6800,ca771d80,e910cc74,c01807e1,ca771d80) at uhci_device_ctrl_abort+0x19 usbd_ar_pipe(ca771d80,e910cc88,c017f4a4,ca771d80,e910cca4) at usbd_ar_pipe+0x29 usbd_abort_pipe(ca771d80,e910cca4,c790e680,e910cca4,c017ffa8) at usbd_abort_pipe+0x11 usbd_kill_pipe(ca771d80,c63b00f0,c790e680,c62844c0,2) at usbd_kill_pipe+0x14 usb_free_device(c790e680,c6284500,11,0,0) at usb_free_device+0xa8 uhub_explore(c6284600,c6162820,e910cd0c,c017d7e8,c6162820) at uhub_explore+0x259 usb_discover(c6162820,0,5c,c03400f0,1770) at usb_discover+0x3a usb_event_thread(c6162820,e910cd48,c0345a83,35f,0) at usb_event_thread+0x68 fork_exit(c017d780,c6162820,e910cd48) at fork_exit+0xa9 fork_trampoline() at fork_trampoline+0x1a --- trap 0x1, eip = 0, esp = 0xe910cd7c, ebp = 0 --- -- Lars Eggert <[EMAIL PROTECTED]> USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: se7500+dual xeon?
On 06-Feb-2003 James Schmidt wrote: > It's been a known issue for quite some time that the SMP in 4.x is > broken with the SE7500CW2 boards (Linux and XP appear to function > correctly) and as far as I know a fix was never found. I have not tried > fooling around with FreeBSD 5.x on it however. Last I heard it appeared > to be related to an incorrect APIC id problem of some kind, but I am not > technically proficient enough (at that level) to know any more than that. > > I would assume that this is related to that same problem, but someone > please correct me if I'm mistaken. His board is a WV2, not a CW2. The WV2's should work fine though they might need a BIOS update. > On Wed, 5 Feb 2003, Victor Ponomarev wrote: > >> Hi All. >> >> It's seems that smp kernel configuration doesn't work correctly on >> Intel SE7500WV2 motherboard >> with 2 xeon processors in 5.0-RELEASE. >> > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-smp" in the body of the message -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linux networking emulation broken?
On Thu, Feb 06, 2003 at 02:23:53PM -0200, Fred Souza wrote: > After noticing a huge delay between host names resolution and the > beginning of pages loading with Opera (6.11/Linux), I noticed that it > is trying to connect to 4.0.0.0:111 instead of the usual > 127.0.0.1:111. I worked it around by setting up 4.0.0.0/32 as an alias > on lo0, but this obviously shouldn't be happening. Are you running 5.0-RELEASE or -current? If -current, when did you last rebuild your kernel? Some changes were made to the linux network emulation in the last few days. I was testing them and didn't notice any problems like this, but I may have missed something. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linux networking emulation broken?
I have similar problem after upgrading to a up-to-date -CURRENT. > uname -a FreeBSD cartier.home 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Feb 6 23:56:44 CST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERI i386 My kernel config is simply a SMP-enabled GENERIC. I keep seeing something below in the truss(1) output. linux_socketcall(0x2,0xbfbfe3dc) ERR#13 'Permission denied' ... read(0x7,0xbfbfcf1c,0x20)ERR#35 'Resource temporarily unavailable' My linux application also keeps reporting something below to me. do_ypcall: clnt_call: RPC: Timed out and unable to resolve host name ... No matter being root or not, the results are the same. On Thu, Feb 06, 2003 at 02:23:53PM -0200, Fred Souza wrote: > Hi again, > > After noticing a huge delay between host names resolution and the > beginning of pages loading with Opera (6.11/Linux), I noticed that it > is trying to connect to 4.0.0.0:111 instead of the usual > 127.0.0.1:111. I worked it around by setting up 4.0.0.0/32 as an alias > on lo0, but this obviously shouldn't be happening. > > The Opera port was installed back when I still ran 4.7-STABLE and was > working fine up to the two most recent updates (I try building > kernel/world every week for testing), so I don't think it's an Opera > fault per se. Any ideas? > > > Fred > > > -- > "Death is only a state of mind. > Only it doesn't leave you much time to think about anything else." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: vnode locking question.
On Thu, 6 Feb 2003, John Baldwin wrote: > > On 05-Feb-2003 Julian Elischer wrote: > > > > Is there ever a case when a vnode is locked for longer than the duration > > of the syscall that locked it? > > Shouldn't be. That would be a bug I believe. Userland threads should > never hold any kernel locks. That's what I think too but I just thought I'd ask.. (NFS worries me a bit) > > -- > > John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linux networking emulation broken?
On Thu, Feb 06, 2003 at 02:23:53PM -0200, Fred Souza wrote: > Hi again, > > After noticing a huge delay between host names resolution and the > beginning of pages loading with Opera (6.11/Linux), I noticed that it > is trying to connect to 4.0.0.0:111 instead of the usual > 127.0.0.1:111. I worked it around by setting up 4.0.0.0/32 as an alias > on lo0, but this obviously shouldn't be happening. > > The Opera port was installed back when I still ran 4.7-STABLE and was > working fine up to the two most recent updates (I try building > kernel/world every week for testing), so I don't think it's an Opera > fault per se. Any ideas? I'm also seeing this with Linux Phoenix, though I haven't tcpdumped the output. Kris msg51892/pgp0.pgp Description: PGP signature
Re: Linux networking emulation broken?
> Are you running 5.0-RELEASE or -current? If -current, when did you > last rebuild your kernel? Some changes were made to the linux network > emulation in the last few days. I was testing them and didn't notice > any problems like this, but I may have missed something. Sorry for not mentioning it in that last e-mail. Here's my `uname -a`: FreeBSD torment.storming.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Feb 6 05:11:34 BRST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/torment i386 (Currently BRST == GMT-2, the source tree had been cvsup'd right before the building of the kernel) I'm also attaching my kernel config file, in case it should help at all. Fred -- "Q: What's tan and black and looks great on a lawyer? A: A doberman." # # torment -- Torment's kernel configuration file for FreeBSD5/i386 # machine i386 cpu I586_CPU ident TORMENT maxusers0 # NO_MEMORY_HOLE is an optimisation for systems with AMD K6 processors # which indicates that the 15-16MB range is *definitely* not being # occupied by an ISA memory hole. # options NO_MEMORY_HOLE # MAXMEM specifies the amount of RAM on the machine; if this is not # specified, FreeBSD will first read the amount of memory from the CMOS # RAM, so the amount of memory will initially be limited to 64MB or 16MB # depending on the BIOS. If the BIOS reports 64MB, a memory probe will # then attempt to detect the installed amount of RAM. If this probe # fails to detect >64MB RAM you will have to use the MAXMEM option. # The amount is in kilobytes, so for a machine with 128MB of RAM, it would # be 131072 (128 * 1024). # options MAXMEM="(256*1024)" options INET#InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options MD_ROOT #MD is a potential root device options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options PSEUDOFS#Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options COMPAT_LINUX#Linux binary compatability options SCSI_DELAY=0#Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV# install a CDEV entry in /dev # Scheduler to use. options SCHED_4BSD # The following options have been commented out for forcing the system to use # their benefits as modules. # #optionsMFS #Memory Filesystem # ISA & PCI controllers. # device isa device pci # Audio support. # device pcm # Floppy drives # device fdc # Specify floppy devices # ATA and ATAPI devices # device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering # SCSI controller and supported devices #device aic #device scbus # SCSI bus (required) #device cd # CD # atkbdc0 controls both the keyboard and the PS/2 mouse # device atkbdc device atkbd # Video card driver for VGA adapters. device vga # AGP GART support device agp # To include support for VESA video modes # options VESA # splash screen/screen saver # device splash # syscons is the default console driver, resembling an SCO console # device sc options MAXCONS=16 options SC_HISTORY_SIZE=4096# number of history buffer lines options SC_PIXEL_MODE # add support for the raster text mode options SC_DFLT_FONT# compile font in makeoptions SC_DFLT_FONT=iso01 # default font # Floating point support - do not disable. # device npx # Serial (COM) ports # device sio # Ethernet NICs. # 'device ed' requires 'device miibus' # device miibus device ed # Various devices # device random # Entropy device device loop# Network loopback device ether # Ethernet support #device ppp # Kernel PPP device tun # Packet tunnel. dev
Re: Linux networking emulation broken?
On Thu, Feb 06, 2003 at 11:00:21AM -0800, Kris Kennaway wrote: > I'm also seeing this with Linux Phoenix, though I haven't tcpdumped > the output. I think there may be a problem with the new version of linux_sendmsg. I'll check in detail at home, where I have linux_kdump installed. It should be easy to fix. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SiS pciconf's request ending :)
Thanks to all those that replied with pciconf output from various SiS chipsets (and thanks to those that sent from other systems as well :) ). I now have a significant amount of data to use for the SiS chipset support, and am working on it over the next days.. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: X compilation problems
On Thu, 2003-02-06 at 02:53, Fred Souza wrote:
> Since the last port update for XFree86-libraries, I've been unable to
> get that port (x11/XFree86-4-libraries) compiled. I insistently get this
> error:
>
> cc -c -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../include
>-I/usr/ports/x11/XFree86-4-libraries/work/xc/include
>-I/usr/ports/x11/XFree86-4-libraries/work/xc/include/GL
>-I/usr/ports/x11/XFree86-4-libraries/work/xc
>-I/usr/ports/x11/XFree86-4-libraries/work/xc/exports/include -DCSRG_BASED
>-DFUNCPROTO=15 -DNARROWPROTO -DNDEBUG -O2 -pipe -march=k6-2 mipmap.c -o
>unshared/mipmap.o
> {standard input}: Assembler messages:
> {standard input}:7683: Error: value of -129 too large for field of 1 bytes at 20035
> *** Error code 1
>
> I'm running 5.0-CURRENT built yesterday (02/06), but I have seen this
> happening since the update from revision 5 to 6 of the port (I'm not
> sure about the exact date, but I think it happened about a week or so
> ago.) Has anyone seen this? How do I fix it?
Please remove your nonstandard CFLAGS and try again.
--
Eric Anholt[EMAIL PROTECTED]
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
¥Î¤ß¬Ý§¹³á!!!.....
Title: ¯¬±z¦Ï¦~
¯¬±z¦Ï¦~
¤@¦|·¶¶¡B¤GÀsÄ˸¡B¤T¦Ï¶}®õ¡B
¥|©u¥¦w¡B¤ºÖÁ{ªù¡B¤»¤»¤j¶¶¡B
¤C¬P°ª·Ó¡B¤K¤è¨Ó°]¡B¤E¤E¦P¤ß¡B
¤Q¥þ¤Q¬ü¡A¬v¬v±o·N¹L¦n¦~
³Ì¦³¬¡¤Oªº---¤pºµºµ
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall->Configure->Fdisk
On Tue, 4 Feb 2003 17:16:22 +1000 (EST), "Andy Farkas" <[EMAIL PROTECTED]> said: > > sysinstall's 'FDISK Partition Editor' won't let me create a second slice. > > After pressing 'w' it says: "ERROR: Unable to write data to disk ad4!" > then check your securelevel man securelevel 2 Highly secure mode - same as secure mode, plus disks may not be opened for writing (except by mount(2)) whether mounted or not. This level precludes tampering with filesystems by unmounting them, but also inhibits running newfs(8) while the system is multi-user. Murat Bicer [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall->Configure->Fdisk
On Tue, 4 Feb 2003 17:16:22 +1000 (EST), "Andy Farkas" <[EMAIL PROTECTED]> said: > > sysinstall's 'FDISK Partition Editor' won't let me create a second slice. > > After pressing 'w' it says: "ERROR: Unable to write data to disk ad4!" > then check your securelevel man securelevel 2 Highly secure mode - same as secure mode, plus disks may not be opened for writing (except by mount(2)) whether mounted or not. This level precludes tampering with filesystems by unmounting them, but also inhibits running newfs(8) while the system is multi-user. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: L440gx+ serial BIOS needs text mode
On Mon, 3 Feb 2003, Terry Lambert wrote: > Lucky Green wrote: > > However, the Intel L440gx+ motherboard I have (it came in a VA Linux > > rackmount) seems to have a separate CPU performing all kinds of > > monitoring tasks, watchdog, etc, so I was hoping this separate CPU was > > actually performing the serial console task. > > According to Doug's Intel page: > > http://people.freebsd.org/~dwhite/ipmi/setup_intel_scb2.html > > It's possible that it is, and that what's happening is some probe > is writing to the port address on the I/O bus, causing the problem. > If this is the case, then the only way to deal with it is to write > a real driver for the thing (not the user space driver), and have > the kernel claim it early, which would (should) keep other drivers > from trying to poke it in the eye to see if their own hardware is > there. That'd be nice if the L440GX+ was IPMI compliant. It isn't. :-) You're better off trying to use the intpm driver to talk to the old-style monitoring chips. Several IPMI features came from features implemented on the BMC on the L440GX, but it still uses the proprietary smbus interface. I never fiddled with the BMC features of the L440GX board. Linux's monitoring driver does talk to it though, you might be able to port it over. On the current generation Intel boards, serial redirection is handled by the BIOS. Once the kernel starts and the kernel takes over output, that redirection ceases to function. By that point, though, you have the usual FreeBSD serial console facilities and thus have a smooth transition. I suspect the same applies for any other Intel motherboard that supports serial redirection. You can confirm support for serial redirection by downloading the Technical Product Specifications for the Intel board you're interested in through support.intel.com. We have Tyan boards at my current employer with serial redirection and they work the same way. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: L440gx+ serial BIOS needs text mode
On Tue, 4 Feb 2003, Andrew Gordon wrote: > - On the latest machines featuring 'serial over LAN', you can >persuade the management CPU to subvert the serial port and >pass the data over one of the ethernet ports. This seems to use >a proprietary protocol, but if you have one Windows machine >somewhere with the Intel management software loaded on it, you >can use that to proxy the protocol for any number of managed >machines - ie. telnet to port 623 on the Windows machine, then >connect back to the target machine and get attached to the >serial console (and so get a FreeBSD login, if that's what is >running on COM2). I'd love to get the spec on this -- its a proprietary Intel feature and they won't cough up the spec unless you're a high volume integrator or have money and NDAs. > - Medium-aged machines seem to have all the hardware to subvert the >serial and ethernet ports, but won't do serial redirection apart >from controlling the BIOS. Upgrading the BMC software didn't >help on the machine I had in this category. No big loss for FreeBSD of course :) -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall->Configure->Fdisk
On Tue, Feb 04, 2003 at 05:16:22PM +1000, Andy Farkas wrote: > > sysinstall's 'FDISK Partition Editor' won't let me create a second slice. > > After pressing 'w' it says: "ERROR: Unable to write data to disk ad4!" then > "Disk partition write returned an error status!" > > Freshly cvsup'd a few hours ago. > > # sysctl -a | grep kern.version > kern.version: FreeBSD 5.0-CURRENT #2: Tue Feb 4 11:04:44 EST 2003 This is a known problem due to GEOM. It doesn't matter if you are root, or if your securelevel is set properly. It just won't work. See the thread: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=295042+0+archive/2002/freebsd-current/20021229.freebsd-current Try to boot from another disk or a floppy, then you will be able to create a new partition with sysinstall. -- Craig Rodrigues http://home.attbi.com/~rodrigc [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall->Configure->Fdisk
> Date: Thu, 6 Feb 2003 16:50:51 -0500 > From: Craig Rodrigues <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > On Tue, Feb 04, 2003 at 05:16:22PM +1000, Andy Farkas wrote: > > > > sysinstall's 'FDISK Partition Editor' won't let me create a second slice. > > > > After pressing 'w' it says: "ERROR: Unable to write data to disk ad4!" then > > "Disk partition write returned an error status!" > > > > Freshly cvsup'd a few hours ago. > > > > # sysctl -a | grep kern.version > > kern.version: FreeBSD 5.0-CURRENT #2: Tue Feb 4 11:04:44 EST 2003 > > > This is a known problem due to GEOM. It doesn't matter if you are root, > or if your securelevel is set properly. It just won't work. > > See the thread: > >http://docs.freebsd.org/cgi/getmsg.cgi?fetch=295042+0+archive/2002/freebsd-current/20021229.freebsd-current > > Try to boot from another disk or a floppy, then you will be able to > create a new partition with sysinstall. This is what the second ISO image is for. It contains the holographic shell and is sometimes called the "fixit" disk. Boot it select Fixit. Then follow the instructions. Or, if you just want to partition, use the "Configure" option and select Fdisk. (For this, you don't even need the Fixit disk. The main OS disk can do this.) 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linux networking emulation broken?
On Thu, Feb 06, 2003 at 11:00:21AM -0800, Kris Kennaway wrote: > I'm also seeing this with Linux Phoenix, though I haven't tcpdumped > the output. I'm guessing the short patch at: http://www.maths.tcd.ie/~dwmalone/linux_sendmsg.patch should help. Can you try it and let me know? David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
read/write errors with USB CF reader
Hi, (this is unrelated to my earlier post about the kernel panic.) when doing I/O to an IBM microdrive mounted via an USB CF reader, I get read/write errors about once an hour or so. Here's an example: dd if=/dev/zero of=/dev/da1 bs=512 count=32 dd: /dev/da1: Input/output error 1+0 records in 0+0 records out 0 bytes transferred in 0.905537 secs (0 bytes/sec) *** Error code 1 Relevant syslog excerpt: umass0: SanDisk Corporation ImageMate CompactFlash USB, rev 1.10/0.09, addr 2 umass0: Get Max Lun not supported (STALLED) da1 at umass-sim0 bus 0 target 0 lun 0 da1: Removable Direct Access SCSI-2 device da1: 1.000MB/s transfers da1: 1027MB (2104705 512 byte sectors: 255H 63S/T 131C) umass0: BBB reset failed, STALLED (da1:umass-sim0:0:0:0): AutoSense Failed umass0: BBB reset failed, STALLED (da1:umass-sim0:0:0:0): AutoSense Failed umass0: BBB reset failed, STALLED (da1:umass-sim0:0:0:0): AutoSense Failed Retrying the failed command usually works (and the dd above was just an example, I've seen it happen with dump/restore, tar, or make.) Also, this may not be specific to -current, I think I saw it on -STABLE as well a while ago. The microdrive itself is fine, I also mount it with a CF PC-card adaptor, and have never seen an error then. Any clues? Thanks, Lars -- Lars Eggert <[EMAIL PROTECTED]> USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
pcm channel duplicate lock
Got thsi when opening gnomemeeting2 while having xmms playing:
acquiring duplicate lock of same type: "pcm channel"
1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
Debugger("witness_lock")
Stopped at Debugger+0x5a: xchgl %ebx,in_Debugger.0
db> trace
Debugger(c0328da1,c6283a54,c0532609,bf,eb3828ac) at Debugger+0x5a
witness_lock(c635ce40,8,c0532609,bf,eb3828d4) at witness_lock+0x142
_mtx_lock_flags(c635ce40,0,c0532609,bf,c5e5) at _mtx_lock_flags+0x63
pcm_chnalloc(c21a9e00,1,c5e5,,8) at pcm_chnalloc+0x66
dsp_open(c03a6a50,7,2000,c6612780,c0534380) at dsp_open+0x12f
spec_open(eb3829c8,eb382ae4,c0217796,eb3829c8,c03b3ae0) at spec_open+0x37d
spec_vnoperate(eb3829c8,c03b3ae0,0,180,c6612780) at spec_vnoperate+0x18
vn_open_cred(eb382bd4,eb382cd4,0,c7575600,eb382cc0) at vn_open_cred+0x306
vn_open(eb382bd4,eb382cd4,0,295,eb382b20) at vn_open+0x29
kern_open(c6612780,888ceb0,0,7,0) at kern_open+0x197
open(c6612780,eb382d10,c0363f83,407,c6610c50) at open+0x30
syscall(875002f,2f,bfbf002f,6,0) at syscall+0x3d6
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (5, FreeBSD ELF32, open), eip = 0x2932e273, esp =
0xbfa65abc, ebp = 0xbfa65ad8 ---
Lars
--
Lars Eggert <[EMAIL PROTECTED]> USC Information Sciences Institute
smime.p7s
Description: S/MIME Cryptographic Signature
alpha tinderbox failure
-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree -- >>> stage 2: rebuilding the object tree -- >>> stage 2: build tools -- >>> stage 3: cross tools -- >>> stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- >>> stage 4: building libraries -- >>> stage 4: make dependencies -- >>> stage 4: building everything.. -- >>> Kernel build for GENERIC started on Thu Feb 6 15:18:24 PST 2003 -- >>> Kernel build for GENERIC completed on Thu Feb 6 15:53:57 PST 2003 -- >>> Kernel build for LINT started on Thu Feb 6 15:53:57 PST 2003 -- ===> vinum "Makefile", line 4450: warning: duplicate script for target "geom_bsd.o" ignored /h/des/src/sys/dev/lmc/if_lmc.c:32:2: warning: #warning "The lmc driver is broken and is not compiled with LINT" /h/des/src/sys/dev/pdq/pdq.c: In function `pdq_initialize': /h/des/src/sys/dev/pdq/pdq.c:1606: warning: cast discards qualifiers from pointer target type /h/des/src/sys/pci/meteor.c:149:2: warning: #warning "The meteor driver is broken and is not compiled with LINT" /h/des/src/sys/pci/simos.c:30:2: warning: #warning "The simos driver is broken and is not compiled with LINT" /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_open': /h/des/src/sys/dev/gfb/gfb_pci.c:268: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:268: (Each undeclared identifier is reported only once /h/des/src/sys/dev/gfb/gfb_pci.c:268: for each function it appears in.) cc1: warnings being treated as errors /h/des/src/sys/dev/gfb/gfb_pci.c:275: warning: passing arg 1 of `genfbopen' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_close': /h/des/src/sys/dev/gfb/gfb_pci.c:284: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:285: warning: passing arg 1 of `genfbclose' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_read': /h/des/src/sys/dev/gfb/gfb_pci.c:293: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:294: warning: passing arg 1 of `genfbread' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_write': /h/des/src/sys/dev/gfb/gfb_pci.c:302: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:303: warning: passing arg 1 of `genfbwrite' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_ioctl': /h/des/src/sys/dev/gfb/gfb_pci.c:311: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:312: warning: passing arg 1 of `genfbioctl' from incompatible pointer type /h/des/src/sys/dev/gfb/gfb_pci.c: In function `pcigfb_mmap': /h/des/src/sys/dev/gfb/gfb_pci.c:320: `gfb_devclass' undeclared (first use in this function) /h/des/src/sys/dev/gfb/gfb_pci.c:321: warning: passing arg 1 of `genfbmmap' from incompatible pointer type *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sshd + NIS = bad mojo?
I'm upgrading my cluster to 5.0-R (fresh from CD), and everything works
swimmingly except logging in as user on the YPmap.
[3jane:~$] ssh ypuser@mcp
Password:
Connection to mcp.evil.mil closed by remote host.
Connection to mcp.evil.mil closed.
[3jane:~$] ssh user@mcp
Password:
However, I can su, finger and all files list the correct ownership on the
system, leading me to believe that yp is actually working.
When I check the logs, I see this message:
Feb 6 17:09:32 MCP sshd[562]: fatal: login_get_lastlog: Cannot find account
for uid 1002
Which I tracked to loginrec.c line 296:
pw = getpwuid(uid);
if (pw == NULL)
fatal("login_get_lastlog: Cannot find account for uid %i",
uid)
And that looks idential to the working code on 4.6.2... So perhaps I've
missed some configuration somewhere or there is something wrong with the
library.
Am I missing something? (I don't think so, the configuration is identical
to the working 4.6.2 setup I was running until this afternoon) or is this
a bug?
---
Barkley C. Vowk -- Systems Analyst -- University of Alberta
Math Sciences Department - [EMAIL PROTECTED]
Office: CAB642A, 780-492-4064
Opinions expressed are the responsibility of the author and
may not reflect the opinions of others or reality.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: rsync --daemon problems
On Thursday, February 6, 2003, at 05:31 PM, Sean Winn wrote: What does netstat -na | grep 873 show? On one machine that rsync start's on, I get this from netstat. tcp6 0 0 *.873 *.* LISTEN On another machine that it just dies and never seems to startup, I'm seeing this in ktrace. 839 rsyncRET __getcwd 0 839 rsyncCALL getsockopt(0,0x,0x1008,0xbfbffba0,0xbfbffba4) 839 rsyncRET getsockopt -1 errno 38 Socket operation on non-socket 839 rsyncCALL fork 839 rsyncRET fork 840/0x348 839 rsyncCALL exit(0) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd + NIS = bad mojo?
On Thu, 6 Feb 2003, Barkley Vowk wrote: > I'm upgrading my cluster to 5.0-R (fresh from CD), and everything works > swimmingly except logging in as user on the YPmap. I have about six boxes at work using 5.0-CURRENT and 5.0-RELEASE with NIS accounts without any apparent problems. I did shoot my toes several times during the upgrade process, though. I think I ended up manually forcing rpcbind to be on as well as nisclient. If finger and so on are working, I'm not sure why you'd see this failure, though. Does "id username" return the correct grouplist? Does this machine have multiple network interfaces, or just one? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
¹®ÀÇ µå¸³´Ï´Ù.
º¸ÁöÅÚ´åÄÄ BoziTel.com ¼ºÇö¾Æ ´©µå 2ź ! À¯¹Î Æ÷¸£³ë¹«·á°ø°³ ¼ö½Å°ÅºÎ¸¦ ¿øÇÏ½Ã¸é ¹æ¹®ÇϽþî Ãʱâȸé ÇÏ´Ü¿¡¼ ¼ö½Å°ÅºÎ¸¦ ó¸®ÇØ ÁÖ¼¼¿ä! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linux networking emulation broken?
On Thu, Feb 06, 2003 at 10:28:26PM +, David Malone wrote: > On Thu, Feb 06, 2003 at 11:00:21AM -0800, Kris Kennaway wrote: > > I'm also seeing this with Linux Phoenix, though I haven't tcpdumped > > the output. > > I'm guessing the short patch at: > > http://www.maths.tcd.ie/~dwmalone/linux_sendmsg.patch > > should help. Can you try it and let me know? > > David. Hi, After playing around yp and the patch, I got a simple result: the application runs happily without yp configured, no matter the patch applied or not. I disable yp by simply hitting "domainname ''", and re-enable it by hitting "domainname mynisdomainname". The application mentioned above is winconnect (http://www.thinsoftinc.com/products_winconnect_info.html), a RDP 5.1 capable client for Linux. I think the yp ability inside linux emulator is somewhat broken. Some other interesting output: As normal user: > id clive uid=1000(clive) gid=1000(clive) groups=1000(clive), 0(wheel), 989(samba) > /compat/linux/bin/sh do_ypcall: clnt_call: RPC: Timed out [hangs for a moment here] sh-2.04$ whoami do_ypcall: clnt_call: RPC: Timed out [hangs for a moment here] whoami: cannot find username for UID 1000 As root: > sudo su - # id clive uid=1000(clive) gid=1000(clive) groups=1000(clive), 0(wheel), 989(samba) # /compat/linux/bin/sh sh-2.04# id uid=0(root) gid=0(wheel) groups=0(wheel),5(operator) sh-2.04# id clive do_ypcall: clnt_call: RPC: Timed out [hangs for a moment here] id: clive: No such user sh-2.04# To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linux networking emulation broken?
Hi,
> On Thu, 6 Feb 2003 22:28:26 +
> David Malone <[EMAIL PROTECTED]> said:
dwmalone> On Thu, Feb 06, 2003 at 11:00:21AM -0800, Kris Kennaway wrote:
> I'm also seeing this with Linux Phoenix, though I haven't tcpdumped
> the output.
dwmalone> I'm guessing the short patch at:
dwmalone> http://www.maths.tcd.ie/~dwmalone/linux_sendmsg.patch
dwmalone> should help. Can you try it and let me know?
Oops, thanks! Though I cannot test it for now, it seems correct to
me. However, I think that where
bsd_args.msg = (caddr_t)((nmsg == NULL) ? linux_args.msg : nmsg);
it is sufficient to just substitute nmsg for bsd_args.msg:
bsd_args.msg = (caddr_t) nmsg;
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED] [EMAIL PROTECTED] ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ATA code is buggy and slower
My 5.0R kernel complains about "READ timeout" and "resetting" when I try to dd the disk. But everything *works* if I boot the same equipment with 4.5R and 4.7R. It seems that the error can occur on any sector I pick as long as I keep reading it inside a loop, a sign of timing problems. The 5.0 ATA code is so different that I am not sure where to start. If someone can show me a way to run the 4.7 ATA code under 5.0, I am willing to debug it. My equipment: Promise ATA66 controller(0x4d38105a r01), WDC WD400BB ATA/100, ATA66 cable. Also, my simple dd measurements show that performance is going down: dd if=/dev/ad4 of=/dev/null bs=8m 4.5R: 49 MB/s 4.7R: 39 MB/s 5.0R: does not finish To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: X compilation problems
> > ago.) Has anyone seen this? How do I fix it? > > Please remove your nonstandard CFLAGS and try again. Yes, that was the problem. Thank you :-) Fred -- "The first marriage is the triumph of imagination over intelligence, and the second the triumph of hope over experience." msg51915/pgp0.pgp Description: PGP signature
Re: ATA code is buggy and slower
On Fri, 2003-02-07 at 13:44, Dong Lin wrote: > My 5.0R kernel complains about "READ timeout" and "resetting" when I try > to dd the disk. But everything *works* if I boot the same equipment with > 4.5R and 4.7R. It seems that the error can occur on any sector I pick as > long as I keep reading it inside a loop, a sign of timing problems. > > The 5.0 ATA code is so different that I am not sure where to start. If > someone can show me a way to run the 4.7 ATA code under 5.0, I am > willing to debug it. > > My equipment: Promise ATA66 controller(0x4d38105a r01), WDC WD400BB > ATA/100, ATA66 cable. > > Also, my simple dd measurements show that performance is going down: > > dd if=/dev/ad4 of=/dev/null bs=8m > 4.5R: 49 MB/s > 4.7R: 39 MB/s > 5.0R: does not finish You might get more help if you sent a more complete problem description.. eg dmesg output for a start. I'm pretty sure the 5.x code is almost identical to the 4.x stuff bar extra locking calls. My Quantum fireball drive gets 35Mb/sec under both 4.5 and 4.7.. I have a WD800BB on a 4.7 box and it does 48.7 Mb/sec. -- 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 - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: se7500+dual xeon?
On Thu, 6 Feb 2003, John Baldwin wrote: > His board is a WV2, not a CW2. The WV2's should work fine though they > might need a BIOS update. I can verify the WV2's ... just built a server with one of these .. can't verify the BIOS issue, as it was upgraded before I got the machine, but have been most impressd with both the server and the chassis ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
users of the ida driver
Can someone please test for me if the following patch gets crashdumps working on the ida driver under -current? http://people.freebsd.org/~ps/ida.diff recompile and all that jazz break into DDB and type 'call doadump' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Disk problems (buffers unsynced)
Hi,
For about two weeks now, each time I halt my computer, all the buffers are not
synced (sometimes they are 1, 2 or 5).
Moreover, when I compile my custom kernel, at the linking stage ("linking
kernel.debug") I got ENOMEM at 0xadress(ad0s1g) (ad0s1g is my /usr slice) (
a time I even got a panic with XXX: free mem at bad place or something like
that)
Any ideas ?
msg51919/pgp0.pgp
Description: PGP signature
Re: ATA code is buggy and slower
It seems Dong Lin wrote: > > My 5.0R kernel complains about "READ timeout" and "resetting" when I try > to dd the disk. But everything *works* if I boot the same equipment with > 4.5R and 4.7R. It seems that the error can occur on any sector I pick as > long as I keep reading it inside a loop, a sign of timing problems. > > The 5.0 ATA code is so different that I am not sure where to start. If > someone can show me a way to run the 4.7 ATA code under 5.0, I am > willing to debug it. > > My equipment: Promise ATA66 controller(0x4d38105a r01), WDC WD400BB > ATA/100, ATA66 cable. > > Also, my simple dd measurements show that performance is going down: > > dd if=/dev/ad4 of=/dev/null bs=8m > 4.5R: 49 MB/s > 4.7R: 39 MB/s > 5.0R: does not finish Grap the ATA driver (sys/dev/ata) from -currrent, there is a bug in the 48bit support code for old promises thats not fixed in 5.0. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
xunpcb size mismatch
Hi all, I've just cvsup'd and when booting I have this warning that I do not understand uname -a FreeBSD princess.wokonet.jp 5.0-CURRENT FreeBSD 5.0-CURRENT #5: Fri Feb 7 14:40:51 JST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KERNEL2 i386 and the message is : sockstat: struct xunpcb size mismatch. What causes this? Google comes with nothing really. Thanks Cyril To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unable to boot 5.0-R CD error
Stephen Cravey <[EMAIL PROTECTED]> writes: > I'm getting an error when trying to boot any of the 5.0-RELEASE cd's > something like: > > CD Loader 1.01 > Building txxx boot loader arguments > Could not find primary volume descriptor > > > and then it dies there. txxx is illegible in my notes, but somehow I don't > think that is significant. When booting from floppy, I have to install > additional drivers from the driver floppy to be able to install from CD. > > The device line from dmesg after installation is: > > acd0: CDROM at ata1-master PIO3 > > I have a vague recollection of a problem similar to this sometime in the > 4.x tree, but specifics totally escape me. If you can boot from floppy, do that. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Server locking hard -- A LOT!!!
On Wed, 2003-02-05 at 21:03, Peter Kostouros wrote: > Hi > > I experienced the problem with kernels from last weekend. I rebuilt > yesterday, but have not undergone high loads since. I will do thorough tests > over the weekend. > > Keep in mind there have been some complaints recently, and there is new > scheduler code just implemented, so I guess at that at the moment CURRENT is > a place for the brave, well, braver than most. > > -Original Message- > From: Muhannad Asfour [mailto:[EMAIL PROTECTED]] > Sent: Thursday, 6 February 2003 12:40 PM > To: Peter Kostouros > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: RE: Server locking hard -- A LOT!!! > > > On Wed, 2003-02-05 at 20:03, Peter Kostouros wrote: > > Not sure this is much help, but I have been getting many hard locks too, > > from about a kernel I built around the 27th January. My symptoms are that > > under a relatively heavy CPU load, upon invoking or terminating an > > application, the machine occasionally terminates (abruptly). I do not even > > get core dumps. > > > > -Original Message- > > From: Muhannad Asfour [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, 6 February 2003 11:27 AM > > To: Peter Kostouros > > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > > Subject: Re: Server locking hard -- A LOT!!! > > > > > > On Wed, 2003-02-05 at 19:23, Peter Kostouros wrote: > > > Hi Muhannad > > > > > > Your dmesg output had the following: > > > lock order reversal 1st 0xc2b5d230 process lock (process lock) @ > > > ../../../kern/kern_descrip.c:2104 > > > 2nd 0xc2b5bd34 filedesc structure (filedesc structure) @ > > > ../../../kern/kern_descrip.c:2111 > > > > > > These are indicative of the lock order reversals appearing recently. Do > > you > > > always get these? > > > > > > Regards > > > > > > Peter > > > > > > This e-mail and any attachment(s) is intended for the party to which it > is > > > addressed and may contain confidential information or be subject to > > > professional privilege. Its transmission in not intended to place the > > > contents into the public domain. If you have received this e-mail in > > error, > > > please notify us immediately and delete the email and all copies. > > > AWTA Ltd does not warrant that this e-mail is virus or error free. By > > > opening this e-mail and any attachment the user assumes all > responsibility > > > for any loss or damage resulting from such action, whether or not caused > > by > > > the negligence of AWTA Ltd. > > > The contents of this e-mail and any attachments are subject to copyright > > and > > > may not be reproduced, adapted or transmitted without the prior written > > > permission of the copyright owner. > > > > Yes, I always get these. > I am experiencing the same exact thing. Odd. Any idea if it still > occurs with a more recently built kernel? I've felt like I tried everything so far, and I cannot figure out what the problem is, I've done numerous hardware tests, and every single one was passed with flying colours. I have narrowed it down to apache locking the box though. So I'm not sure what I can do to fix this, because it is very tedious to have to keep manually rebooting the box everytime it locks (sometimes 3 times a day!) Can anyone please suggest something to fix this issue? If any of the developers read this, I can give you ssh to the box if required so you can see what's happening. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
