panic on current boot

apologies for posting this for the second time, but i think the previous subject lead most of the people to miss/skip this. i get below after installation from a floppy, flopy boots ok, the first real boot fails each time, with any current version i've tested from devel snapshot to apr 22nd. ofc

Re: DRM in the sys/ tree: looking for testers

Thank you very much, Mr. Eric Anholt, I have been testing your code on my PC, and found that kernel cannot initialize agpgart device so far. Environment: Dell Latitude C400 (w/ Intel 82830 aka I830MG) FreeBSD 4.5 STABLE (last cvsuped around 2002/Apr/24) XFree86 4.2.0 (using /usr/po

Re: Minor things: swi_net: unregistered isr number

On Thu, 25 Apr 2002, Peter Wemm wrote: > This is well known. If we recieve an ARP frame before we sent one, then > we print this. eg: a broadcast ARP packet will trigger it. dhclient > etc use bpf etc so ARP isn't initialized at this point. We could just put this block of code from arp_rtreque

Re: Minor things: swi_net: unregistered isr number

John Baldwin wrote: > On 25-Apr-2002 Jan Stocker wrote: > > My -current system gives me a > > > > swi_net: unregistered isr number: 18. > > > > too. I cant find any reply to this old subject. May anyone know where it > > comes from? > > It seems to trigger whenever there is traffic while the IP i

free: address 0x3ce000(0x3ce000) has not been allocated.

This from the trustedbsd_mac branch -- malloc is largely untouched (except for a patch I sent to Jeff from Brian Feldman that re-introduces memory trashing on free), and specfs is untouched, so probably also applies to recent -CURRENT. This could well be the malloc debugging panic some others ha

RE: linux broken?

On Thu, 25 Apr 2002, John Baldwin wrote: > > On 25-Apr-2002 Julian Elischer wrote: > > kldload sysvipc.ko or compile the SYSV stuff into your kernel. > Perhaps the linux kld needs to have a module dependency on > the sysvipc modules? there is no sysvipc module but this is what I tried.. jul

RE: linux broken?

On Thu, 25 Apr 2002, John Baldwin wrote: > > kldload sysvipc.ko or compile the SYSV stuff into your kernel. > Perhaps the linux kld needs to have a module dependency on > the sysvipc modules? I did.. it make no difference. > > > julian > > -- > > John Baldwin <[EMAIL PROTECTED]> <>< htt

Re: nVidia nForce 420

Maxim M. Kazachek wrote: > Does nVidia nForce 420D chipset is supported by FreeBSD? I'm looking for > motherboard upgrade and trying to choose chipset... > I've booted my 2 week old FreeBSD on a Gigabyte 7ZXE motherboard... I > don't like messages I saw... I'm thinked about Irongate+VIA686B > sout

nVidia nForce 420

Does nVidia nForce 420D chipset is supported by FreeBSD? I'm looking for motherboard upgrade and trying to choose chipset... I've booted my 2 week old FreeBSD on a Gigabyte 7ZXE motherboard... I don't like messages I saw... I'm thinked about Irongate+VIA686B soutbridge... But it seems that it have

Re: Revision 1.88 of kern_linker.c breaks module loading for diskless

> In message <[EMAIL PROTECTED]>, Harti Brandt write > s: > >the check for rootdev != NODEV introduced in rev 1.88 breaks loading of > >kernel modules from an NFS mounted root in diskless configurations. > >Dropping in gdb and printing rootdev shows -1 which is, I assume, NODEV. > > Ah, that woul

Re: Minor things: swi_net: unregistered isr number

John Baldwin wrote: > > On 25-Apr-2002 Jan Stocker wrote: > > My -current system gives me a > > > > swi_net: unregistered isr number: 18. > > > > too. I cant find any reply to this old subject. May anyone know where it > > comes from? > > It seems to trigger whenever there is traffic while th

Re: Revision 1.88 of kern_linker.c breaks module loading for diskless

In message <[EMAIL PROTECTED]>, Harti Brandt write s: >the check for rootdev != NODEV introduced in rev 1.88 breaks loading of >kernel modules from an NFS mounted root in diskless configurations. >Dropping in gdb and printing rootdev shows -1 which is, I assume, NODEV. Ah, that would explain a pr

Re: panic at shutdown, ums related?

On 24 Apr, Terry Lambert wrote: >> USB is pretty hosed. :-( >> >> For a while, removing the mouse didn't get detected and you had to kill moused >> manually. Then the removal event happened. A new moused would start but it >> was impossible to kill -9 the old moused. If you remove the mouse a

Problems installing -Current on Dell Power Edge 4100

Hello, We are trying to convert a Dell Power Edge 4100 Server at work to a good use (from running NT Server 4.0) to FreeBSD. After installing either -current or 4.5, then rebooting the system does not try and boot at all when hitting 'F1'. No error(s) or messages of any kind…it just does not see

Re: Minor things: swi_net: unregistered isr number

On 25-Apr-2002 Jan Stocker wrote: > My -current system gives me a > > swi_net: unregistered isr number: 18. > > too. I cant find any reply to this old subject. May anyone know where it > comes from? It seems to trigger whenever there is traffic while the IP is 0.0.0.0, even for non-DHCP stuff

Re: Minor things: swi_net: unregistered isr number

My -current system gives me a swi_net: unregistered isr number: 18. too. I cant find any reply to this old subject. May anyone know where it comes from? Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Spin lock (?) problems with MUTEX_PROFILING

On 25-Apr-2002 Dag-Erling Smorgrav wrote: > John Baldwin <[EMAIL PROTECTED]> writes: >> This means WITNESS is broken with MUTEX_PROFIING (I guess they were >> never tested together without WITNESS_SKIPSPIN). > > WITNESS makes my box about as useful as a heap of bricks, so no, > MUTEX_PROFILING w

Re: Locking down a socket, milestone 1

In article <[EMAIL PROTECTED]> you write: >I am now working on locking down a socket. (I have heard that Jeffrey >Hsu is also doing that, but I have never seen his patch. Has anyone >seen that?) I have. :-) I do coarse-grain locking at the inpcb and sockbuf level as is done in BSD/OS. This is

Re: 4 panics under 5.0 on ports cluster

On Thu, Apr 25, 2002 at 02:06:51PM -0400, John Baldwin wrote: > You have stale kernels. Yes, as noted the cluster has been running for a few weeks with March 31 kernels. I'll try again with WITNESS enabled next time I update them. Kris msg37704/pgp0.pgp Description: PGP signature

Re: 4 panics under 5.0 on ports cluster

On 25-Apr-2002 Kris Kennaway wrote: > On Thu, Apr 25, 2002 at 01:10:50PM -0400, John Baldwin wrote: >> >> On 25-Apr-2002 Kris Kennaway wrote: >> > panic: sleeping thread owns a mutex >> > Uptime: 8h52m59s >> > (kgdb) bt >> >#0 dumpsys () at /local0/scratch/usr/src/sys/kern/kern_shutdown.c:506 >

Re: Locking down a socket, milestone 1

If you compare the two approaches, the BSD/OS approach is simpler because it is coarse. You're confusing finer grain locking with better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: 4 panics under 5.0 on ports cluster

On Thu, Apr 25, 2002 at 01:10:50PM -0400, John Baldwin wrote: > > On 25-Apr-2002 Kris Kennaway wrote: > > panic: sleeping thread owns a mutex > > Uptime: 8h52m59s > > (kgdb) bt > >#0 dumpsys () at /local0/scratch/usr/src/sys/kern/kern_shutdown.c:506 > >#1 0xc0207cb0 in boot (howto=260) at > >#/

Re: Spin lock (?) problems with MUTEX_PROFILING

John Baldwin <[EMAIL PROTECTED]> writes: > This means WITNESS is broken with MUTEX_PROFIING (I guess they were > never tested together without WITNESS_SKIPSPIN). WITNESS makes my box about as useful as a heap of bricks, so no, MUTEX_PROFILING was never tested with WITNESS. >

Re: Locking down a socket, milestone 1

* Jeffrey Hsu <[EMAIL PROTECTED]> [020425 10:50] wrote: > In article <[EMAIL PROTECTED]> you write: > >I am now working on locking down a socket. (I have heard that Jeffrey > >Hsu is also doing that, but I have never seen his patch. Has anyone > >seen that?) > > I have. :-) I do coarse-grain l

