usb flashkey disk copy error
Hello all, I have a copy error between hdd and a flashkey 1gig usb (easydisk) on Current dated August 28. Here is in short: mount -t msdos /dev/da2s1 /flashkey cp myfile /flashkey/ diff myfile /flashkey/myfile (ok). umount /flashkey mount (flashkey) diff myfile /flashkey/myfile (Binary file differ)! It is not a flashkey disk error, it works on XP. Note that this error occurs on FreeBSD 4.8 too. Please, can you tell me how to deal with that? And in an other hand can you tell me how to obtain the exact map of the flashkey to verify the writing on the disk. Thanks in advance for this newbie question. [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb flashkey disk copy error
raoul.megelas wrote this message on Sun, Sep 07, 2003 at 08:45 +0200: I have a copy error between hdd and a flashkey 1gig usb (easydisk) on Current dated August 28. Here is in short: mount -t msdos /dev/da2s1 /flashkey cp myfile /flashkey/ diff myfile /flashkey/myfile (ok). could you try a fsync /flashkey/myfile before the umount? umount /flashkey mount (flashkey) diff myfile /flashkey/myfile (Binary file differ)! It is not a flashkey disk error, it works on XP. Note that this error occurs on FreeBSD 4.8 too. Please, can you tell me how to deal with that? And in an other hand can you tell me how to obtain the exact map of the flashkey to verify the writing on the disk. Thanks in advance for this newbie question. You're the second person that has reported corruption with USB umass devices. I am interested in tracking down this problem, but it's a bit difficult since I haven't seen it myself. (I currently don't quite have a test bed box to play with, but I will in the next week.) Thanks. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ [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-07 07:43:59 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-09-07 07:43:59 - 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-07 07:46:20 - 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-07 08:41:07 - 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 7 08:41:07 GMT 2003 [...] /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c:271: error: invalid operands to binary /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c: In function `sab82532_bus_getsig': /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c:448: error: invalid operands to binary /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c: In function `sab82532_bus_probe': /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c:555: error: invalid operands to binary /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c: In function `sab82532_bus_setsig': /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c:637: error: invalid operands to binary /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c:639: error: invalid operands to binary *** 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-07 08:49:42 - /usr/bin/make returned exit code 1 TB --- 2003-09-07 08:49:42 - ERROR: failed to build generic kernel TB --- 2003-09-07 08:49:42 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng problems
It seems Christian Laursen wrote: Since ATAng was comitted I've had problems with the disk on which my root filesystem is residing. If I choose 'Safe mode' in the boot menu, it will boot but it is then running with DMA and write caching disabled. This is the dmesg output from a failed boot. If anything else is needed to figure it out, just tell me what to do. I have one other report of problems on the older Acer chips, I must have screwed something up there. I'll dig out my old ASUS board and see what I can find out... Bortset fra det kunne vi da snakke dansk ku' vi ikke ? :) -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
cosmetic bug in newsyslog ?
Hi all, maybe not really proper mailling list, I just cvsuped 4.9 prerelease and funny thing with syslog this is newsyslog.conf /var/log/httpd-referer.log 644 20*$M1D0 BZ /var/run/httpd.pid 30 this is newsyslog -v output /var/log/httpd-referer.log 20Z: -- will trim at Mon Sep 1 00:00:00 2003 and this is date today: Sun Sep 7 11:34:48 EET 2003 If I would believe the output, the log rotation would NEVER hapen :) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [PATCH] /bin/sh buglet
On Sun, Sep 07, 2003 at 04:27:00AM +0300, Enache Adrian wrote:
# $ a=foo
# $ : $((a=15))
# arithmetic expression: variable assignment error: a=15
# $ echo $a
# 15
#
# --- /usr/src/bin/sh/arith.y Thu Sep 4 23:31:14 2003
# +++ ./arith.y Sun Sep 7 01:04:06 2003
# @@ -155,7 +155,7 @@
# } |
# ARITH_VAR ARITH_ASSIGN expr
# {
# - if (arith_assign($1, $3) != 1)
# + if (arith_assign($1, $3) != 0)
# yyerror(variable assignment error);
# $$ = $3;
# } |
Good catch! Commited. Thanks!
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LS120, ATANg and Atapicam
On Sun, 7 Sep 2003, Mark Dixon wrote: I'm not sure if this is a known problem, but I don't see any references to it. I've gone from 5.1-RELEASE to todays CURRENT to try to get rid of a different panic (no news on that yet), but I have hit this one. If I boot my system with no floppy in the LS-120, the system panics where atapicam creates da0 for it. If there is a disk in the drive, it works fine. As yet, I havn't got the details of the panic, but if this is of interest to anyone here, I will be willing to provide them with them (they wil have to be be copied out by hand, so I'm lothe to do it if nobody is interested). I see similar bugs for a 1 ZIP drive 2 CDROM drives. The panic is mostly for division by 0 in cam_calc_geometry(), but sometimes there is division by a garbage value and the error is detected before it causes a panic. Debugging one of the CDROM drives shows that all SCSI commands done as part of cdopen() succeed although there is no disk in the drive! Most of the commands are reads and the reads are apparently null, leaving garbage in the buffers. In particular, the disk geometry is garbage and dividing by a garbage sector size of 0 causes the panic. The SCSI commands get at least as far as ata_completed() (via ata_command() and ata_interrupt() so they apparently get sent to the drive, but no errors are detected. For ATAPI drives, there are no problems unless the drives are explicitly accessed since GEOM doesn't probe them unconditonally. Panics for the ZIP drive are deterministic here since GEOM accesses it unconditionally at boot time when the garbage is more likely to be 0. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with ATAng and cdparanoia
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. My CD drives are: acd0: DVDROM CREATIVEDVD5240E-1 at ata1-master WDMA2 Waiting 2 seconds for SCSI devices to settle cd1 at ata1 bus 0 target 0 lun 0 cd1: CREATIVE DVD5240E-1 1.30 Removable CD-ROM SCSI-0 device cd1: 16.000MB/s transfers cd1: cd present [405416901 x 0 byte records] Mounting root from ufs:/dev/ad0s1a cd0 at sym0 bus 0 target 2 lun 0 cd0: PLEXTOR CD-R PX-R412C 1.07 Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present Best regards, Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.1-RELEASE-p2 panic
For the last couple weeks, I have been getting a daily panic just before
24 hours uptime.
Seems to have started after -p2 patches and rebuild. The system was
solid up until that point. I know I have seen others complain about
this 24 hr panic but no suggestions.
[.]
panic: from debugger
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xcf41224
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0380a07
stack pointer = 0x10:0xde0f7b28
frame pointer = 0x10:0xde0f7b80
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 51776 (sudo)
panic: from debugger
Fatal trap 3: breakpoint instruction fault while in kernel mode
instruction pointer = 0x8:0xc047eb54
stack pointer = 0x10:0xde0f78a8
frame pointer = 0x10:0xde0f78b4
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= IOPL = 0
current process = 51776 (sudo)
panic: from debugger
Uptime: 23h52m33s
Dumping 511 MB
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:238
238 dumping++;
(kgdb) bt
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:238
#1 0xc0309828 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:370
#2 0xc0309b1b in panic () at /usr/src/sys/kern/kern_shutdown.c:543
#3 0xc0162bb2 in db_panic () at /usr/src/sys/ddb/db_command.c:448
#4 0xc0162b32 in db_command (last_cmdp=0xc0518d40, cmd_table=0x0,
aux_cmd_tablep=0xc050fbbc, aux_cmd_tablep_end=0xc050fbd4)
at /usr/src/sys/ddb/db_command.c:346
#5 0xc0162c46 in db_command_loop () at
/usr/src/sys/ddb/db_command.c:470
#6 0xc01659da in db_trap (type=12, code=0) at
/usr/src/sys/ddb/db_trap.c:72
#7 0xc047e8b5 in kdb_trap (type=12, code=0, regs=0xde0f7ae8)
at /usr/src/sys/i386/i386/db_interface.c:170
#8 0xc04905c2 in trap_fatal (frame=0xde0f7ae8, eva=0)
at /usr/src/sys/i386/i386/trap.c:829
#9 0xc04902d2 in trap_pfault (frame=0xde0f7ae8, usermode=0,
eva=217322020)
at /usr/src/sys/i386/i386/trap.c:748
#10 0xc048fead in trap (frame=
{tf_fs = -569442280, tf_es = 16, tf_ds = -962985968, tf_edi = 152,
tf_esi
= 0, tf_ebp = -569410688, tf_isp = -569410796, tf_ebx = -964577280,
tf_edx = -96
2953984, tf_ecx = -569410664, tf_eax = 217321984, tf_trapno = 12, tf_err
= 0, tf
_eip = -1070069241, tf_cs = 8, tf_eflags = 66182, tf_esp = 12, tf_ss =
-56941074
8}) at /usr/src/sys/i386/i386/trap.c:433
#11 0xc0480208 in calltrap () at {standard input}:96
#12 0xc0380b91 in sysctl_rtsock (oidp=0xc054db40, arg1=0xde0f7cb0,
arg2=4,
---Type return to continue, or q return to quit---
req=0x0) at /usr/src/sys/net/rtsock.c:1048
#13 0xc03121ba in sysctl_root (oidp=0x0, arg1=0x98, arg2=0,
req=0xc681b800)
at /usr/src/sys/kern/kern_sysctl.c:1173
#14 0xc031245d in userland_sysctl (td=0x0, name=0xde0f7ca8, namelen=6,
old=0x0, oldlenp=0xc681b800, inkernel=0, new=0x98, newlen=0,
retval=0xde0f7ca4) at /usr/src/sys/kern/kern_sysctl.c:1280
#15 0xc03122a0 in __sysctl (td=0x0, uap=0xde0f7d10)
at /usr/src/sys/kern/kern_sysctl.c:1210
#16 0xc04908be in syscall (frame=
{tf_fs = -1078001617, tf_es = 47, tf_ds = -1078001617, tf_edi = 0,
tf_esi
= -1077937156, tf_ebp = -1077937288, tf_isp = -569410188, tf_ebx =
672630356, tf
_edx = 0, tf_ecx = -1077937152, tf_eax = 202, tf_trapno = 12, tf_err =
2, tf_eip
= 672127299, tf_cs = 31, tf_eflags = 663, tf_esp = -1077937332, tf_ss =
47})
at /usr/src/sys/i386/i386/trap.c:1021
#17 0xc048025d in Xint0x80_syscall () at {standard input}:138
---Can't read userspace from dump, or kernel process---
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
ATAng and CF cards
Hi. The latest changes in ATAng code made it impossible to use my CF cards. I have a few of them which previously worked just fine. Now, each time I put one to my laptop's PCMCIA slot i get following errors: pccard0: Allocation failed for cfe 0 ata2: CL ATA FLASH CARD LEXAR TIDALWV at port 0x110-0x11f irq 11 function 0 config 1 on pccard0 ata2: [MPSAFE] ad4: FAILURE - SETFEATURES status=51READY,DSC,ERROR error=4ABORTED ad4: FAILURE - SETFEATURES status=51READY,DSC,ERROR error=4ABORTED ad4: FAILURE - SET_MULTI status=51READY,DSC,ERROR error=4ABORTED GEOM: create disk ad4 dp=0xc1e9d770 ad4: 9007199253773098MB \M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P [426376296036596/208/208] at ata2-master PIO0 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng and CF cards
On Sun, 7 Sep 2003, Martin Jessa wrote: The latest changes in ATAng code made it impossible to use my CF cards. I have a few of them which previously worked just fine. Now, each time I put one to my laptop's PCMCIA slot i get following errors: Looks like it mounted fine to me; some of the special options failed but thats not unusual. GEOM: create disk ad4 dp=0xc1e9d770 ad4: 9007199253773098MB \M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P [426376296036596/208/208] at ata2-master PIO0 Does ad4 work? -- 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: ATAng and CF cards
On Sun, 7 Sep 2003, Doug White wrote: On Sun, 7 Sep 2003, Martin Jessa wrote: The latest changes in ATAng code made it impossible to use my CF cards. I have a few of them which previously worked just fine. Now, each time I put one to my laptop's PCMCIA slot i get following errors: Looks like it mounted fine to me; some of the special options failed but thats not unusual. GEOM: create disk ad4 dp=0xc1e9d770 ad4: 9007199253773098MB \M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P [426376296036596/208/208] at ata2-master PIO0 Does ad4 work? Perhaps not the last 9007199252 TB of it. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng problems
Soren Schmidt [EMAIL PROTECTED] writes: I have one other report of problems on the older Acer chips, I must have screwed something up there. I'll dig out my old ASUS board and see what I can find out... Great, I'll be happy to test stuff. Bortset fra det kunne vi da snakke dansk ku' vi ikke ? :) Jo, men så forstår de andre jo ikke så meget. :) -- Med venlig hilsen Christian Laursen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb flashkey disk copy error
On Sun, Sep 07, 2003 at 12:32:46AM -0700, John-Mark Gurney wrote: You're the second person that has reported corruption with USB umass devices. I am interested in tracking down this problem, but it's a bit difficult since I haven't seen it myself. Make me the third. I have a Sony F707 camera, which I can use on 4-stable and with 5-current on a Dell I5000 laptop, but not on 5-current on an Asus A7M266-D with world/kernel built 9/4/03. The bad data starts at byte 4096, always. The problem has existed for at least a month, perhaps longer; I can't remember if it ever worked on the Asus. But the same system runs fine with usb keyboard and mouse - which proves nothing as the data rate and amount are so small. So I can't rule out hardware as the problem. In a few days I can try booting from a 4.8 live cd and see if the hardware works ok. Old-quirks had no effect on the problem. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb flashkey disk copy error
Barney Wolff wrote this message on Sun, Sep 07, 2003 at 13:46 -0400: On Sun, Sep 07, 2003 at 12:32:46AM -0700, John-Mark Gurney wrote: You're the second person that has reported corruption with USB umass devices. I am interested in tracking down this problem, but it's a bit difficult since I haven't seen it myself. Make me the third. I have a Sony F707 camera, which I can use on 4-stable and with 5-current on a Dell I5000 laptop, but not on 5-current on an Asus A7M266-D with world/kernel built 9/4/03. The bad data starts at byte 4096, always. The problem has existed for at least a month, Ahh, this is useful information. What are the controller types of the two machines? ohci? uhci? I think it might be ohci, and it maybe a page miscalculation when dispatching the request. Have you looked at the corrupted data? does it apear to be from some other location, like the kernel? perhaps longer; I can't remember if it ever worked on the Asus. But the same system runs fine with usb keyboard and mouse - which proves nothing as the data rate and amount are so small. So I can't rule out hardware as the problem. In a few days I can try booting from a 4.8 live cd and see if the hardware works ok. Old-quirks had no effect on the problem. It's been about two months since I updated USB to use bus_dma. So you could try checking out the usb code from July 4th or so and see if it goes away (it probably will). -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng problems
I thought I was going to miss out on the ATAng issues... I use a SanDisk CompactFlash PC Card Adapter to read my digital camera pictures. It worked fine before ATAng. Now I get: ata2: spurious interrupt - status=0xff error=0x00 reason=0x00 ata2: spurious interrupt - status=0xff error=0x00 reason=0x00 ata2: spurious interrupt - status=0xff error=0x00 reason=0x00 ata2: spurious interrupt - status=0xff error=0x00 reason=0x00 ata2: spurious interrupt - status=0xff error=0x00 reason=0x00 ... And after transferring some data the machine locks up. I updated last night from my week old -CURRENT but still have the same problem. Starting update: Sat Sep 6 21:27:09 EDT 2003 Finished update: Sat Sep 6 21:35:20 EDT 2003 http://www.lambertfam.org/~lambert/laptop/5/20030907-1331 has the verbose dmesg.boot and dmesg showing the insertion and removal of the card as well as other things. It doesn't lockup until I try to transfer data. When it locks up and I restart, it has typically transferred about 10 - 15 700K to 1.2M photos. -- Scott LambertKC5MLE Unix SysAdmin [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng problems
On Sun, 7 Sep 2003, Scott Lambert wrote:
I thought I was going to miss out on the ATAng issues...
I use a SanDisk CompactFlash PC Card Adapter to read my digital camera
pictures. It worked fine before ATAng. Now I get:
ata2: spurious interrupt - status=0xff error=0x00 reason=0x00
ata2: spurious interrupt - status=0xff error=0x00 reason=0x00
ata2: spurious interrupt - status=0xff error=0x00 reason=0x00
ata2: spurious interrupt - status=0xff error=0x00 reason=0x00
ata2: spurious interrupt - status=0xff error=0x00 reason=0x00
...
And after transferring some data the machine locks up.
I get endless spurious interrupts at boot time and use the following
fix.
%%%
Index: ata-lowlevel.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-lowlevel.c,v
retrieving revision 1.8
diff -u -2 -r1.8 ata-lowlevel.c
--- ata-lowlevel.c 1 Sep 2003 11:13:21 - 1.8
+++ ata-lowlevel.c 1 Sep 2003 18:03:56 -
@@ -271,10 +271,15 @@
struct ata_channel *ch = (struct ata_channel *)data;
struct ata_request *request = ch-running;
+static int spurcount;
+static int spurtotcount;
int length;
/* if we dont have a running request shout and ignore this interrupt */
if (request == NULL) {
- if (bootverbose) {
- printf(ata%d: spurious interrupt - , device_get_unit(ch-dev));
+ spurcount++;
+ spurtotcount++;
+ if (1 || bootverbose) {
+ printf(ata%d: %d/%dth spurious interrupt - ,
+ device_get_unit(ch-dev), spurtotcount, spurcount);
if (request)
printf(request OK - );
@@ -283,4 +288,8 @@
ATA_IDX_INB(ch, ATA_IREASON));
}
+ if (spurcount == 10) {
+ (void)ATA_IDX_INB(ch, ATA_STATUS);
+ spurcount = 0;
+ }
return;
}
%%%
More details:
- most of the above is debuggig code. Only on line near the end that
reads the status register is necessary. The debugging code waits for
10 spurious interrupts before clearing the interrupt.
- the spurious interrupts somehow go away without the above change after
2 or 3 of them for plain -current, but repeat endlessly with my version
of -current. The hardware interrupt is not repeated, but something at
a level between Xintr*() and ata_highpoint_intr() apparently keeps
dispatching the interrupt.
- the spurious interrupts only happen on a channel with an atapi slave.
They don't happen on channels with both slaves and masters or on an
empty channel.
Some dmesg output with the above fix:
%%%
...
atapci1: HighPoint HPT366 UDMA66 controller port
0xbc00-0xbcff,0xb800-0xb803,0xb400-0xb407 irq 11 at device 19.0 on pci0
ithread_add_handler: atapci1: id -1
atapci1: [MPSAFE]
ata2: at 0xb400 on atapci1
ata2: [MPSAFE]
atapci2: HighPoint HPT366 UDMA66 controller port
0xc800-0xc8ff,0xc400-0xc403,0xc000-0xc007 irq 11 at device 19.1 on pci0
ithread_add_handler: atapci2: id -1
atapci2: [MPSAFE]
ata3: at 0xc000 on atapci2
ata3: [MPSAFE]
orm0: Option ROMs at iomem 0xc8000-0xcbfff,0xc-0xc7fff on isa0
fdc0: Enhanced floppy controller (i82077, NE72065 or clone) at port
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
ithread_add_handler: fdc0: id -1
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5 drive on fdc0 drive 0
atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
ithread_add_handler: atkbd0: id -1
psm0: PS/2 Mouse irq 12 on atkbdc0
ithread_add_handler: psm0: id -1
psm0: model Generic PS/2 mouse, device ID 0
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0
sio0: type 16550A
ithread_add_handler: sio0: id -1
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ithread_add_handler: sio1: id -1
cy0 at iomem 0xd4000-0xd5fff irq 10 on isa0
ithread_add_handler: tty:cy: id 10
ithread_add_handler: cy: id -1
cy0: driver is using old-style compatibility shims
ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0: Parallel port bus on ppc0
plip0: PLIP network interface on ppbus0
lpt0: Printer on ppbus0
lpt0: Interrupt-driven port
ppi0: Parallel I/O on ppbus0
ithread_add_handler: ppc0: id -1
unknown: PNP0303 can't assign resources (port)
pca1: AT-style speaker sound at port 0x61 on isa0
unknown: PNP0a03 can't assign resources (port)
unknown: PNP0f13 can't assign resources (irq)
unknown: PNP0501 can't assign resources (port)
unknown: PNP0700 can't assign resources (port)
unknown: PNP0401 can't assign resources (port)
unknown: PNP0501 can't assign resources (port)
ithread_add_handler: clk: id -1
ata0: 1/1th spurious interrupt - status=0x00 error=0x01 reason=0x01
ata1: 2/2th spurious interrupt -
Re: devd *NOT* called on wi0 insert?
M == M Warner Losh [EMAIL PROTECTED] writes: M In message: [EMAIL PROTECTED] Larry M Rosenman [EMAIL PROTECTED] writes: : I have a (within the week) M -CURRENT system. If I boot with my Linksys : WPC11 V.3 card M inserted : I get the dhcp actions and all is fine. If I remove the M card, we don't : kill off dhclient. : : If I boot without the Actually, I think devd needs to be significantly smarter. Consider the average laptop: one or more permanent interfaces and one or more transient interfaces. Currently, if bge0 (my permanent interface) has link at boot, it gets dhclient. Similarly to the origional poster, if wi0 is inserted at boot, it gets dhclient. devd doesn't seem to do much else. There is a caveat, of course. You can't run multiple copies of dhclient (say one for each interface). This is broken. You must, in fact, run one copy of dhclient listing all the interfaces to configure. This is contrary (say) to moused ... which works well with multiple mice. Ideally, you would start dhclient on an interface when it had link and stop it when it lost link. You might want to put a 10 or 15 second timeout on that (as it could be annoying with a flakey controller), but this makes sense. In this case, devd would not only have to watch changes to the device tree, but device state transitions. Less ideally, dhclient should run on all capable interfaces whenever they're present. In the current scheme, this requires some external smarts as you must kill off the current dhclient and restart it with a new list of interfaces. 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: ATAng problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 To all the english speaking on this list, I'm sorry for this small internal joke - but when I observe two danes thinking they are the only ones to understand their language, I need to remind them otherwise ;) Si for all del ikke noe dritt om meg, for jeg forstår dere ; /Eirik On 07 Sep 2003 19:44:10 +0200 Christian Laursen [EMAIL PROTECTED] wrote: Soren Schmidt [EMAIL PROTECTED] writes: I have one other report of problems on the older Acer chips, I must have screwed something up there. I'll dig out my old ASUS board and see what I can find out... Great, I'll be happy to test stuff. Bortset fra det kunne vi da snakke dansk ku' vi ikke ? :) Jo, men så forstår de andre jo ikke så meget. :) -- Med venlig hilsen Christian Laursen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/W3dZdAvR8ct7fEcRAivPAJ9+CW462hrRVoiN5W2axzacfw+EJACZAUS/ NPHoaGVNJlhhHbTfjEieVGM= =nJMz -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
LS120, ATANg and Atapicam
Mark == Mark Dixon [EMAIL PROTECTED] writes: Mark Hi, I'm not sure if this is a known problem, but I don't see any Mark references to it. I've gone from 5.1-RELEASE to todays CURRENT Mark to try to get rid of a different panic (no news on that yet), Mark but I have hit this one. Mark If I boot my system with no floppy in the LS-120, the system Mark panics where atapicam creates da0 for it. If there is a disk in Mark the drive, it works fine. Mark As yet, I havn't got the details of the panic, but if this is of Mark interest to anyone here, I will be willing to provide them with Mark them (they wil have to be be copied out by hand, so I'm lothe to Mark do it if nobody is interested). Mark Sorry if this email is a little vague, its been a long week. I'm just about to try to reproduce a panic along the same lines. My laptop has two ide channels with the hard drive on one and the DVD+R drive on the other. With yesterday's cvsup, it somehow finds a phantom ad3 _only_ if the DVD+R is in it's bay. With the DVD+R removed, the system is still functional (luckily). More info to follow as I get a kernel with debugging symbols in it. 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]
problems with_dynamicroot =yes/noshared=no ?
Hello friends, I'm seeing a weird issue with my recent build, here goes: shiba# ls -ld /lib drwxr-xr-x 2 root wheel 1024 Sep 7 01:53 /lib shiba# ls -lh /lib/libc.so.5 -r--r--r-- 1 root wheel862K Sep 7 01:50 /lib/libc.so.5 shiba# ls -lh /usr/lib/libc.so.5 -r--r--r-- 1 root wheel875K Jul 6 19:53 /usr/lib/libc.so.5 shiba# ldd /sbin/init /sbin/init: libutil.so.3 = /usr/lib/libutil.so.3 (0x28076000) libcrypt.so.2 = /usr/lib/libcrypt.so.2 (0x28082000) libc.so.5 = /usr/lib/libc.so.5 (0x2809b000) Nothing in my /bin or /sbin is linked to anything in /lib. =( My environment is a jail where I use NOSHARED=NO, and WITH_DYNAMICROOT. At first I though my init was linking to stuff in /usr/lib for compatibility, but libc is not a symbolic link, so this is not a compatability-link issue. My working theory thus far is that maybe NOSHARED=NO might be interfearing with WITH_DYNAMICROOT, but I'm not sure how to find out if that is true/false. Anybody know what is going on? Thanks in advance, -Jon (masta) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb flashkey disk copy error
On Sun, Sep 07, 2003 at 10:55:24AM -0700, John-Mark Gurney wrote: Make me the third. I have a Sony F707 camera, which I can use on 4-stable and with 5-current on a Dell I5000 laptop, but not on 5-current on an Asus A7M266-D with world/kernel built 9/4/03. The bad data starts at byte 4096, always. The problem has existed for at least a month, Ahh, this is useful information. What are the controller types of the two machines? ohci? uhci? I think it might be ohci, and it maybe a page miscalculation when dispatching the request. Indeed, failing system has ohci, working has uhci. Have you looked at the corrupted data? does it apear to be from some other location, like the kernel? Can't tell offhand, but doesn't look like code - not enough zeroes. As I recall, multiple tries produced the same bad data each time (after umount and re-mount). I can't do more detailed diagnosis right now, but could in a few days. perhaps longer; I can't remember if it ever worked on the Asus. But the same system runs fine with usb keyboard and mouse - which proves nothing as the data rate and amount are so small. So I can't rule out hardware as the problem. In a few days I can try booting from a 4.8 live cd and see if the hardware works ok. Old-quirks had no effect on the problem. It's been about two months since I updated USB to use bus_dma. So you could try checking out the usb code from July 4th or so and see if it goes away (it probably will). Will try that, again in a few days. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
i386_set_ldt messages with today's world
Hi all, I have no idea what it means, but since today's world I get the following messages after starting x: Warning: pid 541 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 547 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 548 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 567 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 568 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 569 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 570 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 573 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 572 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 577 used static ldt allocation. See the i386_set_ldt man page for more info Only ode still exists which is: 541 ?? S 0:15,50 /usr/X11R6/bin/XFree86 -auth /var/run/xauth/A:0-2CitM Thanks, -Harry pgp0.pgp Description: signature
Re: ATAng problems
Si for all del ikke noe dritt om meg, for jeg forst=E5r dere ; Soeren cyning,ATAng das blinkenleiten dryhten, beorna beahgifa, his broþor eac, Fred,ealdorlangne tir geslogon æt sæccesweorda ecgum ymbe [EMAIL PROTECTED] Bordweal clufan, heowan heaþolindehamora lafan, afaran Eadweardes,swa him geæþele wæs from cneomægum,þæt hi æt campe oft wiþ laþra gehwæneland ealgodon, hord hamas ja baby! Andrew Lankford ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
patch for ATAng bug
I submitted kern/56572 a few minutes ago. It patches ata-disk.c to reject a disk that has zero blocks. This is a good thing ... malicious or broken disks (compact flash, whatever) shouldn't crash machines. But in this case, the detected ad3 doesn't exist. The machine is a laptop with a drive on channel 0 and a DVD+R on channel 1. If the DVD is removed, the phantom ad3 doesn't show up, either. ... so that issue with ATAng is unresolved. 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: usb flashkey disk copy error
Barney Wolff wrote this message on Sun, Sep 07, 2003 at 15:48 -0400:
I can't do more detailed diagnosis right now, but could in a few days.
When you get a chance (or anyone else who has this problem), try the
attached patch, and add options BROKEN_OHCI to your kernel config file.
Please set hw.usb.ohci.debug=1, and send me the dmesg output of the
writes. (When you copy the data to the media.)
Hmmm. I just thought of something. Now is the data corrupt still correupt
on another system? What I mean is did the data get written properly, but
just isn't being read back from the media correctly. Unless you are
coping a file larger than memory size, the cmp just pulls it from memory,
not from the media. The umount/mount forces a flush of the cache, and so
attempts to read from the media.
Thanks.
--
John-Mark Gurney Voice: +1 415 225 5579
All that I will do, has been done, All that I have, has not.
Index: ohci.c
===
RCS file: /home/ncvs/src/sys/dev/usb/ohci.c,v
retrieving revision 1.132
diff -u -r1.132 ohci.c
--- ohci.c 2003/08/24 17:55:54 1.132
+++ ohci.c 2003/09/07 20:28:13
@@ -513,6 +513,14 @@
DPRINTFN(alen 4096,(ohci_alloc_std_chain: start len=%d\n, alen));
+ if (ohcidebug alen 4096) {
+ printf(len: %d, pages: , alen);
+ for (len = 0; len alen; len += OHCI_PAGE_SIZE) {
+ printf(%s0x%x, len == 0 ? : , , DMAADDR(dma,
+ len));
+ }
+ }
+
len = alen;
cur = sp;
@@ -546,9 +554,14 @@
* We can describe the above using maxsegsz = 4k and nsegs = 2
* in the future.
*/
+#if BROKEN_OHCI
+ if (len OHCI_PAGE_SIZE - OHCI_PAGE_OFFSET(dataphys))
+#else
if (OHCI_PAGE(dataphys) == OHCI_PAGE(DMAADDR(dma, offset +
len - 1)) || len - (OHCI_PAGE_SIZE -
- OHCI_PAGE_OFFSET(dataphys)) = OHCI_PAGE_SIZE) {
+ OHCI_PAGE_OFFSET(dataphys)) = OHCI_PAGE_SIZE)
+#endif
+ {
/* we can handle it in this TD */
curlen = len;
} else {
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devd *NOT* called on wi0 insert?
In message: [EMAIL PROTECTED] David Gilbert [EMAIL PROTECTED] writes: : M == M Warner Losh [EMAIL PROTECTED] writes: : : M In message: [EMAIL PROTECTED] Larry : M Rosenman [EMAIL PROTECTED] writes: : I have a (within the week) : M -CURRENT system. If I boot with my Linksys : WPC11 V.3 card : M inserted : I get the dhcp actions and all is fine. If I remove the : M card, we don't : kill off dhclient. : : If I boot without the : : Actually, I think devd needs to be significantly smarter. Consider : the average laptop: one or more permanent interfaces and one or more : transient interfaces. The current devd is smart enough. Devd's config file might use some additional tweaking. : Currently, if bge0 (my permanent interface) has link at boot, it gets : dhclient. Similarly to the origional poster, if wi0 is inserted at : boot, it gets dhclient. Don't blame devd for dhclient being brain dead. Fix the brain damage in dhclient, don't use devd to work around that brain damage. : devd doesn't seem to do much else. Devd does anything you want it to do. Warner ___ [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-07 20:02:57 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-09-07 20:02:57 - 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-07 20:05:46 - 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-07 21:00:50 - 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 7 21:00:50 GMT 2003 [...] /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c:271: error: invalid operands to binary /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c: In function `sab82532_bus_getsig': /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c:448: error: invalid operands to binary /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c: In function `sab82532_bus_probe': /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c:555: error: invalid operands to binary /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c: In function `sab82532_bus_setsig': /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c:637: error: invalid operands to binary /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/dev/uart/uart_dev_sab82532.c:639: error: invalid operands to binary *** 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-07 21:09:30 - /usr/bin/make returned exit code 1 TB --- 2003-09-07 21:09:30 - ERROR: failed to build generic kernel TB --- 2003-09-07 21:09:30 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i386_set_ldt messages with today's world
On Sun, 7 Sep 2003, Harald Schmalzbauer wrote: Hi all, I have no idea what it means, but since today's world I get the following messages after starting x: Warning: pid 541 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 547 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 548 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 567 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 568 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 569 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 570 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 573 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 572 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 577 used static ldt allocation. See the i386_set_ldt man page for more info Something is using i386_set_ldt() static ldt allocations. We added the warning message to detect usage of these allocations so they could be changed to dynamic allocations. Our threads libraries make use of LDTs on i386, so having other code also use (possibly) the same LDT would break things. Only ode still exists which is: 541 ?? S 0:15,50 /usr/X11R6/bin/XFree86 -auth /var/run/xauth/A:0-2CitM What is ode? Typo? pid? I don't see how XFree86 can use i386_set_ldt(). It doesn't reference it on my box: $ nm /usr/X11R6/bin/XFree86 | grep ldt $ -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i386_set_ldt messages with today's world
On Sunday 07 September 2003 23:13, Daniel Eischen wrote: *SNIP* Warning: pid 577 used static ldt allocation. See the i386_set_ldt man page for more info Something is using i386_set_ldt() static ldt allocations. We added the warning message to detect usage of these allocations so they could be changed to dynamic allocations. Our threads libraries make use of LDTs on i386, so having other code also use (possibly) the same LDT would break things. Only ode still exists which is: 541 ?? S 0:15,50 /usr/X11R6/bin/XFree86 -auth /var/run/xauth/A:0-2CitM What is ode? Typo? pid? Typo. Only one PID is still listed. I don't see how XFree86 can use i386_set_ldt(). It doesn't reference it on my box: $ nm /usr/X11R6/bin/XFree86 | grep ldt I also tried that and nothing returns. Had a look at man nm, but can't do anything with it. I'm no programmer. And first I'll have to get a i386 Microprocessor Programmer's Reference Manual, Intel. Well, like mentioned I'm no programmer, I only wondered what this was and as far as I understood it's nothing I have to worry about, but unclear to you? Let me know if I can do anything helpful. Thanks, -Harry $ pgp0.pgp Description: signature
Re: usb flashkey disk copy error
On Sun, 7 Sep 2003, John-Mark Gurney wrote: Hmmm. I just thought of something. Now is the data corrupt still correupt on another system? What I mean is did the data get written properly, but just isn't being read back from the media correctly. Unless you are coping a file larger than memory size, the cmp just pulls it from memory, not from the media. The umount/mount forces a flush of the cache, and so attempts to read from the media. I'm also suffering (probably) the same problem. In my case, the drive is a Sony memory stick slot on a PCG-U1 laptop; connection to the system is via OHCI. For my usage, it's definitely a _read_ phenomenon - I'm creating images on the memory stick in my P800 phone/camera and trying to read them via an msdosfs mount on the laptop. Retrieving them via Windows demonstrates that the images are good; reading them under FreeBSD shows them corrupt at a _file_ offset of 4096 decimal. I tried copying the whole filesystem with 'dd', then using 'mdconfig' to mount the resulting image, eg.: dd if=/dev/da0s1 of=stickfile4 bs=32k mdconfig -a stickfile4 mount -t msdos /dev/md0 /mnt With a blocksize to 'dd' of 512, 8k it worked fine (no corruption); with a block size of 100k the files were corrupt (but in different places compared to mounting the memorystick directly). Using a block size of 32k, it copied for a minute or so and then the machine hung totally (repeatable across two attempts). In terms of dates, I'm now running with -current of 4th september; this problem was also present in a kernel built on August 22nd. It was working OK with whatever kernel I was running on 23rd May (based on timestamps on some files I wrote on the PC). In fact, up until around that time this setup didn't work at all: the internal OCHI port that connects to the memory stick slot always reported 'device problem' and wouldn't find the device (the second OHCI controller that is brought out to conventional sockets worked OK). One system update that I did suddenly made everything work, then a month or two later this problem arrived. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng and CF cards
Hi. It can be mounted when I boot the laptop and do not take the card out of the slot. If I eject it and then put it back in, I cannot mount it or dd files to it anymore... Anyway, this bit of dmesg does not look healthy to me. And as I said, everything worked fine before the ATAng code got changed. Cheers, YazzY Doug White wrote: On Sun, 7 Sep 2003, Martin Jessa wrote: The latest changes in ATAng code made it impossible to use my CF cards. I have a few of them which previously worked just fine. Now, each time I put one to my laptop's PCMCIA slot i get following errors: Looks like it mounted fine to me; some of the special options failed but thats not unusual. GEOM: create disk ad4 dp=0xc1e9d770 ad4: 9007199253773098MB \M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P [426376296036596/208/208] at ata2-master PIO0 Does ad4 work? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i386_set_ldt messages with today's world
On Sun, 2003-09-07 at 14:13, Daniel Eischen wrote: On Sun, 7 Sep 2003, Harald Schmalzbauer wrote: Hi all, I have no idea what it means, but since today's world I get the following messages after starting x: Warning: pid 541 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 547 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 548 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 567 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 568 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 569 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 570 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 573 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 572 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 577 used static ldt allocation. See the i386_set_ldt man page for more info Something is using i386_set_ldt() static ldt allocations. We added the warning message to detect usage of these allocations so they could be changed to dynamic allocations. Our threads libraries make use of LDTs on i386, so having other code also use (possibly) the same LDT would break things. Only ode still exists which is: 541 ?? S 0:15,50 /usr/X11R6/bin/XFree86 -auth /var/run/xauth/A:0-2CitM What is ode? Typo? pid? I don't see how XFree86 can use i386_set_ldt(). It doesn't reference it on my box: $ nm /usr/X11R6/bin/XFree86 | grep ldt $ XFree86 loads various modules from /usr/X11R6/lib/modules. That said, I could find nothing about ldts being used anywhere in the source (grepping for LDT, sldt, and set_ldt). Perhaps the nvidia driver is being used? That's the only thing I could think of. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Help with password expire
I am trying to use freebsd's way of password expiration to make it so i need to change my password every 30 days ive got: :warnpassword=4d:\ :passwordtime=30d: in my /etc/login.conf did a cap_mkdb /etc/login.conf i tryed to change the password of one of my users using passwd and it doesnt seem to add a change time to it according to chpass the: Change [month day year]: stays unchanged but if i manually add the change time using pw it adds the change time but if i change the password it doesnt add a new change time do i need to edit the /etc/pam.d/passwd and uncomment the top line thats commented out ? cause it seems to be broken atm as it doesnt do what i ask it to do. if you need anythign else please let me know -chris _ Get 10MB of e-mail storage! Sign up for Hotmail Extra Storage. http://join.msn.com/?PAGE=features/es ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i386_set_ldt messages with today's world
On Monday 08 September 2003 00:17, Eric Anholt wrote: On Sun, 2003-09-07 at 14:13, Daniel Eischen wrote: On Sun, 7 Sep 2003, Harald Schmalzbauer wrote: *SCHNIP* See the i386_set_ldt man page for more info Something is using i386_set_ldt() static ldt allocations. We added the warning message to detect usage of these allocations so they could be changed to dynamic allocations. Our threads libraries make use of LDTs on i386, so having other code also use (possibly) the same LDT would break things. Only ode still exists which is: 541 ?? S 0:15,50 /usr/X11R6/bin/XFree86 -auth /var/run/xauth/A:0-2CitM What is ode? Typo? pid? I don't see how XFree86 can use i386_set_ldt(). It doesn't reference it on my box: $ nm /usr/X11R6/bin/XFree86 | grep ldt $ XFree86 loads various modules from /usr/X11R6/lib/modules. That said, I could find nothing about ldts being used anywhere in the source (grepping for LDT, sldt, and set_ldt). Perhaps the nvidia driver is being used? That's the only thing I could think of. Yep, exactly that's the driver I'm using (GF4MX440-8) (I'm one of those without ANY problem with this card/driver (dualHead) btw.) Thanks, -Harry pgp0.pgp Description: signature
Re: Help with password expire
On Sun, Sep 07, 2003 at 04:31:33PM -0700, Chris Petrik wrote: I am trying to use freebsd's way of password expiration to make it so i need to change my password every 30 days ive got: :warnpassword=4d:\ :passwordtime=30d: in my /etc/login.conf did a cap_mkdb /etc/login.conf i tryed to change the password of one of my users using passwd and it doesnt seem to add a change time to it according to chpass the: Change [month day year]: stays unchanged but if i manually add the change time using pw it adds the change time but if i change the password it doesnt add a new change time do i need to edit the /etc/pam.d/passwd and uncomment the top line thats commented out ? cause it seems to be broken atm as it doesnt do what i ask it to do. if you need anythign else please let me know A password expiry system is not natively implemented in FreeBSD although the password expiry field in the password database allows one to set up a system. The users on the system where I work log in mostly via gdm so I set up some checks in the PreSession file to check the password expiry field and call passwd if the password has expired. After a successful password change, the pw command is called to reset the expiry field. To catch the case where a user changes the password at a time other than when prompted via the PreSession script I set up a script that runs via periodic/daily. This script checks the expiry field and if 0 it calls pw to set the expiry field to the appropriate value. Since this runs daily, the assumption is that the password was changed within the last 24 hours. The password warning feature works really well with gdm as it pops up a dialog box. There is no warning at console logins but I am the only one allowed to login at the console so that is not a big deal for me but may be for you. There is a warning displayed during an ssh login but it is very easy to miss it as it scrolls off the screen. One warning about ssh: Once the user's password has expired, ssh will not allow the login thereby locking out that user from that mode of access. This is not FreeBSD specific. There are probably several ways to write scripts for this and they would have to be tailored to your situation but hopefully I have given you some ideas about how to proceed. One thing that will definitely influence how you ultimately set this up is whether you use NIS or not. -- Glenn Johnson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng and CF cards
In message: [EMAIL PROTECTED] Bruce Evans [EMAIL PROTECTED] writes: : On Sun, 7 Sep 2003, Doug White wrote: : On Sun, 7 Sep 2003, Martin Jessa wrote: : ad4: 9007199253773098MB \M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P [426376296036596/208/208] at ata2-master PIO0 : : Does ad4 work? : : Perhaps not the last 9007199252 TB of it. :-) Where can I get a 9007199252TB flash part? Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
sylogd not logging
I used to run 4.6 where syslogd worked fine with cisco 7507, as5300, and max4048. Eversince I've installed 5.0-RELEASE, I used exact same config as old, but can't get it working. Please help. The following is configs: syslog.conf *.err;kern.debug;auth.notice;mail.crit /dev/console *.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages security.* /var/log/security auth.info;authpriv.info /var/log/auth.log mail.info /var/log/maillog lpr.info/var/log/lpd-errs ftp.info/var/log/xferlog cron.* /var/log/cron *.emerg * local0 /var/log/routers/nas1.log local1 /var/log/routers/gw-kln.log local2 /var/log/routers/max3.log local3 /var/log/routers/max2.log local4 /var/log/routers/max1.log *.* /var/log/all.log rc.conf syslogd_flags=-a *.isot.com #syslogd_flags=-a nas1.isot.com ; also tried this - Forwarded message from - From: Sing Song [EMAIL PROTECTED] Yesterday, I tried your recomendation to use rc.conf. Looked at the log file, still nothing. I added 'syslogd_flags=-a *.isot.com to the rc.conf and used '/etc/rc.d/syslogd start' after killing the old syslogd process. I sure am getting frustrated as not getting any diag info from the routers. Maybe I need to put back my old radius box. Instead of using *.isot.com, try just specifing the dns name of one of your routers that you would like to log. syslogd_flags=-a rtr1.isot.com If you get syslog messages with this, then try adding additional -a flags for each of your routers. syslogd_flags=-a rtr1.isot.com -a rtr2.isot.com ... rtrN.isot.com You may want to send a message to [EMAIL PROTECTED] informing them that remote logging isn't working for you. Scot - End forwarded message - - This mail sent through ISOT. To find out more about ISOT, visit http://isot.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: i386_set_ldt messages with today's world
On Mon, 8 Sep 2003, Harald Schmalzbauer wrote: On Monday 08 September 2003 00:17, Eric Anholt wrote: On Sun, 2003-09-07 at 14:13, Daniel Eischen wrote: On Sun, 7 Sep 2003, Harald Schmalzbauer wrote: *SCHNIP* See the i386_set_ldt man page for more info Something is using i386_set_ldt() static ldt allocations. We added the warning message to detect usage of these allocations so they could be changed to dynamic allocations. Our threads libraries make use of LDTs on i386, so having other code also use (possibly) the same LDT would break things. Only ode still exists which is: 541 ?? S 0:15,50 /usr/X11R6/bin/XFree86 -auth /var/run/xauth/A:0-2CitM What is ode? Typo? pid? I don't see how XFree86 can use i386_set_ldt(). It doesn't reference it on my box: $ nm /usr/X11R6/bin/XFree86 | grep ldt $ XFree86 loads various modules from /usr/X11R6/lib/modules. That said, I could find nothing about ldts being used anywhere in the source (grepping for LDT, sldt, and set_ldt). Perhaps the nvidia driver is being used? That's the only thing I could think of. Yep, exactly that's the driver I'm using (GF4MX440-8) (I'm one of those without ANY problem with this card/driver (dualHead) btw.) Is this binary only or source? Either way, it needs to be changed to use dynamic LDT allocations. -- Dan Eischen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI problems with this morning's -CURRENT
I set up a box yesterday to play with -CURRENT on. I used the 2003-09-06 snapshot code from ftp://current.freebsd.org/. Initial setup and boot worked just fine, but when I did a rebuild/reboot last night, this is what I saw: pmap_mapdev: Couldn't alloc kernel virtual memory So thinking I missed some kernel options, I pulled a couple of things, did another cvsup/rebuild/reboot this morning, and got the same thing. I know that various people have been having ongoing issues with ACPI, but this is the first problem I've had with it (I have a couple of other boxen running 5.1-RELEASE and 5-CURRENT). I was able to fix it (and discover that it was ACPI related) by finding this post (even though it's two years old): http://www.geocrawler.com/archives/3/147/2001/8/0/6526228/ The difference is that I'm seeing the pmap_mapdev error immediately after it spits out the 'real memory' and 'avail memory' lines. This is being run on a DFI CD70-SC, 512MB DDR SDRAM, with a Via C3 Nehemiah. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
pst driver: timeout explosion? (patch is attached)
Hi,
I think I may have found the cause of the pst timeout panics. I'm using
the Promise SX6000 RAID on -CURRENT, using the pst driver. Unfortunately,
under sufficiently high I/O load, the box starts printing:
pst: timeout mfa=0x00327b90 cmd=0x01
The 'mfa' address varies. It starts printing more and more rapidly, and
then eventually the machine wedges solid. Sometimes it makes it to:
panic: timeout table full
Here's what I think is happening. Two timeouts are being scheduled every
time a timeout triggers, because pst_timeout schedules a timeout before
calling pst_rw to retry the operation. Then pst_rw schedules ANOTHER
timeout. Both of these timeouts call pst_timeout, so they double every 10
seconds until there are a large enough number of timeouts firing, retrying
the same I/O operation, that the table fills and the machine panics.
Check out the following diff
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/pst/pst-raid.c.diff?r1=1.8r2=1.9f=h
This is where pst_rw was changed to schedule its own timeouts, but the
timeout function didn't have its removed.
Do you think this could be the correct explanation? It seems like once
pst_timeout is called, the machine is doomed... I'm recompiling my kernel
now to test the fix under load.
--Aaron
Index: /sys/dev/pst/pst-raid.c
===
RCS file: /usr/cvs/src/sys/dev/pst/pst-raid.c,v
retrieving revision 1.11
diff -u -r1.11 pst-raid.c
--- /sys/dev/pst/pst-raid.c 24 Aug 2003 17:54:17 - 1.11
+++ /sys/dev/pst/pst-raid.c 8 Sep 2003 02:32:58 -
@@ -316,11 +316,6 @@
mtx_unlock(request-psc-iop-mtx);
return;
}
-if (dumping)
- request-timeout_handle.callout = NULL;
-else
- request-timeout_handle =
- timeout((timeout_t*)pst_timeout, request, 10 * hz);
if (pst_rw(request)) {
iop_free_mfa(request-psc-iop, request-mfa);
biofinish(request-bp, NULL, EIO);
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb flashkey disk copy error
John-Mark Gurne wrote this message on Sun, Sep 07, 2003 at 08:45 +0200: raoul.megelas wrote: I have a copy error between hdd and a flashkey 1gig usb (easydisk) on Current dated August 28. Here is in short: mount -t msdos /dev/da2s1 /flashkey cp myfile /flashkey/ diff myfile /flashkey/myfile (ok). could you try a fsync /flashkey/myfile before the umount? umount /flashkey mount (flashkey) diff myfile /flashkey/myfile (Binary file differ)! It is not a flashkey disk error, it works on XP. Note that this error occurs on FreeBSD 4.8 too. Please, can you tell me how to deal with that? And in an other hand can you tell me how to obtain the exact map of the flashkey to verify the writing on the disk. Thanks in advance for this newbie question. You're the second person that has reported corruption with USB umass devices. I am interested in tracking down this problem, but it's a bit difficult since I haven't seen it myself. (I currently don't quite have a test bed box to play with, but I will in the next week.) John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. You have found the trick, fsync after cp works fine. Thanks very much. But why the fsync is not automatically done by umount on umass? (note) if you need to test against flashkey i can do that if you want.) raoul [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng and CF cards
Isn't the ATAng code great? It makes it affordable to get a 9007199253773098MB CF for the price of a 32 MB card. Now I am taking backups of the internet on it. :) M. Warner Losh wrote: In message: [EMAIL PROTECTED] Bruce Evans [EMAIL PROTECTED] writes: : On Sun, 7 Sep 2003, Doug White wrote: : On Sun, 7 Sep 2003, Martin Jessa wrote: : ad4: 9007199253773098MB \M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P\M-P [426376296036596/208/208] at ata2-master PIO0 : : Does ad4 work? : : Perhaps not the last 9007199252 TB of it. :-) Where can I get a 9007199252TB flash part? Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
usb flashkey error
Hello all, in a precedent message, i reported an error using a flashkey. I must add the following: as one can see in the dmesg below, the controller is NOT the ohci but uhci. The error occurs on writing not reading I tested the file written to the flashkey, without fsync and after unmount applied; The file looks garbage. In this case, as suggested by John-Mark Gurney, the fsync made the trick. Best regards. uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-A port 0xbce0-0xbcff irq 11 at device 31.2 on pci0 usb0: Intel 82801BA/BAM (ICH2) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub1: Philips Semiconductors hub, class 9/0, rev 1.10/1.10, addr 2 uhub1: 4 ports with 4 removable, self powered umass0: GENERIC USB Mass Storage, rev 1.10/1.00, addr 3 GEOM: create disk da2 dp=0xc2714c50 da2 at umass-sim0 bus 0 target 0 lun 0 da2: EasyDisk 1.00 Removable Direct Access SCSI-2 device da2: 1.000MB/s transfers da2: 1000MB (2048000 512 byte sectors: 64H 32S/T 1000C) ___ [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 Fri, Sep 05, 2003 at 07:50:24PM +0100, Stuart Walsh wrote: On Mon Aug 25, 11:11P -0500, Glenn Johnson wrote: Hi again chaps, I've been working on other things lately, including getting ready to move house and looking after my 3 month old daughter :) but recently I've took up trying to get this driver working again. If anyone is interested in helping out, could they give http://stu.bash.sh/if_sk.c and http://stu.bash.sh/if_skreg.h a try and let me know what output you get. I'm only really interested in what happens after the MAC gets printed so don't go to too much trouble to get the exact info. Just plonk the files in /usr/src/sys/pci over the top of the old ones. Thanks to anyone who helps out. Sorry for the delay. I just upgraded this machine to -current and things have just now settled down. I compiled the if_sk module (it seemed to want yukonreg.h, which I found on your site), loaded it, and got this: skc0: 3Com 3C940 Gigabit Ethernet port 0xb800-0xb8ff mem 0xdc80-0xdc803fff irq 5 at device 9.0 on pci0 skc0: 3Com Gigabit LOM (3C940) sk0: GI Yukon MAC on skc0 sk0: Ethernet address: xx:xx:xx:xx:xx:xx Yukon chip deteched Phy type 4 addr 0 sk_intr sk_intr sk_intr sk_intr sk_intr sk_intr sk_intr At this point the machine seemed to be writing to swap and kldload was hung, so I rebooted. Note that this the onboard 3C940 on the Asus A77V600 motherboard. I will be more than happy to help test any more code you have to get this driver working. -jre ___ [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, Sep 07, 2003 at 01:59:55PM +0200, 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. I have this same problem trying to use cdparanoia on my IDE CDROM (/dev/acd0), and my SCSI CDROM (/dev/cd0). I do not know if atapicam would help, as I have the same problem mentioned in another thread where atapicam panics on my atapi zip drive. -jre ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ADI AD1980 / VIA VT8237 sound support?
I just bought a new Asus A7V600 motherboard, which claims to have an ADI AD1980 SoundMAX 6-channel CODEC and a VIA VT8237 southbridge. Unfortunately, the sound does not seem to be supported. That's what I get for buying newly-released hardware I guess. Here is the appropriate portion of pciconf -l -v: [EMAIL PROTECTED]:17:5:class=0x040100 card=0x80b01043 chip=0x30591106 rev=0x60 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8233/33A AC97 Enhanced Audio Controller' class= multimedia subclass = audio I tried simply adding my chip revision to the probe routine in dev/sound/pci/via8233.c (patch included below) with this result: pcm0: VIA VT8237 port 0xe000-0xe0ff irq 5 at device 17.5 on pci0 pcm0: Analog Devices AD1980 AC97 Codec I was then able to play sound, but with an odd beeping noise. If there's anyone out there who wants to try to get this working, I will gratefully help in any way I can. Thanks, -jre --- via8233.c.orig Tue Sep 2 13:30:37 2003 +++ via8233.c Sun Sep 7 23:38:20 2003 @@ -53,6 +53,7 @@ #define VIA8233_REV_ID_82330x30 #define VIA8233_REV_ID_8233A 0x40 #define VIA8233_REV_ID_82350x50 +#define VIA8233_REV_ID_82370x60 #define SEGS_PER_CHAN 2 /* Segments per channel */ #define NDXSCHANS 4 /* No of DXS channels */ @@ -634,6 +635,9 @@ return 0; case VIA8233_REV_ID_8235: device_set_desc(dev, VIA VT8235); + return 0; + case VIA8233_REV_ID_8237: + device_set_desc(dev, VIA VT8237); return 0; default: device_set_desc(dev, VIA VT8233X);/* Unknown */ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LS120, ATANg and Atapicam
On Sun, Sep 07, 2003 at 12:18:56AM +, Mark Dixon wrote: Hi, I'm not sure if this is a known problem, but I don't see any references to it. I've gone from 5.1-RELEASE to todays CURRENT to try to get rid of a different panic (no news on that yet), but I have hit this one. If I boot my system with no floppy in the LS-120, the system panics where atapicam creates da0 for it. If there is a disk in the drive, it works fine. As yet, I havn't got the details of the panic, but if this is of interest to anyone here, I will be willing to provide them with them (they wil have to be be copied out by hand, so I'm lothe to do it if nobody is interested). Sorry if this email is a little vague, its been a long week. Just want to add a me too here. I have what looks like the same problem with an atapi zip drive. I can set up a serial cable and try to get a backtrace if that would help. -jre ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems on MSI K7D
This is the line that triggers that panic, from /sys/dev/acpica/Osd/OsdHardware.c: if (pci_cfgregopen() == 0) panic(AcpiOsDerivePciId unable to initialize pci bus); Please report the dmesg from boot -v as that should help figure out why pci_cfgregopen() fails. Also, I think the following should be \_S3: Name (\SS3, Package (0x04) -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
