ata driver question..
I made world and build a new kernel on Friday the 24th, and later that evening, I got these: Sep 24 18:00:33 jabberwock /kernel: ata0-master: ad_timeout: lost disk contact - resetting Sep 24 18:00:33 jabberwock /kernel: ata0: resetting devices .. done Today morning, I found my machine "hung" (couldn't kill old processes, couldn't start new ones). Any ideas? Here's the kernel config: # # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # http://www.FreeBSD.ORG/> # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.118 1998/09/18 00:46:40 mjacob Exp $ machine "i386" cpu "I686_CPU" ident "J38" maxusers128 options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE#Allow users to grab the console # Allow the FFS to use Softupdates technology. # To do this you need to copy the two files # /sys/ufs/ffs/softdep.h and /sys/ufs/ffs/ffs_softdep.c # from /usr/src/contrib/sys/softupdates # and understand the licensing restrictions. # You should also check on the FreeBSD website for newer versions. optionsSOFTUPDATES controller isa0 controller pci0 controller fdc0at isa? port "IO_FD1" irq 6 drq 2 diskfd0 at fdc0 drive 0 controller ata0 device atadisk0# ATA disk drives device atapicd0# ATAPI CDROM drives #device atapifd0# ATAPI floppy drives #device atapist0# ATAPI tape drives controller ahc0 device pass0 controller scbus0 device da0 # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0at atkbdc? irq 12 device vga0at isa? port ? conflicts device sc0 at isa? device npx0at nexus? port IO_NPX irq 13 device sio0at isa? port "IO_COM1" flags 0x10 irq 4 pseudo-device loop pseudo-device ether pseudo-device pty 48 pseudo-device bpf 2 #Berkeley packet filter #pseudo-device splash # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # options SYSVSHM options SYSVSEM options SYSVMSG # sound card stuff controller pnp0 #device pcm0 at nexus ? port? irq 5 drq 1 device pcm0 options USER_LDT#allow user-level control of i386 ldt options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L -- Viren Shah | IF YOU CAN'T BE GOOD, BE LOUD. [EMAIL PROTECTED] | -- Frank Hill RST, Inc| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata driver question..
>>>>> "Soren" == Soren Schmidt <[EMAIL PROTECTED]> writes: Soren> It seems Viren R. Shah wrote: >> >> I made world and build a new kernel on Friday the 24th, and later that >> evening, I got these: >> >> Sep 24 18:00:33 jabberwock /kernel: ata0-master: ad_timeout: lost disk contact - >resetting >> Sep 24 18:00:33 jabberwock /kernel: ata0: resetting devices .. done Soren> Be sure you have the latest, I fixed a couble of bugs in the timeout Soren> code on friday, you shoudl have versions: That turned out to be the problem -- I cvsupped at an inconvenient time. Thanks. Soren> -Søren Note to self: cvsup and rebuild world before posting to -current. Viren -- Viren R. Shah | "For oft, when on my couch I lie [EMAIL PROTECTED] | In vacant or in pensive mood, Research Associate | They flash upon that inward eye RST Inc. | Which is the bliss of solitude;" --WW To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PS/2 mouse (psm0) is not detected with recent -current
nown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) ata-: ata0 already exists, using ata2 instead ata-: ata1 already exists, using ata3 instead atkbdc-: atkbdc0 already exists, using atkbdc1 instead fdc-: fdc0 already exists, using fdc1 instead ppc-: ppc0 already exists, using ppc1 instead sio-: sio0 already exists, using sio1 instead sio-: sio1 already exists, using sio2 instead sio-: sio2 already exists, using sio3 instead sio-: sio3 already exists, using sio4 instead Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 sc-: sc0 already exists, using sc1 instead vga-: vga0 already exists, using vga1 instead isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: at iomem 0xc-0xc,0xd-0xd07ff on isa0 ata2 failed to probe at port 0x1f0 irq 14 on isa0 ata3 failed to probe at port 0x170 irq 15 on isa0 atkbdc1: failed to probe at port 0x60 on isa0 fdc1: cannot reserve I/O port range (6 ports) fdc1 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 pcic0 failed to probe on isa0 ppc1: parallel port found at 0x378 ppc1: cannot reserve I/O port range ppc1: failed to probe at port 0x378-0x37f irq 7 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio1 failed to probe at port 0x3f8 irq 4 flags 0x10 on isa0 sio2: configured irq 3 not in bitmap of probed irqs 0 sio2: irq maps: 0x1 0x1 0x1 0x1 sio2: probe failed test(s): 0 1 2 4 6 7 9 sio2 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio3: not probed (disabled) sio4: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa 0x2 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc1: no video adapter found. sc1: failed to probe on isa0 vga1: failed to probe on isa0 isa_probe_children: probing PnP devices BIOS Geometries: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: faith0 attached bpf: lo0 attached ad0: success setting UDMA4 on Intel chip Creating DISK ad0 ad0: ATA-5 disk at ata0-master ad0: 28629MB (58633344 sectors), 58168 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA66 ad0: piomode=4 dmamode=2 udmamode=4 cblid=1 ata1-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 ata1-master: success setting PIO4 on generic chip acd0: CDROM drive at ata1 as master acd0: read 8250KB/s (32KB/s), 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Writes: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked, lock protected acd0: Medium: no/blank disc Mounting root from ufs:/dev/ad0s1a ad0s1: type 0xa5, start 63, end = 58621184, size 58621122 : OK start_init: trying /sbin/init splash: image decoder found: logo_saver -- Viren R. Shah | "Practice safe government [EMAIL PROTECTED] | -- use kingdoms." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PS/2 mouse (psm0) is not detected with recent -current
1: adding io range 0x778-0x77a, size=0x3, align=0x8 PNP0401: adding irq mask 0x80 PNP0401: adding dma mask 0x8 pnpbios: handle 16 device ID PNP0401 (0104d041) PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x1 PNP0700: adding io range 0x3f7-0x3f7, size=0x1, align=0x1 PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 pnpbios: handle 17 device ID PNP0700 (0007d041) PNP0f13: adding irq mask 0x1000 pnpbios: handle 18 device ID PNP0f13 (130fd041) pnpbios: handle 19 device ID PNP0a03 (030ad041) sc-: sc0 already exists, using sc1 instead vga-: vga0 already exists, using vga1 instead isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: at iomem 0xc-0xc,0xd-0xd07ff on isa0 ata2 failed to probe at port 0x1f0 irq 14 on isa0 ata3 failed to probe at port 0x170 irq 15 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d atkbd1: unable to allocate IRQ psm0: current command byte:0065 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0-50, 3 buttons psm0: config:, flags:, packet size:3 psm0: syncmask:08, syncbits:08 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pcic0 failed to probe on isa0 ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: ECP SPP ECP+EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: irq maps: 0x1 0x1 0x1 0x1 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa 0x2 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc1: no video adapter found. sc1: failed to probe on isa0 vga1: failed to probe on isa0 isa_probe_children: probing PnP devices unknown: can't assign resources unknown: at port 0x60 on isa0 unknown: failed to probe at port 0x61 on isa0 unknown: failed to probe at iomem 0xffb0-0xffbf on isa0 unknown: can't assign resources unknown: at port 0x3f8-0x3ff on isa0 unknown: can't assign resources unknown: at port 0x378-0x37f on isa0 unknown: can't assign resources unknown: at port 0x3f0-0x3f5 on isa0 unknown: can't assign resources unknown: at irq 12 on isa0 BIOS Geometries: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: faith0 attached bpf: lo0 attached ad0: success setting UDMA4 on Intel chip Creating DISK ad0 ad0: ATA-5 disk at ata0-master ad0: 28629MB (58633344 sectors), 58168 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA66 ad0: piomode=4 dmamode=2 udmamode=4 cblid=1 ata1-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 ata1-master: success setting PIO4 on generic chip acd0: CDROM drive at ata1 as master acd0: read 8250KB/s (32KB/s), 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Writes: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked, lock protected acd0: Medium: no/blank disc Mounting root from ufs:/dev/ad0s1a ad0s1: type 0xa5, start 63, end = 58621184, size 58621122 : OK start_init: trying /sbin/init splash: image decoder found: logo_saver Kazu> Thank you, Kazu> Kazu Thanks. Viren -- Viren R. Shah| "I said it was an upgrade. Research Associate | I didn't say it was better." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PS/2 mouse (psm0) is not detected with recent -current
>>>>> "DC" == David W Chapman, writes: DC> Basically delete your /boot/kernel/acpi.ko until this has been DC> fixed. That's what I am having to do. Yeah, I've done that as a temporary measure. However, I'd like to help people figure out what's wrong. DC> David W. Chapman Jr. Viren -- Viren R. Shah| "I said it was an upgrade. Research Associate | I didn't say it was better." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NFS problems with movemail
[-current from 04/21 ] After I upgraded from a current dated approx 04/15 to current from 04/21, my movemail stopped working on NFS mounted partitions (i use XEmacs and VM for mail). I tested it out and it works fine on local partitions. My normal NFS server is a FreeBSD 3.4-stable box. I also tried using a NFS server that was a solaris 2.7 box. Same results. Movemail works fine when the client is a 4.3 RC2 box talking to the 3.4-stable NFS server. [I even compiled movemail from ports in order to check whether this would solve the problem, but no dice] Any ideas? Thanks Viren -- Viren R. Shah Man's Greatest Asset is... ...an unsettled mind To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problem with loader?
I just cvsupped (01/26 2pm EST) and made world. After building a new kernel, and installing new bootblocks, upon boot I get the following error: FreeBSD/i386 bootstrap loader Revision 0.2 ficlExecFD: Error at line 1 int=000e err=0004 efl=00010246 eip=fda0 [at which point my patience ran out, and I didn't jot down the rest] I booted with a loader from Jan 19, and it works. Did I goof up somewhere? or is this a loader bug? If needed I can boot from the recent loader again, and get the rest of the register dump. Viren -- Viren R. Shah | Everyone was born right-handed. vi...@rstcorp.com | Only the greatest overcome it. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
SVR4 module doesn't load
Is anyone having problems loading the SVR4 module? I have it loading up thru loader.rc, and I get: Preloaded elf kernel "kernel" at 0xf02a3000. Preloaded splash_image_data "/boot/splash.bmp" at 0xf02a309c. Preloaded elf module "splash_bmp.ko" at 0xf02a30ec. Preloaded elf module "cd9660.ko" at 0xf02a3190. Preloaded elf module "vesa.ko" at 0xf02a3230. Preloaded elf module "linux.ko" at 0xf02a32cc. Preloaded elf module "svr4.ko" at 0xf02a336c. link_elf: symbol msginfo undefined ^^^ When I try to load it using kldload, I get: [vs...@jabberwock] /sys/i386/conf# kldload /modules/svr4.ko kldload: can't load /modules/svr4.ko: Exec format error This is on a -current world as of 11:30am EST 02/09/99. [vs...@jabberwock] /sys/i386/conf# ls -la /modules/svr4.ko -r-xr-xr-x 1 root wheel 75194 Feb 9 13:40 /modules/svr4.ko [vs...@jabberwock] /sys/i386/conf# file /modules/svr4.ko /modules/svr4.ko: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), not stripped I do have "pseudo-device streams" in my kernel config. Is there anything else that I require? Thanks Viren -- Viren R. Shah "You are about as sharp as a sack of wet mice" -- Foghorn Leghorn To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: USB keyboard attach function?
>>>>> "Kazu" == Kazutaka YOKOTA writes: Kazu> You need to be running usbd. Kazu> In any case, we need some more work in the usb and ukbd driver code to Kazu> be able to "detach" the ukbd driver while the system is running. Amancio and Nick helped me get my system with only a USB keyboard and USB mouse up and running. Right now I'm pretty happy with the way it is now. My only concern is that the FreeBSD bootloader does not appear to see keystrokes from the USB keyboard (which kinda makes it difficult to switch OSes on an USB only system). Kazu> Kazu [Amancio: I'm currently building world in preparation for compiling a kernel without atkbdc and atkbd, as you suggested] Viren -- Viren R. Shah "You are about as sharp as a sack of wet mice" -- Foghorn Leghorn To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: USB keyboard attach function?
>>>>> "Amancio" == Amancio Hasty writes: Amancio> Hi, >> is now. My only concern is that the FreeBSD bootloader does not appear Amancio> If you are running -current as of at least last nite you Amancio> will not have any problems with the bootloader and your USB Amancio> keyboard in fact I just rebooted my test system and was able Amancio> to select the kernel to boot; previously, you are right the Amancio> bootloader didn't work with a USB keyboard only system. You are right! I just rebooted after a make world and a new kernel, and it worked!!! Cool. Viren -- Viren R. Shah "You are about as sharp as a sack of wet mice" -- Foghorn Leghorn To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: USB keyboard attach function?
> "Daniel" == Daniel O'Connor writes: Daniel> On 22-Apr-99 Amancio Hasty wrote: >> The problem was not really a bios problem not sure what the guys >> did to fix the boot loader probably switch to using a dos int function >> to access the keyboard from the boot loader. Daniel> Hmm.. what does it do now? Just talk to the keyboard Daniel> controller directly? The BIOS I have here have an option Daniel> 'Port 60/64 emulation' in the USB related section...
