Re: asr can not map memory?
Michael Smith wrote: > > What's the basis of the assumption that the I/O range is > > unsupported in the first place, and why isn't it true for this > > bridge chip, if it's a valid assumption for others? > > The information was provided in the debugging output and code that Alfred > supplied in earlier messages. The short answer is "programmer error". > > You're walking into another conversation with insufficient context. 8) Hey, I'll always sit still for someone willing to give me context... 8-). I was thinking it would be easier to get enough info to Alfred, and let the patch pop out there. 8-) 8-). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stdout changes break some ports
Kris Kennaway wrote: > How does one fix this in a library? I've been moving the > initialization to main() for applications. Use assembly glue to put it in a linker set that gets pulled in by the .init code. This will only work for user space code, since it depends in the crt0 treating it like a C++ binary (linker sets are a C++ feature which FreeBSD uses all over anyway). I'm not totally convinced this is really the way to fix this, since I'm not totally convinced that this isn't an introduced problem, rather than a real problem (e.g. perhaps the stdio changes were not completely and totally well thought out, if how to handle this problem wasn't part of the changes). If it's now a requirement, it's very tempting to put the code in the entry code, before it even calls "main" (e.g. in crt0 proper, rather than in a linker set crt0 knows about). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: asr can not map memory?
> What's the basis of the assumption that the I/O range is > unsupported in the first place, and why isn't it true for this > bridge chip, if it's a valid assumption for others? The information was provided in the debugging output and code that Alfred supplied in earlier messages. The short answer is "programmer error". You're walking into another conversation with insufficient context. 8) -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: asr can not map memory?
Michael Smith wrote: > > wtf is going on here? > > Your BIOS is assigning a memory range to the card that we don't believe > the bridge passes through. Our check is bogus because (as you see) the > range is actually legitimate (and we booger up some calculations). Add > the PCI_ALLOW_UNSUPPORTED_IO_RANGE option and this should go away. > > You should have bought a 3ware controller. 8) Apparently, that belief is in error, whenit comes to this bridge, if adding PCI_ALLOW_UNSUPPORTED_IO_RANGE works. What's the basis of the assumption that the I/O range is unsupported in the first place, and why isn't it true for this bridge chip, if it's a valid assumption for others? Give Alfred enough information, and a patch is bound to pop out... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldxref problem
Doug White wrote: > On Sat, 30 Mar 2002, A.Z. wrote: > > ***Error code 1(ignored) > Did you miss this part? > > Man, this throws everyone off. > > The error was IGNORED. THERE IS NO PROBLEM. Perhaps if the kernel printf also "ignored" the request to print the little S.O.B. out, there would be less confusion... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: asr can not map memory?
* Michael Smith <[EMAIL PROTECTED]> [020330 22:25] wrote: > > Is there a way that we can "fix" this without blindly allowing bad > > bus_alloc_resources ? I'm a bit confused as to wheather our code is > > behaving oddly or if it's just the device violating some spec... > > Yes, our code is busted; it should check both ranges and get the > arithmetic right. I believe that Warner did something about this in > -current, but I'm not sure what or if it's backportable. dude... duude... DUDE! FreeBSD big.endian.org 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Sat Mar 30 13:52:36 PST 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/smpng2 i386 (as of a couple of hours ago) heh. If you have time and enough pity I'll take as much time as it takes to get you the info to fix this. > > > You should have bought a 3ware controller. 8) > > > > 3ware should talk to Frys. :) > > 3ware don't feel like the bend-over-and-you-pay-for-the-crisco treatment, > I guess. Yeah, they were a pretty nifty bunch of people when I saw them at BAFUG. Anyhow, once the raid finishes building (in the background no less!) I'll give it a whirl for perf testing, see how it stands, if the driver continues to suck or perf does it's going to get one of Fry's famous stickers. :) -- -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.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stdout changes break some ports
On Sun, Mar 24, 2002 at 05:54:36PM -0800, Kris Kennaway wrote: > On Sun, Mar 24, 2002 at 06:43:13PM -0700, M. Warner Losh wrote: > > > : David O'Brien committed a workaround to the clog port yesterday to > > : move the initializer to main() instead of trying to do it statically. > > : > > : Is this something which is supposed to work? > > > > No. This isn't something that is guaranteed to work per the > > standards, iirc. The proper fix is to put the initializer in main. > > OK. Someone needs to go and fix those 84 ports then. How does one fix this in a library? I've been moving the initialization to main() for applications. Kris msg36818/pgp0.pgp Description: PGP signature
Re: asr can not map memory?
> > This avoids a panic when probing, there's probably still some > badness going on with make/destroy dev in this driver. Pending commentary from Scott, I think you should commit this. > Should I hold onto this card or should I suck it up and get > a 3ware online somewhere? By all means use it; as far as I can tell it should be a trooper. I'm just rather more fond of the 3ware adapters. 8) -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: asr can not map memory?
> Is there a way that we can "fix" this without blindly allowing bad > bus_alloc_resources ? I'm a bit confused as to wheather our code is > behaving oddly or if it's just the device violating some spec... Yes, our code is busted; it should check both ranges and get the arithmetic right. I believe that Warner did something about this in -current, but I'm not sure what or if it's backportable. > > You should have bought a 3ware controller. 8) > > 3ware should talk to Frys. :) 3ware don't feel like the bend-over-and-you-pay-for-the-crisco treatment, I guess. -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: asr can not map memory?
* Alfred Perlstein <[EMAIL PROTECTED]> [020330 21:51] wrote: > * Michael Smith <[EMAIL PROTECTED]> [020330 21:34] wrote: > > > > Your BIOS is assigning a memory range to the card that we don't believe > > the bridge passes through. Our check is bogus because (as you see) the > > range is actually legitimate (and we booger up some calculations). Add > > the PCI_ALLOW_UNSUPPORTED_IO_RANGE option and this should go away. > > I was about to do that (add PCI_ALLOW_UNSUPPORTED_IO_RANGE) I'll toss > a patch to make this a tunable/sysctl in a bit. > > Is there a way that we can "fix" this without blindly allowing bad > bus_alloc_resources ? I'm a bit confused as to wheather our code is > behaving oddly or if it's just the device violating some spec... > > > You should have bought a 3ware controller. 8) > > 3ware should talk to Frys. :) > > Thanks for responding so promptly. This avoids a panic when probing, there's probably still some badness going on with make/destroy dev in this driver. Should I hold onto this card or should I suck it up and get a 3ware online somewhere? Index: asr.c === RCS file: /home/ncvs/src/sys/dev/asr/asr.c,v retrieving revision 1.18 diff -u -r1.18 asr.c --- asr.c 20 Mar 2002 02:02:35 - 1.18 +++ asr.c 30 Mar 2002 22:15:01 - @@ -3179,7 +3192,6 @@ * Generate the device node information */ (void)make_dev(&asr_cdevsw, unit, 0, 0, S_IRWXU, "rasr%d", unit); -destroy_dev(makedev(asr_cdevsw.d_maj,unit+1)); ATTACH_RETURN(0); } /* asr_attach */ -- -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.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: asr can not map memory?
* Michael Smith <[EMAIL PROTECTED]> [020330 21:34] wrote: > > I just got the Adaptec 4 port IDE raid card 2400A. > > > > It doesn't probe right: > > asr0: could not map memory > > > > I added some debug printouts to the asr driver and pci code. > > > > asr0: mem 0xf600-0xf7ff irq 5 at device 5 > > .1 on pci2 > > pcib2: device asr0 requested unsupported memory range 0xf600-0xf640 > > pcib2: device asr0 requested unsupported memory range 0x0-0xec9f (decodin > > g 0xec90-0xec9f, 0xf600-0xfbff) > > asr: map failed at: 2602 p:f600 f640 l:0040 > > asr0: could not map memory > > device_probe_and_attach: asr0 attach returned 6 > > > > wtf is going on here? > > Your BIOS is assigning a memory range to the card that we don't believe > the bridge passes through. Our check is bogus because (as you see) the > range is actually legitimate (and we booger up some calculations). Add > the PCI_ALLOW_UNSUPPORTED_IO_RANGE option and this should go away. I was about to do that (add PCI_ALLOW_UNSUPPORTED_IO_RANGE) I'll toss a patch to make this a tunable/sysctl in a bit. Is there a way that we can "fix" this without blindly allowing bad bus_alloc_resources ? I'm a bit confused as to wheather our code is behaving oddly or if it's just the device violating some spec... > You should have bought a 3ware controller. 8) 3ware should talk to Frys. :) Thanks for responding so promptly. -- -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.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kldxref problem
On Sat, 30 Mar 2002, Doug White wrote: > On Sat, 30 Mar 2002, A.Z. wrote: > > I am upgrading 4.5 to -current. > > > > buildworld went fine, > > make buildkernel also fine, > > but make installkernel is giving me an error > > > > kldxref/boot/kernel > > kldxref: No Such Fule or Directory > > > > ***Error code 1(ignored) > Did you miss this part? > > Man, this throws everyone off. > > The error was IGNORED. THERE IS NO PROBLEM. I'm telling you all, its very easy to miss that "(ignored)" Either work around this or suffer through posts about it every single week... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: asr can not map memory?
> I just got the Adaptec 4 port IDE raid card 2400A. > > It doesn't probe right: > asr0: could not map memory > > I added some debug printouts to the asr driver and pci code. > > asr0: mem 0xf600-0xf7ff irq 5 at device 5 > .1 on pci2 > pcib2: device asr0 requested unsupported memory range 0xf600-0xf640 > pcib2: device asr0 requested unsupported memory range 0x0-0xec9f (decodin > g 0xec90-0xec9f, 0xf600-0xfbff) > asr: map failed at: 2602 p:f600 f640 l:0040 > asr0: could not map memory > device_probe_and_attach: asr0 attach returned 6 > > wtf is going on here? Your BIOS is assigning a memory range to the card that we don't believe the bridge passes through. Our check is bogus because (as you see) the range is actually legitimate (and we booger up some calculations). Add the PCI_ALLOW_UNSUPPORTED_IO_RANGE option and this should go away. You should have bought a 3ware controller. 8) -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: asr can not map memory?
* Alfred Perlstein <[EMAIL PROTECTED]> [020330 20:47] wrote: > I just got the Adaptec 4 port IDE raid card 2400A. > > It doesn't probe right: > asr0: could not map memory > > I added some debug printouts to the asr driver and pci code. > > asr0: mem 0xf600-0xf7ff irq 5 at device 5.1 on >pci2 > pcib2: device asr0 requested unsupported memory range 0xf600-0xf640 > pcib2: device asr0 requested unsupported memory range 0x0-0xec9f (decoding >0xec90-0xec9f, 0xf600-0xfbff) > asr: map failed at: 2602 p:f600 f640 l:0040 > asr0: could not map memory > device_probe_and_attach: asr0 attach returned 6 > > wtf is going on here? One wild guess, our PCI code isn't noticing that the device is sitting on the other side of a bridge? pci2: on pcib2 pci2: at device 4.0 (no driver attached) pcib3: at device 5.0 on pci2 pci2: at device 5.1 (no driver attached) ... asr0: mem 0xf600-0xf7ff irq 5 at device 5.1 on pci2 asr0: mem 0xf600-0xf7ff irq 5 at device 5.1 on pci2 asr0: mem 0xf600-0xf7ff irq 5 at device 5.1 on pci2 full dmesg follows: 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 #1: Sat Mar 30 12:28:13 PST 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/smpng2 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0564000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc05640a8. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc05640f8. Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) MP 1900+ (1600.06-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383fbff AMD Features=0xc048 real memory = 536870912 (524288K bytes) avail memory = 515665920 (503580K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 1, version: 0x00040010, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Pentium Pro MTRR support enabled VESA: v2.0, 8192k memory, flags:0x1, mode table:0xc0486d62 (122) VESA: Matrox Graphics Inc. Using $PIR table, 12 entries at 0xc00fdf00 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. acpi0: sleep button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_button0: on acpi0 acpi_pcib0: port 0x8080-0x80ff,0x8000-0x807f,0xcf8-0xcff iomem 0xd8000-0xdbfff on acpi0 pci0: on acpi_pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 7.3 (no driver attached) pcib2: at device 16.0 on pci0 pci2: on pcib2 pci2: at device 4.0 (no driver attached) pcib3: at device 5.0 on pci2 pci3: on pcib3 pci2: at device 5.1 (no driver attached) ohci0: mem 0xec901000-0xec901fff irq 10 at device 6.0 on pci2 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: OPTi OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0xec902000-0xec902fff irq 9 at device 6.1 on pci2 usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: OPTi OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pcm0: port 0x2000-0x20ff irq 9 at device 7.0 on pci2 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x2400-0x247f mem 0xec903000-0xec90307f irq 9 at device 8.0 on pci2 xl0: Ethernet address: 00:e0:81:20:6f:f5 miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto 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 4D+ Mouse, device ID 8 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-0x77f,0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 on acpi0 fdc0: FIFO enabled, 8 bytes threshold orm0: at iomem 0xc8800-0xce7ff,0xc8000-0xc87ff,0xc-0xc7fff 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 ad0: 29188MB [59303/16/63] at ata0-master
Re: kldxref problem
On Sat, 30 Mar 2002, A.Z. wrote: > I am upgrading 4.5 to -current. > > buildworld went fine, > make buildkernel also fine, > but make installkernel is giving me an error > > kldxref/boot/kernel > kldxref: No Such Fule or Directory > > ***Error code 1(ignored) Did you miss this part? Man, this throws everyone off. The error was IGNORED. THERE IS NO PROBLEM. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
asr can not map memory?
I just got the Adaptec 4 port IDE raid card 2400A.
It doesn't probe right:
asr0: could not map memory
I added some debug printouts to the asr driver and pci code.
asr0: mem 0xf600-0xf7ff irq 5 at device 5.1 on pci2
pcib2: device asr0 requested unsupported memory range 0xf600-0xf640
pcib2: device asr0 requested unsupported memory range 0x0-0xec9f (decoding
0xec90-0xec9f, 0xf600-0xfbff)
asr: map failed at: 2602 p:f600 f640 l:0040
asr0: could not map memory
device_probe_and_attach: asr0 attach returned 6
wtf is going on here?
? pci/.pci_pci.c.swp
cvs server: Diffing pci
Index: pci/pci_pci.c
===
RCS file: /home/ncvs/src/sys/dev/pci/pci_pci.c,v
retrieving revision 1.12
diff -u -r1.12 pci_pci.c
--- pci/pci_pci.c 26 Feb 2002 03:31:35 - 1.12
+++ pci/pci_pci.c 31 Mar 2002 04:44:57 -
@@ -345,6 +345,12 @@
case SYS_RES_MEMORY:
if (!pcib_is_isa_mem(start)) {
#ifndef PCI_ALLOW_UNSUPPORTED_IO_RANGE
+ if (bootverbose)
+ device_printf(dev,
+ "device %s%d requested unsupported memory range "
+ "0x%lx-0x%lx\n",
+ device_get_name(child), device_get_unit(child), start,
+ end);
if (start < sc->membase && end > sc->membase)
start = sc->membase;
if (end > sc->memlimit)
cvs server: Diffing asr
Index: asr/asr.c
===
RCS file: /home/ncvs/src/sys/dev/asr/asr.c,v
retrieving revision 1.18
diff -u -r1.18 asr.c
--- asr/asr.c 20 Mar 2002 02:02:35 - 1.18
+++ asr/asr.c 31 Mar 2002 04:45:12 -
@@ -2598,16 +2598,20 @@
sc->ha_mem_res = bus_alloc_resource(tag, SYS_RES_MEMORY, &rid,
p, p + l, l, RF_ACTIVE);
if (sc->ha_mem_res == (struct resource *)NULL) {
+ printf("asr: map failed at: %d p:%08x %08x l:%08x\n",
+ __LINE__, p, p+l, l);
return (0);
}
sc->ha_Base = (void *)rman_get_start(sc->ha_mem_res);
if (sc->ha_Base == (void *)NULL) {
+ printf("map failed at: %d\n", __LINE__);
return (0);
}
sc->ha_Virt = (i2oRegs_t *) rman_get_virtual(sc->ha_mem_res);
if (s == 0xA5111044) { /* Split BAR Raptor Daptor */
if ((rid += sizeof(u_int32_t))
>= (PCIR_MAPS + 4 * sizeof(u_int32_t))) {
+ printf("map failed at: %d\n", __LINE__);
return (0);
}
p = pci_read_config(tag, rid, sizeof(p));
@@ -2621,9 +2625,11 @@
sc->ha_mes_res = bus_alloc_resource(tag, SYS_RES_MEMORY, &rid,
p, p + l, l, RF_ACTIVE);
if (sc->ha_mes_res == (struct resource *)NULL) {
+ printf("map failed at: %d\n", __LINE__);
return (0);
}
if ((void *)rman_get_start(sc->ha_mes_res) == (void *)NULL) {
+ printf("map failed at: %d\n", __LINE__);
return (0);
}
sc->ha_Fvirt = (U8 *) rman_get_virtual(sc->ha_mes_res);
@@ -2671,6 +2677,7 @@
debug_asr_printf (
"asr_pci_map_mem failed: bad memory type=0x%x\n",
(unsigned) l);
+ printf("map failed at: %d\n", __LINE__);
return (0);
};
@@ -2703,6 +2710,7 @@
if ((sc->ha_Base == (void *)NULL)
|| (sc->ha_Base == (void *)PCI_MAP_MEMORY_ADDRESS_MASK)) {
debug_asr_printf ("asr_pci_map_mem: not configured by bios.\n");
+ printf("map failed at: %d\n", __LINE__);
return (0);
};
@@ -2716,6 +2724,7 @@
psize + poffs);
if (sc->ha_Virt == (i2oRegs_t *)NULL) {
+ printf("map failed at: %d\n", __LINE__);
return (0);
}
@@ -2723,6 +2732,7 @@
if (s == 0xA5111044) {
if ((rid += sizeof(u_int32_t))
>= (PCI_MAP_REG_START + 4 * sizeof(u_int32_t))) {
+ printf("map failed at: %d\n", __LINE__);
return (0);
}
@@ -2757,6 +2767,7 @@
debug_asr_printf (
"asr_pci_map_mem failed: bad memory type=0x%x\n",
(unsigned) l);
+ printf("map failed at: %d\n", __LINE__);
return (0);
};
@@ -2778,6 +2789,7 @@
sc->ha_Fvirt = (U8 *)pmap_mapdev (p - poffs, psize + poffs);
if (sc->ha_Fvirt == (U8 *)NULL) {
+ printf("map failed at: %d\n", __LINE__);
retu
kldxref problem
I am upgrading 4.5 to -current. buildworld went fine, make buildkernel also fine, but make installkernel is giving me an error kldxref/boot/kernel kldxref: No Such Fule or Directory ***Error code 1(ignored) Any suggestions? I am using SMP system. Thanks, Andrei. P.S. please CC me as I am not on the list. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: nfsclient module panics
It would be good to see where this actually is when it traps; DDB would help. (Sorry if this has already been dealt with) > For a couple of days, I have been consistent panics whenever I mount > an NFS filesystem on a newly made -CURRENT. Things seem to work fine > when NFS is actually built into the kernel. But when mount(8) is auto > loading the nfsclient.ko module, I get an immediate panic when > something actually tries to access the filesystem, > > IdlePTD at phsyical address 0x00411000 > initial pcb at physical address 0x00340ac0 > panicstr: bdwrite: buffer is not busy > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xc2 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc942baeb > stack pointer = 0x10:0xc8ea1c10 > frame pointer = 0x10:0xc8ea1cbc > 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 = 7 (syncer) > trap number = 12 > panic: page fault > > syncing disks... panic: bdwrite: buffer is not busy > Uptime: 2m10s > > dumping to dev ad0s2b, offset 264864 > dump ata0: resetting devices .. done > 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 1 > 07 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 8 > 4 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 > 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 > 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 > 5 4 3 2 1 0 > --- > #0 0xc01b6b8a in dumpsys () > > Is this a known issue (I haven't noted mention of it on here) or does > someone want to see some more debugging info? > -- > Crist J. Clark | [EMAIL PROTECTED] >| [EMAIL PROTECTED] > http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bus error compiling thefish 0.2 on -current
In the last episode (Mar 30), Kris Kennaway said: > On Sat, Mar 30, 2002 at 06:40:52PM +0100, Miguel Mendez wrote: > > On Sat, Mar 30, 2002 at 02:17:45PM +0100, Miguel Mendez wrote: > > > > Just for the record, and to make things more fun, the program works when > > linked with efence. Could this narrow the problem to libc? Any ideas? > > Sounds like it could be the malloc.conf defaults on -current exposing > a bug in the program code. BTW, you set efence to fill memory like -current's malloc by setting the environment variable EF_FILL to "208". -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'moused' freezing system
According to Matthias Schuendehuette: > I encountered a problem when using 'moused' on /dev/ums0: On shutdown > or if 'moused' gets killed manually, the system freezes completely and > silently, no further shutdown is possible, only the resetbutton > operates... I think it is more of an USB problem than just moused. If I have loaded the usb module (which create a usb0 kernel thread) when I do a suspend, on resume the machine hangs. Around BSDcon in February, I was getting a panic() now that I've temporarely removed DDB, it just hangs. This is on a Sony VAIO Z600TEK with APM (not ACPI, it doesn't resume at all with ACPI). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bus error compiling thefish 0.2 on -current
On Sat, Mar 30, 2002 at 10:58:58PM +0100, Miguel Mendez wrote: > Why this problem doesn't show on -STABLE is still beyond my > comprehension, default malloc behaviour maybe? -stable has different default settings for malloc.conf, that's probably why it didn't show up. the -current settings are for maximum debugging, at the expense of performance, but it helps people catch bugs like this. -garrett -- garrett rooneyRemember, any design flaw you're [EMAIL PROTECTED] sufficiently snide about becomes http://electricjellyfish.net/ a feature. -- Dan Sugalski To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bus error compiling thefish 0.2 on -current
On Sat, Mar 30, 2002 at 01:31:09PM -0800, Kris Kennaway wrote: Hi Terry and Kris, > Sounds like it could be the malloc.conf defaults on -current exposing > a bug in the program code. Yes, there was a bug in my code, it just didn't show up on -STABLE. Apparently, when one uses efence, allocated memory is zeroed, which would explain why the program worked when linked with efence. I've built a debug version of libdialog and found something interesting... #0 0x28324253 in dialog_checklist (title=0x80bcf54 "Knobs Menu", prompt=0x80bcf60 "A checked entry means that knob is set to YES", height=-1,width=-1, list_height=15, cnt=-1697, it=0x81e6014, result=0x0) at checklist.c:82 82 status[i] = ditems[i].checked ? ditems[i].checked(&ditems[i]) : FALSE; There is something odd in that cnt value, as there aren't 1697 entries in the menu. The problem is the way the dialog structure is built, I malloc memory but don't zero it, so when I call the function that in the end calls dialog, it erroneously assumes that there are more entries than there really are, since it simply checks for !=0 data. The garbage present in the malloc'ed mem is the cause. Why this problem doesn't show on -STABLE is still beyond my comprehension, default malloc behaviour maybe? Anyway, problem solved, thanks for all. Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg36803/pgp0.pgp Description: PGP signature
Re: Bus error compiling thefish 0.2 on -current
On Sat, Mar 30, 2002 at 06:40:52PM +0100, Miguel Mendez wrote: > On Sat, Mar 30, 2002 at 02:17:45PM +0100, Miguel Mendez wrote: > > Just for the record, and to make things more fun, the program works when > linked with efence. Could this narrow the problem to libc? Any ideas? Sounds like it could be the malloc.conf defaults on -current exposing a bug in the program code. Kris msg36802/pgp0.pgp Description: PGP signature
Re: usbd(8) doesn't attach aue(4) device properly?
On Sat, Mar 30, 2002 at 01:33:13PM +, Josef Karthauser wrote: > It's more likely that it's a new device that isn't included in usbdevs > or the driver. What's the product id that you get with 'usbdevs -v'. > Check that they're in the usbdevs file and in the driver code. Good call. Here's the info: <1 1105-0> (15:44:40) [will@altair ~]% sudo usbdevs -v Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 addr 2: full speed, power 156 mA, config 1, DSB-650TX USB Ethernet(0x400b), D-Link Corp.(0x2001), rev 1.01 port 2 powered According to sys/dev/usbdevs: /* D-Link products */ /*product DLINK DSBS25 0x0100 DSB-S25 serial adapter*/ product DLINK DSB650C 0x4000 10Mbps ethernet adapter product DLINK DSB650TX 0x4002 10/100 ethernet adapter product DLINK DSB650TX_PNA 0x4003 1/10/100 ethernet adapter product DLINK DSB6500xABC1 10/100 ethernet adapter So, like I said, you're right. :) Is this the only place I need to put information in? Somehow I doubt it. Please provide a patch so I can learn... :) BTW, I tried to override the default behavior found here by adding this information to /etc/usbd.conf but that doesn't work.. Thanks! -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bus error compiling thefish 0.2 on -current
Miguel Mendez wrote: > > On Sat, Mar 30, 2002 at 02:17:45PM +0100, Miguel Mendez wrote: > > Just for the record, and to make things more fun, the program works when > linked with efence. Could this narrow the problem to libc? Any ideas? Sounds like a change in the libdialig stuff is biting you. You may want to try an older version of the code to see if that's it, and then talk to Eric Melville, if it is. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: help needed: freebsd gcc bug breaks STLport and OpenOffice
Martin Blapp wrote: > > Not help, but a question: > > > > If openoffice compiles with ports' version of gcc? > > And if it runs compiled this way? > > unfortunatly not. The build segfaults in a different way. I'll upgrade the port > to the latedt build tomorrow. Let's see if it builds now properly with > gcc3.1 Not going to work. It's going to get the wrong RTTI header. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Another possible solution for non-sendmail users
Thanks to some reviewers, a couple of problems with my last patch have been fixed. This time, I've actually tried the combinations involved to make sure it works. The changes from the last patch are only to /etc/mail/Makefile and /etc/rc.sendmail. rc.sendmail changes: - Use proper shell variable substitution - Make it more like rc.d scripts: - start, stop, and restart now affect all daemons, not just the MTA. - New targets: start-mta, stop-mta, restart-mta - Optimize by using functions instead of making the script re-execute itself. Makefile changes: - Fix syntax error - Check for pidfile before trying to use it with kill (warn if not present) - Minor cosmetic changes The updated patch is available in the same location: http://people.freebsd.org/~gshapiro/mta-start I've also pulled out the two changed files for those who have already patched: http://people.freebsd.org/~gshapiro/Makefile http://people.freebsd.org/~gshapiro/rc.sendmail I'll give this new patch a couple of days review time before committing it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Another possible solution for non-sendmail users
>> In a somewhat unrelated note, I also plan on arranging to move the >> sendmail-specific stuff out of src/etc/mail/ and into src/etc/sendmail so >> the installation of things like sample sendmail maps, etc. don't clutter a >> NO_SENDMAIL installation. I'll need to arrange this event with the CVS >> repomeisters. Hopefully, this change (along with the patch) will make >> things more palatable for non-sendmail users. andyf> Could you expand on this please? Why would a NO_SENDMAIL andyf> installworld install sendmail maps, etc. in the first place? It andyf> shouldn't matter what the source directory is. That's just the way /usr/src/etc/Makefile has always been. Strictly speaking, the source files don't have to move, I think it would be more logical if they did. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Another possible solution for non-sendmail users
keramida> A better fix would be to use the sh(1) way of conditionally setting a
keramida> variable:
keramida> sendmail_program=${sendmail_program:-/usr/sbin/sendmail}
keramida> Similarly for the rest of those ?= assignments.
keramida> AFAIK, the ?= assignment style works in make rules.
keramida> Perhaps that's where this came from :-)
Thanks, that will teach me to write a script at 5:30 in the morning. I'll
post a new version shortly.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: USB printing broken?
>
> I've a kernel from Mar 27 which isn't able to print with my USB printer.
>
> usbdevs hangs hard ('.vd' is a typo, I wanted to use '-vd'):
> ---snip---
> netchild 14525 0.0 0.7 4152 427 p0 D+4:13pm 0:00.02 usbdevs .vd
> ---snip---
>
> ulpt0: Hewlett-Packard DeskJet 895C, rev 1.00/1.00, addr 3, iclass 7/1
> ulpt0: using bi-directional mode
>
> Is anyone out there able to reproduce this?
>
> A Mar 12 kernel works just fine.
A kernel from Mar 19 also does not work for me. Usbdevs doesn't hang but
printing just doesn't happen. It just stays in the queue. When I tried
to print a test page from the SETUP program that comes with apsfilter,
it either hangs forever or just says that /dev/ulpt0 is busy. My printer
is:
ulpt0: Hewlett-Packard DeskJet 840C, rev 1.00/1.00, addr 3, iclass 7/1
ulpt0: using bi-directional mode
John
--
John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Another possible solution for non-sendmail users
On Sat, Mar 30, 2002 at 07:12:52PM +0100, Dag-Erling Smorgrav wrote: > Gregory Neil Shapiro <[EMAIL PROTECTED]> writes: > > Given that non-sendmail users will be inconvenienced when upgrading due to > > the 8.12 changes (need to change sendmail_enable from "NO" to "NONE"), > > Why? It doesn't make any difference as long as one uses the > mailwrapper stuff: Yes, it does. > > des@des ~% grep sendmail /etc/rc.conf > sendmail_enable="YES" > des@des ~% cat /etc/mail/mailer.conf > # > # Execute the Postfix sendmail program, named /usr/local/sbin/sendmail > # > sendmail/usr/local/sbin/sendmail > send-mail /usr/local/sbin/sendmail > mailq /usr/local/sbin/sendmail > newaliases /usr/local/sbin/sendmail > > So what's all this noise and racket about? This assumes that the replacement "sendmail" binary accepts the same options as the real sendmail. In particular the options that are used by default in the rc* files. This is not the case for qmail for example. (And there the normal use is not to start it with sendmail_enable="YES" but rather from its own start file under /usr/local/etc/rc.d/ after disabling sendmail with sendmail_enable="NO" (now "NONE"), which I think should be the standard behaviour for alternative MTAs.) So, if one uses qmail this change does require you to modify the sendmail_* options in /etc/rc.conf. -- Erik Trulsson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Another possible solution for non-sendmail users
ianjhart> One small quibble. If I want to set ianjhart> mta_start_script="" ianjhart> and run rc.sendmail(.sh) from /usr/local/etc/rc.d ianjhart> shouldn't "stop" kill both queues? You'd need to add ianjhart> a stop-mtaq obviously. ianjhart> A global restart might be nice too. Yes, rc.sendmail should follow the standard start/stop conventions. I'll fix it up today and post a new version. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Another possible solution for non-sendmail users
>> Given that non-sendmail users will be inconvenienced when upgrading due to >> the 8.12 changes (need to change sendmail_enable from "NO" to "NONE"), des> Why? It doesn't make any difference as long as one uses the des> mailwrapper stuff: des> des@des ~% grep sendmail /etc/rc.conf des> sendmail_enable="YES" This fixes things for people who use sendmail_enable="NO". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Another possible solution for non-sendmail users
Gregory Neil Shapiro <[EMAIL PROTECTED]> writes: > Given that non-sendmail users will be inconvenienced when upgrading due to > the 8.12 changes (need to change sendmail_enable from "NO" to "NONE"), Why? It doesn't make any difference as long as one uses the mailwrapper stuff: des@des ~% grep sendmail /etc/rc.conf sendmail_enable="YES" des@des ~% cat /etc/mail/mailer.conf # # Execute the Postfix sendmail program, named /usr/local/sbin/sendmail # sendmail/usr/local/sbin/sendmail send-mail /usr/local/sbin/sendmail mailq /usr/local/sbin/sendmail newaliases /usr/local/sbin/sendmail So what's all this noise and racket about? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: help needed: freebsd gcc bug breaks STLport and OpenOffice
> With gcc3.1 on -CURRENT, or with gcc3.1 on -STABLE? Both :) martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current:LINT broken...
On Sat, 30 Mar 2002, Poul-Henning Kamp wrote: > ../../../dev/pdq/pdq.c: In function `pdq_initialize': > ../../../dev/pdq/pdq.c:1606: warning: cast discards qualifiers from > pointer target type *** Error code 1 Bah. Bandaided. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bus error compiling thefish 0.2 on -current
On Sat, Mar 30, 2002 at 02:17:45PM +0100, Miguel Mendez wrote: Just for the record, and to make things more fun, the program works when linked with efence. Could this narrow the problem to libc? Any ideas? Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg36788/pgp0.pgp Description: PGP signature
Re: help needed: freebsd gcc bug breaks STLport and OpenOffice
Hello, Martin Blapp! On Sat, Mar 30, 2002 at 06:38:20PM +0100, you wrote: > > If openoffice compiles with ports' version of gcc? > > And if it runs compiled this way? > > unfortunatly not. The build segfaults in a different way. I'll upgrade the port > to the latedt build tomorrow. Let's see if it builds now properly with > gcc3.1 With gcc3.1 on -CURRENT, or with gcc3.1 on -STABLE? -- NEVE-RIPE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: help needed: freebsd gcc bug breaks STLport and OpenOffice
Hi, > Not help, but a question: > > If openoffice compiles with ports' version of gcc? > And if it runs compiled this way? unfortunatly not. The build segfaults in a different way. I'll upgrade the port to the latedt build tomorrow. Let's see if it builds now properly with gcc3.1 Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current:LINT broken...
bang# make LINT perl5 makeLINT.pl < NOTES > LINT bang# config LINT LINT: unknown option "CV_DEBUG" If one stubbornly fixes that, the next roadblock becomes: cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I/usr/include -DGPROF -DGPROF4 -DGUPROF -D_KERNEL -ffreestanding -include opt_global.h -fno-common -malign-functions=4 -fno-builtin -mpreferred-stack-boundary=2 -Werror -pg -mprofiler-epilogue ../../../dev/pdq/pdq.c cc1: warnings being treated as errors ../../../dev/pdq/pdq.c: In function `pdq_initialize': ../../../dev/pdq/pdq.c:1606: warning: cast discards qualifiers from pointer target type *** Error code 1 -- 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: help needed: freebsd gcc bug breaks STLport and OpenOffice
Hello, Martin Blapp! On Mon, Mar 04, 2002 at 01:10:58AM +0100, you wrote: > It looks like our modified FreeBSD GCC breaks the STLport tests, > as it breaks OpenOffice too. > > If one uses a normal unmodified stock gcc version (gcc 2.95.2 or > 2.95.3), and compiles it on STABLE or CURRENT, the coredump goes away. > > Note that there are no special flags, only c++ -pthread -Wall -g -O > where specified. Not help, but a question: If openoffice compiles with ports' version of gcc? And if it runs compiled this way? -- NEVE-RIPE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USB printing broken?
Hi,
I've a kernel from Mar 27 which isn't able to print with my USB printer.
usbdevs hangs hard ('.vd' is a typo, I wanted to use '-vd'):
---snip---
netchild 14525 0.0 0.7 4152 427 p0 D+4:13pm 0:00.02 usbdevs .vd
---snip---
ulpt0: Hewlett-Packard DeskJet 895C, rev 1.00/1.00, addr 3, iclass 7/1
ulpt0: using bi-directional mode
Is anyone out there able to reproduce this?
A Mar 12 kernel works just fine.
Bye,
Alexander.
--
Loose bits sink chips.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Just a reminder
rwatson> It seems to me the kernel entry point should be mi_start() rwatson> rather than main(), however. Good point. I just did a small hack to do that: http://snapshots.jp.freebsd.org/tour/current/kernel/> 4-stable kernel tour will be changed also tomorrow. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/share/mk bsd.lib.mk
Ruslan Ermilov <[EMAIL PROTECTED]> writes:
> A note. What appears in dependency lists actually are libraries
> from ${WORLDTMP}/usr/include, not /usr/include. Not very useful
> outside of "make buildworld", yeah?
Wrong. Try backing out the patch, then
# cd /usr/src/secure
# make obj && make depend && make && make install
# make && make install
You'll see a lot of stuff getting rebuilt because static libraries
in /usr/lib have changed.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/share/mk bsd.lib.mk
On Sat, Mar 30, 2002 at 02:15:56PM +0100, Dag-Erling Smorgrav wrote:
> Ruslan Ermilov <[EMAIL PROTECTED]> writes:
> > On Fri, Mar 22, 2002 at 12:28:17PM -0800, Dag-Erling Smorgrav wrote:
> > > Log:
> > > Install static and profiled libraries with -C.
> > Um why, what's so special about them?
>
> They appear in dependency lists. This was discussed on -arch.
>
Thanks. Please include this sort of information in commitlogs.
A note. What appears in dependency lists actually are libraries
from ${WORLDTMP}/usr/include, not /usr/include. Not very useful
outside of "make buildworld", yeah? Same for headers. But I can
see the bonus with "make -DNOCLEAN buildworld" over previous run.
Was that the real aim?
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
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: usbd(8) doesn't attach aue(4) device properly?
On Fri, Mar 29, 2002 at 08:37:55PM -0500, Will Andrews wrote: > Hi, > > I'm trying to hook my new D-Link DSB-650TX up to a laptop with > USB on a March ~26 -CURRENT. However, it's failing miserably: > > uhci0: port 0xfce0-0xfcff irq 11 at device >7.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 > ugen0: D-Link Corp. DSB-650TX USB Ethernet, rev 1.10/1.01, addr 2 > > if_aue.ko is being loaded by the loader at boot time, so this > should be working.. but the device is attaching to ugen(4) > instead of aue(4). Ideas? The only thing I could think of was > /etc/usbd.conf was out of date, but a mergemaster didn't fix this > problem. It's more likely that it's a new device that isn't included in usbdevs or the driver. What's the product id that you get with 'usbdevs -v'. Check that they're in the usbdevs file and in the driver code. Joe msg36779/pgp0.pgp Description: PGP signature
Re: USB mouse problem
On Sat, 30 Mar 2002, Masahide -mac- NODA wrote: Same here, solid lock, debug key not work. If I setup X to use /dev/ums0 computer hang just after startx. All worked with kernel/world from Mar 12. -- Mar 26 17:32:08 pyvo kernel: FreeBSD 5.0-CURRENT #10: Tue Mar 26 16:29:37 EET 2002 ... Mar 26 17:32:08 pyvo kernel: uhci0: port 0xb400-0xb41f irq 11 at device 4.2 on pci0 Mar 26 17:32:08 pyvo kernel: usb0: on uhci0 Mar 26 17:32:08 pyvo kernel: usb0: USB revision 1.0 Mar 26 17:32:08 pyvo kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 26 17:32:08 pyvo kernel: uhub0: 2 ports with 2 removable, self powered Mar 26 17:32:08 pyvo kernel: ums0: Microsoft Microsoft IntelliMouse. Explorer, rev 1.10/1.14, addr 2, iclass 3/1 Mar 26 17:32:08 pyvo kernel: ums0: 5 buttons and Z dir. Mar 26 17:32:08 pyvo kernel: uhci1: port 0xb000-0xb01f irq 11 at device 4.3 on pci0 Mar 26 17:32:08 pyvo kernel: usb1: on uhci1 Mar 26 17:32:08 pyvo kernel: usb1: USB revision 1.0 Mar 26 17:32:08 pyvo kernel: uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Mar 26 17:32:08 pyvo kernel: uhub1: 2 ports with 2 removable, self powered > Hi, -current users. > > I found 'hung up situtation' with USB mouse on current. > > - Insert USB mouse to FreeBSD-CURRENT machine. > - search moused pid for USB mouse > - kill pid to hungup > > This problem cause 'unable to shutdown FreeBSD'. > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Another possible solution for non-sendmail users
On Thu, 28-Mar-2002 at 14:49:49 -0600, Scot W. Hetzel wrote: > From: "Coleman Kane" <[EMAIL PROTECTED]> > > Another thing to look at is the /usr/sbin/sendmail -> mailwrapper link > that is > > produced from installworld. In current it seems to have been linking that, > even > > Stable creates the same links to mailwrapper. > > > when NO_SENDMAIL=yes in make.conf. Qmail et al. overwrite this with their > own > > workalike (since /usr/sbin/sendmail is a 'standard' these days) local > mailer. > > I dunno if -stable has this problem too. > > > You want to set NO_MAILWRAPPER in make.conf to prevent the linking to This might give you more problems: http://www.freebsd.org/cgi/query-pr.cgi?pr=29699 Nobody seems to have agreed to a solution yet... :-) -Andre > mailwrapper. But if you do this, you'll loose the configurablity that > mailwrapper provides for alternate MTA's via /etc/mail/mailer.conf. > > Qmail install shouldn't need to install anything into /usr/[sbin,bin] > directories with mailwrapper properly configured (see `man mailer.conf` & > 'man mailwrapper'). > > Mailwrapper was designed so that you didn't need to re-create your links to > your personal MTA (in /usr/[bin,sbin], when upgrading FreeBSD. > > Scot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bus error compiling thefish 0.2 on -current
Hi, I'm finishing the new version of sysutils/thefish, and doing some development on a -current box. For the ncurses/dialog frontend, I'm using a couple of functions from the sysinstall code, and this program works perfectly well on a 4.5-STABLE system. If I take the binary and run it on -CURRENT, it works as well, but, if I compile that code on -CURRENT, the program dies with a Bus Error the moment I enter the Knobs menu. I've seen this problem both with the 11th of March snapshot and with a world I built yesterday, cvsupped at 1500 UTC. The current box specs are these: flynn@saioa# uname -a FreeBSD saioa.energyhq.tk 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Mar 30 00:37:49 GMT 2002 root@:/usr/obj/usr/src/sys/SAIOA i386 flynn@saioa# cc -v Using builtin specs. gcc version 2.95.4 20020320 [FreeBSD] The gdb trace when the program fails: (gdb) bt #0 0x280da10a in dialog_menu () from /usr/lib/libdialog.so.4 #1 0x804e0a7 in dmenuOpen (menu=0x81d5000, choice=0xbfbff8bc, scroll=0xbfbff8c0, curr=0xbfbff8c4, max=0xbfbff8c8, buttons=0) at ncurses_ui.c:249 #2 0x804df6a in dmenuOpenSimple (menu=0x81d5000, buttons=0) at ncurses_ui.c:191 #3 0x804deff in dmenuSubmenu (tmp=0x80bb6f4) at ncurses_ui.c:175 #4 0x280db1ae in dialog_menu () from /usr/lib/libdialog.so.4 #5 0x804e0a7 in dmenuOpen (menu=0x80bb680,choice=0xbfbffa5c, scroll=0xbfbffa60, curr=0xbfbffa64, max=0xbfbffa68,buttons=1) at ncurses_ui.c:249 #6 0x804debf in create_ncurses_ui(rc_knobs=0x817b000, num_knobs=96, rc_strings=0x8197000, num_str=138) at ncurses_ui.c:163 #7 0x804b2ed in main (argc=0, argv=0xbfbffb18) at main.c:216 #8 0x804a5c5 in _start () (gdb) The program tarball can be found at http://energyhq.homeip.net/files/thefish-0.2.tar.gz My question is, is it a bug in my program that only shows in -CURRENT or is the compiler in current broken? Cheers, -- Miguel Mendez - [EMAIL PROTECTED] GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! msg36776/pgp0.pgp Description: PGP signature
Re: cvs commit: src/share/mk bsd.lib.mk
Ruslan Ermilov <[EMAIL PROTECTED]> writes: > On Fri, Mar 22, 2002 at 12:28:17PM -0800, Dag-Erling Smorgrav wrote: > > Log: > > Install static and profiled libraries with -C. > Um why, what's so special about them? They appear in dependency lists. This was discussed on -arch. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/share/mk bsd.lib.mk
On Fri, Mar 22, 2002 at 12:28:17PM -0800, Dag-Erling Smorgrav wrote: > des 2002/03/22 12:28:17 PST > > Modified files: > share/mk bsd.lib.mk > Log: > Install static and profiled libraries with -C. > > Revision ChangesPath > 1.106 +2 -2 src/share/mk/bsd.lib.mk > Um why, what's so special about them? -- 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with ssh
"David O'Brien" <[EMAIL PROTECTED]> writes: > Something is still very wrong: > > ssh foo@releng4 > otp-md5 350 re9786 ext > S/Key Password: > otp-md5 134 re2584 ext > S/Key Password: > otp-md5 417 re5381 ext > S/Key Password: > otp-md5 198 re2571 ext > S/Key Password: > > Uh, why does my sequence keep changing when I just hit ??? Because it's generating fake S/Key challenges, and badly. > And this will not accept my Unix password until I enter garbage _3_ times, > then I finally get a Unix password prompt. > > Hello, DES? Have you seen this thread? No, I haven't seen it, but I've had similar reports. It's actually a bug on the server side, in older OpenSSH servers, that is exposed by newer OpenSSH clients. I haven't yet determined a correct client-side solution, but a workaround is to disable S/Key authentication for those hosts where you don't actually want to use it, by adding the following to ~/.ssh/config: Host foo bar baz SKeyAuthentication no OpenSSH 3.1 servers on -CURRENT will DTRT since they use PAM. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USB mouse problem
Hi, -current users. I found 'hung up situtation' with USB mouse on current. - Insert USB mouse to FreeBSD-CURRENT machine. - search moused pid for USB mouse - kill pid to hungup This problem cause 'unable to shutdown FreeBSD'. -- Masahide -mac- NODA [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current SMP status with Intel PR440FX?
Manfred Antar writes: > Here it is: > CPU: Overdrive Pentium II/Pentium II Xeon/Celeron (331.11-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x1632 Stepping = 2 > >Features=0x183fbff > Programming 24 pins in IOAPIC #0 > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000 > cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000 > io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec0 > Mounting root from uSfMsP::/ dAePv /CdPaU0 s#11a > Launched! > Also yours looks quite funny. Tomppa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current SMP status with Intel PR440FX?
Manfred Antar writes: > > I'm using one of these boards for about 3 years with SMP. > I'm running current with a kernel from sources current as of 1/2 hour ago > no problem. > The cpu's I'm using are the PentiumPro Overdrive processors that > intel put out. I've been using these the last 6 months, before that I > was using 200mhz ones. > Hi, If you compare your dmesg output to this one, does your CPU1 apic_initialize look any better than this? One those many panics we have seen this line is sometimes full of control characters. CPU: Pentium Pro (198.67-MHz 686-class CPU) SMP: CPU0 apic_initialize(): lint0: 0x0700 lint1: 0x00010400 TPR: 0x0010 SVR: 0x01ff FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x0400 TPR: 0x0010 SVR: 0x01ff SMP: CPU1 apic_initountinialg roize(ot ): from lint0: 0x00010700 lint1: 0x00010400 TPR: 0x0010 SVR: 0x01ff SMP: AP CPU #1 Launched! Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Superfast clock on current.
In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes: >In message <[EMAIL PROTECTED]>, David Malone writes: >>On Tue, Mar 26, 2002 at 09:59:29AM +0100, Poul-Henning Kamp wrote: >>> This is an interesting machine: A K6 wiht ACPI, havn't seen that >>> before. >> >>I had one of these machines and concluded that the ACPI time counter >>was busted. I dunno if it is possible to sanity check the time >>counter before using it? I just switched to using the TSC early in >>boot and forgot about it. > >That is what I try to do, and I recently rewrote the code in current >for that exact reason, so I'm very interested in seeing the diagnostic >output (boot -v) from a -current kernel on these motherboards. I've stared at the data file and I'll be damned if I can find anything which would case the clock to double its speed :-( -- 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: ICC userland patch (was: Re: cvs commit: ports/lang Makefile ports/lang/icc Makefile distinfo pkg-comment pkg-descr pkg-plist ports/lang/icc/files patch-include)
On 29 Mär, David O'Brien wrote: >> Not tested, feel free to point out some typo's: >> http://www.leidinger.net/FreeBSD/icc.mk.diff > > Also forbidden to access. Fixed. Sorry. Bye, Alexander. -- Reboot America. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: ports/lang Makefile ports/lang/icc Makefile distinfo pkg-comment pkg-descr pkg-plist ports/lang/icc/files patch-include
On 29 Mär, David O'Brien wrote:
>> > My patches to src/share/mk/ are here:
>> >
>> >ftp://ftp.jurai.net/users/winter/icc.mk.diff
>> >
>> > This allows you to set 'USE_ICC' and 'ICFLAGS' and build stuff.
>
> This is fine just to get things working. But please consider Doing It
> Right -- that being wrap the definitions of CC, CFLAGS, and PICFLAG with
> USE_ICC rather than strew USE_ICC all over the place. For instance:
>
> /usr/share/mk/sys.mk
> .if defined(USE_ICC)
> CC= icc
> .else
> CC= cc
> .endif
- How do you want to solve the single suffix rules then?
- Do we use ${LD} in every significant place?
- What about ports with "CC=${CC}" in CONFIGURE_ENV (they would break
in the USE_ICC case)?
>> > -D__ICC__=1
>>
>> ICC already defines '__ICC', doe we really need this?
>
> I see no reason for it. We should use the vendor's spelling for
> identifying their compiler.
>
>> > -D__attribute__(x)=
>> > -D__GNUC__=2
>>
>> Ok as a short term solution, but IMHO this should get solved in the
>> source.
>
> Totally agreed for defining __GNUC__.
And the __attribute__ line is the reason why libc doesn't work.
Bye,
Alexander.
--
The computer revolution is over. The computers won.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
