Re: maxphys = 0??
Poul-Henning Kamp wrote: Meanwhile the mystery has been solved. I was a miscommunication between sos and me. He only committed one half of the fix for this issue. He has now committed the rest along with the latest version of his ata drivers (he claims :-) Things are fine here now. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: maxphys = 0??
In message [EMAIL PROTECTED], "Bria n F. Feldman" writes: On Tue, 5 Oct 1999, Daniel C. Sobral wrote: Poul-Henning Kamp wrote: You need to move your sources further forward. Alas, it didn't help. What versions of what files I should have? The warnings are still appearing, at fsck time. The lastest. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: maxphys = 0??
Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], "Bria n F. Feldman" writes: On Tue, 5 Oct 1999, Daniel C. Sobral wrote: Poul-Henning Kamp wrote: You need to move your sources further forward. Alas, it didn't help. What versions of what files I should have? The warnings are still appearing, at fsck time. The lastest. Well, I tried with the latest after you said the above. I'll try with a later latest again. But, really... -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: maxphys = 0??
In message [EMAIL PROTECTED], "Daniel C. Sobral" writes: Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], "Bria n F. Feldman" writes: On Tue, 5 Oct 1999, Daniel C. Sobral wrote: Poul-Henning Kamp wrote: You need to move your sources further forward. Alas, it didn't help. What versions of what files I should have? The warnings are still appearing, at fsck time. The lastest. Well, I tried with the latest after you said the above. I'll try with a later latest again. But, really... Well, there are two options, either your sources are not up to date, or your config is very special in some way... -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: maxphys = 0??
On Sat, 9 Oct 1999, Poul-Henning Kamp wrote: Well, there are two options, either your sources are not up to date, or your config is very special in some way... I am absolutely certain that my sources are up-to-date. I'll attach my kernel config in case you can find something special there. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # 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 # URL: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.102 1998/01/11 02:16:38 jkh Exp $ machine i386 cpu I586_CPU ident GREEN maxusers64 makeoptions DEBUG="-g" #optionsMATH_EMULATE #Support for x87 emulation options INET#InterNETworking options IPX options NETATALK options FFS #Berkeley Fast Filesystem options FFS_ROOT options CD9660 #ISO 9660 Filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options NO_F00F_HACK options IPFIREWALL options IPFIREWALL_FORWARD #enable xparent proxy support options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=100 options IPDIVERT options IPSTEALTH #optionsIPFILTER options DUMMYNET options DDB options DDB_UNATTENDED options SOFTUPDATES options PQ_HUGECACHE # color for 1024k cache options ICMP_BANDLIM options MSGBUF_SIZE=16384 options INVARIANTS options INVARIANT_SUPPORT options CLK_USE_TSC_CALIBRATION #optionsICMP_BANDLIM_SILENT options CPU_WT_ALLOC options NO_MEMORY_HOLE options MAXFILES=65536 controller pci0at nexus? controller isa0at nexus? controller pnp0 # Luigi's snd code. # You may also wish to enable the pnp controller with this, for pnp # sound cards. # #device pcm0 at isa? port 0x220 irq 5 drq 1 #flags 0x16 controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 6 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 device joy0at isa? port IO_GAME #controller fdc0at isa? port IO_FD1 irq 6 drq 2 #disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 # for a PCI only system (most modern machines) controller ata0 device atadisk0# ATA disks device atapicd0# ATAPI CDROM's device atapist0# ATAPI tapes device atapifd0 controller ncr0 controller scbus0 #base SCSI code device ch0 #SCSI media changers device da0 #SCSI direct access devices (aka disks) device sa0 #SCSI tapes device cd0 #SCSI CD-ROMs device pass0 #CAM passthrough driver device pt0 at scbus?# SCSI processor type options SCSI_DELAY=5000 # Be pessimistic about Joe SCSI device # The keyboard controller; it controlls the keyboard and the PS/2 mouse. controller atkbdc0 at isa? port IO_KBD # The AT keyboard device atkbd0 at atkbdc? irq 1 # PS/2 mouse device psm0at atkbdc? irq 12 # The video card driver. device vga0at isa? port ? conflicts # The syscons console driver (sco color console compatible). device sc0 at isa? device npx0at nexus? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # #device apm0at nexus? conflicts # Advanced Power Management # System Management Bus! controller smbus0 controller alpm0 device smb0 at smbus? device sio0at isa? port IO_COM1 flags 0x10 irq 4 device sio1at isa? port IO_COM2 irq 3 device sio2at isa? disable port IO_COM3 irq 5 device sio3at isa? disable port IO_COM4 irq 3 controller ppbus0 device lpt0 at ppbus? device
Re: maxphys = 0??
In message [EMAIL PROTECTED], "Bria n F. Feldman" writes: On Sat, 9 Oct 1999, Poul-Henning Kamp wrote: Well, there are two options, either your sources are not up to date, or your config is very special in some way... I am absolutely certain that my sources are up-to-date. I'll attach my kernel config in case you can find something special there. What does your /etc/fstab look like ? I would also like to see a dmesg output. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: maxphys = 0??
Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], "Bria n F. Feldman" writes: On Sat, 9 Oct 1999, Poul-Henning Kamp wrote: Well, there are two options, either your sources are not up to date, or your config is very special in some way... I tried again. My sources are now dated from this morning's pnpparse.c breakage, so we can be sure of it's updatedness. What does your /etc/fstab look like ? I would also like to see a dmesg output. And here is fstab, dmesg and kernel configuration file. # DeviceMountpoint FStype Options DumpPass# /dev/ad0s2b noneswapsw 0 0 /dev/ad0s2a / ufs rw 1 1 /dev/ad0s2f /usrufs rw 1 3 /dev/ad0s2e /varufs rw 2 2 /dev/ad0s1 /dosmsdos rw 0 0 proc/proc procfs rw 0 0 kern/kern kernfs rw 0 0 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #4: Fri Oct 8 18:11:32 JST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/DCS Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6tm w/ multimedia extensions (233.86-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x570 Stepping = 0 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX AMD Features=0x400b10 real memory = 100663296 (98304K bytes) avail memory = 94580736 (92364K bytes) Preloaded elf kernel "kernel" at 0xc02b2000. Preloaded elf module "splash_bmp.ko" at 0xc02b209c. Preloaded elf module "vesa.ko" at 0xc02b2140. Preloaded splash_image_data "/boot/chuck_nebula.bmp" at 0xc02b21dc. VESA: v2.0, 1920k memory, flags:0x0, mode table:0xc02a0062 (122) VESA: MagicGraph 128XD 40K SVGA BIOS apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 isab0: PCI to ISA bridge (vendor=1045 device=c700) at device 1.0 on pci0 isa0: ISA bus on isab0 pcic0: TI PCI-1131 PCI-CardBus Bridge at device 10.0 on pci0 pcic1: TI PCI-1131 PCI-CardBus Bridge at device 10.1 on pci0 vga-pci0: NeoMagic NM2160 laptop SVGA controller irq 11 at device 18.0 on pci0 ata-pci0: Unknown PCI IDE controller (generic mode) at device 20.0 on pci0 ata-pci0: Busmastering DMA not enabled ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pccard0: PC Card bus -- KLUDGE version on motherboard 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 pcm0: ESS1868 rev 11 at irq 5 drq 1 flags 0x10 on isa0 pca0 at port 0x40 on isa0 pca0: PC speaker audio driver 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 pcic: pccard bridge VLSI 82C146 (5 mem 2 I/O windows) pcic: controller irq 3 pccard: initalizing drivers: ad0: FUJITSU MHA2021AT/8209 ATA-3 disk at ata0 as master ad0: 2067MB (4233600 sectors), 4200 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, PIO Creating DISK ad0 Creating DISK wd0 acd0: TOSHIBA CD-ROM XM-1602B/1132 CDROM drive at ata1 as master acd0: read 3445KB/s (3445KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked changing root device to wd0s2a WARNING: / was not properly dismounted pccard: card inserted, slot 1 WARNING: #ad/0x30005 maxphys = 0 ??WARNING: #ad/0x30004 maxphys = 0 ?? syncing disks... done Rebooting... Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Oct 10 06:20:59 JST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/DCS Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6tm w/ multimedia extensions (233.87-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x570 Stepping = 0 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX AMD Features=0x400b10 real memory = 100663296 (98304K bytes) avail memory = 94584832 (92368K bytes) Preloaded elf kernel "kernel" at 0xc02b2000. Preloaded elf module "splash_bmp.ko" at 0xc02b209c. Preloaded elf module
Re: maxphys = 0??
Meanwhile the mystery has been solved. I was a miscommunication between sos and me. He only committed one half of the fix for this issue. He has now committed the rest along with the latest version of his ata drivers (he claims :-) -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: maxphys = 0??
On Tue, 5 Oct 1999, Daniel C. Sobral wrote: Poul-Henning Kamp wrote: You need to move your sources further forward. Alas, it didn't help. What versions of what files I should have? The warnings are still appearing, at fsck time. Alas, similarly I get: changing root device to wd0s1a WARNING: #ad/0x20007 maxphys = 0 ??WARNING: #ad/0x20006 maxphys = 0 ??WARNING: #ad/0x20004 maxphys = 0 ??WARNING: #ad/0x20005 maxphys = 0 ??WARNING: #ad/2 maxphys = 0 ?? -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: maxphys = 0??
Poul-Henning Kamp wrote: You need to move your sources further forward. Alas, it didn't help. What versions of what files I should have? The warnings are still appearing, at fsck time. In message [EMAIL PROTECTED], "Daniel C. Sobral" writes: A kernel from this weekend's sources is showing this warning message at boot: WARNING: #ad/0x30005 maxphys = 0 ??WARNING: #ad/0x30004 maxphys = 0 ?? These are: brw-r- 1 root operator 30, 0x00030004 Apr 6 11:48 ad0s2e brw-r- 1 root operator 30, 0x00030005 Apr 6 11:48 ad0s2f -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
