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=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 267583488 (255 MB) avail memory = 251961344 (240 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: INTEL S875PWP1 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: CPU on acpi0 acpi_cpu1: CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus 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: Intel 82875P host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 3.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib2: slot 1 INTA is routed to irq 10 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.16 port 0xac00-0xac1f mem 0xfc9e-0xfc9f irq 10 at device 1.0 on pci2 em0: Speed:N/A Duplex:N/A uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0xcc00-0xcc1f irq 5 at device 29.0 on pci0 usb0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0xd000-0xd01f irq 10 at device 29.1 on pci0 usb1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0xd400-0xd41f irq 10 at device 29.2 on pci0 usb2: Intel 82801EB (ICH5) USB controller USB-C 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: Intel 82801EB (ICH5) USB controller USB-D port 0xd800-0xd81f irq 5 at device 29.3 on pci0 usb3: Intel 82801EB (ICH5) USB controller USB-D 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: serial bus, USB at device 29.7 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 30.0 on pci0 pci3: ACPI PCI bus 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: Adaptec 29160N Ultra160 SCSI adapter 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: display, VGA at device 6.0 (no driver attached) fxp0: Intel 82801BA (D865) Pro/100 VE Ethernet port 0xbc00-0xbc3f mem 0xfeafd000-0xfeafdfff irq 11 at device 8.0 on pci3 fxp0: Ethernet address 00:07:e9:45:69:3d miibus0: MII bus on fxp0 inphy0: i82562ET 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller 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: mass storage, RAID at device 31.2 (no driver attached) pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_button0: Sleep Button on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold
Re: panic: mutex vm object not owned at ../../../vm/vm_page.c:762
On Mon, Oct 06, 2003 at 02:30:30AM -0700, Kris Kennaway wrote:
I got this upon attempting to burn a CD with cdrecord on my
freshly-updated current machine:
panic: mutex vm object not owned at ../../../vm/vm_page.c:762
This should now be fixed.
Alan
syncing disks, buffers remaining... 3842 3842 3842 3842 3842 3842 3842 3842 3842
3842 3842 3842 3842 3842 3842 3842 3842 3842 3842 3842
giving up on 218 buffers
Uptime: 16m51s
Dumping 511 MB
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352
368 384 400 416 432 448 464 480 496
---
Reading symbols from /boot/kernel/nvidia.ko...done.
Loaded symbols for /boot/kernel/nvidia.ko
#0 doadump () at ../../../kern/kern_shutdown.c:240
240 dumping++;
(kgdb) bt
#0 doadump () at ../../../kern/kern_shutdown.c:240
#1 0xc054a32d in boot (howto=256) at ../../../kern/kern_shutdown.c:372
#2 0xc054a6b7 in panic () at ../../../kern/kern_shutdown.c:550
#3 0xc05410cc in _mtx_assert (m=0xc4ea4c24, what=0, file=0xc06f8518
../../../vm/vm_page.c, line=762)
at ../../../kern/kern_mutex.c:855
#4 0xc065c03c in vm_page_alloc (object=0xc4ea4c24, pindex=0, req=0) at
../../../vm/vm_page.c:762
#5 0xc064e68b in vm_fault_copy_entry (dst_map=0xc4f527e0, src_map=0xc4d653f0,
dst_entry=0xc537fd5c,
src_entry=0x0) at ../../../vm/vm_fault.c:1167
#6 0xc0654e81 in vm_map_copy_entry (src_map=0xc4d653f0, dst_map=0xc4f527e0,
src_entry=0xc537f834,
dst_entry=0xc537fd5c) at ../../../vm/vm_map.c:2379
#7 0xc06551c6 in vmspace_fork (vm1=0xc4d653f0) at ../../../vm/vm_map.c:2494
#8 0xc064fcce in vm_forkproc (td=0xc4ebe130, p2=0xc53855ac, td2=0xc4ebeab0,
flags=20)
at ../../../vm/vm_glue.c:624
#9 0xc05353f5 in fork1 (td=0xc4ebe130, flags=20, pages=0, procp=0xd9d38cd8) at
../../../kern/kern_fork.c:654
#10 0xc053441b in fork (td=0xc4ebe130, uap=0xd9d38d10) at
../../../kern/kern_fork.c:102
#11 0xc06a4d93 in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 4096, tf_esi = 65536, tf_ebp =
-1077948008, tf_isp = -640447116, tf_ebx = 64, tf_edx = 1307, tf_ecx = 672806144,
tf_eax = 2, tf_trapno = 0, tf_err = 2, tf_eip = 672202079, tf_cs = 31, tf_eflags =
582, tf_esp = -1077948052, tf_ss = 47}) at ../../../i386/i386/trap.c:1006
#12 0xc069505d in Xint0x80_syscall () at {standard input}:144
---Can't read userspace from dump, or kernel process---
(kgdb)
The annoying thing was that something apparently overwrote the
partition table on the disk holding the swap partition - I had to
recreate it by hand before I could bring the system back up, although
it then came back up without further problems.
Kris
___
[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
, 07.10.2003, 23:26, Soren Schmidt : It seems Vladimir B. Grebenschikov wrote: Any solution or workaround ? Try this patch please: diff -u -r1.191 ata-all.c Does not help, another panic in ad_attach: ... GEOM: create disk ad1 dp=0xc2358a70 ad1: MEMORYSTICK 4M 8K/SONY1.00 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 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x6 fault code = supervisor read, page not present instruction pointer = 0x8:0xc047d801 stack pointer = 0x10:0xc0c21cf4 frame pointer = 0x10:0xc0c21d3c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) kernel: type 12 trap, code=0 Stopped at ad_attach+0x61: movzbl 0x6(%edi),%ecx db tra ad_attach(c227d2d4,1,c1122c50,c074a990,c0c21d74) at ad_attach+0x61 ata_boot_attach(0,c0539736,c0768fec,0,c074a990) at ata_boot_attach+0x6f run_interrupt_driven_config_hooks(0,0,c1120708,c1120708,c1ec00) at run_interrupt_driven_config_hooks+0x2b mi_startup() at mi_startup+0xa1 begin() at begin+0x2c db full boot -v: OK boot -v /boot/kernel.soren/acpi.ko text=0x3b43c data=0x16cc+0xee0 syms=[0x4+0x6480+0x4+0x7fb5] SMAP type=01 base= len=0009f800 SMAP type=02 base=0009f800 len=0800 SMAP type=02 base=000e7800 len=00018800 SMAP type=01 base=0010 len=0bef SMAP type=03 base=0bff len=f800 SMAP type=04 base=0bfff800 len=0800 SMAP type=02 base=fffe7800 len=00018800 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 #11: Wed Oct 8 03:00:25 MSD 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VBOOK Preloaded elf kernel /boot/kernel.soren/kernel at 0xc08a8000. Preloaded elf module /boot/kernel.soren/ums.ko at 0xc08a8208. Preloaded elf module /boot/kernel.soren/usb.ko at 0xc08a82b8. Preloaded elf module /boot/kernel.soren/ukbd.ko at 0xc08a8368. Preloaded elf module /boot/kernel.soren/snd_neomagic.ko at 0xc08a8418. Preloaded elf module /boot/kernel.soren/snd_pcm.ko at 0xc08a84d0. Preloaded elf module /boot/kernel.soren/acpi.ko at 0xc08a8584. Calibrating clock(s) ... i8254 clock: 1193111 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 331580921 Hz CPU: Pentium II/Pentium II Xeon/Celeron (331.58-MHz 686-class CPU) Origin = GenuineIntel Id = 0x66a Stepping = 10 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 201261056 (191 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c26000 - 0x0bc69fff, 184827904 bytes (45124 pages) avail memory = 185966592 (177 MB) bios32: Found BIOS32 Service Directory header at 0xc00f6c50 bios32: Entry = 0xfd7c0 (c00fd7c0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd7c0+0x214 pnpbios: Found PnP BIOS data at 0xc00f6c80 pnpbios: Entry = f:b5d4 Rev = 1.0 Other BIOS signatures found: random: entropy source mem: memory I/O Pentium Pro MTRR support enabled null: null device, zero device npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: SONY Z0 on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x80003b54 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71928086) pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00fdf50 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded01A 0x60 9 embedded01B 0x61 9 embedded01C 0x62 9 embedded01D 0x63 9 embedded07D 0x63 9 embedded08A 0x60 9 embedded08B 0x61 9 embedded09A 0x62 9 embedded0 10A 0x61 9 embedded0 11A 0x60 9 embedded06A 0x60 9 AcpiOsDerivePciId: bus 0 dev 7 func 2 AcpiOsDerivePciId: bus 0 dev 10 func 0 AcpiOsDerivePciId: bus 0 dev 7 func 0 acpi0: Power Button (fixed) ACPI timer looks BAD min = 2, max = 8, width = 6 ACPI timer looks BAD min = 2, max = 8, width = 6 ACPI timer looks BAD min = 2, max = 8, width = 6 ACPI timer looks BAD min = 3, max = 16777202, width = 16777199 ACPI timer looks BAD min = 3, max = 8, width = 5 ACPI timer looks BAD min = 3, max = 9, width = 6 ACPI timer looks BAD min = 2, max = 8, width = 6 ACPI timer looks BAD min = 0, max = 8, width = 8 ACPI timer looks BAD
Re: panic: mutex vm object not owned at ../../../vm/vm_page.c:762
On Wed, Oct 08, 2003 at 02:16:52AM -0500, Alan Cox wrote: On Mon, Oct 06, 2003 at 02:30:30AM -0700, Kris Kennaway wrote: I got this upon attempting to burn a CD with cdrecord on my freshly-updated current machine: panic: mutex vm object not owned at ../../../vm/vm_page.c:762 This should now be fixed. Great, thanks. Now I just have to summon up the courage to try Tor's patch for fixing ATA dumping and test both hypotheses :-) Kris pgp0.pgp Description: PGP signature
Re: ATAng doesn't boot on my notebook - panic
It seems Vladimir B. Grebenschikov wrote:
Does not help, another panic in ad_attach:
ARGH, try this instead:
diff -u -r1.191 ata-all.c
--- ata-all.c 7 Oct 2003 13:44:15 - 1.191
+++ ata-all.c 8 Oct 2003 08:03:09 -
@@ -35,6 +35,7 @@
#include sys/ata.h
#include sys/kernel.h
#include sys/endian.h
+#include sys/ctype.h
#include sys/conf.h
#include sys/bus.h
#include sys/bio.h
@@ -555,6 +556,8 @@
}
ata_free_request(request);
}
+ if (!isalpha(atacap-model[0]) || !isalpha(atacap-model[1]))
+ error = ENXIO;
if (error) {
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]
no partition entries for /dev/ad3
Here are the contents of my /dev. As you can see, there are no entries for the partitions of ad3. My 5.0 system has no bsdlabel command. Can anyone tell me how I can coax the ad3s1* entries into existence? ./ ad2s1c dspW0.1 pci stdin@ ttypg ../ ad2s1d dspr0.0 ppi0 stdout@ ttyph ad0 ad2s1e fd/ psm0 sysmousettypi ad0s1 ad2s1f geom.ctlptyp0 ttyd0 ttyv0 ad0s1a ad2s1g io ptyp1 ttyd1 ttyv1 ad0s1b ad3 ipauth ptyp2 ttyid0 ttyv2 ad0s1c agpgart ipl ptyp3 ttyid1 ttyv3 ad0s1d ata ipnat ptyp4 ttyld0 ttyv4 ad0s1e audio0.0ipstate ptyp5 ttyld1 ttyv5 ad0s1f audio0.1kbd0ptyp6 ttyp0 ttyv6 ad0s1g bpf0klogptyp7 ttyp1 ttyv7 ad1 bpsm0 kmemptyp8 ttyp2 ttyv8 ad1cconsole log@ptyp9 ttyp3 ttyv9 ad1s1 consolectl lpt0ptypa ttyp4 ttyva ad1s1a cttylpt0.ctlptypb ttyp5 ttyvb ad1s1b cuaa0 mdctl ptypc ttyp6 ttyvc ad1s1c cuaa1 mem ptypd ttyp7 ttyvd ad1s1e cuaia0 mixer0 ptype ttyp8 ttyve ad1s1f cuaia1 net/ptypf ttyp9 ttyvf ad1s1g cuala0 net1@ ptypg ttypa urandom@ ad1s1h cuala1 net2@ ptyph ttypb vga@ ad2 devctl net3@ ptypi ttypc xpt0 ad2s1 dsp0.0 net4@ random ttypd zero ad2s1a dsp0.1 network sndstat ttype ad2s1b dspW0.0 nullstderr@ ttypf ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no partition entries for /dev/ad3
On Wed, 8 Oct 2003, ecsd wrote: eHere are the contents of my /dev. As you can see, there are no entries efor the epartitions of ad3. My 5.0 system has no bsdlabel command. Can anyone etell me how I can coax the ad3s1* entries into existence? You probably need to fdisk(8) your disk first. The slices should then appear automagically. Then you can disklabel(8) the slices which will bring the partitions into life. Disklabel and bsdlabel are the same on i386. harti e e./ ad2s1c dspW0.1 pci estdin@ ttypg e../ ad2s1d dspr0.0 ppi0 estdout@ ttyph ead0 ad2s1e fd/ psm0 esysmousettypi ead0s1 ad2s1f geom.ctlptyp0 ettyd0 ttyv0 ead0s1a ad2s1g io ptyp1 ettyd1 ttyv1 ead0s1b ad3 ipauth ptyp2 ettyid0 ttyv2 ead0s1c agpgart ipl ptyp3 ettyid1 ttyv3 ead0s1d ata ipnat ptyp4 ettyld0 ttyv4 ead0s1e audio0.0ipstate ptyp5 ettyld1 ttyv5 ead0s1f audio0.1kbd0ptyp6 ettyp0 ttyv6 ead0s1g bpf0klogptyp7 ettyp1 ttyv7 ead1 bpsm0 kmemptyp8 ettyp2 ttyv8 ead1cconsole log@ptyp9 ettyp3 ttyv9 ead1s1 consolectl lpt0ptypa ettyp4 ttyva ead1s1a cttylpt0.ctlptypb ettyp5 ttyvb ead1s1b cuaa0 mdctl ptypc ettyp6 ttyvc ead1s1c cuaa1 mem ptypd ettyp7 ttyvd ead1s1e cuaia0 mixer0 ptype ettyp8 ttyve ead1s1f cuaia1 net/ptypf ettyp9 ttyvf ead1s1g cuala0 net1@ ptypg ettypa urandom@ ead1s1h cuala1 net2@ ptyph ettypb vga@ ead2 devctl net3@ ptypi ettypc xpt0 ead2s1 dsp0.0 net4@ random ettypd zero ead2s1a dsp0.1 network sndstat ttype ead2s1b dspW0.0 nullstderr@ ttypf e e e___ e[EMAIL PROTECTED] mailing list ehttp://lists.freebsd.org/mailman/listinfo/freebsd-current eTo unsubscribe, send any mail to [EMAIL PROTECTED] e -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private [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: no partition entries for /dev/ad3
I had already been able to go so far as to disklabel -w -r ad3 auto. After doing this on a 4.X system I would then disklabel -e /dev/ad3s1c, but /dev/ad3s1c does not exist, so I am stuck. Maybe there is a rescan devices command? fdisk thinks it has no work to do: *** Working on device /dev/ad3 *** [...] Information from DOS bootblock is: 1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 39102273 (19092 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 15/ sector 63 2: UNUSED 3: UNUSED 4: UNUSED Harti Brandt wrote: On Wed, 8 Oct 2003, ecsd wrote: eHere are the contents of my /dev. As you can see, there are no entries efor the epartitions of ad3. My 5.0 system has no bsdlabel command. Can anyone etell me how I can coax the ad3s1* entries into existence? You probably need to fdisk(8) your disk first. The slices should then appear automagically. Then you can disklabel(8) the slices which will bring the partitions into life. Disklabel and bsdlabel are the same on i386. harti ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no partition entries for /dev/ad3
On Wed, 8 Oct 2003, ecsd wrote: eI had already been able to go so far as to disklabel -w -r ad3 auto. eAfter doing this eon a 4.X system I would then disklabel -e /dev/ad3s1c, but /dev/ad3s1c edoes enot exist, so I am stuck. Maybe there is a rescan devices command? e efdisk thinks it has no work to do: e e*** Working on device /dev/ad3 *** e[...] eInformation from DOS bootblock is: e1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) estart 63, size 39102273 (19092 Meg), flag 80 (active) ebeg: cyl 0/ head 1/ sector 1; eend: cyl 1023/ head 15/ sector 63 e2: UNUSED e3: UNUSED e4: UNUSED In that case you should have a /dev/ad3s1. Have you? harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private [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: savecore: first and last dump headers disagree on /dev/ad0b
On 2003/10/07 18:11:30, 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. You could optionally set hw.ata.ata_dma=0 in loader.conf to disable UDMA rather than apply the patch. Yes, setting hw.ata.ata_dma=0 allowed me to dump a usable core file. Thanks. -- YONETANI Tomokazu / Ergo-Brains Inc. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proliant 1600R Install Failure (ida + SMPng to blame?)
On Tue, 7 Oct 2003, Edward Aronyk wrote: Booting off the 5.1 boot floppies gives a page fault about 15 seconds after the mfsroot floppy finishes loading. Boot off of a -CURRENT snapshot; 5.1 shipped with a broken IDA driver. -- | 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 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no partition entries for /dev/ad3
Harti Brandt wrote: On Wed, 8 Oct 2003, ecsd wrote: eI had already been able to go so far as to disklabel -w -r ad3 auto. eAfter doing this on a 4.X system I would then disklabel -e /dev/ad3s1c ebut /dev/ad3s1c does not exist, so I am stuck. eMaybe there is a rescan devices command? e fdisk thinks it has no work to do. In that case you should have a /dev/ad3s1. Have you? harti The chronology is that I booted the system, did the disklabel -w -r ad3 auto, turned around to disklabel -e /dev/ad3s1c (as I would normally do), and was told that /dev/ad3s1c did not exist. Then I wrote in here asking for help. ad3s1c does not exist. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no partition entries for /dev/ad3
On Wed, 8 Oct 2003, ecsd wrote: eHarti Brandt wrote: eOn Wed, 8 Oct 2003, ecsd wrote: eeI had already been able to go so far as to disklabel -w -r ad3 auto. eeAfter doing this on a 4.X system I would then disklabel -e /dev/ad3s1c eebut /dev/ad3s1c does not exist, so I am stuck. eeMaybe there is a rescan devices command? e ee fdisk thinks it has no work to do. e eIn that case you should have a /dev/ad3s1. Have you? eharti e eThe chronology is that I booted the system, did the disklabel -w -r ad3 eauto, eturned around to disklabel -e /dev/ad3s1c (as I would normally do), and ewas told that /dev/ad3s1c did not exist. Then I wrote in here asking for ehelp. ead3s1c does not exist. If I understand correctly disklabel -e ad3 auto will create you partitions without creating slices. You should get /dev/ad3c and this will cover the entire disk (though I don't know if this is really supported). Normally you should put slices onto your disk and disklabel the slices. Given that you have a correct fdisk label you should have the slice entries /dev/ad3s[1-4]. Then you can disklabel the slices: 'disklabel -e /dev/ad3s1 auto'. ad3s1c of course does not exist if you don't have labeled the slice. You must label the slice (da3s1), not a partition thereof (da3s1c). harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[current tinderbox] failure on ia64/ia64
TB --- 2003-10-08 09:25:40 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2003-10-08 09:25:40 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-10-08 09:29:09 - building world TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64/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/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything.. TB --- 2003-10-08 10:33:01 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Wed Oct 8 10:33:01 GMT 2003 Kernel build for GENERIC completed on Wed Oct 8 10:48:47 GMT 2003 TB --- 2003-10-08 10:48:47 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64/src/sys/ia64/conf TB --- /usr/bin/make -B LINT TB --- 2003-10-08 10:48:47 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64/src TB --- /usr/bin/make buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Oct 8 10:48:47 GMT 2003 [...] cc -c -O -pipe -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/ia64/ia64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath/freebsd -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ia64/libuwx/src -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -mno-sdata -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/mca.c cc -c -O -pipe -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/ia64/ia64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath/freebsd -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ia64/libuwx/src -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -mno-sdata -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/mem.c cc -c -O -pipe -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/ia64/ia64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath/freebsd -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ia64/libuwx/src -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -mno-sdata -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/mp_machdep.c cc -c -O -pipe -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/ia64/ia64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath/freebsd -I/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ia64/libuwx/src -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mconstant-gp
Re: cannot create partition entries for /dev/ad3
Given that FreeBSD 5.1 is on the shelf in a box at CompUSA for sale to the general public, I think the proper thing to do is address the matter of documenting the revised operation of the devices in 5.X, rather than tell people to downgrade if they don't understand the behavior of their system, besides which FreeBSD 4.8 or 4.9 are not for sale at CompUSA as a consolation. I did ask to know what documentation there is for the new behavior, but I have not heard any replies. If there isn't any documentation, that's an answer too. -ecsd Poul-Henning Kamp writes: 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. ___ [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 Wed, 8 Oct 2003, ecsd wrote: eGiven that FreeBSD 5.1 is on the shelf in a box at CompUSA for sale to the egeneral public, I think the proper thing to do is address the matter of edocumenting the revised operation of the devices in 5.X, rather than tell epeople to downgrade if they don't understand the behavior of their system, ebesides which FreeBSD 4.8 or 4.9 are not for sale at CompUSA as a consolation. eI did ask to know what documentation there is for the new behavior, but I have enot heard any replies. If there isn't any documentation, that's an answer too. You may want to look at section 12.3.2.1 of the handbook which will tell you to use 1) fdisk on the disk (da3) 2) disklabel on the slice (da3s1) 3) newfs on the partition (da3s1e) Yes, I know, real users don't read handbooks ... harti ePoul-Henning Kamp writes: eIn message [EMAIL PROTECTED], ecsd writes: eMAKEDEV was the cheese since year zero. [...] eI suggest you stick with 4-stable until you have caught up with ethe changes and the documentation. e e e___ e[EMAIL PROTECTED] mailing list ehttp://lists.freebsd.org/mailman/listinfo/freebsd-current eTo unsubscribe, send any mail to [EMAIL PROTECTED] e -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private [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: cannot create partition entries for /dev/ad3
If you read the early adopters doc at: http://www.freebsd.org/releases/5.1R/early-adopter.html You will se it clearly says: MAKEDEV is no longer available, nor is it required. FreeBSD 5.X uses a device filesystem, which automatically creates device nodes on demand. For more information, please see http://www.FreeBSD.org/cgi/man.cgi?query=devfssektion=5manpath=FreeBSD+5.1-releasedevfs(5). Any new version of an OS, particularly a free one, as FreeBSD is, will have issues. Particularly with the recent rapidity of new hardware, SATA drives, SATA card, RAID cards, etc. There are places to purchase copies of FreeBSD other than CompUSA where you can get 4.X or 5.X versions. Or you can download and burn your own CD's. You sound upset that you bought FreeBSD, if you are be upset perhaps you should be with CompUSA who made the money off the sale. -Derek At 04:05 AM 10/8/2003 -0700, ecsd wrote: Given that FreeBSD 5.1 is on the shelf in a box at CompUSA for sale to the general public, I think the proper thing to do is address the matter of documenting the revised operation of the devices in 5.X, rather than tell people to downgrade if they don't understand the behavior of their system, besides which FreeBSD 4.8 or 4.9 are not for sale at CompUSA as a consolation. I did ask to know what documentation there is for the new behavior, but I have not heard any replies. If there isn't any documentation, that's an answer too. -ecsd Poul-Henning Kamp writes: 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [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
Derek Ragona wrote: If you read the early adopters doc at: http://www.freebsd.org/releases/5.1R/early-adopter.html You will se it clearly says: MAKEDEV is no longer available, nor is it required. FreeBSD 5.X uses a device filesystem, which automatically creates device nodes on demand. For more information, please see http://www.FreeBSD.org/cgi/man.cgi?query=devfssektion=5manpath=FreeBSD+5.1-releasedevfs(5) http://www.FreeBSD.org/cgi/man.cgi?query=devfssektion=5manpath=FreeBSD+5.1-release%3Edevfs%285%29 I read that too. That appears to be just about all the information about the new devfs that there is, short of reading the source code. Here is the result of clicking on that more information link: FreeBSD Hypertext Man Pages http://www.FreeBSD.org */Man Page or Keyword Search:/* Man http://www.freebsd.org/cgi/man.cgi?query=mansektion=1apropos=0 Apropos http://www.freebsd.org/cgi/man.cgi?query=apropossektion=1apropos=0 Keyword Search (all sections) Output format Index Page and Help http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+4.8-RELEASE |FAQ http://www.freebsd.org/cgi/man.cgi/faq.html |Copyright http://www.freebsd.org/cgi/man.cgi/copyright.html Sorry, no data found for `devfs(5)'. You may look for other FreeBSD Search Services http://www.freebsd.org/search/. That's a bit unfair, perhaps; the result shows 4.8-RELEASE selected. But that's what the link does. Any new version of an OS, particularly a free one, as FreeBSD is, will have issues. Particularly with the recent rapidity of new hardware, SATA drives, SATA card, RAID cards, etc. The disks I'm dealing with are all well-known entirely standard IDE drives. There are places to purchase copies of FreeBSD other than CompUSA where you can get 4.X or 5.X versions. Or you can download and burn your own CD's. You sound upset that you bought FreeBSD, if you are be upset perhaps you should be with CompUSA who made the money off the sale. I was being rhetorical. I am chiding PHK for suggesting that the fix for my problem is to backstep the OS version - because that implies that 5.X should be recalled off the shelves. The book (FreeBSD Companion) included with the boxed version will still not be aware of version 5's lack of a MAKEDEV, and so Mr Mrs. Smith who walk in and buy 5.1 and try to do what the book says to do will be sorely disappointed. The books will catch up in their glacial way, but in the meantime I'd like to be able to read something about the operation of this new mechanism that will help me understand what is most likely wrong in my system. Poul says, maybe just stay with 4.8 until you have read the documentation. I asked, what documentation? Well, what documentation? Somebody somewhere, even if only in an email, will have described how the new devfs mechanism obviates the need for MAKEDEV. Maybe my 5.0 /is/ sick, but I suspect not. I booted with ad3 being an already-formatted disk from another system and the only ad3 entry in /dev/ is /dev/ad3. No /dev/ad3s1 or any other entry. I added device bktr and device pcm into the kernel config file and the devices are physically there, but /dev/bktr0 doesn't exist either. So I wonder what MANUAL operation I can perform to fix the problems. I am entirely willing to read anything that will inform me what revised protocol goes on with this stuff so I can tell what I'll need to do to get over this hump. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Why is em nic generating interrupts?
Hello, everyone! I've got a [uniprocessor 5.1-RELEASE] router machine with fxp and em nics. I've built my kernel with the following included: options DEVICE_POLLING options HZ=2500 and enabled polling in /etc/sysctl.conf. Having looked through a vmstat -i output I see that the em card is generating interrupts, although they should be disabled (as I see in em's source code). interrupt total rate stray irq01 0 stray irq61 0 npx0 irq131 0 ata0 irq14 2339 0 em0 irq10421457155 fxp0 irq5 2 0 atkbd0 irq13326 1 clk irq06778872 2500 rtc irq8 346899127 Total 7552898 2786 What's happening? Is polling working in my case? If yes, why is vmstat showing interrupts? I see clearly, that fxp's counter doesn't increase, and em's is constantly growing. Is there anyone who knows for sure that em's polling works? Thanks in advance to anyone for an idea! Please also CC: me as I'm not subscribed. P.S. I've posted this question to questions@, but so far the question is still open. So if someone finds this post familiar, please just ignore it. -- Best wishes, [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no driver attached messsage
That is because there is no driver for that specific hardware. If FreeBSD supports them, you need to recompile kernel with appropriate drivers or dynamically load them. As for the unsupported devices, (like winmodems), you can't help it. -- Babak Farrokhi Dikshie wrote: 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=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 267583488 (255 MB) avail memory = 251961344 (240 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: INTEL S875PWP1 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: CPU on acpi0 acpi_cpu1: CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus 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: Intel 82875P host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 3.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib2: slot 1 INTA is routed to irq 10 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.16 port 0xac00-0xac1f mem 0xfc9e-0xfc9f irq 10 at device 1.0 on pci2 em0: Speed:N/A Duplex:N/A uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0xcc00-0xcc1f irq 5 at device 29.0 on pci0 usb0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0xd000-0xd01f irq 10 at device 29.1 on pci0 usb1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0xd400-0xd41f irq 10 at device 29.2 on pci0 usb2: Intel 82801EB (ICH5) USB controller USB-C 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: Intel 82801EB (ICH5) USB controller USB-D port 0xd800-0xd81f irq 5 at device 29.3 on pci0 usb3: Intel 82801EB (ICH5) USB controller USB-D 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: serial bus, USB at device 29.7 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 30.0 on pci0 pci3: ACPI PCI bus 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: Adaptec 29160N Ultra160 SCSI adapter 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: display, VGA at device 6.0 (no driver attached) fxp0: Intel 82801BA (D865) Pro/100 VE Ethernet port 0xbc00-0xbc3f mem 0xfeafd000-0xfeafdfff irq 11 at device 8.0 on pci3 fxp0: Ethernet address 00:07:e9:45:69:3d miibus0: MII bus on fxp0 inphy0: i82562ET 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller 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: mass storage, RAID at device 31.2 (no driver attached) pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_button0: Sleep Button on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq
Re: cannot create partition entries for /dev/ad3
Hiya I read that too. That appears to be just about all the information about the new devfs that there is, short of reading the source code. If you look in /usr/share/doc (or someplace like that) there's a document describing the rationale behind devfs and its implementation - it's geared more towards programmers than end users, but I certainly found it useful. Cheers, --Jon http://www.witchspace.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Atmel AT76C503 USB 802.11b device driver
On Wed, Oct 08, 2003 at 03:59:40AM +0100, Stuart Walsh wrote: Aww crap, my apologies for the duplicate email.. sendmail appears to be on steroids or something. The messages are sumited twice by your mailclient - it's not the MTAs fault. See that there are several minutes between them and that they have different message-ids. 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. Sounds interesting. Is this just to configure a WLAN-Ethernet bridge, or can you transmit network data over USB? -- B.Walter BWCThttp://www.bwct.de [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: Atmel AT76C503 USB 802.11b device driver
On Wed Oct 08, 05:27P +0200, Bernd Walter wrote: On Wed, Oct 08, 2003 at 03:59:40AM +0100, Stuart Walsh wrote: Aww crap, my apologies for the duplicate email.. sendmail appears to be on steroids or something. The messages are sumited twice by your mailclient - it's not the MTAs fault. See that there are several minutes between them and that they have different message-ids. They were, yes. But once when the sendmail daemon wasn't running. I checked the mail queue before i sent it again and it wasn't there. Perhaps sendmail stores failed mail somewhere I'm not familiar with. EUSERERROR would seem to apply.. Anyway, I finally got around to installing exim and everyone is happy. 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. Sounds interesting. Is this just to configure a WLAN-Ethernet bridge, or can you transmit network data over USB? It's treated like any other network device. Raw network data is sent and received over the USB transfer pipes and dealt with using mbufs in the normal way. The main difference is that you can only submit one packet at a time, so there is effectively no hardware queue/ring. The wireless part seems to be a cross between 'ath' devices and 'wi' devices. WEP is done in hardware, as is scanning. Scan results are processed in software. Stuart ___ [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
I read that too. That appears to be just about all the information about the new devfs that there is, short of reading the source code. You shouldn't need to do that. You can, more or less entirely forget about DEVFS unless you are a device driver writer. If you needed to run mknod(8) before you don't now, it will happen automatically. If it doesn't happen, it wouldn't have worked to run mknod(8) either. Poul-Henning PS: Eric, didn't you work at TFS at one time ? -- 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]
Nvidia driver
Ahh! Here is a fragment of my loader.conf.. nvidia_load=YES machdep.disable_mtrrs=1 hw.nvidia.registry.ReqAGPRate=1 Although this fix alloes me to start up the nvidia driver, the machine still reboots when I run certain apps (openuniverse, for instance) and at random times otherwise. Since I need this, I'll have to retreat to stable for a while... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
i865 Video Memory
It seems some recent Dell machines have the amount of video memory available set to 1MB by default. The desktop machines allow you to set this in the BIOS, but the laptops don't seem to allow you to adjust this. Christian Zietz has a hack for Linux that convinces the BIOS to let you use more memory, and I've just ported his hack to FreeBSD. Christian's code is at: http://www.chzsoft.com.ar/855patch.html and my patch to his code, and a binary compiled for 4.9 are at: http://www.cnri.dit.ie/~dwmalone/855patch/ You can just run 855patch 8192 before starting X, and suddenly you can do a resolution higher than 640x480 in 8 bit mode ;-) David. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[current tinderbox] failure on alpha/alpha
TB --- 2003-10-08 16:00:01 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-10-08 16: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 16:01:52 - building world TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha/src TB --- /usr/bin/make -B buildworld 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 17:05:01 - 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 17:05:01 GMT 2003 Kernel build for GENERIC completed on Wed Oct 8 17:16:50 GMT 2003 TB --- 2003-10-08 17:16:50 - 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 17:16:50 - 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 17:16:50 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 -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
Upgrading 5.1 to latest - page fault in kernel (crash) upon starting X
Hi, Seems like I'm running into a serious problem upgrading my 5.1 machine to the latest level: The symptoms: I did an upgrade (cvsup) then went through the usual build/install cycle (see below). When I boot the new kernel everything runs straight up to the moment when I start X-Windows. When starting X as a normal user I end up with a db-prompt (debugger?) - from there I can only reset :-(. (for details about the messages see below) When starting X as root the screen goes blank and after some seconds the box reboots. As far as building installing is concerned I did everything as per chapter 21 of the handbook, including installing binaries (userland) in single-user mode, running mergemaster etc.etc i.e. make buildworld; make buildkernel; make installkernel shutdown -r fsck -p mount -u / mount -a -t ufs swapon -a cd /usr/src make installworld When booting the old kernel (kernel.old) everything is fine again - so assume the problem is with the kernel itself. The old kernel is the one that has been installed when installing 5.1 from the CD. I also did a diff between the GENERIC file that came with the original installation and the one that was installed using cvsup (i.e. the one used in the fresh build) - no difference except the version string. I tried configuring device mgadrm into the new kernel (this wasn't there in the the original GENERIC though) - to no extent - same crash. Also: I've no indication about a problem in either /var/log/messages or the X-log - seems the box crashes before being able to write anything to the log. Has anybody else seen this? What can I do against it? Since I don't want to post exessive logs in the first place, here's what I've got: Asus CUSL2-mobo 512MB RAM 2 IDE HDs (80, 60GB) Matrox G400 graphics When upgrading I went from the version that comes on the 5.1-CD to the latest one available via cvsup (the UPDATING file has an entry of 2003-09-28) Please let me know if you need any additional details. Thanks much in advance for your help, -ewald -- Cut here - Here's the output from db which is where I end in when I start X: (BTW - does anybody know a way how to capture this output besides writing it down?) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1c fault code: supervisor read, page not present Instruction pointer = 0x8: 0xc062e40e Stack pointer = 0x10: 0xdcaa0b68 framepointer= 0x10: 0xdcaa0b68 code segment= base 0x0, limit 0xf, type 0x1b DPL 0, pres 1, def32 1, gran 1 procesor eflags = interrupt enabled, resume, IOPL=0 current process = 595 (XFree86) kernel: type12 trap, code0 Stopped at _mtx_assert+0x4e: movl 0x1c(%ebx),%eax ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no partition entries for /dev/ad3
On Wed, 8 Oct 2003, ecsd wrote: The chronology is that I booted the system, did the disklabel -w -r ad3 auto, turned around to disklabel -e /dev/ad3s1c (as I would normally do), and was told that /dev/ad3s1c did not exist. Then I wrote in here asking for help. ad3s1c does not exist. Since it looks like you already have a working FreeBSD system, can you try running /stand/sysinstall ? At that point, you can choose Configure and the Fdisk and Label choices are generally a much freindlier interface to getting a disk online. While Real Men Use the Command Line, I have found more than enough mysterious situations that /stand/sysinstall just seems to get right even though what I type at command line should be the same thing. Sometimes I have to do the slice configuration, reboot the machine, and *then* edit the label. Whatever. I don't use disklabel, bsdlabel, or fdisk often enough to memorize the options and procedures; consequently, everytime I have to configure a random storage device I'm effectively a newbie. Also, I have lost track of the number of times that I have pulled out and booted a RedHat rescue CD in order so that I can get a slice table that Windows, Linux, and FreeBSD (admittedly not all the fault lies with FreeBSD) can all agree on. Configuring disk slices and partitions in FreeBSD sucks, but nobody is going to fix it. It's grubby, grunt work that a company like RedHat has to pay someone to do. The person who does the rewrite for FreeBSD will only catch grief when it has bugs, but will get neither praise nor money when it works. I can only fix one of those things. ;) To whomever wrote the Fdisk and Label editor in sysinstall: Thanks. You did a good job, and I thank you for it. -a ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no partition entries for /dev/ad3
On Wed, Oct 08, 2003 at 11:20:16AM -0700, Andrew P. Lentvorski, Jr. wrote: On Wed, 8 Oct 2003, ecsd wrote: The chronology is that I booted the system, did the disklabel -w -r ad3 auto, turned around to disklabel -e /dev/ad3s1c (as I would normally do), and was told that /dev/ad3s1c did not exist. Then I wrote in here asking for help. ad3s1c does not exist. Since it looks like you already have a working FreeBSD system, can you try running /stand/sysinstall ? At that point, you can choose Configure and the Fdisk and Label choices are generally a much freindlier interface to getting a disk online. On 5.1, you want to use /usr/sbin/sysinstall. -- Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: boot hang: ata1: resetting devices .. done (5.1-CURRENT, IBM T30)
I see this problem as well. I'm running on a T40, with a DVD/CDRW in the ultrabay, and -CURRENT as of this morning. At boot, it hangs immediately after ad0: 35174MB IC25N040ATCS05-0 [71465/16/63] at ata0-master UDMA100 ata1: resetting devices .. done Backing out the most recent checkin to sys/dev/ata/ata-queue.c (i.e. reverting to version 1.6) makes the problem go away. A verbose dmesg from the machine (with that change removed) can be found at http://www.fergusonlabs.com/t40/dmesg0.txt Thanks, Rob Ferguson ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Atmel AT76C503 USB 802.11b device driver
On Wed, 8 Oct 2003 16:49:34 +0100 Stuart Walsh [EMAIL PROTECTED] wrote: They were, yes. But once when the sendmail daemon wasn't running. I checked the mail queue before i sent it again and it wasn't there. Perhaps sendmail stores failed mail somewhere I'm not familiar with. EUSERERROR would seem to apply.. mailq or mailq -Ac? Bye, Alexander. -- Secret hacker rule #11: hackers read manuals. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
UDMA33 on older acer aladdin chips
Hi,
I recently decided to update my alpha UP1000 to today's current from a
mid-July build. However, UDMA33 did not work on a hard disk attached
to the built-in Acer Aladdin controller (verbose dmesg appended).
I think I have narrowed the problem down to this line of code:
atadev-channel-flags |= ATA_ATAPI_DMA_RO;
Removing this line gets my UDMA33 back.
Cheers,
Drew
Patch to hack around problem:
Index: ata-chipset.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-chipset.c,v
retrieving revision 1.39
diff -u -r1.39 ata-chipset.c
--- ata-chipset.c 8 Sep 2003 13:55:05 - 1.39
+++ ata-chipset.c 8 Oct 2003 19:43:30 -
@@ -382,7 +382,10 @@
if (ctlr-chip-cfg2 ALIOLD) {
/* doesn't support ATAPI DMA on write */
+#if 0
+ /* XXX this breaks ATA disk DMA support */
atadev-channel-flags |= ATA_ATAPI_DMA_RO;
+#endif
if (atadev-channel-devices ATA_ATAPI_MASTER
atadev-channel-devices ATA_ATAPI_SLAVE) {
/* doesn't support ATAPI DMA on two ATAPI devices */
Dmesg from failure:
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 #4: Wed Oct 8 14:22:44 EDT 2003
[EMAIL PROTECTED]:/home/gallatin/current/sys/alpha/compile/THUNDER
Preloaded elf kernel /kernel.test at 0xfc766000.
UP1000
API UP1000 598 MHz, 598MHz
8192 byte page size, 1 processor.
CPU: EV67 (21264A) major=11 minor=8 extensions=0x307BWX,FIX,CIX,MVI,PRECISE
OSF PAL rev: 0x100010002013e
real memory = 668344320 (637 MB)
Physical memory chunk(s):
0x00788000 - 0x275dbfff, 652558336 bytes (79658 pages)
avail memory = 643145728 (613 MB)
null: null device, zero device
random: entropy source
mem: memory I/O
irongate0: AMD 751 Core Logic chipset
pcib0: AMD 751 PCI host bus adapter on irongate0
pci0: PCI bus on pcib0
pci0: physical bus=0
map[10]: type 3, range 32, base , size 0, enabled
map[14]: type 3, range 32, base 423a, size 12, enabled
map[18]: type 4, range 32, base 000100c0, size 2, port disabled
found- vendor=0x1022, dev=0x7006, revid=0x25
bus=0, slot=0, func=0
class=06-00-00, hdrtype=0x00, mfdev=1
cmdreg=0x0006, statreg=0x2210, cachelnsz=0 (dwords)
lattimer=0xff (7650 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
found- vendor=0x1022, dev=0x7007, revid=0x01
bus=0, slot=1, func=0
class=06-04-00, hdrtype=0x01, mfdev=1
cmdreg=0x0007, statreg=0x0220, cachelnsz=0 (dwords)
lattimer=0xff (7650 ns), mingnt=0x0e (3500 ns), maxlat=0x00 (0 ns)
found- vendor=0x10b9, dev=0x1533, revid=0xc3
bus=0, slot=7, func=0
class=06-01-00, hdrtype=0x00, mfdev=0
cmdreg=0x0007, statreg=0x3200, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
map[10]: type 3, range 32, base 423a1000, size 12, enabled
map[14]: type 4, range 32, base 00010080, size 5, enabled
map[18]: type 1, range 32, base 4210, size 20, enabled
found- vendor=0x8086, dev=0x1229, revid=0x02
bus=0, slot=8, func=0
class=02-00-00, hdrtype=0x00, mfdev=0
cmdreg=0x0007, statreg=0x0280, cachelnsz=0 (dwords)
lattimer=0xff (7650 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns)
intpin=a, irq=9
map[10]: type 3, range 32, base 4000, size 24, enabled
found- vendor=0x14c1, dev=0x8043, revid=0x03
bus=0, slot=10, func=0
class=00-00-00, hdrtype=0x00, mfdev=0
cmdreg=0x0086, statreg=0x0420, cachelnsz=16 (dwords)
lattimer=0xff (7650 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=a, irq=9
map[10]: type 4, range 32, base 0001, size 7, enabled
map[14]: type 1, range 32, base 423a2000, size 7, enabled
found- vendor=0x10b7, dev=0x9055, revid=0x64
bus=0, slot=11, func=0
class=02-00-00, hdrtype=0x00, mfdev=0
cmdreg=0x0007, statreg=0x0210, cachelnsz=16 (dwords)
lattimer=0xf8 (7440 ns), mingnt=0x0a (2500 ns), maxlat=0x0a (2500 ns)
intpin=a, irq=10
powerspec 1 supports D0 D1 D2 D3 current D0
map[10]: type 4, range 32, base 01f0, size 4, enabled
map[14]: type 4, range 32, base 03f4, size 2, enabled
map[18]: type 4, range 32, base 0170, size 4, enabled
map[1c]: type 4, range 32, base 0374, size 2, enabled
map[20]: type 4, range 32, base 000100b0, size 4, enabled
found- vendor=0x10b9, dev=0x5229, revid=0xc1
bus=0, slot=16, func=0
class=01-01-fa, hdrtype=0x00, mfdev=0
cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords)
lattimer=0xff (7650 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns)
intpin=a, irq=15
map[10]: type 4, range 32, base 1000, size 6, enabled
Re: Atmel AT76C503 USB 802.11b device driver
On Wed, 8 Oct 2003 16:49:34 +0100 Stuart Walsh [EMAIL PROTECTED] wrote: They were, yes. But once when the sendmail daemon wasn't running. I checked the mail queue before i sent it again and it wasn't there. Perhaps sendmail stores failed mail somewhere I'm not familiar with. EUSERERROR would seem to apply.. mailq or mailq -Ac? I think we've established I was at fault, but thanks :) It really was just an off the cuff remark, I didn't intend to start an MTA war or a sendmail usage lecture. Can we restrict all further posts in this thread to feedback on my driver? :) Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no partition entries for /dev/ad3
On Wed, 8 Oct 2003, Harti Brandt wrote: On Wed, 8 Oct 2003, ecsd wrote: eI had already been able to go so far as to disklabel -w -r ad3 auto. This is in error and should have been: fdisk -i -u /dev/ad3 [add a partition 1] disklabel -r -w ad3s1 auto he has a disklabel directly on the raw disk.. (Dangerously dedicated mode) eAfter doing this eon a 4.X system I would then disklabel -e /dev/ad3s1c, but /dev/ad3s1c edoes enot exist, so I am stuck. Maybe there is a rescan devices command? e efdisk thinks it has no work to do: e e*** Working on device /dev/ad3 *** e[...] eInformation from DOS bootblock is: e1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) estart 63, size 39102273 (19092 Meg), flag 80 (active) ebeg: cyl 0/ head 1/ sector 1; eend: cyl 1023/ head 15/ sector 63 e2: UNUSED e3: UNUSED e4: UNUSED In that case you should have a /dev/ad3s1. Have you? harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no partition entries for /dev/ad3
On Wed, 8 Oct 2003, ecsd wrote: Harti Brandt wrote: On Wed, 8 Oct 2003, ecsd wrote: eI had already been able to go so far as to disklabel -w -r ad3 auto. eAfter doing this on a 4.X system I would then disklabel -e /dev/ad3s1c ebut /dev/ad3s1c does not exist, so I am stuck. eMaybe there is a rescan devices command? e fdisk thinks it has no work to do. In that case you should have a /dev/ad3s1. Have you? harti The chronology is that I booted the system, did the disklabel -w -r ad3 auto, turned around to disklabel -e /dev/ad3s1c (as I would normally do), and was told that /dev/ad3s1c did not exist. Then I wrote in here asking for help. ad3s1c does not exist. that's because you didn't do the fdisk before you did the disklabel. a/ NEVER use the 'c' partition as the target. b/ since you never created a ad3s1 what makes you thing it will be subdivided? You subdivided ad3 so that is what you should use with disklabel -e. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia driver
On Wed, 8 Oct 2003, Justin Smith wrote: Ahh! Here is a fragment of my loader.conf.. nvidia_load=YES machdep.disable_mtrrs=1 hw.nvidia.registry.ReqAGPRate=1 Although this fix alloes me to start up the nvidia driver, the machine still reboots when I run certain apps (openuniverse, for instance) and at random times otherwise. Since I need this, I'll have to retreat to stable for a while... If you hook up a serial console, are there any messages that get printed out? Andre Guibert de Bruet | Enterprise Software Consultant Silicon Landmark, LLC. | http://siliconlandmark.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
if_em panic
One of my buddies is having panics with if_em after the last
set of changes a couple of weeks ago. He runs dhclient
on the interface to get a lease from a cable modem. The
panic is a recurse on a non-recursive mutex. I haven't
gotten a traceback from him yet, but a little perusing
through the source seems to show this as a possible problem:
Index: if_em.c
===
RCS file: /opt/FreeBSD/cvs/src/sys/dev/em/if_em.c,v
retrieving revision 1.30
diff -u -r1.30 if_em.c
--- if_em.c 23 Sep 2003 00:18:25 - 1.30
+++ if_em.c 8 Oct 2003 20:12:56 -
@@ -933,7 +933,7 @@
if (ether_poll_register(em_poll, ifp)) {
em_disable_intr(adapter);
-em_poll(ifp, 0, 1);
+ em_poll_locked(ifp, 0, 1);
EM_UNLOCK(adapter);
return;
}
Also, indentation is inconsistent, some lines use tabs, some
uses spaces. It looks like the original code from Intel used
spaces and subsequent mods used tabs. I guess we should be
sticking with the original style, but it is easy to overlook.
--
Dan Eischen
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: if_em panic
On Wednesday 08 October 2003 05:27 pm, Daniel Eischen wrote:
One of my buddies is having panics with if_em after the last
set of changes a couple of weeks ago. He runs dhclient
on the interface to get a lease from a cable modem. The
panic is a recurse on a non-recursive mutex. I haven't
gotten a traceback from him yet, but a little perusing
through the source seems to show this as a possible problem:
Index: if_em.c
===
RCS file: /opt/FreeBSD/cvs/src/sys/dev/em/if_em.c,v
retrieving revision 1.30
diff -u -r1.30 if_em.c
--- if_em.c 23 Sep 2003 00:18:25 - 1.30
+++ if_em.c 8 Oct 2003 20:12:56 -
@@ -933,7 +933,7 @@
if (ether_poll_register(em_poll, ifp)) {
em_disable_intr(adapter);
-em_poll(ifp, 0, 1);
+ em_poll_locked(ifp, 0, 1);
EM_UNLOCK(adapter);
return;
}
Thanks, I've got work to do on DEVICE_POLLING (changes to the core polling
code are still sitting in my perforce tree). I'll commit after going over
the driver again.
Also, indentation is inconsistent, some lines use tabs, some
uses spaces. It looks like the original code from Intel used
spaces and subsequent mods used tabs. I guess we should be
sticking with the original style, but it is easy to overlook.
Yeah, probably. I wouldn't notice it. I agree that it's important to conform
to local style, regardless of whether it conflicts with style(9).
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nvidia driver
On Thursday 09 October 2003 01:41, Justin Smith wrote: Ahh! Here is a fragment of my loader.conf.. nvidia_load=YES machdep.disable_mtrrs=1 hw.nvidia.registry.ReqAGPRate=1 Although this fix alloes me to start up the nvidia driver, the machine still reboots when I run certain apps (openuniverse, for instance) and at random times otherwise. Since I need this, I'll have to retreat to stable for a while... Ahh, sounds exactly like the status of my wife's machine.. Openuniverse sounds.. opengl'ish.. I would suggest putting back the original X OGL libs so you don't accidentally blow your feet off :) -- 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: savecore: first and last dump headers disagree on /dev/ad0b
On Tue, 7 Oct 2003, Kris Kennaway wrote: 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. Well that woudl be funny since the problem boards were replaced with Tyan S2518s, which have a PDC20267 onboard as well as the ROSB4. The disks were attached to the Promise, and never had any data corruption issues with them, at least under linnex. -- 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]
Re: savecore: first and last dump headers disagree on /dev/ad0b
On Wed, Oct 08, 2003 at 07:05:49PM -0700, Doug White wrote: 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. Well that woudl be funny since the problem boards were replaced with Tyan S2518s, which have a PDC20267 onboard as well as the ROSB4. The disks were attached to the Promise, and never had any data corruption issues with them, at least under linnex. This is a FreeBSD bug that was introduced within the past few months, perhaps with ATAng. Kris pgp0.pgp Description: PGP signature
Re: UDMA33 on older acer aladdin chips
Andrew Gallatin wrote: Hi, I recently decided to update my alpha UP1000 to today's current from a mid-July build. However, UDMA33 did not work on a hard disk attached to the built-in Acer Aladdin controller (verbose dmesg appended). I think I have narrowed the problem down to this line of code: atadev-channel-flags |= ATA_ATAPI_DMA_RO; Removing this line gets my UDMA33 back. If I understand the code correctly, the right fix should more look like: diff -u -r1.18 ata-lowlevel.c --- ata-lowlevel.c 7 Oct 2003 13:45:56 - 1.18 +++ ata-lowlevel.c 8 Oct 2003 22:38:15 - @@ -73,7 +73,8 @@ request-device-channel-running = request; /* disable ATAPI DMA writes if HW doesn't support it */ -if (request-flags (ATA_R_ATAPI | ATA_R_DMA | ATA_R_WRITE) +if (((request-flags (ATA_R_ATAPI | ATA_R_DMA | ATA_R_WRITE)) == + (ATA_R_ATAPI | ATA_R_DMA | ATA_R_WRITE)) request-device-channel-flags ATA_ATAPI_DMA_RO) request-flags = ~ATA_R_DMA; But I don't have ATAPI devices attached to this machine to test. Daniel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ath0 point-to-ponit (turbo mode)
Hi There. I have 2 PCI wireless card with the Atheros chipset some one know how can i setup a point-to-point with 2 of this wireless card on Freebsd, I could made work Access Point client, but i couln't adhoc turbo mode 11a thanks -- Marcos Biscaysaqu Systems Administrator ThePacific.Net Ltd. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 point-to-ponit (turbo mode)
On Wednesday 08 October 2003 08:45 pm, Marcos Biscaysaqu wrote: Hi There. I have 2 PCI wireless card with the Atheros chipset some one know how can i setup a point-to-point with 2 of this wireless card on Freebsd, I could made work Access Point client, but i couln't adhoc turbo mode 11a Apparently adhoc mode is currently busted. It's at the top of my todo list and I may even get to it this week... Sam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Sched_Ule
Hi, I see some posts from late Sept about people having issues with SCHED_ULE. I just wanted to add in that I am having the exact same problems. In short: Anything that seems disk intensive: bzip2 (unbzip2ing one big file makes this happen), making world, building ports, etc makes my X environment practically unusable. Mouse stutters, reaction times is very slow, feels 10x more sluggish than normal. (I'm running KDE if anyone is curious). I rebuilt my kernel today (running yesterday's world) with SCHED_4BSD instead, and things are much better. System is much much more responsive. If there's any tests I can run, or anyone I should talk to, I'd love to be of assistance, thanks much, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ipnat memory leak?
I was using ipfw and natd but I wanted to move nat into the kernel so I recompiled with ipfilter and ipnat. Now, after terminating natd, and setting up ipnat rules in /etc/ipnat.rules, I see memory increase at a rate of just under 1MB per minutes. Has anyone else seen a memory leak in ipnat or ipfilter? vec ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Can not remove directory
Hello! Can not remove directory /usr/obj/usr/src/gnu/usr.bin/cc/cc1 rm: /usr/obj/usr/src/gnu/usr.bin/cc/cc1: Directory not empty bash-2.05b# pwd; ls -la /usr/obj/usr/src/gnu/usr.bin/cc/cc1 total 4 drwxr-xr-x 2 root wheel 512 Oct 9 08:54 . drwxr-xr-x 13 root wheel 512 Oct 9 08:54 .. bash-2.05b# pwd; ls -la /usr/obj/usr/src/gnu/usr.bin/cc total 26 drwxr-xr-x 13 root wheel 512 Oct 9 08:54 . drwxr-xr-x 21 root wheel 512 Oct 9 11:23 .. drwxr-xr-x 2 root wheel 512 Oct 9 08:55 c++ drwxr-xr-x 2 root wheel 512 Oct 9 08:55 c++filt drwxr-xr-x 2 root wheel 512 Oct 9 08:54 cc1 drwxr-xr-x 2 root wheel 512 Oct 9 08:55 cc1obj drwxr-xr-x 2 root wheel 1024 Oct 9 08:55 cc1plus drwxr-xr-x 2 root wheel 512 Oct 9 08:55 cpp drwxr-xr-x 2 root wheel 512 Oct 9 08:55 cpp0 drwxr-xr-x 2 root wheel 512 Sep 26 10:34 doc drwxr-xr-x 2 root wheel 512 Oct 9 08:55 gcov drwxr-xr-x 2 root wheel 512 Oct 9 08:55 protoize drwxr-xr-x 2 root wheel 512 Oct 9 08:55 tradcpp0 What is wrong? Current system is 5.1-RELEASE-p8 Yours truly, Boris Kovalenko ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can not remove directory
man rm Note -r and -f. Boris Kovalenko wrote: Hello! Can not remove directory /usr/obj/usr/src/gnu/usr.bin/cc/cc1 rm: /usr/obj/usr/src/gnu/usr.bin/cc/cc1: Directory not empty bash-2.05b# pwd; ls -la /usr/obj/usr/src/gnu/usr.bin/cc/cc1 total 4 drwxr-xr-x 2 root wheel 512 Oct 9 08:54 . drwxr-xr-x 13 root wheel 512 Oct 9 08:54 .. bash-2.05b# pwd; ls -la /usr/obj/usr/src/gnu/usr.bin/cc total 26 drwxr-xr-x 13 root wheel 512 Oct 9 08:54 . drwxr-xr-x 21 root wheel 512 Oct 9 11:23 .. drwxr-xr-x 2 root wheel 512 Oct 9 08:55 c++ drwxr-xr-x 2 root wheel 512 Oct 9 08:55 c++filt drwxr-xr-x 2 root wheel 512 Oct 9 08:54 cc1 drwxr-xr-x 2 root wheel 512 Oct 9 08:55 cc1obj drwxr-xr-x 2 root wheel 1024 Oct 9 08:55 cc1plus drwxr-xr-x 2 root wheel 512 Oct 9 08:55 cpp drwxr-xr-x 2 root wheel 512 Oct 9 08:55 cpp0 drwxr-xr-x 2 root wheel 512 Sep 26 10:34 doc drwxr-xr-x 2 root wheel 512 Oct 9 08:55 gcov drwxr-xr-x 2 root wheel 512 Oct 9 08:55 protoize drwxr-xr-x 2 root wheel 512 Oct 9 08:55 tradcpp0 What is wrong? Current system is 5.1-RELEASE-p8 Yours truly, Boris Kovalenko ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can not remove directory
In the last episode (Oct 09), Boris Kovalenko said: Can not remove directory /usr/obj/usr/src/gnu/usr.bin/cc/cc1 rm: /usr/obj/usr/src/gnu/usr.bin/cc/cc1: Directory not empty bash-2.05b# pwd; ls -la /usr/obj/usr/src/gnu/usr.bin/cc/cc1 total 4 drwxr-xr-x 2 root wheel 512 Oct 9 08:54 . drwxr-xr-x 13 root wheel 512 Oct 9 08:54 .. Interesting. Usually you get this after a crash, due to how softupdates buffers directory updates. The background fsck should have repaired the directory, though. If it isn't still running, try rebooting in single-user mode and run fsck -p on the filesystem. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
