ONE HUNDRED MiLLioN E-MAiL AddREssES *NEW CD* $99
You want email addresses; we've got lots of fresh ones. Face it, there's no way you're going to extract 400 million email addresses with some flimsy email extractor program you downloaded from the web. You're lucky if you can extract 2 million in a year! Our email addresses are even targeted in 34 different categories to help you reach only the market you want. No need to buy any more directories from the web. We've bought almost all of them for you, cleaned them up including removal of duplicates and flamers, and compiled them into a 4 disk volume for only $139.00 Now you can send emails to millions of people worldwide. Imagine if only a small number out of even 1 million emails sent responded to your email. Don't you think you'd make something out of that? No need to worry if our email addresses will work with your mailing program. We already thought of that and made sure to save all files as text files. Text files are the most universal types of files so they will import easily. Also, there's no limit to how many times you can use our email addresses. Still have more specific questions? We're here to help. You can contact us by email At [EMAIL PROTECTED] make sure to put "ENQUIRY" in the subject line Want to order? Follow the instructions below: [] I want to order online Please complete ONLY section A & B of the order form below and either fax or email it back to us. If you're faxing it, send it to 1-6 30-604-1030 or 1-44 3-659-0730 [] I want to order by Credit Card Please complete section A , B & C of the order form below. For your security, DO NOT email anything with your credit card number on it. Please fax your order form to 1-63 0-604-10 30 or 1-4 43-659-07 30 [] I want to order by Paypal Please complete section A , B & D of the order form below. You can email or fax the order form back to us for processing. Return by fax to 1-630-604-1 030 or 1-443-6 59-0730 \ SECTION A - Products & Shipping (prices are in US$) BULK DIRECTORIES: [] Email Marketing CD with 100 million Addresses $69.00 [] 200 Million Email Addresses on 2 CD's $79.00 [] 1.5 Million USA Business Fax Numbers $49.00 [] PACKAGE "A" - ALL DIRECTORIES ABOVE (3 CDs) $99.00 [] Email Gold CD FRESHLY EXTRACTED 100 Million Addresses $99.00 [] 7 Million Chinese Email Addresses $99.00 [] PACKAGE "B" + PACKAGE "A"- All directories above (4 CDs) $139.00 SPECIALTY DIRECTORIES: [] 1 Million Email Addresses from French speaking countries $69 [] 1 Million Email Addresses from Spanish speaking countries $69 [] 1 Million U.K. only email addresses $69 SHIPPING & HANDLING OPTIONS (YOU MUST SELECT ONE): [] $7 Regular Mail (2 - 4 weeks) [] $15 Priority Mail (1 - 2 weeks) [] $30 Fedex (overnight) For US & Canada Only - Other countries extra, please enquire by phone or email TOTAL:_ US$ / SECTION B - Personal Information Full Name: Company Name: Tel: ( __) ___-__ Email Address:__ Shipping Addresss:___Zip/Postal:___ City:___ State/Province: Country: \ SECTION C - Credit Card Information Card Number: Expiration Date:/CVV2 code (last 3 digits on reverse):__ Type of card : [] Visa [] Mastercard[] American Express Exact name on card:___ Billing Address:Zip/Postal___ City:State/Province:___ Country: Cardholder Signature:__ I hereby authorize F.T. Internat ion al to bill my credit card for the items ordered on this form. I understand that all sales are final and further agree not to dispute this charge. \ SECTION D - Paypal Information Email Address associated with Paypal: Note: After receiving this order form, we will send a payment request to the address above. /
Re: WEIRD! div() broken on -CURRENT?
On Sun, Dec 22, 2002 at 10:40:33AM +1100, Bruce Evans wrote: > > that the pcc struct return convention had something to do with it. > > Did we really mean to change this? It is a relatively recent change. From > cvs history: > > % RCS file: /home/ncvs/src/contrib/gcc/config/freebsd.h,v > % Working file: freebsd.h > % head: 1.37 > % ... > % > % revision 1.37 > % date: 2002/04/30 17:22:42; author: obrien; state: Exp; lines: +34 -460 > % MI bits for Gcc 3.1. > % > > This contains mounds changes, one of which breaks 5-10 (?) years of binary > compatibility within gcc-compiled objects: Actually only a 4 years -- the a.out->ELF cut over broke the "5-10 years of binary compatibility". As mentioned at http://gcc.gnu.org/ml/gcc-patches/2002-01/msg01783.html we really made a mistake when we did the a.out->ELF cut over thus resulting in us breaking the i386 ELF ABI. I have wondered in the past how this affects is with sharing XFree86 binary modules with Linux. That said, the ABI change was not intentional. It was a GCC bug. > % RCS file: /home/ncvs/src/contrib/gcc/config/freebsd.h,v ... > % -#undef DEFAULT_PCC_STRUCT_RETURN > % -#define DEFAULT_PCC_STRUCT_RETURN 0 I moved this setting from the MI file to the i386 MD file. > I think gcc didn't override its default of DEFAULT_PCC_STRUCT_RETURN = 1 > on i386's meany years ago, since bcc uses this method of returning structs > and ISTR copying the gcc behaviour. AFAIK, stock GCC always used DEFAULT_PCC_STRUCT_RETURN=1 for i386 ELF. DEFAULT_PCC_STRUCT_RETURN=0 was the a.out default, as there wasn't a standard one had to adhear to. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Fwd: Re: Testing 5.0-rc2 (5.0-current as of 12/23/02)
All, Sorry about the largely incorehant post previously. Here are some more details: DMESG - I just know someone is going to ask. The bad cookie messages - machine is served by linux running on a sparc. Does not seem to cause a problem. Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #3: Mon Dec 23 14:56:26 PST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BRENDY2 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0694000. Preloaded elf module "/boot/kernel/linux.ko" at 0xc06940a8. Preloaded elf module "/boot/kernel/nvidia.ko" at 0xc0694154. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0694200. Timecounter "i8254" frequency 1193182 Hz CPU: Pentium 4 (1982.53-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febfbff real memory = 536805376 (511 MB) avail memory = 514392064 (490 MB) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00178020, at 0xfec0 Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 Using $PIR table, 9 entries at 0xc00fded0 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 0x4008-0x400b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_cpu2: on acpi0 acpi_cpu3: on acpi0 acpi_tz0: on acpi0 acpi_button0: on acpi0 pcib0: port 0x4000-0x40f7,0xcf8-0xcff on acpi0 pci0: on pcib0 IOAPIC #0 intpin 19 -> irq 2 IOAPIC #0 intpin 23 -> irq 5 pcib1: at device 1.0 on pci0 pci1: on pcib1 IOAPIC #0 intpin 22 -> irq 9 nvidia0: mem 0xe000-0xe007,0xd800-0xdfff,0xe800-0xe8ff irq 9 at device 0.0 on pci1 pcib2: at device 2.0 on pci0 pcib2: could not get PCI interrupt routing table for \\_SB_.PCI0.HUBA - AE_NOT_FOUND pci2: on pcib2 pcib3: at device 31.0 on pci2 pcib3: could not get PCI interrupt routing table for \\_SB_.PCI0.HUBA.HUBB - AE_TYPE pci3: on pcib3 pci3: at device 0.0 (no driver attached) pcib4: at device 30.0 on pci0 pci4: on pcib4 IOAPIC #0 intpin 16 -> irq 10 pcm0: port 0xc000-0xc01f irq 2 at device 3.0 on pci4 fxp0: port 0xc800-0xc83f mem 0xeb00-0xeb0f,0xeb105000-0xeb105fff irq 10 at device 4.0 on pci4 fxp0: Ethernet address 00:30:48:23:23:ca inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci4: at device 7.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd000-0xd01f irq 2 at device 31.2 on pci0 usb0: 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 pci0: at device 31.3 (no driver attached) uhci1: port 0xd400-0xd41f irq 5 at device 31.4 on pci0 usb1: 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 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 orm0: at iomem 0xc-0xcefff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Timecounters tick every 10.000 msec acpi_cpu: CPU throttling enabled, 2 steps from 100% to 50.0% ad0: 43979MB [89355/16/63] at ata0-master UDMA100 acd0: CDROM at ata1-master PIO4 SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ad0s2a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted got bad cookie vp 0xc499b834 bp 0xce5b5050 pid 747 (mozilla-bin), uid 500: exited on signal 11 got bad cookie vp 0xc499b834 bp 0xce65fc00
Re: [acpi-jp 2051] ACPI Issues in FreeBSD 5.0-DP2
In message <004b01c2aade$812bfb00$f100a8c0@JEREMIAH>, "Jeremiah Gowdy" wrote: >I am currently testing FreeBSD 5.0-DP2 on my Sony Vaio FX-210 laptop. I am >having some error messages from the ACPI driver, so I figured I would report >them just in case. If anyone needs any more information, perhaps more >verbose debug output or something, please let me know. > >I am getting the following messages repeatedly at startup. > >ACPI-0432: *** Error: Handler for [EmbeddedControl returned AE_ERROR >ACPI-1287: *** Error: Method execution failed, AE_AML_NO_RETURN_VALUE Please boot with set hw.acpi.ec.event_driven=1 And see the result. >When I hit the sleep button on my computer I get: > >acpi0: AcpiGetSleepTypeDate failed - AE_NOT_FOUND Probably your system does not support the sleep state you want to go. > >This is the output of acpidump: Please use acpidump after booting with following parameter. set acpi_load="NO" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: APM on 5.0 RC1
In message <[EMAIL PROTECTED]>, Sean LeBlanc wrote: >Hello, > >I'm trying to figure out how to get apm to run on 5.0 RC1. I have a Thinkpad >390x; apm worked on 4.7. > >If I run apmd -d, I get: >apmd[776]: start >apmd: cannot open device file `/dev/apmctl': No such file or directory You are running ACPI system, and ACPI does not support apmd, though it supports /dev/apm interface. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
APM on 5.0 RC1
Hello, I'm trying to figure out how to get apm to run on 5.0 RC1. I have a Thinkpad 390x; apm worked on 4.7. If I run apmd -d, I get: apmd[776]: start apmd: cannot open device file `/dev/apmctl': No such file or directory Okay, I think. I look for /dev/MAKEDEV, it's missing. After some googling, it looks like devfs is a new concept replacing MAKEDEV. So I do some reading on this, and try to add a rule per the manpage: lappie# devfs rule add path apm mode 660 devfs rule: ioctl DEVFSIO_RADD: Input/output error Any ideas? -- Sean LeBlanc:[EMAIL PROTECTED] http://users.americanisp.net/~seanleblanc/ Get MLAC at: http://sourceforge.net/projects/mlac/ Above all nations is humanity. -Goldwin Smith (contributed by Chris Johnston) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -CURRENT + UDF = panic
Vladimir Kushnir wrote: I'm not sure for how long but at least last couple of weeks any attempt to mount CD with UDF gives panic: lockmgr: locking against myself plus quiet reboot (no dump, no break to DDB - nothing) on my -CURRENT box. uname -a output: FreeBSD kushnir1.kiev.ua 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Sun Dec 22 12:52:50 EET 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KUSHNIR i386 HW: PIII, 440BX based MB, IDE cdwriter (_NEC CD-RW NR-9100A). Linux on the same computer mounts the same CD perfectly all right, so problem isn't a disk. Is there anything I can do to help to debug this? Regards, Vladimir To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Can you share what program you used to create the udf filesystem? Also, making an image available of the disk might be useful too. Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Testing 5.0-rc2 (5.0-current as of 12/23/02)
All, Just a quick report - testing 5.0 rc2 on a dual xeon 2.0G (Supermicro p4dce+). Seems that if I compile the kernel with CPU greater that I486_CPU, the machine will boot, startx, be usable for a random period of time and then lock up. I dont know if the lockups occur in single CPU mode or not. I have an NVidia Ti4200 card - the fault seems independant of whether I use the NVidia GLX driver or not. Cant find any oopses in /var/log/messages - is that the correct place to look? If theres an information I can provide, please let me know - the lockup is 100% reproducable. Cheers, Brendon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mpt(4): berserk interrupt frequency
Hi,
Can someone who has a mpt(4) device tell me if their interrupt frequency
is as absurd as mine is?
\begin{verbatim}
mckinley% vmstat -i
interrupt total rate
clock 272238 1019
ohci1 1 0
fxp0 347 1
atapci0 4 0
mpt0 8286623314361713943 31036042375886569
mpt1 2314885530819653497 8669983261496829
bge0 2105376 7885
Total10601508845183745406 39706025637392304
\end{verbatim}
I want to know if this is something specific to ia64 or if it's
more commonly seen. Some dmesg(8) output:
\begin{verbatim}
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #261: Mon Dec 23 16:20:39 PST 2002
[EMAIL PROTECTED]:/nfs/p4/ia64/sys/ia64/compile/HP_RX2600
Preloaded elf kernel "/boot/kernel/kernel" at 0xe0b8a000.
:
pcib1: on acpi0
pci32: on pcib1
mpt0: port 0x2100-0x21ff mem
0x9083-0x9083,0x9084-0x9084 irq 27 at device 1.0 on pci32
mpt1: port 0x2000-0x20ff mem
0x9081-0x9081,0x9082-0x9082 irq 28 at device 1.1 on pci32
bge0: mem 0x9080-0x9080 irq 29 at device
2.0 on pci32
:
\end{varbatim}
No interrupt sharing. The following snippet is the result of filtering
dmesg(8) with grep(1) on irq:
\begin{verbatim}
ohci0: mem 0x80023000-0x80023fff irq 16 at device 1.0 on
pci0
ohci1: mem 0x80022000-0x80022fff irq 17 at device 1.1 on
pci0
atapci0: port
0xd40-0xd4f,0xd60-0xd63,0xd50-0xd57,0xd64-0xd67,0xd58-0xd5f irq 21 at device 2.0 on
pci0
fxp0: port 0xd00-0xd3f mem
0x8000-0x8001,0x8002-0x80020fff irq 20 at device 3.0 on pci0
mpt0: port 0x2100-0x21ff mem
0x9083-0x9083,0x9084-0x9084 irq 27 at device 1.0 on pci32
mpt1: port 0x2000-0x20ff mem
0x9081-0x9081,0x9082-0x9082 irq 28 at device 1.1 on pci32
bge0: mem 0x9080-0x9080 irq 29 at device
2.0 on pci32
sio0 iomem 0xff5e-0xff5e0007 irq 34 on acpi0
sio1 iomem 0xff5e2000-0xff5e2007 irq 35 on acpi0
sio2: mem 0xf803-0xf8030fff irq 82 at device
1.1 on pci224
\end{verbatim}
Thanks,
--
Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PAWS ack-on-ack loop avoided
On Mon, Dec 23, 2002 at 10:55:05 -0800, Matthew Dillon wrote: > > That's very odd. I see them on my development box too which is just > talking FreeBSD<->FreeBSD. We should not be seeing them at all. I got about 200 of them per 6 hours. Nothing unusual, small webserver + SMTP. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-CURRENT + UDF = panic
I'm not sure for how long but at least last couple of weeks any attempt to mount CD with UDF gives panic: lockmgr: locking against myself plus quiet reboot (no dump, no break to DDB - nothing) on my -CURRENT box. uname -a output: FreeBSD kushnir1.kiev.ua 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Sun Dec 22 12:52:50 EET 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KUSHNIR i386 HW: PIII, 440BX based MB, IDE cdwriter (_NEC CD-RW NR-9100A). Linux on the same computer mounts the same CD perfectly all right, so problem isn't a disk. Is there anything I can do to help to debug this? Regards, Vladimir To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI Issues in FreeBSD 5.0-DP2
I am currently testing FreeBSD 5.0-DP2 on my Sony Vaio FX-210 laptop. I am
having some error messages from the ACPI driver, so I figured I would report
them just in case. If anyone needs any more information, perhaps more
verbose debug output or something, please let me know.
I am getting the following messages repeatedly at startup.
ACPI-0432: *** Error: Handler for [EmbeddedControl returned AE_ERROR
ACPI-1287: *** Error: Method execution failed, AE_AML_NO_RETURN_VALUE
When I hit the sleep button on my computer I get:
acpi0: AcpiGetSleepTypeDate failed - AE_NOT_FOUND
This is the output of acpidump:
/*
RSD PTR: Checksum=80, OEMID=PTLTD, RsdtAddress=0x0fef9a51
*/
/*
RSDT: Length=48, Revision=1, Checksum=247,
OEMID=SONY, OEM Table ID=K5, OEM Revision=0x604,
Creator ID= LTP, Creator Revision=0x0
*/
/*
Entries={ 0x0fefee4c, 0x0fefeec0, 0x0fefeee8 }
*/
/*
DSDT=0xfef9a81
INT_MODEL=PIC
SCI_INT=9
SMI_CMD=0x802f, ACPI_ENABLE=0xf0, ACPI_DISABLE=0xf1, S4BIOS_REQ=0xf2
PM1a_EVT_BLK=0x8000-0x8003
PM1a_CNT_BLK=0x8004-0x8005
PM2_TMR_BLK=0x8008-0x800b
PM2_GPE0_BLK=0x8020-0x8023
P_LVL2_LAT=90ms, P_LVL3_LAT=1100ms
FLUSH_SIZE=0, FLUSH_STRIDE=0
DUTY_OFFSET=0, DUTY_WIDTH=4
DAY_ALRM=125, MON_ALRM=126, CENTURY=50
Flags={WBINVD,PROC_C1,SLP_BUTTON,RTC_S4,TMR_VAL_EXT}
*/
acpidump: DSDT is corrupt
This is the dmesg:
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #3: Sun Dec 22 21:10:40 GMT 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/VAIO
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0499000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04990a8.
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 143490 Hz
CPU: AMD Athlon(tm) Processor (1000.04-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x662 Stepping = 2
Features=0x383f9ff
AMD Features=0xc048
real memory = 268435456 (256 MB)
avail memory = 255709184 (243 MB)
Initializing GEOMetry subsystem
Pentium Pro MTRR support enabled
npx0: on motherboard
npx0: INT 16 interface
acpi0: on motherboard
ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15
Using $PIR table, 6 entries at 0xc00fdf60
acpi0: power button is handled as a fixed feature programming model.
Timecounter "ACPI-safe" frequency 3579545 Hz
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0
acpi_cpu0: on acpi0
acpi_tz0: on acpi0
acpi_button0: on acpi0
pcib0: port 0xcf8-0xcff on acpi0
pci0: on pcib0
agp0: mem
0xf000-0xf7ff at device 0.0 on pci0
pcib1: at device 1.0 on pci0
pci1: on pcib1
pci1: at device 0.0 (no driver attached)
isab0: at device 7.0 on pci0
isa0: on isab0
atapci0: port 0x1c40-0x1c4f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: port 0x1c00-0x1c1f irq 9 at device 7.2 on
pci0
usb0: on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: port 0x1c20-0x1c3f irq 9 at device 7.3 on
pci0
usb1: on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
isab1: at device 7.4 on pci0
pcm0: port 0x1c50-0x1c53,0x1c54-0x1c57,0x1000-0x10ff irq 5
at device 7.5 on pci0
pci0: at device 7.6 (no driver attached)
cbb0: mem 0x8800-0x88000fff irq 9 at device
10.0 on pci0
cardbus0: on cbb0
pccard0: <16-bit PCCard bus> on cbb0
cbb1: mem 0x88001000-0x88001fff irq 10 at device
10.1 on pci0
cardbus1: on cbb1
pccard1: <16-bit PCCard bus> on cbb1
pci0: at device 14.0 (no driver attached)
rl0: port 0x1800-0x18ff mem
0xe8004800-0xe80048ff irq 10 at device 16.0 on pci0
rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect
mode
rl0: Ethernet address: 08:00:46:1d:19:89
miibus0: on rl0
rlphy0: on miibus0
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
acpi_acad0: on acpi0
acpi_cmbat0: on acpi0
acpi_cmbat1: on acpi0
acpi_lid0: on acpi0
fdc0: 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-0x77f,0x378-0x37f irq 7 drq 3 on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
ppi0: on ppbus0
atkbdc0: port 0x64,0x60 irq 1 on acpi0
atkbd0: flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: irq 12 on atkbdc0
psm0: model GlidePoint, device ID 0
acpi_ec0: port 0x66,0x62 on acpi0
orm0: at iomem 0xdc000-0xd,0xd-0xd3fff,0xc-0xc
on isa0
pmtimer0 on isa0
sc0: at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of pr
Re: no single user mode in installworld
From: "Gernot A. Weber" <[EMAIL PROTECTED]> Sent: Monday, December 23, 2002 3:58 PM > Hi, > > I forgot to drop into single user mode before doing make installworld. The > process finished without any obvious errors. I do this all the time when upgrading remotely. The primary issue with rebooting single-user is to prevent old versions of the userland binaries from trying to run against a new kernel. (Especially eg. ipfw, which changes all the time). But if you managed to get the installworld to run to completion and rebooted, you're probably fine. I'd read UPDATING to make sure there are no specific issues you might have to check on, and check to make sure all your normal daemons are active and nothing odd's showing in your logs. --K To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAWS ack-on-ack loop avoided
:Hello -current, : :I'm seeing a bit (12 or more per day) of :"PAWS ack-on-ack loop avoided" in my /var/log/messages : :Which appears to just be triggered by a mechanism to drop :bad packets. Is this correct? Is this something I should be :concerned about? : :Thanks in advance, : :./muk : :-- :m. kolb <[EMAIL PROTECTED]> No, you don't need to be concerned, it's just debugging what we thought was a rare bug case (but apparently is not) that was recently fixed. The printf is only going to be in -current another couple of days. -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no single user mode in installworld
On Mon, Dec 23, 2002 at 09:58:59PM +0100, Gernot A. Weber wrote: > I forgot to drop into single user mode before doing make installworld. The > process finished without any obvious errors. Should I do it again in > single user mode or is it safe and enough to reboot the computer after > compiling the new kernel? No. > It is no machine with hundreds of users. During > installation I was the only person logged in... Best way is doing installworld after reboot in single-mode with new kernel. All other ways is not correct, but sometimes they works. And don't remember run mergemaster :-) -- 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: Sysinstall project?
In message <[EMAIL PROTECTED]>, "Brian J. McGov ern" writes: >I was just going through the list of projects at the FreeBSD website. I >didn't see one for the installer. I was curious if anyone was working on >an upgrade/replacement for sysinstall... I know of Jordan's paper on the >subject, et al, but curious if anyone was doing anything more than maintaining >our existing sysinstall. > -B The word to look for is "libh". PS: I'm not sure what "libh" means, I can't figure out how it can possibly be an acronym for "the big white whale"... :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
no single user mode in installworld
Hi, I forgot to drop into single user mode before doing make installworld. The process finished without any obvious errors. Should I do it again in single user mode or is it safe and enough to reboot the computer after compiling the new kernel? It is no machine with hundreds of users. During installation I was the only person logged in... Thanks, Gernot -- Gernot A. Weber http://www.tux-web.de [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sysinstall project?
On Mon, Dec 23, 2002 at 03:39:05PM -0500, Brian J. McGovern wrote: > I was just going through the list of projects at the FreeBSD website. I > didn't see one for the installer. I was curious if anyone was working on > an upgrade/replacement for sysinstall... I know of Jordan's paper on the > subject, et al, but curious if anyone was doing anything more than maintaining > our existing sysinstall. > -B > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > Hi, what you're looking for is the libh project (http://www.freebsd.org/projects/libh.html). There also exists are mailing list ([EMAIL PROTECTED]). - Christian -- http://www.unixpages.org[EMAIL PROTECTED] GPG Pub-Key: www.unixpages.org/cbrueffer.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D GPG Key ID : 0xA0ED982D msg49254/pgp0.pgp Description: PGP signature
Sysinstall project?
I was just going through the list of projects at the FreeBSD website. I didn't see one for the installer. I was curious if anyone was working on an upgrade/replacement for sysinstall... I know of Jordan's paper on the subject, et al, but curious if anyone was doing anything more than maintaining our existing sysinstall. -B To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: SIS 962 chipset, problems ...
> Hi, > > > > Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff > > > Dec 23 15:17:03 kernel: sis0: MII without any PHY! > > > Dec 23 15:17:03 kernel: device_probe_and_attach: sis0 attach > returned 6 > > > Dec 23 15:17:03 kernel: sis0: port > 0x2000-0x20ff mem > > > 0xec005000-0xec005fff irq 11 at device 4.0 on pci0 > > > Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff > > > Dec 23 15:17:03 kernel: sis0: MII without any PHY! > > The linux driver tells me : > > /** > * sis96x_get_mac_addr: - Get MAC address for SiS962 or SiS963 model > * @pci_dev: the sis900 pci device > * @net_dev: the net device to get address for > * > * SiS962 or SiS963 model, use EEPROM to store MAC address. > And EEPROM > * is shared by > * LAN and 1394. When access EEPROM, send EEREQ signal to > hardware first > * and wait for EEGNT. If EEGNT is ON, EEPROM is permitted > to be access > * by LAN, otherwise is not. After MAC address is read from > EEPROM, send > * EEDONE signal to refuse EEPROM access by LAN. > * The EEPROM map of SiS962 or SiS963 is different to SiS900. > * The signature field in SiS962 or SiS963 spec is meaningless. > * MAC address is read into @net_dev->dev_addr. > */ > > So we definitly are missing the support for the SiS 962/963 southbridge. > > Martin > This is just one part of the problem. The other half is PHY couldn't be detected. It seems that sis no longer implementes the enhanced phy control register, and phy has to be directly accessed via mdio. I have a patch (-stable only) for this problem, http://www.freebsd.org/~luoqi/sis.diff . I've also notice some other quirks of the chip our driver should be dealing with. Among them, the multicast address filter and DMA burst size. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAWS ack-on-ack loop avoided
:I've got this on my development box which doesn't run any services. :I don't remember exactly what I've been doing when these appeared; :probably printing some connection data like IPs and ports from TCB :would help. : : :Cheers, :--=20 :Ruslan Ermilov Sysadmin and DBA, :[EMAIL PROTECTED] Sunbay Software AG, That's very odd. I see them on my development box too which is just talking FreeBSD<->FreeBSD. We should not be seeing them at all. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic: lockmgr: draining against myself
Got another panic with a Sat Dec 21 11:00 PST 2002 kernel:
GNU gdb 5.2.1 (FreeBSD)
This GDB was configured as "i386-undermydesk-freebsd"...
(kgdb) core-file /var/crash/vmcore.1
panic: lockmgr: draining against myself
panic messages:
---
panic: lockmgr: draining against myself
cpuid = 1; lapic.id =
boot() called on cpu#1
Uptime: 4h48m6s
pfs_vncache_unload(): 1 entries remaining
Dumping 1535 MB
ata0: resetting devices ..
done
---
#0 doadump () at ../../../kern/kern_shutdown.c:232
232 dumping++;
(kgdb) where
#0 doadump () at ../../../kern/kern_shutdown.c:232
#1 0xc01eac9e in boot (howto=260) at ../../../kern/kern_shutdown.c:364
#2 0xc01eaf39 in panic () at ../../../kern/kern_shutdown.c:517
#3 0xc01de8b9 in lockmgr (lkp=0xc9f9c7cc, flags=65543, interlkp=0x140,
td=0xc7835620) at ../../../kern/kern_lock.c:441
#4 0xc0231fec in vop_stdlock (ap=0x0) at ../../../kern/vfs_default.c:279
#5 0xc02db0c8 in ufs_vnoperate (ap=0x0) at ../../../ufs/ufs/ufs_vnops.c:2796
#6 0xc023b9a3 in vclean (vp=0xc9f9c708, flags=8, td=0xc7835620) at vnode_if.h:990
#7 0xc023bf1c in vgonel (vp=0xc9f9c708, td=0x0) at ../../../kern/vfs_subr.c:2692
#8 0xc023be3b in vrecycle (vp=0xc9f9c708, inter_lkp=0x0, td=0x0) at
../../../kern/vfs_subr.c:2647
#9 0xc02d35f1 in ufs_inactive (ap=0x0) at ../../../ufs/ufs/ufs_inode.c:133
#10 0xc02db0c8 in ufs_vnoperate (ap=0x0) at ../../../ufs/ufs/ufs_vnops.c:2796
#11 0xc023b200 in vput (vp=0xc9f9c708) at vnode_if.h:930
#12 0xc02c4a4d in handle_workitem_freeblocks (freeblks=0xc9ef2200, flags=0) at
../../../ufs/ffs/ffs_softdep.c:2498
#13 0xc02c3f9a in softdep_setup_freeblocks (ip=0xc9ef7b00, length=0, flags=2048) at
../../../ufs/ffs/ffs_softdep.c:2081
#14 0xc02b9da5 in ffs_truncate (vp=0xc9f9c708, length=0, flags=3072, cred=0x0,
td=0xc7835620) at ../../../ufs/ffs/ffs_inode.c:271
#15 0xc02d34c1 in ufs_inactive (ap=0x0) at ../../../ufs/ufs/ufs_inode.c:100
#16 0xc02db0c8 in ufs_vnoperate (ap=0x0) at ../../../ufs/ufs/ufs_vnops.c:2796
#17 0xc023b200 in vput (vp=0xc9f9c708) at vnode_if.h:930
#18 0xc023ffcf in kern_unlink (td=0xc7835620, path=---Can't read userspace from dump,
or kernel process---
) at ../../../kern/vfs_syscalls.c:1281
#19 0xc023fe32 in unlink (td=0x0, uap=0x0) at ../../../kern/vfs_syscalls.c:1223
#20 0xc032b7c0 in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 1, tf_esi = 134930432, tf_ebp =
-1077938760, tf_isp = -336339596, tf_ebx = 134939136, tf_edx = 0, tf_ecx = 134939208,
tf_eax = 10, tf_trapno = 12, tf_err = 2, tf_eip = 134525687, tf_cs = 31, tf_eflags =
658, tf_esp = -1077938804, tf_ss = 47}) at ../../../i386/i386/trap.c:1033
#21 0xc031463d in Xint0x80_syscall () at {standard input}:141
---Can't read userspace from dump, or kernel process---
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PAWS ack-on-ack loop avoided
On Monday, December 23, 2002, at 12:23 PM, Matthew Dillon wrote: The printf() is only in HEAD for feedback purposes. I'd like to leave it in there just a little while longer (maybe a week at the rate things are going). It looks like more people are hitting this bug(fix) then we previously thought would hit it, which is actually somewhat worrying because it only occurs when you get out-of-order timestamp replies. Could you tell me what services were running or what you were doing when you got the warnings? Are you running a web server? Talking to windows boxes at all? My machines are running smtp, each machine doing about 3k messages per hour, so surely, some kind of windows machines are speaking to them. That's it service wise. My development/build box is not seeing any of these messages. ./muk -- m. kolb <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAWS ack-on-ack loop avoided
In the last episode (Dec 23), Matthew Dillon said: > The printf() is only in HEAD for feedback purposes. I'd like to > leave it in there just a little while longer (maybe a week at the > rate things are going). It looks like more people are hitting this > bug(fix) then we previously thought would hit it, which is actually > somewhat worrying because it only occurs when you get out-of-order > timestamp replies. > > Could you tell me what services were running or what you were doing > when you got the warnings? Are you running a web server? Talking to > windows boxes at all? I got 25 of these messages on the 17th, 12 on the 18th, and after that, 2-3 a day. Not sure why the count was so high the first 2 days. It's a squid proxy, plus bigbrother network agent. Lots of TCP connections from lots of hosts. Is there a way to maybe print the remote IP in the message? -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAWS ack-on-ack loop avoided
On Mon, Dec 23, 2002 at 09:23:30AM -0800, Matthew Dillon wrote: > The printf() is only in HEAD for feedback purposes. I'd like to leave > it in there just a little while longer (maybe a week at the rate things > are going). It looks like more people are hitting this bug(fix) then > we previously thought would hit it, which is actually somewhat worrying > because it only occurs when you get out-of-order timestamp replies. > > Could you tell me what services were running or what you were doing > when you got the warnings? Are you running a web server? Talking > to windows boxes at all? > I've got this on my development box which doesn't run any services. I don't remember exactly what I've been doing when these appeared; probably printing some connection data like IPs and ports from TCB would help. 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 msg49247/pgp0.pgp Description: PGP signature
Re: PAWS ack-on-ack loop avoided
The printf() is only in HEAD for feedback purposes. I'd like to leave it in there just a little while longer (maybe a week at the rate things are going). It looks like more people are hitting this bug(fix) then we previously thought would hit it, which is actually somewhat worrying because it only occurs when you get out-of-order timestamp replies. Could you tell me what services were running or what you were doing when you got the warnings? Are you running a web server? Talking to windows boxes at all? -Matt Matthew Dillon <[EMAIL PROTECTED]> :>=20 :> Which appears to just be triggered by a mechanism to drop :> bad packets. Is this correct? Is this something I should be :> concerned about? :>=20 :Matt, : :I'm seeing these too. Can you please remove the relevant :printf() or at least limit it to the ``if (verbose)'' or :DIAGNOSTIC, whatever is more appropriate? : : :Cheers, :--=20 :Ruslan Ermilov Sysadmin and DBA, :[EMAIL PROTECTED] Sunbay Software AG, To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SIS 962 chipset, problems ...
Hi Soeren, > This does not work correctly, your ATA timings are way out of wack > since botht ATA100 and ATA133 SiS chips uses different register > layouts... I know. This is just a workaround. At least my box does not hang during boot and ATA100 seems to work. No crash since then. Do you have a more correct fix for the ATA133 chipset in work, or already ready so I could test it ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UPDATING error
In message: <[EMAIL PROTECTED]> Andy Farkas <[EMAIL PROTECTED]> writes: : : $FreeBSD: src/UPDATING,v 1.228 2002/10/30 20:11:07 imp Exp $ : : "To upgrade from 4.x-stable to current" suggests: : : cd src/sys/boot ; make install [6] : : This does not work. You need to: : : cd src/sys/boot ; make all install [6] make all isn't needed here because it was already built as part of the buildworld. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic during daily periodic run
This is 100% identical to my panic. My system is a dual athlon/2G system too. In message <[EMAIL PROTECTED]>, "David O'Brien" writes: >--- >#0 doadump () at ../../../kern/kern_shutdown.c:232 >232dumping++; >(kgdb) bt >#0 doadump () at ../../../kern/kern_shutdown.c:232 >#1 0xc01eac9e in boot (howto=260) at ../../../kern/kern_shutdown.c:364 >#2 0xc01eaf39 in panic () at ../../../kern/kern_shutdown.c:517 >#3 0xc02e25ed in kmem_malloc (map=0xc082e07c, size=4096, flags=4) at >../../../vm/vm_kern.c:336 >#4 0xc02f25a7 in page_alloc (zone=0xc083a600, bytes=0, pflag=0x0, wait=0) at >../../../vm/uma_core.c:798 >#5 0xc02f230d in slab_zalloc (zone=0xc083a600, wait=4) at ../../../vm/uma_core.c:707 >#6 0xc02f33d3 in uma_zone_slab (zone=0xc083a600, flags=0) at >../../../vm/uma_core.c:1486 [...] -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAWS ack-on-ack loop avoided
On Mon, Dec 23, 2002 at 10:13:29AM -0500, Matthew Kolb wrote: > Hello -current, > > I'm seeing a bit (12 or more per day) of > "PAWS ack-on-ack loop avoided" in my /var/log/messages > > Which appears to just be triggered by a mechanism to drop > bad packets. Is this correct? Is this something I should be > concerned about? > Matt, I'm seeing these too. Can you please remove the relevant printf() or at least limit it to the ``if (verbose)'' or DIAGNOSTIC, whatever is more appropriate? 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 msg49242/pgp0.pgp Description: PGP signature
Panic during daily periodic run
I've gotten this two days in a row (but wasn't configured to get a core
dump the 1st day):
kernel.debug + vmcore + src tree available to trusted individuals.
Sources are from Sat Dec 21 11:00 PST 2002.
GNU gdb 5.2.1 (FreeBSD)
This GDB was configured as "i386-undermydesk-freebsd"...
(kgdb) core-file /var/crash/vmcore.0
panic: kmem_malloc(4096): kmem_map too small: 275378176 total allocated
panic messages:
---
panic: kmem_malloc(4096): kmem_map too small: 275378176 total allocated
cpuid = 0; lapic.id = 0100
boot() called on cpu#0
Uptime: 1d17h14m4s
Dumping 1535 MB
ata0: resetting devices ..
done
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368
384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704
720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008 1024 1040
1056 1072 1088 1104 1120 1136 1152 1168 1184 1200 1216 1232 1248 1264 1280 1296 1312
1328 1344 1360 1376 1392 1408 1424 1440 1456 1472 1488 1504 1520
---
#0 doadump () at ../../../kern/kern_shutdown.c:232
232 dumping++;
(kgdb) bt
#0 doadump () at ../../../kern/kern_shutdown.c:232
#1 0xc01eac9e in boot (howto=260) at ../../../kern/kern_shutdown.c:364
#2 0xc01eaf39 in panic () at ../../../kern/kern_shutdown.c:517
#3 0xc02e25ed in kmem_malloc (map=0xc082e07c, size=4096, flags=4) at
../../../vm/vm_kern.c:336
#4 0xc02f25a7 in page_alloc (zone=0xc083a600, bytes=0, pflag=0x0, wait=0) at
../../../vm/uma_core.c:798
#5 0xc02f230d in slab_zalloc (zone=0xc083a600, wait=4) at ../../../vm/uma_core.c:707
#6 0xc02f33d3 in uma_zone_slab (zone=0xc083a600, flags=0) at
../../../vm/uma_core.c:1486
#7 0xc02f3589 in uma_zalloc_bucket (zone=0xc083a600, flags=0) at
../../../vm/uma_core.c:1590
#8 0xc02f32cb in uma_zalloc_arg (zone=0xc083a600, udata=0x0, flags=0) at
../../../vm/uma_core.c:1417
#9 0xc02e8b78 in vm_object_allocate_wait (type=2 '\002', size=1, flags=0) at uma.h:229
#10 0xc02e8bd8 in vm_object_allocate (type=2 '\002', size=0) at
../../../vm/vm_object.c:360
#11 0xc02f4b84 in vnode_pager_alloc (handle=0x0, size=512, prot=0 '\0', offset=0) at
../../../vm/vnode_pager.c:155
#12 0xc02323ad in vop_stdcreatevobject (ap=0x0) at ../../../kern/vfs_default.c:578
#13 0xc0231ea8 in vop_defaultop (ap=0x0) at ../../../kern/vfs_default.c:161
#14 0xc02db0c8 in ufs_vnoperate (ap=0x0) at ../../../ufs/ufs/ufs_vnops.c:2796
#15 0xc023cf2a in vfs_object_create (vp=0xd34a8a8c, td=0x0, cred=0x0) at
vnode_if.h:1620
#16 0xc0233a26 in namei (ndp=0xebfd3bdc) at ../../../kern/vfs_lookup.c:207
#17 0xc0244f33 in vn_open_cred (ndp=0xebfd3bdc, flagp=0xebfd3cdc, cmode=2248,
cred=0xcfdf9900) at ../../../kern/vfs_vnops.c:190
#18 0xc0244ce9 in vn_open (ndp=0x0, flagp=0x0, cmode=0) at ../../../kern/vfs_vnops.c:91
#19 0xc023ea1d in kern_open (td=0xc769ba80, path=0x0, pathseg=UIO_USERSPACE, flags=5,
mode=-1077937464) at ../../../kern/vfs_syscalls.c:662
#20 0xc023e890 in open (td=0x0, uap=0x0) at ../../../kern/vfs_syscalls.c:625
#21 0xc032b7c0 in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134594816, tf_esi = 134558656,
tf_ebp = -1077937464, tf_isp = -335725196, tf_ebx = 672262700, tf_edx = 0, tf_ecx =
134594816, tf_eax = 5, tf_trapno = 0, tf_err = 2, tf_eip = 671824511, tf_cs = 31,
tf_eflags = 658, tf_esp = -1077937924, tf_ss = 47}) at ../../../i386/i386/trap.c:1033
#22 0xc031463d in Xint0x80_syscall () at {standard input}:141
---Can't read userspace from dump, or kernel process---
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SIS 962 chipset, problems ...
It seems Martin Blapp wrote: > --- sys/dev/ata/ata-dma.c.origMon Dec 23 14:44:39 2002 > +++ sys/dev/ata/ata-dma.c Mon Dec 23 15:49:20 2002 > @@ -632,7 +632,9 @@ > ata_find_dev(parent, 0x06351039, 0) || /* SiS 635 */ > ata_find_dev(parent, 0x06401039, 0) || /* SiS 640 */ > ata_find_dev(parent, 0x06451039, 0) || /* SiS 645 */ > + ata_find_dev(parent, 0x06461039, 0) || /* SiS 646 */ > ata_find_dev(parent, 0x06501039, 0) || /* SiS 650 */ > + ata_find_dev(parent, 0x06511039, 0) || /* SiS 651 */ > ata_find_dev(parent, 0x07301039, 0) || /* SiS 730 */ > ata_find_dev(parent, 0x07331039, 0) || /* SiS 733 */ > ata_find_dev(parent, 0x07351039, 0) || /* SiS 735 */ > --- sys/dev/ata/ata-pci.c.origMon Dec 23 16:40:04 2002 > +++ sys/dev/ata/ata-pci.c Mon Dec 23 16:39:27 2002 > @@ -188,7 +188,9 @@ > ata_find_dev(dev, 0x06351039, 0) || > ata_find_dev(dev, 0x06401039, 0) || > ata_find_dev(dev, 0x06451039, 0) || > + ata_find_dev(dev, 0x06461039, 0) || > ata_find_dev(dev, 0x06501039, 0) || > + ata_find_dev(dev, 0x06511039, 0) || > ata_find_dev(dev, 0x07301039, 0) || > ata_find_dev(dev, 0x07331039, 0) || > ata_find_dev(dev, 0x07351039, 0) || This does not work correctly, your ATA timings are way out of wack since botht ATA100 and ATA133 SiS chips uses different register layouts... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SIS 962 chipset, problems ...
Hi, > > Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff > > Dec 23 15:17:03 kernel: sis0: MII without any PHY! > > Dec 23 15:17:03 kernel: device_probe_and_attach: sis0 attach returned 6 > > Dec 23 15:17:03 kernel: sis0: port 0x2000-0x20ff mem > > 0xec005000-0xec005fff irq 11 at device 4.0 on pci0 > > Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff > > Dec 23 15:17:03 kernel: sis0: MII without any PHY! The linux driver tells me : /** * sis96x_get_mac_addr: - Get MAC address for SiS962 or SiS963 model * @pci_dev: the sis900 pci device * @net_dev: the net device to get address for * * SiS962 or SiS963 model, use EEPROM to store MAC address. And EEPROM * is shared by * LAN and 1394. When access EEPROM, send EEREQ signal to hardware first * and wait for EEGNT. If EEGNT is ON, EEPROM is permitted to be access * by LAN, otherwise is not. After MAC address is read from EEPROM, send * EEDONE signal to refuse EEPROM access by LAN. * The EEPROM map of SiS962 or SiS963 is different to SiS900. * The signature field in SiS962 or SiS963 spec is meaningless. * MAC address is read into @net_dev->dev_addr. */ So we definitly are missing the support for the SiS 962/963 southbridge. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SIS 962 chipset, problems ...
On Mon, Dec 23, 2002 at 04:22:22PM +0100, Martin Blapp wrote the words in effect of: > > Hi all, > > I'm trying to get my laptop running, with some success, but the > network card is not very friendly to me. > > none3@pci0:4:0: class=0x02 card=0x105517c0 chip=0x09001039 rev=0x91 hdr=0x00 > vendor = 'Silicon Integrated Systems (SiS)' > device = 'SiS900 Fast Ethernet/Home Networking Ctrlr' > class= network > subclass = ethernet > > Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff > Dec 23 15:17:03 kernel: sis0: MII without any PHY! > Dec 23 15:17:03 kernel: device_probe_and_attach: sis0 attach returned 6 > Dec 23 15:17:03 kernel: sis0: port 0x2000-0x20ff mem > 0xec005000-0xec005fff irq 11 at device 4.0 on pci0 > Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff > Dec 23 15:17:03 kernel: sis0: MII without any PHY! > > I thought first that this is a similar problem to the one where > the physical is at id 1, not 0. But it still doesn't work. IIRC, this is the same problem, that was posted on -hackers -- something to do with the Card not reading the MAC address from the EEPROM. I may be wrong. -- Hiten Pandya ([EMAIL PROTECTED], [EMAIL PROTECTED]) http://www.unixdaemons.com/~hiten/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SIS 962 chipset, problems ...
Hi all,
I'm trying to get my laptop running, with some success, but the
network card is not very friendly to me.
none3@pci0:4:0: class=0x02 card=0x105517c0 chip=0x09001039 rev=0x91 hdr=0x00
vendor = 'Silicon Integrated Systems (SiS)'
device = 'SiS900 Fast Ethernet/Home Networking Ctrlr'
class= network
subclass = ethernet
Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff
Dec 23 15:17:03 kernel: sis0: MII without any PHY!
Dec 23 15:17:03 kernel: device_probe_and_attach: sis0 attach returned 6
Dec 23 15:17:03 kernel: sis0: port 0x2000-0x20ff mem
0xec005000-0xec005fff irq 11 at device 4.0 on pci0
Dec 23 15:17:03 kernel: sis0: Ethernet address: ff:ff:ff:ff:ff:ff
Dec 23 15:17:03 kernel: sis0: MII without any PHY!
I thought first that this is a similar problem to the one where
the physical is at id 1, not 0. But it still doesn't work.
http://www.freebsd.org/cgi/query-pr.cgi?pr=30836
Then I tried another tip from google:
http://www.geocrawler.com/archives/3/152/2002/6/0/9065467/
No way ... I'll try some other tricks now ...
Other things I got running, like the ATA UDMA support. It seems
that many new chipsets are unsupported in FreeBSD ...
--- sys/pci/agp_sis.c.orig Mon Dec 23 14:34:30 2002
+++ sys/pci/agp_sis.c Mon Dec 23 14:34:32 2002
@@ -66,6 +66,8 @@
switch (pci_get_devid(dev)) {
case 0x00011039:
return ("SiS 5591 host to AGP bridge");
+ case 0x06461039:
+ return ("SiS 645DX host to AGP bridge");
};
if (pci_get_vendor(dev) == 0x1039)
--- sys/dev/ata/ata-dma.c.orig Mon Dec 23 14:44:39 2002
+++ sys/dev/ata/ata-dma.c Mon Dec 23 15:49:20 2002
@@ -632,7 +632,9 @@
ata_find_dev(parent, 0x06351039, 0) || /* SiS 635 */
ata_find_dev(parent, 0x06401039, 0) || /* SiS 640 */
ata_find_dev(parent, 0x06451039, 0) || /* SiS 645 */
+ ata_find_dev(parent, 0x06461039, 0) || /* SiS 646 */
ata_find_dev(parent, 0x06501039, 0) || /* SiS 650 */
+ ata_find_dev(parent, 0x06511039, 0) || /* SiS 651 */
ata_find_dev(parent, 0x07301039, 0) || /* SiS 730 */
ata_find_dev(parent, 0x07331039, 0) || /* SiS 733 */
ata_find_dev(parent, 0x07351039, 0) || /* SiS 735 */
--- sys/dev/ata/ata-pci.c.orig Mon Dec 23 16:40:04 2002
+++ sys/dev/ata/ata-pci.c Mon Dec 23 16:39:27 2002
@@ -188,7 +188,9 @@
ata_find_dev(dev, 0x06351039, 0) ||
ata_find_dev(dev, 0x06401039, 0) ||
ata_find_dev(dev, 0x06451039, 0) ||
+ ata_find_dev(dev, 0x06461039, 0) ||
ata_find_dev(dev, 0x06501039, 0) ||
+ ata_find_dev(dev, 0x06511039, 0) ||
ata_find_dev(dev, 0x07301039, 0) ||
ata_find_dev(dev, 0x07331039, 0) ||
ata_find_dev(dev, 0x07351039, 0) ||
Martin
Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 061 826 93 00: +41 61 826 93 01
PGP:
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
PAWS ack-on-ack loop avoided
Hello -current, I'm seeing a bit (12 or more per day) of "PAWS ack-on-ack loop avoided" in my /var/log/messages Which appears to just be triggered by a mechanism to drop bad packets. Is this correct? Is this something I should be concerned about? Thanks in advance, ./muk -- m. kolb <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem upgrading to -current
On Mon, Dec 23, 2002 at 03:12:50PM +0200, Giorgos Keramidas wrote: > On 2002-12-22 17:19, walt <[EMAIL PROTECTED]> wrote: > >Martin Hasenbein wrote: > >> I've tried to upgrade to -current a few minutes ago. Before > >> upgrading I had FreeBSD 4.7-RELEASE-p2 > >> > >> After a "make buildworld / make buildkernel /make installkernel" > >> and rebooting, I still have FreeBSD 4.7-RELEASE-p2 > > > > Sounds like you are rebooting with the old kernel in the / directory > > instead of the new kernel which is now in the /boot/kernel > > directory. > > > > If you interrupt the boot loader by hitting SPACE, you can then type > > 'unload' and then 'load /boot/kernel/kernel' then 'boot' which will > > boot the new kernel. > > > > I've never done the upgrade path, so I'm not sure how you are > > supposed to avoid this problem. Maybe you are doing things in the > > wrong sequence or skipping steps? > > By editing /boot/loader.conf before rebooting and changing `bootfile' > to the new location of the kernel: > > bootfile="/boot/kernel/kernel" > > you can instruct the loader to load the new kernel by default. > Perhaps we should add this to the instructions of UPDATING for > upgrades of 4.X to 5.X :-/ This change is mentioned in UPDATING, see entry 2905. The instructions in UPDATING are a kind of an ad-hoc upgrade guide, but not a complete one. Read it from oldest entry to the newest, apply some common sense and you will do fine. -- All opinions expressed above are mine alone and do not express the views of my employer or any other organizations that I am affiliated with. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic when mounting w2k ntfs partition on -CURRENT of Dec20
The system panics when I mount my Windows 2000 NTFS partition. It is easily repeatable on -RC1 and -CURRENT as of December 20. Hardware is AMD Duron, KT133, Fujitsu IDE UDMA 66 HDD, with ACPI enabled. Short backtrace: db> tr Debugger() panic(c04474ce, c76e96f8, 2 c76e96f8, d6186488) bundirty(c79e96f8) brelse(c79c96f8, c0463ca0, c2807834, c76c96f8) bwrite(c79c96f8) getblk(c28ffe10, 2681ed, 0, 400, 0) breadn(c28ffe10, 2681ed, 0, 400, 0) ntfs_readntvattr_plain(c286f800, c2732e00, c2a18000, 1e0, 0) ntfs_readattr_plain(c286f800, 80, 0, 1e0) ntfs_mountfs(c28ffe10, c28c5800, d61808e8, c268c540, c28c5915) ntfs_mount vfs_mount syscall Xint0x80_syscall syscall(21, FreeBSD ELF32, mount) I can supply more information, should it be necessary. -- Saulius Menkevicius, [EMAIL PROTECTED] on 12.23.2002 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem upgrading to -current
On 2002-12-22 17:19, walt <[EMAIL PROTECTED]> wrote: >Martin Hasenbein wrote: >> I've tried to upgrade to -current a few minutes ago. Before >> upgrading I had FreeBSD 4.7-RELEASE-p2 >> >> After a "make buildworld / make buildkernel /make installkernel" >> and rebooting, I still have FreeBSD 4.7-RELEASE-p2 > > Sounds like you are rebooting with the old kernel in the / directory > instead of the new kernel which is now in the /boot/kernel > directory. > > If you interrupt the boot loader by hitting SPACE, you can then type > 'unload' and then 'load /boot/kernel/kernel' then 'boot' which will > boot the new kernel. > > I've never done the upgrade path, so I'm not sure how you are > supposed to avoid this problem. Maybe you are doing things in the > wrong sequence or skipping steps? By editing /boot/loader.conf before rebooting and changing `bootfile' to the new location of the kernel: bootfile="/boot/kernel/kernel" you can instruct the loader to load the new kernel by default. Perhaps we should add this to the instructions of UPDATING for upgrades of 4.X to 5.X :-/ - Giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: errors in buildworld
On (23/12/02 11:55), Gernot A. Weber wrote: > Building an up-to-date make(1) > > But it is compiling anyway. Are these errors anything I have to worry > about? Or should it be no problem to do a 'make installworld' after > compilation has finished? Yes it is, the checks at the beginning only check if your make is suitable to build world. If not it updates make and then compiles with the updated one. - Christopher To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
errors in buildworld
Hi, just tried to upgrade to RC2. But when I start 'make buildworld', I get the following output: bash-2.05b# make -j4 buildworld Running test variables PASS: Test variables detected no regression, output matches. Running test targets "Makefile", line 53: warning: duplicate script for target "double" ignored PASS: Test targets detected no regression. Running test sysvmatch PASS: Test sysvmatch detected no regression. Running test lhs_expn Variable BAR is recursive. PASS: Test lhs_expn detected no regression. Running test notdef PASS: Test notdef detected no regression. Running test modifiers PASS: Test modifiers detected no regression. Running test funny_targets make: don't know how to make colons::target. Stop FAIL: Test failed: regression detected. See above. *** Error code 1 1 error *** Error code 2 -- Building an up-to-date make(1) But it is compiling anyway. Are these errors anything I have to worry about? Or should it be no problem to do a 'make installworld' after compilation has finished? Thanks, Gernot P.S. I changed /etc/make.conf to NOPROFILE=true like it was recommended in the handbook... -- Gernot A. Weber http://www.tux-web.de [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 4.2.1 doesn't work with last CURRENT
Aurelien Nephtali wrote: On Mon, Dec 23, 2002 at 12:18:45AM +0100, Jens Rehsack wrote: Aurelien Nephtali wrote: Hi, I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/ I've attached the error log. Any help would be appreciated :) -- Aurelien 1) How did you upgrade? 2) What's the name of your machine? I've upgraded using 'portupgrade' tool and my box is a Celeron 700 running on -CURRENT. -- Aurelien portupgrade and what kind of parameters? Send me please following outputs: 'pkg_info' 'dmesg' 'ifconfig -a' 'cat /etc/make.conf' 'cat /etc/rc.conf' I don't care if you're using a i486SX-33 or a Athlon-MP 2.2+ GHz Dual Box, the relevant information is the name of your machine. Please send me the output of previously requested commands. Jens -- L i W W W i Jens Rehsack LW W W L i W W W W i nnnLiWing IT-Services L iW W W Wi n n g g i W W i n n g gFriesenstraße 2 06112 Halle g g g Tel.: +49 - 3 45 - 5 17 05 91ggg e-Mail: <[EMAIL PROTECTED]> Fax: +49 - 3 45 - 5 17 05 92http://www.liwing.de/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 4.2.1 doesn't work with last CURRENT
> On Mon, 23 Dec 2002 10:11:29 +0100, Aurelien Nephtali ><[EMAIL PROTECTED]> said: >> >I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/ >> >I've attached the error log. >> > >> 1) How did you upgrade? >> 2) What's the name of your machine? >> Aurelien> I've upgraded using 'portupgrade' tool and my box is a Celeron 700 running on Aurelien> -CURRENT. Hi, Do a 'portupgrade -f wrapper' and try starting X. HTH Regards Sid -- Do what comes naturally now. Seethe and fume and throw a tantrum. Sid Carter - http://khader.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 4.2.1 doesn't work with last CURRENT
On Mon, Dec 23, 2002 at 12:18:45AM +0100, Jens Rehsack wrote: > Aurelien Nephtali wrote: > >Hi, > > > >I've upgraded from 4.2.0 to 4.2.1 and now X11 doesn't want to start :/ > >I've attached the error log. > > > >Any help would be appreciated :) > > > >-- Aurelien > > 1) How did you upgrade? > 2) What's the name of your machine? > I've upgraded using 'portupgrade' tool and my box is a Celeron 700 running on -CURRENT. -- Aurelien msg49228/pgp0.pgp Description: PGP signature
