Re: HELP WANTED: buildworld shortening options.

On Mon, Oct 21, 2002 at 07:49:13PM +0200, Poul-Henning Kamp wrote: A number of us go into release crunching mode now, and that means running make release a lot. I have totally lost track of which /etc/make.conf options we have which cuts things out of the build, so I could use some help:

Re: [PATCH] Workaround for bogus INT 12H BIOS serviceimplementation

I've recalled that FreeBSD used RTC to determine base memory size in old days. I've tested this method on my machines and confirmed it's working well. If this is done, then FreeBSD won't work on many laptops and other desktops, which report 640K for memory, but the BIOS actually steals some

HELP WANTED: buildworld shortening options.

A number of us go into release crunching mode now, and that means running make release a lot. I have totally lost track of which /etc/make.conf options we have which cuts things out of the build, so I could use some help: If somebody would make a skeleton /etc/make.conf which pulls out as much

alpha tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: zombies from linux binaries

Duncan, Duncan Barclay wrote: On 01-Oct-2002 Lars Eggert wrote: I've been running the guidescope web ad blocker (http://www.guidescope.com/home/) as a Linux binary under FreeBSD for a long time. The thing seems to fork a child for each web request it proxies. Under -current, it seems that

Re: zombies from linux binaries

Lars Eggert wrote: I've been running the guidescope web ad blocker (http://www.guidescope.com/home/) as a Linux binary under FreeBSD for a long time. The thing seems to fork a child for each web request it proxies. Under -current, it seems that the child processes become zombies, and

Re: [PATCH] Workaround for bogus INT 12H BIOS serviceimplementation

Hmmm, actually no. I know that some machines get panic with fatal trap 12 if we do 0x12 call. The worst case is getting panic, not losing 640K memory. Where does the panic occur? I checked that there is no problem here if the result of INT 0x12 is ignored and basemem is set to

Re: HELP WANTED: buildworld shortening options.

In message [EMAIL PROTECTED], Kris Kennaway writes: --4SFOXa2GPu3tIq4H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 21, 2002 at 07:49:13PM +0200, Poul-Henning Kamp wrote: =20 A number of us go into release

Re: panic: mtx_lock() of spin mutex

John Baldwin wrote: On 18-Oct-2002 Lars Eggert wrote: John Baldwin wrote: What is line 488 of src/sys/kern/kern_descrip.c? fhold(fp) in do_dup(). Hrm. You can try adding some KASSERT()'s that the reference count of that struct file isn't zero or negative. fd_refcnt is an u_short,

Re: panic: mtx_lock() of spin mutex

Lars Eggert wrote: John Baldwin wrote: On 18-Oct-2002 Lars Eggert wrote: John Baldwin wrote: What is line 488 of src/sys/kern/kern_descrip.c? fhold(fp) in do_dup(). Hrm. You can try adding some KASSERT()'s that the reference count of that struct file isn't zero or negative. fd_refcnt

GLX cmd X server crash

Failure: Xlib: extension GLX missing on display :0.0 The system did not lock; X crashed clear out. another major ongoing problem: PS/2 mouse does not track; it appears to be missing motion 'hits' and interprets some as button 1. It is impossible to use on

Re: [PATCH] re-attach cards after resume

I reported the same(+different fix) to Warner a while ago. He had troubles with his tree and didn't want to commit before he had the issues sorted out. However, it seems to me a very crucial fix. Hopefully it can be committed now. Btw, your patch is alot smaller than mine :-) (Mine was

Re: kernel panic when booting with USB CF reader

Bernd Walter wrote: On Sat, Sep 28, 2002 at 07:20:08PM -0700, Lars Eggert wrote: I'm seeing a kernel panic on -current (9/26) when booting with a SanDisk ImageMate II USB comact flash reader plugged in. The panic occurs after the kernel has loaded when the first rc.d scripts execute (dumpon,

Re: kernel panic when booting with USB CF reader

