ATA DVD-ROM failure
Hi everyone, I haven't been using my DVD-ROM in my Fujitsu/Siemens S-1540 series laptop with FreeBSD for some time, so I don't know how long this problem has been. (I used it quite a bit when installing, so it hasn't always been like this) When I boot up or do a atacontrol reinit 0 I get ata0: resetting devices .. ata0-slave: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED done Does anyone recognize this or have any idea why this happens or how I can debug it further to get an idea? Cheers Nik ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng ate my hampster...
It seems Ashley Penney wrote: Hiya, I recently upgraded my -current box, only to have my Serial ATA device move from ar0 to ad6, making things cry. Read UPDATING!! (hint you need to include device ataraid in your config). -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bad performance
hi, i did a lot of changes and tests last night :) -u were right there was a bug in the network config (i fixed some named entries) now netstat -r is really fast (no timeouts which occured before) -i wrote a simple c test program using gethostname, gethostbyname, gethostbyaddr as suggested it work fine -i disabled all these debugging options in kernel and did that ln -s aj /etc/malloc.conf thing all in all performance seem to be better now :) BUT: i have a lot trouble with the new kernel (without debug) - pf.ko cannot be loaded - evolution is unable to send mails (core dump) - possible a different problem - vmware crashes - AND: the whole system crashed 3 times with FS problems since the last crash i am unable to clean up the ufs2 using fsck !!! now my system is DEAD i guess :'( any ideas how to at least be able to boot fbsd agian ?? many thx seb -- COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test -- 1. GMX TopMail - Platz 1 und Testsieger! 2. GMX ProMail - Platz 2 und Preis-Qualitätssieger! 3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
fsck failed after hard crash
hi, i did cvsup for /usr/src yesterday and did a build world. i also build a new kernel without all these debugging things. i rebooted the system and everything went fine first but then i tried to recompile pf_freebsd and the system crashed. i rebooted and did fsck and tried the rebuild again - same thing :( reboot again, fsck with many errors (some sectors could not be written, inconsistancy soft updates). i managed to start gnome2 agian. i started vmware and ... crash agin :'( so i thought of using the old kernel again but when i restart and run fsck it is NOT able to mark /usr as clean !! :( what can i do now ? any ideas ? thx seb -- COMPUTERBILD 15/03: Premium-e-mail-Dienste im Test -- 1. GMX TopMail - Platz 1 und Testsieger! 2. GMX ProMail - Platz 2 und Preis-Qualitätssieger! 3. Arcor - 4. web.de - 5. T-Online - 6. freenet.de - 7. daybyday - 8. e-Post ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ATAng vs Aladdin chipset
ASUS P5A or P5AB (one of each now) - won't boot without setting hw.ata.ata_dma=0. GEOM recognizes the drive itself but then the reads of the disklabels fail with a message that I can't find in the source, about a DMA failure. System then prompts to mount root and nothing I type works. I see looking at the list archive that I'm not the only one with this problem. The message appears 3 times per drive with some seconds between, implying to me that it is (at least) a missing interrupt (or completely missing operation?). If anyone wants I could take the trouble to set up a serial console and capture the output. I suspect that is already done somewhere though. Approx same cvsup time works fine in my laptop running ICH3 chipset. Then again, Intel != Acer :-) At least I figured out a bypass easily... Makes make world lots slower but at least works. Other (unrelated?) minor problem in past (don't know if it's still there); acpi timer doesn't work right on this chipset either (ran clock at approx double rate with lots of went backwards messages). Appears better now at least on one example (non-ASUS board, though) - at least ntp is happy. -- Pete ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng vs Aladdin chipset
Well, I misspoke on the timer; the one that works is booting in non-acpi mode by beasties choice; the older one still fails if I comment the acpi ignore timer statement. Actually that one appears to run slow by about half. Both fail equally in ATAng so acpi isn't making any difference (nor does it appear to make much if any other difference in the motherboard operation); on the laptop acpi is necessary to make PCMCIA work at all, among other things. -- Pete ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade from static to dynamic root
On Thu, Sep 11, 2003 at 02:44:55PM +0200, Harti Brandt wrote:
Hi,
I just tried to upgrade one of my systems from a static root from july to
an actual dynamic root. The installworld went fine 'til the place where
/bin/test is installed. At that point the installation stopped with ELF
interpreter /libexec/ld-elf.so.1 not found. And really /libexec is not
populated yet. May it be, that the makefile uses one of the newly
installed tools during install? For example 'ln' to make the link test -
[?
It shouldn't happen, because we save test and [ in ${INSTALLTMP}.
It looks like something hardcodes /bin/test. I've grepped the
src/ makefiles and cannot find such a place. Where exactly did
it happen in the installworld for you?
Also, wouldn't it be helpful to populate /rescue before /bin? Just in
the case something goes wrong between installing been and rescue for the
first time?
Good idea!
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
[EMAIL PROTECTED] Sunbay Software Ltd,
[EMAIL PROTECTED] FreeBSD committer
pgp0.pgp
Description: PGP signature
Re: ATA problems(unlean fs) on recent cvsup
Just a follow up. I've since been able to get my -CURRENT system running under the new build. However the booting process is still slow around those ata?: [MPSAFE] messages. Any ideas on getting a speed up? -Al ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA problems(unlean fs) on recent cvsup
It seems Alastair G. Hogge wrote: Just a follow up. I've since been able to get my -CURRENT system running under the new build. However the booting process is still slow around those ata?: [MPSAFE] messages. Any ideas on getting a speed up? I'm working on it... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng vs Aladdin chipset
It seems Pete Carah wrote: ASUS P5A or P5AB (one of each now) - won't boot without setting hw.ata.ata_dma=0. GEOM recognizes the drive itself but then the reads of the disklabels fail with a message that I can't find in the source, about a DMA failure. System then prompts to mount root and nothing I type works. I see looking at the list archive that I'm not the only one with this problem. The message appears 3 times per drive with some seconds between, implying to me that it is (at least) a missing interrupt (or completely missing operation?). I'm aware of the problem, I dont know why it happens though. I do have a P5A somewhere in the attic, I'll give it a go as soon as I get the time... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA problems(unlean fs) on recent cvsup
Hi... Sorry to do a me too, but I have a similar problem after a cvsup midday on the 13th September. The previous kernel was pre-ATAng. The machine panic'd after inserting a friends wireless PCMCIA card (but that's probably another unrelated issue), rebooted and left me in single user after failing to automatically run fsck. Prior to that it had booted fine when the disks were clean. Unfortunately, I wasn't able to copy down the exact error messages it printed in the failed fsck_ufs. But they were definitely of the form CANNOT WRITE BLK: and the fsck then died with a SIGABRT. A manual fsck of the disks has got me back up and running and the machine now boots multiuser without fsck terminating abnormally, but still seems unable to resolve the inconsistencies on-disk. http://www.silent.co.uk/freebsd/ ... contains a dmesg and messages log of the failing background fsck if they are of any help. I will try to investigate further but please get in touch if there is more information I can provide. Cheers, Si On Sun, Sep 14, 2003 at 03:52:33PM +1000, Alastair G. Hogge wrote: Hello list, I've recently cvsup'd current (14th of Sep). After a build and install world/kernel I rebooted to find some new and interesting kernel messages about ata? MPSAFE. Well as the booting continued I notcied the machine was going through more disk activity then usal. It was also taking alot longer to actully start. Eventully the kernel dropped into single user mode. It appears my filesystem is playing up for some reason. I haven't had any power failures for random hangs/reboots. After the recent cvsup my /usr fs appears to be coruppt or something. In single user mode I'm unable fix the problem with fsck. At first when I had softupdates /usr fsck would give me messages like UNEXPECTED SOFT UPDATE INCONSISTENCY I turned of softupate to see if it would help...it didn't. I still can't fix the fs. I get output like CANNOT WRITE BLK: xxx and I'm always unable to salvage blks and what not. Anyway my dmesg is as follows: Copyright (c) 1992-2003 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.1-CURRENT #0: Sun Sep 14 12:59:35 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel.GENERIC/kernel at 0xc076. Preloaded elf module /boot/modules/acpi.ko at 0xc076024c. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2533.05-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 536854528 (511 MB) avail memory = 513466368 (489 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P4S8Xon motherboard pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00f1720 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 2 INTA is routed to irq 11 pcib0: slot 3 INTA is routed to irq 9 pcib0: slot 3 INTB is routed to irq 9 pcib0: slot 3 INTC is routed to irq 9 pcib0: slot 14 INTA is routed to irq 11 agp0: SiS 648 host to AGP bridge mem 0xe000-0xe7ff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib1: slot 0 INTA is routed to irq 11 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 fwohci0: vendor=1039, dev=7007 fwohci0: 1394 Open Host Controller Interface mem 0xde80-0xde800fff at device 2.3 on pci0 pcib0: slot 2 INTB is routed to irq 5 fwohci0: [MPSAFE] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:e0:18:00:00:0a:83:4c fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 if_fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:0a:83:4c sbp0: SBP2/SCSI over firewire on firewire0 fwohci0: Initiate bus reset atapci0: SiS 963 UDMA133 controller port 0xb400-0xb40f,0xb800-0xb803,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 irq 11 at device 2.5 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: multimedia, audio at device 2.7 (no driver attached) ohci0: SiS 5571 USB controller mem 0xde00-0xde000fff irq 9 at device 3.0 on pci0 usb0: OHCI version 1.0, legacy
-pthread is deprecated
hello, as you know, there is no more -pthread gcc flag in -current. but many ports (kde3, for example) still wants it. So what should I do to compile kde3 succesfully? The one way I see now is to s/-pthread/-lc_r/g in Makefiles :-) maybe there is another way? Thank you. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA problems(unlean fs) on recent cvsup
I've seen that too, although my problem was with my Alcatel Speedtouch 330 which routinely panics the system. I'djust retrieved usr from a backup to get round it, and put it down to the perils of -current, but if there is really a problem, I can investigate further here. Mark Simon Brown wrote: Hi... Sorry to do a me too, but I have a similar problem after a cvsup midday on the 13th September. The previous kernel was pre-ATAng. The machine panic'd after inserting a friends wireless PCMCIA card (but that's probably another unrelated issue), rebooted and left me in single user after failing to automatically run fsck. Prior to that it had booted fine when the disks were clean. Unfortunately, I wasn't able to copy down the exact error messages it printed in the failed fsck_ufs. But they were definitely of the form CANNOT WRITE BLK: and the fsck then died with a SIGABRT. A manual fsck of the disks has got me back up and running and the machine now boots multiuser without fsck terminating abnormally, but still seems unable to resolve the inconsistencies on-disk. http://www.silent.co.uk/freebsd/ ... contains a dmesg and messages log of the failing background fsck if they are of any help. I will try to investigate further but please get in touch if there is more information I can provide. Cheers, Si On Sun, Sep 14, 2003 at 03:52:33PM +1000, Alastair G. Hogge wrote: Hello list, I've recently cvsup'd current (14th of Sep). After a build and install world/kernel I rebooted to find some new and interesting kernel messages about ata? MPSAFE. Well as the booting continued I notcied the machine was going through more disk activity then usal. It was also taking alot longer to actully start. Eventully the kernel dropped into single user mode. It appears my filesystem is playing up for some reason. I haven't had any power failures for random hangs/reboots. After the recent cvsup my /usr fs appears to be coruppt or something. In single user mode I'm unable fix the problem with fsck. At first when I had softupdates /usr fsck would give me messages like UNEXPECTED SOFT UPDATE INCONSISTENCY I turned of softupate to see if it would help...it didn't. I still can't fix the fs. I get output like CANNOT WRITE BLK: xxx and I'm always unable to salvage blks and what not. Anyway my dmesg is as follows: Copyright (c) 1992-2003 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.1-CURRENT #0: Sun Sep 14 12:59:35 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel.GENERIC/kernel at 0xc076. Preloaded elf module /boot/modules/acpi.ko at 0xc076024c. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.53GHz (2533.05-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 536854528 (511 MB) avail memory = 513466368 (489 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P4S8Xon motherboard pcibios: BIOS version 2.10 Using $PIR table, 11 entries at 0xc00f1720 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 2 INTA is routed to irq 11 pcib0: slot 3 INTA is routed to irq 9 pcib0: slot 3 INTB is routed to irq 9 pcib0: slot 3 INTC is routed to irq 9 pcib0: slot 14 INTA is routed to irq 11 agp0: SiS 648 host to AGP bridge mem 0xe000-0xe7ff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib1: slot 0 INTA is routed to irq 11 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 2.0 on pci0 isa0: ISA bus on isab0 fwohci0: vendor=1039, dev=7007 fwohci0: 1394 Open Host Controller Interface mem 0xde80-0xde800fff at device 2.3 on pci0 pcib0: slot 2 INTB is routed to irq 5 fwohci0: [MPSAFE] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:e0:18:00:00:0a:83:4c fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 if_fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:0a:83:4c sbp0: SBP2/SCSI over firewire on firewire0 fwohci0: Initiate bus reset atapci0: SiS 963 UDMA133 controller port 0xb400-0xb40f,0xb800-0xb803,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 irq 11 at device 2.5 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq
Re: SOS: ATAng: Broke my ATA (ICH3).
backing off to ata-lowlevel.c 1.10 allows me to boot again. --On Saturday, September 13, 2003 18:54:18 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: --On Saturday, September 13, 2003 18:09:21 -0500 Larry Rosenman [EMAIL PROTECTED] wrote: I have a ICH3 controller, and a 9/9 kernel works just fine, but a today kernel hangs(!) after printing ata0: [MPSAFE] Here is the GOOD dmesg: $ dmesg|grep ata atapci0: Intel ICH3 UDMA100 controller port 0x1c20-0x1c2f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 mem 0xe010-0xe01003ff at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ad0: 57231MB FUJITSU MHS2060AT [116280/16/63] at ata0-master UDMA100 acd0: CDRW SONY CD-RW CRX800E at ata1-master WDMA2 cd0 at ata1 bus 0 target 0 lun 0 $ Any ideas? LER For the record, I also pulled atapicam out of the kernel, and the same thing happens. Where to, folks? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: -pthread is deprecated
On Sun, 14 Sep 2003, tokza wrote: hello, as you know, there is no more -pthread gcc flag in -current. but many ports (kde3, for example) still wants it. So what should I do to compile kde3 succesfully? The one way I see now is to s/-pthread/-lc_r/g in Makefiles :-) maybe there is another way? Thank you. Please see ports@ or [EMAIL PROTECTED] Also for reference: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=629118+0+archive/2001/freebsd-current/20010218.freebsd-current -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck failed after hard crash
On Sun, Sep 14, 2003 at 11:42:21AM +0200, Sebastian Ssmoller wrote: i did cvsup for /usr/src yesterday and did a build world. i also build a new kernel without all these debugging things. If you're running FreeBSD-current, I would suggest that you put the debugging options back into your kernel. i rebooted the system and everything went fine first but then i tried to recompile pf_freebsd and the system crashed. Without debugging or even a panic message, it is fairly difficult to make any useful suggestions. i rebooted and did fsck and tried the rebuild again - same thing :( Panic message? reboot again, fsck with many errors (some sectors could not be written, inconsistancy soft updates). i managed to start gnome2 agian. i started vmware and ... crash agin :'( Are you sure you don't want to run FreeBSD 4.8? so i thought of using the old kernel again but when i restart and run fsck it is NOT able to mark /usr as clean !! :( what can i do now ? any ideas ? When fsck fails to clean /usr are there any error messages? What fsck command did you issue to clean up /usr? Did you try using an alternate super block? What compiler flags did you use to build the kernel? -- Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck failed after hard crash
I'm seeing similar messages from fsck: unexpected soft-update inconsistency, unable to write block, etc. going back to my 9/9/2003 good kernel, it works. so I think SOMETHING broke here. LER --On Sunday, September 14, 2003 08:30:51 -0700 Steve Kargl [EMAIL PROTECTED] wrote: On Sun, Sep 14, 2003 at 11:42:21AM +0200, Sebastian Ssmoller wrote: i did cvsup for /usr/src yesterday and did a build world. i also build a new kernel without all these debugging things. If you're running FreeBSD-current, I would suggest that you put the debugging options back into your kernel. i rebooted the system and everything went fine first but then i tried to recompile pf_freebsd and the system crashed. Without debugging or even a panic message, it is fairly difficult to make any useful suggestions. i rebooted and did fsck and tried the rebuild again - same thing :( Panic message? reboot again, fsck with many errors (some sectors could not be written, inconsistancy soft updates). i managed to start gnome2 agian. i started vmware and ... crash agin :'( Are you sure you don't want to run FreeBSD 4.8? so i thought of using the old kernel again but when i restart and run fsck it is NOT able to mark /usr as clean !! :( what can i do now ? any ideas ? When fsck fails to clean /usr are there any error messages? What fsck command did you issue to clean up /usr? Did you try using an alternate super block? What compiler flags did you use to build the kernel? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
unable to get dumps?
Is there a known issue with recent -CURRENT (between September 10, 2003 and today) where you can't get a panic dump? I have a kernel from yesterday's sources (modulo a reversion of ata-lowlevel to version 1.10 because 1.11 won't boot), and some debugging code from Nate Lawson to debug my ACPI issue. When I hit DDB, and type panic, it says it's dumping, but NO disk I/O occurs. What can I get to help this? Also, when coming back up after the Panic on the same kernel, we get unexpected soft-update inconsistencies, cannot write block type errors from FSCK. Going back to my September 9, 2003 kernel, fsck deals with the same exact filesystem just fine. What can I get to help with this issue as well? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: fsck failed after hard crash
Am Son, 2003-09-14 um 17.30 schrieb Steve Kargl: On Sun, Sep 14, 2003 at 11:42:21AM +0200, Sebastian Ssmoller wrote: i did cvsup for /usr/src yesterday and did a build world. i also build a new kernel without all these debugging things. If you're running FreeBSD-current, I would suggest that you put the debugging options back into your kernel. sorry to forget to post these info's: i am running freebsd-current. started with 5.1 release and updated yesterday. i removed the debugging stuff from the kernel cause i wanted to check the possible performance difference. i rebooted the system and everything went fine first but then i tried to recompile pf_freebsd and the system crashed. Without debugging or even a panic message, it is fairly difficult to make any useful suggestions i agree but this would be difficult when being unable to reboot the system :) . i rebooted and did fsck and tried the rebuild again - same thing :( Panic message? no message :( first time it froze , second time it rebooted. reboot again, fsck with many errors (some sectors could not be written, inconsistancy soft updates). i managed to start gnome2 agian. i started vmware and ... crash agin :'( Are you sure you don't want to run FreeBSD 4.8? good question :) so i thought of using the old kernel again but when i restart and run fsck it is NOT able to mark /usr as clean !! :( what can i do now ? any ideas ? When fsck fails to clean /usr are there any error messages? What fsck command did you issue to clean up /usr? Did you try using an alternate super block? i ran: fsck -y /usr and it complains several times (!) about unexpected soft-update inconsistency and unable to write block :( i have not tried an alternate super block yet - i was not sure whether this could help, could it ? What compiler flags did you use to build the kernel? i used default settings finally i found out that i can mount /usr readonly so a backup could be possible (?); creating new ufs2 and restore backup could be a possible solution (?) thx seb -- Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unable to get dumps?
It seems Larry Rosenman wrote: Also, when coming back up after the Panic on the same kernel, we get unexpected soft-update inconsistencies, cannot write block type errors from FSCK. Going back to my September 9, 2003 kernel, fsck deals with the same exact filesystem just fine. What if you use kernel src from sep 9 with just dev/ata updated to latest ? -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unable to get dumps?
--On Sunday, September 14, 2003 18:46:19 +0200 Soren Schmidt [EMAIL PROTECTED] wrote: It seems Larry Rosenman wrote: Also, when coming back up after the Panic on the same kernel, we get unexpected soft-update inconsistencies, cannot write block type errors from FSCK. Going back to my September 9, 2003 kernel, fsck deals with the same exact filesystem just fine. What if you use kernel src from sep 9 with just dev/ata updated to latest ? how can I do that from a CVSup'd source tree? (I'm lucky to still have the 9/9/2003 binary). LER -Søren -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: unable to get dumps?
--On Sunday, September 14, 2003 18:46:19 +0200 Soren Schmidt [EMAIL PROTECTED] wrote: It seems Larry Rosenman wrote: Also, when coming back up after the Panic on the same kernel, we get unexpected soft-update inconsistencies, cannot write block type errors from FSCK. Going back to my September 9, 2003 kernel, fsck deals with the same exact filesystem just fine. What if you use kernel src from sep 9 with just dev/ata updated to latest ? Also, did you see my note about the hang with ata-lowlevel.c r1.11? -Søren -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: ATA DVD-ROM failure
On Sun, 14 Sep 2003 09:41:44 +0200 (CEST) Niklas Saers Mailinglistaccount [EMAIL PROTECTED] wrote: Hi everyone, I haven't been using my DVD-ROM in my Fujitsu/Siemens S-1540 series laptop with FreeBSD for some time, so I don't know how long this problem has been. (I used it quite a bit when installing, so it hasn't always been like this) When I boot up or do a atacontrol reinit 0 I get ata0: resetting devices .. ata0-slave: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED done Does anyone recognize this or have any idea why this happens or how I can debug it further to get an idea? The same here (on a workstation) with an AOpen DVD reader. Before ATAng it works perfectly and was recognized as: acd0: DVD-ROM AOPEN 16XDVD-ROM/AMH 20010712 at ata1-master UDMA33 Now: ata1-master: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED ata1-master: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED My 0.2, Dario -- Dario Freni ([EMAIL PROTECTED]) - SaturNero on IRCNet, Azzurra Gruppo Utenti FreeBSD Italia (http://www.gufi.org) GPG Public key at http://www.saturnero.net/saturnero.asc pgp0.pgp Description: PGP signature
Re: fsck failed after hard crash
Am Son, 2003-09-14 um 17.49 schrieb Larry Rosenman: I'm seeing similar messages from fsck: unexpected soft-update inconsistency, unable to write block, etc. going back to my 9/9/2003 good kernel, it works. i tried to use my old kernel; build with sources from fbsd 5.1 release). i rebooted the system and started fsck -y /usr again but the same problems occur :( now there are two possibilities i guess: - something in userland is broken too - my ufs2 is really dead any ideas ? seb so I think SOMETHING broke here. LER --On Sunday, September 14, 2003 08:30:51 -0700 Steve Kargl [EMAIL PROTECTED] wrote: On Sun, Sep 14, 2003 at 11:42:21AM +0200, Sebastian Ssmoller wrote: i did cvsup for /usr/src yesterday and did a build world. i also build a new kernel without all these debugging things. If you're running FreeBSD-current, I would suggest that you put the debugging options back into your kernel. i rebooted the system and everything went fine first but then i tried to recompile pf_freebsd and the system crashed. Without debugging or even a panic message, it is fairly difficult to make any useful suggestions. i rebooted and did fsck and tried the rebuild again - same thing :( Panic message? reboot again, fsck with many errors (some sectors could not be written, inconsistancy soft updates). i managed to start gnome2 agian. i started vmware and ... crash agin :'( Are you sure you don't want to run FreeBSD 4.8? so i thought of using the old kernel again but when i restart and run fsck it is NOT able to mark /usr as clean !! :( what can i do now ? any ideas ? When fsck fails to clean /usr are there any error messages? What fsck command did you issue to clean up /usr? Did you try using an alternate super block? What compiler flags did you use to build the kernel? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck failed after hard crash
--On Sunday, September 14, 2003 19:02:17 +0200 Sebastian Ssmoller [EMAIL PROTECTED] wrote: Am Son, 2003-09-14 um 17.49 schrieb Larry Rosenman: I'm seeing similar messages from fsck: unexpected soft-update inconsistency, unable to write block, etc. going back to my 9/9/2003 good kernel, it works. i tried to use my old kernel; build with sources from fbsd 5.1 release). i rebooted the system and started fsck -y /usr again but the same problems occur :( now there are two possibilities i guess: - something in userland is broken too - my ufs2 is really dead I'm using ufs1, FWIW, and my userland is from september 9 as well. So, either 5.1R is too far back or you are in trouble. FWIW. any ideas ? seb so I think SOMETHING broke here. LER --On Sunday, September 14, 2003 08:30:51 -0700 Steve Kargl [EMAIL PROTECTED] wrote: On Sun, Sep 14, 2003 at 11:42:21AM +0200, Sebastian Ssmoller wrote: i did cvsup for /usr/src yesterday and did a build world. i also build a new kernel without all these debugging things. If you're running FreeBSD-current, I would suggest that you put the debugging options back into your kernel. i rebooted the system and everything went fine first but then i tried to recompile pf_freebsd and the system crashed. Without debugging or even a panic message, it is fairly difficult to make any useful suggestions. i rebooted and did fsck and tried the rebuild again - same thing :( Panic message? reboot again, fsck with many errors (some sectors could not be written, inconsistancy soft updates). i managed to start gnome2 agian. i started vmware and ... crash agin :'( Are you sure you don't want to run FreeBSD 4.8? so i thought of using the old kernel again but when i restart and run fsck it is NOT able to mark /usr as clean !! :( what can i do now ? any ideas ? When fsck fails to clean /usr are there any error messages? What fsck command did you issue to clean up /usr? Did you try using an alternate super block? What compiler flags did you use to build the kernel? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: mysql-client compiler error
On Sat, 13 Sep 2003, Matt wrote: After building world as of late last night I decided to portupgrade -rRaf, mainly due to having the libintl.so.4 missing problem when I tried to start X. Everything compiled perfectly fine (and X is now working fine) except for databases/mysql40-client. I get this error: checking for C compiler default output... configure: error: C compiler cannot create executables configure: error: could not configure Berkeley DB Whenever autoconf explodes, check config.log in the same directory as the configure script to find out why. All it does is compile a 'hello world' program which has no dependencies in this target (I think). -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mystery kernel spew
On Sat, 13 Sep 2003, masta wrote: For some time now I've have an issue with a dell laptop I use. It spews a bunch of kernel junk after init is spawned, and the spew causes my dmesg to become too full to actually produce a file I can send to the list that is meaningfull. I remember this :) This is probably because you have a syntax error in sysctl.conf. The stuff thats printed is the sysctl tree. Its a debugging feature, although I've forgotten what exactly triggers it. sysctl.conf should be name=value pairs like this: kern.maxfiles=16384 -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with ATAng and cdparanoia
On Sun, 07 Sep 2003 13:01:13 +, Arjan van Leeuwen wrote: Hi, Since the ATAng import, I can't use the cd ripper cdparanoia (audio/cdparanoia) with my IDE CD-ROM drive. When I direct cdparanoia to device /dev/acd0, it will exit with the message 006: Could not read any data from drive Cdparanoia could not find a way to read audio from this drive. If, however, I use the atapicam device to rip (I have to set the device to /dev/cd1 for that), it works without any problem. Before ATAng, I could use cdparanoia on both devices, now I can only use the atapicam one, which probably means that people without atapicam can't use cdparanoia at all. Hi, I noticed that after ATAng import you need root privileges to use cdparanoia. Just try running cdparanoia under root, or give it a setuid bit. Worked for me. -- Pav Lucistnik [EMAIL PROTECTED] What do we know about love? Love is like a pear. Pear is sweet and have a specific shape. Try to exactly define the shape of a pear. -- Marigold: 50 Years Of Poetry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA DVD-ROM failure
It seems Dario Freni wrote: ata0: resetting devices .. ata0-slave: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED done Does anyone recognize this or have any idea why this happens or how I can debug it further to get an idea? The same here (on a workstation) with an AOpen DVD reader. Before ATAng it works perfectly and was recognized as: acd0: DVD-ROM AOPEN 16XDVD-ROM/AMH 20010712 at ata1-master UDMA33 Now: ata1-master: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED This is with an uptodate -current ? Could you please boot verbose and mail me the output of dmesg ? -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bikeshed
On Friday, 12 September 2003 at 5:10:39 +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], [EMAIL PROTECTED] ibsd.org writes: Did you ever consider that your doing exactly what phk's logo protests? ;) Maybe that is why phk hasn't responded any further, because he's laughing at you! You have to admit that is just a bit ironic. Well, the reason I didn't answer until now was that I was eating some sort of fish (species now forgotten). But let me make it 100% clear: You can use the no bikeshed logo for anything you want, anywhere you want, anytime you want with the following simple exception: YOU MAY NOT UNDER ANY CIRCUMSTANCES _EVER_ make it the subject of a bikeshed discussion. The question is, can you restrict use of the topic in this manner? Since you have received no consideration for the topic, in most countries you can't restrict its use. Greg -- See complete headers for address and phone numbers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mystery kernel spew
I owe you a beer Doug (or a soda-pop)! ;) You were correct about the sysctl.conf being the root-cause of the kernel spew. My sysctl.conf is having these lines: #security.bsd.see_other_uids=0 sysctl net.inet.tcp.blackhole=1 sysctl net.inet.udp.blackhole=1 See the fau paux? I must have decided to yank/paste the example incorrectly from the BLACKHOLE(4) manual, because I also included the sysctl word at the begining of the two lines. To error is human, but this is utter comedy if you ask me. =) I'm now able to use dmesg again, wuhoo! Thanks! -masta Allegedly Doug Whitesaid On Sat, 13 Sep 2003, masta wrote: For some time now I've have an issue with a dell laptop I use. It spews a bunch of kernel junk after init is spawned, and the spew causes my dmesg to become too full to actually produce a file I can send to the list that is meaningfull. I remember this :) This is probably because you have a syntax error in sysctl.conf. The stuff thats printed is the sysctl tree. Its a debugging feature, although I've forgotten what exactly triggers it. sysctl.conf should be name=value pairs like this: kern.maxfiles=16384 -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org __ __ _ | \/ | __ _ ___| |_ __ _ | |\/| |/ _` / __| __/ _` | | | | | (_| \__ \ || (_| | |_| |_|\__,_|___/\__\__,_| [EMAIL PROTECTED] http://wifibsd.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Dumps with ATAng?
Can ANYONE out there get a panic dump on an ATA disk with ATAng? I can't get my 9/9/2003 kernel to dump, nor a current -CURRENT. Thanks, LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
mdmfs: newfs exited with error code 36
mdmfs don't work on CURRENT diskless sparc64: Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point. Starting file system checks: nfs: can't update /var/db/mounttab for 1.1.1.1:/sparc64/netboot cp: utmp: Read-only file system /etc/rc.d/cleanvar: cannot create /var/run/clean_var: Read-only file system +++ mount_md of /var mdmfs: newfs exited with error code 36 nfs: can't update /var/db/mounttab for 1.1.1.1:/sparc64/netboot . dropping into shell, ^D to continue anyway. # mdmfs -i 4096 -s 32m -M md /var mdmfs: newfs exited with error code 36 # mdmfs -i 4096 -s 16m -M md /var # df -h Filesystem Size Used Avail Capacity Mounted on 1.1.1.1:/sparc64/netboot16G 3.0G11G21%/ devfs 1.0K 1.0K 0B 100%/dev /dev/md215M 2.0K14M 0%/var # top last pid: 124; load averages: 0.01, 0.05, 0.03 up 0+00:09:58 23:30:01 4 processes: 1 running, 3 sleeping Mem: 2864K Active, 1544K Inact, 10M Wired, 40K Cache, 3392K Buf, 472M Free Swap: PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND 93 root 80 5440K 1448K wait 0:00 0.00% 0.00% sh 35 root 80 5408K 1408K wait 0:00 0.00% 0.00% sh 109 root 80 5216K 1320K wait 0:00 0.00% 0.00% sh 124 root 960 6808K 1480K RUN 0:00 0.00% 0.00% top P.S. On current 20030825 diskless operations works fine. Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA DVD-ROM failure
On Sun, 14 Sep 2003 20:08:17 +0200 (CEST) Soren Schmidt [EMAIL PROTECTED] wrote: This is with an uptodate -current ? pigra:/home/saturnero uname -a FreeBSD pigra.saturnero.sat 5.1-CURRENT FreeBSD 5.1-CURRENT #10: Mon Sep 8 01:15:32 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PIGRA i386 (sources of 7 Sep) Could you please boot verbose and mail me the output of dmesg ? Sure. That's in attachment. -- Dario Freni ([EMAIL PROTECTED]) - SaturNero on IRCNet, Azzurra Gruppo Utenti FreeBSD Italia (http://www.gufi.org) GPG Public key at http://www.saturnero.net/saturnero.asc dmesg.txt Description: Binary data pgp0.pgp Description: PGP signature
Re: ATAng regression: cdcontrol close not working
V so, 06. 09. 2003 v 21:41, Bruce Evans pe:
On Sat, 6 Sep 2003, Pav Lucistnik wrote:
after recent ATAng changes, cdcontrol close stopped working
with my CD-ROM drive. It used to close the tray. It works with -f
/dev/cd0 but not with /dev/acd0. cdcontrol eject still works fine.
I use the following fix:
%%%
Index: atapi-cd.c
===
RCS file: /home/ncvs/src/sys/dev/ata/atapi-cd.c,v
retrieving revision 1.142
diff -u -2 -r1.142 atapi-cd.c
--- atapi-cd.c5 Sep 2003 10:40:16 - 1.142
+++ atapi-cd.c6 Sep 2003 17:16:16 -
@@ -1870,7 +1913,7 @@
int error;
-if ((error = acd_start_stop(cdp, 0)) == EBUSY) {
+if ((error = acd_start_stop(cdp, 0)) == EBUSY || close) {
if (!close)
- return 0;
+ return EBUSY;
if ((error = acd_start_stop(cdp, 3)))
return error;
@@ -1882,6 +1925,4 @@
if (error)
return error;
-if (close)
- return 0;
acd_prevent_allow(cdp, 0);
cdp-flags = ~F_LOCKED;
%%%
acd_eject() doesn't seem to have been changed by ATAng, so I don't see how
close it could have ever worked, but I seem to remember it working.
This patch works for me. Any chance to get it committed?
Relevant dmesg parts:
...
cd0 at ata1 bus 0 target 0 lun 0
cd0: TEAC CD-532E-B 1.0A Removable CD-ROM SCSI-0 device
cd0: 16.000MB/s transfers
cd0: cd present [357072 x 2048 byte records]
I do have atapicam in my kernel.
Close works on cd0 and cd1 for me without the above patch. The code for
eject and close in scsi_cd.c is easier to understand.
Yes, for me too. I haven't tought to try cdcontrol on /dev/cd0 before,
thank you for the tip.
--
Pav Lucistnik [EMAIL PROTECTED]
What do we know about love? Love is like a pear. Pear is sweet and have
a specific shape. Try to exactly define the shape of a pear.
-- Marigold: 50 Years Of Poetry
signature.asc
Description: Toto je =?iso-8859-2?Q?digit=E1ln=EC?= =?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?= =?ISO-8859-1?Q?_zpr=E1vy?=
Re: mdmfs: newfs exited with error code 36
* Deiter Alexandr Valerievich [EMAIL PROTECTED] [2003-09-14 22:10]: mdmfs: newfs exited with error code 36 This error seems to be generic, I see it on i386 too. I usually mount /tmp with the following entry from fstab: md /tmp mfs rw,-s250m 2 0 This gives the newfs error mentioned above. Doing the steps by hand I get: # mdconfig -a -t swap -s 256m md4 # newfs /dev/md4 /dev/md4: 256.0MB (524288 sectors) block size 16384, fragment size 4096 using 4 cylinder groups of 64.02MB, 4097 blks, 4160 inodes. super-block backups (for fsck -b #) at: 160, 131264, 262368, 393472 newfs: wtfs: 4096 bytes at sector 192: Bad address Regards -Thorsten -- Williams and Holland's Law: If enough data is collected, anything may be proven by statistical methods. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng regression: cdcontrol close not working
On Sun, 14 Sep 2003, Pav Lucistnik wrote:
V so, 06. 09. 2003 v 21:41, Bruce Evans pí¹e:
On Sat, 6 Sep 2003, Pav Lucistnik wrote:
after recent ATAng changes, cdcontrol close stopped working
with my CD-ROM drive. It used to close the tray. It works with -f
/dev/cd0 but not with /dev/acd0. cdcontrol eject still works fine.
I use the following fix:
%%%
Index: atapi-cd.c
===
RCS file: /home/ncvs/src/sys/dev/ata/atapi-cd.c,v
retrieving revision 1.142
diff -u -2 -r1.142 atapi-cd.c
--- atapi-cd.c 5 Sep 2003 10:40:16 - 1.142
+++ atapi-cd.c 6 Sep 2003 17:16:16 -
@@ -1870,7 +1913,7 @@
int error;
-if ((error = acd_start_stop(cdp, 0)) == EBUSY) {
+if ((error = acd_start_stop(cdp, 0)) == EBUSY || close) {
if (!close)
- return 0;
+ return EBUSY;
if ((error = acd_start_stop(cdp, 3)))
return error;
@@ -1882,6 +1925,4 @@
if (error)
return error;
-if (close)
- return 0;
acd_prevent_allow(cdp, 0);
cdp-flags = ~F_LOCKED;
%%%
acd_eject() doesn't seem to have been changed by ATAng, so I don't see how
close it could have ever worked, but I seem to remember it working.
This patch works for me. Any chance to get it committed?
Up to the maintainer :-).
Bruce
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mdmfs: newfs exited with error code 36
I can confirm this on i386, and sparc also. This is a semi-anoying hickup for those who wish to make tiny root-msf images for a soekris boards, or nfs diskless, and/or mfs-root floppies, etc. I belive PHK is/was looking for the root cause of this, which was a thread that had something to do with bsdlabel's, or not. Anyways, here was that thread: http://lists.freebsd.org/pipermail/freebsd-current/2003-September/009979.html __ __ _ | \/ | __ _ ___| |_ __ _ | |\/| |/ _` / __| __/ _` | | | | | (_| \__ \ || (_| | |_| |_|\__,_|___/\__\__,_| [EMAIL PROTECTED] http://wifibsd.org Thorsten Greiner wrote: * Deiter Alexandr Valerievich [EMAIL PROTECTED] [2003-09-14 22:10]: mdmfs: newfs exited with error code 36 This error seems to be generic, I see it on i386 too. I usually mount /tmp with the following entry from fstab: md /tmp mfs rw,-s250m 2 0 This gives the newfs error mentioned above. Doing the steps by hand I get: # mdconfig -a -t swap -s 256m md4 # newfs /dev/md4 /dev/md4: 256.0MB (524288 sectors) block size 16384, fragment size 4096 using 4 cylinder groups of 64.02MB, 4097 blks, 4160 inodes. super-block backups (for fsck -b #) at: 160, 131264, 262368, 393472 newfs: wtfs: 4096 bytes at sector 192: Bad address Regards -Thorsten ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[current tinderbox] failure on i386/pc98
TB --- 2003-09-14 20:08:26 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-09-14 20:08:26 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-09-14 20:11:56 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: populating /home/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/i386/usr/include stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything.. TB --- 2003-09-14 21:08:37 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Sun Sep 14 21:08:37 GMT 2003 [...] cc -O -pipe -mcpu=pentiumpro -DPC98 -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -finline-limit=15000 -fno-common -g -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_bus_pci.c cc -O -pipe -mcpu=pentiumpro -DPC98 -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -finline-limit=15000 -fno-common -g -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_bus_pccard.c /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_bus_pccard.c: In function `uart_pccard_probe': /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_bus_pccard.c:102: warning: implicit declaration of function `SET_FLAG' /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_bus_pccard.c:102: warning: implicit declaration of function `SET_IFTYPE' /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_bus_pccard.c:102: error: `COM_IF_MODEM_CARD' undeclared (first use in this function) /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_bus_pccard.c:102: error: (Each undeclared identifier is reported only once /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_bus_pccard.c:102: error: for each function it appears in.) *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/modules/uart. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/modules. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/GENERIC. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. TB --- 2003-09-14 21:17:29 - /usr/bin/make returned exit code 1 TB --- 2003-09-14 21:17:29 - ERROR: failed to build generic kernel TB --- 2003-09-14 21:17:29 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devd/devctl
In message: [EMAIL PROTECTED] Brandon S. Allbery KF8NH [EMAIL PROTECTED] writes: : On Sat, 2003-09-13 at 18:49, M. Warner Losh wrote: : and you cannot tell dhclient that interfaces have arrived. : : dhclient(8) seems to think otherwise, although it doesn't explain quite : how (I assume it wants you to pause and resume via OMAPI/omshell(8) : since it doesn't appear to support interface objects according to the : documentation). dhclient(8) is wrong. dhclient can't do it in a meaningful way. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng regression: cdcontrol close not working
It seems Pav Lucistnik wrote: This patch works for me. Any chance to get it committed? I'll look at it... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
-current troubles on Dell Latitude C600
I am having troubles installing -current from JSNAP -current iso images on my Dell Latitude C600 laptop. Everything is ok when / has not been set on softupdates, but when softupdates is activated on / (and / is the only partition besides swap) I get an error during extraction of base. kernel: type 12 trap, code=0 Stopped at vm_page_set_invalid+0x90: incl 0x5c(%eax) That traces to: vm_page_set_invalid(c0fc9a70,0,1000,54a,0) at vm_page_set_invalid+0x90 brelse(c78a4f40,c0fc00e0,c0fc00e0,c2ca9280,c78a4bd0) at brelse+0x56b softdep_disk_io_initiation(c78a4bd0,d213fba8,246,c053e430,c0fc00e0) at softdep_disk_io_initiation+0xc4 spec_xstrategy(c2c7e490,c78a4bd0,c053e430,d213fbd0,c78a4bd0) at spec_xstrategy+0x114 spec_specstrategy(d213fbe0,,c0fc00e0,4,c78a4bd0) at spec_specstrategy+0x72 ufs_strategy(d213fc24,d213fc5c,c037bf57,d213fc24,1) at ufs_strategy+0x110 ufs_vnoperate(d213fc24,1,c053e430,35a,c032b300) at ufs_vnoperate+0x18 bwrite(c78a4bd0,0,c053e430,694,2863c0) at bwrite+0x427 vfs_bio_awrite(c78a4bd0,0,c053e430,884,c2a18130) at vfs_bio_awrite+0x241 flushbufqueues(0,0,c053e430,10e,64) at flushbufqueues+0x22c buf_daemon(0,d213fd48,c053640c,314,0) at buf_daemon+0xdc fork_exit(c037e630,0,d213fd48) at fork_exit+0xcf fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd213fd7c, ebp = 0 --- Any ideas? With softupdates disabled everything works. I have tried the last 3 isos on JSNAP of -current and every one of them fails when softupdates is enabled. Olev ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
mdmfs failing.
With today's cvsup, I cannot create a md based /tmp. If I run 'mount_mfs -s 512m md /tmp' (what runs from the entry in fstab), it says: mount_mfs: newfs exited with error code 36 if I separate the operations, mdconfig runs fine, but newfs says: /dev/md0: 512.0MB (1048576 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 128.02MB, 8193 blks, 16448 inodes. newfs: wtfs: 65536 bytes at sector 160: Bad address What's up? Dave. -- |David Gilbert, Independent Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sat, Sep 13, 2003 at 03:37:51PM +0100, Stuart Walsh wrote: On Fri, Sep 12, 2003 at 09:55:54PM -0400, Jung-uk Kim wrote: I have my own *working* driver, which is for 4-STABLE. It works with SK-9521 V2.0 (for me, at least) and it should work with 3C940. Note: This driver is ported from Nathan L. Binkert's OpenBSD driver. Note: This is completely independent from Stuart Walsh's work. ;-) Note: You must recompile MII driver and dependent network drivers. It's worth noting my patch was a port of Natan's patch also(which is actually Bill's driver technically speaking ;), so I'd be interested to see where i went wrong. But if it works then great, I'll get on with something else :) It's somewhat difficult to fine tune a driver when you dont actually own the hardware in question. I just tried Jung-uk Kim's driver on -stable and sofar it works OK: pcib2: Intel 82801BA/BAM (ICH2) Hub to PCI bridge at device 30.0 on pci0 pci2: PCI bus on pcib2 skc0: 3Com 3C940 Gigabit Ethernet port 0xd400-0xd4ff mem 0xfeaf8000-0xfeafbfff irq 11 at device 5.0 on pci2 skc0: 3Com Gigabit LOM (3C940) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:0c:6e:4f:77:0c miibus0: MII bus on sk0 e1000phy0: Marvell Semiconductor 88E1000* gigabit PHY on miibus0 e1000phy0: 1000baseTX-FDX, 100baseTX-FDX, 100baseTX, 10baseTX-FDX, 10baseTX, auto isp0: Qlogic ISP 1020/1040 PCI SCSI Adapter port 0xd800-0xd8ff mem 0xfeaff000-0xfeaf irq 10 at device 9.0 on pci2 This is with the LOM found on Asus P4P800 btw. Curious minds obviously wonder about the difference with Stuart's driver ;) ENOTIME to check right now. Sleep first. Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Bug in make release regarding install.cfg
Folks, I've noted that the following inconsistency exists in make release. If there is a install.cfg file in /usr/src/release when executing make release (the file which if exists is placed into the root of mfs and customises behaviour of sysinstall), /usr/src/release/install.cfg takes precedence over the same file in CVS from which release is being built and is placed onto the floppy instead of file with the same name in CVS. Appatently this breaks clean room principle of make release and needs to be fixed. Regards, Maxim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
rsh commands to 5.1-CURRENT being rejected
Sep 14 17:46:52 local7.notice target logger: TCP_Wrappers ALLOW: source/target,rshd,974,[EMAIL PROTECTED] Sep 14 17:46:52 auth.info target inetd[974]: connection from source, service rshd (tcp) Sep 14 17:46:52 auth.info target rshd[974]: [EMAIL PROTECTED] as root: permission denied (authentication error). cmd='date' /root/.rhosts (600): source root /etc/pam.d/rsh: not changed /etc/inetd.conf: shell stream tcp nowait root /usr/libexec/rshd rshd -L /etc/hosts: both source and target are defined /etc/named/s/: both source and target are defined 5.1-CURRENT: Wednesday, 20 August 2003 20:36:05 Under FBSD-4.8, this is not a problem. Under FBSD-5.1, nothing I do seems to allow rsh from another LAN host. A TCPDUMP of the rsh session shows root.root.command coming from source and then permission denied coming from target, where the TCPDUMP is running. The source host displays: rshd: Login incorrect.. RSH from target to source works just fine?!? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsh commands to 5.1-CURRENT being rejected
On Sunday, September 14, 2003, at 07:29 PM, [EMAIL PROTECTED] wrote: Sep 14 17:46:52 local7.notice target logger: TCP_Wrappers ALLOW: source/target,rshd,974,[EMAIL PROTECTED] Sep 14 17:46:52 auth.info target inetd[974]: connection from source, service rshd (tcp) Sep 14 17:46:52 auth.info target rshd[974]: [EMAIL PROTECTED] as root: permission denied (authentication error). cmd='date' What happens if you type in rsh target ? Does that then give you a shell ? -DR ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsh commands to 5.1-CURRENT being rejected
Yes - rsh target, after enabling login/rlogind ;), gives me a shell on target. Even after enabling login/rlogind, rsh target command still fails as outlined below. On 14 Sep, David Rhodus wrote: On Sunday, September 14, 2003, at 07:29 PM, [EMAIL PROTECTED] wrote: Sep 14 17:46:52 local7.notice target logger: TCP_Wrappers ALLOW: source/target,rshd,974,[EMAIL PROTECTED] Sep 14 17:46:52 auth.info target inetd[974]: connection from source, service rshd (tcp) Sep 14 17:46:52 auth.info target rshd[974]: [EMAIL PROTECTED] as root: permission denied (authentication error). cmd='date' What happens if you type in rsh target ? Does that then give you a shell ? -DR ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsh commands to 5.1-CURRENT being rejected
In message [EMAIL PROTECTED], [EMAIL PROTECTED] writes: Sep 14 17:46:52 local7.notice target logger: TCP_Wrappers ALLOW: source/tar get,rshd,974,[EMAIL PROTECTED] Sep 14 17:46:52 auth.info target inetd[974]: connection from source, servic e rshd (tcp) Sep 14 17:46:52 auth.info target rshd[974]: [EMAIL PROTECTED] as root: permission denied (authentication error). cmd='date' /root/.rhosts (600): source root /etc/pam.d/rsh: not changed /etc/inetd.conf: shell stream tcp nowait root /usr/libexec/rshd rshd -L /etc/hosts: both source and target are defined /etc/named/s/: both source and target are defined 5.1-CURRENT: Wednesday, 20 August 2003 20:36:05 Under FBSD-4.8, this is not a problem. Under FBSD-5.1, nothing I do seems to allow rsh from another LAN host. A TCPDUMP of the rsh session shows root.root.command coming from source and then permission denied coming from target, where the TCPDUMP is running. The source host displays: rshd: Login incorrect.. RSH from target to source works just fine?!? A picture is worth a thousand words. (No worries folks, this is in my internal network here at home. Professionally I use SSH and Kerberos rsh.) --- /usr/src/etc/pam.d/rsh Sun Feb 9 16:50:03 2003 +++ /etc/pam.d/rsh Mon Jun 16 15:20:00 2003 @@ -6,7 +6,7 @@ # auth auth requiredpam_nologin.so no_warn -auth requiredpam_rhosts.so no_warn +auth requiredpam_rhosts.so no_warn allow_root # account accountrequiredpam_unix.so Cheers, -- Cy Schubert [EMAIL PROTECTED]http://www.komquats.com/ BC Government . FreeBSD UNIX [EMAIL PROTECTED] . [EMAIL PROTECTED] http://www.gov.bc.ca/ .http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mysql-client compiler error
I get the same problem in the same place with current as of today. Cheers, Mark On Sat, 2003-09-13 at 20:37, Matt wrote: After building world as of late last night I decided to portupgrade -rRaf, mainly due to having the libintl.so.4 missing problem when I tried to start X. Everything compiled perfectly fine (and X is now working fine) except for databases/mysql40-client. I get this error: checking for C compiler default output... configure: error: C compiler cannot create executables configure: error: could not configure Berkeley DB I just wish to know is this something wrong with my system in general or is this just due to the -pthread discussions that have been occuring and that this port is one example of those that no longer works on -current? It is not a problem as I have the previously compiled/installed version still on the system but I just wish to confirm if the problem is likely to be down to the pthreads changes, and if I should report it to the port maintainer etc? Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mark Sergeant [EMAIL PROTECTED] SNSOnline Technical Services ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mystery kernel spew
On Sun, 14 Sep 2003, masta wrote: I owe you a beer Doug (or a soda-pop)! ;) hehe :) You were correct about the sysctl.conf being the root-cause of the kernel spew. Mike Smith ran into it one day and we spent some time debugging it. Someone made the observation that they were sysctl items and not function calls and that tipped us off. 'sysctl sysctl' is a magic incantation to dump the sysctl tree. There's a couple of other magic words. #security.bsd.see_other_uids=0 sysctl net.inet.tcp.blackhole=1 sysctl net.inet.udp.blackhole=1 Heh, you even had an example :) Incidentally, if you are getting wrapping even without this, you can use a serial console to capture the output. I've had to do this for doing nasty ACPI debugging with lots of the options enabled. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
