no driver attached messsage
why my dmesg always show "no driver attached" ? the mainboard is intel server board S875WP1-E with best regards, -dikshie- --- Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT-20031001-JPSNAP #0: Wed Oct 1 00:54:54 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0761000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0761244. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2394.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 267583488 (255 MB) avail memory = 251961344 (240 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 12 entries at 0xc00f3310 acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib0: slot 29 INTA is routed to irq 5 pcib0: slot 29 INTB is routed to irq 10 pcib0: slot 29 INTC is routed to irq 10 pcib0: slot 29 INTA is routed to irq 5 pcib0: slot 29 INTD is routed to irq 9 pcib0: slot 31 INTA is routed to irq 10 pcib0: slot 31 INTB is routed to irq 11 agp0: mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 3.0 on pci0 pci2: on pcib2 pcib2: slot 1 INTA is routed to irq 10 em0: port 0xac00-0xac1f mem 0xfc9e-0xfc9f irq 10 at device 1.0 on pci2 em0: Speed:N/A Duplex:N/A uhci0: port 0xcc00-0xcc1f irq 5 at device 29.0 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 uhci1: port 0xd000-0xd01f irq 10 at device 29.1 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 uhci2: port 0xd400-0xd41f irq 10 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xd800-0xd81f irq 5 at device 29.3 on pci0 usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib3: at device 30.0 on pci0 pci3: on pcib3 pcib3: slot 1 INTA is routed to irq 11 pcib3: slot 6 INTA is routed to irq 11 pcib3: slot 8 INTA is routed to irq 11 ahc0: port 0xb400-0xb4ff mem 0xfeafe000-0xfeafefff irq 11 at device 1.0 on pci3 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs pci3: at device 6.0 (no driver attached) fxp0: port 0xbc00-0xbc3f mem 0xfeafd000-0xfeafdfff irq 11 at device 8.0 on pci3 fxp0: Ethernet address 00:07:e9:45:69:3d miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0-0x3,0-0x7,0-0x3,0-0x7 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: at device 31.2 (no driver attached) pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 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 IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xc8000-0xcbfff,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 Timecounter "TSC" frequency 2394011720 Hz quality 800 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% acd0: CDROM at ata1-slave PIO4 Waiting 15 seconds for SCSI devices to settle GEOM: create disk da0 dp=0xc2704850 da0 at ahc0 bus 0 target 0 lun 0 d
[current tinderbox] failure on alpha/alpha
TB --- 2003-10-08 04:00:01 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-10-08 04:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-10-08 04:02:02 - building world TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: populating >>> /home/des/tinderbox/CURRENT/alpha/alpha/obj/alpha/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/i386/usr/include >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything.. TB --- 2003-10-08 05:03:45 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Wed Oct 8 05:03:45 GMT 2003 >>> Kernel build for GENERIC completed on Wed Oct 8 05:15:17 GMT 2003 TB --- 2003-10-08 05:15:17 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src/sys/alpha/conf TB --- /usr/bin/make -B LINT TB --- 2003-10-08 05:15:18 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Oct 8 05:15:18 GMT 2003 [...] cc -c -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/coda/coda_subr.c cc -c -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/coda/coda_venus.c cc -c -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/coda/coda_vfsops.c cc -c -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/alpha/alpha/src/sys/coda/coda_vnops.c cc -c -O -pipe -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnest
Re: Atmel AT76C503 USB 802.11b device driver
On Tue Oct 07, 02:36P +0100, Stuart Walsh wrote: > Hi folks, > > I've come up with a driver for the above mentioned devices. This > particular chip is found in a whole load of 802.11b USB devices. My > particular device is an SMC2662W-AR, but it should work for any device > containing the above chip. Just fill in the product/vendor ids and let > me know your results and i'll update my local copy accordingly. > > The driver is at http://stu.bash.sh/atwi-20031007.tar.gz. > Extract the files from within /usr/src/sys and apply atwi.diff with patch > -p0 < atwi.diff. Only 5-CURRENT is supported at this time, so you will > need a fairly recent cvsup. > > If you are going to report problems, set sysctl hw.atwi.debug=2 first > and include all output. Both infrastructure and adhoc modes should > work, but infrastructure mode hasnt been tested this last week as I had > to return the AP I had on loan. You are strongly advised to use this > driver as a module as the usb code has issues with the device if you > unplug and replug it while the module is loaded. I'm working on > fixing this. Other than that it should work fine. Please do report any > successes or failures. Enjoy! Aww crap, my apologies for the duplicate email.. sendmail appears to be on steroids or something. Anyway.. just an update to the installation instructions. Warner kindly committed the usbdevs portion of the driver, so if you have a cvsup from yesterday or newer, you don't need to apply atwi.diff. Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Repeatable ATAng panic.
I have a repeatable ATAng panic. The panic string is "vm_map_wire: lookup failed" and it's caused by using cdrdao on my ATAPICAM connected DVD writer. In this particular case, I'm trying to write a bin/cue format file onto a writeable CD. The panic goes roughly like this: panic: vm_map_wire: lookup failed syncing disks, buffers remaining... 609 609 609 609 609 609 609 609 609 609 609 609 609 609 609 609 609 609 609 609 giving up on 508 buffers Uptime: 2h21m40s Dumping 1023 MB 16 32 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0x0 stack pointer = 0x10:0xe03fbcb0 frame pointer = 0x10:0xe03fbcd4 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 = 20 (swi7: task queue) trap number = 12 panic: page fault Uptime: 2h21m48s ad0: timeout waiting for write DRQad0: timeout waiting for write DRQad0: timeout waiting for write DRQ 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 and the backtrace (without symbols) is: (kgdb) bt #0 0xc055d0db in doadump () #1 0xc055d702 in boot () #2 0xc055da58 in panic () #3 0xc0653912 in vm_map_wire () #4 0xc0656c43 in mlockall () #5 0xc0694873 in syscall () #6 0xc068571d in Xint0x80_syscall () Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: savecore: first and last dump headers disagree on /dev/ad0b
On Tue, 7 Oct 2003, Kris Kennaway wrote: > I also had problems dumping onto a UDMA66 disk on a promise PDC20267 > controller - it seemed to dump OK (dump was readable after I recovered > the disk), but it (or maybe the crash itself) trashed the partition > table. > > Kris I mentioned the very same problem last June in a few posts here. I guess no one else experienced this issue, or there would have been some kind of response. In fact, I haven't been able to recover a crashdump since I switched over to current at the beginning of the year. I have a promise PDC20269 UDMA133 and a Maxtor 60G. More recently, though, sometime in mid September, a panic and crash dump trash my partition table as well. And it's repeatable, but I'm not going to try again to see if it was fixed :) -Bryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Atmel AT76C503 USB 802.11b device driver
Hi folks, I've come up with a driver for the above mentioned devices. This particular chip is found in a whole load of 802.11b USB devices. My particular device is an SMC2662W-AR, but it should work for any device containing the above chip. Just fill in the product/vendor ids and let me know your results and i'll update my local copy accordingly. The driver is at http://stu.bash.sh/atwi-20031007.tar.gz. Extract the files from within /usr/src/sys and apply atwi.diff with patch -p0 < atwi.diff. Only 5-CURRENT is supported at this time, so you will need a fairly recent cvsup. If you are going to report problems, set sysctl hw.atwi.debug=2 first and include all output. Both infrastructure and adhoc modes should work, but infrastructure mode hasnt been tested this last week as I had to return the AP I had on loan. You are strongly advised to use this driver as a module as the usb code has issues with the device if you unplug and replug it while the module is loaded. I'm working on fixing this. Other than that it should work fine. Please do report any successes or failures. Enjoy! Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Proliant 1600R Install Failure (ida + SMPng to blame?)
Good day all, I have a Compaq Proliant 1600R equipped with dual Pentium 2 processors, ECC RAM and a Compaq Smart Array 2DH controller (which uses the ida driver). This machine has been working well with FreeBSD 4.8 and has been tracking the RELENG_4_8 tree without problems. Because running mySQL on 4.8 with SMP is flaky at best, I've been trying to update to 5.X. Sadly, every attempt to do so fails miserably, leading me to believe that there's something going on above my head. Booting off the 5.1 boot floppies gives a page fault about 15 seconds after the mfsroot floppy finishes loading. I know what everyone's going to suggest - hardware - bad RAM or cache. I've run Memtest86 (http://www.memtest86.com/) for the complete suite of tests and it has found no errors. This, plus the fact that 4.8 worked flawlessly leads me to believe that this is not a hardware issue. I also tried remaking the boot disks with fresh floppies, using rawrite instead of fdimage. I get the same results with both methods. Following this I burned an ISO and booted from that - same thing. Here's the message from the panic: -- sio1: type 16550A vga0: at port 0x3e0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec Fatal trap 12: page fault while in kernel mode fault virtual address = 0x5c fault code = supervisor read, page not present instruction pointer = 0x8:0xc01a6ed7 stack pointer = 0x10:0xd6b6dc70 frame pointer = 0x10:0xd6b6dc7c code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPC = 0 current process = 4 (g_down) trap number = 12 panic: page fault ... -- I decided to try another approach: doing a CVSup from RELENG_4_8 to RELENG_5_1 and then remaking world and the kernel. The CVSup works well, but about an hour and a bit into make buildworld I get errors in libpthread and the make dies. Note that I followed the instructions in the Handbook and the src/UPDATING file to the letter. >From what I've heard and seen at http://www.freebsd.org/projects/busdma/ I gather that the ida driver is not ready for SMPng, but regardless. I should at least be able to get into sysinstall, shouldn't I? Does the 5.1 GENERIC kernel even use SMP? The release notes for 5.1 make no special mention of any issues that should affect me and all my hardware appears as being supported in the hardware notes for 5.1. Does anyone have further suggestions for me? Has anyone else got a similar hardware setup which works? I'm rather desperate for help - any suggestions are welcome. Thanks, Ed Aronyk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: savecore: first and last dump headers disagree on /dev/ad0b
On Tue, Oct 07, 2003 at 06:11:30PM -0700, Doug White wrote: > On Tue, 7 Oct 2003, YONETANI Tomokazu wrote: > > > The hardware is IBM NetFinity 6000R, and it has ServerWorks ROSB4 UDMA33 > > controller, to which the IDE disk is attached. The size of the IDE hard > > disk is 4Gbytes, and the size of the kernel dump and physical memory both > > fits in that size. > > The ROSB4 is known to have data-corruption problems with running in UDMA > mode. The dump is probably tripping over this, which is why Tor's patch > works since it demotes the device back to PIO. I also had problems dumping onto a UDMA66 disk on a promise PDC20267 controller - it seemed to dump OK (dump was readable after I recovered the disk), but it (or maybe the crash itself) trashed the partition table. Kris pgp0.pgp Description: PGP signature
Re: savecore: first and last dump headers disagree on /dev/ad0b
On Tue, 7 Oct 2003, YONETANI Tomokazu wrote: > The hardware is IBM NetFinity 6000R, and it has ServerWorks ROSB4 UDMA33 > controller, to which the IDE disk is attached. The size of the IDE hard > disk is 4Gbytes, and the size of the kernel dump and physical memory both > fits in that size. The ROSB4 is known to have data-corruption problems with running in UDMA mode. The dump is probably tripping over this, which is why Tor's patch works since it demotes the device back to PIO. You could optionally set hw.ata.ata_dma=0 in loader.conf to disable UDMA rather than apply the patch. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Strange behaviour with ata(pi)/(cam) OR swapoff OR ext2fs?
Hi, I have had a kernel panic recently on a recent -CURRENT, but I have no clues where that was from (no BT either). I do know that I've used "swapoff -a" with some dozen kBytes in swap, and I've played a lot with atapicam (Plextor PX-4824TA, VIA KT133), and I've had a Linux ext3 partition mounted ro at first and then "mount -u"'d to rw. Since I don't want to point the finger on anything yet: has anyone else seen "swapoff -a" or r/w on ext3 partitions cause strange things? TIA, -- Matthias Andree Encrypt your mail: my GnuPG key ID is 0x052E7D95 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAng doesn't boot on my notebook - panic
It seems Vladimir B. Grebenschikov wrote:
> > Any solution or workaround ?
Try this patch please:
diff -u -r1.191 ata-all.c
--- ata-all.c 7 Oct 2003 13:44:15 - 1.191
+++ ata-all.c 7 Oct 2003 19:15:03 -
@@ -35,6 +35,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -555,7 +556,7 @@
}
ata_free_request(request);
}
- if (error) {
+ if (error || !isalpha(atacap->model[0]) || !isalpha(atacap->model[1])) {
atadev->param = NULL;
free(atacap, M_ATA);
}
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
boot hang: "ata1: resetting devices .. done" (5.1-CURRENT, IBM T30)
Recently I posted about boot hangs if I have atapicam defined in the kernel and a DVD/CD-RW drive in the ultrabay on my T30. As of today's CVSup, I get a hang on boot if the drive is in there regardless of atapicam being defined or not. ad0: 38154MB [77520/16/63] at ata0-master UDMA100 ata1: resetting devices .. done Then it hangs so hard I have to power cycle it to get the system to notice me. The hang does not happen if the DVD/CD-RW drive is pulled from the system. Booting an old kernel (previous to this problem) and searching the logs, I see: Oct 7 12:46:24 tylendel kernel: atapci0: port 0x1860-0x186f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 31.1 on pci0 Oct 7 12:46:24 tylendel kernel: ata0: at 0x1f0 irq 14 on atapci0 Oct 7 12:46:24 tylendel kernel: ata0: [MPSAFE] Oct 7 12:46:24 tylendel kernel: ata1: at 0x170 irq 15 on atapci0 Oct 7 12:46:24 tylendel kernel: ata1: [MPSAFE] and Oct 7 12:46:24 tylendel kernel: GEOM: create disk ad0 dp=0xc5beb670 Oct 7 12:46:24 tylendel kernel: ad0: 38154MB [77520/16/63] at ata0-master UDMA100 Oct 7 12:46:24 tylendel kernel: acd0: CDRW at ata1-master UDMA33 I'd really appreciate any help that could be tossed my direction. thanks, nomad --- - Lee "nomad" Damon - \ play: [EMAIL PROTECTED]or castle!nomad \ work: [EMAIL PROTECTED] \ /\ Seneschal, Castle PAUS./ \ "Celebrate Diversity" /\ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: umass panic when connecting camera
On Tue, Oct 07, 2003 at 07:11:10PM +0100, Bruce M Simpson wrote: > On Tue, Oct 07, 2003 at 08:02:02PM +0200, John Hay wrote: > > Any comments from people a little more knowledgable in the umass/usb > > area? > > I don't know about USB specifically, but I thought timeout() et al were > to be deprecated in favour of callout*() ? Well I just wanted to get my device working again without changing the code too much, so I added an untimeout() for the existing timeout(). The usb code is also shared with the other *BSD groups. Looking at the rest of the usb files, I see that they do use usb_callout*(), so one can probably convert umass to it. The man page for (un)timeout and callout* is interesting because it does say that timeout() "is the old style and new code should use the callout_* functions" but a little later it also says "The functions callout_init(), callout_stop() and callout_reset() are low- level routines for clients who wish to allocate their own callout struc- tures." :-) John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Failed building XFree86-4-clients
On Tue, Oct 07, 2003 at 12:06:31PM -0700, James Satterfield wrote: > On a recent -current > FreeBSD bishop.uberduper.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Oct 6 > 15:12:45 PDT 2003 > I am unable to build XFree86-4-clients from ports. Here's the last little bits > from the build. > > macro "in" not recognized -- ignoring > making all in programs/bdftopcf... > cc -O -pipe -mcpu=pentiumpro -ansi -Dasm=__asm -Wall -Wpointer-arith -Wundef > -I/usr/ports/x11/XFree86-4-clients/work/xc/include/fonts > -I/usr/ports/x11/XFree86-4-clients/work/xc/lib/font/include > -I/usr/ports/x11/XFree86-4-clients/work/xc/lib/font/bitmap > -I/usr/ports/x11/XFree86-4-clients/work/xc > -I/usr/ports/x11/XFree86-4-clients/work/xc/exports/include > -I/usr/X11R6/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -c > bdftopcf.c > In file included from /usr/include/string.h:40, > from > /usr/ports/x11/XFree86-4-clients/work/xc/exports/include/X11/Xfuncs.h:49, > from > /usr/ports/x11/XFree86-4-clients/work/xc/lib/font/include/fontmisc.h:38, > from bdftopcf.c:34: > /usr/include/sys/cdefs.h:173:51: warning: "__STDC_VERSION__" is not defined > /usr/include/sys/cdefs.h:184:5: warning: "__STDC_VERSION__" is not defined > /usr/include/sys/cdefs.h:372:5: warning: "_POSIX_C_SOURCE" is not defined > /usr/include/sys/cdefs.h:378:5: warning: "_POSIX_C_SOURCE" is not defined > make: don't know how to make > /usr/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop > *** Error code 2 > > Any ideas? > > James. Well, I'm sure there's a *right* way to do this, but I got the installation to go through by copying the contents of /usr/ports/x11/XFree86-4-libraries/work/xc/exports/lib (which now that I look at it are links) to XFree86-4-clients/blah/blah... Good luck. Greg ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Failed building XFree86-4-clients
On a recent -current FreeBSD bishop.uberduper.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Oct 6 15:12:45 PDT 2003 I am unable to build XFree86-4-clients from ports. Here's the last little bits from the build. macro "in" not recognized -- ignoring making all in programs/bdftopcf... cc -O -pipe -mcpu=pentiumpro -ansi -Dasm=__asm -Wall -Wpointer-arith -Wundef -I/usr/ports/x11/XFree86-4-clients/work/xc/include/fonts -I/usr/ports/x11/XFree86-4-clients/work/xc/lib/font/include -I/usr/ports/x11/XFree86-4-clients/work/xc/lib/font/bitmap -I/usr/ports/x11/XFree86-4-clients/work/xc -I/usr/ports/x11/XFree86-4-clients/work/xc/exports/include -I/usr/X11R6/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -c bdftopcf.c In file included from /usr/include/string.h:40, from /usr/ports/x11/XFree86-4-clients/work/xc/exports/include/X11/Xfuncs.h:49, from /usr/ports/x11/XFree86-4-clients/work/xc/lib/font/include/fontmisc.h:38, from bdftopcf.c:34: /usr/include/sys/cdefs.h:173:51: warning: "__STDC_VERSION__" is not defined /usr/include/sys/cdefs.h:184:5: warning: "__STDC_VERSION__" is not defined /usr/include/sys/cdefs.h:372:5: warning: "_POSIX_C_SOURCE" is not defined /usr/include/sys/cdefs.h:378:5: warning: "_POSIX_C_SOURCE" is not defined make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop *** Error code 2 Any ideas? James. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: savecore: first and last dump headers disagree on /dev/ad0b
> Hello.
> -CURRENT as of yesterday can't save kernel dump:
>
> savecore: first and last dump headers disagree on /dev/ad0b
> savecore: unsaved dumps found but not saved
>
> Is this a known issue?
Yes.
I had the same problem on my development machine at the end of August and
ended up using the enclosed patch to get working dumps.
- Tor Egge
Index: sys/dev/ata/ata-all.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v
retrieving revision 1.187
diff -u -r1.187 ata-all.c
--- sys/dev/ata/ata-all.c 27 Aug 2003 15:27:56 - 1.187
+++ sys/dev/ata/ata-all.c 31 Aug 2003 22:31:33 -
@@ -109,9 +109,11 @@
ch->device[MASTER].channel = ch;
ch->device[MASTER].unit = ATA_MASTER;
ch->device[MASTER].mode = ATA_PIO;
+ch->device[MASTER].dumping = 0;
ch->device[SLAVE].channel = ch;
ch->device[SLAVE].unit = ATA_SLAVE;
ch->device[SLAVE].mode = ATA_PIO;
+ch->device[SLAVE].dumping = 0;
ch->dev = dev;
ch->state = ATA_IDLE;
bzero(&ch->queue_mtx, sizeof(struct mtx));
Index: sys/dev/ata/ata-all.h
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-all.h,v
retrieving revision 1.65
diff -u -r1.65 ata-all.h
--- sys/dev/ata/ata-all.h 25 Aug 2003 11:13:04 - 1.65
+++ sys/dev/ata/ata-all.h 31 Aug 2003 22:56:14 -
@@ -227,6 +227,7 @@
intcmd;/* last cmd executed */
intmode; /* transfermode */
+intdumping;/* panic dump in progress */
void (*setmode)(struct ata_device *atadev, int mode);
};
Index: sys/dev/ata/ata-disk.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v
retrieving revision 1.159
diff -u -r1.159 ata-disk.c
--- sys/dev/ata/ata-disk.c 25 Aug 2003 09:01:49 - 1.159
+++ sys/dev/ata/ata-disk.c 31 Aug 2003 23:18:40 -
@@ -336,6 +336,26 @@
if (!adp)
return ENXIO;
+/* Some chipsets must be configured for PIO before dump starts. */
+if (adp->device->dumping == 0) {
+ adp->device->dumping = 1;
+ adp->device->setmode(adp->device, ATA_PIO_MAX);
+}
+if (length == 0) {
+ int error = 0;
+ /* Commit dump to media */
+ if (adp->device->param != NULL &&
+ adp->device->param->support.command2 & ATA_SUPPORT_FLUSHCACHE) {
+ error = ata_controlcmd(adp->device, ATA_FLUSHCACHE, 0, 0, 0);
+ if (error != 0)
+ ata_prtdev(adp->device, "Flush cache failed\n");
+ else
+ ata_prtdev(adp->device, "Flush cache succeeded\n");
+ } else
+ ata_prtdev(adp->device, "Flush cache skipped\n");
+ return error;
+}
+
bzero(&request, sizeof(struct ata_request));
request.device = adp->device;
request.data = virtual;
@@ -352,13 +372,15 @@
if (adp->device->channel->hw.transaction(&request) == ATA_OP_FINISHED)
return EIO;
-while (request.bytecount > request.donecount) {
+while (adp->device->channel->running == &request) {
DELAY(20);
- adp->device->channel->running = &request;
adp->device->channel->hw.interrupt(adp->device->channel);
- adp->device->channel->running = NULL;
if (request.status & ATA_S_ERROR)
return EIO;
+}
+if (request.bytecount > request.donecount) {
+ printf("Short write?");
+ return EIO;
}
return 0;
}
Index: sys/dev/ata/ata-queue.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-queue.c,v
retrieving revision 1.4
diff -u -r1.4 ata-queue.c
--- sys/dev/ata/ata-queue.c 28 Aug 2003 08:22:53 - 1.4
+++ sys/dev/ata/ata-queue.c 31 Aug 2003 22:35:30 -
@@ -106,9 +106,36 @@
ata_controlcmd(struct ata_device *atadev, u_int8_t command, u_int16_t feature,
u_int64_t lba, u_int16_t count)
{
-struct ata_request *request = ata_alloc_request();
+struct ata_request *request;
int error = ENOMEM;
+/* Handle calls from addump */
+if (atadev->dumping) {
+ struct ata_request request2;
+ request = &request2;
+ bzero(request, sizeof(struct ata_request));
+ request->device = atadev;
+ request->u.ata.command = command;
+ request->u.ata.lba = lba;
+ request->u.ata.count = count;
+ request->u.ata.feature = feature;
+ request->flags = ATA_R_CONTROL;
+ request->timeout = 5;
+ if (atadev->channel->hw.transaction(request) ==
+ ATA_OP_CONTINUES) {
+ while (atadev->channel->running == request &&
+ (request->status & ATA_S_ERROR) == 0) {
+ DELAY(20);
+ atadev->channel->hw.interrupt(atadev->channel);
+
ATAng issues status report
Here is an updated status of ATAng for me. I periodically test it to see if any of the following problems go away. * Panic occurs after ATAFD fails to probe. Last event: 2003/10/6 I have no ATAFD device on my system and normally no messages are printed about it on boot. However, periodically ATAFD will print a bunch of messages on console about failing to probe. The machine works normally but at some point during use, it panics with a re-use of freed memory, last user was ATAFD. Most of the time the machine doesn't print anything about ATAFD and there is no panic but maybe 1/5 reboots it does. * Resume fails, hanging with drive light on. Last event: 2003/10/2 Appears to be a lost interrupt during reset. * Lost interrupt for ATA-SLAVE on reboot. Last event: 2003/10/7 I'm unsure if this is actually a problem but occasionally it prints a message right before rebooting about loosing an interrupt. I'll try to get more info. Device is Intel 82801CA/CAM ICH3 ATA100 controller. There are no slave devices, just one master hard drive on primary and one master DVD/CDRW on secondary. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: umass panic when connecting camera
On Tue, Oct 07, 2003 at 08:02:02PM +0200, John Hay wrote: > Any comments from people a little more knowledgable in the umass/usb > area? I don't know about USB specifically, but I thought timeout() et al were to be deprecated in favour of callout*() ? BMS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: umass panic when connecting camera
>
> I have decided to upgrade my home box from a March -current to the latest
> stuff and now when I connect my HP850 digital camera to the usb port, it
> panics the machine. I got a dump and according to the instruction pointer
> and kldstat, it must be inside the umass, but I think something confuse
> gdb a little because that doesn't show up in the backtrace or maybe it is
> just me not knowing how to convince gdb to tell me:
>
> ###
> ---
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x10
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xc0729c26
> stack pointer = 0x10:0xc6317cbc
> frame pointer = 0x10:0xc6317cd0
> 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 = 13 (swi8: tty:sio clock)
> trap number = 12
> panic: page fault
Ok, it seems that when plugging in a device, the contacts can have some
"noise" and you get a disconnect inbetween. If that happens before the
timeout() in umass, bad things can happen. I have added an untimeout()
and now everything seems ok. Patch at the end.
Any comments from people a little more knowledgable in the umass/usb
area?
John
--
John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED]
Index: umass.c
===
RCS file: /home/ncvs/src/sys/dev/usb/umass.c,v
retrieving revision 1.91
diff -u -r1.91 umass.c
--- umass.c 20 Sep 2003 08:18:16 - 1.91
+++ umass.c 7 Oct 2003 16:35:45 -
@@ -396,6 +396,7 @@
usbd_device_handle sc_udev;/* USB device */
struct cam_sim *umass_sim; /* SCSI Interface Module */
+ struct callout_handle rescanh;/* timeout handle */
unsigned char flags; /* various device flags */
# define UMASS_FLAGS_GONE 0x01/* devices is no more */
@@ -2165,7 +2166,7 @@
/* XXX This will bomb if the driver is unloaded between attach
* and execution of umass_cam_rescan.
*/
- timeout(umass_cam_rescan, sc, MS_TO_TICKS(200));
+ sc->rescanh = timeout(umass_cam_rescan, sc, MS_TO_TICKS(200));
}
return(0); /* always succesfull */
@@ -2179,6 +2180,7 @@
umass_cam_detach_sim(struct umass_softc *sc)
{
if (sc->umass_sim) {
+ untimeout(umass_cam_rescan, sc, sc->rescanh);
if (xpt_bus_deregister(cam_sim_path(sc->umass_sim)))
cam_sim_free(sc->umass_sim, /*free_devq*/TRUE);
else
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Screen blanking on suspend?
On Oct 07, "David Gilbert" wrote: > It would appear that the screen on my Dell D800 laptop will shut of > it's backlight when DPMS turns off the screen (with the binary driver > from nvidia). This is useful. I posted this weekend about the same thing, but your post reminds me that I only tried it while *not* running X Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: D-Link DWL-520+
On Tuesday 07 October 2003 03:10, Marcos Biscaysaqu wrote: > Hi there. > If you want a very stable Freebsd Access Point, use a PCMCIA card with > chipset prism II and freebsd 5.0 release > I 've got one working for 6 month with more than 40 customers (never > crash!!) if you want to use a PCI card try with a Netgear is prism > 2.5 (I testing one these now and looks fine but slower than PCMCIA prism > II) . Wow. What a stunning things :) PCMCIA is better than PCI... so i have to get pcmcia-adapter for my PC :) However, I'm planning to use 4-stable or 5-current (there are two boxes I'm running freebsd on). Is it very important to up(down)grade it to 5.0? Is 4-stable too bad fot Host AP? Or what about hardware AP and freebsd? Sorry for a lot of questions, I had never mess with wi-fi before. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Serial debug broken in recent -CURRENT?
On Tue, 30 Sep 2003, Sam Leffler wrote:
> It reliably locks up for me when you break into a running system; set a
> breakpoint; and then continue. Machine is UP+HTT. Haven't tried other
> machines.
This seems to be because rev.1.75 of db_interface.c disturbed some much
larger bugs related to the ones that it fixed. It takes miracles for
entering ddb to even sort of work in the SMP case. If multiple CPUs
call kdb_trap() concurrently, e.g., by all hitting the same breakpoint,
then after 1.75 they first race to stop each other. Before 1.75, they
raced to clobber each others registers before this. The race to stop
each other cannot be won since all the CPUs have interrupts disabled
so they cannot respond to IPIs. It doesn't help that stop_cpus is silent
about this. It spins silently forever if a CPU can't be stopped, unless
DIAGNOSTIC is configured in which case it gives the plain broken behaviour
of warning and returning after not waiting for long enough. But things
somehow worked better before 1.75. I don't know exactly why. 1.75 only
changes the timing a little, and I would have thought that it reduced the
races by giving the other CPUs less time to enter ddb. My tests mainly
used a breakpoint at ithread_schedule which is sure to be hit by multiple
CPUs quite often, but there wasn't enough interrupt activity for concurrent
entry to be the usual case. Debugging printfs affected the races a lot --
turning on VERBOSE_STOP_ON_CPU_BREAK mostly avoided the problem, but with
a syscons console it sometimes caused fatal traps in bcopy().
If one of multiple CPUs in kdb_trap() somehow stops the others, then the
others face different problems when they restart. They can't just return
because debugger traps are not restartable (by just returning). They can't
just proceed because the first CPU may changed the state in such a way as
to make proceeding in the normal way not work (e.g., it may have deleted
a breakpoint).
These problems are not correctly or completely fixed in:
%%%
Index: db_interface.c
===
RCS file: /home/ncvs/src/sys/i386/i386/db_interface.c,v
retrieving revision 1.75
diff -u -2 -r1.75 db_interface.c
--- db_interface.c 7 Sep 2003 13:43:01 - 1.75
+++ db_interface.c 7 Oct 2003 14:11:35 -
@@ -35,4 +35,5 @@
#include
#include
+#include
#include
#include
@@ -41,4 +42,5 @@
#include
#ifdef SMP
+#include
#include /** CPUSTOP_ON_DDBBREAK */
#endif
@@ -73,4 +75,31 @@
}
+/* XXX this is cloned from stop_cpus() since that function can hang. */
+static int
+attempt_to_stop_cpus(u_int map)
+{
+ int i;
+
+ if (!smp_started)
+ return 0;
+
+ CTR1(KTR_SMP, "attempt_to_stop_cpus(%x)", map);
+
+ /* send the stop IPI to all CPUs in map */
+ ipi_selected(map, IPI_STOP);
+
+ i = 0;
+ while ((atomic_load_acq_int(&stopped_cpus) & map) != map) {
+ /* spin */
+ i++;
+ if (i == 1) {
+ printf("timeout stopping cpus\n");
+ break;
+ }
+ }
+
+ return 1;
+}
+
/*
* kdb_trap - field a TRACE or BPT trap
@@ -81,4 +110,6 @@
u_int ef;
volatile int ddb_mode = !(boothowto & RB_GDB);
+ static u_int kdb_trap_lock = NOCPU;
+ static u_int output_lock;
/*
@@ -103,16 +134,48 @@
#ifdef SMP
+ if (atomic_cmpset_int(&kdb_trap_lock, NOCPU, PCPU_GET(cpuid)) == 0 &&
+ kdb_trap_lock != PCPU_GET(cpuid)) {
+ while (atomic_cmpset_int(&output_lock, 0, 1) == 0)
+ ;
+ db_printf(
+ "concurrent ddb entry: type %d trap, code=%x cpu=%d\n",
+ type, code, PCPU_GET(cpuid));
+ atomic_store_rel_int(&output_lock, 0);
+ if (type == T_BPTFLT)
+ regs->tf_eip--;
+ else {
+ while (atomic_cmpset_int(&output_lock, 0, 1) == 0)
+ ;
+ db_printf(
+"concurrent ddb entry on non-breakpoint: too hard to handle properly\n");
+ atomic_store_rel_int(&output_lock, 0);
+ }
+ while (atomic_load_acq_int(&kdb_trap_lock) != NOCPU)
+ ;
+ write_eflags(ef);
+ return (1);
+ }
+#endif
+
+#ifdef SMP
#ifdef CPUSTOP_ON_DDBBREAK
+#define VERBOSE_CPUSTOP_ON_DDBBREAK
#if defined(VERBOSE_CPUSTOP_ON_DDBBREAK)
+ while (atomic_cmpset_int(&output_lock, 0, 1) == 0)
+ ;
db_printf("\nCPU%d stopping CPUs: 0x%08x...", PCPU_GET(cpuid),
PCPU_GET(other_cpus));
+ atomic_store_rel_int(&output_lock, 0);
#endif /* VERBOSE_CPUSTOP_ON_DDBBREAK */
/* We stop all CPUs except ourselves (obviously) */
- stop_cpus(PCPU_GET(other_cpus));
+ attempt_to_stop_cpus(PCPU_GET(other_cpus));
#if
Screen blanking on suspend?
It would appear that the screen on my Dell D800 laptop will shut of it's backlight when DPMS turns off the screen (with the binary driver from nvidia). This is useful. However, the screen does not turn off on suspend (in other messages to this list I wrestle with the lack of S3 suspend, but not here). It would be "good" if I could figure out how to run 'xset dpms force off' on suspend, but this laptop is acpi-only. rc.suspend doesn't run. Should this be a devd thing? Would apmd work with the apm deviced that is emulated by the acpi code? Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Atmel AT76C503 USB 802.11b device driver
Hi folks, I've come up with a driver for the above mentioned devices. This particular chip is found in a whole load of 802.11b USB devices. My particular device is an SMC2662W-AR, but it should work for any device containing the above chip. Just fill in the product/vendor ids and let me know your results and i'll update my local copy accordingly. The driver is at http://stu.bash.sh/atwi-20031007.tar.gz. Extract the files from within /usr/src/sys and apply atwi.diff with patch -p0 < atwi.diff. Only 5-CURRENT is supported at this time, so you will need a fairly recent cvsup. If you are going to report problems, set sysctl hw.atwi.debug=2 first and include all output. Both infrastructure and adhoc modes should work, but infrastructure mode hasnt been tested this last week as I had to return the AP I had on loan. You are strongly advised to use this driver as a module as the usb code has issues with the device if you unplug and replug it while the module is loaded. I'm working on fixing this. Other than that it should work fine. Please do report any successes or failures. Enjoy! Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: KSE & MySQL & rc.d
On Tue, 7 Oct 2003, Alexander Motin wrote:
> Hi!
>
> I have P4 system with SMP kernel and HyperThreading enabled.
> I have one strange problem with mysql 4.1.0 when using KSE on 5.1-CURRENT.
> After building mysql server with libkse as thread library and adding its
> start script into /usr/local/etc/rc.d, system hangs on boot without any
> error message when mysql trying to start.
> If I trying to start mysql by hands after system completely boot then
> everything works just fine.
> If I add delay into mysql start script and run it in backgroud from rc.d
> - everything is fine
> If I build mysql without KSE it works fine.
I'm not sure, but try this patch; it duplicates what libc_r does.
--
Dan Eischen
Index: thread/thr_init.c
===
RCS file: /opt/FreeBSD/cvs/src/lib/libpthread/thread/thr_init.c,v
retrieving revision 1.60
diff -u -r1.60 thr_init.c
--- thread/thr_init.c 18 Aug 2003 03:58:29 - 1.60
+++ thread/thr_init.c 7 Oct 2003 13:30:54 -
@@ -251,6 +251,10 @@
PANIC("Can't set login to root");
if (__sys_ioctl(fd, TIOCSCTTY, (char *) NULL) == -1)
PANIC("Can't set controlling terminal");
+ if (__sys_dup2(fd, 0) == -1 ||
+ __sys_dup2(fd, 1) == -1 ||
+ __sys_dup2(fd, 2) == -1)
+ PANIC("Can't dup2");
}
/* Initialize pthread private data. */
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: LiVeCD Based on FBSD Current
On Tue, 7 Oct 2003 14:23:19 + "Sebastian Yepes F. [ESN]" <[EMAIL PROTECTED]> wrote: > Hi all. > > I have done a Mini-Hot-To on how to make a LiVeBSD CD it's really a > Mini-How-To because there is not much to do to make this work.. > I have been abel to do a LiVeBSD FW+PF and it's working realy good.. > and a mini distro with X and xfce4 and it to work ok.. There's FreeSBIE (www.freesbie.org) which is a much similar LiveCD, and it's a good project. Maybe you can give a look at its code and see if something you've worked on can be ported into it. You could also join the project and help adding new features and new ideas. > What well be really nice is to have a 'linux like cloop' on BSD so we > can compress the CD.. At the moment I think that using a DVD would be much easier. Their price is continuosly decreasing. Greetings -- Stucchi Massimiliano | Gruppo Utenti FreeBSD Italia WillyStudios.com | http://www.gufi.org [EMAIL PROTECTED] | [EMAIL PROTECTED] "People who make no mistakes do not usually make anything" pgp0.pgp Description: PGP signature
LiVeCD Based on FBSD Current
Hi all. I have done a Mini-Hot-To on how to make a LiVeBSD CD it's really a Mini-How-To because there is not much to do to make this work.. I have been abel to do a LiVeBSD FW+PF and it's working realy good.. and a mini distro with X and xfce4 and it to work ok.. What well be really nice is to have a 'linux like cloop' on BSD so we can compress the CD.. http://www.x123.info [Coding -> ViewCVS -> LiVeBSD] -- /* FingerPrint: 5BF1 58B1 DE75 CBE3 6044 7098 1246 1EF6 9E78 041C */ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ? warning used static ldt allocation
Pau Rodriguez wrote: > #dmesg|tail -n 2 > Warning: pid 474 used static ldt allocation. > See the i386_set_ldt man page for more info > > What does it means? > > It was apearring for aprox. 15days. > > What I have to do? > > Maybe it was asked before... Could anybody refetch that message or answer? :( The program you are running is asking for a specific LDT entry, and this usage is deprecated, to avoid multiple library instances requesting the same LDT in the same program. The program should be recompiled to use a start_sel of LDT_AUTO_ALLOC, which will cause it to be dynamically allocated, which will avoid any potential conflict between libraries and/or your application. This was done a while ago, and was discussed on both the -current and -arch mailing lists; if you are going to run -current, you should probably subscribe to the -current mailing list so you see these things when they happen, and they don't suprise you. More information is available in the man page references on 5.1-current on the FreeBSD.org web site (Documentation/Manual pages) or in the man page on the system having the problem. The man page should probably be updated to deprecate non-automatic allocation specifically, since it doesn't appear to say anything useful about it at present (and your console message specifically references the non-existent deprecation in the man page). -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Debugging CURRENT kernels using remote gdb on STABLE does not work ?
В вт, 07.10.2003, в 04:24, Kris Kennaway пишет: > > Debugging CURRENT kernels using remote gdb on STABLE does not work ? > > That's probably to be expected - trying to debug a 5.x crashdump with > 4.x's gdb also doesn't work, because gdb needs to know details of the > kernel which are not the same between the two versions. As I understand - solution is port of gdb52 with FreeBSD kernel debugging hacks ? But we have no such port now. > Kris -- Vladimir B. Grebenschikov <[EMAIL PROTECTED]> SWsoft Inc. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAng doesn't boot on my notebook - panic
В пн, 06.10.2003, в 22:48, Vladimir B. Grebenschikov пишет:
> Soren, please help.
>
> I can't boot kernel after ATAng. It founds one extra ATA device
> (I have no ata1-slave attached) and then panics.
>
> All details in PR kern/57156.
I have workarounded problem by disabling slave ATA devices
(I have no slaves so it is acceptable for me):
RCS file: /ext/ncvs/src/sys/dev/ata/ata-all.c,v
retrieving revision 1.190
diff -u -r1.190 ata-all.c
--- sys/dev/ata/ata-all.c 27 Sep 2003 12:00:58 - 1.190
+++ sys/dev/ata/ata-all.c 6 Oct 2003 19:00:14 -
@@ -577,11 +577,12 @@
ata_identify_devices(struct ata_channel *ch)
{
if (ch->devices & ATA_ATA_SLAVE) {
- if (ata_getparam(&ch->device[SLAVE], ATA_ATA_IDENTIFY))
+/* if (ata_getparam(&ch->device[SLAVE], ATA_ATA_IDENTIFY)) */
ch->devices &= ~ATA_ATA_SLAVE;
#ifdef DEV_ATADISK
- else
- ch->device[SLAVE].attach = ad_attach;
+/* else
+ ch->device[SLAVE].attach = ad_attach;
+*/
#endif
}
if (ch->devices & ATA_ATAPI_SLAVE) {
> In short:
>
> ad0: setting UDMA33 on Intel PIIX4 chip
> GEOM: create disk ad0 dp=0xc1d00970
> ad0: ATA-5 disk at ata0-master
> ad0: 38154MB (78140160 sectors), 77520 C, 16 H, 63 S, 512 B
> ad0: 16 secs/int, 1 depth queue, UDMA33
> GEOM: new disk ad0
> [0] f:00 typ:6 s(CHS):0/1/1 e(CHS):969/239/63 s:63 l:14666337
> [1] f:00 typ:160 s(CHS):970/0/1 e(CHS):996/239/63 s:14666400 l:408240
> [2] f:80 typ:165 s(CHS):997/0/1 e(CHS):1023/239/63 s:15074640 l:41942880
> [3] f:00 typ:165 s(CHS):1023/0/1 e(CHS):1023/239/63 s:57017520
> l:21122640
> GEOM: Configure ad0s1, start 32256 length 7509164544 end 7509196799
> GEOM: Configure ad0s2, start 7509196800 length 209018880 end 7718215679
> GEOM: Configure ad0s3, start 7718215680 length 21474754560 end
> 9192970239
> GEOM: Configure ad0s4, start 29192970240 length 10814791680 end
> 40007761919
> GEOM: Configure ad0s3a, start 0 length 134217728 end 134217727
> GEOM: Configure ad0s3b, start 134217728 length 268435456 end 402653183
> GEOM: Configure ad0s3c, start 0 length 21474754560 end 21474754559
> GEOM: Configure ad0s3e, start 402653184 length 6442450944 end 6845104127
> GEOM: Configure ad0s3f, start 6845104128 length 14629650432 end
> 1474754559
> GEOM: Configure ad0s4c, start 0 length 10814791680 end 10814791679
> GEOM: Configure ad0s4e, start 0 length 134217728 end 134217727
> GEOM: Configure ad0s4f, start 134217728 length 8915517440 end 9049735167
> ata1-slave: pio=0x08 wdma=0x udma=0x cable=40pin
> ata1-master: pio=0x09 wdma=0x udma=0x cable=40pin
> ad1: FAILURE - SETFEATURES status=51 error=4
> ad1: FAILURE - SETFEATURES status=51 error=4
> ad1: FAILURE - SETFEATURES status=51 error=4
> ad1: FAILURE setting PIO1 on Intel PIIX4 chip
> GEOM: create disk ad1 dp=0xc1d4b770
> ad1: ATA-0 disk at ata1-master
> ad1: 3MB (7904 sectors), 247 C, 2 H, 16 S, 512 B
> ad1: 1 secs/int, 1 depth queue, BIOSPIO
> GEOM: new disk ad1
> ad2: WARNING - SETFEATURES recovered from missing interrupt
> [0] f:80 typ:1 s(CHS):0/1/12 e(CHS):245/1/16 s:27 l:7845
> [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
> [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
> [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
> GEOM: Configure ad1s1, start 13824 length 4016640 end 4030463
> ad2: WARNING - SETFEATURES recovered from missing interrupt
> ad2: WARNING - SETFEATURES recovered from missing interrupt
> ad2: setting PIO0 on Intel PIIX4 chip
> GEOM: create disk ad2 dp=0xc1d4b970
> ad2: ATA-0 disk at ata1-slave
>
> Fatal trap 18: integer divide fault while in kernel mode
> instruction pointer = 0x8:0xc03fa088
> stack pointer = 0x10:0xc05c5c54
> frame pointer = 0x10:0xc05c5cd0
> code segment= base 0x0, limit 0xf, type 0x1b
> = DPL 0, pres 1, def32 1, gran 1
> processor eflags= interrupt enabled, resume, IOPL = 0
> current process = 0 (swapper)
> kernel: type 18 trap, code=0
> Stopped at __qdivrem+0x38: divl%ecx,%eax
> db> tra
> __qdivrem(0,0,0,0,0) at __qdivrem+0x38
> __udivdi3(0,0,0,0,0) at __udivdi3+0x2e
> ad_attach(c1c712d4,1,c0ac6c50,c0445310,c05c5d74) at ad_attach+0x4aa
> ata_boot_attach(0,c02392d6,c046392c,0,c0445310) at ata_boot_attach+0x6f
> run_interrupt_driven_config_hooks(0,0,c0ac46f8,c0ac46f8,5c2c00) at
> run_interrupt_driven_config_hooks+0x2b
> mi_startup() at mi_startup+0xa1
> begin() at begin+0x2c
> db>
>
> Any solution or workaround ?
--
Vladimir B. Grebenschikov <[EMAIL PROTECTED]>
SWsoft Inc.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
calcru: negative time of...
I guess this probably came up before, but I could find any helpful info in the list's archive... I am getting a lot of "calcru: negative time of...". I am on 5.1 RELEASE. I have tried troubleshooting hints but without luck. "sysctl -w kern.timecounter.method=1" gives me "sysctl: unknown oid 'kern.timecounter.method'" Could somebody point me to the right direction? Please! Thanks a lot. -Roman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
KSE & MySQL & rc.d
Hi! I have P4 system with SMP kernel and HyperThreading enabled. I have one strange problem with mysql 4.1.0 when using KSE on 5.1-CURRENT. After building mysql server with libkse as thread library and adding its start script into /usr/local/etc/rc.d, system hangs on boot without any error message when mysql trying to start. If I trying to start mysql by hands after system completely boot then everything works just fine. If I add delay into mysql start script and run it in backgroud from rc.d - everything is fine If I build mysql without KSE it works fine. -- Alexander Motin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cannot create partition entries for /dev/ad3
On Tuesday 07 October 2003 18:01, ecsd wrote:
> I have a WintTV card that should be /dev/bktr0. I have tried using "devfs"
> to remedy this:
>
> host[157] # fxtv
> open("/dev/bktr0") failed: No such file or directory
>
> but I cannot see what to do, precisely and in order, to make the device
> exist.
I think you have a pretty fundamental misconception about /dev and devfs.
Makeing devices in /dev doesn't create those devices, or install their
drivers.
In reality you need both the /dev entry AND the driver to be able to access a
device. What devfs does is just make it so that you don't have to bother
changing /dev to reflect newely loaded drivers - the drivers tell devfs to
create the device nodes to reflect what hardware they have actually found.
> I can't tell if use of devfs makes permanent changes to a system definition
> file so that changes are retained across reboots. I don't see a reference
> to a system file I would modify to make devices exist. The man page for
> devfs does not provide an example of creating a device - or if it does, it
> doesn't explain what /other/ commands are needed in tandem to make the
> device usable (extant.) If devfs will create devices to correspond to
> devices defined in the kernel config file, then where is the bktr device?
You don't WANT to create device nodes in devfs, that's like the whole [user
visible] point!
kldload bktr might help you out.
If you have it, or it's in the kernel read dmesg, if THAT doesn't help and the
device used to work, email a list, or the device maintainer.
The only reason most people will ever touch /dev is to either make devices
(hence no longer necessary with devfs), or change permissions. The later is
more difficult with devfs, but IMHO the tradeoff is worthwhile.
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cannot create partition entries for /dev/ad3
In message <[EMAIL PROTECTED]>, ecsd writes: >MAKEDEV was the cheese since year zero. [...] I suggest you stick with 4-stable until you have caught up with the changes and the documentation. -- 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cannot create partition entries for /dev/ad3
Poul-Henning Kamp writes:
In message <[EMAIL PROTECTED]>, ecsd writes:
with MAKEDEV gone, the mystery is how to use devfs.
In /dev I have ad3, but I cannot "disklabel -e /dev/ad3s1d",
nor can I "disklabel -e /dev/ad3", and I can't determine
what minor device numbers to assign for mknod to create
the partition entries.
Try
bsdlabel -w /dev/ad3
bsdlabel does not exist on my system as a preinstalled script or program,
or as a port:
FreeBSD 5.0-RELEASE #2
MAKEDEV was the cheese since year zero. Removing it as of 5.0 invalidates everything
written about creating devices in everything in print and in almost all of the online
documentation on freebsd.org. Documentation for devfs is nearly nonexistent. The man
page suggests that now I will be learning a language (!) for specifying what devices
to create, based in some hazy way on the kernel config file. Something I've read
suggests that "devices will be created as needed" using devfs.
I looked for any discussion of devfs in the Release Notes for 5.0 and 5.1 and found
that it was only barely mentioned.
With such a major change - literally invalidating every How-To written to date about
devices - where is a discursive description of the workings of devfs? Might it be a
good
idea to provide a stub /dev/MAKEDEV, so that such a thing would exist, for people still
buying FreeBSD books off the shelf today? That script could either just say "sorry,
MAKEDEV is replaced by devfs(8)", or it could use devfs to emulate what MAKEDEV did,
which I think is the preferred option to support the majority of users who'll be happy
when they can use the parlor table book of bsd to set up their home PC as a DVD player.
I have a WintTV card that should be /dev/bktr0. I have tried using "devfs" to remedy this:
host[157] # fxtv
open("/dev/bktr0") failed: No such file or directory
but I cannot see what to do, precisely and in order, to make the device exist.
I can't tell if use of devfs makes permanent changes to a system definition file
so that changes are retained across reboots. I don't see a reference to a system
file I would modify to make devices exist. The man page for devfs does not provide
an example of creating a device - or if it does, it doesn't explain what /other/
commands are needed in tandem to make the device usable (extant.) If devfs will create
devices to correspond to devices defined in the kernel config file, then where is the
bktr device?
Is there any more comprehensive documentation for the DEVFS and devfs and usage
to replace MAKEDEV? As is, I have devices I need to access but can't. Have I left
something out of the kernel gen process? Is 5.0 screwed? ARGH!!
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