In message [EMAIL PROTECTED], Lars Eggert writes: umass0: SanDisk Corporation ImageMate CompactFlash USB, rev 1.10/0.09, addr 5 umass0: Get Max Lun not supported (STALLED) da2 at umass-sim0 bus 0 target 0 lun 0 da2: SanDisk ImageMate II 1.30 Removable Direct Access SCSI-2 device da2: 1.000MB/s

Re: kernel: lock order reversal

Alex Zepeda wrote: I see this on a fairly regular basis (at least once per 24 hour period): lock order reversal 1st 0xc0490ca0 spechash (spechash) @ ../../../kern/vfs_subr.c:2748 2nd 0xc1ed2818 vnode interlock (vnode interlock) @ ../../../kern/vfs_subr.c:2751 Dunno if it's any help, but it

ia64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

another lock order reversal

lock order reversal 1st 0xc6f47a68 vnode interlock (vnode interlock) @ /usr/src/sys/nfsclient/nfs_vnops.c:2629 2nd 0xc04b8640 vm page queue mutex (vm page queue mutex) @ /usr/src/sys/vm/vm_kern.c:424 Debugger(witness_lock) Stopped at Debugger+0x5a: xchgl %ebx,in_Debugger.0 db trace

Re: zombies from linux binaries

Terry Lambert wrote: Linux has the SVR4 behaviour in that, if SIGCHLD is not caught, zombies are reaped automatically, without the parent needing to explicitly reap their exit status. Most likely, they are installing a signal handler of SIG_IGN for SIGCHLD, and expecting the standard behaviour

yet another lock order reversal

lock order reversal 1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465 2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156 Debugger(witness_lock) Stopped at Debugger+0x5a: xchgl %ebx,in_Debugger.0 db trace

Re: [PATCH] Workaround for bogus INT 12H BIOS service implementation

On Tue, 22 Oct 2002, Mitsuru IWASAKI wrote: Hmmm, actually no. I know that some machines get panic with fatal trap 12 if we do 0x12 call. The worst case is getting panic, not losing 640K memory. ... ... FYI: On RELENG_4, this problem is critical too because this panic isn't

rl driver lock order reversal

rl0: RealTek 8139 10/100BaseTX port 0xe800-0xe8ff mem 0xd900-0xd9ff irq 11 at device 12.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode ../../../vm/uma_core.c:1307: could sleep with rl0 locked from ../../../pci/if_rl.c:872

Re: rl driver lock order reversal

How recent is your kernel? I thought I'd fixed this in recent current (at least the could sleep with rl0 part). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Building -CURRENT with 4.5-RELEASE

Is it possible, or do I need to use a more recent installation to be able to build -CURRENT? -- Gerhard To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: rl driver lock order reversal

today's source code David - Original Message - From: M. Warner Losh [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, October 22, 2002 10:20 AM Subject: Re: rl driver lock order reversal How recent is your kernel? I thought I'd fixed this in recent current

sparc64 tinderbox failure

-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: rl driver lock order reversal

