Panic after sleep.
Hello, My laptop paniced when he tried coming back from a sleep. This happens a few times a week. [snowlap] /var/crash$ uname -a FreeBSD snowlap.unixguru.nl 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Tue Mar 11 15:11:05 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SNOWLAP i386 Script started on Wed Mar 12 09:42:18 2003 snowlap# gdb -k kernel.11-03-2003 vmcore.0 GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-undermydesk-freebsd... --- Uptime: 36m36s Terminate ACPI Rebooting... Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Tue Mar 11 15:11:05 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SNOWLAP Preloaded elf kernel /boot/kernel/kernel at 0xc0568000. Preloaded elf module /boot/kernel/acpi.ko at 0xc05680a8. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 797579512 Hz CPU: Intel Pentium III (797.58-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 401997824 (383 MB) avail memory = 384536576 (366 MB) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: TOSHIB 750 on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00f01c0 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0xee08-0xee0b on acpi0 acpi_cpu0: CPU port 0x530-0x537 on acpi0 acpi_tz0: thermal zone on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82815 (i815 GMCH) host to PCI bridge mem 0xf000-0xf3ff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 fxp0: Intel Pro/100 Ethernet port 0xdf40-0xdf7f mem 0xf7dff000-0xf7df irq 11 at device 8.0 on pci2 fxp0: Ethernet address 00:00:39:be:6a:32 inphy0: i82562ET 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto cbb0: TI1410 PCI-CardBus Bridge at device 12.0 on pci2 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 pcib2: slot 12 INTA is routed to irq 11 cbb1: ToPIC100 PCI-CardBus Bridge at device 13.0 on pci2 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 pcib2: slot 13 INTA is routed to irq 11 cbb2: ToPIC100 PCI-CardBus Bridge at device 13.1 on pci2 cardbus2: CardBus bus on cbb2 pccard2: 16-bit PCCard bus on cbb2 pcib2: slot 13 INTB is routed to irq 11 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 UDMA100 controller port 0xcff0-0xcfff at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0xcf80-0xcf9f irq 11 at device 31.2 on pci0 usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801BA/BAM (ICH2) USB controller USB-B port 0xcf60-0xcf7f irq 11 at device 31.4 on pci0 usb1: Intel 82801BA/BAM (ICH2) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pcm0: Intel 82801BA (ICH2) port 0xcdc0-0xcdff,0xce00-0xceff irq 11 at device 31.5 on pci0 pcm0: unknown ac97 codec (id=0x594d4800) pci0: simple comms at device 31.6 (no driver attached) acpi_lid0: Control Method Lid Switch on acpi0 acpi_cmbat0: Control method Battery on acpi0 acpi_acad0: AC adapter on acpi0 speaker0 port 0x61 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ppc0 port 0x778-0x77a,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold lpt0: Printer on ppbus0 lpt0: Interrupt-driven
Re: agp stuff
Is your problem with sound or video? If sound, then you need to recompile your Kernel as such: mkdir /root/kernels cp /usr/src/sys/i386/conf/GENERIC /root/kernels/MYKERNEL ln -s /root/kernels/MYKERNEL /usr/src/sys/i386/conf/MYKERNEL now edit the /root/MYKERNEL and at the end add: options pcm options sbc (this one is for some on-Motherboard sound) Now, for your Nvidia problem, there is a quick solution for you, add: options VESA And select VESA for your card in the XFree86 Config setup. This will get you to a stage in which you can at least run X in a decent usable resolution. Now for the compile: cd /usr/src make buildworld (build kernel may need to rely on this) make buildkernel KERNCONF=MYKERNEL make installkernel KERNCONF=MYKERNEL Hope this helps, Anthony Carter On Wed, 2003-03-12 at 00:13, David Holm wrote: Hi, I get the following error (or whatever) in my bootmessage: agp0: VIA Generic host to PCI bridge mem 0xf000-0xf7ff at device 0.0 o n pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.AGP_ - AE_NOT_F OUND I tried playing around in the bios but couldn't find anything that would fix this. Could this be what is causing all my nvidia problems? (and yeah, I'm running on a current kernel, not RELENG_5_0) //David Holm To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: agp stuff
Sound works, and as for nvidia it works as long as I don't run any 3d stuff. And the xf86 supplied driver works like a charm. But I'm working on some 3d code and need the 3d acceleration, the odd thing is that it worked until I upgraded my server from 4.7 to 5.0, I NFS mount everything from the server except the system etc (so I was running on a CURRENT kernel on the machine with the 3d hardware, but with XF86 etc compiled on 4.7). //David On 12 Mar 2003 11:01:10 +0100 CARTER Anthony [EMAIL PROTECTED] wrote: Is your problem with sound or video? If sound, then you need to recompile your Kernel as such: mkdir /root/kernels cp /usr/src/sys/i386/conf/GENERIC /root/kernels/MYKERNEL ln -s /root/kernels/MYKERNEL /usr/src/sys/i386/conf/MYKERNEL now edit the /root/MYKERNEL and at the end add: options pcm options sbc (this one is for some on-Motherboard sound) Now, for your Nvidia problem, there is a quick solution for you, add: options VESA And select VESA for your card in the XFree86 Config setup. This will get you to a stage in which you can at least run X in a decent usable resolution. Now for the compile: cd /usr/src make buildworld (build kernel may need to rely on this) make buildkernel KERNCONF=MYKERNEL make installkernel KERNCONF=MYKERNEL Hope this helps, Anthony Carter On Wed, 2003-03-12 at 00:13, David Holm wrote: Hi, I get the following error (or whatever) in my bootmessage: agp0: VIA Generic host to PCI bridge mem 0xf000-0xf7ff at device 0.0 o n pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.AGP_ - AE_NOT_F OUND I tried playing around in the bios but couldn't find anything that would fix this. Could this be what is causing all my nvidia problems? (and yeah, I'm running on a current kernel, not RELENG_5_0) //David Holm To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: crash: bwrite: need chained iodone
Le 2003-03-12, Jeff Roberson écrivait :
Can you please print bp? I'd like to know what all of the members are. A
cluster buf should NEVER have BX_BKGRDWRITE set. This is totally bogus.
(kgdb) fr
#11 0xc0232072 in bwrite (bp=0xce5313e0) at
/usr/src/sys/kern/vfs_bio.c:795
795 panic(bwrite: need chained iodone);
(kgdb) print *bp
$3 = {b_io = {bio_cmd = 2, bio_dev = 0x, bio_disk = 0x0,
bio_blkno = 18540672, bio_offset = 9492758528, bio_bcount = 32768,
bio_data = 0xd42da000 , bio_flags = 0, bio_error = 0, bio_resid = 0,
bio_done = 0xc0235db0 bufdonebio, bio_driver1 = 0x0, bio_driver2 = 0x0,
bio_caller1 = 0x0, bio_caller2 = 0xce5313e0, bio_queue = {tqe_next = 0x0,
tqe_prev = 0xc408200c}, bio_attribute = 0x0, bio_from = 0x0,
bio_to = 0x0, bio_length = 0, bio_completed = 0, bio_children = 91,
bio_inbed = 0, bio_parent = 0x0, bio_t0 = {sec = 0, frac = 0},
bio_task = 0, bio_task_arg = 0x0, bio_pblkno = 64}, b_op = 0xc03a89f8,
b_magic = 280038160, b_iodone = 0xc0239320 cluster_callback,
b_offset = 688128, b_vnbufs = {tqe_next = 0x0, tqe_prev = 0x0},
b_left = 0x0, b_right = 0x0, b_vflags = 0, b_freelist = {
tqe_next = 0xce531228, tqe_prev = 0xc03dcb3c}, b_qindex = 0,
b_flags = 1677721604, b_xflags = 0 '\0', b_lock = {
lk_interlock = 0xc03d750c, lk_flags = 0, lk_sharecount = 0,
lk_waitcount = 0, lk_exclusivecount = 0, lk_prio = 80,
lk_wmesg = 0xc0379b53 bufwait, lk_timo = 0, lk_lockholder = 0x,
lk_newlock = 0x0}, b_bufsize = 32768, b_runningbufspace = 0,
b_kvabase = 0xd42da000 , b_kvasize = 32768, b_lblkno = 42,
b_vp = 0xc4a21124, b_object = 0x0, b_dirtyoff = 0, b_dirtyend = 32768,
b_rcred = 0x0, b_wcred = 0x0, b_saveaddr = 0xbfbfea40, b_pager = {
pg_spc = 0x0, pg_reqpage = 0}, b_cluster = {cluster_head = {
tqh_first = 0xce67bfe8, tqh_last = 0xce6b6b80}, cluster_entry = {
tqe_next = 0xce67bfe8, tqe_prev = 0xce6b6b80}}, b_pages = {0xc0d14748,
0xc0acff90, 0xc0a7cbd8, 0xc0bffc20, 0xc1074868, 0xc10106b0, 0xc10700f8,
0xc0f9c040, 0xc0af5808, 0xc0c56c50, 0xc0b47198, 0xc0bdb9e0, 0xc10e7b28,
0xc0abba70, 0xc09888b8, 0xc09d3600, 0xc0d14748, 0xc0acff90, 0xc0a7cbd8,
0xc0bffc20, 0xc1074868, 0xc10106b0, 0xc10700f8, 0xc0f9c040, 0xc0d21888,
0xc105cfd0, 0xc1057f18, 0xc109ff60, 0xc0a18948, 0xc0ab3d90, 0xc0a36fd8,
0xc0b91820}, b_npages = 8, b_dep = {lh_first = 0x0}}
(kgdb)
Hum. Now this is *most* peculiar. bp-b_xflags is 0, so we should never
have entered that 'if', unless there is a race condition somewhere such
that we test b_xflags on a buffer and carry on processing on another...
Hope this helps...
Thomas.
--
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
please apply patch to openwebmail /FreeBSD ports
hi all http://openwebmail.org/openwebmail/download/cert/patches/SA-03:01/ is the patch please apply it to your ports my uname: FreeBSD kripel 5.0-CURRENT FreeBSD 5.0-CURRENT #4: Fri Jan 31 14:32:34 CET 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/GENERIC i386 and todays ports /* it's local root */ -- have a nice day and bye - R To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)!
Hello, There is a patch which can be tried at: http://phk.freebsd.dk/patch/ken.patch I dumped some GBs over the wire with this and haven't seen any ill effects. Thanks, --[ Free Software ISOs - http://www.fsn.hu/?f=download ]-- Attila Nagy e-mail: [EMAIL PROTECTED] Free Software Network (FSN.HU)phone @work: +361 210 1415 (194) cell.: +3630 306 6758 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
C++ Exception handling with shared libs in current is broken again
Hi all,
I do know now why I have again problems with building openoffice.
It seems that exceptions over shared libraries are broken again in
CURRENT.
Alexander, do you have a idea why this got broken again ?
Attached is your test programm ...
Martin
STABLE:
[EMAIL PROTECTED]:~/cxxtest$ export LD_LIBRARY_PATH=.
[EMAIL PROTECTED]:~/cxxtest$ ./arf
calling foo
in baz
foo caught Bax thowing...
returned from foo
CURRENT:
[EMAIL PROTECTED]:~/cxxtest$ export LD_LIBRARY_PATH=.
[EMAIL PROTECTED]:~/cxxtest$ ./arf
abort trap
... The exception is not catched at all ...
Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 61 826 93 00 Fax: +41 61 826 93 01
PGP: finger -l [EMAIL PROTECTED]
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--# This is a shell archive. Save it in a file, remove anything before
# this line, and then unpack it by entering sh file. Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
# Makefile
# foo.cc
# main.cc
#
echo x - Makefile
sed 's/^X//' Makefile 'END-of-Makefile'
XCXX=g++
XLD=ld
XCXXFLAGS=-g -fpic -fexceptions
X
Xall: arf
X
Xarf: main.o foo.so
X ${CXX} -o arf main.o foo.so
X
X
Xfoo.so: foo.o
X ${LD} -Bshareable -o foo.so foo.o
X
Xclean:
X rm -f arf *.o *.so
END-of-Makefile
echo x - foo.cc
sed 's/^X//' foo.cc 'END-of-foo.cc'
X#include stdio.h
X
Xint Foo ();
X
Xint Baz ()
X{
Xchar *msg = Bax thowing...;
Xprintf (in baz\n);
Xthrow msg;
Xprintf (baz should not be here.\n);
X}
X
X
Xint Foo ()
X{
Xtry {
XBaz ();
X} catch (char *msg) {
Xprintf (foo caught %s\n, msg);
X}
X}
END-of-foo.cc
echo x - main.cc
sed 's/^X//' main.cc 'END-of-main.cc'
X#include stdio.h
X
Xint Foo ();
X
Xint
Xmain ()
X{
Xtry {
Xprintf (calling foo\n);
XFoo ();
Xprintf (returned from foo\n);
X} catch (char *msg) {
Xprintf (exception from foo: %s\n, msg);
X} catch (...) {
Xprintf (unknown exception\n);
X}
X}
END-of-main.cc
exit
kernel panic in tcp_input.c:2252
Am Di, 2003-03-11 um 17.43 schrieb KT Sin:
Another panic in tcp_input while exiting gtk-gnutella.
I just can say 'me too'. This kind of panic in tcp_input.c bites me
since some weeks. It seems to be triggered by massive opening/closing of
tcp connections (like gtk-gnutella does).
Any ideas how to track this down?
schnipp
This GDB was configured as i386-undermydesk-freebsd...
panic: headlocked should be 1
panic messages:
---
panic: headlocked should be 1
Uptime: 50m36s
Dumping 247 MB
ata0: resetting devices ..
done
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
---
#0 doadump () at ../../../kern/kern_shutdown.c:239
239 dumping++;
(kgdb) bt full
#0 doadump () at ../../../kern/kern_shutdown.c:239
No locals.
#1 0xc01acb0b in boot (howto=260) at ../../../kern/kern_shutdown.c:371
No locals.
#2 0xc01acd38 in panic () at ../../../kern/kern_shutdown.c:542
td = (struct thread *) 0xc0e91a50
bootopt = 260
newpanic = 1
ap = 0x0
buf = headlocked should be 1, '\0' repeats 233 times
#3 0xc021dc6f in tcp_input (m=0xc0e9e100, off0=20) at
../../../netinet/tcp_input.c:2252
th = (struct tcphdr *) 0xc1316834
ip = (struct ip *) 0xc1316820
ipov = (struct ipovly *) 0x3f14
inp = (struct inpcb *) 0xc2c7e0e4
optp = (u_char *) 0xc1316848 \001\001\b\n
optlen = 12
len = -1027090700
tlen = 23
off = -1027090700
drop_hdrlen = 52
tp = (struct tcpcb *) 0xc2c7d6f4
thflags = 1
so = (struct socket *) 0xc2c11000
todrop = -1027090700
acked = -1027090700
ourfinisacked = -1027090700
needoutput = 0
tiwin = 16148
to = {to_flags = 1, to_tsval = 2289001, to_tsecr = 303502, to_cc = 0,
to_ccecho = 0, to_mss = 0,
to_requested_s_scale = 0 '\0', to_pad = 0 '\0'}
taop = (struct rmxp_tao *) 0xc2c7d6f4
tao_noncached = {tao_cc = 3801157, tao_ccsent = 8003, tao_mssopt =
5760}
headlocked = 0
next_hop = (struct sockaddr_in *) 0x0
rstreason = -1027090700
ip6 = (struct ip6_hdr *) 0x0
isipv6 = 0
#4 0xc02170f5 in ip_input (m=0xc0e9e100) at
../../../netinet/ip_input.c:944
ip = (struct ip *) 0xc1316820
fp = (struct ipq *) 0xc2bcf600
ia = (struct in_ifaddr *) 0xc2bcf600
ifa = (struct ifaddr *) 0x0
i = 0
hlen = 20
checkif = 0
sum = 0
pkt_dst = {s_addr = 3110381760}
divert_info = 0
args = {m = 0x561, oif = 0x0, next_hop = 0x0, rule = 0x0, eh = 0x0, ro
= 0xe9, dst = 0xc02f5be7,
flags = -857973540, f_id = {dst_ip = 3222949867, src_ip = 3224892020,
dst_port = 1, src_port = 0,
proto = 172 '¬', flags = 212 'Ô'}, divert_rule = 0, retval =
3224534064}
#5 0xc0205c66 in swi_net (dummy=0x0) at ../../../net/netisr.c:236
ni = (struct netisr *) 0xc0327c30
m = (struct mbuf *) 0xc0e9e100
bits = 0
i = 0
#6 0xc019dd06 in ithread_loop (arg=0xc0e8f200) at
../../../kern/kern_intr.c:536
ithd = (struct ithd *) 0xc0e8f200
ih = (struct intrhand *) 0xc0e86840
td = (struct thread *) 0xc0e91a50
p = (struct proc *) 0xc0e909ec
#7 0xc019d10f in fork_exit (callout=0xc019dbe0 ithread_loop,
arg=0xc0e8f200, frame=0xccdc5d48)
at ../../../kern/kern_fork.c:871
td = (struct thread *) 0x0
p = (struct proc *) 0xc0e909ec
schnapp
bye
--
Tobias Reifenberger -- [EMAIL PROTECTED] -- DG1NGT
GEE e* dpu s:- a-- C+++ UB+++ L- W+ N+ w--- Y+ tv+ b++ D++ h++ r---
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: What's happened to bpf?
Terry Lambert wrote: Daniel C. Sobral wrote: device cloning is really a wrong name for this, and I regret that I every used that term. On demand device creation is closer, but it doesn't have any sort of ring to it. Worst of all, device cloning is one of Terry's buzzwords. :-) Actually, it's an SVR4/AIX/Solaris/Any-UNIX-Except-FreeBSD buzzword. 8-). So... are we buzzword-compliant now? :-) -- Daniel C. Sobral Gerência de Operações Divisão de Comunicação de Dados Coordenação de Segurança TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: C++ Exception handling with shared libs in current is brokenagain
Hi all, [EMAIL PROTECTED]:~/cxxtest$ export LD_LIBRARY_PATH=. [EMAIL PROTECTED]:~/cxxtest$ ./arf abort trap rtld from 19.October has the same problem. I guess it must be gcc3.2 which is the problem. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel panic in tcp_input.c:2324
leafy wrote: On Tue, Mar 11, 2003 at 05:24:55PM -0800, Doug Barton wrote: You didn't say when your most recent upgrade was. If you're using 5.0-Release, you should upgrade to 5-current, where this problem should be fixed already. Doug I buildworld/installworld daily. So it's not fixed. Well, yes, but are you cvsupping from releng=. or releng=RELENG_5_0 or releng=RELENG_5_0_0_RELEASE (or similar stuff)? I did experience such problems for a while, but they did get fixed a week or two ago for me. -- Daniel C. Sobral Gere^ncia de Operac,o~es Divisa~o de Comunicac,a~o de Dados Coordenac,a~o de Seguranc,a TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel panic in tcp_input.c:2324
On Wed, Mar 12, 2003 at 10:20:59AM -0300, Daniel C. Sobral wrote: Well, yes, but are you cvsupping from releng=. or releng=RELENG_5_0 or releng=RELENG_5_0_0_RELEASE (or similar stuff)? I did experience such problems for a while, but they did get fixed a week or two ago for me. -- Daniel C. Sobral Hi, I run -current. period :) Jiawei -- Without the userland, the kernel is useless. --inspired by The Tao of Programming To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel panic in tcp_input.c:2324
On Wed, Mar 12, 2003 at 10:40:56PM +0800, leafy wrote: I run -current. period :) Jiawei As a side note, I've used both userland PPPoE and kernel PPPoE (mpd +ipfilter, which is my current setup), both exhibit the same problem. I'll try again tonight. Jiawei -- Without the userland, the kernel is useless. --inspired by The Tao of Programming To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ld -Bsharable broken in CURRENT ?
See testcase
STABLE:
[EMAIL PROTECTED]:~/cxxtest2$ export LD_LIBRARY_PATH=.
[EMAIL PROTECTED]:~/cxxtest2$ ./a.out
cought string: x == 1
bar: cought string: x == 1
[EMAIL PROTECTED]:~/cxxtest2$ ./b.out
cought string: x == 1
bar: cought string: x == 1
CURRENT:
[EMAIL PROTECTED]:~/cxxtest2$ ./a.out
cought string: x == 1
bar: cought string: x == 1
[EMAIL PROTECTED]:~/cxxtest2$ ./b.out
Abort trap (core dumped)
cxxtest2/Makefile
CXX=g++
LD=ld
CXXFLAGS=-fpic -fexceptions
all: a.out b.out
#
# Works
#
a.out: main.o foo.so bar.so
${CXX} -o a.out main.o foo.so bar.so
#
# Broken
#
b.out: main.o foo2.so bar2.so
${CXX} -o b.out main.o foo2.so bar2.so
#
# Works
#
bar.so: bar.o
${CXX} -shared -o bar.so bar.o
foo.so: foo.o
${CXX} -shared -o foo.so foo.o
#
# Broken
#
bar2.so: bar.o
${LD} -Bshareable -o bar2.so bar.o
foo2.so: foo.o
${LD} -Bshareable -o foo2.so foo.o
clean:
rm -f a.out *.o *.so
cxxtest2/bar.cc
/* compile with g++ -shared -fPIC -o bar.so bar.cc */
#include iostream
#include string
using namespace std;
using std::cerr;
extern void foo(int);
void bar(int x)
{
try {
foo(x);
} catch (string s) { cerr bar: cought string: s endl;
} catch (int i) { cerr bar: cought int: i endl;
} catch (...) { cerr bar: cought something endl;
}
}
cxxtest2/foo.cc
/* compile with g++ -shared -fPIC -o foo.so foo.cc */
#include string
using namespace std;
void foo(int x)
{
switch(x) {
case 1:
throw string(x == 1);
case 2:
throw int(2);
default:
throw float(3.1415);
}
}
cxxtest2/main.cc
/* compile with g++ main.cc ./foo.so ./bar.so */
#include string
#include iostream
using namespace std;
extern void foo(int);
extern void bar(int);
main(int argc, char *argv[])
{
try {
foo(argc);
} catch (string s) { cerr cought string: s endl;
} catch (int i) { cerr cought int: i endl;
} catch (...) { cerr cought something endl;
}
bar(argc);
return 0;
}
Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 61 826 93 00 Fax: +41 61 826 93 01
PGP: finger -l [EMAIL PROTECTED]
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: kernel panic in tcp_input.c:2324
On Wed, Mar 12, 2003 at 10:42:30PM +0800, leafy wrote: On Wed, Mar 12, 2003 at 10:40:56PM +0800, leafy wrote: I run -current. period :) Jiawei As a side note, I've used both userland PPPoE and kernel PPPoE (mpd +ipfilter, which is my current setup), both exhibit the same problem. I'll try again tonight. Jiawei It still panics but has no core dump anymore. Jiawei -- Without the userland, the kernel is useless. --inspired by The Tao of Programming To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Time drift.
On Wed, Mar 12, 2003 at 07:14:38AM +0100, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Andrew P. Lentvorski, Jr. writes: An $8.00 wristwatch has much better time accuracy that your multi-$100 PC. That's because the crystal in your wristwatch is cut specially so that it has a flat temp-co at about 23-16 C, whereas the xtal in your computer is has a gradient all the way from 0 to 70 C. And this is easily verifiable too: just leave your wristwatch in an unheated (cold) bedroom and watch the drift. -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
MAKEDEV lost in 5.0-CURRENT?
Where are the MAKEDEV and MAKEDEV.local scripts in 5.0-CURRENT? I cvsupdate today last time and did a find through /usr/src, but I can not find both script ... -- MfG O. Hartmann [EMAIL PROTECTED] -- Systemadministration des Institutes fuer Physik der Atmosphaere (IPA) -- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 (Buero) FAX: +496131/3923532 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV lost in 5.0-CURRENT?
On Wed, Mar 12, 2003 at 04:44:25PM +0100, Hartmann, O. wrote: Where are the MAKEDEV and MAKEDEV.local scripts in 5.0-CURRENT? I cvsupdate today last time and did a find through /usr/src, but I can not find both script ... MAKEDEV is dead, baby. MAKEDEV is dead (c) paraphrase from Pulp Fiction Long live devfs(8) :-) Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/48038 Committers still have no time for commit this :-) -- Rgdz,/\ ASCII RIBBON CAMPAIGN Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL http://ozz.pp.ru/ X AND NEWS / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: exclusive sleep mutex netisr...
On 12-Mar-2003 Derek Tattersall wrote: * Jonathan Lemon ([EMAIL PROTECTED]) [030312 01:12]: Date: Tue, 11 Mar 2003 18:59:15 -0600 (CST) From: Jonathan Lemon [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: exclusive sleep mutex netisr... Organization: Cc: In article local.mail.freebsd-current/[EMAIL PROTECTED] you write: I see several instances of this in /var/log/messages after cvsup'ing Monday evening and rebuilding world and kernel. I haven't seen any messages about this, so I figured I'd ask here. Message: Mar 11 17:33:30 lorne kernel: malloc() of 64 with the following non-sleepablelocks held: Mar 11 17:33:30 lorne kernel: exclusive sleep mutex netisr lock r = 0 (0xc0579160) locked @ /usr/src/sys/net/netisr.c:215 Can anybody supply me a clue as to what's going on here? It can be ignored for now, the code path is still under the Giant lock, so this is harmless, I'll fix this soon to use a different approach; the lock was intended to protect against reentrancy. However, I'd be interested to know what is calling malloc(), if that information is in the syslog. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message The only other bit of information I have is: Mar 10 20:55:09 lorne kernel: Bad malloc flags: 4 Mar 10 20:55:09 lorne kernel: Stack backtrace: Mar 10 20:55:09 lorne kernel: malloc() of 64 with the following non-sleepablelocks held: Mar 10 20:55:09 lorne kernel: exclusive sleep mutex netisr lock r = 0 (0xc0579160) locked @ /usr/src/sys/net/netisr.c:215 Mar 10 20:55:09 lorne kernel: malloc() of 64 with the following non-sleepablelocks held: Mar 10 20:55:09 lorne kernel: exclusive sleep mutex netisr lock r = 0 (0xc0579160) locked @ /usr/src/sys/net/netisr.c:215 I haven't found anything that was crisper. I hope this is useful. I'll keep following the list for more info. You can turn on witness_ddb and get a stack trace to see where malloc() is called from. You might also be able to use witness_trace to do this. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: lock order reversal? current with tl ethernet
On 12-Mar-2003 Tod McQuillin wrote:
Running -current from March 11 on a dual cpu compaq 5100, there are some
warnings in the dmesg about the tl ethernet interface.
Here are the warnings:
malloc() of 128 with the following non-sleepablelocks held:
exclusive sleep mutex tl0 (network driver) r = 0 (0xc4017aa8) locked @
/usr/src/5-current/src/sys/pci/if_tl.c:1146
It's holding the lock across bus_setup_intr(). You can try the
following patch:
Index: if_tl.c
===
RCS file: /usr/cvs/src/sys/pci/if_tl.c,v
retrieving revision 1.74
diff -u -r1.74 if_tl.c
--- if_tl.c 19 Feb 2003 05:47:41 - 1.74
+++ if_tl.c 12 Mar 2003 15:20:47 -
@@ -1138,12 +1138,11 @@
if (t-tl_name == NULL) {
device_printf(dev, unknown device!?\n);
- goto fail;
device_printf(dev, unknown device!?\n);
- goto fail;
RCS file: /usr/cvs/src/sys/pci/if_tl.c,v
retrieving revision 1.74
diff -u -r1.74 if_tl.c
--- if_tl.c 19 Feb 2003 05:47:41 - 1.74
+++ if_tl.c 12 Mar 2003 15:20:47 -
@@ -1138,12 +1138,11 @@
if (t-tl_name == NULL) {
device_printf(dev, unknown device!?\n);
- goto fail;
+ return (ENXIO);
}
mtx_init(sc-tl_mtx, device_get_nameunit(dev), MTX_NETWORK_LOCK,
MTX_DEF | MTX_RECURSE);
- TL_LOCK(sc);
/*
* Map control/status registers.
@@ -1348,12 +1347,12 @@
/*
* Call MI attach routine.
*/
--
John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve! - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
More isp(4) strangeness...
The 5-CURRENT machine I've got rebooted itself last night. Right before the reboot, I found this in /var/log/messages: Mar 12 03:00:00 alvin newsyslog[2598]: logfile turned over due to size100K Mar 12 03:07:09 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Mar 12 03:07:13 alvin last message repeated 956 times Mar 12 03:07:13 alvin kernel: isp0: bad underrun for 124.0 (count 65536, resid 2147461119, status not marked) Mar 12 03:07:13 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Mar 12 03:07:13 alvin last message repeated 11 times Mar 12 03:07:13 alvin kernel: isp0: bad underrun for 124.0 (count 65536, resid 2147467263, status not marked) Mar 12 03:07:13 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Mar 12 03:07:14 alvin last message repeated 39 times Mar 12 03:07:14 alvin kernel: isp0: bad underrun for 124.0 (count 65536, resid 2147425279, status not marked) Mar 12 03:07:14 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Mar 12 03:07:28 alvin last message repeated 3959 times Mar 12 03:07:28 alvin kernel: isp0: bad underrun for 124.0 (count 65536, resid 2147473407, status not marked) Mar 12 03:07:28 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Mar 12 03:07:28 alvin last message repeated 9 times Mar 12 03:07:28 alvin kernel: isp0: bad underrun for 124.0 (count 65536, resid 2147431423, status not marked) Mar 12 03:07:28 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Mar 12 03:07:33 alvin last message repeated 1840 times Mar 12 03:07:39 alvin kernel: isp0: LIP destroyed 4 active commands Mar 12 03:07:42 alvin kernel: isp0: LIP destroyed 4 active commands Mar 12 03:07:44 alvin kernel: isp0: bad underrun for 124.0 (count 65536, resid 2147418111, status not marked) Mar 12 03:07:44 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Mar 12 03:07:57 alvin last message repeated 4078 times Mar 12 03:07:57 alvin kernel: isp0: bad underrun for 124.0 (count 65536, resid 2147431423, status not marked) Mar 12 03:07:57 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Mar 12 03:08:02 alvin last message repeated 1650 times Mar 12 03:08:02 alvin kernel: isp0: bad underrun for 124.0 (count 65536, resid 2147455999, status not marked) Mar 12 03:08:02 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Mar 12 03:08:07 alvin last message repeated 1346 times Mar 12 03:08:07 alvin kernel: isp0: bad underrun for 124.0 (count 65536, resid 2147427327, status not marked) Mar 12 03:08:07 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Mar 12 03:08:11 alvin last message repeated 1183 times Mar 12 03:08:11 alvin kernel: isp0: bad underrun for 124.0 (count 65536, resid 2147439615, status not marked) Mar 12 03:08:11 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Mar 12 03:08:14 alvin last message repeated 559 times Mar 12 03:08:14 alvin kernel: isp0: bad underrun for 124.0 (count 65536, resid 2147447807, status not marked) Mar 12 03:08:14 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Mar 12 03:08:14 alvin last message repeated 10 times Mar 12 03:08:14 alvin kernel: isp0: bad underrun for 124.0 (count 65536, resid 2147427327, status not marked) Mar 12 03:08:14 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Mar 12 03:08:14 alvin last message repeated 11 times Mar 12 03:08:18 alvin kernel: isp0: LIP destroyed 6 active commands Mar 12 03:08:25 alvin kernel: (da1:isp0:0:124:0): lost device Mar 12 03:08:25 alvin kernel: (da1:isp0:0:124:0): Invalidating pack Mar 12 03:08:45 alvin last message repeated 5 times Mar 12 03:08:45 alvin kernel: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)! Uhhh... lost device? :-) I can post a kernel config if needed (as well as /boot/loader.conf and /etc/sysctl.conf). Cheers, Ryan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV lost in 5.0-CURRENT?
On Wed, 12 Mar 2003, Sergey A. Osokin wrote: :On Wed, Mar 12, 2003 at 04:44:25PM +0100, Hartmann, O. wrote: : Where are the MAKEDEV and MAKEDEV.local scripts in 5.0-CURRENT? : I cvsupdate today last time and did a find through /usr/src, : but I can not find both script ... : :MAKEDEV is dead, baby. MAKEDEV is dead (c) paraphrase from Pulp Fiction :Long live devfs(8) :-) :Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/48038 : :Committers still have no time for commit this :-) : :-- : :Rgdz,/\ ASCII RIBBON CAMPAIGN :Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL :http://ozz.pp.ru/ X AND NEWS : / \ : Ouch ;-)) All right, a new 'think another way when going to FreeBSD 5.0 ...'. Thanks. -- MfG O. Hartmann [EMAIL PROTECTED] -- Systemadministration des Institutes fuer Physik der Atmosphaere (IPA) -- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 (Buero) FAX: +496131/3923532 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
bluetooth BW-BH02U reset failure
Hi, I'm sorry for huge mail. I heard 5-CURRENT support BlueTooth device. I tried install 5-CURRENT and test BlueTooth usb dongle now. So I have problem in hccontrol with reset. At first, I installed 5-CURRENT on P3 machine and sync with cvsup to latest. and overwrite 2003-03-05 maksim's bluetooth modules. I tried to use planex(http://www.planex.co.jp/) BW-BH02U BlueTooth USB dongle. I plugged BW-BH02U in to FreeBSD without any ko module. FreeBSD found that device with ugen0. following message got with usbdevs -v and udesc_dump. ---dmesg--- as connect ugen0: Broadcom product 0x2033, rev 1.01/0.a0, addr 2 --usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 addr 2: full speed, power 100 mA, config 1, product 0x2033(0x2033), Broadcom(0x0a5c), rev 0.a0 port 2 powered --udesc_dump Standard Device Descriptor: bLength18 bDescriptorType01 bcdUSB 0101 bDeviceClass e0 bDeviceSubClass01 bDeviceProtocol01 bMaxPacketSize 64 idVendor 0a5c idProduct 2033 bcdDevice 00a0 iManufacturer 0 iProduct 0 iSerialNumber 0 bNumConfigurations 1 Configuration 0: Standard Configuration Descriptor: bLength 9 bDescriptorType 02 wTotalLength200 bNumInterface 3 bConfigurationValue 1 iConfiguration 0 bmAttributesa0 (remote-wakeup) bMaxPower 50 (100 mA) Standard Interface Descriptor: bLength9 bDescriptorType04 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClasse0 bInterfaceSubClass 01 bInterfaceProtocol 01 iInterface 0 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 81 (in) bmAttributes 03 (Interruput) wMaxPacketSize 16 bInterval1 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 82 (in) bmAttributes 02 (Bulk) wMaxPacketSize 64 bInterval1 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 02 (out) bmAttributes 02 (Bulk) wMaxPacketSize 64 bInterval1 Standard Interface Descriptor: bLength9 bDescriptorType04 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClasse0 bInterfaceSubClass 01 bInterfaceProtocol 01 iInterface 0 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 83 (in) bmAttributes 01 (Isochronous) wMaxPacketSize 0 bInterval1 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 03 (out) bmAttributes 01 (Isochronous) wMaxPacketSize 0 bInterval1 Standard Interface Descriptor: bLength9 bDescriptorType04 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClasse0 bInterfaceSubClass 01 bInterfaceProtocol 01 iInterface 0 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 83 (in) bmAttributes 01 (Isochronous) wMaxPacketSize 16 bInterval1 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 03 (out) bmAttributes 01 (Isochronous) wMaxPacketSize 16 bInterval1 Standard Interface Descriptor: bLength9 bDescriptorType04 bInterfaceNumber 1 bAlternateSetting 2 bNumEndpoints 2 bInterfaceClasse0 bInterfaceSubClass 01 bInterfaceProtocol 01 iInterface 0 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 83 (in) bmAttributes 01 (Isochronous) wMaxPacketSize 32 bInterval1 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 03 (out) bmAttributes 01 (Isochronous) wMaxPacketSize 32 bInterval
Re: failed to set signal flags properly for ast()
On Wed, 12 Mar 2003, Tim Robbins wrote:
Compile, run under gdb, then type print test() when the program receives
SIGABRT. Seems to work incorrectly on 4.7 too.
#include stdio.h
#include stdlib.h
void
test(void)
{
puts(hello);
}
int
main(int argc, char *argv[])
{
abort();
exit(0);
}
Thanks. At last it is possible to reproduce this bug :-).
The bug seems to be that issignal() is quite broken. It gets called
for masked signals in the P_TRACED case, but never does anything for
masked signals, but at least the following things poing to a need
for doing something for masked signals:
- the special case for P_TRACED in SIGPENDING()
- the incorrect behaviour of the above program in RELENG_4. I think
it misbehaves in the same way under -current except in the INVARIANTS
case the sanity check spews kernel printfs.
- code in NetBSD's issignal() to do something in the (p-p_stat == SSTOP)
case without even checking if there are any signals (masked or not).
This bug seems to go back to at least FreeBSD-1 (Net/2).
SIGPENDING() is also inconsistent with issignal() in the P_PPWAIT case.
I think this just wastes time doing null calls to issignal(), and
triggers the INVARIANTS check in the same way as the P_TRACED case
(see below). This seems to go back to FreeBSD-1 too.
SIGPENDING() is consistent with issignal() in the S_SIG case, but this
may be wrong since S_SIG is similar to P_TRACED.
The invariants check gets trigger as follows:
- sigpending() is called correctly.
- ast() clears the flags set by sigpending() and handles the signal
using while ((sig == cursig(td)) != 0) postsig(). But cursig()
doesn't find any signals since all the pending ones are masked.
- userret() checks that pending signals were handled. It finds
unhandled masked ones and thinks they needed handling because
P_TRACED is set.
(IIRC, there is only a SIGTRAP pending to begin with, but attempting
to control the process using ^C^Z gave masked SIGINTs and SIGSTOPs
too).
Appart from the diagnostic, the incorrect working in -current is to
loop endlessly calling ast() and usrret(). ^C^Z doesn't stop it
because they are masked.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Still getting panic on boot.
--- walt [EMAIL PROTECTED] wrote: 04:00 GMT Mar 12: Just cvsup'd and rebuilt with same result as 12 hours ago -- I see a kernel panic page fault while in kernel mode just after attempting to mount the root filesystem. The kernel from yesterday works fine and when I reboot the filesystems come up clean, so the new kernel nevers writes to disk, apparently. Am I the only one seeing this? I saw the same here. However, after reboot with the same faulty kernel, it may not panic but doesn't have the /dev/null entry which makes the bootup process failed. In addition, my -current was cvsup'd about four hours ago. Regards, __ Do you Yahoo!? Yahoo! Web Hosting - establish your business online http://webhosting.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV lost in 5.0-CURRENT?
Hartmann, O. (Wed, Mar 12, 2003 at 04:59:52PM +0100) wrote: On Wed, 12 Mar 2003, Sergey A. Osokin wrote: :On Wed, Mar 12, 2003 at 04:44:25PM +0100, Hartmann, O. wrote: : Where are the MAKEDEV and MAKEDEV.local scripts in 5.0-CURRENT? : I cvsupdate today last time and did a find through /usr/src, : but I can not find both script ... : :MAKEDEV is dead, baby. MAKEDEV is dead (c) paraphrase from Pulp Fiction :Long live devfs(8) :-) :Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/48038 : :Committers still have no time for commit this :-) : :-- : :Rgdz,/\ ASCII RIBBON CAMPAIGN :Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL :http://ozz.pp.ru/ X AND NEWS : / \ : Ouch ;-)) All right, a new 'think another way when going to FreeBSD 5.0 ...'. It also helps when you read src/UPDATING :-) NODEVFS option has been removed and DEVFS thereby made standard. This makes all references to MAKEDEV obsolete, and they should be removed when convenient. -- Hiten To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)!
Poul-Henning Kamp wrote: Yes, I just got this myself today. I overlooked that devstat is not locked when I moved the devstat to geom_disk. Expect a patch tonight. There is a patch which can be tried at: http://phk.freebsd.dk/patch/ken.patch Seeing the same messages, going through a buildworld w/the patch now and will let you know if it helps. Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: ld -Bsharable broken in CURRENT ?
Hi all, See testcase [EMAIL PROTECTED]:~/cxxtest2$ ./a.out cought string: x == 1 bar: cought string: x == 1 [EMAIL PROTECTED]:~/cxxtest2$ ./b.out Abort trap (core dumped) Looks like gcc2.9.x works, but it doesn't need to do this of course. Using ld without using the crt objects with gcc3.x produces a working binary, but exceptions over shared libs are broken in this case. So everything works as expected. I'll have to look where the real problem is for the openoffice-devel port. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: please apply patch to openwebmail /FreeBSD ports
On Wed, Mar 12, 2003 at 12:05:51PM +0100, Radko Keves wrote: hi all http://openwebmail.org/openwebmail/download/cert/patches/SA-03:01/ is the patch please apply it to your ports I'm working on this patch now. -- Yen-Ming Lee [§õ«Û©ú] KeyID: 0x5EB52E51 : www.leeym.com : Taipei, Taiwan [EMAIL PROTECTED] leeym.com, FreeBSD.org, yahoo-inc.com, ntu.edu.tw, civil.ncku.edu.tw } pgp0.pgp Description: PGP signature
Re: Fix for rtc, vmware modules and post-500104 -current
hi. On Wed, 12 Mar 2003 14:05:42 +0900 Norikatsu Shigemura [EMAIL PROTECTED] wrote: On Wed, 5 Mar 2003 19:37:35 +0100 (MET) Marcin CIE LAK [EMAIL PROTECTED] wrote: See the patches enclosed to emulators/rtc and emulators/vmware2 ports. Tested only for -current with: #define __FreeBSD_version 500104 Hum.. This is not work in my environment. Because MOD_LOAD initializer didn't kick rtc_attach. I fixed this problem and merge(but ADHOC:-). Please, anyone, check following patch. I've just applied your patch and rebuilt rtc.ko. It gave me /dev/rtc and VMware2 doesn't complain about 'cannot open /dev/rtc...' any more. It seems to be working well. (except WARNING: driver rtc used unreserved major device number 202 message, which seems to be harmless) BTW, vmmon_*.ko is not good. hum vmmon_up.ko is working for me now with Marcin's patch. My -current is dated as 2003/03/10. /usr/include/sys/param.h has #define __FreeBSD_version 500105. vmmon_up.ko and rtc.ko are kldload'ed. VMware2 is running Win2K, netgraph-bridging over fxp0. Thanks for you both!! :) Y.Kasazaki // To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
latest working snapshot?
I need to install current on a new box that just arrived. What's the latest working snapshot? 20030312-JPSNAP get about 40% of the way through the base install and sysinstall complains about a bad realloc, and lets me hit a key to reboot ;-( Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Startup scripts stop in middle of startup
Hi ! I just installed FreeBSD-5 from CD (iso images I found on freebsd site), over my 4.7. But I got some weird problem. When computer starts, it stops in middle of one of scripts. After it writes Configuring syscons: blanktime. it stops. I can boot if I press CTRL-C, and then it goes further with scripts. Did someone encounter the same problem? Is it possible to exactly determine which script is problem (script debuging os something)? Ok that's all for now. Andy ** * Aleksander Rozman - Andy * Fandoms: E2:EA, SAABer, Trekkie, Earthie * * [EMAIL PROTECTED] * Sentinel, BH 90210, True's Trooper, * *[EMAIL PROTECTED] * Heller's Angel, Questie, Legacy, PO5, * * Maribor, Slovenia (Europe) * Profiler, Buffy (Slayerete), Pretender* * ICQ-UIC: 4911125 * * PGP key available *http://www.atechnet.dhs.org/~andy/ * ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: latest working snapshot?
On Wed, Mar 12, 2003 at 02:14:25PM -0500, Andrew Gallatin wrote: I need to install current on a new box that just arrived. What's the latest working snapshot? 20030312-JPSNAP get about 40% of the way through the base install and sysinstall complains about a bad realloc, and lets me hit a key to reboot ;-( You're just lucky. Mine just panics. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age pgp0.pgp Description: PGP signature
Re: latest working snapshot?
On Wed, Mar 12, 2003 at 10:32:02PM +0200, Ruslan Ermilov wrote: On Wed, Mar 12, 2003 at 02:14:25PM -0500, Andrew Gallatin wrote: I need to install current on a new box that just arrived. What's the latest working snapshot? 20030312-JPSNAP get about 40% of the way through the base install and sysinstall complains about a bad realloc, and lets me hit a key to reboot ;-( You're just lucky. Mine just panics. I wonder how long this has been happening -- 12-Feb-2003 also panics for me. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
problem with a file-backed md
Hello! I have a nasty problem with a file-backed md. The file is the Windows' swap file residing on a msdosfs part of the drive. First I tried to just swapon to the md: tmp=`mdconfig -a -t vnode -f /W/pagefile.sys` swapon $tmp But random big-memory programs were hanging. At that stage, even the simple sync(8) was hanging and reboot would report that some processes would not die. So I switched to using that chunk of disk as: newfs /dev/$tmp mount /dev/$tmp /scratch This seems to work initially -- the file system is created at boot. I was able to untar a sizable tarball onto it. I opened a file under /scratch in vi and was able to browse it, but on trying to :q, the editor hung and is still hung as I type this. An attempt to `umount /scratch' is currently hung as: MWCHAN STAT `wdrain D' while a subsequent forcefull `umount -f /scratch' looks slightly different: MWCHAN STAT `devfs D' Attempt to delete the md fails with EBUSY. A big program (kmail) is now hung too, although it is not supposed to look at /scratch: MWCHAN STAT `wdrain D' -- I'm afraid all disk-access is now busted and I'm able to type this only because with my 1Gb or RAM most of the stuff is entirely in cache. The -current kernel is built from Mar 6 sources, but I first observed the problem with an earlier kernel -- a few weeks before. Any hope? Thanks! -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Startup scripts stop in middle of startup
On Wed, 12 Mar 2003 20:55:26 +0100 Aleksander Rozman - Andy [EMAIL PROTECTED] wrote: Did someone encounter the same problem? Is it possible to exactly determine which script is problem (script debuging os something)? put: rc_debug=yes in rc.conf -- Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc [EMAIL PROTECTED] | Fingerprint: D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Panics with GnuPG
I've been running -CURRENT on my workstation for a couple of months, and have been quite impressed. But I've started seeing pretty consistant panics when verifying PGP-signed messages. Everything was fine until I cvsup'ed about two weeks ago, and is still apparent in another cvsup as of March 10. So a rough timeline, I *wasn't* panic'ing about a month ago, and I am now. Anyone else seen something similar? I've managed to write down the actual panic twice (no panic to screen if you're in X), and they both look pretty similar. It seems to be caused directly by GnuPG trying to import a key it doesn't have from a keyserver. So it's not difficult to work around, but it'd be nice to have this working again. :) Here's the panic: Fatal trap 12: page fault in kernel mode fault virtual address = 0x20 fault code = supervisor read, page not present instruction pointer = 0x8:0xc023faf6 stack pointer = 0x10:0xdf10faa0 frame pointer = 0x10:0xdf10fac4 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 = 11 (swi1: net) trap number = 12 panic: page fault And I just reproduced the panic, by typing: % gpg --recv-key BB6BC940 In case anyone asks, yes, it is the same version of GnuPG, and yes, I have already tried recompiling it since the new buildworld. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: crash: bwrite: need chained iodone
On Wed, 12 Mar 2003, Thomas Quinot wrote:
Le 2003-03-12, Jeff Roberson écrivait :
Can you please print bp? I'd like to know what all of the members are. A
cluster buf should NEVER have BX_BKGRDWRITE set. This is totally bogus.
(kgdb) fr
#11 0xc0232072 in bwrite (bp=0xce5313e0) at
/usr/src/sys/kern/vfs_bio.c:795
795 panic(bwrite: need chained iodone);
(kgdb) print *bp
$3 = {b_io = {bio_cmd = 2, bio_dev = 0x, bio_disk = 0x0,
bio_blkno = 18540672, bio_offset = 9492758528, bio_bcount = 32768,
bio_data = 0xd42da000 , bio_flags = 0, bio_error = 0, bio_resid = 0,
bio_done = 0xc0235db0 bufdonebio, bio_driver1 = 0x0, bio_driver2 = 0x0,
bio_caller1 = 0x0, bio_caller2 = 0xce5313e0, bio_queue = {tqe_next = 0x0,
tqe_prev = 0xc408200c}, bio_attribute = 0x0, bio_from = 0x0,
bio_to = 0x0, bio_length = 0, bio_completed = 0, bio_children = 91,
bio_inbed = 0, bio_parent = 0x0, bio_t0 = {sec = 0, frac = 0},
bio_task = 0, bio_task_arg = 0x0, bio_pblkno = 64}, b_op = 0xc03a89f8,
b_magic = 280038160, b_iodone = 0xc0239320 cluster_callback,
b_offset = 688128, b_vnbufs = {tqe_next = 0x0, tqe_prev = 0x0},
b_left = 0x0, b_right = 0x0, b_vflags = 0, b_freelist = {
tqe_next = 0xce531228, tqe_prev = 0xc03dcb3c}, b_qindex = 0,
b_flags = 1677721604, b_xflags = 0 '\0', b_lock = {
lk_interlock = 0xc03d750c, lk_flags = 0, lk_sharecount = 0,
lk_waitcount = 0, lk_exclusivecount = 0, lk_prio = 80,
lk_wmesg = 0xc0379b53 bufwait, lk_timo = 0, lk_lockholder = 0x,
lk_newlock = 0x0}, b_bufsize = 32768, b_runningbufspace = 0,
b_kvabase = 0xd42da000 , b_kvasize = 32768, b_lblkno = 42,
b_vp = 0xc4a21124, b_object = 0x0, b_dirtyoff = 0, b_dirtyend = 32768,
b_rcred = 0x0, b_wcred = 0x0, b_saveaddr = 0xbfbfea40, b_pager = {
pg_spc = 0x0, pg_reqpage = 0}, b_cluster = {cluster_head = {
tqh_first = 0xce67bfe8, tqh_last = 0xce6b6b80}, cluster_entry = {
tqe_next = 0xce67bfe8, tqe_prev = 0xce6b6b80}}, b_pages = {0xc0d14748,
0xc0acff90, 0xc0a7cbd8, 0xc0bffc20, 0xc1074868, 0xc10106b0, 0xc10700f8,
0xc0f9c040, 0xc0af5808, 0xc0c56c50, 0xc0b47198, 0xc0bdb9e0, 0xc10e7b28,
0xc0abba70, 0xc09888b8, 0xc09d3600, 0xc0d14748, 0xc0acff90, 0xc0a7cbd8,
0xc0bffc20, 0xc1074868, 0xc10106b0, 0xc10700f8, 0xc0f9c040, 0xc0d21888,
0xc105cfd0, 0xc1057f18, 0xc109ff60, 0xc0a18948, 0xc0ab3d90, 0xc0a36fd8,
0xc0b91820}, b_npages = 8, b_dep = {lh_first = 0x0}}
(kgdb)
Hum. Now this is *most* peculiar. bp-b_xflags is 0, so we should never
have entered that 'if', unless there is a race condition somewhere such
that we test b_xflags on a buffer and carry on processing on another...
Can you disable sync on panic to make sure that something has not come
along and cleaned this buffer? I suspect that it has been modified after
the first panic. Do you know when this first started to happen? Do you
have any more clues into what triggered it?
Cheers,
Jeff
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Still getting panic on boot. (fwd)
oops, didn't cc this to the list -- Forwarded message -- Date: Wed, 12 Mar 2003 15:50:01 -0500 (EST) From: Bryan Liesner [EMAIL PROTECTED] To: Shizuka Kudo [EMAIL PROTECTED] Subject: Re: Still getting panic on boot. On Wed, 12 Mar 2003, Shizuka Kudo wrote: --- walt [EMAIL PROTECTED] wrote: 04:00 GMT Mar 12: Just cvsup'd and rebuilt with same result as 12 hours ago -- I see a kernel panic page fault while in kernel mode just after attempting to mount the root filesystem. The kernel from yesterday works fine and when I reboot the filesystems come up clean, so the new kernel nevers writes to disk, apparently. Am I the only one seeing this? I saw the same here. However, after reboot with the same faulty kernel, it may not panic but doesn't have the /dev/null entry which makes the bootup process failed. In addition, my -current was cvsup'd about four hours ago. I'm seeing the same thing - /dev/null disappeared. I also saw in my nightly scripts that 'tee /dev/stderr' failed as well. It seems fairly random. X wouldn't start, complaining that /dev/vga doesn't exist. I did a cvsup by date/time: *default release=cvs date=2003.03.10.12.00.00 tag=. That seems to put things right. There were some kern commits shortly after that time that caused this weirdness. I've been really busy at work fixing a billion bugs for c client rollout - no time for a backtrace... ( the bugs aren't mine - I write perfect code every time :) ) -- == = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = [EMAIL PROTECTED]Home of the Gipper= == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panics with GnuPG
Wow. That's quite a trick. I've CVSup'ed, buildworld/kernel and freshly installed gpg, within the last two hours. [EMAIL PROTECTED]:/home/brent $ gpg --keyserver pgp.mit.edu --recv-key BB6BC940 and then it dies... Brent On Wednesday, Mar 12, 2003, at 14:45 America/Denver, Damian Gerow wrote: Thus spake Brent Jones ([EMAIL PROTECTED]) [03.03.12 16:41]: Can you tell me the keyserver you're using? In ~/.gnupg/gpg.conf: keyserver x-hkp://pgp.mit.edu When I type: % gpg --recv-key BB6BC940 I panic. I'd *really* like to try other keyservers, but I've already lost about three hours today (my own fault, I know, I'm not complaining about FBSD whatsoever) in panics, and I'm feeling a little behind. -- Brent Jones Phone: 505.984.8800 ext. 225 Director of Computing Santa Fe Institute PGP Key ID: 0xEE820415 1399 Hyde Park Rd. GPG Key ID: 0xC50A0BC0 Santa Fe, NM 87501 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panics with GnuPG
On Wed, 12 Mar 2003, Brent Jones wrote: Wow. That's quite a trick. I've CVSup'ed, buildworld/kernel and freshly installed gpg, within the last two hours. [EMAIL PROTECTED]:/home/brent $ gpg --keyserver pgp.mit.edu --recv-key BB6BC940 and then it dies... Brent On Wednesday, Mar 12, 2003, at 14:45 America/Denver, Damian Gerow wrote: Thus spake Brent Jones ([EMAIL PROTECTED]) [03.03.12 16:41]: Can you tell me the keyserver you're using? In ~/.gnupg/gpg.conf: keyserver x-hkp://pgp.mit.edu When I type: % gpg --recv-key BB6BC940 I panic. I'd *really* like to try other keyservers, but I've already lost about three hours today (my own fault, I know, I'm not complaining about FBSD whatsoever) in panics, and I'm feeling a little behind. With the latest code, panics happen when running almost anything. I triggered a panic typing in man acpi... -- == = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = [EMAIL PROTECTED]Home of the Gipper= == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: latest working snapshot?
David O'Brien wrote: On Wed, Mar 12, 2003 at 10:32:02PM +0200, Ruslan Ermilov wrote: On Wed, Mar 12, 2003 at 02:14:25PM -0500, Andrew Gallatin wrote: I need to install current on a new box that just arrived. What's the latest working snapshot? 20030312-JPSNAP get about 40% of the way through the base install and sysinstall complains about a bad realloc, and lets me hit a key to reboot ;-( You're just lucky. Mine just panics. I wonder how long this has been happening -- 12-Feb-2003 also panics for me. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Commits shortly after 3/10 are causing weirdness. Looks like this has been happening (at least for me) after 3/10. Last night, I came home from work, touched my keyboard, and it panic'd. I thought it was strange, the machine was on all day and I was logging in and out at various times from work. After a few reboots, I noticed that it wasn't panicking in the same place. Sometimes before mounting. Sometimes while running init. Sometimes while starting sendmail. Sometimes not at all. Once, I thought it was up, but with the console was hosed, so I tried to telnet in from my wife's system. That succeeded, caused it to panic, and the message was: remaking ttyp0 don't do that panic... I have seen disappearing devices like /dev/null and stderr missing at boot time or just going away while the system is up. -- == = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = [EMAIL PROTECTED]Home of the Gipper= == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: C++ Exception handling with shared libs in current is broken again
I do know now why I have again problems with building openoffice.
It seems that exceptions over shared libraries are broken again in
CURRENT.
Alexander, do you have a idea why this got broken again ?
rtld from 19.October has the same problem. I guess it must be gcc3.2
which is the problem.
[This response addresses your other thread as well:
ld -Bsharable broken in CURRENT ?]
Hi Martin,
If you really want to directly use ld to build a shared C++ image,
then you will need to do additional study because a lot of things
changed between gcc 2 (used longjump-based EH) and gcc 3 (dwarf-region
based EH, requires more environment support). From gcc 3.2.2
documentation as installed on CURRENT (regarding the *only* supported
way to make a C++ shared library): However, if a library or main
executable is supposed to throw or catch exceptions, you must link it
using the G++ or GCJ driver, as appropriate for the languages used in
the program, or using the option @option{-shared-libgcc} [to the gcc
driver], such that it is linked with the shared @file{libgcc}.
Now, FreeBSD might have guaranteed other ways in the past, but from
the gcc side of things, this is the only supported way to make a C++
shared image with gcc3 on modern ELF platforms:
foo.so: foo.o
${CXX} -shared -o foo.so foo.o
Regards,
Loren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: C++ Exception handling with shared libs in current is brokenagain
Hi, the gcc side of things, this is the only supported way to make a C++ shared image with gcc3 on modern ELF platforms: Thank you even I have found that out myself too :) Using ld directly is a no-go for a gcc3.2 platform. Linking with the crt files fixes the problem. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: C++ Exception handling with shared libs in current is broken again
Thank you even I have found that out myself too :) Using ld directly is a no-go for a gcc3.2 platform. Linking with the crt files fixes the problem. OK, cool. BTW, in case you care, the exact reason why you now need the startup file wrappers in the shared image with gcc3 style EH but not with gcc2 style EH: There are special ELF constructors/destructors hook symbols which are registered/found on a per-shared image basis by the Dwarf EH walking code... If those aren't present, then it doesn't work (the gcc mainline reports an error message before coring with your example code). Although it seems odd, all that support comes in the startup code. Did using ld directly ever work on CURRENT after the first upgrade to gcc 3? I suppose it might have worked the gcc 2.95 way in gcc 3.1 since we were slow to adopt support for some of the newer ELF features in the FSF copy of gcc. -Loren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: devstat_end_transaction: HELP!! busy_count for da1 is 0 (-1)!
Lars Eggert wrote: Poul-Henning Kamp wrote: Yes, I just got this myself today. I overlooked that devstat is not locked when I moved the devstat to geom_disk. Expect a patch tonight. There is a patch which can be tried at: http://phk.freebsd.dk/patch/ken.patch Seeing the same messages, going through a buildworld w/the patch now and will let you know if it helps. Seems to fix things for me! Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
GBDE automation scripts?
I am writing a section for the Handbook on how to use gbde. Currently, using gbde is a rather manual process. Each time a host reboots, the admin needs to attach the gbde device(s), enter any required passphrases, manually fsck the partition, and mount it. I suspect some subscribers to this mailing list have scripts in place to at least partially automate the process. If you have such a script, could you please get in touch with me for inclusion of the script in the Handbook? What I am looking for is something along the following lines: At the low end: a script that takes a list of gbde-encrypted file systems stored in an fstab-like file that contains the names of the gbde lock files together with their ultimate mount points. Think of this file as an /etc/fstab.gbde. The script then prompts the admin for the required passphrases, and completes the remainder of the tasks though mounting the attached partitions. For simplicity, the script could assume that the gbde lock files are all stored in /etc/gbde/ and are named with the name of the underlying device. At the not quite so low end: same as above, but the script will try an admin-provided passphrase on all gbde devices, only asking the admin to provide additional passphrases if the decryption does not yield a file system that mount knows about. Rationale: Few will use 4 passphrases to encrypt /aux1 through /aux4 and the user probably doesn't want to be prompted multiple times, once for each device, to enter the same passphrase multiple times. Much better user experience: extend fstab(5) to hold the information that would under the earlier scenarios have been stored in /etc/fstab.gbde. Of course the gbde devices listed in /etc/fstab should not be auto-mounted during boot. Then extend mount with an argument to mount encrypted partitions based on the information stored in /etc/fstab, asking the user for a passphrase as needed. Hey, one can hope. ;) Either way, if you have any scripts that do even part of what I am describing, please get in touch with time. Thanks, --Lucky To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GBDE automation scripts?
On Wed, Mar 12, 2003 at 05:39:01PM -0800, Lucky Green wrote: I am writing a section for the Handbook on how to use gbde. Currently, using gbde is a rather manual process. Each time a host reboots, the admin needs to attach the gbde device(s), enter any required passphrases, manually fsck the partition, and mount it. I suspect some subscribers to this mailing list have scripts in place to at least partially automate the process. If you have such a script, could you please get in touch with me for inclusion of the script in the Handbook? I suggest getting it added to the ports tree, or perhaps the base system itself. PHK might have a preference along these lines. Putting it in the Handbook isn't my idea of being a good place to maintain actual programs. Just a thought. Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[no subject]
I found on tty0 the following backtrace. I infer, because it died in malloc, that it has something to do with netisr problem. I had to copy it by hand. backtrace(c04b7645,4,1,0,c40be100) at backtrace+0x17 malloc(3c,c050fca0,4,c1531300,d67e6c78) at malloc+0x5b mtag_alloc(0,e,30,4,c151ac00) at mtag_alloc+0x2f ip6_addaux(c1531300,d6706cbc,c037b09c,c1531300,c151ac00) at ip6_addaux+0x59 ip6_setdstifaddr(c1531300,c151ac00,d6te6cbc,c02d2480,c057a254) at ip6_setdstifaddr+0x11 ip6_input(c1531300,0,c04c0a40,e9,c1513ac00) at ip6_input+0x78c swi_net(0,0,c04b672f,217,c15209ec) at swi_net+0x112 ithread_loop(c151f200,d67e6048,c04b65ac,35f,0) at ithread_loop+0x182 fork_exit(c02c95e0,c151f200,d67e6048) at fork_exit+0xc4 fork_trampoline() at fork_trampoline+0x1a --- trap 0x1, eip=0, esp=0xd67e6d7c, ebp=0 --- -- Derek Tattersall[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
trap in netisr...
I found on tty0 the following backtrace. I infer, because it died in malloc, that it has something to do with netisr problem. I had to copy it by hand. backtrace(c04b7645,4,1,0,c40be100) at backtrace+0x17 malloc(3c,c050fca0,4,c1531300,d67e6c78) at malloc+0x5b mtag_alloc(0,e,30,4,c151ac00) at mtag_alloc+0x2f ip6_addaux(c1531300,d6706cbc,c037b09c,c1531300,c151ac00) at ip6_addaux+0x59 ip6_setdstifaddr(c1531300,c151ac00,d6te6cbc,c02d2480,c057a254) at ip6_setdstifaddr+0x11 ip6_input(c1531300,0,c04c0a40,e9,c1513ac00) at ip6_input+0x78c swi_net(0,0,c04b672f,217,c15209ec) at swi_net+0x112 ithread_loop(c151f200,d67e6048,c04b65ac,35f,0) at ithread_loop+0x182 fork_exit(c02c95e0,c151f200,d67e6048) at fork_exit+0xc4 fork_trampoline() at fork_trampoline+0x1a --- trap 0x1, eip=0, esp=0xd67e6d7c, ebp=0 --- -- Derek Tattersall[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
vfs panic on 2003-03-11(cvsuped)
Panic in my environment. # uname -a FreeBSD ***.*-.*** 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Wed Mar 12 18:39:05 JST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MELFINA i386 There are no dmesg in vmcore.0, but I saw process name as mount_procfs in after fsck(when panic). So I removed procfs in /etc/fstab. Then there are no problem. # gdb -k /usr/obj/usr/src/sys/MELFINA/kernel.debug vmcore.0 GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-undermydesk-freebsd... panic: bremfree: removing a buffer not on a queue panic messages: --- dmesg: kernel message buffer has different magic number --- #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:239 239 dumping++; (kgdb) bt #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:239 #1 0xc01c68ca in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:371 #2 0xc01c6bc2 in panic () at /usr/src/sys/kern/kern_shutdown.c:542 #3 0xc0209070 in bremfreel (bp=0xce611278) at /usr/src/sys/kern/vfs_bio.c:630 #4 0xc0208f82 in bremfree (bp=0x0) at /usr/src/sys/kern/vfs_bio.c:612 #5 0xc020af4c in vfs_bio_awrite (bp=0x0) at /usr/src/sys/kern/vfs_bio.c:1682 #6 0xc02e0e1a in ffs_fsync (ap=0xd68fdb60) at /usr/src/sys/ufs/ffs/ffs_vnops.c:257 #7 0xc02dfef7 in ffs_sync (mp=0xc43d6000, waitfor=2, cred=0xc150ae80, td=0xc039f640) at vnode_if.h:612 #8 0xc021f9c6 in sync (td=0xc039f640, uap=0x0) at /usr/src/sys/kern/vfs_syscalls.c:138 #9 0xc01c63ef in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:280 #10 0xc01c6bc2 in panic () at /usr/src/sys/kern/kern_shutdown.c:542 #11 0xc02d9152 in softdep_disk_io_initiation (bp=0xce611278) at /usr/src/sys/ufs/ffs/ffs_softdep.c:3466 #12 0xc02118af in cluster_wbuild (vp=0xc56b336c, size=16384, start_lbn=524, len=3) at buf.h:422 #13 0xc020af2a in vfs_bio_awrite (bp=0xce64a690) at /usr/src/sys/kern/vfs_bio.c:1675 #14 0xc020b9a9 in flushbufqueues () at /usr/src/sys/kern/vfs_bio.c:2132 #15 0xc020b775 in buf_daemon () at /usr/src/sys/kern/vfs_bio.c:2054 #16 0xc01b1a73 in fork_exit (callout=0xc020b650 buf_daemon, arg=0x0, frame=0x0) at /usr/src/sys/kern/kern_fork.c:871 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
5.0 Install Kernel
I hope this is okay.. I needed to cross post this for more exposure. Apparently, I need to disable eisa support to successfully boot a kernel on my Dell Inspiron 2650. In 4.x, I would do a `boot -c` followed by `eisa 0`. What about FreeBSD 5.0? I tried `set hint.eisa.0.disabled=1` at the stage 3 boot prompt. It didn't seem to work. Any other ideas? I _really_ need the ACPI support. _Any_ help is appriciated. Thanks in advance, Lucas To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
disappearing devices
Todays sources as of about 22:00 est I built a kernel, rebooted, and built another, which failed with: NM=nm sh /usr/src/sys/kern/genassym.sh genassym.o assym.s /usr/src/sys/kern/genassym.sh: cannot create /dev/stdout: Operation not supported *** Error code 2 Stop in /usr/obj/usr/src/sys/GRAVY. *** Error code 1 One more reboot and another random? panic... -- == = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = [EMAIL PROTECTED]Home of the Gipper= == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panic after sleep.
I experienced the same problem a couple of weeks ago. uname -a FreeBSD george.spyderweb.com.au 5.0-RELEASE FreeBSD 5.0-RELEASE #0: Thu Jan 16 22:16:53 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 The kernel panicked and then spontaneously rebooted. I had no time to record the error message. Regards George Patterson On Wed, 12 Mar 2003 10:01:45 +0100 (CET) Richard Arends [EMAIL PROTECTED] wrote: Hello, My laptop paniced when he tried coming back from a sleep. This happens a few times a week. [snowlap] /var/crash$ uname -a FreeBSD snowlap.unixguru.nl 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Tue Mar 11 15:11:05 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SNOWLAP i386 Script started on Wed Mar 12 09:42:18 2003 snowlap# gdb -k kernel.11-03-2003 vmcore.0 GNU gdb 5.2.1 (FreeBSD) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-undermydesk-freebsd... --- Uptime: 36m36s Terminate ACPI Rebooting... Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Tue Mar 11 15:11:05 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SNOWLAP Preloaded elf kernel /boot/kernel/kernel at 0xc0568000. Preloaded elf module /boot/kernel/acpi.ko at 0xc05680a8. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 797579512 Hz CPU: Intel Pentium III (797.58-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE, MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 401997824 (383 MB) avail memory = 384536576 (366 MB) Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: TOSHIB 750 on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00f01c0 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0xee08-0xee0b on acpi0 acpi_cpu0: CPU port 0x530-0x537 on acpi0 acpi_tz0: thermal zone on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82815 (i815 GMCH) host to PCI bridge mem 0xf000-0xf3ff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 fxp0: Intel Pro/100 Ethernet port 0xdf40-0xdf7f mem 0xf7dff000-0xf7df irq 11 at device 8.0 on pci2 fxp0: Ethernet address 00:00:39:be:6a:32 inphy0: i82562ET 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto cbb0: TI1410 PCI-CardBus Bridge at device 12.0 on pci2 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 pcib2: slot 12 INTA is routed to irq 11 cbb1: ToPIC100 PCI-CardBus Bridge at device 13.0 on pci2 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 pcib2: slot 13 INTA is routed to irq 11 cbb2: ToPIC100 PCI-CardBus Bridge at device 13.1 on pci2 cardbus2: CardBus bus on cbb2 pccard2: 16-bit PCCard bus on cbb2 pcib2: slot 13 INTB is routed to irq 11 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 UDMA100 controller port 0xcff0-0xcfff at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0xcf80-0xcf9f irq 11 at device 31.2 on pci0 usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801BA/BAM (ICH2) USB controller USB-B port 0xcf60-0xcf7f irq 11 at device 31.4 on pci0 usb1: Intel 82801BA/BAM (ICH2) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pcm0: Intel 82801BA (ICH2) port 0xcdc0-0xcdff,0xce00-0xceff irq 11 at device 31.5 on pci0 pcm0: unknown ac97 codec (id=0x594d4800) pci0: simple comms at device 31.6 (no driver attached) acpi_lid0: Control Method Lid Switch on acpi0 acpi_cmbat0: Control method Battery on acpi0 acpi_acad0: AC adapter on acpi0 speaker0 port 0x61 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
Re: trap in netisr...
I found on tty0 the following backtrace. I infer, because it died in malloc, that it has something to do with netisr problem. I had to copy it by hand. backtrace(c04b7645,4,1,0,c40be100) at backtrace+0x17 malloc(3c,c050fca0,4,c1531300,d67e6c78) at malloc+0x5b mtag_alloc(0,e,30,4,c151ac00) at mtag_alloc+0x2f ip6_addaux(c1531300,d6706cbc,c037b09c,c1531300,c151ac00) at ip6_addaux+0x59 ip6_setdstifaddr(c1531300,c151ac00,d6te6cbc,c02d2480,c057a254) at ip6_setdstifaddr+0x11 ip6_input(c1531300,0,c04c0a40,e9,c1513ac00) at ip6_input+0x78c swi_net(0,0,c04b672f,217,c15209ec) at swi_net+0x112 ithread_loop(c151f200,d67e6048,c04b65ac,35f,0) at ithread_loop+0x182 fork_exit(c02c95e0,c151f200,d67e6048) at fork_exit+0xc4 fork_trampoline() at fork_trampoline+0x1a --- trap 0x1, eip=0, esp=0xd67e6d7c, ebp=0 --- Fixed last night. Sam To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
big file became broken on 2003-03-11(cvsuped)
Big file like OOo_1.0.2_source.tar.bz2 became broken with making openoffice in my environment. # uname -a FreeBSD ***.*-.*** 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Wed Mar 12 18:39:05 JST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MELFINA i386 # mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/md0 on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /export (ufs, local, soft-updates) /dev/ad0s1d on /usr (ufs, local, soft-updates) /dev/ad0s1e on /var (ufs, local, soft-updates) /usr/compat on /compat (nullfs, local) linprocfs on /compat/linux/proc (linprocfs, local) /export/home on /home (nullfs, local) I tested on /, /var, /usr, /home, /tmp. There is a same problem. # cd /any/partition; scp -p mystable.machine:/usr/ports/distfiles/openoffice/OOo_1.0.2_source.tar.bz2 .; chflags schg OOo_1.0.2_source.tar.bz2; while true; do md5 OOo_1.0.2_source.tar.bz2; sleep 1; done OOo_1.0.2_source.tar 100% |*| 154 MB00:41 MD5 (OOo_1.0.2_source.tar.bz2) = 8a82b4dbdd4e305b6f6db70ea65dce8c MD5 (OOo_1.0.2_source.tar.bz2) = 8a82b4dbdd4e305b6f6db70ea65dce8c (snip) MD5 (OOo_1.0.2_source.tar.bz2) = 83d7c6e49bb4586ba9b8478798952c29 MD5 (OOo_1.0.2_source.tar.bz2) = 83d7c6e49bb4586ba9b8478798952c29 (snip) MD5 (OOo_1.0.2_source.tar.bz2) = 142ee73901a58445ebd4cccb3d0af223 MD5 (OOo_1.0.2_source.tar.bz2) = 2e9fa2b1b924595eb11760cd728ade95 MD5 (OOo_1.0.2_source.tar.bz2) = c3eee272f6f9b4c90f10c8ca0a2eb537 : To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: bluetooth BW-BH02U reset failure
Hello Takahiko,
At first, I installed 5-CURRENT on P3 machine and sync with cvsup to
latest. and overwrite 2003-03-05 maksim's bluetooth modules.
please verify that tarball you have downloaded has both kernel
and userland stuff, i.e. you have sys, share, usr.bin and usr.sbin
in the snapshot's src/ directory. if not please download updated
snapshot from the same location.
I tried to use planex(http://www.planex.co.jp/) BW-BH02U BlueTooth USB
dongle.
I plugged BW-BH02U in to FreeBSD without any ko module. FreeBSD found
that device with ugen0. following message got with usbdevs -v and udesc_dump.
ugen(4) is generic USB device driver. you need to load ng_ubt(4) driver
before plugging your device.
ugen0: Broadcom product 0x2033, rev 1.01/0.a0, addr 2
from ng_ubt.[ch]
{ USB_VENDOR_BROADCOM, USB_PRODUCT_DBW_120M_BT_DONGLE },
#define USB_PRODUCT_DBW_120M_BT_DONGLE 0x2033 /* D-Link DBW-120M */
your device already supported by ng_ubt(4) driver.
[...]
These message asked BW-BH02U is like BroadCom Product 2033. I think
this device similar D-Link DBW-120M.
yes, it is :)
After, I disconnect BW-BH02U and load ng_ubt.ko. I plugged BW-BH02U
again. FreeBSD found that module with ubt0.
It looks like work then I try to run rc.bluetooth start ubt0.
rc.bluetooth is provided maksim's 2003-02-10 version.
Unfortunately, rc.bluetooth has problem with hccontrol ubt0hci reset
command. This error message is following..
Could not execute command reset. Operation timed out
hmm... strange. now i'm confused. i could not find any info on
D-Link DBW-120M, but there is D-Link DWB-120M. it could be that
i mistyped the name. is that the one you have
http://www.dlink.com/products/usb/dwb120m/
the bad news is that page says its Mac only. also it seems in order
to make D-Link DWB-120M work on PC you need to download some sort of
firmware into it.
according to D-Link there is another adapter D-Link DBT-120
http://www.dlink.com/products/usb/dbt120/
and the page says it works with Mac PC. also to make things very
confusing according to BlueZ page there are two revisions of DBT-120.
One has Broadcomm chip (Rev A1) and other CSR chip (Rev B1). The
version with Broadcomm chip (Rev A1) also needs firmware download.
Version with CSR chip (Rev B1) works just as it is.
i will have to go back to the original tester for clarification on that.
sorry i do not have this device my self.
[...]
I don't know this error related from USB, BT or others. If you have any
ideas, please give me suggestions.
if you have original D-Link DWB-120M or D-Link DBT-120 (Rev A1) than
for now you out of luck :( i need to get one of these devices myself
to figure out how to download firmware and add proper support in ng_ubt(4)
driver. i have downloaded w2k driver for D-Link DBT-120 and will try
to poke around later.
thanks,
max
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: big file became broken on 2003-03-11(cvsuped)
On Thu, 13 Mar 2003, Norikatsu Shigemura wrote: Big file like OOo_1.0.2_source.tar.bz2 became broken with making openoffice in my environment. How much memory is in your machine? Can you go back to an earlier date and see if this is still a problem? Are you doing anything else with the machine while this is going on? Thanks, Jeff # uname -a FreeBSD ***.*-.*** 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Wed Mar 12 18:39:05 JST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MELFINA i386 # mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/md0 on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /export (ufs, local, soft-updates) /dev/ad0s1d on /usr (ufs, local, soft-updates) /dev/ad0s1e on /var (ufs, local, soft-updates) /usr/compat on /compat (nullfs, local) linprocfs on /compat/linux/proc (linprocfs, local) /export/home on /home (nullfs, local) I tested on /, /var, /usr, /home, /tmp. There is a same problem. # cd /any/partition; scp -p mystable.machine:/usr/ports/distfiles/openoffice/OOo_1.0.2_source.tar.bz2 .; chflags schg OOo_1.0.2_source.tar.bz2; while true; do md5 OOo_1.0.2_source.tar.bz2; sleep 1; done OOo_1.0.2_source.tar 100% |*| 154 MB00:41 MD5 (OOo_1.0.2_source.tar.bz2) = 8a82b4dbdd4e305b6f6db70ea65dce8c MD5 (OOo_1.0.2_source.tar.bz2) = 8a82b4dbdd4e305b6f6db70ea65dce8c (snip) MD5 (OOo_1.0.2_source.tar.bz2) = 83d7c6e49bb4586ba9b8478798952c29 MD5 (OOo_1.0.2_source.tar.bz2) = 83d7c6e49bb4586ba9b8478798952c29 (snip) MD5 (OOo_1.0.2_source.tar.bz2) = 142ee73901a58445ebd4cccb3d0af223 MD5 (OOo_1.0.2_source.tar.bz2) = 2e9fa2b1b924595eb11760cd728ade95 MD5 (OOo_1.0.2_source.tar.bz2) = c3eee272f6f9b4c90f10c8ca0a2eb537 : To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: big file became broken on 2003-03-11(cvsuped)
On Thu, 13 Mar 2003, Jeff Roberson wrote: On Thu, 13 Mar 2003, Norikatsu Shigemura wrote: Big file like OOo_1.0.2_source.tar.bz2 became broken with making openoffice in my environment. How much memory is in your machine? Can you go back to an earlier date and see if this is still a problem? Are you doing anything else with the machine while this is going on? Also, can you do 'sysctl vfs.read_max=0' and retest? # uname -a FreeBSD ***.*-.*** 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Wed Mar 12 18:39:05 JST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MELFINA i386 # mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/md0 on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /export (ufs, local, soft-updates) /dev/ad0s1d on /usr (ufs, local, soft-updates) /dev/ad0s1e on /var (ufs, local, soft-updates) /usr/compat on /compat (nullfs, local) linprocfs on /compat/linux/proc (linprocfs, local) /export/home on /home (nullfs, local) I tested on /, /var, /usr, /home, /tmp. There is a same problem. # cd /any/partition; scp -p mystable.machine:/usr/ports/distfiles/openoffice/OOo_1.0.2_source.tar.bz2 .; chflags schg OOo_1.0.2_source.tar.bz2; while true; do md5 OOo_1.0.2_source.tar.bz2; sleep 1; done OOo_1.0.2_source.tar 100% |*| 154 MB00:41 MD5 (OOo_1.0.2_source.tar.bz2) = 8a82b4dbdd4e305b6f6db70ea65dce8c MD5 (OOo_1.0.2_source.tar.bz2) = 8a82b4dbdd4e305b6f6db70ea65dce8c (snip) MD5 (OOo_1.0.2_source.tar.bz2) = 83d7c6e49bb4586ba9b8478798952c29 MD5 (OOo_1.0.2_source.tar.bz2) = 83d7c6e49bb4586ba9b8478798952c29 (snip) MD5 (OOo_1.0.2_source.tar.bz2) = 142ee73901a58445ebd4cccb3d0af223 MD5 (OOo_1.0.2_source.tar.bz2) = 2e9fa2b1b924595eb11760cd728ade95 MD5 (OOo_1.0.2_source.tar.bz2) = c3eee272f6f9b4c90f10c8ca0a2eb537 : To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
can't boot with twe anymore.
I can't boot with twe now. I wind up calling into device_printf with a NULL dev_t which used to crash me until my most recent commit. Now I get: unknown0: controller error - unit not available (flags = 0x0) twe0: AEN: drive error for unknown unit 0 A kernel from Feb 14th seems fine. Please fix. -- -Alfred Perlstein [EMAIL PROTECTED] 'Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: big file became broken on 2003-03-11(cvsuped)
On Thu, 13 Mar 2003, Jeff Roberson wrote: On Thu, 13 Mar 2003, Norikatsu Shigemura wrote: Big file like OOo_1.0.2_source.tar.bz2 became broken with making openoffice in my environment. How much memory is in your machine? Can you go back to an earlier date and see if this is still a problem? Are you doing anything else with the machine while this is going on? Also, can you do 'sysctl vfs.read_max=0' and retest? I am not able to reproduce this. # uname -a FreeBSD ***.*-.*** 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Wed Mar 12 18:39:05 JST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MELFINA i386 # mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/md0 on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /export (ufs, local, soft-updates) /dev/ad0s1d on /usr (ufs, local, soft-updates) /dev/ad0s1e on /var (ufs, local, soft-updates) /usr/compat on /compat (nullfs, local) linprocfs on /compat/linux/proc (linprocfs, local) /export/home on /home (nullfs, local) I tested on /, /var, /usr, /home, /tmp. There is a same problem. # cd /any/partition; scp -p mystable.machine:/usr/ports/distfiles/openoffice/OOo_1.0.2_source.tar.bz2 .; chflags schg OOo_1.0.2_source.tar.bz2; while true; do md5 OOo_1.0.2_source.tar.bz2; sleep 1; done OOo_1.0.2_source.tar 100% |*| 154 MB00:41 MD5 (OOo_1.0.2_source.tar.bz2) = 8a82b4dbdd4e305b6f6db70ea65dce8c MD5 (OOo_1.0.2_source.tar.bz2) = 8a82b4dbdd4e305b6f6db70ea65dce8c (snip) MD5 (OOo_1.0.2_source.tar.bz2) = 83d7c6e49bb4586ba9b8478798952c29 MD5 (OOo_1.0.2_source.tar.bz2) = 83d7c6e49bb4586ba9b8478798952c29 (snip) MD5 (OOo_1.0.2_source.tar.bz2) = 142ee73901a58445ebd4cccb3d0af223 MD5 (OOo_1.0.2_source.tar.bz2) = 2e9fa2b1b924595eb11760cd728ade95 MD5 (OOo_1.0.2_source.tar.bz2) = c3eee272f6f9b4c90f10c8ca0a2eb537 : To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Time drift.
Brooks Davis [EMAIL PROTECTED] writes: I have one machine which failes to keep decent time with ACPI enabled, but it's more like .5sec/sec. Disabling ACPI fixed that machine (it's an old thin client so I don't care if it stops being supported at some point). You don't need to disable ACPI completely, just add debug.acpi.disable=timer to /boot/loader.conf. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Time drift.
In the last episode (Mar 12), Poul-Henning Kamp said: In message [EMAIL PROTECTED], Andrew P. Lentvorski, Jr. writes: An $8.00 wristwatch has much better time accuracy that your multi-$100 PC. That's because the crystal in your wristwatch is cut specially so that it has a flat temp-co at about 23-16 C, whereas the xtal in your computer is has a gradient all the way from 0 to 70 C. See: http://www.corningfrequency.com/library/vig/Vig-tutorial_files/frame.htm http://www.corningfrequency.com/library/vig/vig-tutorial.pdf http://www.corningfrequency.com/library/vig/vig-tutorial.ppt -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FBSD 5.0 diskless environment does not work!
On Tue, 11 Mar 2003, M. Warner Losh wrote: :In message: [EMAIL PROTECTED] :Hartmann, O. [EMAIL PROTECTED] writes: :: Can anyone help? Has someone a runnng diskless FBSD 5.0-R/5-CURRENT :: environment? : :I fixed a couple of bugs in the /etc/rc.d files that broke diskless :boots about a month or two so after 5.0-RELEASE. It would have :precluded diskless systems network from working most of the time. : :Warner : Dear Warner. I cvsupdate, build worl and already mergmastered the newest stuff from FreeBSD 5.0-CURRENT to avoid being outdated. Possibly I should repeat in short terms what I did when 'migrating' from the working 4.X diskless system to the 5.0 system. I backuped everything so I can switch back to the working stuff. I installed a clear, fresh copy of a FreeBSD 5.0-CURRENT into the root path of the diskless stations, e.g. for the X11 terminals this is /usr/diskless/xterm. I populated ROOT/conf/[base,default,IP. as well as ROOT/etc. The config looks like very primitive and I did the whole config from scratch, so there should nothing be left from the 4.0 config. DHCP (isc-dhcpd) works like it worked before, no changes. The diskless station offers a request via PXE (Intel fxp device), gets IP and pxeboot file, loads kernel, bootstraps kernel and then does the whole stuff as it would be a standalone machine. It does not touch the diskless scripts! I checked this by adding some echo lines which reflect that those scripts has been involved. It seems to me that after the kernel has been booted and the init process is walking through all the configurations the system does not recognize itself being diskless. I'm sorry, I have no glue how this gets figured out, maybe there should be a special marker in some of the loader files or in device.hints or within KERNEL config. If I can figure out what is to do I would probably be able to boot into diskless. If I understand what the rc_ng system is doing, the first script is initdiskless in the hierarchy. But it does not get touched anyway. Next I try is to figure out whether there is a kernel-switch which could be set by some loader.conf tags telling that this kernel is some diskless kernel ... Sorry bothering you and wasting your time. Oliver -- MfG O. Hartmann [EMAIL PROTECTED] -- Systemadministration des Institutes fuer Physik der Atmosphaere (IPA) -- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 (Buero) FAX: +496131/3923532 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FBSD 5.0 diskless environment does not work!
On Wed, Mar 12, 2003 at 03:43:52PM +0100, Hartmann, O. wrote: Possibly I should repeat in short terms what I did when 'migrating' from the working 4.X diskless system to the 5.0 system. I think some of the directory layout needed for diskless nfs booting was frobbed by dillon a few months ago (I had some trouble updating my diskless machines past this change, although I think that was mostly because of a typo in his commit that went unnoticed/untested for a few months). Compare your previous installation to the comments in rc.diskless (and I presume, the manpage). Kris pgp0.pgp Description: PGP signature
Re: FBSD 5.0 diskless environment does not work!
On Wed, 12 Mar 2003, Kris Kennaway wrote:
Dear Kris.
At the momnent I do several stupid tasks on the faulty environment
and I got several new informations which are hopefully helpful.
I deleted all rc.* files in etc except rc and rc.subr because they
seem to be needed. I wish to use rc_ng and therefore configured
rc.conf (by default it does).
Within rc I found this line:
files=`rcorder -k ${os} -s nostart /etc/rc.d/* 2/dev/null`
It shows us the order in which the rc.d/-located scripts get passed
through. The first one is 'initdiskless', when I do
files=`rcorder -k FreeBSD -s nostart *
being within the rc.d of the diskless environment.
Just for fun I provided this file with an additional line at the first
place it should show me something like
echo Hello, this is initdiskless
and then tried to boot the diskless station again.
The boot process was normal, kernel got bootstrapped but this specific file
never got touched (in meanwhile I tried to set manually 'nfs.diskless_valid=1'
in boot/loader.conf.local).
I think something got wind up in rc or rc.subr that prevents initdiskless get
executed. I'm not competent to do the work (braindamaged, stupid guy I am...).
Maybe there is another tricky point on which the whole thing collapses which
is invisible to me.
I nice feature would be to have some 'knob' switching on/off debugging, maybe
this is possible or already realized in the shell? How to do the verbosity task?
Within an other experiment I tried the old way to pass through the init scripts,
means: using the old rc.*-styles.
Then I get another weird error message. These scripts obviously walk through
rc.diskless1
and rc.diskless2 but I got a failure about a missing device md0c, which means to me:
no RAM disk. And therefore all subsequent errors are relying on this because the
copy actions fail.
Bytheway, I do not know how to do a fast and 'out of the long bug report way' bug
report: while the newest 5.0-CURRENT stuff got rid of Kerberos IV, thenaming of the
kerberos/heimdal services did some changing and in /etc/defaults/rc.conf it has
to be
kadmind5_server=/usr/libexec/kadmind # path to kerberos 5 admin daemon
^
instead of
kadmind5_server=/usr/libexec/k5admind # path to kerberos 5 admin daemon
.
Best wishes and thanks for your quick response,
Oliver
:On Wed, Mar 12, 2003 at 03:43:52PM +0100, Hartmann, O. wrote:
:
: Possibly I should repeat in short terms what I did when 'migrating'
: from the working 4.X diskless system to the 5.0 system.
:
:I think some of the directory layout needed for diskless nfs booting
:was frobbed by dillon a few months ago (I had some trouble updating my
:diskless machines past this change, although I think that was mostly
:because of a typo in his commit that went unnoticed/untested for a few
:months). Compare your previous installation to the comments in
:rc.diskless (and I presume, the manpage).
:
:Kris
:
--
MfG
O. Hartmann
[EMAIL PROTECTED]
--
Systemadministration des Institutes fuer Physik der Atmosphaere (IPA)
--
Johannes Gutenberg Universitaet Mainz
Becherweg 21
55099 Mainz
Tel: +496131/3924662 (Maschinenraum)
Tel: +496131/3924144 (Buero)
FAX: +496131/3923532
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: FBSD 5.0 diskless environment does not work!
On Wed, 12 Mar 2003 19:56:47 +0100 (CET) Hartmann, O. [EMAIL PROTECTED] wrote: I nice feature would be to have some 'knob' switching on/off debugging, maybe this is possible or already realized in the shell? How to do the verbosity task? rc_debug=yes -- Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc [EMAIL PROTECTED] | Fingerprint: D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FBSD 5.0 diskless environment does not work!
On Wed, 12 Mar 2003, Kris Kennaway wrote: :On Wed, Mar 12, 2003 at 03:43:52PM +0100, Hartmann, O. wrote: : : Possibly I should repeat in short terms what I did when 'migrating' : from the working 4.X diskless system to the 5.0 system. : :I think some of the directory layout needed for diskless nfs booting :was frobbed by dillon a few months ago (I had some trouble updating my :diskless machines past this change, although I think that was mostly :because of a typo in his commit that went unnoticed/untested for a few :months). Compare your previous installation to the comments in :rc.diskless (and I presume, the manpage). : :Kris : Dear Kris, It's me again. I tried now the old fashioned rc.-script way and that do some 'diskless' recognition. The first row after the kernel has been mounted its root from the server is filled with IP, gateway etc. The next row shows some formating information and reports that md0c (RAM disk?) has been formated. But then the next row shows another error: mount: /dev/md0c: No such file or directory Then a bunch of cp failures shows up and at the end I receive a dhcp.host-name error (but this can be ignored, I think) and kernel drops into /bin/sh as it does when boot fails (and it fails in this case, but I compared it with a normal disk-boot). I did a ls -l on /dev and saw /dev/md0c already there. It seems weird to me ... sorry. rc.d does not work, definitely not. Maybe some of the routines in rc or rc.subr skip over initdiskless or some other essential scripts. I will give up for today, switch back to the running config and images up to tommorrow. Will do tomorrow next investigations ... oliver -- MfG O. Hartmann [EMAIL PROTECTED] -- Systemadministration des Institutes fuer Physik der Atmosphaere (IPA) -- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 (Buero) FAX: +496131/3923532 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