Revision 1.88 of kern_linker.c breaks module loading for diskless

Hello, the check for rootdev != NODEV introduced in rev 1.88 breaks loading of kernel modules from an NFS mounted root in diskless configurations. Dropping in gdb and printing rootdev shows -1 which is, I assume, NODEV. This worked before without problems. harti -- harti brandt, http://www.fok

RE: linux broken?

On 25-Apr-2002 Julian Elischer wrote: > > > after a complete resup, re-checkout and recompile > on trying to load the linux module: > > link_elf: symbol semop undefined > > > Anyone have a quick fix? kldload sysvipc.ko or compile the SYSV stuff into your kernel. Perhaps the linux kld ne

RE: 4 panics under 5.0 on ports cluster

On 25-Apr-2002 Kris Kennaway wrote: > panic: sleeping thread owns a mutex > Uptime: 8h52m59s > (kgdb) bt >#0 dumpsys () at /local0/scratch/usr/src/sys/kern/kern_shutdown.c:506 >#1 0xc0207cb0 in boot (howto=260) at >#/local0/scratch/usr/src/sys/kern/kern_shutdown.c:338 >#2 0xc020814f in panic (

RE: Spin lock (?) problems with MUTEX_PROFILING

On 24-Apr-2002 Hiten Pandya wrote: > Hi all, > > I am not generating a false alarm, but I compiled a fresh kernel > yesterday with the MUTEX_PROFILING option, and it just went haywire just > after the FreeBSD copyright messages and the build info: > > [ Copyright Info ] > [ Build In

Re: FreeBSD security hole?

Kris Kennaway wrote: > On Thu, Apr 25, 2002 at 02:22:10PM +0600, Vladimir G. Drobyshevsky wrote: > >>Have a nice day! >> >> Yesterday I received that message from one of linux guys: > > > Perhaps you should read the security advisories we release. I never saw this, and thought I was subscribe

Re: FreeBSD security hole?

On Thu, Apr 25, 2002 at 02:56:26PM +0600, Vladimir G. Drobyshevsky wrote: > Hello all! > > >> stdio kernel bug in All releases of FreeBSD up to and including 4.5-RELEASE > >> decided to make a trivial exploit to easily get root :) > > CW> Indeed, see security advisory FreeBSD-SA-02:23.stdio at:

