RE: Current SMP with ACPI dies in a second
John Baldwin writes: Ok, your BIOS is buggy, but I think I can work around it. http://www.FreeBSD.org/~jhb/patches/acpi_irq.patch Thanks, now it's working much better! New dmesg and vmstat-i at http://tomppa.iki.fi/~tomppa/FreeBSD/ Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Current SMP with ACPI dies in a second
Tomi Vainio writes: My old MSI-6120 SMP system has been unusable quite a while with ACPI. I've got these so far: - Couldn't get vector from ISR - vmstat -i shows high interrupt rates and system is very slow - kernel trap 12 panic Latest problem is something like this: pfs_vncache_unload(): 2 entries remaining current process = 27 (irq17: fxp0) kernel trap 12 stray irq20 Kernel config, dmesg, acpidump, etc. files available at http://tomppa.iki.fi/~tomppa/FreeBSD/ With latest source cvsupped 15 minutes ago system don't panic anymore but it's still unusable with acpi because of too high interrupt rate from acpi device. vmstat -i interrupt total rate irq1: atkbd0 291 1 irq0: clk 28360 99 irq6: fdc0 5 0 irq8: rtc 36303127 irq12: psm0 942 3 irq14: ata0 10 0 irq15: ata1 49 0 irq16: ahc0 ahc17788 27 irq17: fxp0 2886 10 irq19: uhci0 bktr0 31336110 irq20: acpi011614583 40896 irq9: intpm01376 4 Total 11723929 41281 Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Current SMP with ACPI dies in a second
My old MSI-6120 SMP system has been unusable quite a while with ACPI. I've got these so far: - Couldn't get vector from ISR - vmstat -i shows high interrupt rates and system is very slow - kernel trap 12 panic Latest problem is something like this: pfs_vncache_unload(): 2 entries remaining current process = 27 (irq17: fxp0) kernel trap 12 stray irq20 Kernel config, dmesg, acpidump, etc. files available at http://tomppa.iki.fi/~tomppa/FreeBSD/ Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ata problem with latest current
Hi, Once again we cvsupped latest ATA code changes and nothing much changed. Only after couple minutes of stress testing system will freeze. Though error message is little different than before. Tomppa ad5: TIMEOUT - READ_DMA retrying (2 retries left) ata2: resetting devices .. ata2: reset tp1 mask=03 ostat0=80 ostat1=80 ad4: stat=0x90 err=0x90 lsb=0x90 msb=0x90 ad5: stat=0x90 err=0x90 lsb=0x90 msb=0x90 ad4: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ad5: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 mask=03 stat0=50 stat1=50 devices=0x3ATA_SLAVE,ATA_MASTER ad4: FAILURE - already active DMA on this device ad4: setting up DMA failed ad5: pio=0x0c wdma=0x22 udma=0x45 cable=80pin smbfs_getpages: error 4 vm_fault: pager read error, pid 621 (cp) smb_iod_recvall: drop resp with mid 31170 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ata problem with latest current
Hi, Current ATA code is still unusable unstable. We cvsupped latest source yesterday and tried our standard stress test copy between two vinum volumes. Once we even got 12 hour uptime but today it won't take longer than couple minutes before system freezes. Situation is even worse if we replace single port 3com-905-xl0 with znyx-quad-dc0. With this card system won't stay up even a minute. Tomppa clip clip *** Oct 17 10:20:29 tiikeli kernel: smb_iod_recvall: drop resp with mid 10121 Oct 17 13:03:35 tiikeli kernel: ad5: TIMEOUT - READ_DMA retrying (2 retries left) Oct 17 13:03:35 tiikeli kernel: ata2: resetting devices .. Oct 17 13:03:35 tiikeli kernel: ata2: reset tp1 mask=03 ostat0=80 ostat1=80 Oct 17 13:03:35 tiikeli kernel: ad4: stat=0x80 err=0x80 lsb=0x80 msb=0x80 Oct 17 13:03:35 tiikeli kernel: ad5: stat=0x90 err=0x90 lsb=0x90 msb=0x90 Oct 17 13:03:35 tiikeli kernel: ad4: stat=0x90 err=0x90 lsb=0x90 msb=0x90 Oct 17 13:03:35 tiikeli kernel: ad5: stat=0x90 err=0x90 lsb=0x90 msb=0x90 Oct 17 13:03:35 tiikeli kernel: ad4: stat=0x50 err=0x01 lsb=0x00 msb=0x00 Oct 17 13:03:35 tiikeli kernel: ad5: stat=0x50 err=0x01 lsb=0x00 msb=0x00 Oct 17 13:03:36 tiikeli kernel: ata2: reset tp2 mask=03 stat0=50 stat1=50 devices=0x3ATA_SLAVE,ATA_MASTER Oct 17 13:03:36 tiikeli kernel: ata2: reset tp3 devices=0x3ATA_SLAVE,ATA_MASTER Oct 17 13:03:36 tiikeli kernel: ad5: pio=0x0c wdma=0x22 udma=0x45 cable=80pin Oct 17 13:03:45 tiikeli reboot: rebooted by ramppa clip clip *** Oct 17 16:02:36 tiikeli kernel: WARNING: /v was not properly dismounted Oct 17 16:02:51 tiikeli kernel: /v: superblock summary recomputed Oct 17 16:03:15 tiikeli kernel: WARNING: /mnt was not properly dismounted Oct 17 16:03:36 tiikeli kernel: /mnt: superblock summary recomputed Oct 17 16:20:43 tiikeli kernel: ad6: WARNING - READ_DMA recovered from missing interrupt Oct 17 16:20:50 tiikeli kernel: ad4: WARNING - READ_DMA recovered from missing interrupt Oct 17 16:20:53 tiikeli kernel: ad6: WARNING - READ_DMA recovered from missing interrupt Oct 17 16:21:00 tiikeli kernel: ad4: WARNING - READ_DMA recovered from missing interrupt Oct 17 16:21:03 tiikeli kernel: ad7: WARNING - READ_DMA recovered from missing interrupt Oct 17 16:21:03 tiikeli kernel: ad6: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=4ABORTED Oct 17 16:22:17 tiikeli kernel: ad5: TIMEOUT - READ_DMA retrying (2 retries left) Oct 17 16:22:17 tiikeli kernel: ata2: resetting devices .. Oct 17 16:22:17 tiikeli kernel: ata2: reset tp1 mask=03 ostat0=80 ostat1=80 Oct 17 16:22:17 tiikeli kernel: ad4: stat=0x80 err=0x80 lsb=0x80 msb=0x80 Oct 17 16:22:17 tiikeli kernel: ad5: stat=0x90 err=0x90 lsb=0x90 msb=0x90 Oct 17 16:22:17 tiikeli kernel: ad4: stat=0x90 err=0x90 lsb=0x90 msb=0x90 Oct 17 16:22:17 tiikeli kernel: ad5: stat=0x90 err=0x90 lsb=0x90 msb=0x90 Oct 17 16:22:17 tiikeli kernel: ad4: stat=0x50 err=0x01 lsb=0x00 msb=0x00 Oct 17 16:22:17 tiikeli kernel: ad5: stat=0x50 err=0x01 lsb=0x00 msb=0x00 Oct 17 16:22:17 tiikeli kernel: ata2: reset tp2 mask=03 stat0=50 stat1=50 devices=0x3ATA_SLAVE,ATA_MASTER Oct 17 16:22:17 tiikeli kernel: ata2: reset tp3 devices=0x3ATA_SLAVE,ATA_MASTER Oct 17 16:22:17 tiikeli kernel: ad5: pio=0x0c wdma=0x22 udma=0x45 cable=80pin Oct 17 16:25:34 tiikeli syslogd: kernel boot file is /boot/kernel/kernel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ata problem with 13/10/2003 current
Hi, I'd like to give a try for this new code solving lost interrupts but current code still doesn't find all my slave disks. Is there anything what might help on this? Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: more panics from current (partII)
Once again our vinum build failed. This time it could do over 90% of 14 hours of work and we didn't got a panic just a hang. Only we could do while system was printing ata error messages was to press reset button. Difference to earlier situation is that we put back old 3c905 xl-card and removed 4 port dc-Znyx. At the same time we changed pci card positions. Do you still think this has nothing do ata kernel code? Tomppa login: ad6: WARNING - WRITE_DMA recovered from missing interrupt ad6: WARNING - WRITE_DMA recovered from missing interrupt ad6: WARNING - WRITE_DMA recovered from missing interrupt ad4: WARNING - WRITE_DMA recovered from missing interrupt ata2: spurious interrupt - status=0x51 error=0x84 reason=0x01 ad6: WARNING - WRITE_DMA recovered from missing interrupt ata2: spurious interrupt - status=0x51 error=0x84 reason=0x01 ata2: spurious interrupt - status=0x51 error=0x84 reason=0x01 ata2: spurious interrupt - status=0x51 error=0x84 reason=0x01 ata2: spurious interrupt - status=0x51 error=0x84 reason=0x01 ata2: spurious interrupt - status=0x51 error=0x84 reason=0x01 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[no subject]
Dag-Erling Smørgrav writes: An NMI almost certainly indicates a hardware failure. Lucas James writes: It could be a power supply on the way out. I had an old dual P-166 that rebooted misterously until I took out two CD-ROM drives I wanted for another machine. (replaced the power supply, and refitted the CDROMS, and every thing worked ok.) We're already running this system with two power supplys. All old stuff is using old power and 4 new disks were attached to new one. Because we had multiple reboots without any trace we also replaced mother board and memory though mobo type is same as before. Messages like these don't mean anything bad? ad6: WARNING - READ_DMA recovered from missing interrupt ad7: WARNING - READ_DMA recovered from missing interrupt ar: Promise check1 failed Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
more panics from current (partII)
After adding more disks to this system it dies continously. Last two traces look quite the same. Tomppa ---clipclip--- login: kernel trap 19 with interrupts disabled NMI ... going to debugger kernel: type 19 trap, code=0 Stopped at rtcintr+0x57: callrtcin db trace rtcintr(0) at rtcintr+0x57 Xfastintr8() at Xfastintr8+0x68 --- interrupt, eip = 0xc037ed02, esp = 0xcd680cdc, ebp = 0xcd680cdc --- cpu_idle(73042444,890002c0,bde8241c,c780,10c2444) at cpu_idle+0x22 idle_proc(0,cd680d48,c700,50082444,c7df) at idle_proc+0x25 fork_exit(c01ecd40,0,cd680d48) at fork_exit+0xb1 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcd680d7c, ebp = 0 --- db rtcintr(0) at rtcintr+0x57 Xfastintr8() at Xfastintr8+0x68 --- interrupt, eip = 0xc037ed02, esp = 0xcd680cdc, ebp = 0xcd680cdc --- db panic panic: from debugger Debugger(panic) Fatal trap 3: breakpoint instruction fault while in kernel mode instruction pointer = 0x8:0xc0375b34 stack pointer = 0x10:0xcd680a80 frame pointer = 0x10:0xcd680a8c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= IOPL = 0 current process = 11 (idle) Stopped at rtcintr+0x57: callrtcin db panic: from debugger Uptime: 7h17m58s Dumping 255 MB 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 Dump complete Shutting down ACPI Automatic reboot in 15 seconds - press a key on the console to abort -- Press a key on the console to reboot, -- or switch off the system now. Rebooting... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
more panics from current
Once again our current platform is unstable. Two weeks ago we had problems with kmem allocator and this was fixed by adding more memory and Dag-Erling Smørgrav still investigating those panics. Now we got different looking panic and there is core available if someone wants to take a peek on it. Tomppa ---clipclip--- kernel trap 19 with interrupts disabled NMI ... going to debugger kernel: type 19 trap, code=0 Stopped at sched_ithd+0x1d:movl$0x1,%eax db trace sched_ithd(a) at sched_ithd+0x1d Xintr10() at Xintr10+0x6c --- interrupt, eip = 0xc037ed02, esp = 0xcd680cdc, ebp = 0xcd680cdc --- cpu_idle(73042444,890002c0,bde8241c,c780,10c2444) at cpu_idle+0x22 idle_proc(0,cd680d48,c700,50082444,c7df) at idle_proc+0x25 fork_exit(c01ecd40,0,cd680d48) at fork_exit+0xb1 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcd680d7c, ebp = 0 --- db sched_ithd(a) at sched_ithd+0x1d Xintr10() at Xintr10+0x6c --- interrupt, eip = 0xc037ed02, esp = 0xcd680cdc, ebp = 0xcd680cdc --- db sched_ithd(a) at sched_ithd+0x1d Xintr10() at Xintr10+0x6c --- interrupt, eip = 0xc037ed02, esp = 0xcd680cdc, ebp = 0xcd680cdc --- db panic panic: from debugger Debugger(panic) Fatal trap 3: breakpoint instruction fault while in kernel mode instruction pointer = 0x8:0xc0375b34 stack pointer = 0x10:0xcd680a70 frame pointer = 0x10:0xcd680a7c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= IOPL = 0 current process = 11 (idle) Stopped at sched_ithd+0x1d:movl$0x1,%eax db panic: from debugger Uptime: 4h49m49s Dumping 255 MB 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 Dump complete Shutting down ACPI Automatic reboot in 15 seconds - press a key on the console to abort -- Press a key on the console to reboot, -- or switch off the system now. Rebooting... |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS drive E: is disk3 BIOS drive F: is disk4 BIOS drive G: is disk5 BIOS drive H: is disk6 BIOS drive I: is disk7 BIOS drive J: is disk8 BIOS drive K: is disk9 BIOS 639kB/261056kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Sun Sep 7 22:26:04 EEST 2003) Loading /boot/defaults/loader.conf |/boot/kernel/kernel text=0x2e50e4 data=0x2e854+0x51be8 syms=[0x4+0x39f60+0x4+0x46e72] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 9 seconds... Booting [/boot/kernel/kernel] in 8 seconds... Booting [/boot/kernel/kernel] in 7 seconds... Booting [/boot/kernel/kernel] in 6 seconds... Booting [/boot/kernel/kernel]... |/boot/kernel/acpi.ko text=0x3b1f4 /-\data=0x170c+0xec0 |syms=[0x4+0x5bf0/+0x4+0x7a42-\] |/-SMAP type=01 base= len=0009fc00 SMAP type=01 base=0009fc00 len=0400 SMAP type=02 base=000f len=0001 SMAP type=02 base= len=0001 SMAP type=01 base=0010 len=0fef SMAP type=03 base=0fff3000 len=d000 SMAP type=04 base=0fff len=3000 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 #0: Sat Sep 13 01:27:45 EEST 2003 [EMAIL PROTECTED]:/u/FreeBSD/src/sys/i386/compile/TIIKELI Preloaded elf kernel /boot/kernel/kernel at 0xc0535000. Preloaded elf module /boot/kernel/acpi.ko at 0xc05351f4. Calibrating clock(s) ... i8254 clock: 1193367 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 634775245 Hz CPU: Intel Celeron (634.78-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA T,PSE36,MMX,FXSR,SSE real memory = 268369920 (255 MB) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x0055c000 - 0x0fb49fff, 257875968 bytes (62958 pages) avail memory = 255086592 (243 MB) bios32: Found BIOS32 Service Directory header at 0xc00fb080 bios32: Entry = 0xfb4f0 (c00fb4f0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xb520 pnpbios: Found PnP BIOS data at 0xc00fbed0 pnpbios: Entry = f:bf00 Rev = 1.0 Other BIOS signatures found: null: null device, zero device mem: memory I/O Pentium Pro MTRR support enabled random: entropy source netsmb_dev: loaded npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: IntelR AWRDACPI on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x8058 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck:
Re: ufs related panic with latest current
Doug White writes: On Tue, 9 Sep 2003, Tomi Vainio - Sun Finland wrote: Tomi Vainio - Sun Finland writes: Our system died when using iozone -a to ~300G vinum partition made from four disks. Sources were cvsupped 7.9.2003. Second panic an hour later. Any good ideas how to fix this? Tomppa panic: kmem_malloc(4096): kmem_map too small: 28229632 total allocated How much RAM is in the system? What do you have maxusers set to? First maxusers was 0 then when changed it to 8. When system was still unstable we added memory from 64M to 256M. Now uptime is already 7 hours and we are waiting results. Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ufs related panic with latest current
Dag-Erling Smørgrav writes: Tomi Vainio - Sun Finland [EMAIL PROTECTED] writes: First maxusers was 0 then when changed it to 8. That's a regression. Keep it at 0. I understood that there is a bug on new kmem allocator and this was an attempt to reduce kmem allocations but it didn't help. Do you know if this is going to fixed somehow or should people just install more memory to get system stay up? Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ufs related panic with latest current
Dag-Erling Smørgrav writes: The backtrace you showed seems to indicate that the panic happened somewhere in the softupdates code, but IIRC that code has a fairly conservative built-in limit on memory consumption and degrades gracefully when it hits that limit. It's likely that something else gobbled up all available kernel memory, and the mallloc() call from softupdates was simply the straw that broke the camel's back. If you have a serial console hooked up, you could try running while :; do vmstat -m ; sleep 1 ; done Second trace didn't have anything to do with fs only fork system calls there so your expanation sounds reasonable. We probably don't see this problem again because system now has enough memory (256M). Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ufs related panic with latest current
Dag-Erling Smørgrav writes: It would be really useful to know where the fault lies. We might even (God forbid!) figure out a way to fix it. You can easily force the system to boot with less than the full amount of memory by setting hw.physmem to e.g. 64m in /boot/loader.conf or at the loader prompt. If you could just give instructions what you wanna get when system panics I might be able to persuade the other that we should crash our system once more. What scripts should we run continously until system panics? What you want to check with kdb after system panics? Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ufs related panic with latest current
Our system died when using iozone -a to ~300G vinum partition made from four disks. Sources were cvsupped 7.9.2003. Tomppa kmem_malloc(8192): kmem_map too small: 28229632 total allocated db trace Debugger(c03cc728,c0429ce0,c03db0bd,ca6c4800,100) at Debugger+0x54 panic(c03db0bd,1000,1aec000,ca6c4830,c15ee720) at panic+0xd5 kmem_malloc(c082f0b0,1000,402,ca6c48a8,c034d1c5) at kmem_malloc+0x100 page_alloc(c083a9a0,1000,ca6c4893,402,c1416640) at page_alloc+0x27 slab_zalloc(c083a9a0,502,0,c03463cb,c0934738) at slab_zalloc+0xc5 uma_zone_slab(c083a9a0,502,c288c000,c24f8c90,4) at uma_zone_slab+0xe8 uma_zalloc_bucket(c083a9a0,502,c24f52a8,c17557fc,c24f8b60) at uma_zalloc_bucket+ 0x185 uma_zalloc_arg(c083a9a0,0,502,0,c083a9a0) at uma_zalloc_arg+0x2c7 malloc(3c,c0407640,502,0,1a180) at malloc+0x5c newallocindir(c1a0ae38,38e,1a180,0,0) at newallocindir+0x37 softdep_setup_allocindir_page(c1a0ae38,39a,0,c2516ae8,38e) at softdep_setup_allo cindir_page+0x3d ffs_balloc_ufs1(c17557fc,e68000,0,4000,c146a500) at ffs_balloc_ufs1+0xee9 ffs_write(ca6c4bc4,20002,c15ee720,0,ca6c4c70) at ffs_write+0x447 vn_write(c16b3594,ca6c4c70,c146a500,0,c15ee720) at vn_write+0x233 dofilewrite(c15ee720,c16b3594,3,810,8) at dofilewrite+0xf8 write(c15ee720,ca6c4d10,c,c15ee720,3) at write+0x6e syscall(4002f,2817002f,bfbf002f,8,bfbff7c0) at syscall+0x2b0 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (4, FreeBSD ELF32, write), eip = 0x280e5b3f, esp = 0xbfbff70c, ebp = 0xbfbff728 --- db 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 #7: Mon Sep 8 17:09:29 EEST 2003 Preloaded elf kernel /boot/kernel/kernel at 0xc04ec000. Calibrating clock(s) ... i8254 clock: 1193374 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 601365089 Hz CPU: Intel Celeron (601.37-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 67108864 (64 MB) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x00513000 - 0x03eb9fff, 60452864 bytes (14759 pages) avail memory = 59953152 (57 MB) bios32: Found BIOS32 Service Directory header at 0xc00fb080 bios32: Entry = 0xfb4f0 (c00fb4f0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xb520 pnpbios: Found PnP BIOS data at 0xc00fbed0 pnpbios: Entry = f:bf00 Rev = 1.0 Other BIOS signatures found: random: entropy source netsmb_dev: loaded null: null device, zero device mem: memory I/O Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface pci_open(1):mode 1 addr port (0x0cf8) is 0x8058 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00fde70 PCI-Only Interrupts: 5 10 11 12 Location Bus Device Pin Link IRQs slot 1 0 19A 0x62 3 4 5 7 9 10 11 12 14 15 slot 1 0 19B 0x63 3 4 5 7 9 10 11 12 14 15 slot 1 0 19C 0x60 3 4 5 7 9 10 11 12 14 15 slot 1 0 19D 0x61 3 4 5 7 9 10 11 12 14 15 slot 2 0 17A 0x60 3 4 5 7 9 10 11 12 14 15 slot 2 0 17B 0x61 3 4 5 7 9 10 11 12 14 15 slot 2 0 17C 0x62 3 4 5 7 9 10 11 12 14 15 slot 2 0 17D 0x63 3 4 5 7 9 10 11 12 14 15 slot 3 0 15A 0x61 3 4 5 7 9 10 11 12 14 15 slot 3 0 15B 0x63 3 4 5 7 9 10 11 12 14 15 slot 3 0 15C 0x62 3 4 5 7 9 10 11 12 14 15 slot 3 0 15D 0x60 3 4 5 7 9 10 11 12 14 15 slot 4 0 13A 0x62 3 4 5 7 9 10 11 12 14 15 slot 4 0 13B 0x63 3 4 5 7 9 10 11 12 14 15 slot 4 0 13C 0x60 3 4 5 7 9 10 11 12 14 15 slot 4 0 13D 0x61 3 4 5 7 9 10 11 12 14 15 slot 5 0 11A 0x63 3 4 5 7 9 10 11 12 14 15 slot 5 0 11B 0x60 3 4 5 7 9 10 11 12 14 15 slot 5 0 11C 0x61 3 4 5 7 9 10 11 12 14 15 slot 5 0 11D 0x62 3 4 5 7 9 10 11 12 14 15 slot 6 09A 0x61 3 4 5 7 9 10 11 12 14 15 slot 6 09B 0x60 3 4 5 7 9 10 11 12 14 15 slot 6 09C 0x63 3 4 5 7 9 10 11 12 14 15 slot 6 09D 0x62 3 4 5 7 9 10 11 12 14 15 slot 7 08A 0x62 3 4 5 7 9 10 11 12 14 15 slot 7 08B 0x63 3 4 5 7 9 10 11 12 14 15 slot 7 08C 0x60 3 4 5 7 9 10 11 12 14 15 slot 7 08D 0x61 3 4 5 7 9 10 11 12 14 15 embedded07A 0x60 3 4 5 7 9 10 11 12 14 15 embedded07B 0x61 3 4 5 7 9 10 11 12 14 15 embedded07C 0x62 3 4 5 7 9 10 11 12 14 15 embedded07
ufs related panic with latest current
Tomi Vainio - Sun Finland writes: Our system died when using iozone -a to ~300G vinum partition made from four disks. Sources were cvsupped 7.9.2003. Second panic an hour later. Any good ideas how to fix this? Tomppa panic: kmem_malloc(4096): kmem_map too small: 28229632 total allocated trace Debugger(c03cc728,c0429ce0,c03db0bd,ca3c6a80,100) at Debugger+0x54 panic(c03db0bd,1000,1aec000,ca3c6ab0,ca3c6aa0) at panic+0xd5 kmem_malloc(c082f0b0,1000,2,ca3c6b28,c034d1c5) at kmem_malloc+0x100 page_alloc(c083aee0,1000,ca3c6b13,2,0) at page_alloc+0x27 slab_zalloc(c083aee0,102,c09fc900,8108000,ca3c6cb8) at slab_zalloc+0xc5 uma_zone_slab(c083aee0,102,ca3c6bbf,ca3c6bc0,a4) at uma_zone_slab+0xe8 uma_zalloc_bucket(c083aee0,102,0,f,1) at uma_zalloc_bucket+0x185 uma_zalloc_arg(c083aee0,0,102,ca3c6bfc,c083aee0) at uma_zalloc_arg+0x2c7 malloc(adc,c03f8480,102,384,384) at malloc+0x5c sigacts_alloc(c0429b00,0,0,280f3000,c026af9d) at sigacts_alloc+0x25 fork1(c1224be0,14,0,ca3c6ccc,c022c226) at fork1+0x7ab fork(c1224be0,ca3c6d10,2,c,0) at fork+0x2b syscall(2f,2f,2f,0,8108000) at syscall+0x2b0 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (2, FreeBSD ELF32, fork), eip = 0x807c3a7, esp = 0xbfbffb5c, ebp = 0 xbfbffb88 --- db ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Martin Blapp writes: Hi, DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 212.226.167.254 bound to 212.226.167.247 -- renewal in 228123 seconds. So the first time it works ? You get an IP here ... an0: Found Link on interface DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on an0 to 255.255.255.255 port 67 interval 15 No DHCPOFFERS received. No working leases in persistent database - sleeping. Why don't you get an IP here ? Does the server see your requests ? If not, the an0 driver is broken for your card. IMHO it's not dhclient fault here. Now I tested this at work with ISC DHCPD V3.0.1rc9 and it works just fine. For some reason Cisco dhcp server doesn't like FreeBSD anymore if connect comes from an0 driver :-) Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Martin Blapp writes: Hi, Now I tested this at work with ISC DHCPD V3.0.1rc9 and it works just fine. with the freebsd dhclient, or a unmodified V3.0.1rc9 one ? For some reason Cisco dhcp server doesn't like FreeBSD anymore if connect comes from an0 driver :-) Can you test the V3.0.1rc9 one at home too ? I've to clarify this a little. I just used different dhcp server so FreeBSD side was always using the same latest dhclient cvsupped week ago. ISC dhcp server works with an0 and em0 Cisco dhcp server works with em0 but not with an0 Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Doug Ambrisko writes: I assume you are using a pccard version. It only a problem newer firmware. It works ... just noisy! You can try this patch to -current that should make it quiet. There is a bug with -current and setting the TX speed that I need to work on. Looks like things changed in the wlan module. I may commit this but there is an issue with the mpi-350 support. They changed the programing paradigm and after 14 packets the TX engine stalls. I'm still working on tweaks to that. I had hoped to get that working and commit all of this. Let me know how this works. It should just work. I was ready to say that it's not working but then ipv6 came up automatically. I didn't look this before but now it looks that dhclient don't get address but if manually set v4 address it works. I've to check how it works with older kernel because until now I only checked that I didn't get address from dhcp. Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Martin Blapp writes: How old is your CURRENT installation ? Can you run dhclient in verbose mode and in foreground (-d -v) and maybe compile if with -DDEBUG ? I've supped current on last Saturday. Here are debug logs and how Cisco sees the situation. Windows XP debug from Cisco is quite different. Tomppa *** em0 *** Script started on Tue Aug 19 21:10:58 2003 phb:~(1)# ifconfig -a fwe0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::39ff:fe34:7ff2%fwe0 prefixlen 64 scopeid 0x1 ether 02:00:39:34:7f:f2 ch 1 dma 0 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet6 fe80::208:dff:feda:ec61%em0 prefixlen 64 scopeid 0x2 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 ether 00:08:0d:da:ec:61 media: Ethernet autoselect status: no carrier lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 phb:~(2)# dhclient -d -v em0 Internet Software Consortium DHCP Client V3.0.1rc11 Copyright 1995-2002 Internet Software Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP Listening on BPF/em0/00:08:0d:da:ec:61 Sending on BPF/em0/00:08:0d:da:ec:61 Sending on Socket/fallback em0: Polling interface state em0: client state of 2 em0: link = 1 em0: Found Link on interface em0: Polling interface state em0: client state of 2 em0: link = 1 DHCPREQUEST on em0 to 255.255.255.255 port 67 em0: Polling interface state em0: client state of 1 em0: link = 1 DHCPREQUEST on em0 to 255.255.255.255 port 67 em0: Polling interface state em0: client state of 1 em0: link = 1 em0: Polling interface state em0: client state of 1 em0: link = 1 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 10 DHCPOFFER from 212.226.167.254 DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 212.226.167.254 bound to 212.226.167.247 -- renewal in 228123 seconds. em0: Polling interface state em0: client state of 5 em0: link = 1 em0: Polling interface state em0: client state of 5 em0: link = 1 ^C phb:~(3)# ifconfig -a fwe0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::39ff:fe34:7ff2%fwe0 prefixlen 64 scopeid 0x1 ether 02:00:39:34:7f:f2 ch 1 dma 0 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet6 fe80::208:dff:feda:ec61%em0 prefixlen 64 scopeid 0x2 inet 212.226.167.247 netmask 0xfff0 broadcast 212.226.167.255 ether 00:08:0d:da:ec:61 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 phb:~(4)# Script done on Tue Aug 19 21:12:19 2003 *** an0 *** Script started on Tue Aug 19 21:13:40 2003 phb:~(1)# ifconfig -a fwe0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::39ff:fe34:7ff2%fwe0 prefixlen 64 scopeid 0x1 ether 02:00:39:34:7f:f2 ch 1 dma 0 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet6 fe80::208:dff:feda:ec61%em0 prefixlen 64 scopeid 0x2 inet 212.226.167.247 netmask 0xfff0 broadcast 212.226.167.255 inet6 2001:670:82:babe:208:dff:feda:ec61 prefixlen 64 tentative autoconf ether 00:08:0d:da:ec:61 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 an0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::240:96ff:fe38:56e7%an0 prefixlen 64 scopeid 0x4 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 ether 00:40:96:38:56:e7 media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) status: associated ssid AsOlA 1:AsOlA stationname phb channel 6 authmode OPEN powersavemode CAM powersavesleep 200 wepmode ON weptxkey 1 wepkey 1:128-bit phb:~(2)# dhclient -d -v an0 Device an0 has 802.11 Internet Software Consortium DHCP Client V3.0.1rc11 Copyright 1995-2002 Internet Software Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP Device an0 has 802.11 Listening on BPF/an0/00:40:96:38:56:e7 Sending on BPF/an0/00:40:96:38:56:e7 Sending on Socket/fallback an0: Polling interface state an0: client state of 2 an0: link = 1 an0: Found Link on interface DHCPDISCOVER on an0 to
Re: an driver / Cisco Aironet 340 stopped working
Martin Blapp writes: Why don't you get an IP here ? Does the server see your requests ? If not, the an0 driver is broken for your card. IMHO it's not dhclient fault here. Martin Did you look Cisco's dump where Windows DHCPDISCOVER appears as 0100.4096.3856.e7 but FreeBSD is 0040.9638.56e7? Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Peter Radcliffe writes: Have you got recent firmware on the cisco card ? The newer windows driver will helpfully upgrade it for you silently. If it has upgraded, downgrade it. The freebsd driver doesn't yet work with the new firmware. Cisco have changed the operation of the card with newer firmware and havn't released docs on working with the newer firmware. [EMAIL PROTECTED] writes: Don't know if anyone replied yet since I don't subscribe to freebsd-current, but I had to add the following line to my /boot/loader.conf file. hw.pci.allow_unsupported_io_range=1 I've tried multiple old firmwares and this loader.conf tweak but no luck yet. Can you say what was the last working firmware? Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: an driver / Cisco Aironet 340 stopped working
Peter Radcliffe writes: Tomi Vainio - Sun Finland [EMAIL PROTECTED] probably said: Peter Radcliffe writes: Cisco have changed the operation of the card with newer firmware and havn't released docs on working with the newer firmware. I've tried multiple old firmwares and this loader.conf tweak but no luck yet. Can you say what was the last working firmware? I don't have any 340 cards, just 350 cards, so no. Firmware files are the same for both cards or that's my thought from this filename. 350-340-PCMCIA-LMC-PCI-v52017.exe Tomppa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Fxtv DGA mode doesn't work anymore
Something has changed during last week because my Fxtv stopped working in DGA mode. I'm back running old kernel so any clues what might cause this? Tomppa FreeBSD 5.1-CURRENT #3: Sun Aug 10 00:57:18 EEST 2003 FreeBSD 5.1-CURRENT #4: Sat Aug 16 21:17:19 EEST 2003 ***clip clip*** 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 #3: Sun Aug 10 00:57:18 EEST 2003 [EMAIL PROTECTED]:/u/F/local/sup/5.0/sys/i386/compile/CAT acpi_alloc_wakeup_handler: unable to allocate wake memory Preloaded elf kernel /boot/kernel.old/kernel at 0xc053a000. Calibrating clock(s) ... i8254 clock: 1193190 Hz Timecounter i8254 frequency 1193190 Hz Calibrating TSC clock ... TSC clock: 400913881 Hz CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU) Origin = GenuineIntel Id = 0x653 Stepping = 3 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 536805376 (511 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00564000 - 0x1f6b1fff, 521461760 bytes (127310 pages) avail memory = 514416640 (490 MB) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 bios32: Found BIOS32 Service Directory header at 0xc00fdb60 bios32: Entry = 0xfdb70 (c00fdb70) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xdb91 pnpbios: Found PnP BIOS data at 0xc00f7a30 pnpbios: Entry = f:74be Rev = 1.0 Other BIOS signatures found: null: null device, zero device mem: memory I/O Pentium Pro MTRR support enabled SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff acpi0: AMIINT on motherboard ACPI-1287: *** Error: Method execution failed [\\_SB_.NRTH.SBRG.PS2M._STA] (Node 0xc1bbb9a0), AE_AML_REGION_LIMIT ACPI-0175: *** Error: Method execution failed [\\_SB_.NRTH.SBRG.PS2M._STA] (Node 0xc1bbb9a0), AE_AML_REGION_LIMIT pci_open(1):mode 1 addr port (0x0cf8) is 0x8058 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) pcibios: BIOS version 2.10 AcpiOsDerivePciId: bus 0 dev 7 func 0 acpi0: power button is handled as a fixed feature programming model. ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 6, width = 4 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 Timecounter ACPI-safe frequency 3579545 Hz AcpiOsDerivePciId: bus 0 dev 0 func 0 ACPI-1287: *** Error: Method execution failed [\\_SB_.NRTH.SBRG.PS2M._STA] (Node 0xc1bbb9a0), AE_AML_REGION_LIMIT ACPI-0175: *** Error: Method execution failed [\\_SB_.NRTH.SBRG.PS2M._STA] (Node 0xc1bbb9a0), AE_AML_REGION_LIMIT acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) acpi_cpu0: CPU port 0x530-0x537 on acpi0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) acpi_cpu1: CPU port 0x530-0x537 on acpi0 pcib0: ACPI Host-PCI bridge port 0x440-0x44f,0x400-0x43f,0xcf8-0xcff on acpi0 initial configuration before setting priority for links before fixup boot-disabled links - after fixup boot-disabled links -- arbitrated configuration - pci0: ACPI PCI bus on pcib0 pci0: physical bus=0 map[10]: type 3, range 32, base e800, size 26, enabled found- vendor=0x8086, dev=0x7190, revid=0x02 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x2210, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found- vendor=0x8086, dev=0x7191, revid=0x02 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x011f, statreg=0x0220, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x88 (34000 ns), maxlat=0x00 (0 ns) found- vendor=0x8086, dev=0x7110, revid=0x02 bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x010f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base
an driver / Cisco Aironet 340 stopped working
I've used my Cisco WLAN with Toshiba Portege 3440 couple years but now it's broken. I just upgraded to new Toshiba Tecra M1 and reinstalled FreeBSD there and now I get an0: record length mismatch -- expected 430, got 440 for Rid ff68 errors. I already tried with old laptop with latest kernel and old kernel from Jun 26th but it's also broken there so I cannot say who long this has been broken. Tomppa fwe0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::39ff:fe34:7ff2%fwe0 prefixlen 64 scopeid 0x1 ether 02:00:39:34:7f:f2 ch 1 dma 0 em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet6 fe80::208:dff:feda:ec61%em0 prefixlen 64 scopeid 0x2 inet 212.226.167.247 netmask 0xfff0 broadcast 212.226.167.255 inet6 2001:670:82:babe:208:dff:feda:ec61 prefixlen 64 tentative autoconf ether 00:08:0d:da:ec:61 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 an0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::240:96ff:fe38:56e7%an0 prefixlen 64 scopeid 0x4 ether 00:40:96:38:56:e7 media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) status: associated ssid AsOlA 1:AsOlA stationname phb channel 6 authmode OPEN powersavemode CAM powersavesleep 200 wepmode ON weptxkey 1 wepkey 1:128-bit 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 #3: Sat Aug 16 20:28:39 EEST 2003 [EMAIL PROTECTED]:/u/F/local/sup/5.0/sys/i386/compile/PHB acpi_alloc_wakeup_handler: unable to allocate wake memory Preloaded elf kernel /boot/kernel/kernel at 0xc065. Preloaded elf module /boot/kernel/splash_bmp.ko at 0xc06502e4. Preloaded elf module /boot/kernel/vesa.ko at 0xc0650394. Preloaded splash_image_data /boot/splash.bmp at 0xc0650440. Preloaded elf module /boot/kernel/usb.ko at 0xc0650490. Preloaded elf module /boot/kernel/ukbd.ko at 0xc0650538. Preloaded elf module /boot/kernel/ums.ko at 0xc06505e4. Preloaded elf module /boot/kernel/umass.ko at 0xc065068c. Preloaded elf module /boot/kernel/random.ko at 0xc0650738. Calibrating clock(s) ... i8254 clock: 1193183 Hz Timecounter i8254 frequency 1193183 Hz quality 0 Calibrating TSC clock ... TSC clock: 1396507980 Hz CPU: Intel(R) Pentium(R) M processor 1400MHz (1396.51-MHz 686-class CPU) Origin = GenuineIntel Id = 0x695 Stepping = 5 Features=0xa7e9f9bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE real memory = 536674304 (511 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00677000 - 0x1f692fff, 520208384 bytes (127004 pages) avail memory = 513142784 (489 MB) bios32: Found BIOS32 Service Directory header at 0xc00f0240 bios32: Entry = 0xfc0e3 (c00fc0e3) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xd641 pnpbios: Found PnP BIOS data at 0xc00f0450 pnpbios: Entry = f:9138 Rev = 1.0 pnpbios: Event flag at 510 pnpbios: OEM ID 8938f351 Other BIOS signatures found: wlan: 802.11 Link Layer null: null device, zero device mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 02 00 01 00 01 01 00 00 00 40 00 00 01 00 02 00 02 13 01 00 01 2d 01 00 01 38 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 31 mode(s) found VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc053aca0 (140) VESA: Trident CYBER 2100 VESA: TRIDENT MICROSYSTEMS INC. CYBER 2100 RXT 7.3 (16.28) random: entropy source splash: [EMAIL PROTECTED], size:787506 splash_bmp: beyond screen capacity (1024x768, 255 colors) splash_bmp: beyond screen capacity (1024x768, 255 colors) bmp_start(): splash_mode:261 splash: image decoder found: splash_bmp acpi0: TOSHIB 750 on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=33408086) pcibios: BIOS version 2.10 Using $PIR table, 8 entries at 0xc00f01a0 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded0 31A 0x62 11 embedded0 31B 0x61 11 embedded0 29A 0x60 11 embedded0 29B 0x63 11 embedded0 29C 0x62 11 embedded0 29D 0x6b 11 embedded2 11A 0x60 11 embedded2 11B 0x63 11 embedded10A 0x6a 11 embedded2 10A 0x63 11 embedded2 10B 0x60 11 embedded2 13A 0x60 11
Re: Creating bootsector file for W2k boot menu
Giorgos Keramidas writes: I have FreeBSD installed on two primary slices of my machine, as you can see from the df(1) output below. I can boot FreeBSD fine, if I copy the boot record of the slice my root partition lives in: # df / Filesystem 1K-blocksUsedAvail Capacity Mounted on /dev/ad0s1a498078 85920 37231219%/ # dd if=/dev/ad0s1 of=/root/bsdboot.bin bs=512 count=1 Then copy bsdboot.bin to a Windows partition, say in C:\BSDBOOT.BIN and add the following to the C:\BOOT.INI file: C:\BSDBOOT.BIN=FreeBSD on ad0s1 That should be all... Hi, Your idea is correct but this gives just Boot error. I need to make a boot sector which contains information that I'm booting from third physical disk. I think normally there is a value of 0x80 which means first disk. Old Makefile option changed just this value. Tomppa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Creating bootsector file for W2k boot menu
I've used Windows NT boot menu for years to boot FreeBSD from the second disk on my machines. I've used bootpart DOS program to do this but now I can't find correct way to do FreeBSD boot block for it. Earlier there was a diskid definition in some Makefile to change. How should I do this now? Tomppa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
IBM microdrive
Is anyone using IBM microdrive with latest current? Should it work? My laptop is Toshiba CT3440 running current cvsupped last weekend. My Cisco Aironet and Linksys network cards are working just fine with this new card concept. pccard0: Allocation failed for cfe 0 ata2 at port 0x100-0x10f irq 11 function 0 config 1 on pccard0 pccard0: WARNING: Resource not reserved by pccard bus device_probe_and_attach: ata2 attach returned 6 Tomppa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Build world problems in todays sources
Glenn Gombert writes: I get the following error when trying to rebuild the last couple of days... ../sys/kern/syscalls.master syscall.master : line 55: syscall number out of sync at 7 ... line is: struct rusage * rsuage ) ; } wait4 wait_args int I've seen this and if I remember anything it was sed or awk problem. Do first cd /usr/src/usr.bin/sed ; make all install and then try buildworld again. Tomppa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Still can't use keyboard with X
Hi, I have had this same problem couple months already. Last time I asked about this I didn't get any answers. I'am running latest current cvsupped during the weekend and XFree86-4.2.0 is also compiled couple hours ago. xdm and startx are otherwise just fine but I can't write anything. Everything seems to go the login process running on that same virtual terminal where my X session sits and if I kill that login my X dies. Only way to start X is to log in and run XFree86 binary, then log in from another machine and set DISPLAY=:0.0 and then run programs. Tomppa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
X don't accept anything from keyboard
I'm running current cvsupped two days ago. This time my X broke down. It don't accept anything from keyboard. Situation is same when using xdm or startx. I think last working world build was done two weeks ago. XFree86-4.2.0 was built 30.3.2002 and I already tried to built X-server from scratch but nothing changed. If I try to write something sometimes I see login process starting for ttyv0 and if I use startx and I kill this login process X-server dies. 254 v0 Rs+ 0:11.76 login -p 8`S`SÖ^Å88Ö^ÅSSÖ^Å88Ö^ÅSSÖ^Å8Ö^ÖÖ^ÖÖ^ÖÖ^ÖÖ^Ö atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 sc0: System console on isa0 sc0: VGA 4 virtual consoles, flags=0x200 Tomppa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
make buildworld fails / neqn / grog /groff
I haven't been able to build new world since Apr14 or so. I have cvsupped sources multiple times and buildworld always fails on neqn. If I remove this next it fails on grog and so on. Any good ideas what's wrong? Tomppa c++ -O -pipe -I/f/local/sup/5.0/gnu/usr.bin/groff/src/prproc/eqn/../../../../../../contrib/groff/src/preproc/eqn -I. -DHAVE_STDLIB_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_STRING_H=1 -DHAVE_STRINGS_H=1 -DHAVE_MATH_H=1 -DRET_TYPE_SRAND_IS_VOID=1 -DHAVE_SYS_NERR=1 -DHAVE_SYS_ERRLIST=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_GETPAGESIZE=1 -DHAVE_MMAP=1 -DHAVE_FMOD=1 -DHAVE_STRTOL=1 -DHAVE_GETCWD=1 -DHAVE_STRERROR=1 -DHAVE_PUTENV=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DHAVE_STRCASECMP=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRSEP=1 -DHAVE_STRDUP=1 -DSYS_SIGLIST_DECLARED=1 -I/f/local/sup/5.0/gnu/usr.bin/groff/src/preproc/eqn/../../../../../../contrib/groff/src/include -I/f/local/sup/5.0/gnu/usr.bin/groff/src/preproc/eqn/../../../src/include -D__FBSDID=__RCSID -fno-rtti -fno-exceptions -static -o eqn eqn.o main.o lex.o box.o limit.o list.o over.o text.o script.o mark.o other.o delim.o sqrt.o pile.o special.o /f/local/obj/f/local/sup/5.0/i386/f/local/sup/5.0/gnu/usr.bin/groff/src/preproc/eqn/../../../src/libs/libgroff/libgroff.a make: don't know how to make neqn. Stop *** Error code 2 Stop in /f/local/sup/5.0/gnu/usr.bin/groff/src/preproc. *** Error code 1 Stop in /f/local/sup/5.0/gnu/usr.bin/groff/src. *** Error code 1 Stop in /f/local/sup/5.0/gnu/usr.bin/groff. *** Error code 1 Stop in /f/local/sup/5.0. *** Error code 1 Stop in /f/local/sup/5.0. *** Error code 1 Stop in /f/local/sup/5.0. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make buildworld fails / neqn / grog /groff
Steve Kargl writes: On Wed, Apr 24, 2002 at 02:19:29AM +0300, Tomi Vainio - Sun Finland - wrote: I haven't been able to build new world since Apr14 or so. I have cvsupped sources multiple times and buildworld always fails on neqn. If I remove this next it fails on grog and so on. Any good ideas what's wrong? cd /usr/src/usr.bin/make make clean make depend make make install make clean make cleandepend cd /usr/src make buildworld That was it, thanks! There is nothing about this on UPDATING? What I have missed? Tomppa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current SMP status with Intel PR440FX?
Manfred Antar writes: I'm using one of these boards for about 3 years with SMP. I'm running current with a kernel from sources current as of 1/2 hour ago no problem. The cpu's I'm using are the PentiumPro Overdrive processors that intel put out. I've been using these the last 6 months, before that I was using 200mhz ones. Hi, If you compare your dmesg output to this one, does your CPU1 apic_initialize look any better than this? One those many panics we have seen this line is sometimes full of control characters. CPU: Pentium Pro (198.67-MHz 686-class CPU) SMP: CPU0 apic_initialize(): lint0: 0x0700 lint1: 0x00010400 TPR: 0x0010 SVR: 0x01ff FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x0400 TPR: 0x0010 SVR: 0x01ff SMP: CPU1 apic_initountinialg roize(ot ): from lint0: 0x00010700 lint1: 0x00010400 TPR: 0x0010 SVR: 0x01ff SMP: AP CPU #1 Launched! Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current SMP status with Intel PR440FX?
Manfred Antar writes: Here it is: CPU: Overdrive Pentium II/Pentium II Xeon/Celeron (331.11-MHz 686-class CPU) Origin = GenuineIntel Id = 0x1632 Stepping = 2 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000 cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000 io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec0 Mounting root from uSfMsP::/ dAePv /CdPaU0 s#11a Launched! Also yours looks quite funny. Tomppa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Current SMP status with Intel PR440FX?
Hi, We've tried to get my brothers dual cpu intel pr440fx up with current cvsupped two days ago. This machine has worked just fine couple years with stable but we had some problems with latest X so we also updated system to current. We've been booting this system whole day just trying different kernels but didn't have any luck. Mostly system just freezes when it tries to lauch cpu1 so bad that we can't enter debugger. Last thing to do was GENERIC kernel with SMP+APIC_IO and with this we could access debugger the first time ever. Second boot using this same kernel succeeded but now we don't have enough courage to boot it again. CPU1 apic init message looks messy. I haven't seen any problems reported smp or current mailing lists. Tomppa Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #4: Fri Mar 29 22:55:16 EET 2002 [EMAIL PROTECTED]:/u/FreeBSD/obj/u/FreeBSD/src/sys/ATOM Preloaded elf kernel /boot/kernel/kernel at 0xc054a000. Preloaded userconfig_script /boot/kernel.conf at 0xc054a0a8. Preloaded elf module /boot/kernel/splash_bmp.ko at 0xc054a0f8. Preloaded elf module /boot/kernel/vesa.ko at 0xc054a1a8. Calibrating clock(s) ... TSC clock: 198660631 Hz, i8254 clock: 1193158 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium Pro (198.67-MHz 686-class CPU) Origin = GenuineIntel Id = 0x619 Stepping = 9 Features=0xfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV real memory = 268435456 (262144K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00574000 - 0x0fff7fff, 262684672 bytes (64132 pages) avail memory = 255340544 (249356K bytes) Programming 24 pins in IOAPIC #0 SMP: CPU0 apic_initialize(): lint0: 0x0700 lint1: 0x00010400 TPR: 0x0010 SVR: 0x01ff FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000 cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000 io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec0 bios32: Found BIOS32 Service Directory header at 0xc00fd9e0 bios32: Entry = 0xfd9f0 (c00fd9f0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xda11 pnpbios: Found PnP BIOS data at 0xc00fa000 pnpbios: Entry = f:a100 Rev = 1.0 Other BIOS signatures found: null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 02 d7 74 00 c0 01 00 00 00 22 00 00 01 40 00 05 02 ec 74 00 c0 f3 74 00 c0 fe 74 00 c0 00 01 01 01 02 01 03 01 05 01 07 01 08 01 09 01 0b 01 0c 01 10 01 11 01 12 01 13 01 14 01 VESA: 24 mode(s) found VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc05472a2 (122) VESA: Matrox Graphics Inc. VESA: Matrox MILLENNIUM 00 module_register_init: MOD_LOAD (splash_bmp, 0xc053f8c8, 0) error 2 SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x0400 TPR: 0x0010 SVR: 0x01ff pci_open(1):mode 1 addr port (0x0cf8) is 0x80005848 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=12378086) npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge at pcibus 0 on motherboard pci0: physical bus=0 found- vendor=0x8086, dev=0x1237, revid=0x02 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 IOAPIC #0 intpin 18 - irq 2 Freeing (NOT implemented) redirected PCI irq 11. map[10]: type 3, range 32, base ffbe8000, size 12, enabled map[14]: type 4, range 32, base ff40, size 5, enabled map[18]: type 1, range 32, base ff80, size 20, enabled found- vendor=0x8086, dev=0x1229, revid=0x01 bus=0, slot=6, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=2 found- vendor=0x8086, dev=0x7000, revid=0x01 bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 map[20]: type 4, range 32, base ffa0, size 4, enabled found- vendor=0x8086, dev=0x7010, revid=0x00 bus=0, slot=7, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 IOAPIC #0 intpin 17 - irq 10 map[10]: type 4, range 32, base fc00, size 8, enabled map[14]: type 1, range 32, base ffbeb000, size 12, enabled found- vendor=0x9004, dev=0x8078, revid=0x00 bus=0, slot=9, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=10 IOAPIC #0 intpin 16 - irq 11 map[10]: type 1, range 32, base ffbec000, size 14, enabled map[14]: type 3, range 32, base ff00, size 23, enabled found- vendor=0x102b, dev=0x0519, revid=0x01 bus=0, slot=11, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=11
Nokia C110 WLAN
Hi, This card should be a prism2 clone and it works with Linux prism2 driver. I have tried to get this work with current but no luck yet. Jul 4 21:48:35 phb pccardd[174]: Card Nokia(C110/C111 Wireless LAN Card) [(null)] [(null)] matched Nokia (C110/C111 Wireless LAN Card) [(null)] [(null)] Jul 4 21:48:40 phb /boot/kernel/kernel: wi0: No I/O space?! Jul 4 21:48:40 phb pccardd[174]: driver allocation failed for Nokia(C110/C111 Wireless LAN Card): Device not configured card Nokia C110/C111 Wireless LAN Card config 0x1 wi ? 0x1 insert /etc/pccard_ether $device start remove /etc/pccard_ether $device stop I already tried auto and without 0x1 Configuration data for card in slot 1 Tuple #1, code = 0x1 (Common memory descriptor), length = 3 000: 00 00 ff Common memory device information: Device number 1, type No device, WPS = OFF Speed = No speed, Memory block size = 512b, 1 units Tuple #2, code = 0x1c (Other conditions for common memory), length = 4 000: 02 00 00 ff (3V card) Tuple #3, code = 0x15 (Version 1 info), length = 37 000: 07 00 4e 6f 6b 69 61 00 43 31 31 30 2f 43 31 31 010: 31 20 57 69 72 65 6c 65 73 73 20 4c 41 4e 20 43 020: 61 72 64 00 ff Version = 7.0, Manuf = [Nokia], card vers = [C110/C111 Wireless LAN Card] Tuple #4, code = 0x20 (Manufacturer ID), length = 4 000: 24 01 10 11 PCMCIA ID = 0x124, OEM ID = 0x1110 Tuple #5, code = 0x21 (Functional ID), length = 2 000: 06 00 Network/LAN adapter Tuple #6, code = 0x22 (Functional EXT), length = 2 000: 01 07 Network technology: Wireless Tuple #7, code = 0x22 (Functional EXT), length = 5 000: 02 c0 d8 a7 00 Network speed: 11 Mb/sec Tuple #8, code = 0x22 (Functional EXT), length = 2 000: 03 07 Network media: 2.4 GHz Tuple #9, code = 0x1a (Configuration map), length = 4 000: 00 02 f4 01 Reg len = 1, config register addr = 0xf4, last config = 0x2 Registers: X--- Tuple #10, code = 0x1b (Configuration entry), length = 19 000: c1 01 1d 79 55 a6 1e a6 1e b6 14 24 e5 13 5f 64 010: 30 ff ff Config index = 0x1(default) Interface byte = 0x1 (I/O) Vcc pwr: Nominal operating supply voltage: 5 x 1V Continuous supply current: 2 x 100mA, ext = 0x1e Max current average over 1 second: 2 x 100mA, ext = 0x1e Max current average over 10 ms: 3 x 100mA, ext = 0x14 Power down supply current: 2 x 1mA Wait scale Speed = 1.2 x 1 us, scaled by 10 RDY/BSY scale Speed = 5.0 x 10 ms, scaled by 10 Card decodes 4 address lines, full 8/16 Bit I/O IRQ modes: Level IRQs: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Tuple #11, code = 0x1b (Configuration entry), length = 10 000: 02 01 79 b5 1e 36 36 b6 46 24 Config index = 0x2 Vcc pwr: Nominal operating supply voltage: 3 x 1V, ext = 0x1e Continuous supply current: 3 x 100mA Max current average over 1 second: 3 x 100mA Max current average over 10 ms: 3 x 100mA, ext = 0x46 Power down supply current: 2 x 1mA Tuple #12, code = 0x14 (No link), length = 0 Tuple #13, code = 0xff (Terminator), length = 0 -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WinModem Support
Mark Santcroos writes: I have contacted the author and he made a last change in the interrupt setup. I have made a small stand alone package for -CURRENT, it holds the .c, the linux object file, a Makefile and a script to create the necessary device files. (If you want it in your kernel you can figure out yourself probably, this is just a proof of concept) http://www.ripe.net/home/mark/files/ltmdm_current_may_10.tgz It works great for me, let me know if it is not generic enough and I will apply the changes. I tried your package with Toshiba Portege 3440CT and 5.0C cvsupped last weekend. Still the same problems, no connect though it dials and ATI3 gives hard hang. Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: camcontrol stop / restart broken
Kenneth D. Merry writes: Hmm. Well, I definitely haven't seen this before. The only thing I can figure is that we got into some sort of infinite rescan loop. I don't know how spinning up the disk (or trying to) would trigger a rescan. My system has been up and running 21 hours since world rebuild and reboot. During this time I have stopped and started disk multiple times and these errors are history now. Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: camcontrol stop / restart broken
Kenneth D. Merry writes: This should be fixed as of rev 1.22 of scsi_all.c. There was an errant search and replace that caused the 'start' bit in the start/stop unit to always be set to 0 (stop). So automatic spinups wouldn't work, and 'camcontrol start' wouldn't work. Thanks, I'll test this soon. I'd still like to know when these messages are cropping up. I scanned messages files and it seems to start ~2 hours after I have tried to spin up the disk first time. Apr 28 23:01:40 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack Apr 28 23:08:10 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack Apr 29 00:49:42 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate CCB, can't continue Apr 29 14:40:00 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack Apr 29 14:44:31 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack Apr 29 16:34:04 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
WinModem Support/Learning the kernel Internals
Benjamin Close writes: Is anyone looking into converting the Linux winmodem driver ( Lucent Technologies binary object file compiled together with the linux kernel serial driver) into a freebsd device? Please check http://www.geocities.com/wtnbkysh/ . It should work under 4.2R. There is also some 5.0C patches but still some problems probably with interrupts. Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: Lucent Win Modem port 0x1c00-0x1cff,0x2f8-0x2ff mem 0xffefff00-0xffef irq 11 at device 2.0 on pci0 Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: using SHARED IRQ. Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: unable to activate interrupt in fast mode - using normal modeltmdm0: type Virtual 16550A Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: camcontrol stop / restart broken
Kenneth D. Merry writes: Can you do the following: camcontrol stop da1 camcontrol tur da1 -v [ then you can start it back up with camcontrol start ] What I want to see here is the sense information coming back from the drive when it is spun down. The new error recovery code should be doing the same thing as the old error recovery code -- sending a start unit. For some reason it isn't doing the right thing, though. cat:~(10)# camcontrol stop da1 Unit stopped successfully cat:~(11)# camcontrol tur da1 -v Unit is not ready (pass1:ahc0:0:2:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (pass1:ahc0:0:2:0): CAM Status: SCSI Status Error (pass1:ahc0:0:2:0): SCSI Status: Check Condition (pass1:ahc0:0:2:0): NOT READY asc:4,2 (pass1:ahc0:0:2:0): Logical unit not ready, initializing cmd. required field replaceable unit: 2 cat:~(12)# mount /f mount: /dev/da1s1e: Input/output error cat:~(13)# camcontrol tur da1 -v Unit is not ready (pass1:ahc0:0:2:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (pass1:ahc0:0:2:0): CAM Status: SCSI Status Error (pass1:ahc0:0:2:0): SCSI Status: Check Condition (pass1:ahc0:0:2:0): NOT READY asc:4,2 (pass1:ahc0:0:2:0): Logical unit not ready, initializing cmd. required field replaceable unit: 2 cat:~(15)# camcontrol start da1 Unit started successfully cat:~(16)# mount /f mount: /dev/da1s1e: Input/output error cat:~(17)# camcontrol devlist IBM DDRS-34560 S97B at scbus0 target 0 lun 0 (pass0,da0) SEAGATE ST32550W 0420at scbus1 target 2 lun 0 (probe0,pass1,da1) Also messages file is full of these: Apr 29 00:55:42 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue Apr 29 00:55:43 cat last message repeated 26 times Apr 29 00:57:43 cat last message repeated 359 times Apr 29 01:07:43 cat last message repeated 1793 times Apr 29 01:17:43 cat last message repeated 1794 times Apr 29 01:27:43 cat last message repeated 1793 times Apr 29 01:34:13 cat last message repeated 1122 times Apr 29 01:34:13 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue Apr 29 01:34:13 cat last message repeated 43 times Apr 29 01:36:02 cat last message repeated 322 times Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
camcontrol stop / restart broken
Hi, My source disk is quite noisy so normally I stop it after building the world and restart it once a week. Couple weeks this restart hasn't worked as before. Only way to start disk again is reboot. camcontrol stop 1:2:0 Unit stopped successfully mount /f mount: /dev/da1s1e: Input/output error tail /var/log/messages Apr 28 23:01:40 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack Apr 28 23:01:40 cat /boot/kernel/kernel: da1: reading primary partition table: error reading fsbn 0 camcontrol start 1:2:0 Unit started successfully mount /f mount: /dev/da1s1e: Input/output error ahc0: Adaptec aic7895 Ultra SCSI adapter port 0xd400-0xd4ff mem 0xefffe000-0xefffefff irq 11 at device 9.0 on pci0 aic7895C: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: Adaptec aic7895 Ultra SCSI adapter port 0xdc00-0xdcff mem 0xe000-0xefff irq 11 at device 9.1 on pci0 aic7895C: Wide Channel B, SCSI Id=7, 32/255 SCBs da1 at ahc0 bus 0 target 2 lun 0 da1: SEAGATE ST32550W 0420 Fixed Direct Access SCSI-2 device da1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 2048MB (4194995 512 byte sectors: 255H 63S/T 261C) da0 at ahc1 bus 0 target 0 lun 0 da0: IBM DDRS-34560 S97B Fixed Direct Access SCSI-2 device da0: 5.813MB/s transfers (5.813MHz, offset 15), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
modified ich sound driver for current?
Mixer stuff was modified couple days ago. Does anyone have working ich driver? I got original driver from http://www.katsurajima.seya.yokohama.jp/ich/index.en.html but now this site is dead. Does author (Katsurajima Naoto) of this driver read FreeBSD mailing lists? Could someone include this driver to current so it get updated? -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: modified ich sound driver for current?
Cameron Grant writes: i'm not happy with some of the things the driver does, so until i can modify it i won't commit it. this necessitates having hardware to test with, which i should be getting in the near future. Nice to know that someone is even thinking about what to do with this driver. Chris Knight writes: I modified the mentioned driver when newpcm got kobjified and submitted the patches back to the author. I didn't get a reply. I haven't synced up my laptop to current since about the new year, so I don't know if it works with any changes made. Rather than send the patch to the list, I'll e-mail it to anyone that asks. Your modification worked just fine and my laptop is back in business. Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ffs_valloc: dup alloc panics with stable/current
Tomi Vainio - Sun Finland - writes: We got old Mylex DAC960PD-Ultra-raid-adapter and have tried to use it with FreeBSD 4.2-stable and 5.0-current. Adapter is configured with three luns 5+5*9G, 8+8*9G (raid5) and 1+1*2G (mirrored boot disk). All 9G disks are quite old Seagate Barracuda 9 disks ST19171W. System is working quite well but under heavier load we start to get scsi errors from luns. This is not so bad but 5-30 minutes after this command system will always panic. cd /uu ; dump 0buf 126 - /w | restore xbf 126 - mode = 0100644, inum = 720391, fs = /uu panic: ffs_valloc: dup alloc Hi, I wrote about these problems two weeks ago. After this we had done lot of testing with this system and last 4 days system has been up and running. We still get scsi errors but it doesn't seem to harm system drives. Panic problem hasn't appeared since we changed mylex config. Now we are running only 8 disks on two channels and one raid5 system drive on both. Any thoughts why this works better than the old configuration? Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ffs_valloc: dup alloc panics with stable/current
Mike Smith writes: This is not so bad but 5-30 minutes after this command system will always panic. cd /uu ; dump 0buf 126 - /w | restore xbf 126 - mode = 0100644, inum = 720391, fs = /uu panic: ffs_valloc: dup alloc This looks like memory or PCI data corruption. You don't say how you're generating this load, or what the motherboard is, but I suspect that you may have hardware issues here. /w fs contains cvsupped FreeBSD source, objs and ports alltogether 1G of data. Load test is this simple "cd /uu ; dump 0buf 126 - /w | restore xbf 126 -" between two partitions. First motherboard we tried was Intel PPro 200Mhz (FX440 based I think/Natoma?). Second one is newer 633MHz Celeron system but I don't know manufacturer. One question - I assume you're not seeing any read error diagnostics from the Mylex driver (other than the disk errors?) Sometimes we have got more those scsi errors before fs panic. Wilko Bulte writes: PCI bus clock is at the nominal speed? Can be a source of interesting effects. Both motherboards are used with standard settings and older Intel PPro system don't support overclocking or other kludge stuff. Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ffs_valloc: dup alloc panics with stable/current
Mike Smith writes: First motherboard we tried was Intel PPro 200Mhz (FX440 based I think/Natoma?). Second one is newer 633MHz Celeron system but I don't know manufacturer. But the same symptoms? Have you tried replacing the controller (or even just the onboard RAM)? All but raid controller was replaced (RAM, video, net). We also have another raid controller and we are going to test it also. Also tried with and without soft updates and async io. But no other errors? In particular, nothing that looks like a "real" I/O error? This we have to double check because normally we don't stare at the console when we test this system. The problem that you're seeing looks like filesystem metadata corruption. If it's not memory/system related, it has to be in the datapath from the disks through the driver. I'm not aware of any bugs in the driver that could cause this. 8( I think old PPro system even supported ECC memory. We are getting out ideas. Maybe small 3 disk raid5 with little newer disks than we use now. Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ffs_valloc: dup alloc panics with stable/current
Mark Newton writes: sense = 3 asc = 11 asq = 0 This is not so bad but 5-30 minutes after this command system will always panic. Are you surprised? The system is complaining that it's having intermittent difficulty accessing the disk, so it shouldn't be at all surprising that you'd have disk corruption problems as a result. Start by checking your SCSI cabling and termination. Almost all SCSI problems boil down to that eventually. Sorry, but done that already. Mylex manual says this and this is how we did it. We also use force perfect terminators just to be sure evetrything works smoothly. System has complained a lot of drives 0:0 0:1 0:2 and these we had replaced twice also used low level formatting. ---clip clip--- Setting Device Termination Power All of the SCSI drives connected to the DAC960P Series should be shunted to apply power on the SCSI TERMPWR line, as well as having any of their builtin terminators disabled or removed. It is important that all drives supply termination power, so that power is applied to the SCSI bus even if drives are removed or replaced. The same rules also apply to non disk SCSI devices connected to any of the DAC960P Series SCSI channels. -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ffs_valloc: dup alloc panics with stable/current
Hi, We got old Mylex DAC960PD-Ultra-raid-adapter and have tried to use it with FreeBSD 4.2-stable and 5.0-current. Adapter is configured with three luns 5+5*9G, 8+8*9G (raid5) and 1+1*2G (mirrored boot disk). All 9G disks are quite old Seagate Barracuda 9 disks ST19171W. System is working quite well but under heavier load we start to get scsi errors from luns. sense = 4 asc = 3 asq = 0 sense = 1 asc = 3 asq = 0 sense = 3 asc = 12 asq = 0 sense = 3 asc = 11 asq = 0 This is not so bad but 5-30 minutes after this command system will always panic. cd /uu ; dump 0buf 126 - /w | restore xbf 126 - mode = 0100644, inum = 720391, fs = /uu panic: ffs_valloc: dup alloc syncing disks... 82 40 16 2 2 1 1 1 done Uptime: 29m30s mlx0: flushing cache...done mlxd0: detached mlxd1: detached mlxd2: detached -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SB128/ES1370 sound broken since 26th Oct
SB128 sound support has been broken over a week now. I don't who has made changes on 26th Oct but after these changes I can't get any sound out of my machine. Sources cvsupped 25th Oct still worked fine. Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Sound support broken after latest sup
I cvsupped latest sources two days ago and it broke my sounds. I cannot watch TV with sound anymore. Pervious kernel was built on 20.5.2000. I'm using voxware driver because it supports my old PAS16 card. How to fix this? Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Voxware audio is too fast
I'm still using old voxware driver on 5.0 current system because it is only way to get support for my Pro Audio Spectrum card. But there is one problem on playback. It's 5% too fast and it sounds annoying. If I play these same mp3 files through pcm/sbc driver everything is ok. It's also easy to measure this problem just using time command. pas0 at port 0x388 irq 10 drq 5 on isa0 snd0: Pro AudioSpectrum 16 rev 0 pas0: driver is using old-style compatability shims mss_detect, busy still set (0xff) sbc0: Soundblaster at port 0x220-0x22f irq 7 drq 1 on isa0 pcm1: SB DSP 2.00 on sbc0 pcm: setmap 1a000, 2000; 0xc5cfa000 - 1a000 pcm: setmap 1c000, 2000; 0xc5cfc000 - 1c000 Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
