Re: ATAng still problematic
On Fri, Sep 19, 2003 at 08:02:31AM +0200, Soren Schmidt wrote: It seems Jan Srzednicki wrote: As far as problems with dagrab and cdda2wav are conserned - this is because of removal of CDIOCREADAUDIO ioctl in ATAng (see recent thread What's happened to CDIOCREADAUDIO friends) I've seen it (after posting the original mail, though;). Is there going to be any audio reading utility avalaible? When atapicam is broken, I can still use burncd and it works fine. But I don't have any tool to read audio. dd if=/dev/acdXtY of=trackY bs=2352 Cool. ;) Could you give me a hint what to put in devd.conf to get acdXtY files created automatically when a CD is inserted? -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ATAng still problematic
Hello there, I still have problems with ATAng, with kernel from 15th of September. First of all, the drive still does not get detected properly. Funny thing is that after some playing with atacontrol attach/detach, it finally gets detected. And later on, it is normally detected, before. Same scenario happened like 3 times with ATAng and newer and newer kernels. I don't know whether some device hints or anything are just updated; yet, I didn't have _any_ drive detection problems with ATAold. The problem is with the second drive. There's still some randomness in it, as it gets undetected from time to time. Another thing is with atapicam. First of all, I am not able to do any CD audio ripping, getting the following: [15:29] stronghold:/usr/tmp(569)# dagrab -d /dev/acd1 -a dagrab: error retrieving cddb data Dumping all tracks Dumping track 1: lba 0 to lba 42800 (needs 96 MB) Output file is: track01.wav dagrab: read raw ioctl failed at lba 0 length 12: Inappropriate ioctl for device I get the same error with cdda2wav. I've recompiled them both after upgrading, to no avail. The second thing is that I get a panic when trying to burn a CD with atapicam mode. panic: vm_fault_copy_wired: page missing I have recent cdrtools, recompiled after system upgrade. I will try to debug that with a freshly cvsupped kernel. I have my dmesg attached. -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- 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 #11: Tue Sep 16 00:53:17 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MOONDANCE Preloaded elf kernel /boot/kernel/kernel at 0xc04db000. Preloaded elf module /boot/kernel/if_rl.ko at 0xc04db1f4. Preloaded elf module /boot/kernel/miibus.ko at 0xc04db2a0. Preloaded elf module /boot/kernel/snd_via82c686.ko at 0xc04db34c. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc04db400. Preloaded elf module /boot/kernel/mga.ko at 0xc04db4ac. Preloaded elf module /boot/kernel/acpi.ko at 0xc04db554. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Duron(tm) Processor (600.03-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x630 Stepping = 0 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! real memory = 536805376 (511 MB) avail memory = 515842048 (491 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: VIA694 AWRDACPI on motherboard pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00fdd00 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 0x4008-0x400b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0x6000-0x607f,0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 7 INTC is routed to irq 11 pcib0: slot 9 INTA is routed to irq 5 pcib0: slot 10 INTA is routed to irq 11 agp0: VIA 82C8363 (Apollo KT133A) host to PCI bridge mem 0xd500-0xd5ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pcib0: slot 1 INTA is routed to irq 10 pcib1: slot 0 INTA is routed to irq 10 drm0: Matrox G400/G450 (AGP) mem 0xd300-0xd37f,0xd200-0xd2003fff,0xd000-0xd1ff irq 10 at device 0.0 on pci1 info: [drm] AGP at 0xd500 16MB info: [drm] Initialized mga 3.1.0 20021029 on minor 0 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686A UDMA66 controller port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pcm0: VIA VT82C686A port 0xe400-0xe403,0xe000-0xe003,0xdc00-0xdcff irq 11 at device 7.5 on pci0 pcm0: ICEnsemble ICE1232 AC97 Codec pci0: multimedia, audio at device 9.0 (no driver attached) rl0: RealTek 8139 10/100BaseTX port 0xec00-0xecff mem 0xd600-0xd6ff irq 11 at device 10.0 on pci0 rl0: Ethernet address: 00:e0:7d:b4:33:16 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at
static ldt allocation
Hello, I'm getting the following warning when running xmms with libthr: Warning: pid 589 used static ldt allocation. See the i386_set_ldt man page for more info When I use libkse, I don't get this warning. As I understand, someone's is hunting down static LDT usage, so here's my feedback. ;) -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng still problematic
On Thu, Sep 18, 2003 at 03:54:36PM +0200, Soren Schmidt wrote: It seems Jan Srzednicki wrote: First of all, the drive still does not get detected properly. Funny thing is that after some playing with atacontrol attach/detach, it finally gets detected. And later on, it is normally detected, before. Same scenario happened like 3 times with ATAng and newer and newer kernels. I don't know whether some device hints or anything are just updated; yet, I didn't have _any_ drive detection problems with ATAold. The problem is with the second drive. There's still some randomness in it, as it gets undetected from time to time. Try the below patch and let me know if that changes anything.. It seems that things have changed a bit (the drive gets detected more often), but still, it's not perfect. Anyway, here's backtrace for atapicam panic I've mentioned. It's triggered by: cdrecord dev=1,1,0 /some/track greetings, -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- Script started on Thu Sep 18 17:43:10 2003 [m[27m[24m[J[17:43] stronghold:/usr/tmp/crash(608)# [Kggdb -k kernel.debug0 .0 vmcore.0 GNU gdb 5.2.1 (FreeBSD) Copyright 2002 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-undermydesk-freebsd... panic: vm_fault_copy_wired: page missing panic messages: --- panic: vm_fault_copy_wired: page missing syncing disks, buffers remaining... 3428 3428 3426 3426 3426 3426 3426 3426 3426 3426 3426 3426 3426 3426 3426 3426 3426 3426 3426 3426 3426 3426 giving up on 2440 buffers Uptime: 4m54s Dumping 511 MB [CTRL-C to abort] [CTRL-C to abort] 16 32 48 64 80 96 112 128 144 160 176 192 208 224[CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] 240 256 272 288 304 320 336 352 368 384 400 416 432 448Copyright (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 #12: Thu Sep 18 16:36:35 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MOONDANCE Preloaded elf kernel /boot/kernel/kernel at 0xc04e7000. Preloaded elf module /boot/kernel/if_rl.ko at 0xc04e71f4. Preloaded elf module /boot/kernel/miibus.ko at 0xc04e72a0. Preloaded elf module /boot/kernel/snd_via82c686.ko at 0xc04e734c. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc04e7400. Preloaded elf module /boot/kernel/mga.ko at 0xc04e74ac. Preloaded elf module /boot/kernel/acpi.ko at 0xc04e7554. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Duron(tm) Processor (600.03-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x630 Stepping = 0 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! real memory = 536805376 (511 MB) avail memory = 515792896 (491 MB) Pentium Pro MTRR support enabled npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: VIA694 AWRDACPI on motherboard pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00fdd00 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 0x4008-0x400b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0x6000-0x607f,0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 7 INTC is routed to irq 11 pcib0: slot 9 INTA is routed to irq 5 pcib0: slot 10 INTA is routed to irq 11 agp0: VIA 82C8363 (Apollo KT133A) host to PCI bridge mem 0xd500-0xd5ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pcib0: slot 1 INTA is routed to irq 10 pcib1: slot 0 INTA is routed to irq 10 drm0: Matrox G400/G450 (AGP) mem 0xd300-0xd37f,0xd200-0xd2003fff,0xd000-0xd1ff irq 10 at device 0.0 on pci1 info: [drm] AGP at 0xd500 16MB info: [drm] Initialized mga 3.1.0 20021029 on minor 0 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686A UDMA66 controller port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pcm0: VIA VT82C686A port 0xe400-0xe403,0xe000-0xe003,0xdc00-0xdcff irq 11 at device 7.5 on pci0 pcm0: ICEnsemble ICE1232 AC97 Codec pci0: multimedia, audio at device 9.0 (no driver attached) rl0: RealTek 8139 10/100BaseTX
Re: ATAng still problematic
On Thu, Sep 18, 2003 at 11:46:35AM -0500, Steve Ames wrote: On Thu, Sep 18, 2003 at 06:38:25PM +0200, Soren Schmidt wrote: Anyhow, what I need to be able to tell what may be going on, is that you boot verbose and get me the output from dmesg from a boot that found all device, and from a boot that missed. Anyone know how to make the message buffer larger? I don't have a serial console hooked up currently and a boot verbose is way over the 32K default buffer size so only get the last 32K once the system is booted up. How about /var/run/dmesg.boot? ;) -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng still problematic
On Fri, Sep 19, 2003 at 01:32:45AM +0300, Vladimir Kushnir wrote: Um. Do you see the same crash if both drives contain CDs at boot time? If not, this could be a consequence of the error condition corruption problem others have been reporting. Thomas. These crashes started before ATAng commit, some time between 10 and 15 August, and with precisely the same symptoms. I wasn't following -CURRENT that time, I can't confirm it. As far as problems with dagrab and cdda2wav are conserned - this is because of removal of CDIOCREADAUDIO ioctl in ATAng (see recent thread What's happened to CDIOCREADAUDIO friends) I've seen it (after posting the original mail, though;). Is there going to be any audio reading utility avalaible? When atapicam is broken, I can still use burncd and it works fine. But I don't have any tool to read audio. -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng probe updated please test
On Mon, Sep 01, 2003 at 01:16:00PM +0200, Soren Schmidt wrote: I've gone over the probe code once again. Please test, and in case it fails to detect or misdetects anything, mail me the output of dmesg from a verbose boot, and state what devices actually are there. Hello, The new stuff still failed to detect properly my hardware. Whole dmesg is attached. But, mysteriously, after two reboots the problem vanished, and I can see my HW as I should: GEOM: create disk ad0 dp=0xc409ee70 ad0: 19546MB FUJITSU MPF3204AT [39714/16/63] at ata0-master UDMA66 GEOM: create disk ad1 dp=0xc409ed70 ad1: 39093MB FUJITSU MPG3409AH EF [79428/16/63] at ata0-slave UDMA66 acd0: CDROM CD-540E at ata1-master UDMA33 acd1: CDRW CD-W540E at ata1-slave UDMA33 cd0 at ata1 bus 0 target 0 lun 0 cd0: TEAC CD-540E 1.0A Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [348277 x 2048 byte records] cd1 at ata1 bus 0 target 1 lun 0 cd1: TEAC CD-W540E 1.0C Removable CD-ROM SCSI-0 device cd1: 33.000MB/s transfers cd1: cd present [1 x 0 byte records] (this funny phantom CD inside of my drives is still there ;) I don't have any idea why this thing was not working in the begining. I did not touch anything, I swear. ;) Anyway, On the new kernel, reboot (after waiting for all the fsck's to finish) resulted in panic when syncer was called to flush everything. This has happened only once, I cannot reproduce it, yet the syncer problem (giving up on 1 buffer) persist. It is not a problem with the aio module, as I have removed it, and it still happens. Willing to provide more feedback, if I knew how.. greets, -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- 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 #8: Tue Sep 2 00:08:11 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MOONDANCE Preloaded elf kernel /boot/kernel/kernel at 0xc0546000. Preloaded elf module /boot/kernel/mga.ko at 0xc0546200. Preloaded elf module /boot/kernel/aio.ko at 0xc05462a8. Preloaded elf module /boot/kernel/acpi.ko at 0xc0546350. Calibrating clock(s) ... i8254 clock: 1193155 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 600025865 Hz CPU: AMD Duron(tm) Processor (600.03-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x630 Stepping = 0 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! Data TLB: 24 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 1 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 536805376 (511 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0056d000 - 0x1f6c9fff, 521523200 bytes (127325 pages) avail memory = 515391488 (491 MB) bios32: Found BIOS32 Service Directory header at 0xc00faee0 bios32: Entry = 0xfb350 (c00fb350) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xb380 pnpbios: Found PnP BIOS data at 0xc00fbe50 pnpbios: Entry = f:be80 Rev = 1.0 Other BIOS signatures found: null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: VIA694 AWRDACPI on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=03051106) pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00fdd00 PCI-Only Interrupts: 5 10 11 Location Bus Device Pin Link IRQs slot 1 08A 0x01 3 4 5 7 9 10 11 12 14 15 slot 1 08B 0x02 3 4 5 7 9 10 11 12 14 15 slot 1 08C 0x03 3 4 5 7 9 10 11 12 14 15 slot 1 08D 0x05 3 4 5 7 9 10 11 12 14 15 slot 2 09A 0x02 3 4 5 7 9 10 11 12 14 15 slot 2 09B 0x03 3 4 5 7 9 10 11 12 14 15 slot 2 09C 0x05 3 4 5 7 9 10 11 12 14 15 slot 2 09D 0x01 3 4 5 7 9 10 11 12 14 15 slot 3 0 10A 0x03 3 4 5 7 9 10 11 12 14 15 slot 3 0 10B 0x05 3 4 5 7 9 10 11 12 14 15 slot 3 0 10C 0x01 3 4 5 7 9 10 11 12 14 15 slot 3 0 10D 0x02 3 4 5 7 9 10 11 12 14 15 slot 4 0 11A 0x05 3 4 5 7 9 10 11 12 14 15 slot 4 0 11B 0x01 3 4 5 7
Re: Syncer giving up on buffers
On Mon, Sep 01, 2003 at 07:53:48PM +0300, Lefteris Chatzibarbas wrote: Hello, I have a problem with kernels, built the last couple of days, where during shutdown syncer is giving up on buffers. During the next boot all filesystems are checked because of improper dismount. Here follow the exact messages I get: Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks, buffers remaining... 8 8 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 giving up on 6 buffers Uptime: 41m20s pfs_vncache_unload(): 1 entries remaining Shutting down ACPI Rebooting... After some testing I found out that this does _not_ happen if I manually unmount my ext2 filesystems, before shutting down. In this case syncer finishes without any problems. I confirm that, same thing happened in my case. But, I had just one buffer remaining and ext2fs mounted in read-only. It seems that it's not so read-only then.. -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng probe updated please test
On Tue, Sep 02, 2003 at 10:23:02AM +0200, Jan Srzednicki wrote: I've gone over the probe code once again. Please test, and in case it fails to detect or misdetects anything, mail me the output of dmesg from a verbose boot, and state what devices actually are there. Hello, The new stuff still failed to detect properly my hardware. Whole dmesg is attached. But, mysteriously, after two reboots the problem vanished, and I can see my HW as I should: OK, the drive did not get detected once again. This seems to be pretty random. Anyway, On the new kernel, reboot (after waiting for all the fsck's to finish) resulted in panic when syncer was called to flush everything. This has happened only once, I cannot reproduce it, yet the syncer problem (giving up on 1 buffer) persist. It is not a problem with the aio module, as I have removed it, and it still happens. Willing to provide more feedback, if I knew how.. I've found this thing is related to ext2fs, as I stated in different thread. -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng not detecting drives
On Sun, Aug 31, 2003 at 04:57:57PM +0200, Soren Schmidt wrote: It seems Jan Srzednicki wrote: ad0: 19546MB FUJITSU MPF3204AT [39714/16/63] at ata0-master UDMA66 ad1: 39093MB FUJITSU MPG3409AH EF [79428/16/63] at ata0-slave UDMA66 ata1-slave: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED acd0: CDROM CD-540E at ata1-master UDMA33 cd0 at ata1 bus 0 target 0 lun 0 cd0: TEAC CD-540E 1.0A Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [2154583490 x 838860800 byte records] Mounting root from ufs:/dev/ad0s2a (it's this ata1-slave thing). Previously, it has been seen as: acd1: CD-RW CD-W540E at ata1-slave UDMA33 Ok, I've finally managed to get a setup that exhibits this problem, expect a fix soon... Anyway, the syncer problem (giving up on just one buffer) appeared again, this time without any heavy disk loads. I'm sure it hasn't been happening before the upgrade, yet I have no idea how can I provide more feedback about it. -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ATAng not detecting drives
Hello sir, I've just cvsupped the new -C source, and installed a new kernel. My CD-RW could not be detected: FreeBSD 5.1-CURRENT #7: Sun Aug 31 12:21:57 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MOONDANCE Preloaded elf kernel /boot/kernel/kernel at 0xc0545000. Preloaded elf module /boot/kernel/mga.ko at 0xc05451f4. Preloaded elf module /boot/kernel/aio.ko at 0xc054529c. Preloaded elf module /boot/kernel/acpi.ko at 0xc0545344. Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Duron(tm) Processor (600.03-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x630 Stepping = 0 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! real memory = 536805376 (511 MB) avail memory = 515395584 (491 MB) Pentium Pro MTRR support enabled [..] atapci0: VIA 82C686A UDMA66 controller port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 [..] ad0: 19546MB FUJITSU MPF3204AT [39714/16/63] at ata0-master UDMA66 ad1: 39093MB FUJITSU MPG3409AH EF [79428/16/63] at ata0-slave UDMA66 ata1-slave: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED acd0: CDROM CD-540E at ata1-master UDMA33 cd0 at ata1 bus 0 target 0 lun 0 cd0: TEAC CD-540E 1.0A Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [2154583490 x 838860800 byte records] Mounting root from ufs:/dev/ad0s2a (it's this ata1-slave thing). Previously, it has been seen as: acd1: CD-RW CD-W540E at ata1-slave UDMA33 And everything worked fine, Teacs run in DMA mode without any problems. Another weird thing is that the first drive in atapicam mode (accessed as /dev/cd0, not /dev/acd0) reports something inside of it, while there's no CD inside (as you can see it in dmesg). After atacontrol detach/attach, I've got the thing flip-flopped: acd0: WARNING - removed from configuration (cd0:ata1:0:0:0): lost device (cd0:ata1:0:0:0): removing device entry ata1-master: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR error=4ABORTED acd0: CDRW CD-W540E at ata1-slave UDMA33 cd0 at ata1 bus 0 target 1 lun 0 cd0: TEAC CD-W540E 1.0C Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [879076549 x 1006698496 byte records] (the second drive is also empty) After some playing with atacontrol, it appears that it's rather random which drive gets detected. But I could not get them both working at one time, it always detected just one. Anyway, after some massive disk IO (installworld mergemaster) and reboot, syncer decided to give up on one buffer. No idea, whether this is ATAng feature, yet it hasn't been happening on ATAold. greets, -- -- wrzask --= v =-- Winfried --===-- GG# 3838383 --- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: background fsck did not create lost+found
On Mon, 20 Jan 2003, David Schultz wrote: First two entries clearly correspond to the missing file, which should have been put in /home/lost+found. But, the poroblem is that no lost+found directory was created, while it should (as fsck_ffs(8) says). I guess its a bug, probably in the background fsck code. Still, is there any way to reclaim the file now, besides running strings(1) on the whole partition? Consider what happens when you remove a large directory tree. Thousands of directory entries may be removed, but in the softupdates case, the inodes will stick around a bit longer. The same also applies to files that have been intentionally unlinked but are still open. To avoid a syndrome where all these thousands of files end up in lost+found after a crash or power failure, fsck just removes them on softupdates-enabled filesystems. Would that be a big problem to allow some fsck option not to erase all these softupdates-pending inodes, but to put them in lost+found as usual? The default behaviour is unchanged, yet there is a way to reclaim lost files. -- -- wrzask --= v =-- Winfried --=-- GG# 3838383 --=-- JS500-RIPE -- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: background fsck did not create lost+found
On Wed, 22 Jan 2003, Garrett Wollman wrote: Would that be a big problem to allow some fsck option not to erase all these softupdates-pending inodes, but to put them in lost+found as usual? It certainly couldn't be done with the background fsck, because background fsck works on a snapshot and not the running filesystem; thus, it cannot make any allocations -- it can only deallocate things. Still, in case you know some of your important files can be lost, you can boot the system to single user and run foreground fsck. -- -- wrzask --= v =-- Winfried --=-- GG# 3838383 --=-- JS500-RIPE -- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
background fsck did not create lost+found
Hello, After building new world and installing new kernel, I rebooted my machine to launch a new kernel. The system mysteriously failed to flush 22 disk buffers, and after reboot fsck was launched. I have the following partitions: / - UFS1 /usr - UFS2 /home - UFS1 This massive disk mangling occured on /usr, but still, one file in /home got lost - which happened to be quite important file. Background fsck logged: Jan 20 16:06:30 stronghold root: /dev/ad1s1d: UNREF FILE I=1723065 OWNER=winfried MODE=100644 Jan 20 16:06:30 stronghold root: /dev/ad1s1d: SIZE=23397 MTIME=Jan 20 15:57 2003 (CLEARED) Jan 20 16:06:30 stronghold root: /dev/ad1s1d: Reclaimed: 0 directories, 8 files, 16439 fragments Jan 20 16:06:30 stronghold root: /dev/ad1s1d: 33802 files, 13109700 used, 6310697 free (11577 frags, 787390 blocks, 0.1% fragmentation) First two entries clearly correspond to the missing file, which should have been put in /home/lost+found. But, the poroblem is that no lost+found directory was created, while it should (as fsck_ffs(8) says). I guess its a bug, probably in the background fsck code. Still, is there any way to reclaim the file now, besides running strings(1) on the whole partition? -- -- wrzask --= v =-- Winfried --=-- GG# 3838383 --=-- JS500-RIPE -- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump(8) + UFS2
On Sat, 30 Nov 2002, Manfred Antar wrote: I guess dump is not ready for UFS2 I just have made dump and restore of my 3GB UFS2 /usr partition and did not experience any problems with that. Working on -CURRENT from Nov 24th. -- -- wrzask --= v =-- Winfried --=-- GG# 3838383 --=-- JS500-RIPE -- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump(8) + UFS2
On Sat, 30 Nov 2002, Matthias Schuendehuette wrote: I just have made dump and restore of my 3GB UFS2 /usr partition and did not experience any problems with that. Working on -CURRENT from Nov 24th. Sure you dumped an UFS2 filesystem? Here's my try: root@current - /root 104 # uname -a FreeBSD current.best-eng.de 5.0-CURRENT FreeBSD 5.0-CURRENT #3: Thu Nov 28 21:59:11 CET 2002 [EMAIL PROTECTED]:/disk/obj/usr/src/sys/CURRENT i386 Hm, this is weird. I'm sure I have dumped an UFS2 filesystem earlier and it worked. Now I get similar error messages as you. Yes, I'm absolutely sure that the filesystem was UFS2 - played with extattrctl on it, checked it with dumpfs and was not able to mount it under -STABLE. dump utility is exacly the same (except that it now resides on a different disk). The filesystem after restore does not seem to be corrupted in any way (well, except that linux-*-jdk-* stuff SEGVs - kinda weird). This thing gets spooky a bit.. ;) Both my disks are IDEs, if that matters in any way. -- -- wrzask --= v =-- Winfried --=-- GG# 3838383 --=-- JS500-RIPE -- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump(8) + UFS2
On Sun, 1 Dec 2002, Jan Srzednicki wrote: Hm, this is weird. I'm sure I have dumped an UFS2 filesystem earlier and it worked. Now I get similar error messages as you. Yes, I'm absolutely sure that the filesystem was UFS2 - played with extattrctl on it, checked it with dumpfs and was not able to mount it under -STABLE. dump utility is exacly the same (except that it now resides on a different disk). The filesystem after restore does not seem to be corrupted in any way (well, except that linux-*-jdk-* stuff SEGVs - kinda weird). This thing gets spooky a bit.. ;) Both my disks are IDEs, if that matters in any way. Erm, s/extattrctl/setextattr and getextattr/. -- -- wrzask --= v =-- Winfried --=-- GG# 3838383 --=-- JS500-RIPE -- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
sound problems
Hello there, I have -CURRENT from Saturday on my box. I have SB 128PCI on my board, the module detects it without problems and seems to work fine. But the problem is that the sound is not clear; there happen to be some itchy noises from time to time, when I push up the system load. I wonder whether enlarging the sound buffer woul help, yet hw.snd.pcm0.buffersize is read-only, even setting it in /boot/loader.conf does not help. Under -STABLE those ithes never happened, so I don't think it's a hw issue. Here's my dmesg output, with some irrelevant (IMHO) stuff removed: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #2: Sun Nov 24 23:36:06 CET 2002 root@stronghold:/usr/obj/usr/src/sys/MOONDANCE5 Preloaded elf kernel /boot/kernel/kernel at 0xc04e4000. Preloaded elf module /boot/kernel/mga.ko at 0xc04e4204. Preloaded elf module /boot/kernel/acpi.ko at 0xc04e42ac. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 600026288 Hz CPU: AMD Duron(tm) Processor (600.03-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x630 Stepping = 0 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! real memory = 536805376 (511 MB) avail memory = 515969024 (492 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: VIA694 AWRDACPI on motherboard Using $PIR table, 7 entries at 0xc00fdd00 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0x6000-0x607f,0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 initial configuration [.. here comes the irqs output and stuff ..] pci0: ACPI PCI bus on pcib0 agp0: VIA 82C8363 (Apollo KT133A) host to PCI bridge mem 0xd500-0xd53f at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 drm0: Matrox G400/G450 (AGP) mem 0xd300-0xd37f,0xd200-0xd2003fff,0xd000-0xd1ff irq 10 at device 0.0 on pci1 info: [drm] AGP at 0xd500 4MB info: [drm] Initialized mga 3.0.2 20010321 on minor 0 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686 ATA66 controller port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pcm0: Creative CT5880-C port 0xdc00-0xdc3f irq 5 at device 9.0 on pci0 rl0: RealTek 8139 10/100BaseTX port 0xe000-0xe0ff mem 0xd540-0xd54000ff irq 11 at device 10.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:e0:7d:b4:33:16 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto [.. floppy, serial/parallel ports, keyboard, PS/2 mouse ..] pmtimer0 on isa0 orm0: Option ROM at iomem 0xc-0xc87ff on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 [.. and ATA drives ..] -- -- wrzask --= v =-- Winfried --=-- GG# 3838383 --=-- JS500-RIPE -- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
UFS2 and disklabel fstype
Hello there, As UFS2 is not backward compatible at all, I wonder why the old fstype in disklabel is being kept: #size offsetfstype [fsize bsize bps/cpg] a: 102400004.2BSD 2048 16384 64008 # (Cyl.0 - 63*) c: 186103260unused0 0 # (Cyl.0 - 1158*) d: 17586326 10240004.2BSD 2048 16384 28552 # (Cyl. 63*- 1158*) This is a disklabel of my newly installed -DP2 system. Partition a is formatted as UFS, while d is UFS2. I wonder, is there any reason for not distincting these filesystems on disklabel level? Would specyfying different fstype for UFS2 (whatever you call it then) break something? It's not a real problem, but in some cases may confuse someone. I've done some googling, but didn't find any discussion on this topic, so I'm writing here. -- -- wrzask --= v =-- Winfried --=-- GG# 3838383 --=-- JS500-RIPE -- -- [EMAIL PROTECTED] --- [EMAIL PROTECTED] --===-- http://violent.dream.vg/ --- --= Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! =-- Queen -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
