Re: My ATAPI CD not come ready
On Tue, Jan 25, 2000 at 09:40:11AM +0100, Anders Andersson wrote: I have the same problem: [anders@enterprise:anders] $ dmesg | grep ata ata-pci0: Intel PIIX3 ATA controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata-isa0: already registered as ata0 ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed -- Anders Andersson [EMAIL PROTECTED] Sanyusan International AB http://www.sanyusan.se/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message With current cvsupped an hour ago, I am seeing this. With current about a month old things are perfect. (and have been for many months on ata driver) Hardware is SMP (2*PIII-450) BX chipset motherboard, second bus has IDE hard disk as primary and atapi CD as secondary.I have never prior to this seen a failure to probe. The primary drive runs fine. I get exactly the same error message on the recent kernel. Normal (correct boot messages) Jan 25 20:08:13 rose /kernel: Copyright (c) 1992-1999 The FreeBSD Project. Jan 25 20:08:13 rose /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jan 25 20:08:13 rose /kernel: The Regents of the University of California. All rights reserved. Jan 25 20:08:13 rose /kernel: FreeBSD 4.0-CURRENT #1: Tue Dec 28 17:21:58 CST 1999 Jan 25 20:08:13 rose /kernel: [EMAIL PROTECTED]:/usr/src/sys/compile/ROSE Jan 25 20:08:13 rose /kernel: Timecounter "i8254" frequency 1193182 Hz Jan 25 20:08:13 rose /kernel: CPU: Pentium III/Xeon (451.02-MHz 686-class CPU) Jan 25 20:08:13 rose /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Jan 25 20:08:13 rose /kernel: Features=0x387fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,XMM Jan 25 20:08:13 rose /kernel: real memory = 268423168 (262132K bytes) Jan 25 20:08:13 rose /kernel: avail memory = 256626688 (250612K bytes) Jan 25 20:08:13 rose /kernel: Programming 24 pins in IOAPIC #0 Jan 25 20:08:13 rose /kernel: FreeBSD/SMP: Multiprocessor motherboard Jan 25 20:08:13 rose /kernel: cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 Jan 25 20:08:13 rose /kernel: cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 Jan 25 20:08:13 rose /kernel: io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Jan 25 20:08:13 rose /kernel: Preloaded elf kernel "kernel" at 0xc03a. Jan 25 20:08:13 rose /kernel: Pentium Pro MTRR support enabled Jan 25 20:08:13 rose /kernel: md0: Malloc disk Jan 25 20:08:13 rose /kernel: npx0: math processor on motherboard Jan 25 20:08:13 rose /kernel: npx0: INT 16 interface Jan 25 20:08:13 rose /kernel: pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard Jan 25 20:08:13 rose /kernel: pci0: PCI bus on pcib0 Jan 25 20:08:13 rose /kernel: pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 Jan 25 20:08:13 rose /kernel: pci1: PCI bus on pcib1 Jan 25 20:08:13 rose /kernel: vga-pci0: Matrox model 051f graphics accelerator irq 16 at device 0.0 on pci1 Jan 25 20:08:13 rose /kernel: isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 Jan 25 20:08:13 rose /kernel: isa0: ISA bus on isab0 Jan 25 20:08:13 rose /kernel: ata-pci0: Intel PIIX4 ATA controller at device 4.1 on pci0 Jan 25 20:08:13 rose /kernel: ata-pci0: Busmastering DMA supported Jan 25 20:08:13 rose /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Jan 25 20:08:13 rose /kernel: ata1 at 0x0170 irq 15 on ata-pci0 Jan 25 20:08:13 rose /kernel: pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 4.2 Jan 25 20:08:13 rose /kernel: Timecounter "PIIX" frequency 3579545 Hz Jan 25 20:08:13 rose /kernel: intpm0: Intel 82371AB Power management controller at device 4.3 on pci0 Jan 25 20:08:13 rose /kernel: intpm0: I/O mapped e800 Jan 25 20:08:13 rose /kernel: intpm0: intr IRQ 9 enabled revision 0 Jan 25 20:08:13 rose /kernel: smbus0: System Management Bus on intsmb0 Jan 25 20:08:13 rose /kernel: smb0: SMBus general purpose I/O on smbus0 Jan 25 20:08:13 rose /kernel: intpm0: PM I/O mapped e400 Jan 25 20:08:13 rose /kernel: bktr0: BrookTree 848A irq 19 at device 9.0 on pci0 Jan 25 20:08:13 rose /kernel: iicbb0: I2C generic bit-banging driver on bti2c0 Jan 25 20:08:13 rose /kernel: iicbus0: Philips I2C bus on iicbb0 master-only Jan 25 20:08:13 rose /kernel: smbus1: System Management Bus on bti2c0 Jan 25 20:08:13 rose /kernel: smb1: SMBus general purpose I/O on smbus1 Jan 25 20:08:13 rose /kernel: bktr0: Hauppauge Model 60104 C VM Jan 25 20:08:13 rose /kernel: bktr0: Detected a MSP3400C-C6 at 0x80 Jan 25 20:08:13 rose /kernel: Hauppauge WinCast/TV, Philips PAL I tuner, msp3400c stereo. Jan 25 20:08:13 rose /kernel: fxp0: Intel EtherExpress Pro 10/100B Ethernet irq 16 at device 10.0 on pci0 Jan 25 20:08:13 rose /kernel: fxp0: Ethernet address 00:90:27:3c:03:4d Jan 25 20:08:13 rose /kernel: fxp0: supplying EUI64: 00:90:27:ff:fe:3c:03:4d Jan 25 20:08:13 rose
Re: ESS 1868 and DSP_BUFFSIZE
On Sun, Jan 09, 2000 at 06:16:30AM -0500, Donn Miller wrote: It looks like the ESS 1868 is working OK now with the DSP_BUFFSIZE set to 8192. Before, it wouldn't work unless I set this value to (65536 - 256), which was the original value, I believe. So, why does the ESS work OK now with a buffer size of 8192? And how is this buffersize an advantage over (65536 - 256)? Everything seems to be working great for the ESS 1868 now, but I was just wondering... While it is much better than it was (sound happens, and the machine doesn't reboot :-), I am still seeing a repeat of the last few seconds of some audio with the ESS 1869 chipset. This seems to occur using waveplay (.wav files) and au files (cat *.au /dev/dsp). I can't pick any pattern to it, although it is consistent on a per file basis. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Ouch! Something broke (possibly ATA)
On Tue, Jan 04, 2000 at 09:06:14AM +, Alex wrote: Today's -current: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #21: Tue Jan 4 08:00:34 GMT 2000 Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (333.35-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 134217728 (131072K bytes) avail memory = 126709760 (123740K bytes) Preloaded elf kernel "kernel.test" at 0xc02e2000. VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc0294fa0 (140) VESA: CHIPS 6x555 Super VGA npx0: math processor on motherboard npx0: INT 16 interface apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 isab0: Intel 82371AB PCI to ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 ata-pci0: Intel PIIX4 ATA-33 controller at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 1.2 chip1: Intel 82371AB Power management controller at device 1.3 on pci0 vga-pci0: Chips Technologies model 00e5 VGA-compatible display device at device 6.0 on pci0 pcic-pci0: TI PCI-1131 PCI-CardBus Bridge at device 7.0 on pci0 pcic-pci1: TI PCI-1131 PCI-CardBus Bridge at device 7.1 on pci0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 pcic0: VLSI 82C146 at irq 10 on isa0 pccard0: PC Card bus -- kludge version on pcic0 pccard1: PC Card bus -- kludge version on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: not probed (disabled) sio2: configured irq 3 not in bitmap of probed irqs 0 sio2 at port 0x3e8-0x3ef irq 3 on isa0 sio2: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 pcm0: CS4231 at port 0x530-0x537,0x538-0x539 irq 5 drq 1 flags 0xa110 on isa0 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xbff21000 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0214ffe stack pointer = 0x10:0xc02f6b58 frame pointer = 0x10:0xc02f6b8c 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) interrupt mask = net tty bio cam trap number = 12 panic: page fault Uptime: 0s Automatic reboot in 15 seconds - press a key on the console to abort % nm /kernel.test | grep c0214f c0214f68 T bus_dmamap_load c0214f28 T bus_dmamem_free Would you like to know more? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message I got exactly this from compiling a kernel (accidentally) with the development port of GCC. I am not sure if the same feature exists with the latest GCC imported into the tree, but as of two days ago it didn't. I am currently doing a make world on a spare machine to check it with the latest compiler. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
IPFW as built in kernel feature seems broken.
Hi, since rougly the time the recent changes were commited, I have been unable to compile a kernel with the IPFW funtionality build in. It still works as an KLD, but I would prefer not to run it this way. (It bothers me that if something caused it to be unloaded, or to fail to load, the machine could and would quite cheerfully pass everything.) Is this a transient thing, or is this a permanent change ? I have cvsupped and rebuilt quite a few times, the last only about 30 minutes ago, and it still appears to be the same. Thankyou for any feeback you can give me on this. On a brighter note, my machine is running fine with a fresh kernel, dual PII-350, vr0, fxp0 lan cards, bt848 video capture card and matrox millenium II agp card. No problems at all. (Other than the IPFW thing) Sorry if this has nothing to do with these changes, I did post a query a couple of days back, but there has been no response to this. Thankyou. Regards, Ian West. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
IPFW does not seem to work except as kld on recent builds (last day or so)
Hi, I noticed that IPFW as a built in kernel options quietly doesn't seem to work, no compile errors, but the resultant kernel passes evrything and does not appear to contain ipfw funtionality. ipfw -a l returns ipfw: getsockopt(IP_FW_GET): Protocol not available. kldload ipfw and it all works fine. Is the intention for it to longer be a available except as a kld module ? Thankyou for any feedback. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Atime not set on execution ?
Is it normal for atime not to be set on execution of a file ? I should have thought this would class as an access ? (I do not have the filesystem mounted -o noatime :-) This may be questions, but I am running current... Thankyou. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Atime not set on execution ?
Bruce Evans wrote: Is it normal for atime not to be set on execution of a file ? I should have thought this would class as an access ? It's normal in FreeBSD, although this breaks POSIX.1 conformance. Bruce Thanks for the response, there isn't per chance an option to turn this on is there ? I am doing some maintenance on a few machines, and it would be really nice to know when some programs were last run, this seems like the ideal way to do it ? Is this a fault, or has this been done for some good reason ? Is it something I should try and fix ? Thanks for any feedback To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