Cash Out

Don't be raped by high interest rates! http://211.91.3.16/cl5/index.php Some types of rates start under 5% Fed will most likly begin to raise rates soon. Take 2 minutes for a FREE Quote! http://211.91.3.16/cl5/index.php Mortgage rates have NEVER been lower. Is your credit good?

A sigio lock (was: Re: Locking down a socket, milestone 1)

On Thu, 25 Apr 2002 18:01:51 +0900, Seigo Tanimura <[EMAIL PROTECTED]> said: Seigo> On Thu, 25 Apr 2002 01:36:44 -0700, Seigo> Alfred Perlstein <[EMAIL PROTECTED]> said: bright> * Seigo Tanimura <[EMAIL PROTECTED]> [020425 01:19] wrote: >>> >> >>> >> http://people.FreeBSD.org/~tanimura/patc

Re: FreeBSD 5.0 Developer Preview #1 Now Available / diskless booting

On Wed, 24 Apr 2002, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > "David O'Brien" <[EMAIL PROTECTED]> writes: > : On Tue, Apr 23, 2002 at 12:19:58PM -0400, Robert Watson wrote: > : > diskless_root_readonly="NO" # Make it "YES" for readonly > : > : good. > >

linux broken?

after a complete resup, re-checkout and recompile on trying to load the linux module: link_elf: symbol semop undefined Anyone have a quick fix? julian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: PPPoE using aue ethernet goes kernel panic

