Linux ls fails on DEVFS /dev
Hi, linux ls fails on DEVFS /dev because linux_getdents fails because linux_getdents uses VOP_READDIR( ..., ncookies, cookies ) instead of VOP_READDIR( ..., NULL, NULL ) because it seems to need the offsets for linux_dirent and sizeof(dirent) != sizeof(linux_dirent)... If I eliminate the usage of cookies, then a ls on at least a cd9660 mounted dir fails with not finding all direntries. So the question is if all filesystems are expected to implement the cookies != NULL case? BTW: Wy doesn't a call to fstat on a directory set a st_blksize != 0? Do directories have no preferred blocksize? I ask because getdents(2) explicitly states one should use stat(2) to get the minimum buffersize... Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Linux ls fails on DEVFS /dev
In message 20010805104350.A1188-10@nihil, Michael Reifenberger writes: Hi, linux ls fails on DEVFS /dev because linux_getdents fails because linux_getdents uses VOP_READDIR( ..., ncookies, cookies ) instead of VOP_READDIR( ..., NULL, NULL ) because it seems to need the offsets for linux_dirent and sizeof(dirent) != sizeof(linux_dirent)... Open a PR so I don't forget and please include how I can reproduce it while I test. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ntpd 4.1
On Sat, 04 Aug 2001 17:20:05 -0400, Mixtim wrote: Ha, you think that's bad. Mills doesn't want to be bothered to change his ways to use any sort of revision control. That's how set in his ways he is. Almost as bad as Linus. :pserver:[EMAIL PROTECTED]:/cvs/ntp You can checkout modules 'ntp' or 'ntpfaq'. Been there for a rather long time. That's totally irrelevant. David Mills doesn't make use of CVS. Someone else checks his changes in. Particularly in the documentation, these checkins consist of megacommits that mix sweeping content changes with massive tidy(1) style changes. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ntpd 4.1
According to Mark Murray: Can you make it so that if NO_OPENSSL is not defined, then openssl is used? I could of course but I don't think that having PUBKEYS by defaults (X.509 based, not the PGP ones) is probably not very useful yet as it is a fairly recent option. AUTOKEY should be enough. Any objection? No objection from me :-) M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
No Subject
auth 7f5c1c66 unsubscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
VERMOEGENSBERATUNG
! Wichtige Mitteilung an die Geschäftsleitung ! Betr.: VERMOEGENSBERATUNG Bitte umgehend an die Hauptverwaltung weiterleiten. -- Sehr geehrte Damen, sehr geehrter Herren, die Domain Vermoegensberatung.com wird zum Kauf angeboten. Falls Sie an dieser, vielleicht für Ihr Unternehmen kuenftig sehr wertvollen Domain Interesse haben, koennen Sie sich auf der Site www.vermoegensberatung.com informieren. Die Verwendung einer solchen beschreibenden Domain ist seit der Entscheidung des Bundesgerichtshofs in letzter Instanz vom 18.05.2001 (Az. I ZR 216/99) nicht mehr wettbewerbswidrig. Ich wünsche Ihnen einen schoenen Tag. Mit freundlichen Gruessen Gerhard Vehns Fax 0721 9473048 [EMAIL PROTECTED] IFAG - Sesam Software Elsa Brandstroemstr.15 76228 Karlsruhe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Linksys WDT11/WPC11 Combo
Sorry if this is a duplicate Hello, Does anyone have any patches for preliminary support of the Linksys WDT11/WPC11 wireless ethernet combo? The WDT card uses the PLX PCI9052 chipset and shows up under -STABLE's dmesg as: pci0: unknown card (vendor=0x16ab, dev=0x1102) at 19.0 irq 12 With what I have been reading so far on the PLX thread, I appear to have a different dev number. Most people have talked about dev=1101, but I have dev=1102. Is this a new rev of the board? How can I get this working? Patches for -CURRENT or -STABLE would be appreciated. -STEVEl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Base de Datos - 1.000 Empresas
Title: EMPRESAS - Base de datos de las 500Empresas más grandes, (por ventas), del país con los siguientes campos: razón social, sigla EMPRESAS - Base de datos con las 1.000 Empresas más grandes de Colombia (ventas superiores a $20.000 millones anuales), con los siguientes campos: razón social, sigla, Nit, dirección, teléfono, fax, actividad empresarial (código CIIU Rev. 3.0), número de empleados, ciudad y departamento, cifras de Activos, Patrimonio, Ventas y Utilidad para los últimos cinco años (Incluye cifras del año 2.000). Adicional a esta base se encuentra la base de datos de directivos y ejecutivos de estas empresas (más de 9.500), con los siguientes campos: nombre, cargo, área por cargos, dirección, teléfono y fax. Estas bases de datos se encuentran relacionadas, la APLICACION que las maneja permite hacer búsquedas simples o complejas por todos los campos, agrupa diferentes tipos de búsquedas, prepara e imprime reportes, rótulos y cartas, hace llamadas telefónicas y envía emails. La aplicación es totalmente autónoma, es decir no necesita ningún software adicional para su total desempeño en Windows 95 o superior. COMO VALOR AGREGADO le damos acceso a toda la información sobre COMERCIO EXTERIOR (27.000 importadores y 4.000 exportadores), a través de enlaces Vía Internet a MINCOMEX, PROEXPORT Y LA COMUNIDAD ANDINA. También le facilitamos la conexión a sus propios enlaces. PRESENTACION Las bases de datos y la aplicación se entregan en un CD, que permite la auto-instalación. VALOR DEL CD - Col$100.000, los cuales se deben depositar en COLMENA en la cuenta de ahorros No. 0114500194215 a nombre de Directorio Nacional de Fax, copia de la consignación con las instrucciones de entrega enviarlas al Fax 6178102/6179073 Bogotá y el CD y la factura serán enviados al día siguiente vía Servientrega. Si ya adquirió la versión 500 Empresas deposite únicamente Col$50.000 Empresas - Tr. 51A No 123-01 Int. 10 Tel. 6135184 Fax 6178102/6179073 [EMAIL PROTECTED] - Bogotá Colombia Si desea ser removido de esta base de datos, responda a este mensaje indicando remover en el subject
Re: HEADS UP: ACPI changes
On Fri, Aug 03, 2001 at 03:07:26AM -0700, Mike Smith wrote: - Changed the way ACPI timers are treated to be more pessimistic. It looks like we can't assume that the average ACPI timer is properly implemented. This is a pain; a good timer takes about 350 cycles to read on my PIII/500 laptop, wheras the safe read takes about 1050 To test your ACPI timer, first check to see which one you have. Look at the output of 'pciconf -lv'. If you have an Intel chipset, chances Hi Mike, First let me thank all the ACPI developers for their excellent work, ACPI is working just fine Thermal/CPU and battery wise in my Asus M8300 notebook. Reviewing your last commit on the timer problem, I was a bit suprised to see so little chipsets defined as good (just PCI ID 0x71138086, rev 0x03) and I wondered if the Intel 440MX chipset (82443MX Power Management Controller) in my notebook wasn't also good. I tried the timer_test at boot for about 15mins both with and without AC power, no warnings. Then I changed the cipset probe code to detect my device and it's been working without problems. I've attached my pciconf -lv output, there's also my verbose boot dmesg at http://devils.maquina.com/~gabriel/dmesg.acpi Another thing I've been wondering is why can't I suspend my machine to disk with ACPI or how do I do it. Usually with APM enabled I just press The Fn+F1 key combination to initiate suspend to disk, but this same key sequence doesn't do a thing when under ACPI. Is this supposed to work yet? I've also put my DSDT and ASL files at http://devils.maquina.com/~gabriel/m8300.dsdt and http://devils.maquina.com/~gabriel/m8300.asl Thanks again, Gabriel hostb0@pci0:0:0:class=0x06 card=0x chip=0x71948086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82443MX I/O Controller?' class= bridge subclass = HOST-PCI pcm0@pci0:0:1: class=0x040100 card=0x10631043 chip=0x71958086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82443MX? AC97 Audio Controller' class= multimedia subclass = audio none0@pci0:0:2: class=0x00 card=0x chip=0x rev=0x00 hdr=0x00 class= old subclass = non-VGA display device none1@pci0:2:0: class=0x03 card=0x13321043 chip=0x0720126f rev=0xb1 hdr=0x00 vendor = 'Silicon Motion' device = 'SM720 Lynx3DM' class= display subclass = VGA isab0@pci0:7:0: class=0x060100 card=0x chip=0x71988086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82443MX PCI to ISA Bridge' class= bridge subclass = PCI-ISA atapci0@pci0:7:1: class=0x010180 card=0x chip=0x71998086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82443MX EIDE Controller' class= mass storage subclass = ATA uhci0@pci0:7:2: class=0x0c0300 card=0x chip=0x719a8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82443MX USB Universal Host Controller' class= serial bus subclass = USB none2@pci0:7:3: class=0x068000 card=0x chip=0x719b8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82443MX Power Management Controller' class= bridge subclass = PCI-unknown pcib1@pci0:9:0: class=0x060400 card=0x0080 chip=0x01001668 rev=0x11 hdr=0x01 vendor = 'Action Tec Electronics Inc' class= bridge subclass = PCI-PCI pcic0@pci0:10:0:class=0x060700 card=0x chip=0x04751180 rev=0x80 hdr=0x02 vendor = 'Ricoh Co Ltd' device = 'RL5C475 CardBus controller' class= bridge subclass = PCI-CardBus fxp0@pci1:4:0: class=0x02 card=0x10001668 chip=0x12298086 rev=0x08 hdr=0x00 vendor = 'Intel Corporation' device = '82557/8/9 Fast Ethernet LAN Controller' class= network subclass = ethernet none3@pci1:8:0: class=0x078000 card=0x24001668 chip=0x044811c1 rev=0x01 hdr=0x00 vendor = 'ATT Microelectronics' device = 'LT Winmodem 56k' class= simple comms
Re: HEADS UP: ACPI changes
To test your ACPI timer, first check to see which one you have. Look at the output of 'pciconf -lv'. If you have an Intel chipset, chances Reviewing your last commit on the timer problem, I was a bit suprised to see so little chipsets defined as good (just PCI ID 0x71138086, rev 0x03) and I wondered if the Intel 440MX chipset (82443MX Power Management Controller) in my notebook wasn't also good. I haven't had any to test with; I'd assume that the 440MX is using the PIIX4M core. I tried the timer_test at boot for about 15mins both with and without AC power, no warnings. Then I changed the cipset probe code to detect my device and it's been working without problems. Thanks; I'll add your device ID - feedback like this is very useful. Another thing I've been wondering is why can't I suspend my machine to disk with ACPI or how do I do it. This isn't supported at the moment; there will probably be keymap entries to do this once the suspend kinks are worked out. Usually with APM enabled I just press The Fn+F1 key combination to initiate suspend to disk, but this same key sequence doesn't do a thing when under ACPI. Is this supposed to work yet? Under ACPI, the OS initiates sleep, not the BIOS, so the keyboard shortcuts aren't going to do anything. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ahc fails to attach in -current (was: snapshot installation woes)
+---[ Gordon Tetlow ]-- | On Sat, 4 Aug 2001, Gordon Tetlow wrote: | | Sure enough, that fixed the kernel panic, but here's the next odd piece, | my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940 | dmesg reports that ahc0 is there. The lines from the dmesg are (hand | typed): | | ahc0: Adaptec 2940 Ultra SCSI adapter port 0x5000-0x50ff mem 0x5000-0x5fff |irq 15 at device 15.0 on pci0 | aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs | | Since -stable and -current are using the exact same driver, there is | something more subtle (and sinister?) going on that I can't figure out. At | this point, I'm throwing my hands up in the air unless someone can give me | a better idea as to what the possible problem could be. I'd really like to | try -current on this box as it's a dual proc PPro 200. You'll probably need to use DEVFS to get booted. I can't boot -current from ahc using a standard /dev/ (or couldn't around the time DEVFS switched from being default disabled, to default enabled, so I've been running DEVFS ever since). This from either a 2940UW, or from dual onboard 7895's. So if you can get it installed, try building a new kernel with DEVFS enabled. I can't run SMP with ahc either, the machine locks up and I get messages about interrupts being off for too long (it was a while ago, but, I try an SMP build every month or so, and it still locks up (don't get to see the messages in X though)). Somtimes I do get more than 2-3 mins of uptime before it locks, and I can see that /dev/smb0 is no longer 'configured' (lmmon et. al. stop working). So if you do get it booted, be prepared for some torrid times d8) -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068|[EMAIL PROTECTED]| To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
rlogin terminal settings messed up
For quite a while now (?3-4 months?) one's terminal settings are messed up when rlogin'ing into a FreeBSD from a FreeBSD-current one. It used to be I could rlogin from an 80x24 Xterm, and the terminal settings on the remote box would also be 80x24. Now COLUMNS=80 and ROWS and TERMCAP isn't set, so a very large number is assumed. Does anyone know what changed? (someone has suggested the change came about when PAM's session model was changed) -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI: Clock problems in -current
Mike Smith schrieb: I forgot: Even if I define CLK_USE_*_CALIBRATION (and get no error messages after defining debug.acpi.timer_test), the Off/2 error still persist. Ok. I'm going to revert to the safe read code in a few minutes. Can you update and let me know if you're still wildly off? I'm having a hard time believing that your timer is really running at double pace, but I guess anything is possible. If it still does, I'll add some code to check it with the TSC. Hmm, just did the update unset debug.acpi.disable=timer but the error is still there. Maybe I'm just having a buggy ACPI implementation (remember, BIOS is from '99) -- Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ahc fails to attach in -current (was: snapshot installation woes)
Gordon Tetlow wrote: On Sat, 4 Aug 2001, Gordon Tetlow wrote: Sure enough, that fixed the kernel panic, but here's the next odd piece, my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940 dmesg reports that ahc0 is there. The lines from the dmesg are (hand typed): ahc0: Adaptec 2940 Ultra SCSI adapter port 0x5000-0x50ff mem 0x5000-0x5fff irq 15 at device 15.0 on pci0 device_probe_and_attach: ahc0 attach returned 12 errno.h says ENOMEM is 12, so it seems that something in the ahc driver is unable to allocate memory. Dunno where or why, but something is fouling it up. By contrast 4.3-RELEASE doesn't have any issues (I'll try a recent snapshot if that would help). Sorry I can't help out any more, but the debugging tools in the installation disks seem to lacking (understandably). Okay, I tried with a 4.4-PRERELEASE bootdisk that was available on current.jp.freebsd.org and dmesg came up with the following: ahc0: Adaptec 2940 Ultra SCSI adapter port 0x5000-0x50ff mem 0x5000-0x5fff irq 15 at device 15.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs Since -stable and -current are using the exact same driver, there is something more subtle (and sinister?) going on that I can't figure out. At this point, I'm throwing my hands up in the air unless someone can give me a better idea as to what the possible problem could be. I'd really like to try -current on this box as it's a dual proc PPro 200. I don't know if -current and -stable are using the same driver. Something *IS* different. Please see my post from about a month or so back in the aic7xxx group. Nobody responded to this. Where it would boot, with both controllers [3940UW on the MB] under -stable, it came up with the same message on ahc0 then after probing ahc1 and finding something there, reassigning ahc1 to ahc0. I ended up solving my own problem on this, although it did cause yet other problems. I had, because of IRQ issues, disabled the secondary IDE controller in the BIOS, to allow for both SCSI controller sides to have independant IRQs. This was causing the exact same message you note [see the dmesg output in the aic7xxx list]. Interesting to note that even with the secondary IDE controller disabled on the MB, -current failed to recognize this, and then in turn enabled it. Once I turned on the second IDE controller, this whole thing cleared up, albeit, with side-effects [now my Hauppauge WinTV/Theatre card is in conflict, and will cause a spontaneous reboot in both winblowz and fbsd when the TV is activated, although radio works fine]. Are you disabling motherboard IRQs in a similar fashion? Play with your IRQs, and have Plug and Play set in your BIOS. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ahc fails to attach in -current (was: snapshot installation woes)
Andrew Kenneth Milton wrote: +---[ Gordon Tetlow ]-- | On Sat, 4 Aug 2001, Gordon Tetlow wrote: | | Sure enough, that fixed the kernel panic, but here's the next odd piece, | my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940 | dmesg reports that ahc0 is there. The lines from the dmesg are (hand | typed): | | ahc0: Adaptec 2940 Ultra SCSI adapter port 0x5000-0x50ff mem 0x5000-0x5fff irq 15 at device 15.0 on pci0 | aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs | | Since -stable and -current are using the exact same driver, there is | something more subtle (and sinister?) going on that I can't figure out. At | this point, I'm throwing my hands up in the air unless someone can give me | a better idea as to what the possible problem could be. I'd really like to | try -current on this box as it's a dual proc PPro 200. You'll probably need to use DEVFS to get booted. I can't boot -current from ahc using a standard /dev/ (or couldn't around the time DEVFS switched from being default disabled, to default enabled, so I've been running DEVFS ever since). This from either a 2940UW, or from dual onboard 7895's. So if you can get it installed, try building a new kernel with DEVFS enabled. I can't run SMP with ahc either, the machine locks up and I get messages about interrupts being off for too long (it was a while ago, but, I try an SMP build every month or so, and it still locks up (don't get to see the messages in X though)). Somtimes I do get more than 2-3 mins of uptime before it locks, and I can see that /dev/smb0 is no longer 'configured' (lmmon et. al. stop working). So if you do get it booted, be prepared for some torrid times d8) As far as DEVFS goes, isn't that config option now depreciated, and everything is in devfs? By the way, I think I see his problem right now! Exactly as I said in my last message on this topic... What does his dmesg say for ata1? irq 15? Same shit I ran into... ata isn't reading if the controller is disabled in BIOS. Under -stable, this is being read, and no conflict exists. Could this actually be related to changes in ata? SMP and ahc0/1 work fine here... Tyan S1696-DLUA MoBo, 2 P2-333's, Linksys 10/100 on dc0, DEC DEFPA SAS UTP-PMD, SB Live!, and WinTV/Theatre. Copyright (c) 1992-2001 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 #12: Tue Jul 31 16:18:35 CDT 2001 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/WAHOO Timecounter i8254 frequency 1192995 Hz CPU: Pentium II/Pentium II Xeon/Celeron (333.00-MHz 686-class CPU) Origin = GenuineIntel Id = 0x650 Stepping = 0 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 536870912 (524288K bytes) avail memory = 516796416 (504684K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 IOAPIC #0 intpin 16 - irq 11 IOAPIC #0 intpin 17 - irq 9 IOAPIC #0 intpin 18 - irq 5 IOAPIC #0 intpin 19 - irq 10 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 [...] ahc0: Adaptec aic7895 Ultra SCSI adapter port 0xe000-0xe0ff mem 0xfebfd000-0xfebfdfff irq 10 at device 15.0 on pci0 ahc0: Using left over BIOS settings ahc1: Adaptec aic7895 Ultra SCSI adapter port 0xec00-0xecff mem 0xfebff000-0xfebf irq 11 at device 15.1 on pci0 ahc1: Using left over BIOS settings jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Linux ls fails on DEVFS /dev
I reported this problem on the linprocfs and procfs modules a while back while playing with a complete Linux environment under jail(). So clearly we have a general problem among our synthetic file systems with regards to the linux emulator (and possibly other emulators?) Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services On Sun, 5 Aug 2001, Michael Reifenberger wrote: Hi, linux ls fails on DEVFS /dev because linux_getdents fails because linux_getdents uses VOP_READDIR( ..., ncookies, cookies ) instead of VOP_READDIR( ..., NULL, NULL ) because it seems to need the offsets for linux_dirent and sizeof(dirent) != sizeof(linux_dirent)... If I eliminate the usage of cookies, then a ls on at least a cd9660 mounted dir fails with not finding all direntries. So the question is if all filesystems are expected to implement the cookies != NULL case? BTW: Wy doesn't a call to fstat on a directory set a st_blksize != 0? Do directories have no preferred blocksize? I ask because getdents(2) explicitly states one should use stat(2) to get the minimum buffersize... Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ahc fails to attach in -current (was: snapshot installation woes)
On Sat, 4 Aug 2001, Gordon Tetlow wrote: Sure enough, that fixed the kernel panic, but here's the next odd piece, my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940 dmesg reports that ahc0 is there. The lines from the dmesg are (hand typed): ahc0: Adaptec 2940 Ultra SCSI adapter port 0x5000-0x50ff mem 0x5000-0x5fff irq 15 at device 15.0 on pci0 device_probe_and_attach: ahc0 attach returned 12 errno.h says ENOMEM is 12, so it seems that something in the ahc driver is unable to allocate memory. Dunno where or why, but something is fouling it up. By contrast 4.3-RELEASE doesn't have any issues (I'll try a recent snapshot if that would help). Sorry I can't help out any more, but the debugging tools in the installation disks seem to lacking (understandably). Okay, I tried with a 4.4-PRERELEASE bootdisk that was available on current.jp.freebsd.org and dmesg came up with the following: ahc0: Adaptec 2940 Ultra SCSI adapter port 0x5000-0x50ff mem 0x5000-0x5fff irq 15 at device 15.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs Since -stable and -current are using the exact same driver, there is something more subtle (and sinister?) going on that I can't figure out. At this point, I'm throwing my hands up in the air unless someone can give me a better idea as to what the possible problem could be. I'd really like to try -current on this box as it's a dual proc PPro 200. Thanks, -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: snapshot installation woes
On Sat, 4 Aug 2001, John Baldwin wrote: On 04-Aug-01 Gordon Tetlow wrote: I decided I was going to brave 5.0-CURRENT and give the snapshots available on current.jp.freebsd.org a try. I found a couple issues with installation disks (FWIW, I tried it on the lastest snapshot avail on current.freebsd.org. I got the same results). Anyway, I go through the standard kern/mfsroot floppy deal and when it boots the kernel, everything seems to be going fine until I get the following kernel panic: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xffab That's a NULL pointer deref. fault code= supervisor write, page not present instruction pointer = 0x8:0xc0a75ac0 Hmmm... Can you look in the bin dist for the kernel.debug and do a 'gdb -k' on it to look up this address to see what line it is dying on? No idea on the ahc0 error. :( A little more information, if I disable the on-board audio (pnpscan shows it to be CSCe835 IBM Audio Feature) the kernel panic goes away. I'm still working on getting the line it's dying on. -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: no new snapshot on ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/
On 2001-08-03 10:27:26 +0900, Makoto MATSUSHITA wrote: wosch What happens? Is -current now so unstable that we cannot make a wosch snapshot anymore? current.jp.FreeBSD.org is for you until current.freebsd.org is back again; it's not a *mirror*, but has almost same features. Great! I will use this server for the automatically update of the -current manpages at http://www.FreeBSD.org/cgi/man.cgi?manpath=FreeBSD+5.0-current Thanks, Wolfram -- Wolfram Schneider [EMAIL PROTECTED] http://wolfram.schneider.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI: Clock problems in -current
Ok. I'm going to revert to the safe read code in a few minutes. Can you update and let me know if you're still wildly off? I'm having a hard time believing that your timer is really running at double pace, but I guess anything is possible. If it still does, I'll add some code to check it with the TSC. Hmm, just did the update unset debug.acpi.disable=timer but the error is still there. Meaning no offense, but I read a lot of mail. Can you please keep your problem reports specific? (ie. which bloody error?) Thanks. Maybe I'm just having a buggy ACPI implementation (remember, BIOS is from '99) Could be, though we're talking hardware here. It's possible that we'll just have to blacklist your timer. 8( Can you give me the ALi chip number(s) again, and I'll go look for datasheets... Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
