Re: PCI brokenness
On Wed, Oct 02, 2002 at 08:41:10AM +0900, Mitsuru IWASAKI wrote:
> Hi,
>
[...]
> > Can you try with the stuff I committed yesterday? It fixed the case (for
> > my tests at least) of legacy0 failing to attach or probe when acpi failed
> > to attach.
>
> If still failed, please try this.
> I've noticed that no chance to call pci_cfgregopen() before probing
> PCI children in case Host PCI bridge _CRS is not method or _INI method
> don't access to PCI config space or something.
>
> Thanks
>
> Index: acpi_pcib_acpi.c
> ===
> RCS file: /home/ncvs/src/sys/dev/acpica/acpi_pcib_acpi.c,v
> retrieving revision 1.23
> diff -u -r1.23 acpi_pcib_acpi.c
> --- acpi_pcib_acpi.c 26 Aug 2002 18:30:27 - 1.23
> +++ acpi_pcib_acpi.c 1 Oct 2002 23:17:51 -
> @@ -114,6 +115,9 @@
> !acpi_disabled("pci") &&
> acpi_MatchHid(dev, "PNP0A03")) {
>
> + if (!pci_cfgregopen())
> + return(ENXIO);
> +
> /*
>* Set device description
>*/
> Index: acpi_pcib_pci.c
> ===
> RCS file: /home/ncvs/src/sys/dev/acpica/acpi_pcib_pci.c,v
> retrieving revision 1.1
> diff -u -r1.1 acpi_pcib_pci.c
> --- acpi_pcib_pci.c 26 Aug 2002 18:30:27 - 1.1
> +++ acpi_pcib_pci.c 1 Oct 2002 23:18:38 -
> @@ -114,6 +115,9 @@
> return (ENXIO);
> if (acpi_get_handle(dev) == NULL)
> return (ENXIO);
> +if (!pci_cfgregopen())
> + return (ENXIO);
> +
> device_set_desc(dev, "ACPI PCI-PCI bridge");
> return (-1000);
> }
Thanks! - this patch fixes the problems I've had with missing
PCI devices.
Regards,
Niels Chr.
--
Niels Christian Bank-Pedersen, NCB1-RIPE.
"Hey, are any of you guys out there actually *using* RFC 2549?"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ATA driver broken?
On Sat, Sep 28, 2002 at 05:55:02PM +0100, Mark Murray wrote: > Hi > > I can't boot a kernel after my 22nd Sept one. The ATA disk controller > does not probe at all, and no bootable disk is found by the kernel. > > The machine is a Toshiba Libretto 110CT. I'm seeing the same (sortof) on my Dual PIII machine - ATA as well as ISA (PCI-ISA bridge), SCSI (sym) and NIC (fxp) has dissapeared recently. I was suspecting the legacy(4) commits on the 23rd to be causing this. Boot messages (before/after) attached. [...] /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. "Hey, are any of you guys out there actually *using* RFC 2549?" Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS drive E: is disk3 BIOS drive F: is disk4 BIOS drive G: is disk5 BIOS 635kB/1047488kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Fri Sep 27 19:22:18 CEST 2002) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x23a018 data=0x310d4+0x3f9cc syms=[0x4+0x2f600+0x4+0x390ba] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 9 seconds... Type '?' for a list of commands, 'help' for more detailed help. OK unload OK boot kernel.old /boot/kernel.old/kernel text=0x236c40 data=0x30df4+0x3f76c syms=[0x4+0x2eb40+0x4+0x38a17] /boot/kernel.old/acpi.ko text=0x37254 data=0x1a84+0x6e0 syms=[0x4+0x5540+0x4+0x702d] Copyright (c) 1992-2002 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-CURRENT #0: Mon Sep 16 22:10:00 CEST 2002 [EMAIL PROTECTED]:/data/usr/obj/raid01/usr/src/sys/MONSTER Preloaded elf kernel "/boot/kernel.old/kernel" at 0xc0458000. Preloaded elf module "/boot/kernel.old/acpi.ko" at 0xc04580ac. Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (448.88-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 1073676288 (1048512K bytes) avail memory = 1037463552 (1013148K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Pentium Pro MTRR support enabled Using $PIR table, 8 entries at 0xc00fdf40 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0xc08-0xc0b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_button0: on acpi0 pcib1: port 0xcf8-0xcff on acpi0 pci0: on pcib1 IOAPIC #0 intpin 21 -> irq 2 IOAPIC #0 intpin 22 -> irq 9 IOAPIC #0 intpin 20 -> irq 10 sym0: <875> port 0x1400-0x14ff mem 0xfa10-0xfa100fff,0xfa103000-0xfa1030ff irq 2 at device 13.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: <875> port 0x1800-0x18ff mem 0xfa101000-0xfa101fff,0xfa103400-0xfa1034ff irq 9 at device 13.1 on pci0 sym1: No NVRAM, ID 7, Fast-20, SE, parity checking fxp0: port 0x1060-0x107f mem 0xfa00-0xfa0f,0xfa104000-0xfa104fff irq 10 at device 15.0 on pci0 fxp0: Ethernet address 00:90:27:73:c2:02 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 18.0 on pci0 isa0: on isab0 atapci0: port 0x1050-0x105f at device 18.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 18.2 (no driver attached) Timecounter "PIIX" frequency 3579545 Hz pci0: at device 18.3 (no driver attached) pci0: at device 20.0 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x378-0x37f,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A, console orm0: at iomem 0xe4000-0xe7fff,0xcc000-0xcc7ff,0xc8000-0xcbfff,0xc-0xc7fff on isa0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Timecounters tick every 10.000 msec ad0: DMA limited to UDMA33, non-ATA66 cable or device ad0: 76345MB [155114/16/63] at ata0-master UDMA33 Waiting 5 seconds for SCSI devices to settle da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabl
Re: buildworld failed...
On Mon, Jun 24, 2002 at 11:49:02PM +0400, Sergey A. Osokin wrote: > Hello. > > Here is the today buildworld: > -- > >>> Rebuilding the temporary build tree > -- > . > -- > >>> stage 1: bootstrap tools > -- > . > ===> gnu/usr.bin/groff/src/preproc/eqn > . > c++ -O -pipe -march=pentiumpro >-I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../../../../contrib/groff/src/preproc/eqn > -I. -DHAVE_STDLIB_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 >-DHAVE_STRING_H=1 -DHAVE_STRINGS_H=1 -DHAVE_MATH_H=1 -DRET_TYPE_SRAND_IS_VOID=1 >-DHAVE_SYS_NERR=1 -DHAVE_SYS_ERRLIST=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void >-DHAVE_STRUCT_EXCEPTION=1 -DHAVE_GETPAGESIZE=1 -DHAVE_MMAP=1 -DHAVE_FMOD=1 >-DHAVE_STRTOL=1 -DHAVE_GETCWD=1 -DHAVE_STRERROR=1 -DHAVE_PUTENV=1 -DHAVE_RENAME=1 >-DHAVE_MKSTEMP=1 -DHAVE_STRCASECMP=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRSEP=1 >-DHAVE_STRDUP=1 -DSYS_SIGLIST_DECLARED=1 >-I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../../../../contrib/groff/src/include > -I/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../src/include >-D__FBSDID=__RCSID -fno-rtti -fno-exceptions -static -o eqn eqn.o main.o lex.o box.o >limit.o list.o over.o text.o script.o mark.o other.o delim.o sqrt.o pile.o special.o >/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../src/libs/libgroff/libgroff.a > make: don't know how to make neqn. Stop It looks as if your box was last updated on Apr. 13. - there was a window of a few hours where make(1) was broken. If this is the case, the following should solve your problem. cd /usr/src/usr.bin/make make clean && make depend && make && make install make clean && make cleandepend cd /usr/src make buildworld > Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: machine/endian.h revision 1.33 breaks port x11-fm/gentoo
On Sun, May 19, 2002 at 12:32:07AM +0200, Oliver Braun wrote: > Hi, > > I am the ports maintainer of x11-fm/gentoo. Building gentoo dies since > revision 1.33 of machine/endian.h with the following error: > > In file included from cmdseq.c:18: > /usr/include/sys/wait.h:114: duplicate member `w_Filler' > /usr/include/sys/wait.h:115: duplicate member `w_Retcode' > /usr/include/sys/wait.h:116: duplicate member `w_Coredump' > /usr/include/sys/wait.h:117: duplicate member `w_Termsig' > /usr/include/sys/wait.h:132: duplicate member `w_Filler' > /usr/include/sys/wait.h:133: duplicate member `w_Stopsig' > /usr/include/sys/wait.h:134: duplicate member `w_Stopval' > *** Error code 1 > > With machine/endian.h revision 1.32 it works. > > A workaround for x11-fm/gentoo is to declare the functions needed > explicit and avoid including whole sys/wait.h. Same problem (and workaround) exists for comms/gnokii (not that the workaround matters too much, xgnokii still cores for me). [...] > Olli /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: i386 tinderbox failure
On Sat, May 25, 2002 at 12:22:57PM -0700, Peter Wemm wrote:
> Dag-Erling Smorgrav wrote:
> > Peter Wemm <[EMAIL PROTECTED]> writes:
> > > Indeed it is installed. Note that you have exposed a fundamental bug
> > > in the perl wrapper. It only searches $PATH, and /usr/local/bin is not
> > > in $PATH for many system tools (eg: pkg_add -r).
> >
> > How about this:
> >
> > Index: perl.c
> > ===
> > RCS file: /home/ncvs/src/usr.bin/perl/perl.c,v
> > retrieving revision 1.2
> > diff -u -u -r1.2 perl.c
> > --- perl.c 18 May 2002 05:33:28 - 1.2
> > +++ perl.c 25 May 2002 12:52:43 -
> > @@ -59,5 +59,6 @@
> > if (errno != ENOENT)
> > err(1, "%s", path);
> > }
> > + execve("/usr/local/bin/perl", argv, environ);
> > errx(1, "Perl is not installed, try 'pkg_add -r perl'");
> > }
> >
> > Of course, it won't work if Perl was installed with a non-standard
> > PREFIX.
>
> That would work, but IMHO this should be the first location we try since it
> is the "most likely" location for it.
>
> Another idea. Suppose we have /etc/ports.conf or /etc/pkg.conf which is a
> symlink to the base of the installed location of ports/packages? (like we
> do with /etc/malloc.conf being a symlink). We could exec
> /etc/ports.conf/bin/perl as a last resort too. It would look pretty freaky
> but would be faster than parsing a text config file. pkg_add could do a
> readlink("/etc/ports.conf") to set the default for pkg_add -p as
> well.
Why not make the link as "/etc/localbase" or somesuch - "*.conf"
sort of implies that it is a file for editing (well, most files
in /etc are, but anyway). Makes it a little less freaky to me.
> -Peter
/Niels Chr.
--
Niels Christian Bank-Pedersen, NCB1-RIPE.
"Hey, are any of you guys out there actually *using* RFC 2549?"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make world stops...
On Sun, Apr 14, 2002 at 07:22:33PM +0200, Jeroen Ruigrok/asmodai wrote: > -On [20020414 19:14], Matthias Schuendehuette ([EMAIL PROTECTED]) wrote: > >make: don't know how to make neqn. Stop > >*** Error code 2 > > I think David O`Brien fixed this by backing out a commit to make. I don't think he fixed the bootstrapping issue if you've build world between 1.17 and 1.20. `make clean depend && make all install' in /usr/src/usr.bin/make fixed it for me, though. > In general, wait a couple of hours or a day before reporting a failure, > since chances are good it has already been fixed. > > -- > Jeroen Ruigrok van der Werven / asmodai / Kita no Mono > asmodai@[wxs.nl|xmach.org], finger [EMAIL PROTECTED] > http://www.softweyr.com/asmodai/ | http://www.[tendra|xmach].org/ > Like cures like... > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, TDC, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -CURRENT as of 14 Jan seems slow
On Tue, Jan 15, 2002 at 04:56:03PM -0800, David Wolfskill wrote: [...] > > I gather no one else has noticed this? Not here at least (timestamps are CET): note% ls -l /var/log/build/buildworld.log* -rw-r--r-- 1 root wheel 5728428 15 Jan 22:58 /var/log/build/buildworld.log -rw-r--r-- 1 root wheel 5727901 12 Jan 15:14 /var/log/build/buildworld.log.0 -rw-r--r-- 1 root wheel 5728013 11 Jan 04:35 /var/log/build/buildworld.log.1 -rw-r--r-- 1 root wheel 5701184 5 Jan 18:34 /var/log/build/buildworld.log.2 -rw-r--r-- 1 root wheel 5701184 5 Jan 18:34 /var/log/build/buildworld.log.3 note% egrep ' real.* user.* sys' /var/log/build/buildworld.log* /var/log/build/buildworld.log: 3860,96 real 2480,12 user 513,99 sys /var/log/build/buildworld.log.0: 4310,09 real 2948,09 user 560,00 sys /var/log/build/buildworld.log.1: 8044,91 real 2941,55 user 555,54 sys /var/log/build/buildworld.log.2: 4099,63 real 2935,31 user 562,73 sys /var/log/build/buildworld.log.3: 4099,63 real 2935,31 user 562,73 sys > david Cheers, Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current broken ?
On Thu, Dec 06, 2001 at 02:26:31AM +0100, Martin Heller wrote: > The 'make buildworld' stops while doing the 'make depend'-stage in the > usr.sbin/keyserv/ directory with an 'Error 2' . > Sources 2h old , current system 24h. I think the breakage is actually pam related and occurs in usr.bin/login: ===> usr.bin/login cd /usr/src/usr.sbin/gifconfig; make _EXTRADEPEND echo gifconfig: /usr/obj/usr/src/i386/usr/lib/libc.a >> .depend ===> usr.sbin/ifmcstat rm -f .depend mkdep -f .depend -a-DLOGIN_ACCESS -DLOGALL -I/usr/obj/usr/src/i386/usr/include /usr/src/usr.bin/login/login.c /usr/src/usr.bin/login/login_access.c / usr/src/usr.bin/login/login_fbtab.c cd /usr/src/gnu/usr.bin/cc/c++filt; make _EXTRADEPEND rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include /usr/src/usr.sbin/ifmcstat/ifmcstat.c echo c++filt: /usr/obj/usr/src/i386/usr/lib/libc.a >> .depend ===> gnu/usr.bin/cc/doc In file included from /usr/src/usr.bin/login/login.c:78: /usr/obj/usr/src/i386/usr/include/security/pam_misc.h:10: security/pam_client.h: No such file or directory cd /usr/src/usr.sbin/ifmcstat; make _EXTRADEPEND echo ifmcstat: /usr/obj/usr/src/i386/usr/lib/libc.a /usr/obj/usr/src/i386/usr/lib/libkvm.a >> .depend ===> usr.sbin/inetd ===> gnu/usr.bin/cc/cc1obj mkdep: compile failed *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 It appears that pam_client.h isn't pulled in from libpamc/include/security /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ELF interpreter /co not found
On Sat, Aug 18, 2001 at 02:34:35AM +0100, Pierre Y. Dampure wrote: > > The above message is what I get after upgrading from an August 7 to > an August 17 world/kernel and trying to run > linux-netscape47-communicator. Prior world/kernel combination worked > okay, there have been no changes to the kernel configuration (which > I can provide if required). I see this as well. Apparantly version 1.98 of sys/kern/imgact_elf.c causes the string containing the path to /compat/linux/lib/ld-2.1.2.so to be truncated. A quick workaround is to symlink /co to /compat/linux/lib/ld-2.1.2.so . > I noticed some recent changes to imgact_elf.c (which stands at > version 1.99 on the box affected), am I missing something else here? > > Regards, > > PYD > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, TDC, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipfilter+ipv6 - what am I missing?
On Sun, Jul 01, 2001 at 09:33:27PM +0200, Gerhard Sittig wrote: > On Sun, Jul 01, 2001 at 10:54 -0700, matt wrote: > > > > I don't think ipf is complete in its ipv6 support yet.You can > > use ipfw instead. > > Ipf has been supporting IPv6 for quite some time. It's just that > one has to enable this support in the Makefile. > > $ grep INET6 contrib/ipfilter/Makefile > #INET6=-DUSE_INET6 > MFLAGS1='CFLAGS=$(CFLAGS) $(ARCHINC) $(SOLARIS2) $(INET6)' \ > [ ... ] Thanks for the pointer - hadn't seen that (makes me wonder if we need a general ipv6 switch in /etc/defaults/make.conf?). Unfortunately I still can't convince ifilter to notice/block ipv6 packets :-( > And ISTR that one has to add "-6" to the ipf(8) invocation > options (like, in /etc/rc.conf). Yup, went there, did that - the following is taken from an ipv6 telnet session going throug the firewall (after make world with INET6=-DUSE_INET6): bm# ipfstat -6io block out quick on xl0 from any to any block out quick on vx0 from any to any block in quick on xl0 from any to any block in quick on vx0 from any to any bm# ipfstat -6 IPv6 packets: in 0 out 0 [..] /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, TDC, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ipfilter+ipv6 - what am I missing?
Hi, On yesterdays -current I'm having some problems making ipfilter DTRT with ipv6 packets: bm# ipfstat -6io block out quick on xl0 from any to any block out quick on vx0 from any to any block in quick on xl0 from any to any block in quick on vx0 from any to any (passing ipv6 traffic) bm# ipfstat -6 IPv6 packets: in 0 out 0 Even with the above ruleset installed, ipfilter doesn't block any traffic at all, and counters for ipv6 packets remains at zero while successfully running various ipv6 sessions through the firewall, so what am I missing here? Feel free to flame me if I am missing the obvious :-) /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, TDC, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic during -CURRENT buildworld
On Fri, May 18, 2001 at 09:25:59PM -0700, David Wolfskill wrote: > > I haven't seen anyone else reporting any problems similar to what I > experienced, so I'm not about to claim there's something that's > definitely broken I have seen exactly the same - the machine (IBM thinkpad T21) freezes during buildworld (or it appears to, but as you said, it's hard to say if it panic'ed when you run X). This problem appear to have been introduced sometime within the last 3-4 days. Only reason I've been silent is that I still haven't had the time to get a trace. > david Cheers, /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, TDC, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems with fsck after dirpref changes
Is it me fsck'ing up, or is fsck(8) lacking behind in the dirpref changes? Automatic boot in progress... /dev/da0s1a: BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE /dev/da0s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. /dev/da0s1a: Automatic file system check failed . . . help! Enter full pathname of shell or RETURN for /bin/sh: # fsck_ffs -b 32 / Alternate super block location: 32 ** /dev/da0s1a ** Last Mounted on ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? [yn] y 2683 files, 136083 used, 399724 free (1164 frags, 49820 blocks, 0.2% fragmentation) UPDATE STANDARD SUPERBLOCK? [yn] y * FILE SYSTEM WAS MODIFIED * Wonder if we should have seen something like this: http://www.openbsd.org/cgi-bin/cvsweb/src/sbin/fsck_ffs/setup.c.diff?r1=1.8&r2=1.9&f=h BTW, the box then panic'ed right after going multiuser, but I dunno if thats related (managed to get it running on kernel.old): Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc021ebda stack pointer = 0x10:0xdfa6ec20 frame pointer = 0x10:0xdfa6ec30 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 = 319 (named) kernel: type 12 trap, code=0 CPU1 stopping CPUs: 0x0001... stopped. Stopped at ffs_valloc+0x8e:cmpb$0,0(%edi,%eax,1) db> trace ffs_valloc(dabeb1c0,81a4,c1c54500,dfa6ec58,dfa6edb8) at ffs_valloc+0x8e ufs_makeinode(81a4,dabeb1c0,dfa6eea4,dfa6eeb8) at ufs_makeinode+0x61 ufs_create(dfa6edb8,dfa6ee2c,c01bd59f,dfa6edb8,dfa6ef80) at ufs_create+0x2b ufs_vnoperate(dfa6edb8,dfa6ef80,0,3,a02) at ufs_vnoperate+0x15 vn_open(dfa6ee90,dfa6ee5c,1a4,d9d40100,0) at vn_open+0x177 open(d9d40100,dfa6ef80,8114366,80eb062,0) at open+0xd6 syscall(2f,2f,2f,0,80eb062) at syscall+0x405 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current reliably panics during make release (current process = dd)
On a -current from this morning, I can reliably trigger a panic by "make release" (I believe the problem has existed for some time, though). The box can do make worlds without problem, but during make release, it stumples at the same place every time. This is a Dual P3 with all involved filesystems (/usr/src, /usr/obj and the chrootdir) nullfs-mounted from a SU vinum raid01 volume. monster# mount /dev/da0s1a on / (ufs, local, noatime, soft-updates) devfs on /dev (devfs, local) /dev/da3s1e on /usr (ufs, local, noatime, soft-updates) /dev/da0s1f on /var (ufs, local, noatime, soft-updates) procfs on /proc (procfs, local) /dev/vinum/vol/raid01 on /raid01 (ufs, NFS exported, local, noatime, soft-updates) /raid01/usr/src on /usr/src (nullfs, local, noatime) /raid01/usr/obj on /usr/obj (nullfs, local, noatime) /raid01/usr/ports on /usr/ports (nullfs, local, noatime) monster# The panic: Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = fault virtual address = 0x58 fault code = supervisor read, page not present instruction pointer = 0x8:0xc016749e stack pointer = 0x10:0xe009ddf4 frame pointer = 0x10:0xe009ddf4 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 = 88329 (dd) kernel: type 12 trap, code=0 CPU1 stopping CPUs: 0x0001... stopped. Stopped at devsw+0x6: cmpl$0,0x58(%eax) db> trace devsw(0,c41c3280,0,4,e0b8a36c) at devsw+0x6 vn_ioctl(c41c3280,4004667a,e009ded0,dfb3d740,dfb3d740) at vn_ioctl+0xb5 ioctl(dfb3d740,e009df80,805b5c0,bfbff868,bfbff880) at ioctl+0x20a syscall(2f,2f,2f,bfbff880,bfbff868) at syscall+0x405 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b db> I'll try to get a crashdump - 1GB (if anyone's interested?). Config attached. /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark NET, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" machine i386 cpu I686_CPU ident MONSTER maxusers128 hints "/boot/device.hints" #makeoptionsDEBUG=-g options INET options FFS options SOFTUPDATES options NFS options CD9660 options DEVFS options PROCFS options COMPAT_43 options SCSI_DELAY=5000 options UCONSOLE options USERCONFIG options VISUAL_USERCONFIG options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV options SMP options APIC_IO options DDB device isa device pci device fdc device ata #device atadisk device atapicd #device atapifd #device atapist #optionsATA_STATIC_ID device sym device scbus device da #device sa #device cd device pass device atkbdc 1 device atkbd device psm device vga device splash device sc 1 device npx device sio device ppc device ppbus device lpt device miibus device fxp device md device random device loop device ether device pty device bpf
Re: NEWCARD broken in -current
On Wed, Mar 28, 2001 at 10:09:28PM +0200, Jesper Skriver wrote: > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes >-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi >-nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/../include >-I/usr/src/sys/contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h >-elf -mpreferred-stack-boundary=2 > /usr/src/sys/dev/pccbb/pccbb.c > In file included from /usr/src/sys/dev/pccbb/pccbb.c:56: > /usr/src/sys/sys/mutex.h:87: field `mtx_object' has incomplete type > /usr/src/sys/dev/pccbb/pccbb.c: In function `pccbb_detach': > /usr/src/sys/dev/pccbb/pccbb.c:533: warning: implicit declaration of function `MPASS' > /usr/src/sys/dev/pccbb/pccbb.c:533: warning: implicit declaration of function >`LOCK_LOG_LOCK' > /usr/src/sys/dev/pccbb/pccbb.c:533: warning: implicit declaration of function >`WITNESS_LOCK' > /usr/src/sys/dev/pccbb/pccbb.c:539: warning: implicit declaration of function >`WITNESS_UNLOCK' > *** Error code 1 You'll need to #include and in /usr/src/sys/dev/pccbb/pccbb.c > /Jesper /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark NET, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: devfs+vinum trouble
On Thu, Mar 22, 2001 at 06:46:40PM +0100, Bernd Walter wrote:
> 1. The minor numbers are completely different from what I have
>without devfs.
>Without a volume is 91,0 91,1 ...
>With I get 91,0 91,0x100 91,2000 ...
>Similar plexes, ...
> 2. When I mount I get with all volume nodes the same filesystem.
>Not astonishing with the broken minors.
> 3. I have 6 volumes and only 5 devnodes in vol showed up.
>All 6 are shown with vinum list.
> 4. during vinum init I get errors:
>WARNING: Driver mistake: repeat make_dev("vinum/controld")
>WARNING: Driver mistake: repeat make_dev("vinum/Control")
>WARNING: Driver mistake: repeat make_dev("vinum/control")
>It doesn't matter if I have devfs compiled in or not.
>And I get similars during kldunload.
>
> It's on an i386 based system with source from 21th March.
Same here.
> B.Walter COSMO-Project http://www.cosmo-project.de
/Niels Chr.
--
Niels Christian Bank-Pedersen, NCB1-RIPE.
Network Manager, Tele Danmark NET, IP-section.
"Hey, are any of you guys out there actually *using* RFC 2549?"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: how's vinum these days with DEVFS?
On Sun, Mar 11, 2001 at 12:03:34AM -0800, Matthew Jacob wrote:
>
>
> On Sun, 11 Mar 2001, Greg Lehey wrote:
>
> > On Saturday, 10 March 2001 at 17:12:42 -0800, Matt Jacob wrote:
> > > (top of tree within the last day or so):
> > >
> > > Things seem *almost* okay, but:
> > >
> > > nellie.feral.com > root vinum
> > > vinum -> stripe -v /dev/da3a /dev/da4a /dev/da5a /dev/da6a /dev/da7a /dev/da8a
> > > /dev/da9a /dev/da10a /dev/da11a /dev/da12a
> > > drive vinumdrive0 device /dev/da3a
> > >
> > > Can't get config for plex 0: Invalid argument
> > >
> > > and at the console:
> > >
> > > WARNING: Driver mistake: repeat make_dev("vinum/control")
> >
> > Hmm.
> >
> > > Mar 10 17:09:57 nellie /boot/kernel/kernel: vinumioctl: invalid ioctl from
>process 682 (vinum): c1384644
> >
> > This looks like a mismatch between the plex size in the userland and
> > kernel code. Did you rebuild vinum(8)?
>
> Complete fresh build, top of tree... I'll try again...
I'll sneak in my experience with DEVFS+vinum here as well:
vinum: loaded
vinum: reading configuration from /dev/da3s1f
vinum: updating configuration from /dev/da1s1e
vinum: updating configuration from /dev/da2s1e
vinum: updating configuration from /dev/da0s1e
swapon: adding /dev/da1s1b as swap device
swapon: adding /dev/da2s1b as swap device
Automatic boot in progress...
/dev/da0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS
/dev/da0s1a: clean, 406977 free (1049 frags, 50741 blocks, 0.2% fragmentation)
Can't stat /dev/vinum/raid01: No such file or directory
Can't stat /dev/vinum/raid01: No such file or directory
/dev/vinum/raid01: CAN'T CHECK FILE SYSTEM.
/dev/vinum/raid01: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
This was with a -current from around March 1. (don't think
anything has changed since). Booting a non-DEVFS kernel
passes the fs-check and works as expected.
/Niels Chr.
--
Niels Christian Bank-Pedersen, NCB1-RIPE.
Network Manager, Tele Danmark NET, IP-section.
"Hey, are any of you guys out there actually *using* RFC 2549?"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Fatal trap 12 panic when starting vinum plex
On a very current -current, I get this reproducable panic when I try to revive a vinum plex: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 0100 fault virtual address = 0x1a0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc015f01d stack pointer = 0x10:0xdfad6ca0 frame pointer = 0x10:0xdfad6cac code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 612 (vinum) kernel: type 12 trap, code=0 CPU0 stopping CPUs: 0x0002... stopped. Stopped at mtx_enter_hard+0x125: movl0x1a0(%edx),%eax db> trace mtx_enter_hard(c28e3930,0,0,0,c28e3900) at mtx_enter_hard+0x125 _mtx_enter(c28e3930,0,c2830240,87,0) at _mtx_enter+0x132 lockrange(0,cec3f330,c28e3900,c25f6000,2) at lockrange+0x31 revive_block(2,c25f6000,c2816d00,dfa90a80,0) at revive_block+0x2f6 start_object(c25f6000,0,c2816d00,dfa90a80,d9d4ac30) at start_object+0x10d setstate(c25f6000,dfad6e08,c2816d00,c25f6000,dfad6dd8) at setstate+0x1fd vinumioctl(c2816d00,c400464c,c25f6000,3,dfa90a80) at vinumioctl+0x4c1 spec_ioctl(dfad6e08,dfad6df0,c020e5f1,dfad6e08,dfad6e98) at spec_ioctl+0x2c spec_vnoperate(dfad6e08,dfad6e98,c019e8ac,dfad6e08,c292ddc0) at spec_vnoperate+0x15 ufs_vnoperatespec(dfad6e08,c292ddc0,0,400,c0283780) at ufs_vnoperatespec+0x15 vn_ioctl(c292ddc0,c400464c,c25f6000,dfa90a80,dfa90a80) at vn_ioctl+0x110 ioctl(dfa90a80,dfad6f80,bfbff64c,bfbff1cc,2) at ioctl+0x20a syscall2(2f,2f,2f,2,bfbff1cc) at syscall2+0x2a0 Xint0x80_syscall() at Xint0x80_syscall+0x23 --- syscall 0x36, eip = 0x8072ecc, esp = 0xbfbff1a0, ebp = 0xbfbff68c --- db> Dunno if this is actually vinum, or it is caused by the mere fact that I'm trying to run -current. Anyway, it happens in UP as well as SMP, and I am not using DEVFS. Oh, one more thing: the vinum volume (raid01) apparantly runs without any problems - as long as I don't try to revive a faulty plex within the volume. /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic - probably aic7810/398X related
On Sun, Nov 12, 2000 at 02:13:39PM -0700, Justin T. Gibbs wrote:
> >Yesterday I decided to upgrade my home server from it's PRE_SMPNG
> >state to -current, but now it panics just after detecting the
> >aic7810 RAID controller (though unsupported, the box booted happily
> >on an PRE_SMPNG kernel).
>
> My guess is that this patch will fix your problem.
Indeed. Thanks.
> Justin
>
> Index: aic7xxx.c
> ===
> RCS file: /usr/cvs/src/sys/dev/aic7xxx/aic7xxx.c,v
> retrieving revision 1.60
> diff -c -r1.60 aic7xxx.c
> *** aic7xxx.c 2000/11/12 05:19:46 1.60
> --- aic7xxx.c 2000/11/12 21:11:43
> ***
> *** 3689,3694
> --- 3689,3696
> struct scb_data *scb_data;
>
> scb_data = ahc->scb_data;
> + if (scb_data == NULL)
> + return;
>
> switch (scb_data->init_level) {
> default:
>
>
/Niels Chr.
--
Niels Christian Bank-Pedersen, NCB1-RIPE.
Network Manager, Tele Danmark NET, IP-section.
"Hey, are any of you guys out there actually *using* RFC 2549?"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
panic - probably aic7810/398X related
Yesterday I decided to upgrade my home server from it's PRE_SMPNG state to -current, but now it panics just after detecting the aic7810 RAID controller (though unsupported, the box booted happily on an PRE_SMPNG kernel). The 398X adapter is one of the cards that doesn't work with AHC_ALLOW_MEMIO (as I understand it because of the PCI-PCI bridge) so I don't know if the recent changes here has something to do with it. -current: Copyright (c) 1992-2000 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-CURRENT #0: Sun Nov 12 12:39:35 CET 2000 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MAIL Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 166193999 Hz CPU: Pentium/P54C (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 134217728 (131072K bytes) avail memory = 126603264 (123636K bytes) Preloaded elf kernel "kernel" at 0xc03d4000. Preloaded elf module "vinum.ko" at 0xc03d40a8. npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 7.1 pcib1: at device 9.0 on pci0 pci1: on pcib1 ahc0: port 0xd800-0xd8ff mem 0xf900-0xf9000fff irq 9 at device 4.0 on pci1 aic7870: Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: port 0xd400-0xd4ff mem 0xfb00-0xfb1f,0xf880-0xf8800fff irq 11 at device 5.0 on pci1 RAID functionality unsupported Fatal trap 12: page fault while in kernel mode fault virtual address = 0x432 fault code = supervisor read, page not present instruction pointer = 0x8:0xc013656b stack pointer = 0x10:0xc03e8e30 frame pointer = 0x10:0xc03e8e38 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 = 0 (swapper) kernel: type 12 trap, code=0 Stopped at ahc_fini_scbdata+0xb: movzbl 0x432(%esi),%eax db> trace ahc_fini_scbdata(c0737000) at ahc_fini_scbdata+0xb ahc_free(c0737000,c0ec8080,c0efa380,c0efa180,c0283888) at ahc_free+0xd ahc_pci_attach(c0efa180,c0efa180,c0efa800,c0efa380,0) at ahc_pci_attach+0xea device_probe_and_attach(c0efa180) at device_probe_and_attach+0x8e bus_generic_attach(c0efa380,c0efa380,c0efac00,c0efa800,0) at bus_generic_attach+0x16 device_probe_and_attach(c0efa380) at device_probe_and_attach+0x8e bus_generic_attach(c0efa800,c0efa800,c0efa800,c026a65f,) at bus_generic_attach+0x16 pcib_attach(c0efa800,c0efa800,c0efac80,c0efac00,0) at pcib_attach+0x9c device_probe_and_attach(c0efa800) at device_probe_and_attach+0x8e bus_generic_attach(c0efac00,c0efac00,c0efad80,c0efac80,0) at bus_generic_attach+0x16 device_probe_and_attach(c0efac00) at device_probe_and_attach+0x8e bus_generic_attach(c0efac80,c0efac80,c027a1b8,0,c0efac80) at bus_generic_attach+0x16 nexus_pcib_attach(c0efac80,c0efac80,c0efad80,c0efad80,0) at nexus_pcib_attach+0x1f device_probe_and_attach(c0efac80) at device_probe_and_attach+0x8e bus_generic_attach(c0efad80,c0ee4080,c0738e00,c03e8fc0,c016a6ca) at bus_generic_attach+0x16 nexus_attach(c0efad80,c0efad80,c02942d0,3ed000,0) at nexus_attach+0xe device_probe_and_attach(c0efad80) at device_probe_and_attach+0x8e root_bus_configure(c0738e00,c02737ac,0) at root_bus_configure+0x16 configure(0,3e6c00,3e6000,0,c011d232) at configure+0x33 mi_startup() at mi_startup+0x68 begin() at begin+0x29 db> >From a working PRE_SMPNG kernel: Copyright (c) 1992-2000 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-CURRENT #0: Thu Nov 9 02:18:13 CET 2000 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MAIL Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 166193968 Hz CPU: Pentium/P54C (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 134217728 (131072K bytes) avail memory = 127541248 (124552K bytes) Preloaded elf kernel "kernel.ko" at 0xc02f. Preloaded elf module "randomdev.ko" at 0xc02f00a0. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 7.1 pcib1: at device 9.0 on pci0 pci1: on pcib1 ahc0: port 0xd800-0xd8ff mem 0xf900-0xf9000fff irq 9 at device 4.0 on pci1 ahc0: aic7870 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: port 0xd400-0xd4ff mem 0xfb00-0xfb1f,0xf880-0xf8800fff irq 11 at device 5.0 on pci1 RAID functionality unsupported device_probe_and_attach: ahc
Re: Latest kernel/module restructuring
On Tue, Sep 12, 2000 at 04:04:20PM +0200, Sheldon Hearn wrote: > > > On Tue, 12 Sep 2000 10:00:06 -0400, Michael Lucas wrote: > > > Some of us rebuild kernels without supping. I, for one, play with all > > sorts of kernel options to see what they do. > > Then you probably want the kernel reinstall target. I don't think that > this target is available from src/Makefile.inc1, so you'd have to use > the old style of kernel building. > > If you want something like ``make reinstallkernel'' from /usr/src to > work, you should probably ask marcel nicely. > > But the original proposal was ill-conceived and simply won't cut it. Hmm, how about those of us doing buildworlds/buildkernels on one (nfs)server for subsequent installworlds/installkernels on multiple other machines? With the current targets, you either have to build modules over and over againg for each `client', or you have to accept that /boot/kernel/* gets nuked when running installkernel (or, as you point out, one can use the old manual scheme). > Sheldon. /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Possible Vinum RAID-5 problems? (was: panic: ffs_valloc: dup alloc)
On Fri, May 19, 2000 at 06:20:44PM +0930, Greg Lehey wrote: > I only stumbled on this thread by accident. If you have problems > which involve Vinum, please copy me, and I may have input. Ok, thanks. Wasn't at all sure vinum had anything to do with this crash (and I still don't know if it has), so I didn't want to "Cry Wolf" :-) . > On Friday, 19 May 2000 at 7:55:37 +0200, Bernd Walter wrote: > > On Fri, May 19, 2000 at 06:24:39AM +0200, Niels Chr. Bank-Pedersen wrote: > >> On Fri, May 19, 2000 at 12:01:59AM +0200, Bernd Walter wrote: > >>> On Thu, May 18, 2000 at 11:43:58PM +0200, Niels Chr. Bank-Pedersen wrote: > >>>> On Thu, May 18, 2000 at 11:21:51PM +0200, Bernd Walter wrote: > >>>>> Does vinum list saying that one subdisk of your R5 volume is down? > >>>> > >>>> 5 subdisks: > >>>> S raid5.p0.s0 State: upPO:0 B Size: 4133 MB > >>>> S raid5.p0.s1 State: upPO: 768 kB Size: 4133 MB > >>>> S raid5.p0.s2 State: upPO: 1536 kB Size: 4133 MB > >>>> S raid5.p0.s3 State: upPO: 2304 kB Size: 4133 MB > >>>> S raid5.p0.s4 State: upPO: 3072 kB Size: 4133 MB > >>>> > >>>> - But since my first attempt to initialize the plex crashed the > >>>> box while only da5se1 was missing, I did a "verify media" from > >>>> the SCSI ctrl. BIOS, and did find errors. They were all successfully > >>>> remapped, though. > >>> > >>> I thought about a parity corrpution bug that there was in history. > >>> But as all drives are up and they are freshly initialized there are 2 > >>> arguments why your problems should be different. > >>> Maybe one drive crashed and the system paniced before vinum was able to update > >>> the state database on the drives. > >>> Did you saw anything unusual on the console before the panic message? > >> > >> > >> - after obliterating the vinum configuration I created the volume > >> without da5, and I have now successfully copied 250+MB to the filesystem. > >> > >> I would have thought that hardware errors like this could be handled > >> in a slightly more controlled manner, though. > > > > At this moment there is no sign of a hardware error. > > The panic itself means that the filessytem allocated a block which > > already was allocated. Usually it means that the data on the drive > > got corrupted while mounted. > > > > You should be carefully testing the volume before copying important > > data to it. In my expirience I can say that using softupdates > > stresses the I/O system much more than the standard way so it makes > > sense to test with softupdates. This is a scratch box used primarily for testing -current, so I don't have anything important on it. Which is good, 'cause as you suspected, it *did* crash again after a while. This time it was, among other things, nfs-serving a buildworld from another filesystem at the time of the crash, so I'm not too sure what triggered it this time (I only got the trace, not any of the messages from the panic): db> trace Debugger(c0245ca3) at Debugger+0x35 panic(c0253e00,c3853a40,c1259500,c3853a40,0) at panic+0x70 handle_written_inodeblock(c1259500,c3853a40) at handle_written_inodeblock+0x2b8 softdep_disk_write_complete(c3853a40) at softdep_disk_write_complete+0x6a bufdone(c3853a40,c0264ab8,c0128558,c3853a40,c0f78400) at bufdone+0x7e bufdonebio(c3853a40) at bufdonebio+0xe dadone(c0f6c680,c0f78400,c073a9a0,4200,) at dadone+0x210 camisr(c0282290,c0264b0c,c021e4e0,4200,c022e8f6) at camisr+0x1eb swi_cambio(4200,c022e8f6,c022e41f,4200,c0ec3800) at swi_cambio+0xd splz_swi(c073a9a0,0,10,10,10) at splz_swi+0x14 Xresume9() at Xresume9+0x2b --- interrupt, eip = 0xc0227a96, esp = 0xc0264b54, ebp = 0 --- default_halt() at default_halt+0x2 db> > I recently fixed a number of problems in RAID-5. Can you give me > details of the problems you've been having, and the date of the sup? > Since this is -CURRENT, I assume that's the version of the system too. It is - sources from ~3 days ago, so I believe I have all your latest fixes. > As far as soft updates goes, basically it's incompatible with Vinum, > since there's currently no way of ensuring the sequence of writes > across a number of disks. I'm thinking of ways of doing it, but they > will cause significant loss in performance. There should be no > problems as long as there isn't a crash, of course :-) I wasn't aware of the incompatibility issues, so all my vinum volumes were running with SU until a few minutes ago :-) I have turned SU off on this R5 volume now as well, but the above trace happened, with SU turned on. > Greg /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark NET, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: ffs_valloc: dup alloc
On Fri, May 19, 2000 at 12:01:59AM +0200, Bernd Walter wrote: > On Thu, May 18, 2000 at 11:43:58PM +0200, Niels Chr. Bank-Pedersen wrote: > > On Thu, May 18, 2000 at 11:21:51PM +0200, Bernd Walter wrote: > > > Does vinum list saying that one subdisk of your R5 volume is down? > > > > 5 subdisks: > > S raid5.p0.s0 State: up PO:0 B Size: 4133 MB > > S raid5.p0.s1 State: up PO: 768 kB Size: 4133 MB > > S raid5.p0.s2 State: up PO: 1536 kB Size: 4133 MB > > S raid5.p0.s3 State: up PO: 2304 kB Size: 4133 MB > > S raid5.p0.s4 State: up PO: 3072 kB Size: 4133 MB > > > > - But since my first attempt to initialize the plex crashed the > > box while only da5se1 was missing, I did a "verify media" from > > the SCSI ctrl. BIOS, and did find errors. They were all successfully > > remapped, though. > > I thought about a parity corrpution bug that there was in history. > But as all drives are up and they are freshly initialized there are 2 > arguments why your problems should be different. > Maybe one drive crashed and the system paniced before vinum was able to update > the state database on the drives. > Did you saw anything unusual on the console before the panic message? It seems to be a hardware problem with da5. After the latest crash, I had the following in dmesg: (da5:ahc4:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da5:ahc4:0:2:0): NO SENSE - after obliterating the vinum configuration I created the volume without da5, and I have now successfully copied 250+MB to the filesystem. I would have thought that hardware errors like this could be handled in a slightly more controlled manner, though. > B.Walter COSMO-Project http://www.cosmo-project.de Once again, thanks for your time. /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark NET, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: ffs_valloc: dup alloc
On Thu, May 18, 2000 at 11:21:51PM +0200, Bernd Walter wrote:
> On Thu, May 18, 2000 at 04:13:43PM +0200, Niels Chr. Bank-Pedersen wrote:
> > Hi,
> >
> > On a -current box, sources approx. 2½ days old, I'm
> > having problems using a vinum raid5 volume - usually
> > the box freezes totally when trying to use the filesystem
> > (mkdir xxx; cd xxx -> crash), but last time it dropped
> > to the debugger:
> >
> > mode = 040755, inum = 25344, fs = /raid5
> > panic: ffs_valloc: dup alloc
> > Debugger("panic")
> > Stopped at Debugger+0x35: movb$0,in_Debugger.390
> > db> trace
> > Debugger(c0245ca3) at Debugger+0x35
> > panic(c0252541,c0252520,41ed,6300,c109e0d4) at panic+0x70
> > ffs_valloc(c9e7e300,41ed,c1171400,c9e69d08,c9e69e70) at ffs_valloc+0xf8
> > ufs_mkdir(c9e69e70,c9e69f2c,c018d272,c9e69e70,c9e2c8e0) at ufs_mkdir+0x82
> > ufs_vnoperate(c9e69e70,c9e2c8e0,2,c9e69f80,c02651e0) at ufs_vnoperate+0x15
> > mkdir(c9e2c8e0,c9e69f80,bfbffc1c,1,1ff) at mkdir+0x162
> > syscall2(2f,2f,2f,1ff,1) at syscall2+0x1f1
> > Xint0x80_syscall() at Xint0x80_syscall+0x28
> > db>
> >
> > I had one crash on my first attempt initialising the volume,
> > but was able to newfs without any problems after initializing
> > succeeded on the second attempt.
> >
> > Anybody able to see what could be happening here?
> > (dmesg below, and dump/kernel.debug available)
>
> I don't know what Greg thinks about but I beleave that the dup alloc is not
> the reason itself.
> Does vinum list saying that one subdisk of your R5 volume is down?
No:
5 drives:
D raid5-00 State: up Device /dev/da1s1e Avail: 0/4133 MB (0%)
D raid5-01 State: up Device /dev/da3s1e Avail: 0/4133 MB (0%)
D raid5-02 State: up Device /dev/da5s1e Avail: 0/4133 MB (0%)
D raid5-03 State: up Device /dev/da6s1e Avail: 0/4133 MB (0%)
D raid5-04 State: up Device /dev/da7s1e Avail: 0/4133 MB (0%)
1 volumes:
V raid5 State: up Plexes: 1 Size: 16 GB
1 plexes:
P raid5.p0 R5 State: up Subdisks: 5 Size: 16 GB
5 subdisks:
S raid5.p0.s0 State: up PO:0 B Size: 4133 MB
S raid5.p0.s1 State: up PO: 768 kB Size: 4133 MB
S raid5.p0.s2 State: up PO: 1536 kB Size: 4133 MB
S raid5.p0.s3 State: up PO: 2304 kB Size: 4133 MB
S raid5.p0.s4 State: up PO: 3072 kB Size: 4133 MB
- But since my first attempt to initialize the plex crashed the
box while only da5se1 was missing, I did a "verify media" from
the SCSI ctrl. BIOS, and did find errors. They were all successfully
remapped, though.
> If yes with which version did you last initialized the plex?
Newly created plex, so that would be the currently installed version.
> Are you using softupdates?
Yup. I am unable to try without SU right now (well, I could, but if it
doesnt work, my foot will be blown of), but I'll try that later when I
get home.
> B.Walter COSMO-Project http://www.cosmo-project.de
Thnx.
/Niels Chr.
--
Niels Christian Bank-Pedersen, NCB1-RIPE.
Network Manager, Tele Danmark NET, IP-section.
"Hey, are any of you guys out there actually *using* RFC 2549?"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
panic: ffs_valloc: dup alloc
Hi,
On a -current box, sources approx. 2½ days old, I'm
having problems using a vinum raid5 volume - usually
the box freezes totally when trying to use the filesystem
(mkdir xxx; cd xxx -> crash), but last time it dropped
to the debugger:
mode = 040755, inum = 25344, fs = /raid5
panic: ffs_valloc: dup alloc
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.390
db> trace
Debugger(c0245ca3) at Debugger+0x35
panic(c0252541,c0252520,41ed,6300,c109e0d4) at panic+0x70
ffs_valloc(c9e7e300,41ed,c1171400,c9e69d08,c9e69e70) at ffs_valloc+0xf8
ufs_mkdir(c9e69e70,c9e69f2c,c018d272,c9e69e70,c9e2c8e0) at ufs_mkdir+0x82
ufs_vnoperate(c9e69e70,c9e2c8e0,2,c9e69f80,c02651e0) at ufs_vnoperate+0x15
mkdir(c9e2c8e0,c9e69f80,bfbffc1c,1,1ff) at mkdir+0x162
syscall2(2f,2f,2f,1ff,1) at syscall2+0x1f1
Xint0x80_syscall() at Xint0x80_syscall+0x28
db>
I had one crash on my first attempt initialising the volume,
but was able to newfs without any problems after initializing
succeeded on the second attempt.
Anybody able to see what could be happening here?
(dmesg below, and dump/kernel.debug available)
/Niels Chr.
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #0: Wed May 17 03:59:29 CEST 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/MAIL
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 166194046 Hz
CPU: Pentium/P54C (166.19-MHz 586-class CPU)
Origin = "GenuineIntel" Id = 0x52c Stepping = 12
Features=0x1bf
real memory = 134217728 (131072K bytes)
avail memory = 127438848 (124452K bytes)
Preloaded elf kernel "kernel" at 0xc02e9000.
npx0: on motherboard
npx0: INT 16 interface
pcib0: on motherboard
pci0: on pcib0
isab0: at device 7.0 on pci0
isa0: on isab0
pci0: at 7.1
pcib1: at device 9.0 on pci0
pci1: on pcib1
ahc0: port 0xd800-0xd8ff mem 0xf900-0xf9000fff
irq 9 at device 4.0 on pci1
ahc0: aic7870 Wide Channel A, SCSI Id=7, 16/255 SCBs
ahc1: port 0xd400-0xd4ff mem
0xfb00-0xfb1f,0xf880-0xf8800fff irq 11 at device 5.0 on pci1
RAID functionality unsupported
device_probe_and_attach: ahc1 attach returned 6
ahc2: port 0xd000-0xd0ff mem 0xf800-0xf8000fff
irq 9 at device 8.0 on pci1
ahc2: aic7870 Wide Channel B, SCSI Id=7, 16/255 SCBs
ahc3: port 0xc800-0xc8ff mem 0xf780-0xf7800fff
irq 9 at device 12.0 on pci1
ahc3: aic7870 Wide Channel C, SCSI Id=7, 16/255 SCBs
pci0: at 10.0 irq 12
ahc4: port 0xb800-0xb8ff mem 0xf680-0xf6800fff
irq 10 at device 11.0 on pci0
ahc4: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs
xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xb400-0xb43f irq 11 at device 12.0 on pci0
xl0: Ethernet address: 00:10:4b:3d:d2:79
miibus0: on xl0
nsphy0: on miibus0
nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: at port 0x60,0x64 on isa0
atkbd0: irq 1 on atkbdc0
vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0: on isa0
sc0: VGA <16 virtual consoles, flags=0x0>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: This ppc chipset does not support the extended I/O port range...no problem
ppc0: at port 0x378-0x37b irq 7 drq 1 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/15 bytes threshold
lpt0: on ppbus0
lpt0: Interrupt-driven port
unknown: can't assign resources
unknown: can't assign resources
unknown: can't assign resources
unknown: can't assign resources
unknown0: at iomem
0-0x9,0x10-0x7ff,0xe8000-0xf,0xfffe-0x on isa0
unknown: can't assign resources
unknown1: at port 0x40-0x43 irq 0 on isa0
unknown2: at port 0x70-0x71 irq 8 on isa0
unknown: can't assign resources
npxisa0: at port 0xf0 irq 13 on isa0
unknown3: at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0
unknown4: at port 0x61 on isa0
unknown5: at port 0xcf8-0xcff,0x4d0-0x4d1 on isa0
Waiting 5 seconds for SCSI devices to settle
ahc4:A:6: refuses synchronous negotiation. Using asynchronous transfers
ahc4:A:6: refuses synchronous negotiation. Using asynchronous transfers
sa0 at ahc4 bus 0 target 6 lun 0
sa0: Removable Sequential Access SCSI-2 device
sa0: 3.300MB/s transfers
da7 at ahc4 bus 0 target 4 lun 0
da7: Fixed Direct Access SCSI-2 device
da7: 10.000MB/s transfers (10.000MHz, offset 15)
da7: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
da6 at ahc4 bus 0 target 3 lun 0
da6: Fixed Direct Access SCSI-2 device
da6: 10.000MB/s transfers (10.000MHz, offset 15)
da6: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
da5 at ahc4 bus 0 target 2 lun 0
da5: Fixed Direct Access SCSI-2 device
da5: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled
da5: 4303MB (8813870 5
current panics
Hi, I know it isn't much (no debugger compiled in (yet)), but is anybody else seeing panics like this: mode = 0100644, inum = 214354, fs = /data0 panic: ffs_valloc: dup alloc syncing disks... 23 13 4 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 giving up on 2 buffers Uptime: 3m24s Automatic reboot in 15 seconds - press a key on the console to abort and dev = #vinum/1, block = 9757, fs = /data10 panic: ffs_blkfree: freeing free frag syncing disks... 63 13 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up on 1 buffers Uptime: 3m34s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Happening within a couple of minutes on -current kernels from 22/3 and 23/3 but not on a kernel from around the 18/3. Running SU and vinum (both panics on a vinum fs), but otherwise its just a plain nfs-server. /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark NET, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with the latest changes to ifconfig (I guess) -> Bad guess...
Sorry to reply to my own mail -- never report problems before investigating what was committed. The $Id$ -> $FreeBSD$ changes to ifconfig are probably not the cause -- more likely the changes to xl (1.52 -> 1.53), and the addition of the mii-controller. Anybody else seeing this, or should I look somewhere else alltogether? > Hi, > > After the recent changes to ifconfig and the xl driver I am getting > a panic when rc.network runs ifconfig: > > [...] > Doing initial network setup: hostname. > UP,LOOPBACK,RUNN > ING,MULTICAST> m > E®WioFnetmask 0xffa00 > tal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0x0 > stack pointer = 0x10:0xc8d18dc4 > frame pointer = 0x10:0xc8d18ddc > 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 = 78 (ifconfig) > interrupt mask = net > kernel: type 12 trap, code=0 > Stopped at 0: > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc020cac4 > stack pointer = 0x10:0xc8d18c3c > frame pointer = 0x10:0xc8d18c40 > 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 = 78 (ifconfig) > interrupt mask = net > kernel: type 12 trap, code=0 > db> > > This is after a make buildworld/installworld on -current (as of today). > > dmesg and config-file: > > > FreeBSD/i386 bootstrap loader, Revision 0.7 639/65472kB > ([EMAIL PROTECTED], Mon Aug 30 10:58:22 CEST 1999) > /kernel text=0x164b84 data=0x1ee6c+0x1e1e8 > syms=[0x4+0x24760+0x4+0x268f8] > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [kernel]... > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights > reserved. > FreeBSD 4.0-CURRENT #0: Mon Aug 30 18:56:22 CEST 1999 > [EMAIL PROTECTED]:/usr/src/sys/compile/HOME > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium II/Xeon/Celeron (400.90-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x652 Stepping = 2 > > >Features=0x183f9ff > real memory = 134217728 (131072K bytes) > avail memory = 127102976 (124124K bytes) > Preloaded elf kernel "kernel" at 0xc02ef000. > VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc029d042 (122) > VESA: ATI MACH64 > Pentium Pro MTRR support enabled > npx0: on motherboard > npx0: INT 16 interface > apm0: on motherboard > apm: found APM BIOS v1.2, connected at v1.2 > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 1.0 on > pci0 > pci1: on pcib1 > vga-pci0: irq 15 at device 0.0 on > pci1 > isab0: at device 7.0 on pci0 > isa0: on isab0 > chip1: at device 7.1 on pci0 > chip2: at device 7.2 on pci0 > chip3: at device 7.3 on pci0 > ahc0: irq 15 at device 15.0 on pci0 > ahc0: aic7870 Wide Channel A, SCSI Id=7, 16/255 SCBs > pcm0: irq 11 at device 16.0 on pci0 > pcm0: using I/O space register mapping at 0xe800 > xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 18.0 on pci0 > xl0: Ethernet address: 00:10:4b:7a:96:7d > miibus0: on xl0 > xlphy0: <3Com internal media interface> on miibus0 > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > xlphy1: <3Com internal media interface> on miibus0 > xlphy1: ignoring this PHY, non-zero instance > device_probe_and_attach: xlphy1 attach returned 6 > Probing for PnP devices: > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > vga0: at port 0x3b0-0x3df iomem 0xa-0xb on > isa0 > sc0: on isa0 > sc0: VGA <9 virtual consoles, flags=0x0> > fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A, console > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0 at port 0x378-0x37f on isa0 > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode > lpt0: on ppbus 0 > Waiting 5 seconds for SCSI devices to settle > changing root device to da0s1a > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 15) > da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) > da2 at ahc0 bus 0 target 8 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) > da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) > da1
Problems with the latest changes to ifconfig (I guess)
Hi, After the recent changes to ifconfig and the xl driver I am getting a panic when rc.network runs ifconfig: [...] Doing initial network setup: hostname. UP,LOOPBACK,RUNN ING,MULTICAST> m E®WioFnetmask 0xffa00 tal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0x0 stack pointer = 0x10:0xc8d18dc4 frame pointer = 0x10:0xc8d18ddc 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 = 78 (ifconfig) interrupt mask = net kernel: type 12 trap, code=0 Stopped at 0: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc020cac4 stack pointer = 0x10:0xc8d18c3c frame pointer = 0x10:0xc8d18c40 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 = 78 (ifconfig) interrupt mask = net kernel: type 12 trap, code=0 db> This is after a make buildworld/installworld on -current (as of today). dmesg and config-file: FreeBSD/i386 bootstrap loader, Revision 0.7 639/65472kB ([EMAIL PROTECTED], Mon Aug 30 10:58:22 CEST 1999) /kernel text=0x164b84 data=0x1ee6c+0x1e1e8 syms=[0x4+0x24760+0x4+0x268f8] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon Aug 30 18:56:22 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/HOME Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (400.90-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 127102976 (124124K bytes) Preloaded elf kernel "kernel" at 0xc02ef000. VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc029d042 (122) VESA: ATI MACH64 Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 15 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 chip1: at device 7.1 on pci0 chip2: at device 7.2 on pci0 chip3: at device 7.3 on pci0 ahc0: irq 15 at device 15.0 on pci0 ahc0: aic7870 Wide Channel A, SCSI Id=7, 16/255 SCBs pcm0: irq 11 at device 16.0 on pci0 pcm0: using I/O space register mapping at 0xe800 xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 10 at device 18.0 on pci0 xl0: Ethernet address: 00:10:4b:7a:96:7d miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xlphy1: <3Com internal media interface> on miibus0 xlphy1: ignoring this PHY, non-zero instance device_probe_and_attach: xlphy1 attach returned 6 Probing for PnP devices: atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <9 virtual consoles, flags=0x0> fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 Waiting 5 seconds for SCSI devices to settle changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da2 at ahc0 bus 0 target 8 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present WARNING: / was not properly dismounted vinum: loaded Can't open history file /var/tmp/vinum_history: Read-only file system (30) vinum: reading configuration from /dev/da2s1h vinum: updatin
Re: Can't open /dev/vinum/Control: Operation not supported by device
On Wed, Jul 21, 1999 at 04:04:13PM +0300, Vallo Kallaste wrote: > > Hello > > Something broke the vinum roughly between 18-21 July. Vinum refuses to > get up my striped volume with message: > > Can't open /dev/vinum/Control: Operation not supported by device > > This is output from command: vinum read /dev/wd0 /dev/wd1 > > All subsequent commands fail with same message. The debug control device > is in place, as are all others. The older kernel and module from July > 16 work well. I've just built the world and kernel from fresh sources. I see _exactly_ the same here. Havent had time to look more into it though. > Vallo Kallaste > [EMAIL PROTECTED] /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark NET, IP-section. "Hey, are any of you guys out there actually *using* RFC 1149?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic after loading vinum
Since the latest patches for vinum were commited I am getting a panic immediately after vinum has started. This is on a UP -current (as of today). --- changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da2 at ahc0 bus 0 target 8 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present vinum: loaded Can't open history file /var/tmp/vinum_history: Read-only file system (30) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1 fault code = supervisor read, page not present instruction pointer = 0x8:0xc017b954 stack pointer = 0x10:0xc64c7d18 frame pointer = 0x10:0xc64c7d34 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 = 17 (vinum) interrupt mask = kernel: type 12 trap, code=0 Stopped at vn_lock+0x10: testb $0x1,0x1(%esi) db> trace vn_lock(0,20002,0,c09acc00,c09acce4) at vn_lock+0x10 _end(c09acc00,c09acc00,c09d56e0,c5,0) at 0xc09ce85b _end(c09acc00,0,4000e600,c64c7d94,c09d4980) at 0xc09ce82f _end(c64c7dac,c09d3461,c64c7e08,4000e600,c5afa4c0) at 0xc09d4890 _end(c64c7e08,4000e600,c5afa4c0,c64c7ecc,c64c7dd4) at 0xc09d4980 _end(4000e600,465d,c64c7ecc,3,c5afa4c0) at 0xc09d3461 spec_ioctl(c64c7e08,c64c7dec,c01e5d65,c64c7e08,c64c7e98) at spec_ioctl+0x40 spec_vnoperate(c64c7e08,c64c7e98,c017b89d,c64c7e08,c09c2800) at spec_vnoperate+0x15 ufs_vnoperatespec(c64c7e08,c09c2800,c09ad440,0,0) at ufs_vnoperatespec+0x15 vn_ioctl(c09ad440,465d,c64c7ecc,c5afa4c0,c5afa4c0) at vn_ioctl+0xdd ioctl(c5afa4c0,c64c7f80,2,bfbfde00,bfbfde0c) at ioctl+0x1ef syscall(2f,2f,2f,bfbfde0c,bfbfde00) at syscall+0x182 Xint0x80_syscall() at Xint0x80_syscall+0x30 db> ps pid proc addruid ppid pgrp flag stat wmesg wchan cmd 17 c5afa4c0 c64c60000 117 04 2 vinum 15 c5afa780 c64bb0000 5 5 004006 2 vinum 5 c5afa8e0 c64b80000 1 5 004086 3wait c5afa8e0 sh 4 c5afaa40 c5b050000 0 0 000204 2 syncer 3 c5afaba0 c5b030000 0 0 000204 3 psleep c028d01c vmdaemon 2 c5afad00 c5b010000 0 0 000604 2 pagedaemon 1 c5afae60 c5aff0000 0 1 004084 3wait c5afae60 init 0 c02961a0 c02f80000 0 0 000204 3 sched c02961a0 swapper 16 c5afa620 c64c2000015 5 002006 5 vinum db> Kernel configuration: machine i386 cpu I686_CPU ident HOME maxusers16 #config kernel root on da0 options INET options FFS options NFS options CD9660 options FFS_ROOT options PROCFS #optionsMSDOSFS options COMPAT_43 options SCSI_DELAY=5000 options UCONSOLE options USERCONFIG options MAXCONS=4 #optionsVISUAL_USERCONFIG options SOFTUPDATES options NO_F00F_HACK options ICMP_BANDLIM options CLK_USE_TSC_CALIBRATION options COMPAT_LINUX options AHC_ALLOW_MEMIO options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options SYSVSHM options SYSVSEM options SYSVMSG options KTRACE options VESA options SC_HISTORY_SIZE=1024 options XSERVER options DDB #optionsGDB_REMOTE_CHAT controller isa0at nexus? controller pnp0 controller pci0at nexus? controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0at atkbdc? irq 12 device vga0at isa? port ? conflicts device sc0 at isa? controller fdc0at isa? port IO_FD1 irq 6 drq 2 diskfd0 at fdc0 drive 0 controller ahc0 controller scbus0 device da0 device sa0 device cd0 device pass0 device pcm0 device npx0at nexus? port IO_NPX irq 13 device apm0at nexus? device sio0at isa? port IO_COM1 flags 0x10 irq 4 device sio1at isa? port IO_COM2 irq 3 device
Re: Your system is too old to use this bsd.port.mk.....
On Wed, Mar 31, 1999 at 01:48:12AM +0400, oZZ!!! wrote: > > Hello! > I cvsup my system at 30.03.1999 23.55 MSK, then make world, but > can't understand following problem: when i try to build application from > port i c following: > ===> windowmaker-0.51.2 : Your system is too old to use this bsd.port.mk. > You need a fresh make world or an upgrade kit. Please go to > http://www.freebsd.org/ports/ or a mirror site and follow the > instructions. > I think my system is too YOUNG, not TOO OLD: > 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Mar 30 02:52:13 MSD 1999 > > What does it mean? It means what it says :) - your "make world" didn't update /usr/share/mk so parts of your system is to old. You'll have to "cd /usr/src/share/mk && make install" to update the make "include" files. It might be a good idea to bring the rest of the system up to date by use of http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/make-world.html I don't know if "make world" _should_ update /usr/share/mk, but apparantly it doesn't for the time beeing... > Sergey A. Osokin aka oZZ, > o...@etrust.ru /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark NET, IP-section. "Hey, are any of you guys out there actually *using* RFC 1149?" To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