matusita> I must provide more detailed information, but here's quick report. Using trace command, this panic is caused by: usbd_open_pipe_ival(c40416e0, 1, c8148858, ) at usbd_open_pipe_ival+0x1d usbd_open_pipe(c40416e0, 81, 1, c8148858, c40769c0, c8148880, 2, 1, c81488

PPPoE using aue ethernet goes kernel panic

Following are observed with 5-current kernel as of Apr/25/2002. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x6 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01898d1 stack pointer = 0x10:0xc9476b24 frame pointe

Re: Locking down a socket, milestone 1

On Thu, 25 Apr 2002 01:36:44 -0700, Alfred Perlstein <[EMAIL PROTECTED]> said: bright> * Seigo Tanimura <[EMAIL PROTECTED]> [020425 01:19] wrote: >> >> >> >> http://people.FreeBSD.org/~tanimura/patches/socket_milestone1.diff.gz >> >> bright> Why is there a "sigio" lock in this delta? I shou

Re[2]: FreeBSD security hole?

Hello all! >> stdio kernel bug in All releases of FreeBSD up to and including 4.5-RELEASE >> decided to make a trivial exploit to easily get root :) CW> Indeed, see security advisory FreeBSD-SA-02:23.stdio at: CW> ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-02:23.stdio.asc CW> P

Re: FreeBSD security hole?

On Thu, Apr 25, 2002 at 02:22:10PM +0600, Vladimir G. Drobyshevsky wrote: > Have a nice day! > > Yesterday I received that message from one of linux guys: Perhaps you should read the security advisories we release. Kris msg37685/pgp0.pgp Description: PGP signature

4 panics under 5.0 on ports cluster

I've had 4 panics on the ports cluster in the past couple of days. They're running kernels from March 31 which have been very stable since then, but on the other hand I've been building packages intensively for the past few days. Is there anything interesting here? I have the cores if more infor

Re: Locking down a socket, milestone 1

* Seigo Tanimura <[EMAIL PROTECTED]> [020425 01:19] wrote: > >> > >> http://people.FreeBSD.org/~tanimura/patches/socket_milestone1.diff.gz > >> This looks really good so far! Needs some more comments explaining socq_lock. Watch long line wraps. Why is there a "sigio" lock in this delta? --

Re: FreeBSD security hole?

Hello, > stdio kernel bug in All releases of FreeBSD up to and including 4.5-RELEASE > decided to make a trivial exploit to easily get root :) Indeed, see security advisory FreeBSD-SA-02:23.stdio at: ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-02:23.stdio.asc Please

FreeBSD security hole?

Have a nice day! Yesterday I received that message from one of linux guys: --- forward message --- /* phased/b10z [EMAIL PROTECTED] 23/04/2002 stdio kernel bug in All releases of FreeBSD up to and including 4.5-RELEASE decided to make a trivial exploit to easily g

Re: Locking down a socket, milestone 1

On Wed, 24 Apr 2002 10:18:01 -0400 (EDT), John Baldwin <[EMAIL PROTECTED]> said: jhb> On 24-Apr-2002 Seigo Tanimura wrote: >> I am now working on locking down a socket. (I have heard that Jeffrey >> Hsu is also doing that, but I have never seen his patch. Has anyone >> seen that?) My first mi

Re: Locking down a socket, milestone 1

On Wed, 24 Apr 2002 08:57:41 -0400, Bosko Milekic <[EMAIL PROTECTED]> said: bmilekic> I've literally just had time to glance at this so far, but can you, if bmilekic> you don't mind, please just briefly explain what BSD/OS does with bmilekic> sockbuf locking (do they use the same lock, or...?)