Re: APCI vs APM
Quoting myself [EMAIL PROTECTED]: How should I proceed to make my laptop sleep ? :) acpiconf -s n (where n is number between 1 and 5) Questions are so nice when you can answer 'em by yourself ;P -- Pierrick Brossin IT Swiss - QUARK Media House 6a Puits Godet, 2000 Neuchatel, Switzerland Mail Prof: [EMAIL PROTECTED] Mail Priv: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
IRDA - ACPI (Battery)
Hi! Since APCI is now used instead of APM, I'm wondering if we have to wait/program softwares to control the battery status ? Is IRDA now supported by 5.0 ? Can't find any docs. Thanx again! -- Pierrick Brossin IT Swiss - QUARK Media House 6a Puits Godet, 2000 Neuchatel, Switzerland Mail Prof: [EMAIL PROTECTED] Mail Priv: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: IPFW/socheckuid() patch
On 03:18+0200, Feb 18, 2003, Giorgos Keramidas wrote:
On 2003-02-18 00:02, Wiktor Niesiobedzki [EMAIL PROTECTED] wrote:
On Mon, Feb 17, 2003 at 11:47:32PM +0100, Wiktor Niesiobedzki wrote:
There is an obvious mistake in patch (or change in ip_fw2.c should
be considered).
[...]
--- sys/kern/uipc_socket.c 2003/02/17 22:37:58 1.144
+++ sys/kern/uipc_socket.c 2003/02/17 22:56:41
@@ -1846,8 +1846,8 @@
{
if (so == NULL)
- return (EPERM);
- if (so-so_cred-cr_uid == uid)
return (0);
- return (EPERM);
+ if (so-so_cred-cr_uid == uid)
+ return (1);
+ return (0);
}
The rest of the uipc_socket.c functions (socreate, sobind, solisten,
soclose, soabort, ...) that return int's use zero as a success
value, and return errno based errors otherwise. I'm thinking if the
error is ipfw2's fault and should be fixed there. It seems slightly
preferable to me.
Yes, I have already fixed this bug in rev.1.26 src/sys/netinet/ip_fw2.c
--
Maxim Konovalov, [EMAIL PROTECTED], [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: IRDA - ACPI (Battery)
On Tue, Feb 18, 2003 at 09:15:43AM +0100, Pierrick Brossin wrote: Is IRDA now supported by 5.0 ? Can't find any docs. If your IrDA device can emulate a UART you can use ports/comms/birda. What kind of IrDA device do you have in your laptop? Mark -- Mark SantcroosRIPE Network Coordination Centre http://www.ripe.net/home/mark/New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/kern kern_intr.c src/sys/dev/ata ata-all.c
On Fri, Feb 14, 2003 at 05:10:40AM -0800, Alfred Perlstein wrote:
alfred 2003/02/14 05:10:40 PST
Modified files:
sys/kern kern_intr.c
sys/dev/ata ata-all.c
Log:
Fix crash dumps on ata and scsi.
[...]
To fix ata, use what appears to be a polling method if we're dumping,
I stole this from tmm but added code to ensure that this change is
only in effect while dumping.
Tested by: des
FWIW, if I propagate this change to the !dumping case, it also
fixes the ``resume stucks in ata1: resetting devices ..'' bug
I was having with my ThinkPad 600X:
%%%
Index: ata-all.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v
retrieving revision 1.165
diff -u -p -r1.165 ata-all.c
--- ata-all.c 14 Feb 2003 13:10:40 - 1.165
+++ ata-all.c 18 Feb 2003 10:08:22 -
@@ -486,8 +486,7 @@ ata_getparam(struct ata_device *atadev,
/* apparently some devices needs this repeated */
do {
- if (ata_command(atadev, command, 0, 0, 0,
- dumping ? ATA_WAIT_READY : ATA_WAIT_INTR)) {
+ if (ata_command(atadev, command, 0, 0, 0, ATA_WAIT_READY)) {
ata_prtdev(atadev, %s identify failed\n,
command == ATA_C_ATAPI_IDENTIFY ? ATAPI : ATA);
free(ata_parm, M_ATA);
%%%
The resume session (with apm(4)) now looks like this:
: cbb0: PCI Memory allocated: 50103000
: cbb1: PCI Memory allocated: 50102000
: pcm0: detached
: csa: card is Thinkpad 600X/A20/T20
: pcm0: CS461x PCM Audio on csa0
: pcm0: Cirrus Logic CS4297A ac97 codec
: wakeup from sleeping state (slept 00:00:10)
: ata0: resetting devices ..
: done
: ata1: resetting devices ..
: ata1-slave: timeout waiting for cmd=ec s=01 e=24
: ata1-slave: ATA identify failed
: done
: system power profile changed to 'economy'
: cbb1: card inserted: event=0x, state=3920
: cbb1: cbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
: cbb1: cbb_power: CARD_VCC_3V and CARD_VPP_VCC [11]
: cardbus1: Bad header in rom 0: [0]
: cardbus1: Resource not specified in CIS: id=10, size=80
: cardbus1: Resource not specified in CIS: id=14, size=800
: cardbus1: Resource not specified in CIS: id=18, size=800
: cardbus1: Non-prefetchable memory at 8800-88000fff
: cardbus1: Non-prefetchable memory rid=18 at 8800-880007ff (800)
: cardbus1: Non-prefetchable memory rid=14 at 88000800-88000fff (800)
: cardbus1: IO port at 1000-107f
: cardbus1: IO port rid=10 at 1000-107f
: dc0: Xircom X3201 10/100BaseTX port 0x1000-0x107f mem
:0x8800-0x880007ff,0x88000800-0x88000fff irq 11 at device 0.0 on cardbus1
: dc0: Ethernet address: 80:a7:b9:c0:80:fc
: miibus0: MII bus on dc0
: tdkphy0: TDK 78Q2120 media interface on miibus0
: tdkphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
I.e., exactly as it is during the boot-up:
: ata0: at 0x1f0 irq 14 on atapci0
: ata1: at 0x170 irq 15 on atapci0
: ata1-slave: timeout waiting for cmd=ec s=01 e=24
: ata1-slave: ATA identify failed
: ad0: 11509MB IBM-DARA-212000 [24944/15/63] at ata0-master UDMA33
: acd0: DVD-ROM LG DVD-ROM DRN-8080B at ata1-master PIO4
Thankyou!
P.S. The funny thing is that I had the ata(4) crashdumps working. :)
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
[EMAIL PROTECTED] Sunbay Software AG,
[EMAIL PROTECTED] FreeBSD committer,
+380.652.512.251Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
msg52650/pgp0.pgp
Description: PGP signature
RE: NFS server vs YO (very long message)
At 01:43 AM 18/02/03, Erik Torres Serrano sent this up the stick: OK, after the weekend I'm here again. Those are the contents of my configuration files: 1) /etc/exports /localhome -maproot=0beta seems OK, maybe try adding the -alldirs switch /localhome -maproot=0 -alldirs beta 3) /etc/rc.conf hostname=mizar.cigb.edu.cu ifconfig_xl0=DHCP kern_securelevel_enable=NO linux_enable=YES moused_enable=YES moused_type=auto nfs_client_enable=YES nfs_server_enable=YES rpcbind_enable=YES saver=logo sendmail_enable=YES sshd_enable=YES usbd_enable=YES moused_type=auto moused_enable=YES moused_port=/dev/cuaa0 moused_type=auto snip rpc_lockd_enable=YES This is a bit of a mess, try removing all the extra bits you don't need. If you are using DHCP, then make sure the hostnames match up in the dhcpd.conf file on the server as well as /etc/rc.conf I have the following nfs entries in my /etc/rc.conf nfs_server_enable=YES rpcbind_enable=YES rpc_lockd_enable=YES rpc_statd_enable=YES 2) showmount -e mizar Exports list on mizar: So mizar isn't exporting anything . well, anything that can be seen by the client I get 6) mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad0s1d on /localhome (ufs, local, soft-updates) Is this on the server? If so, it should look like: aylee% mount /dev/da0a on / (ufs, NFS exported, local) devfs on /dev (devfs, local) /dev/da0f on /tmp (ufs, local, soft-updates) /dev/da0e on /usr (ufs, NFS exported, local, soft-updates) /dev/da0g on /var (ufs, local, soft-updates) Also: 1) I'm sure I'm mounting as root. 2) As you can see both machines know the route for the other. Does the client have the following in /etc/rc.conf ? nfs_client_enable=YES nfs_client_flags=-n 4 rpc_lockd_enable=YES rpc_statd_enable=YES cheers, Rob -- I'd give my right arm to be ambidextrous. This is random quote 649 of a collection of 1273 Distance from the centre of the brewing universe: [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian Public Key fingerprint = 6219 33BD A37B 368D 29F5 19FB 945D C4D7 1F66 D9C5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
memset prototype changed?
A number of ports have started failing due to an incompatible memset prototype. Did someone recently change this? e.g. http://bento.freebsd.org/errorlogs/i386-5-latest/netatalk-1.6.0_1,1.log Kris msg52652/pgp0.pgp Description: PGP signature
Re: IRDA - ACPI (Battery)
Quoting Mark Santcroos [EMAIL PROTECTED]: If your IrDA device can emulate a UART you can use ports/comms/birda. What kind of IrDA device do you have in your laptop? I have no idea. Where can I check this ? Thx -- Pierrick Brossin IT Swiss - QUARK Media House 6a Puits Godet, 2000 Neuchatel, Switzerland Mail Prof: [EMAIL PROTECTED] Mail Priv: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Shell programming 101: Is this an expr(1) bug ?
Running: #!/bin/sh set -ex for p in ad2 ad0 ad1 do a0=`expr $p : '^ad\([0-9]\)$'` done I get: syv# sh _ + expr ad2 : ^ad\([0-9]\)$ + a0=2 + expr ad0 : ^ad\([0-9]\)$ + a0=0 syv# echo $? 1 syv# That looks like a bug to me... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
New ad*s* devices not automatically appearing in devfs
When I add a new slice or partition to a disk, the device files don't automatically appear in /dev. If I reboot, it shows up, but having to reboot twice just to add a filesystem to a running disk is absurd. How do I make /dev automatically add these devices upon creation? Failing that, how do I force the system to notice the new device(s) and add them to /dev? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New ad*s* devices not automatically appearing in devfs
In message [EMAIL PROTECTED], Darren Pilgrim writes: When I add a new slice or partition to a disk, the device files don't automatically appear in /dev. If I reboot, it shows up, but having to reboot twice just to add a filesystem to a running disk is absurd. How do I make /dev automatically add these devices upon creation? Failing that, how do I force the system to notice the new device(s) and add them to /dev? Which exact commands do you use to create them ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: IRDA - ACPI (Battery)
Pierrick Brossin [EMAIL PROTECTED] writes: Is IRDA now supported by 5.0? No. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: memset prototype changed?
Kris Kennaway [EMAIL PROTECTED] writes: http://bento.freebsd.org/errorlogs/i386-5-latest/netatalk-1.6.0_1,1.log The code that fails to compile is blatantly wrong: memset(schedule, 0, sizeof(schedule)); DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: memset prototype changed?
On Tue, Feb 18, 2003 at 12:01:29PM +0100, Dag-Erling Smorgrav wrote: Kris Kennaway [EMAIL PROTECTED] writes: http://bento.freebsd.org/errorlogs/i386-5-latest/netatalk-1.6.0_1,1.log The code that fails to compile is blatantly wrong: memset(schedule, 0, sizeof(schedule)); I think this is due to the openssl upgrade. DES_key_schedule was an array but is now a struct. You would have to something like this to make it work now: memset(schedule, 0, sizeof(schedule)); -Richard To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: IRDA - ACPI (Battery)
: Since APCI is now used instead of APM, I'm wondering if we have to wait/program : softwares to control the battery status ? I use the apm command :-). The acpi code provides enough of the apm API to allow apm and apmd to work. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Shell programming 101: Is this an expr(1) bug ?
On Tue, 2003-02-18 at 06:39, Poul-Henning Kamp wrote: + expr ad0 : ^ad\([0-9]\)$ + a0=0 syv# echo $? 1 syv# That looks like a bug to me... hilfy:202 Z$ /bin/expr ad0 : '^ad\([0-9]\)$' 0 zsh: exit 1 /bin/expr ad0 : '^ad\([0-9]\)$' (Solaris 8 box) The Solaris manpage claims: EXIT STATUS As a side effect of expression evaluation, expr returns the following exit values: (...) 1 if the expression is either NULL or 0 So it looks like correct behavior, if slightly odd in this particular context. -- brandon s allbery [openafs/solaris/japh/freebsd] [EMAIL PROTECTED] system administrator [linux/heimdal/too many hats] [EMAIL PROTECTED] electrical and computer engineering KF8NH carnegie mellon university [better check the oblivious first -ke6sls] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Shell programming 101: Is this an expr(1) bug ?
On Tue, Feb 18, 2003 at 12:39:22PM +0100, Poul-Henning Kamp wrote: Running: #!/bin/sh set -ex for p in ad2 ad0 ad1 do a0=`expr $p : '^ad\([0-9]\)$'` done I get: syv# sh _ + expr ad2 : ^ad\([0-9]\)$ + a0=2 + expr ad0 : ^ad\([0-9]\)$ + a0=0 syv# echo $? 1 syv# That looks like a bug to me... Confusing but documented behaviour: 1. expr ad0 : ad\([0-9]\) = expr 0 man expr If the match succeeds and the pattern contains at least one regu- lar expression subexpression ``\(...\)'', the string correspond- ing to ``\1'' is returned; otherwise the matching operator 2. `expr 0` = exit status = 1 man expr The expr utility exits with one of the following values: 0 the expression is neither an empty string nor 0. 1 the expression is an empty string or 0. This behaviour is the same on linux, *BSD and probably other systems too. Regards Adi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: memset prototype changed?
On Tue, Feb 18, 2003 at 12:01:29PM +0100, Dag-Erling Smorgrav wrote: Kris Kennaway [EMAIL PROTECTED] writes: http://bento.freebsd.org/errorlogs/i386-5-latest/netatalk-1.6.0_1,1.log The code that fails to compile is blatantly wrong: memset(schedule, 0, sizeof(schedule)); I wouldn't say `blantantly'. The expressions `schedule' and `schedule' are equivalent when `schedule' is an array type. I'd call it `ignoring an idiom'. Anyway, with libdes or OpenSSL 0.9.7, the type of `schedule' would have been an array. With OpenSSL = 0.9.7, the type of `schedule' is a struct. This port uses des.h, which we have as a symlink to openssl/des.h (ugh, I'd better remove that, too). If that include is replaced with e.g. #ifdef HAVE_OPENSSL #define OPENSSL_DES_LIBDES_COMPATIBILITY #include openssl/des.h #else #include des.h #endif things will be fine. -- Jacques A. Vidrine [EMAIL PROTECTED] http://www.celabo.org/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /dev/smb where are you?
Hi! This doesn't change anything here :-(! Thanks, Christian. On Tuesday, 18. February 2003 00:33, David Vidal Rodríguez wrote: Christian Gusenbauer wrote: Hello! Using a kernel from last friday, I'm not able to get /dev/smb working. I've added these options to my kernel config: device smbus device intpm device alpm device ichsmb device viapm device amdpm device nfpm device smb Maybe you need the following line in your /boot/device.hints: hint.smb.0.at=smbus I figured that out from my 4.x config file (device smb0 at smbus? in MYKERNEL). Good luck! David. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Shell programming 101: Is this an expr(1) bug ?
Running: #!/bin/sh set -ex for p in ad2 ad0 ad1 do a0=`expr $p : '^ad\([0-9]\)$'` done I get: syv# sh _ + expr ad2 : ^ad\([0-9]\)$ + a0=2 + expr ad0 : ^ad\([0-9]\)$ + a0=0 syv# echo $? 1 The `set -e' says to exit the shell if a simple command fails. POSIX.2 says that the exit status of an assignment statement without an accompanying command is either 0 or the exit status of the last command substitution performed while expanding the rhs. `expr' returns 1 when the result is `0'. Thus the assignment statement fails and the shell exits. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI thermal panics ThinkPad 600X
Tom Rhodes [EMAIL PROTECTED] wrote: ACPI gives me hell on my IBM Thinkpad A31, also. Yet since it does not crash anything I just leave it be waiting for the day when the ACPI hackers have time to fix it :) It may not necessarily be a FreeBSD problem (or, not only). While there may be issues with FreeBSD's ACPI, there are definitely issues with the A31 BIOS: http://sourceforge.net/mailarchive/message.php?msg_id=3597168 -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
multithreaded binaries dump core in linux emulation
I'm using a very recent FreeBSD-current ( ~ 4 days ago ). Since I upgraded my linux installation to RH 8.0 ( ~ 2 months ), I'm not able to run multithreaded binaries under linux emulation any more. ( I hope you understand me - I don't want to install another set of native mozilla, ooffice and other bloats :-) ). That mean: glibc 2.2.93 linuxthreads 0.10 They used to work fine with older glibc - and no significant change has occurred since then in the linux emulation code. I cannot test with other system since I don't have either an older glibc stuff or an older FreeBSD at hand. Is anyone else aware of this problem or should I try to investigate it myself ? Thanks Regards Adi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kern/48381: using mv(1) on smbfs crashes 5.0 kernel
On Mon, Feb 17, 2003 at 10:45:32PM +0800, Thomas E. Zander wrote:
I can reproduce it on my system.
FreeBSD 5.0-CURRENT #0: Tue Feb 18 18:43:57 MSK 2003
Description:
On a mounted network-filesystem using mount_smbfs, using of the command
mv /file/on/the/smbfs /file/on/a/local/fs
freezes the system for about 10 seconds, then immidiate reboot.
No kernel panic is shown, no dump, also no chance to backtrace the problem.
Instead using of cp rm is flawless.
How-To-Repeat:
Just take a 5.0-R and use mv(1) on a smbfs
Fix:
Since I wasn't able to do a trace or gdb -k after the crash, it is difficult to give
an idea of how to fix it.
Sorry.
Release-Note:
Audit-Trail:
%gdb -k kernel.debug /usr/crash/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: bwrite: buffer is not busy???
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xe0
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc027b9f4
stack pointer = 0x10:0xcdcb5774
frame pointer = 0x10:0xcdcb57e4
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 = 616 (mv)
trap number = 12
panic: page fault
syncing disks, buffers remaining... panic: bwrite: buffer is not busy???
Uptime: 2m7s
Dumping 255 MB
ata0: resetting devices ..
ata0: mask=03 ostat0=50 ostat2=00
ad0: ATAPI 00 00
ata0-slave: ATAPI 00 00
ata0: mask=03 stat0=50 stat1=00
ad0: ATA 01 a5
ata0: devices=01
ad0: success setting PIO4 on generic chip
done
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
---
#0 doadump () at ../../../kern/kern_shutdown.c:239
239 dumping++;
(kgdb) bt
#0 doadump () at ../../../kern/kern_shutdown.c:239
#1 0xc01dc5d9 in boot (howto=260) at ../../../kern/kern_shutdown.c:371
#2 0xc01dc843 in panic () at ../../../kern/kern_shutdown.c:542
#3 0xc02204d2 in bwrite (bp=0xc7729880) at ../../../kern/vfs_bio.c:842
#4 0xc0221c91 in vfs_bio_awrite (bp=0xc7729880) at ../../../kern/vfs_bio.c:1724
#5 0xc0229627 in vop_stdfsync (ap=0xcdcb556c) at ../../../kern/vfs_default.c:755
#6 0xc01a56e0 in spec_fsync (ap=0xcdcb556c) at ../../../fs/specfs/spec_vnops.c:422
#7 0xc01a4bb8 in spec_vnoperate (ap=0x0) at ../../../fs/specfs/spec_vnops.c:123
#8 0xc0293ee7 in ffs_sync (mp=0xc25ac200, waitfor=2, cred=0xc0eb2f00, td=0xc03563c0)
at vnode_if.h:612
#9 0xc0236e4b in sync (td=0xc03563c0, uap=0x0) at ../../../kern/vfs_syscalls.c:138
#10 0xc01dc1bc in boot (howto=256) at ../../../kern/kern_shutdown.c:280
#11 0xc01dc843 in panic () at ../../../kern/kern_shutdown.c:542
#12 0xc02f1152 in trap_fatal (frame=0xcdcb5734, eva=0) at ../../../i386/i386/trap.c:844
#13 0xc02f0e32 in trap_pfault (frame=0xcdcb5734, usermode=0, eva=224)
at ../../../i386/i386/trap.c:758
#14 0xc02f0920 in trap (frame=
{tf_fs = -1070596072, tf_es = 327696, tf_ds = 16, tf_edi = 0, tf_esi = 24,
tf_ebp = -842311708, tf_isp = -842311840, tf_ebx = -934060032, tf_edx = -1029007968,
tf_ecx = -934059330, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071138316,
tf_cs = 8, tf_eflags = 66118, tf_esp = 255, tf_ss = 2765}) at
../../../i386/i386/trap.c:445
#15 0xc02e0ad8 in calltrap () at {standard input}:96
#16 0xc027a86a in ffs_hashalloc (ip=0xc2aa95a0, cg=-934060032, pref=0, size=32768,
allocator=0xc027b720 ffs_nodealloccg) at ../../../ufs/ffs/ffs_alloc.c:1154
#17 0xc0279f9e in ffs_valloc (pvp=0xc2aab000, mode=32768, cred=0xc2b9d400,
vpp=0xcdcb5878)
at ../../../ufs/ffs/ffs_alloc.c:856
#18 0xc02a1f6c in ufs_makeinode (mode=32768, dvp=0xc2aab000, vpp=0xcdcb5be0,
cnp=0xcdcb5bf4)
at ../../../ufs/ufs/ufs_vnops.c:2356
#19 0xc029ec09 in ufs_create (ap=0xcdcb5a10) at ../../../ufs/ufs/ufs_vnops.c:197
#20 0xc02a24e8 in ufs_vnoperate (ap=0x0) at ../../../ufs/ufs/ufs_vnops.c:2787
#21 0xc023e60f in vn_open_cred (ndp=0xcdcb5bcc, flagp=0xcdcb5ccc, cmode=0,
cred=0xc2b9d400)
at vnode_if.h:114
#22 0xc023e469 in vn_open (ndp=0x0, flagp=0x0, cmode=0) at ../../../kern/vfs_vnops.c:86
#23 0xc0237c98 in kern_open (td=0xc25a94b0, path=0x0, pathseg=UIO_USERSPACE,
flags=3586, mode=0)
at ../../../kern/vfs_syscalls.c:663
#24 0xc0237b30 in open (td=0x0, uap=0x0) at ../../../kern/vfs_syscalls.c:628
#25 0xc02f147a in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077938544, tf_esi = -1077938544,
tf_ebp = -1077940040, tf_isp = -842310284, tf_ebx = -107794, tf_edx = -1077938704,
tf_ecx = 0, tf_eax = 5, tf_trapno = 12, tf_err = 2, tf_eip = 134520703, tf_cs
WaveLAN problems
Hi, I have a Netgear MA401 PCCard. The system recognizes the card, but after typeing ... bash-2.05a# wicontrol NIC serial number: [ ] Station name: [ FreeBSD WaveL ] SSID for IBSS creation: [ ] Current netname (SSID): [ ] Desired netname (SSID): [ ] Current BSSID: [ 00:00:00:00:00:00 ] Channel list: [ 1fff ] IBSS channel: [ 3 ] Current channel:[ 0 ] Comms quality/signal/noise: [ 0 0 0 ] wicontrol: SIOCGWAVELAN: Invalid argument here's the dmesg output: module_register_init: MOD_LOAD (logo_saver, 0xc2630c80, 0) error 19 wi0: Netgear MA401RA at port 0x100-0x13f irq 9 function 0 config 1 on pccard0 wi0: 802.11 address: 00:09:5b:34:f8:ae wi0: using RF:PRISM2.5 MAC:ISL3873 wi0: Intersil Firmware: Primary (1.0.7), Station (1.3.6) wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps I'm running FreeBSD-Current of today, bye, -- --- - Michael Bretterklieber- [EMAIL PROTECTED] JAWA Management Software GmbH - http://www.jawa.at Liebenauer Hauptstr. 200-- privat --- A-8041 GRAZ GSM: ++43-(0)676-93 96 698 Tel: ++43-(0)316-403274-12 E-mail: [EMAIL PROTECTED] Fax: ++43-(0)316-403274-10 http://www.bretterklieber.com --- - ...the number of UNIX installations has grown to 10, with more expected... - Dennis Ritchie and Ken Thompson, June 1972 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: memset prototype changed?
On Tue, Feb 18, 2003 at 10:10:41AM -0800, Kris Kennaway wrote:
On Tue, Feb 18, 2003 at 12:47:35PM +0100, Richard Nyberg wrote:
On Tue, Feb 18, 2003 at 12:01:29PM +0100, Dag-Erling Smorgrav wrote:
Kris Kennaway [EMAIL PROTECTED] writes:
http://bento.freebsd.org/errorlogs/i386-5-latest/netatalk-1.6.0_1,1.log
The code that fails to compile is blatantly wrong:
memset(schedule, 0, sizeof(schedule));
I think this is due to the openssl upgrade.
DES_key_schedule was an array but is now a struct.
You would have to something like this to make it work now:
memset(schedule, 0, sizeof(schedule));
Could you please submit a patch to the maintainer?
Actually, this works since the port does -I/usr/include/openssl:
Index: Makefile
===
RCS file: /home/ncvs/ports/net/netatalk/Makefile,v
retrieving revision 1.48
diff -c -c -r1.48 Makefile
*** Makefile5 Jan 2003 23:42:00 - 1.48
--- Makefile18 Feb 2003 18:39:46 -
***
*** 23,28
--- 23,29
.endif
USE_BZIP2=yes
+ CONFIGURE_ENV+= CPPFLAGS=-DOPENSSL_DES_LIBDES_COMPATIBILITY
CONFIGURE_ARGS+= --with-tcp-wrappers \
--with-pkgconfdir=${PREFIX}/etc
.if defined(WITH_PAM)
(MAINTAINER cc'd)
Cheers,
--
Jacques A. Vidrine [EMAIL PROTECTED] http://www.celabo.org/
NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos
[EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: memset prototype changed?
On Tue, Feb 18, 2003 at 12:47:35PM +0100, Richard Nyberg wrote: On Tue, Feb 18, 2003 at 12:01:29PM +0100, Dag-Erling Smorgrav wrote: Kris Kennaway [EMAIL PROTECTED] writes: http://bento.freebsd.org/errorlogs/i386-5-latest/netatalk-1.6.0_1,1.log The code that fails to compile is blatantly wrong: memset(schedule, 0, sizeof(schedule)); I think this is due to the openssl upgrade. DES_key_schedule was an array but is now a struct. You would have to something like this to make it work now: memset(schedule, 0, sizeof(schedule)); Could you please submit a patch to the maintainer? Kris msg52671/pgp0.pgp Description: PGP signature
Re: memset prototype changed?
Jacques A. Vidrine [EMAIL PROTECTED] writes: On Tue, Feb 18, 2003 at 12:01:29PM +0100, Dag-Erling Smorgrav wrote: The code that fails to compile is blatantly wrong: memset(schedule, 0, sizeof(schedule)); I wouldn't say `blantantly'. The expressions `schedule' and `schedule' are equivalent when `schedule' is an array type. ...but Key_schedule is an opaque type, so it is not correct to assume it's an array. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New ad*s* devices not automatically appearing in devfs
[EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Darren Pilgrim writes: When I add a new slice or partition to a disk, the device files don't automatically appear in /dev. If I reboot, it shows up, but having to reboot twice just to add a filesystem to a running disk is absurd. How do I make /dev automatically add these devices upon creation? Failing that, how do I force the system to notice the new device(s) and add them to /dev? Which exact commands do you use to create them ? I used sysinstall, Configure-Fdisk to (in order) delete s3, create a 5120m s2, then Write the changes to disk. After exiting sysinstall: # fdisk ad4 *** Working on device /dev/ad4 *** parameters extracted from in-core disklabel are: cylinders=39714 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=39714 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 10485153 (5119 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 15/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 10485216, size 10485216 (5119 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 15/ sector 63 The data for partition 3 is: UNUSED The data for partition 4 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 30967776, size 9063936 (4425 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 15/ sector 63 # disklabel ad2s2 disklabel: /dev/ad2s2: No such file or directory # disklabel -r ad2s2 disklabel: /dev/ad2s2: No such file or directory # disklabel -w ad4s2 auto disklabel: /dev/ad4s2: No such file or directory Going back into sysinstall, the fdisk screen shows the old slice table, and the label screen shows s1, s3, and s4, but no s2. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New ad*s* devices not automatically appearing in devfs
In message [EMAIL PROTECTED], Darren Pilgrim writes: [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Darren Pilgrim writes: When I add a new slice or partition to a disk, the device files don't automatically appear in /dev. If I reboot, it shows up, but having to reboot twice just to add a filesystem to a running disk is absurd. How do I make /dev automatically add these devices upon creation? Failing that, how do I force the system to notice the new device(s) and add them to /dev? Which exact commands do you use to create them ? I used sysinstall, Configure-Fdisk to (in order) delete s3, create a 5120m s2, then Write the changes to disk. After exiting sysinstall: But the changes do appear after you reboot ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New ad*s* devices not automatically appearing in devfs
[EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Darren Pilgrim writes: [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Darren Pilgrim writes: When I add a new slice or partition to a disk, the device files don't automatically appear in /dev. If I reboot, it shows up, but having to reboot twice just to add a filesystem to a running disk is absurd. How do I make /dev automatically add these devices upon creation? Failing that, how do I force the system to notice the new device(s) and add them to /dev? Which exact commands do you use to create them ? I used sysinstall, Configure-Fdisk to (in order) delete s3, create a 5120m s2, then Write the changes to disk. After exiting sysinstall: But the changes do appear after you reboot ? Yes, after rebooting a /dev/ad4s2 is present. I can then issue `disklabel -w ad4s2 auto` to intialize the slice with an appropriate empty label. I can use `disklabel -e ad4s2` or sysinstall to create the partitions. Sysinstall will complain about the lack of partition devices but write the label out anyway. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Drive Resetting
I just installed a new maxtor drive on a 200Mhz Compaq Deskpro running 5.0 setup went normally (no errors) fsck showed no errors. However, I am now getting the following under heavy disk activity: Feb 18 12:32:46 stargate kernel: ad2: WRITE command timeout tag=0 serv=0 - reset ting Feb 18 12:32:46 stargate kernel: ata1: resetting devices .. Feb 18 12:32:46 stargate kernel: done Anyone have any suggestions on how to fix this? Its happens frequently, especially during compiles. Beech --- Beech Rintoul - Network Administrator - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | X - NO Word docs in e-mail | Anchorage, AK 99518-1841 No More Spam! http://www.knockmail.com/default.asp?AID=B0R00073 / \ - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI thermal panics ThinkPad 600X
Darryl Okahata wrote: Tom Rhodes [EMAIL PROTECTED] wrote: ACPI gives me hell on my IBM Thinkpad A31, also. Yet since it does not crash anything I just leave it be waiting for the day when the ACPI hackers have time to fix it :) It may not necessarily be a FreeBSD problem (or, not only). While there may be issues with FreeBSD's ACPI, there are definitely issues with the A31 BIOS: http://sourceforge.net/mailarchive/message.php?msg_id=3597168 A more useful reference, I think, is: http://sourceforge.net/mailarchive/message.php?msg_id=3597172 If you add similar code to FreeBSD to detect and patch the BIOS table, this fixes the problem in FreeBSD, as well (though adding the code is somewhat tricky: YMMV, knowledge of both FreeBSD and Linux required; sorry, I do not have a patch against -current). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Drive Resetting
What kind of IDE cable are you using (40 or 80-conductor)? You might try a new cable. Do you know which UDMA mode the ata driver is running in? Have you tried turning off DMA and/or write-caching? (I think you can use sysctl to do this.) -Original Message- From: Beech Rintoul [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 18, 2003 3:53 PM To: [EMAIL PROTECTED] Subject: Drive Resetting I just installed a new maxtor drive on a 200Mhz Compaq Deskpro running 5.0 setup went normally (no errors) fsck showed no errors. However, I am now getting the following under heavy disk activity: Feb 18 12:32:46 stargate kernel: ad2: WRITE command timeout tag=0 serv=0 - reset ting Feb 18 12:32:46 stargate kernel: ata1: resetting devices .. Feb 18 12:32:46 stargate kernel: done Anyone have any suggestions on how to fix this? Its happens frequently, especially during compiles. Beech --- Beech Rintoul - Network Administrator - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | X - NO Word docs in e-mail | Anchorage, AK 99518-1841 No More Spam! http://www.knockmail.com/default.asp?AID=B0R00073 / \ - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic starting gnome
Hi, on today's -current, I get the following panic when starting gnome from xdm; a kernel from 2/10 works with today's world, so it must be something in the kernel that changed over the last week: Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = fault virtual address = 0x34 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01b28a6 stack pointer = 0x10:0xe91a57c0 frame pointer = 0x10:0xe91a57e0 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 = 2444 (gconf-sanity-check-) kernel: type 12 trap, code=0 Stopped at _mtx_lock_flags+0x26: cmpl$0xc03884a0,0(%esi) db mi_switch(c21b4980,0,c0354624,185,3f8) at mi_switch+0x240 ithread_schedule(c6283b80,1,c0305e16,c658e780,e91a55c0) at ithread_schedule+0x11c sched_ithd(d) at sched_ithd+0x41 Xintr13() at Xintr13+0xd3 --- interrupt, eip = 0xc02efea2, esp = 0xe91a55a4, ebp = 0xe91a55c0 --- siocnopen(e91a55d4,3f8,1c200,301,c01f040b) at siocnopen+0x12 siocncheckc(c03b4c80,78,e91a5608,c01f0358,e91a5624) at siocncheckc+0x40 cncheckc(e91a5624,c0149625,e91a57c8,c03a9ac8,e91a5634) at cncheckc+0x2c cngetc(e91a57c8,c03a9ac8,e91a5634,0,e91a57c8) at cngetc+0x18 db_readline(c03b1b80,78,e91a5658,c01481e6,c03499fb) at db_readline+0x65 db_read_line(c03499fb,c03a9ac8,e91a5658,c0148a28,0) at db_read_line+0x1a db_command_loop(c01b28a6,a0,0,e91a5680,0) at db_command_loop+0x46 db_trap(c,0,0,e91a56c0,5) at db_trap+0x66 kdb_trap(c,0,e91a5780,1,1) at kdb_trap+0x107 trap_fatal(e91a5780,34,c0372ee0,2e4,c658e780) at trap_fatal+0x250 trap_pfault(e91a5780,0,34,c03e0758,34) at trap_pfault+0x17a trap(c21a0018,10,c0360010,9e,34) at trap+0x3e5 calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc01b28a6, esp = 0xe91a57c0, ebp = 0xe91a57e0 --- _mtx_lock_flags(34,0,c035cf5f,9e,c658e780) at _mtx_lock_flags+0x26 namei(e91a5a44,c0207d5a,c749458c,0,c658e780) at namei+0x134 vn_open_cred(e91a5a44,e91a5a0c,0,c2195e80,0) at vn_open_cred+0x53c nfs_dolock(e91a5c0c,c658e780,1b3,c03e0748,6001) at nfs_dolock+0x294 closef(c6673834,c658e780,c0353f03,595,c7375934) at closef+0x123 fdfree(c658e780,0,c03543ab,f2,73) at fdfree+0x1d4 exit1(c658e780,0,c03543ab,73,e91a5d40) at exit1+0x282 sys_exit(c658e780,e91a5d10,c0372ee0,407,c658de4c) at sys_exit+0x41 syscall(2f,2f,2f,0,2b57) at syscall+0x3d6 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (1), eip = 0x288a853f, esp = 0xbfbffbec, ebp = 0xbfbffc18 --- Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
Re: ACPI thermal panics ThinkPad 600X
Terry Lambert [EMAIL PROTECTED] wrote: A more useful reference, I think, is: http://sourceforge.net/mailarchive/message.php?msg_id=3597172 If you add similar code to FreeBSD to detect and patch the BIOS table, this fixes the problem in FreeBSD, as well (though adding the code is somewhat tricky: YMMV, knowledge of both FreeBSD and Linux required; sorry, I do not have a patch against -current). Yah, I think the correct/updated version is at: http://www.poupinou.org/acpi/ibm_ecdt.html However, I think I'll pray and wait for an IBM BIOS fix. I'm not yet that desperate. ;-( In the meantime, I'll muddle through with apm. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic starting gnome
FWIW, this looks nearly identical to the panic I reported last night in the thread VFS panic (possibly NFS locking related?). I didn't manage to catch the ddb trace and had to work postmortem with a crash dump and gdb. But it looked just like here. Lars: Do you by any chance have your home directory on an NFS mount? I think the reason that my gdb trace showed ?? instead of nfs_dolock is that I have nfsclient loaded as a module... Craig On Tue, 2003-02-18 at 17:00, Lars Eggert wrote: Hi, on today's -current, I get the following panic when starting gnome from xdm; a kernel from 2/10 works with today's world, so it must be something in the kernel that changed over the last week: Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = fault virtual address = 0x34 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01b28a6 stack pointer = 0x10:0xe91a57c0 frame pointer = 0x10:0xe91a57e0 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 = 2444 (gconf-sanity-check-) kernel: type 12 trap, code=0 Stopped at _mtx_lock_flags+0x26: cmpl$0xc03884a0,0(%esi) db mi_switch(c21b4980,0,c0354624,185,3f8) at mi_switch+0x240 ithread_schedule(c6283b80,1,c0305e16,c658e780,e91a55c0) at ithread_schedule+0x11c sched_ithd(d) at sched_ithd+0x41 Xintr13() at Xintr13+0xd3 --- interrupt, eip = 0xc02efea2, esp = 0xe91a55a4, ebp = 0xe91a55c0 --- siocnopen(e91a55d4,3f8,1c200,301,c01f040b) at siocnopen+0x12 siocncheckc(c03b4c80,78,e91a5608,c01f0358,e91a5624) at siocncheckc+0x40 cncheckc(e91a5624,c0149625,e91a57c8,c03a9ac8,e91a5634) at cncheckc+0x2c cngetc(e91a57c8,c03a9ac8,e91a5634,0,e91a57c8) at cngetc+0x18 db_readline(c03b1b80,78,e91a5658,c01481e6,c03499fb) at db_readline+0x65 db_read_line(c03499fb,c03a9ac8,e91a5658,c0148a28,0) at db_read_line+0x1a db_command_loop(c01b28a6,a0,0,e91a5680,0) at db_command_loop+0x46 db_trap(c,0,0,e91a56c0,5) at db_trap+0x66 kdb_trap(c,0,e91a5780,1,1) at kdb_trap+0x107 trap_fatal(e91a5780,34,c0372ee0,2e4,c658e780) at trap_fatal+0x250 trap_pfault(e91a5780,0,34,c03e0758,34) at trap_pfault+0x17a trap(c21a0018,10,c0360010,9e,34) at trap+0x3e5 calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc01b28a6, esp = 0xe91a57c0, ebp = 0xe91a57e0 --- _mtx_lock_flags(34,0,c035cf5f,9e,c658e780) at _mtx_lock_flags+0x26 namei(e91a5a44,c0207d5a,c749458c,0,c658e780) at namei+0x134 vn_open_cred(e91a5a44,e91a5a0c,0,c2195e80,0) at vn_open_cred+0x53c nfs_dolock(e91a5c0c,c658e780,1b3,c03e0748,6001) at nfs_dolock+0x294 closef(c6673834,c658e780,c0353f03,595,c7375934) at closef+0x123 fdfree(c658e780,0,c03543ab,f2,73) at fdfree+0x1d4 exit1(c658e780,0,c03543ab,73,e91a5d40) at exit1+0x282 sys_exit(c658e780,e91a5d10,c0372ee0,407,c658de4c) at sys_exit+0x41 syscall(2f,2f,2f,0,2b57) at syscall+0x3d6 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (1), eip = 0x288a853f, esp = 0xbfbffbec, ebp = 0xbfbffc18 --- Lars To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/kern kern_intr.c src/sys/dev/ata ata-all.c
On Tue, 18 Feb 2003, Ruslan Ermilov wrote:
On Fri, Feb 14, 2003 at 05:10:40AM -0800, Alfred Perlstein wrote:
alfred 2003/02/14 05:10:40 PST
Modified files:
sys/kern kern_intr.c
sys/dev/ata ata-all.c
Log:
Fix crash dumps on ata and scsi.
[...]
To fix ata, use what appears to be a polling method if we're dumping,
I stole this from tmm but added code to ensure that this change is
only in effect while dumping.
Tested by: des
FWIW, if I propagate this change to the !dumping case, it also
fixes the ``resume stucks in ata1: resetting devices ..'' bug
I was having with my ThinkPad 600X:
%%%
Index: ata-all.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v
retrieving revision 1.165
diff -u -p -r1.165 ata-all.c
--- ata-all.c 14 Feb 2003 13:10:40 - 1.165
+++ ata-all.c 18 Feb 2003 10:08:22 -
@@ -486,8 +486,7 @@ ata_getparam(struct ata_device *atadev,
/* apparently some devices needs this repeated */
do {
- if (ata_command(atadev, command, 0, 0, 0,
- dumping ? ATA_WAIT_READY : ATA_WAIT_INTR)) {
+ if (ata_command(atadev, command, 0, 0, 0, ATA_WAIT_READY)) {
ata_prtdev(atadev, %s identify failed\n,
command == ATA_C_ATAPI_IDENTIFY ? ATAPI : ATA);
free(ata_parm, M_ATA);
%%%
There is, or was, something near here that made the whole system go
unresponsive (as seen by nfs clients) for several seconds. I guess
the main problem was just using polled mode in all cases here. In
RELENG_4, polling is done at splbio() so normally only disk devices
are blocked, but under -current almost everything is blocked by Giant.
The resume session (with apm(4)) now looks like this:
: cbb0: PCI Memory allocated: 50103000
: cbb1: PCI Memory allocated: 50102000
: pcm0: detached
: csa: card is Thinkpad 600X/A20/T20
: pcm0: CS461x PCM Audio on csa0
: pcm0: Cirrus Logic CS4297A ac97 codec
: wakeup from sleeping state (slept 00:00:10)
: ata0: resetting devices ..
: done
: ata1: resetting devices ..
: ata1-slave: timeout waiting for cmd=ec s=01 e=24
: ata1-slave: ATA identify failed
: done
Apparently the timeout is too short or the interrupt got lost. The
timeout seems to be too short. It is 10 seconds, but IIRC the spec
is says 30 seconds for reset of the master and a bit more for the
slave. Since things work with polling, we know that the device state
changed properly. We could test for this state change instead of
always aborting after the timeout, and do finer grained and more sleeps
to determine the precise timeout required.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: panic starting gnome
Craig Boston wrote: FWIW, this looks nearly identical to the panic I reported last night in the thread VFS panic (possibly NFS locking related?). I missed your message, just read it: yes, that sounds similar. I didn't manage to catch the ddb trace and had to work postmortem with a crash dump and gdb. But it looked just like here. Lars: Do you by any chance have your home directory on an NFS mount? Yes, I do. I think the reason that my gdb trace showed ?? instead of nfs_dolock is that I have nfsclient loaded as a module... Mine's loaded as a module, too. Lars -- Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute smime.p7s Description: S/MIME Cryptographic Signature
background fsck deadlocks with ufs2 and big disk
Hi all, I just wanted to tell that I can deadlock one of my current boxes with a ufs2 filesystem on a 120GB ATA disk. I can reproduce the problem. The background fsck process hangs some time at the same place always at the same place, sometimes the box freezes after some time. The same box works fine with ufs1. Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: finger -l [EMAIL PROTECTED] PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/lib/libc/stdlib rand.c
On Sun, Feb 16, 2003 at 22:08:10 -0800, Kris Kennaway wrote: when they should not. I've given examples of two of them, and there are probably lots of others I haven't noticed. For example, I just checked, and libICE appears to use rand() for cookie generation. This is completely bogus, and insecure. Usually applications we build (like awk, etc.) could be fixed by simple one line change: srand(something) - sranddev() It completely eliminates first value correlation problem. -- Andrey A. Chernov http://ache.pp.ru/ msg52685/pgp0.pgp Description: PGP signature
Diskless: 5.0R scripts, boot, NFS mount problems I didn't have in 4.7S
I was running a VIA Mini-ITX diskless box off a 4.7-STABLE box for a while using a root fs created by the clone_root discussed in the handbook, then some tweaks. I'm having a heck of a time trying to get this running under 5.0-RELEASE, now sync'd to 5.0-CURRENT as of yesterday, then mergemastered. If someone can provide some clues or pointers, I'd be happy to doc how I get it to work (for the Handbook?) and could take a stab at updating clone_root for 5.x if it's needed. Background: Been using FreeBSD since 2.2.x. I can code. I can RTFM. :-) I've read the 5.0 Release Notes and Early Adopters docs. I've read Handbook section 19.6 Diskless Operation and it covers the DHCP, PXE, TFTP, and NFS OK but glosses over how the diskless box actually boots -- what scripts it runs and such. That's where I'm stuck. How does a diskless box know to run a diskless boot script (rather than a standard one)? I'm assuming it invokes init which runs /etc/rc, which then runs /etc/rc.d/* in the 5.0 model. Am I close? I've read Handbook 7.6 Init but it doesn't actually say much about how init hands off to the rc* scripts. The man for rc(8) seems to document the 5.0 rc.d/* well so I'll revisit my diskless boot process. Here's what I have working so far: * isc-dhcpd: offers hostname, IP, location of boot image, root filesystem location * tftpboot: offers pxeboot * pxeboot: gets and runs kernel, mounts root filesystem Then it begins the init/rc startup process and eventually dies. Here's what I've found broken or I can't get past: The clone_root assumes it's copying all the files it needs but (for example) mtree now lives in /usr/sbin instead of /sbin, so it's not copied to the diskless root area so it's not available. kenv lives in /usr/bin, but /usr isn't mounted before kenv is used in rc.diskless1. clone_root wants to run /dev/MAKEDEV but that file doesn't exist in my 5.0 /dev/; I see it in /usr/src/etc/ but it wasn't install by make installworld or mergemaster. (Is this a glitch?) The rc.diskless[12] scripts have changed significantly from 4.7 to 5.0. Are they even used with the new /etc/rc.d/* mechanism? I've run clone_root then manually installed a DISKLESS kernel file into the new location ($DISKLESSROOT)/boot/kernel/kernel. I've manually populated $DISKLESSROOT/conf/default/etc/ with an NFS-oriented fstab, rc.conf, rc.diskless*, and rc.d/[init]diskless and password-related files. Upon boot, after kernel loaded, console shows a bunch of rc.conf-style vars being set, then spews some debugging which I put in $DISKLESSROOT/conf/default/etc/rc.d/diskless, so it's running that rather than the old /etc/rc.diskless* files. I've moved the mount -a near the top of rc.d/diskless since it runs commands which are and not available until /usr is mounted (e.g., mtree). The NFS mount fails with a message I don't understand: [udp] pectopah.shenton.org:/usr: RPCPROG_NFS: RPC: Unknown host This occurs whether I specify a bare hostname, fqdn or IP addr in fstab, even if I put host info in $DISKLESSROOT/conf/default/etc/. Is it really complaining about hosts? or is it an rcpbind thing? Note that it has already mounted the root filesystem a while back. Since it can't mount /usr, everything else fails. Can someone point me in the right direction ? Thanks! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: multithreaded binaries dump core in linux emulation
Linux has changed their threading ans is adding some threading 'support' into the kernel. It is unlikely that our emulation supports that support yet. it would certainly be nice to know what they are doing.. On Tue, 18 Feb 2003, Enache Adrian wrote: I'm using a very recent FreeBSD-current ( ~ 4 days ago ). Since I upgraded my linux installation to RH 8.0 ( ~ 2 months ), I'm not able to run multithreaded binaries under linux emulation any more. ( I hope you understand me - I don't want to install another set of native mozilla, ooffice and other bloats :-) ). That mean: glibc 2.2.93 linuxthreads 0.10 They used to work fine with older glibc - and no significant change has occurred since then in the linux emulation code. I cannot test with other system since I don't have either an older glibc stuff or an older FreeBSD at hand. Is anyone else aware of this problem or should I try to investigate it myself ? Thanks Regards Adi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Diskless: 5.0R scripts, boot, NFS mount problems I didn't have in 4.7S
Chris Shenton [EMAIL PROTECTED] writes:
I've moved the mount -a near the top of rc.d/diskless since it
runs commands which are and not available until /usr is mounted
(e.g., mtree). The NFS mount fails with a message I don't
understand:
[udp] pectopah.shenton.org:/usr: RPCPROG_NFS: RPC: Unknown host
Tasteless self-followup:
I get the same error when the boot process fails and drops me to a
shell; I can get it with UDP or TCP mounts. For example:
mount_nfs -U -2 192.168.255.185:/usr /mnt
mount_nfs -U -3 192.168.255.185:/usr /mnt
mount_nfs -T -2 192.168.255.185:/usr /mnt
mount_nfs -T -3 192.168.255.185:/usr /mnt
The only difference is the [udp] vs [tcp] in the error msg:
[tcp] 192.168.255.185:/usr: RPCPROG_NFS: RPC: Unknown host
I sniffed traffic with tcpdump and ethereal: the diskless client is
contacting the server so it's not having problems resolving that IP
addr.
I'm not hard-core enough to understand what might cause this failure,
which occurs in /usr/src/sbin/mount_nfs/mount_nfs.c:
if (portspec != NULL) {
/* `ai' contains the complete nfsd sockaddr. */
nfs_nb.buf = ai-ai_addr;
nfs_nb.len = nfs_nb.maxlen = ai-ai_addrlen;
} else {
/* Ask the remote rpcbind. */
nfs_nb.buf = nfs_ss;
nfs_nb.len = nfs_nb.maxlen = sizeof nfs_ss;
if (!rpcb_getaddr(RPCPROG_NFS, nfsvers, nconf, nfs_nb,
hostp)) {
if (rpc_createerr.cf_stat == RPC_PROGVERSMISMATCH
trymntmode == ANY) {
trymntmode = V2;
goto tryagain;
}
snprintf(errbuf, sizeof errbuf, [%s] %s:%s: %s,
netid, hostp, spec,
clnt_spcreateerror(RPCPROG_NFS));
return (returncode(rpc_createerr.cf_stat,
rpc_createerr.cf_error));
}
}
To see if this was a portmapper/rpcbind issue, I tried doing the
client mount and specifying the port:
mount -o port=2049 192.168.255.185:/usr /mnt
and got a slightly different error:
[udp] 192.168.255.185:/usr: RPCMNT: clnt_create: RPC: Unknown host
and now I'm definitely over my head trying to read mount_nfs.c. :-(
I don't understand this since the client is able to mount
/usr/local/diskless to get the root filesystem and run the kernel.
But I believe pxeboot is doing this, not a full FreeBSD binary.
What's the difference in the way the mount?
Any suggestions? Thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: memset prototype changed?
On Tue, Feb 18, 2003 at 08:55:02PM +0100, Dag-Erling Smorgrav wrote: Jacques A. Vidrine [EMAIL PROTECTED] writes: On Tue, Feb 18, 2003 at 12:01:29PM +0100, Dag-Erling Smorgrav wrote: The code that fails to compile is blatantly wrong: memset(schedule, 0, sizeof(schedule)); I wouldn't say `blantantly'. The expressions `schedule' and `schedule' are equivalent when `schedule' is an array type. ...but Key_schedule is an opaque type, so it is not correct to assume it's an array. You won't get much argument from me about that. Nonetheless, lots of code `knows' that it is `unsigned char[8]' (it _is_ DES, after all, where all the keys and operations are on 64 bits). Unfortunately, some of these practices were extended to the triple-DES interfaces as well... Cheers, -- Jacques A. Vidrine [EMAIL PROTECTED] http://www.celabo.org/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: memset prototype changed?
Dag-Erling Smorgrav wrote: Jacques A. Vidrine [EMAIL PROTECTED] writes: On Tue, Feb 18, 2003 at 12:01:29PM +0100, Dag-Erling Smorgrav wrote: The code that fails to compile is blatantly wrong: memset(schedule, 0, sizeof(schedule)); I wouldn't say `blantantly'. The expressions `schedule' and `schedule' are equivalent when `schedule' is an array type. ...but Key_schedule is an opaque type, so it is not correct to assume it's an array. Aren't all opaque types pointers, by definition? Gotta wonder how one does a sizeof() on an opaque type... Seems to me that memset()'ing this thing to zero is a bogus thing to do in the first place, and that there should be an initialization routine, instead, that will do the job for you -- if not allocate you one of the things at the same time. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: background fsck deadlocks with ufs2 and big disk
Thus spake Martin Blapp [EMAIL PROTECTED]: I just wanted to tell that I can deadlock one of my current boxes with a ufs2 filesystem on a 120GB ATA disk. I can reproduce the problem. The background fsck process hangs some time at the same place always at the same place, sometimes the box freezes after some time. The same box works fine with ufs1. IIRC, Kirk was trying to reproduce this a little while ago in response to similar reports. He would probably be interested in any new information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: call for testers: cd(4) changes
On Sun, Feb 16, 2003 at 22:45:14 -0700, Kenneth D. Merry wrote:
On Sat, Feb 15, 2003 at 12:20:46 +0100, Thomas Quinot wrote:
Le 2003-02-15, Kenneth D. Merry écrivait :
- Automatically detect CDROM drives that can't handle 6 byte mode
sense and mode select, and adjust our command size accordingly.
More information on that below.
- MODE_SENSE and MODE_SELECT translation removed in ATAPICAM and in
the umass(4) driver, since there's no way for that to work properly
(see below).
I'm afraid things are not as simple as that. Unfortunately you cannot
expect ATAPI drives to properly reject MODE_{SENSE,SELECT}_6 and try the
_10 variants in that case: the reason why ATAPICAM inconditionnally
translates the _6 commands into _10 is because some ATAPI drives have
been found to lock up when they rececive the _6 commands, whereas the
ATAPI specification only mandates the implementation of the _10
versions.
The translation produces bogus results, so we can't really keep it around.
In the mode sense case, the caller will be looking in the wrong place for
the page. In the mode select page, the drive will be looking for the page
at the wrong offset, and the page will be truncated.
The two alternatives I can think of are getting the CAM_NEW_TRAN_CODE
working, so we'll know that drives that talk ATAPI can't do 10 byte mode
sense/select, or quirking drives that are known to hang when they get 6
byte commands.
The long term plan is the first alternative; that really is the cleanest
way to do it. In the short term, I'll put in a quirk mechanism. I'll be
somewhat strict about making submitters prove that the drive has a
problem, and documenting it in a PR audit trail. (The same sort of
approach Nate is using with the da(4) driver quirks.) We should be able
to remove all drives with the 10 byte quirk once we get the
CAM_NEW_TRAN_CODE done.
I've got a new patchset with the quirk definition and comments in there:
http://people.FreeBSD.org/~ken/scsi_cd.cmdsize.20030217
I'm planning to check it in Thursday, assuming I have time.
Ken
--
Kenneth Merry
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
The excellent partner for your business! (030219)
We would like to apologize as soon as this email is caused you any inconvenience. If it is, should you delete it directly, or send it back to [EMAIL PROTECTED] Many thanks! Dear Sir/Madam: PANFINE GROUP, since 1982 The Reliable Partner: Stable Cooperation, Truly Support With Coordination Understanding Are you seeking partner in China? Where is it? Here Panfine is! PANFINE GROUP is very suitable for customers who need a partner's resource production in China. Services: (Location in Shanghai, China) *RESOURCE *REPACKAGE *LOGISTIC CENTER *PRODUCTION Products: 1. Precision Components (CNC Lathe): Electronic, Computer Hardware, Medical Device, Optical-Fiber Instrument, Communication Equipment, Food Hardware, Pneumatic Tools, etc and any parts. 2. Wireless Solution 3. Action Scanners 4. 4-lens Camera (Action Sampler) 5. General Merchandise: Bike, Beauty Care Implement, and Toy¡Ketc. 6. Industrial Items: Battery Button, Cable Tie, Ferrite Core, Electronic Transformer, and Safety Gear Product¡Ketc. If you are looking for more profit or reducing cost for business, please contact with us immediately. We wish you having a great success in business! Best regards, Kimberly Chu for Panfine Creations Corp. (030219)
Re: panic starting gnome
Lars Eggert wrote: Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = fault virtual address = 0x34 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01b28a6 [ ... ] kernel: type 12 trap, code=0 Stopped at _mtx_lock_flags+0x26: cmpl$0xc03884a0,0(%esi) [ ... ] trap_fatal(e91a5780,34,c0372ee0,2e4,c658e780) at trap_fatal+0x250 trap_pfault(e91a5780,0,34,c03e0758,34) at trap_pfault+0x17a trap(c21a0018,10,c0360010,9e,34) at trap+0x3e5 calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc01b28a6, esp = 0xe91a57c0, ebp = 0xe91a57e0 --- _mtx_lock_flags(34,0,c035cf5f,9e,c658e780) at _mtx_lock_flags+0x26 ** Attempt to dereference the value 0x34 as if it were a pointer. namei(e91a5a44,c0207d5a,c749458c,0,c658e780) at namei+0x134 Called from here. Debug: 1) Make sure that the kernel that has the fault was created with config -g, so that there is a debug version of it lying around in the build directory. 2) Make sure that the kernel you installed is the stripped version of the debug kernel (there are two kernels created as a result of config -g; one is kernel.debug (the debug version) and the other is kernel (the stripped version). 3) If #1 and #2 are not true, then make them true, and repeat the problem. 4) Boot a kernel that doesn't crash instead, so that you can run the debugger. 5) Go to the build directory, and look at the faulting code to see where it gets the value 0x34 to pass in to the _mtx_lock_flags(); this is the bogus value. For example, if you had a debug kernel for the kernel that has the problem, and it was config'ed from i386 GENERIC, you would use the following sequence of commands: cd /sys/i386/compile/GENERIC gdb -k kernel.debug list namei+0x134 6) Change the code so the bogus value is no longer being passed. 7) Live happily ever after. Note that, to me, this looks like a problem with a dereference of a current process which is not really current, as a result of a wakeup occurring in an interrupt handler for an outstanding request which was satisfied by the interrupt handler. Note: Under no circumstances should a page 0 address be passed around to anyone, since page zero is typically unmapped in order to trigger NULL pointer dereference faults and/or structure member reference faults for structure elements (at least in the the initial 4K: range 0x-0x1000) when a structure pointer itself is NULL. IMO, the most likely cause is that you have a null structure pointer, and the element at offset 0x34 into the structure is being referenced out of it, without checking that the pointer is not NULL, and the most likely culprit is a proc/kse/thread type structure that's not guaranteed to be valid in interrupt context. Probably, the scheduler is switching directly from interrupt of a process context Q to a wakeup of the same process Q, without restoring a register value that should normally be restored following an interrupt. I have no idea which of the schedulers you are using, so I have no idea if this should be an expected omission; my best guess is you are using the new one, though, because this is an unlikely problem with the old one, if it's really a scheduler wakeup problem. namei(e91a5a44,c0207d5a,c749458c,0,c658e780) at namei+0x134 ^ | vn_open_cred(e91a5a44,e91a5a0c,0,c2195e80,0) at vn_open_cred+0x53c ^ ^ | | ...all three of these are also incredibly suspicious, at first sight... Until you are willing to list out the code where the bogus value is being passed to the function call, there's no way any of us are going to be able to correlate your stack traceback to our own source trees, in order to be able to help you, unless you are running a tagged veraion (e.g. 5.0-RELEASE) with no modifications. Just saying the most recent current or I CVS'up'ed on xxx date is really useless to us, because CVS mirrors don't contain well known information relative to a CVS'up date. In many cases, we will need you to check out (at least!) a fresh /sys source tree from the CVS repository, using a date tage, if you are not running a -RELEASE version. Yes, this is a long-standing problem with the FreeBSD project itself. If you can do this, and repeat the
