RE: ATA - Trouble mounting secondary master
Hmm, My root device still lands up on "wd0" - even though my fstab has the root filesystem on ad0s1a. I haven't looked at getting it to use the ad dev entries for the root file system. (I'm assuming that is still WIP.) Geoff. -Original Message- From: Soren Schmidt [mailto:[EMAIL PROTECTED]] Sent: 11 August 1999 08:53 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: ATA - Trouble mounting secondary master It seems Geoff Rehmet wrote: Brian McGroarty writes : In using the ATA driver, I'm unable to automatically mount a partition on a master drive on the secondary controller. fsck complains that device rwd2s1e isn't configured and exists. Immediately mounting by hand works perfectly. Compiling the kernel with wd instead of ata eliminates the problem. Hmm, I had exactly the same problem, although it manifested itself with a secondary master or slave. It went away a few weeks ago, and I was never able to make any sensible progress in tracking the problem down. Hmm, damn, after the problem went away for Geoff I thought it to be solved since I've never heard of it anywhere else, and I cant reproduce it here no matter what I try. Does it help eany if you only has the root partition use the wd dev and have the rest use the prober ad dev entries ?? It could be some artifact from this... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA - Trouble mounting secondary master
It seems Geoff Rehmet wrote: Hmm, My root device still lands up on "wd0" - even though my fstab has the root filesystem on ad0s1a. I haven't looked at getting it to use the ad dev entries for the root file system. (I'm assuming that is still WIP.) Our boot blocks/loader dont have the needed computrons to use the "ad" device name. However I have some patches to boot2 that allows to boot off an ad root device, provided you dont use the loader, and put the rigth boot string in boot.config. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: installing hack(6) overwrites /var/games/hackdir/record file!
On Wed, Aug 11, 1999 at 04:24:55AM +1000, Andy Farkas wrote: Perhaps this should be a PR... Seeing as how we are recently being amused by fortune(6) quotes, I thought I'd mention an acronymn that hasn't been used recently: POLA Can anyone explain why every time I upgrade world, my hard earned 'record' file whilst playing hack(6) gets overwritten by /dev/null, and also all the user 'bones' and 'save' files rm'd? Blimey! I wondered where all my rogue(6) scores were going. This is an excellent idea. I'll submit a PR, with your diffs and some for rogue. -- Dom Mitchell -- Palmer Harvey McLane -- Unix Systems Administrator "Finally, when replying to messages only quote the parts of the message your will be discussing or that are relevant. Quoting whole messages and adding two lines at the top is not good etiquette." -- Elias Levy -- ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wd0: interrupt timeout (status 58rdy,seekdone,drq error 1no_dam)
That can't be true, at least not for the IBM DeskStars I own, I've NEVER EVER seen them do that, one proof should be: same here wdc0: unit 0 (wd0): IBM-DTTA-350840, DMA, 32-bit, multi-block-16 wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): IBM-DTTA-351010, DMA, 32-bit, multi-block-16 wd1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (wd2): IBM-DTTA-351010, DMA, 32-bit, multi-block-16 wd2: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S I ran into this exact problem on a small LAN server with a single deskstar drive. Usually I would just see the error in the logs once or twice a month without incident, but one time it took down the server hard enough to munge quite a few files. The drive is now in a dualboot win98/freebsd multimedia box and I haven't seen the error again (the box isn't up for a week at a time). - Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA - Trouble mounting secondary master
I've just tried and coming in via wd and ad produce the same problem. Note my previous comment - the access light is a steady on for this particular drive. It's left that way when devices are probed during startup. My configuration FWIW - (Note that the devclass_alloc_unit messages are new as of yesterday's cvsup and, presumably, unrelated.) 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 #7: Tue Aug 10 22:13:10 CDT 1999 Timecounter "i8254" frequency 1193182 Hz CPU: Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM OV,PAT,PSE36,MMX,FXSR real memory = 536870912 (524288K bytes) avail memory = 518422528 (506272K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard 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 Preloaded elf kernel "kernel" at 0xc028f000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc028f09c. Pentium Pro MTRR support enabled Probing for PnP devices: devclass_alloc_unit: pcib0 already exists, using next available unit number devclass_alloc_unit: pcib0 already exists, using next available unit number devclass_alloc_unit: pcib0 already exists, using next available unit number devclass_alloc_unit: pcib0 already exists, using next available unit number devclass_alloc_unit: pcib0 already exists, using next available unit number npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 WARNING: "bktr" is usurping "bktr"'s cdevsw[] pcib6: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib6 vga-pci0: NVidia Riva TNT graphics accelerator irq 16 at device 0.0 on pci1 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 ata-pci0: Intel PIIX4 IDE controller at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip1: UHCI USB controller at device 7.2 on pci0 chip2: Intel 82371AB Power management controller at device 7.3 on pci0 bktr0: BrookTree 878 irq 16 at device 16.0 on pci0 iicbb0: I2C generic bit-banging driver on bti2c0 iicbus0: Philips I2C bus on iicbb0 master-only smbus0: System Management Bus on bti2c0 Hauppauge Model 62471 A Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, dbx stereo. pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 16.1 irq 16 pcm0: AudioPCI ES1370 irq 18 at device 18.0 on pci0 pcm0: using I/O space register mapping at 0xef00 fxp0: Intel EtherExpress Pro 10/100B Ethernet irq 19 at device 19.0 on pci0fxp0: Ethernet address 00:90:27:18:a6:fa xl0: 3Com 3c905B-TX Fast Etherlink XL irq 16 at device 20.0 on pci0 xl0: Ethernet address: 00:50:04:01:77:7b xl0: autoneg complete, link status good (half-duplex, 100Mbps) devclass_alloc_unit: pci1 already exists, using next available unit number pcib1: Host to PCI bridge on motherboard pci2: PCI bus on pcib1 devclass_alloc_unit: pci2 already exists, using next available unit number pcib2: Host to PCI bridge on motherboard pci3: PCI bus on pcib2 devclass_alloc_unit: pci3 already exists, using next available unit number pcib3: Host to PCI bridge on motherboard pci4: PCI bus on pcib3 devclass_alloc_unit: pci4 already exists, using next available unit number pcib4: Host to PCI bridge on motherboard pci5: PCI bus on pcib4 devclass_alloc_unit: pci5 already exists, using next available unit number pcib5: Host to PCI bridge on motherboard pci6: PCI bus on pcib5 isa0: ISA bus 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 IntelliMouse, device ID 3 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 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled SMP: AP CPU #1 Launched! ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: IBM-DTTA-371440/T71OA73A ATA-4 disk at ata0 as master ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 31 depth queue, DMA mode ata0: slave: setting up UDMA2 mode on PIIX4 chip OK ad1: IBM-DJNA-372200/J71OA30K ATA-4 disk at ata0 as slave ad1: 21557MB (44150400 sectors), 43800 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int,
Re: it's time...
: Correct, but the nature of the kernel probe/attach messages is to convey : information in a readable, consistent, useful manner. Agreed. However, what's magical about 80 columns? What's magical is that almost every text console is limited to 80 columns (think serial console), as well as the standard default size for terminal emulators is 80 columns. My editors go out to 180 sometimes. The console can easily be placed into a mode where it is 80. This is especially true for the serial console where it might be connected to a 132 column printer. Just because it *can* be connected to a 132 column printer doesn't mean it *will* be connected. Most printers that I use are 80 columns wide. Heck, almost *every* printer I use is that wide, hence the whole 80 column thing. The most common case for a console is an 80 column wide console (this is the default for the virtual terminals, most printers, most text terminals, etc..) Changing it is silly, and non-standard. No! At some point they should use a facility similar to solaris/sysv where they don't display, but do make it into the dmesg buffer... On my Solaris box, they are displayed at boot time. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
On Wed, 11 Aug 1999, Warner Losh wrote: Then we disagree. There are several scripts floating around that use them for purposes where there isn't a kernel interface... It would be ideal if there were interfaces for all this info, but there isn't always. Fine. Due to flux in the bus-system between versions, probe/attach information is essentially a non supported interface for gathering this data. If you do wish to gather it from this source its up to you to DTRT. If you dislike this then your input on a standard interface to this information would likely be of use. : An interface to query the resource manager directly is likely to be a : better solution to your problem. Well, only kinda. That was one example. The other example is finding out what the ide driver thought the disk geometry of a disk was... If that information needs to be presented I see no reason why drivers can't do some magic and make /kern/foo/wd0/geometry spit out the right thing. Granted, this is more complex, but depending on boot messages for this information is setting yourself up for problems. : Besides, if your perl skills aren't able to cope with getting all 'fooX:' : lines, and stripping out the 'fooX:' bits before parsing then you have : other problems. Hah! You presume too much. None of these scripts are written in perl, so the size of my perl schl*** isn't at issue here :-) You also assume that the wrapping would be of the form fooX:. FreeBSD's boot messages aren't consistant about this right now, witness the difference between isa and pci devices: sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vs ahc0: Adaptec 2940 Ultra SCSI adapter irq 10 at device 16.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs The "proper" way to do this would be sio1 at isa0 port 0x2f8-0x2ff irq 3: type 16550A ahc0 at pci0 irq 10 device 16.0: Adaptec 2940 Ultra SCSI adapter ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Incorrect. The device name should be separated from the rest of the line by a ':'. if you must introduce wrapping. Each phrase should either fit on the current line or be bumped to the next line. However, what is a line? Also, I use "proper" in quotes because others will reasonably differ with the exact details... Indeed. But you've still prooved my point that the probe/attach messages are an unsupported source for such information. : Correct, but the nature of the kernel probe/attach messages is to convey : information in a readable, consistent, useful manner. Agreed. However, what's magical about 80 columns? My editors go out to 180 sometimes. The console can easily be placed into a mode where it is 80. This is especially true for the serial console where it might be connected to a 132 column printer. In the beginning was the punch card... : If we didn't want pretty line wrapping we'd all be using linux and have : stupid stuff like copyright messages as well. :) Don't even get me started on linux' boot messages. :-) I happen to like the stark elegance of the OpenBSD/NetBSD boot messages. Here's the entire dmesg from the boot of my rPC44 MIPS machine when booted under OpenBSD. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-1999 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 2.4-current (IMP-PCCARD) #37: Mon Feb 1 13:28:06 MST 1999 [EMAIL PROTECTED]:/home/imp/src/sys/arch/arc/compile/IMP-PCCARD real mem = 32235520 avail mem = 27754496 using 419 buffers containing 1716224 bytes of memory mainbus0 (root) cpu0 at mainbus0: MIPS R4400 CPU Rev. 4.0 with MIPS R4010 FPC Rev. 0.0 L1 Cache I size 16kb(16 line), D size 16kb(16 line), direct mapped. L2 cache doesn't snoop uncached cpu accesses. isabr0 at mainbus0 isa0 at isabr0 isa_io_base 0xb000 isa_mem_base 0xa000 com0 at isa0 port 0x3f8-0x3ff irq 4: ns16450, no fifo com1 at isa0 port 0x2f8-0x2ff irq 3: ns16450, no fifo wdc0 at isa0 port 0x1f0-0x1f7 irq 14 wd0 at wdc0 drive 0: SAMSUNG WN321620A (2.16 GB) wd0: 2060MB, 4186 cyl, 16 head, 63 sec, 512 bytes/sec, 4219488 sec total wd0: using 16-sector 16-bit pio transfers, lba addressing (109KB cache) clock0 at isa0 port 0x70-0x6d5 irq 0: mc146818 or compatible pcprobe: reset error 1 pc0 at isa0 port 0x60-0x6c5 irq 1: color joy0 at isa0 port 0x201: joystick not connected ed0 at isa0 port 0x300-0x31f irq 5: address 00:00:1b:1e:52:a7, type NE2000 (16-bit) boot device: wd0. root on wd0a rootdev=0x400 rrootdev=0x1200 rawdev=0x1202 Where OpenBSD has com0 at isa0 port 0x3f8-0x3ff irq 4: ns16450, no fifo com1 at isa0 port 0x2f8-0x2ff irq 3: ns16450, no fifo FreeBSD we has sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: configured irq 5 not in bitmap of probed irqs 0 sio3: configured
Re: it's time...
On Wed, 11 Aug 1999, Nate Williams wrote: The most common case for a console is an 80 column wide console (this is the default for the virtual terminals, most printers, most text terminals, etc..) Changing it is silly, and non-standard. The line wrapping stuff I brought back for the EISA bus stuff in -current makes it easy to define the wrap point. If some small number of people want the ability to wrap at 132 or 40 or whatever, I don't think its unreasonable to provide them the knob to tweak in the boot loader. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wd0: interrupt timeout (status 58rdy,seekdone,drq error 1no_dam)
Soren Schmidt wrote: [SNIP] Have you tried putting disks on the UDMA66 channel ?? I think it should work in upto WDMA mode now with the ata driver... I have first to install 4.0 and from my wd2 (I've got a little help from RNordier, I should make do) Then, I'll get a UDMA-66 drive (any recommendation ?) TfH -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wd0: interrupt timeout (status 58rdy,seekdone,drq error 1no_dam)
It seems Thierry Herbelot wrote: Soren Schmidt wrote: [SNIP] Have you tried putting disks on the UDMA66 channel ?? I think it should work in upto WDMA mode now with the ata driver... I have first to install 4.0 and from my wd2 (I've got a little help from RNordier, I should make do) Then, I'll get a UDMA-66 drive (any recommendation ?) You can put any IDE drive on those channels, but of cause you can only use UDMA66 on capable drives. I'd just be interested in if the newest ata driver finds the controller, UDMA66 is not supported yet anyways only std WDMA... And me, I'm a sucker for IBM or Maxtor drives in that order... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
In message [EMAIL PROTECTED] Nate Williams writes: : And you plan on booting FreeBSD on your PDA? Yes. I'm already booting NetBSD/hpcmips on it But that's another thread all by itself... : stty columns is only effective *AFTER* you have a shell and the box has : booted. Yes I know that, but you seem to be arguing that all terminals have 80 columns... This is not the case, although many of them do. I was following your line of reasoning to its logical conclusion (since all terminals have 80 columns, why do we need to tell the kernel how big our terminals are). I agree 100% that 80 shall be the default, since that's how wide these things usually have been since 1890 and this man named Hollereth(sp?)... I just want to make sure that I can change that default. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: recent apm changes
Hi, Oh, do you have suspend button on your box? Cool. On my poor experience, suspeding by hot-keys easier to success than by zzz(8). On this point I can report the oppposite experience, on my machine (a no name special) the trackpad tends to lock up if touched between power on and resume finishing. The best indicator of safety is apm -z returning, if I use the button I have to guess. Ahh, I've seen this kind of behavior on some laptops. I guess this is related with some sort of time limits on communication with APM BIOS. APM Spec. v1.2 Appendix D - APM Driver Considerations - When an APM connection exists, the APM BIOS transitions into System Standby and System Suspend states only when directed to do so by a call from the APM Driver. The calls to change system states are invoked by the APM Driver only after the APM BIOS indicates that the state transition should be made, and the APM Driver has checked with all APM-aware applications to make sure that it is an appropriate time to change system states. However, there are three cases where the APM BIOS may make the system state transition itself. The first case is if the APM Driver does not pick up a posted Standby Request, Suspend Request or Critical Suspend Notification event within the 2 second ~~~ (one second plus one second grace period) time limit. The second is when the APM Driver, after picking up the event, does not respond to a Standby Request, Suspend Request or Critical Suspend Notification event with an appropriate Set Power State call within 5 seconds of receiving the event. The last situation is when the APM Driver has responded to an event with a Request Processing Set Power call and does not reply again within another 5 seconds.The CPU is power managed according to CPU Idle and CPU Busy calls made by the APM Driver to the APM BIOS. Last time, we didn't have `Last Request Processing Notification' to APM BIOS at all for the second case. After adding this hack in PAO, we saw greate improvements about system suspending transition (standby also) on a lot of laptops :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
: stty columns is only effective *AFTER* you have a shell and the box has : booted. Yes I know that, but you seem to be arguing that all terminals have 80 columns... This is not the case, although many of them do. Most of them do. It is the 'least common denominator' that FreeBSD runs into. More than 132 columns is an exception, as well as less than 80 columns. My point was not changing the boot message to more than 80 columns, like you suggested. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
Nate Williams scribbled this message on Aug 11: : The line wrapping stuff I brought back for the EISA bus stuff in -current : makes it easy to define the wrap point. If some small number of people : want the ability to wrap at 132 or 40 or whatever, I don't think its : unreasonable to provide them the knob to tweak in the boot loader. Despite what nate think about 80 columns, my PDA cannot display more than between 30-45 characters, depending on the font, so having a knob for that would be useful in the long term. And you plan on booting FreeBSD on your PDA? I've booted my FreeBSD box w/ my hp48... and that can't do more than about 34 columns in a sucky 3x5 or 4x5 font... and it works great... :) right now my hp48 is the only serial device that I can get close enough to my server, and I don't have any free slots for a mono or vga card.. -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Crash with NFS V2
Hi, I have a program which does something like userland-nfs (nfs v2 client). It is able to crash the machine. After compiling a debug kernel the only output I get after the crashdump is: ---snip--- (100) root@ttyp3 # gdb -kernel -se /sys/compile/WORK/kernel.debug -c /var/crash/vmcore.1 IdlePTD 3743744 initial pcb at 2cb960 panic messages: --- dmesg: kvm_read: invalid address (c02bcb50) --- #0 boot (howto=Cannot access memory at address 0xc62e6b54. ) at ../../kern/kern_shutdown.c:291 291 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=Cannot access memory at address 0xc62e6b54. ) at ../../kern/kern_shutdown.c:291 Cannot access memory at address 0xc62e6b4c. ---snip--- - System is -current from august 5th. - "mountd -2 -n" - "nfsd -u" My program does a nfs read call and wants a buffer (readres.readres_u.reply.data.data_val) of 32k to be filled. - crashed from userland (the program and the nfs server are running on the same machine) The core and the debug kernel are available, feel free to give me some advice how to get more information out of it. - There is also a strange behavior in nfs_readdir: I get a segfault with readdir (in libc, something xdr relatet if I remember correctly) if the buffer (readdirres.readdirres_u.reply.entries) is less than 8k+1 [NFS_MAXDATA+1] (on Solaris 2.4 this buffer has to be 257 [NFS_MAXNAMLEN+1] or greater). This one is testet with: - NFS-Server: FreeBSD 3.x, Userland-NFS-Client: Solaris 2.4 - NFS-Server + Userland-NFS-Client (on the same machine): FreeBSD 4-current (some months ago) Bye, Alexander. -- Can I trade this job for what's behind door #2? http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vty3 and 4.0 snap 080799
At 02:45 PM 08/11/1999 +0200, Dag-Erling Smorgrav wrote: "Michael A. Endsley" [EMAIL PROTECTED] writes: I just downloaded the latest snap (080799) and tried installing it. When getting to the media section and configuring ppp for a ftp install, I try going to vty3 (alt-f3). However, that vty is not available. I have tried this 3 times now. Is this broken? ttyv3 is on Alt-F4. I realized my typing mistake after sending this to the group, but hoped that the "alt-F3" would help. Lets just use alt-f3. To further explain (?): During a fresh install the system uses vty0. When the time comes to finally start downloading (using FTP), a screen is shown telling the person to go use the ALT-F3 keys (vty2) to use term. For me, that key combination is not "active". In fact, just vty1 is available (to view what FreeBSD is doing). I will just download the floppies from a later date (19990808-11). Thanks Mike ps- sorry for some of the generalities...I am just going by memory w/o being able to see the screens. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vty3 and 4.0 snap 080799
Use alt-F4 for the shell during install. vty0 - alt-F1 [Install] vty1 - alt-F2 [Debug] vty2 - alt-f3 [Inactive] vty3 - alt-F4 [Shell] PrtScr will cycle through all available vty's. HTH. HAND :) Larry Lile [EMAIL PROTECTED] On Wed, 11 Aug 1999 [EMAIL PROTECTED] wrote: At 02:45 PM 08/11/1999 +0200, Dag-Erling Smorgrav wrote: "Michael A. Endsley" [EMAIL PROTECTED] writes: I just downloaded the latest snap (080799) and tried installing it. When getting to the media section and configuring ppp for a ftp install, I try going to vty3 (alt-f3). However, that vty is not available. I have tried this 3 times now. Is this broken? ttyv3 is on Alt-F4. I realized my typing mistake after sending this to the group, but hoped that the "alt-F3" would help. Lets just use alt-f3. To further explain (?): During a fresh install the system uses vty0. When the time comes to finally start downloading (using FTP), a screen is shown telling the person to go use the ALT-F3 keys (vty2) to use term. For me, that key combination is not "active". In fact, just vty1 is available (to view what FreeBSD is doing). I will just download the floppies from a later date (19990808-11). Thanks Mike ps- sorry for some of the generalities...I am just going by memory w/o being able to see the screens. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] 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
Re: vty3 and 4.0 snap 080799
On Wed, 11 Aug 1999, Larry Lile wrote:
Use alt-F4 for the shell during install.
vty0 - alt-F1 [Install]
vty1 - alt-F2 [Debug]
vty2 - alt-f3 [Inactive]
How about we emit a message:
"This screen intentionally left blank." :)
vty3 - alt-F4 [Shell]
PrtScr will cycle through all available vty's.
HTH. HAND :)
Larry Lile
[EMAIL PROTECTED]
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
On Wed, 11 Aug 1999, Warner Losh wrote: It also would allow one to kick the VGA display into 132 columns in the boot loader and have more of a chance to get more of the boot process on the screen. syscons already supports parts of this... I was just reading through the thread again, and I was thinking about a Sun style boot where the screen is kicked into the VESA mode of your choice, we could have a FreeBSD daemon displaying in the upper left corner, etc. There is no reason to hard code 80 into the kernel. Otherwise one could argue why have stty columns at all :-). I have to agree with this, flexibility == AGoodThing(TM). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vty3 and 4.0 snap 080799
I should have also stated that I tried all the other "F" keys also. The only vty that is available/active is vty1 for debugging. Every other F-key gets the "beep". HTH in solving my problem fwiw dept.- I have been using FreeBSD since 2.21-R To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vty3 and 4.0 snap 080799
The shell is not started until after the install starts, ie when the ftp connects (the dists start getting untarred.) Larry Lile On Wed, 11 Aug 1999 [EMAIL PROTECTED] wrote: I should have also stated that I tried all the other "F" keys also. The only vty that is available/active is vty1 for debugging. Every other F-key gets the "beep". HTH in solving my problem fwiw dept.- I have been using FreeBSD since 2.21-R 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
Re: vty3 and 4.0 snap 080799
Well, something is wrong with what I am trying to say :) After entering the phone number to my ISP, the message screen pops up saying "...type ALT-F3..." to go to that vty. A person is supposed to go to that vty and then either type "dial" or "term". It is at this time that the vty (alt-f3) is not active/available! In other words, how do I type "dial" or "term" if I can't get to that vty? HTH, Mike At 07:32 PM 08/11/1999 -0400, Larry Lile wrote: The shell is not started until after the install starts, ie when the ftp connects (the dists start getting untarred.) Larry Lile On Wed, 11 Aug 1999 [EMAIL PROTECTED] wrote: I should have also stated that I tried all the other "F" keys also. The only vty that is available/active is vty1 for debugging. Every other F-key gets the "beep". HTH in solving my problem fwiw dept.- I have been using FreeBSD since 2.21-R 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
Re: ATA - Trouble mounting secondary master
Soren Schmidt [EMAIL PROTECTED] writes: It seems Geoff Rehmet wrote: Brian McGroarty writes : In using the ATA driver, I'm unable to automatically mount a partition on a master drive on the secondary controller. fsck complains that device rwd2s1e isn't configured and exists. Immediately mounting by hand works perfectly. I had exactly the same problem, although it manifested itself with a secondary master or slave. It went away a few weeks ago, and I was never able to make any sensible progress in tracking the problem down. Hmm, damn, after the problem went away for Geoff I thought it to be solved since I've never heard of it anywhere else, and I cant reproduce it here no matter what I try. Does it help eany if you only has the root partition use the wd dev and have the rest use the prober ad dev entries ?? It could be some artifact from this... I tried with the ad dev entries for my problem as well with no improvement. I've also tried using: dd if=/dev/ad0s6 of=/dev/null bs=512 count=1 as the first access to one of the failing drives (ad0). The first dd fails with device not configured, but any subsequent access works fine. It seems it's left in an odd state by the driver start up, but all it takes is a read to get it sorted out again. Any thoughts on how we can help debug this? -- Kevin Street [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
vty3 problem solved, but....
I started a fresh installation with todays floppies. During the installation, I monitored vty1. What I found out is that ifconfig doesn't recognize/config either my modem or cuaa0(ppp0). After clicking "YES" at the "Do you want to try DHCP configuration of the interface" screen, I switched to ALT-F2. It showed: "ifconfig: interface ppp0 does not exist ppp0: not found exiting" However, during boot-up, I hit a key to bring up the commands, and typed "pnpscan". I then typed "autoboot". At the next screen, I used the "CLI" mode to configure my sound card and modem. For the modem, I used "pnp 2 0 enable os irq04 port0 0x3f8". What else can I do? Again, thanks Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA - Trouble mounting secondary master
Kevin Street [EMAIL PROTECTED] writes: Soren Schmidt [EMAIL PROTECTED] writes: Hmm, damn, after the problem went away for Geoff I thought it to be solved since I've never heard of it anywhere else, and I cant reproduce it here no matter what I try. Does it help eany if you only has the root partition use the wd dev and have the rest use the prober ad dev entries ?? It could be some artifact from this... I tried with the ad dev entries for my problem as well with no improvement. I've also tried using: dd if=/dev/ad0s6 of=/dev/null bs=512 count=1 as the first access to one of the failing drives (ad0). The first dd fails with device not configured, but any subsequent access works fine. It seems it's left in an odd state by the driver start up, but all it takes is a read to get it sorted out again. More on this. I just booted with -v and now when I do the first dd I see: ad0: invalid primary partition table: no magic and the same on ad2 when the swapon fails. So how do I get the magic back into my relationship with my drives? -- Kevin Street [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: recent apm changes
Hi, Nate.
I'm sorry if my poor english troubled you.
We should have no problems responding in this amount of time in FreeBSD,
since we don't (didn't used to?) have any code that should cause
significant delay in responding.
My understanding on system suspend code in FreeBSD is that once APM
driver get a system suspend request event from the BIOS, the driver is
hurry to put system into suspend state (execute suspend hooks and call
set power state function for suspend) as soon as possible without any
responses to the BIOS.
I think that this style is cool, I like, and no response to the BIOS
is not violating the APM specification at all, but there are many
BIOSes expecting response from driver. In Linux and NetBSD, they have
last request processing notification to the BIOS before transition into
suspend state. I guess they obtained the same conclusion to support
various BIOS implementations including buggy and bogus BIOSes.
That's why `suspending on Linux is OK, but on FreeBSD' like phenomenon
is there I'd like solve this if possible and need your help or
support.
From Linux code:
static void do_apm_timer(unsigned long unused)
{
int err;
static int pending_count = 0;
if (((standbys_pending 0) || (suspends_pending 0))
(apm_bios_info.version 0x100)
(pending_count-- = 0)) {
pending_count = 4;
err = apm_set_power_state(APM_STATE_BUSY);
if (err)
apm_error("busy", err);
}
From NetBSD code:
static void
apm_event_handle(sc, regs)
struct apm_softc *sc;
struct bioscallregs *regs;
{
int error;
struct bioscallregs nregs;
switch(regs-bx) {
case APM_USER_STANDBY_REQ:
DPRINTF(APMDEBUG_EVENTS, ("apmev: user standby request\n"));
if (apm_do_standby) {
if (apm_record_event(sc, regs-bx))
apm_userstandbys++;
apm_op_inprog++;
(void)apm_set_powstate(APM_DEV_ALLDEVS,
APM_LASTREQ_INPROG);
} else {
(void)apm_set_powstate(APM_DEV_ALLDEVS,
APM_LASTREQ_REJECTED);
/* in case BIOS hates being spurned */
apm_powmgt_enable(1);
}
break;
Last time, we didn't have `Last Request Processing Notification' to
APM BIOS at all for the second case.
Huh? I don't see any mention of 'last request processing notification'
anywhere above. Also, I don't believe the APM driver responds with a
Ah, details are described in `4. Advanced Power Managerment Software
Interface - 4.6.8 Set Power State'. `an appropriate Set Power State
call' includes 'last request processing notification' too.
They say:
Set Power State entry codes of CX=0004h and CX=0005h are used by the
APM Driver to respond to requests from the system BIOS for the
global Standby and Suspend states. The APM Driver uses the Last
Request Processing Notification (0004h) to indicate that it is
currently in the process of determining whether or not to reject the
request. This notification must be sent at least once every five
seconds after the APM driver receives the request by calling Get
Power Management Event. The APM driver must eventually end this
"busy" state by accepting the request, (calling Set Power State with
the appropriate state) or by rejecting the request using CX=0005h.
Thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
isa shared interupts
Hi, does current current support isa cards that use shared interupts on the card (eg. multi sio cards) again? Frank To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vty3 and 4.0 snap 080799
It sounds like ppp is simply exiting immediately. I'll turn debugging on and give it a shot myself; perhaps somebody broke something. - Jordan I should have also stated that I tried all the other "F" keys also. The only vty that is available/active is vty1 for debugging. Every other F-key gets the "beep". HTH in solving my problem fwiw dept.- I have been using FreeBSD since 2.21-R 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
Re: it's time...
After taking a break from this discussion, I do think that I like the idea of wrapping boot messages in a sane way at column n (= 80 by default) so long as one knows where messages from one device end and the next one begin. I'd also oppose things like foo0: .. irq foo0: 9 as opposed to foo0: .. foo0: irq 9 Unless there were so many that this couldn't be avoided... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
IBM ThinkPad 600E with cardbus EtherJet 10/100 :)
Ok... needless to say, I am having problems... 1: any access to the serial port (/dev/cuaa0) locks the machine. 2: I cannot get the ethernet card to work. 2a: It is sort-a recognized by the system, It senses the insert and remove, but it cannot get the CIS. I remember reading somewhere that the CIS on these cards is 'somewhere else' and you can tell pccardd where that is. 2b: I believe that this is in reality a tulip card. I am in no way opposed to beta software, and I will code as need be, I just need to know where things already are before I get my feet wet. -- David Cross | email: [EMAIL PROTECTED] Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science| Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
On Wed, 11 Aug 1999, Warner Losh wrote: No! At some point they should use a facility similar to solaris/sysv where they don't display, but do make it into the dmesg buffer... Warner What in the world would be the point of doing this? What would be so great about not seeing the system boot up? Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
On Wed, 11 Aug 1999, Warner Losh wrote: After taking a break from this discussion, I do think that I like the idea of wrapping boot messages in a sane way at column n (= 80 by default) so long as one knows where messages from one device end and the next one begin. I'd also oppose things like foo0: .. irq foo0: 9 as opposed to foo0: .. foo0: irq 9 Unless there were so many that this couldn't be avoided... check out eisa_reg_print() and eisa_print_child() in sys/i386/eisa/eisaconf.c Sanity in output is a good thing. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
On Wed, 11 Aug 1999, Brian F. Feldman wrote: What in the world would be the point of doing this? What would be so great about not seeing the system boot up? The same reason that when you type 'cp foo /tmp/' it doesn't say '1 file copied, 3425 bytes.' or other nonesense. If nothings wrong then print nothing. Granted, you and I would have our 'boot_verbose' envar set to '1' or '2' or something that gave us the correct amount of feedback we've grown acustom to. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
[[ cc trimmed. ]] In message [EMAIL PROTECTED] "Matthew N. Dodd" writes: : check out eisa_reg_print() and eisa_print_child() in : sys/i386/eisa/eisaconf.c : : Sanity in output is a good thing. Agreed. I like what I see there. Maybe it is time to hoist something like that into bus_subr.c Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bus error in isatty() from /usr/lib/libc.so.3
Hello. I have a reproducable problem which gdb says is ending up at
0x2818d862 in isatty() from /usr/lib/libc.so.3. A full back trace is
below. If this is a problem in FreeBSD, I'm very glad to do any
experiments that might be helpful. If it's a problem somewhere else,
any pointers on what I might do next would be great.
Thanks,
Tim
How to repeat:
I installed MySQL 3.23.2, then DBI-1.11. I compiled
Msql-Mysql-modules-1.2200, and ran the test suite. All but the first
test dumped core, all with this same error.
This is with -CURRENT as of Aug 10 @ 7AM (GMT). I did a complete
make buildworld; make installworld;, then I recompiled the kernel.
tim@threads$ uname -a
FreeBSD threads.polyesthetic.org 4.0-CURRENT FreeBSD 4.0-CURRENT #11: Wed Aug 11
08:57:53 MST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/THREADS i386
tim@threads:/usr/local/src/Msql-Mysql-modules-1.2200/mysql$
LD_LIBRARY_PATH=`pwd`/../blib/arch/auto/DBD/mysql gdb /usr/bin/perl
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
(no debugging symbols found)...
(gdb) run -I../blib/lib t/10dsnlist.t
Starting program: /usr/bin/perl -I../blib/lib t/10dsnlist.t
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
Driver is mysql
1..3
(no debugging symbols found)...(no debugging symbols found)...
_login('database=test' 'tim' 'ign0rant')
(no debugging symbols found)...
Program received signal SIGBUS, Bus error.
0x2818d862 in isatty () from /usr/lib/libc.so.3
(gdb) back
#0 0x2818d862 in isatty () from /usr/lib/libc.so.3
#1 0x2818db22 in isatty () from /usr/lib/libc.so.3
#2 0x2818e1de in malloc () from /usr/lib/libc.so.3
#3 0x28236e88 in _thread_fd_table_init () from /usr/lib/libc_r.so.4
#4 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4
#5 0x28248498 in bind () from /usr/lib/libc_r.so.4
#6 0x2818eeb7 in .cerror () from /usr/lib/libc.so.3
#7 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4
#8 0x28248498 in bind () from /usr/lib/libc_r.so.4
#9 0x2818eeb7 in .cerror () from /usr/lib/libc.so.3
#10 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4
#26905 0x28238056 in _thread_fd_lock_debug () from /usr/lib/libc_r.so.4
#26906 0x28248498 in bind () from /usr/lib/libc_r.so.4
#26907 0x2818eeb7 in .cerror () from /usr/lib/libc.so.3
#26908 0x281dbb95 in my_net_init (net=0x8057c54, nettype=NET_TYPE_SOCKET,
fd=5, pipe=0x0) at net.c:137
#26909 0x281d97be in mysql_real_connect (mysql=0x8057c54,
host=0x281e5bf0 "localhost", user=0x81283d0 "tim",
passwd=0x8128650 "ign0rant", db=0x8108650 "test", port=0,
unix_socket=0x281e5b80 "/tmp/mysql.sock", client_flag=0) at libmysql.c:1194
#26910 0x281c0ba2 in mysql_dr_connect ()
from
/usr/local/src/Msql-Mysql-modules-1.2200/mysql/../blib/arch/auto/DBD/mysql/mysql.so
#26911 0x281c130e in _MyLogin ()
from
/usr/local/src/Msql-Mysql-modules-1.2200/mysql/../blib/arch/auto/DBD/mysql/mysql.so
#26912 0x281c139d in mysql_db_login ()
from
/usr/local/src/Msql-Mysql-modules-1.2200/mysql/../blib/arch/auto/DBD/mysql/mysql.so
#26913 0x281c90cd in XS_DBD__mysql__db__login ()
from
/usr/local/src/Msql-Mysql-modules-1.2200/mysql/../blib/arch/auto/DBD/mysql/mysql.so
#26914 0x280af0b5 in Perl_pp_entersub () from /usr/lib/libperl.so.3
#26915 0x28079d69 in Perl_runops_standard () from /usr/lib/libperl.so.3
#26916 0x280e0519 in perl_call_sv () from /usr/lib/libperl.so.3
#26917 0x281b16a5 in XS_DBI_dispatch ()
from /usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/DBI/DBI.so
#26918 0x280af0b5 in Perl_pp_entersub () from /usr/lib/libperl.so.3
#26919 0x28079d69 in Perl_runops_standard () from /usr/lib/libperl.so.3
#26920 0x280dfd6e in perl_run () from /usr/lib/libperl.so.3
#26921 0x8048da8 in perl_free ()
#26922 0x8048cd5 in perl_free ()
(gdb)
Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration:
Platform:
osname=freebsd, osvers=4.0-current, archname=i386-freebsd
uname='freebsd freefall.freebsd.org 4.0-current freebsd 4.0-current #0: $Date:
1999/05/05 19:09:48 $'
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef useperlio=undef d_sfio=undef
Compiler:
cc='cc', optimize='undef', gccversion=egcs-2.91.66 19990314 (egcs-1.1.2 release)
cppflags=''
ccflags =''
stdchar='char', d_stdstdio=undef, usevfork=true
intsize=4, longsize=4, ptrsize=4, doublesize=8
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
alignbytes=4, usemymalloc=n, prototype=define
Linker and Libraries:
ld='cc', ldflags ='-Wl,-E'
libpth=/usr/lib
Re: it's time...
On Wed, 11 Aug 1999, Warner Losh wrote: In message [EMAIL PROTECTED] "Matthew N. Dodd" writes: : check out eisa_reg_print() and eisa_print_child() in : sys/i386/eisa/eisaconf.c : : Sanity in output is a good thing. Agreed. I like what I see there. Maybe it is time to hoist something like that into bus_subr.c Lets define exactly what we want before we start our charge. What should be printed? device ID attachment point resource reservation device additional When should it be printed? bootverbose levels? How should it printed? ???N: ??? on ???N ... or... Since we've got things partway tied up with new_bus, maybe we should complete the job, and define a device method for printing out the device additional information so it can be dispatched from a single place. How are we going to enforce the use of this 'pretty printer'? Should we embed this logic in device_printf()? This would be practical if our goal were not only impose order on the probe/attach messages but also anything a driver printed (nothing more annoying that stray error messages for which the issuing device is unknown.) I'm not sure this is our goal at this time? Will we ever have such a goal? I see our goal as follows. 1. one unified format for devce probe/attach ammouncments. 2. the ability to control the amount of information printed during the device probe/attach. Anyhow, just trying to stir up some ideas here; please don't take any of my statements as an indication of intended course. I really don't have any good answers at this point and would like to hear the opinions of others. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ATA - Trouble mounting secondary master
I just rebooted on an August 11 kernel. My system still is happy with the disks. Hmm. I can't remember exactly where my tracing went, before I left off before, but the message you are seeing comes from /sys/i386/isa/diskslice_machdep.c, line 200 (version 1.35). What you will probably find, is that if you put a line that goes: goto reread_mbr instead of "goto done", you will find that, on the second attempt, it reads the mbr successfully. The above is a severe kludge, and that is why I never committed any code to do anything of the sort. I think the error is actually somewhere in the ATA code (sorry Soren). I don't want to patch around a bug. Now somebody remarked that after the probe, a drive status light stayed on - maybe, the probe is not doing something properly for some drives, or there is somethign timing out. -Original Message- From: Kevin Street [mailto:[EMAIL PROTECTED]] Sent: 12 August 1999 03:10 To: Soren Schmidt Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: ATA - Trouble mounting secondary master Kevin Street [EMAIL PROTECTED] writes: Soren Schmidt [EMAIL PROTECTED] writes: Hmm, damn, after the problem went away for Geoff I thought it to be solved since I've never heard of it anywhere else, and I cant reproduce it here no matter what I try. Does it help eany if you only has the root partition use the wd dev and have the rest use the prober ad dev entries ?? It could be some artifact from this... I tried with the ad dev entries for my problem as well with no improvement. I've also tried using: dd if=/dev/ad0s6 of=/dev/null bs=512 count=1 as the first access to one of the failing drives (ad0). The first dd fails with device not configured, but any subsequent access works fine. It seems it's left in an odd state by the driver start up, but all it takes is a read to get it sorted out again. More on this. I just booted with -v and now when I do the first dd I see: ad0: invalid primary partition table: no magic and the same on ad2 when the swapon fails. So how do I get the magic back into my relationship with my drives? -- Kevin Street [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