In message: 00bd01c27972$5eea20f0$ef01a8c0@davidwnt David Xu [EMAIL PROTECTED] writes: : today's source code Looks like I've not committed it. :-(. Also looks like p4 told me there were no diffs for reasons unknown... This removes the lock around the attach routine. It isn't

Re: yet another lock order reversal

On 21 Oct, Lars Eggert wrote: lock order reversal 1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465 2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156 I've been complaining about that one for ages. I think I know how I want to attack it, but

Re: rl driver lock order reversal

- Original Message - From: M. Warner Losh [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, October 22, 2002 10:40 AM Subject: Re: rl driver lock order reversal In message: 00bd01c27972$5eea20f0$ef01a8c0@davidwnt David Xu [EMAIL PROTECTED]

if_dc: ethernet address now reported as 00:00:00:00:00:00

I upgraded one of my older boxes with a Linksys ethernet card this evening, and was a bit surprised to see this in dmesg: dc0: LC82C115 PNIC II 10/100BaseTX port 0xe800-0xe8ff mem 0xfebfff00-0xfebf irq 9 at device 19.0 on pci0 dc0: Ethernet address: 00:00:00:00:00:00 miibus0: MII bus on dc0

Re: [PATCH] Workaround for bogus INT 12H BIOS serviceimplementation

- vm86_intcall(0x12, vmf); - basemem = vmf.vmf_ax; + if ((basemem = rtcin(RTC_BASELO) + (rtcin(RTC_BASEHI)8)) 640) + basemem = 640; + + if (basemem == 0) { + vm86_intcall(0x12, vmf); + basemem = vmf.vmf_ax; + } + if (basemem 640)

Re: if_dc: ethernet address now reported as 00:00:00:00:00:00

In message: [EMAIL PROTECTED] Robert Watson [EMAIL PROTECTED] writes: : dc0: LC82C115 PNIC II 10/100BaseTX port 0xe800-0xe8ff mem : 0xfebfff00-0xfebf irq 9 at device 19.0 on pci0 : dc0: Ethernet address: 00:00:00:00:00:00 Maybe this is due to if_dcreg.h 1.27 and/or if_dc.c 1.80.

Re: if_dc: ethernet address now reported as 00:00:00:00:00:00

I have the same problem using a Linksys LNE100TX which uses the dc driver. I also started having problems crashing when using an SMP kernel with the same cvsup. I'm not sure if they're in anyway related. -- scott - Original Message - From: Robert Watson [EMAIL PROTECTED] To: [EMAIL

Re: if_dc: ethernet address now reported as 00:00:00:00:00:00

I have the same problem using a Linksys LNE100TX which uses the dc driver. I also started having problems crashing when using an SMP kernel with the same cvsup. I'm not sure if they're in anyway related. -- scott - Original Message - From: Robert Watson [EMAIL PROTECTED] To: [EMAIL

Re: yet another lock order reversal

On Mon, 21 Oct 2002, Lars Eggert wrote: lock order reversal 1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465 2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156 It strikes me that, for better or for worse, the reported reversal is the right

Re: if_dc: ethernet address now reported as 00:00:00:00:00:00

On Mon, 21 Oct 2002, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Robert Watson [EMAIL PROTECTED] writes: : dc0: LC82C115 PNIC II 10/100BaseTX port 0xe800-0xe8ff mem : 0xfebfff00-0xfebf irq 9 at device 19.0 on pci0 : dc0: Ethernet address: 00:00:00:00:00:00 Maybe

Re: Dedicating an interrupt to a PC-Card slot

In message: [EMAIL PROTECTED] Kenneth P. Stox [EMAIL PROTECTED] writes: : Well, I decided to have some fun and see if I could get a Novatel Merlin : C-201 wireless modem running under FreeBSD. It seems I have run into a : bit of a roadblock. It appears that the C-201 will only speak,

Re: yet another lock order reversal

On 21 Oct, Robert Watson wrote: On Mon, 21 Oct 2002, Lars Eggert wrote: lock order reversal 1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465 2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156 It strikes me that, for better or for

Re: if_dc: ethernet address now reported as 00:00:00:00:00:00

In message: [EMAIL PROTECTED] Robert Watson [EMAIL PROTECTED] writes: : : On Mon, 21 Oct 2002, M. Warner Losh wrote: : : In message: [EMAIL PROTECTED] : Robert Watson [EMAIL PROTECTED] writes: : : dc0: LC82C115 PNIC II 10/100BaseTX port 0xe800-0xe8ff mem : :

Re: Bad system call: aio_read()

On Sat, Oct 12, 2002 at 09:26:52PM +0200, Philipp Mergenthaler wrote: Where is stuff like this documented for end-users? AFAIK right now it is only documented in sys/conf/NOTES. I've sent PR docs/39748 some time back which has a patch similar to yours (I forgot about the module, though).