GEOM/libdisk problem on pc98
The test program for libdisk is a failure in pc98 disks.
I wonder at why pc98 disks don't have their type ('ty') in the result
of kern.geom.conftxt, but i386 disks have.
#./tst01 da0
PC98 [da0s1] 2 40958
error = -1
BSD [da0s1b] 2 1024
error = 310
BSD [da0s1a] 1026 39934
error = 310
c 0x8062040
c-p 0x8062080
c-p-p 0x0
--==##==--
Debug_Disk(da0) bios_geom=0/8/128 = 0
boot1=0x0, boot2=0x0, bootipl=0x0, bootmenu=0x0
--0x80620400 40031712 40031711 da0 - ?? 0x00
-- 0x80620800 40031712 40031711 -- unused 0x00
kern.geom.conftxt: 0 DISK da0 20496236544 512 hd 8 sc 128
1 PC98 da0s1 10736893952 512 i 0 o 524288
2 BSD da0s1c 10736893952 512 i 2 o 0
2 BSD da0s1b 268435456 512 i 1 o 0
2 BSD da0s1a 10468458496 512 i 0 o 268435456
0 DISK wd2 1281925120 512 hd 8 sc 17
1 PC98 wd2s1 1281368064 512 i 0 o 69632
0 DISK wd1 426774528 512 hd 8 sc 17
1 PC98 wd1s1 425730048 512 i 0 o 69632
2 BSD wd1s1e 225378304 512 i 4 o 201326592
2 BSD wd1s1c 426704896 512 i 2 o 0
2 BSD wd1s1b 134217728 512 i 1 o 67108864
2 BSD wd1s1a 67108864 512 i 0 o 0
0 DISK wd0 3228696576 512 hd 8 sc 17
1 PC98 wd0s1 3228626944 512 i 0 o 69632
2 BSD wd0s1e 2154885120 512 i 4 o 1073741824
2 BSD wd0s1c 3228626944 512 i 2 o 0
2 BSD wd0s1b 536870912 512 i 1 o 536870912
2 BSD wd0s1a 536870912 512 i 0 o 0
---
TAKAHASHI Yoshihiro [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean disk broken
USB is only the transport. It doesn't add or remove functionality (the only exception being probing for LUNs on CBI devices). If you want to determine the geometry you will have to do this through SCSI commands. I was hoping that the CAM code would be smart enough to request the details from the drive itself, but perhaps there is a good reason for asking the controller for this. It did work without, so it hasn't been implemented yet. Feel free to suggest a SCSI command together with the logic. What is the GET_GEOMETRY used for anyway? Well the short version of the problem is that fdisk -BI disk works on -stable to get a FreeBSD partition on the Compact Flash. This does not work on -current anymore. I have traced that back to the commit in umass.c rev 1.61 that removed the fake geometry setting and just leave the cylinders, heads and sectors_per_track zero. This cause fdisk to coredump with a floating point error. In message: [EMAIL PROTECTED] Poul-Henning Kamp [EMAIL PROTECTED] writes: : We should obviously fix it. I have no idea what is possible in USB : devices in this respect. Nor do I. Maybe there's some SCSI command that we can send that is well defined enough to work often enough. However, I'm not clueful enough about SCSI to know if this can be done (likely reading some mode page will do it in real SCSI), nor about USB's mass storage devices, nor about all the wonderful and weird variations that one might find in the wild... John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean diskbroken
In message: [EMAIL PROTECTED]
John Hay [EMAIL PROTECTED] writes:
: What is the GET_GEOMETRY used for anyway?
:
: Well the short version of the problem is that fdisk -BI disk works
: on -stable to get a FreeBSD partition on the Compact Flash. This does
: not work on -current anymore. I have traced that back to the commit
: in umass.c rev 1.61 that removed the fake geometry setting and just
: leave the cylinders, heads and sectors_per_track zero. This cause
: fdisk to coredump with a floating point error.
fdisk is using them, btw, to create a MBR which needs these fields to
be somewhat sane. The floating point error likely is because we're
dividing by zero on this case:
#define RoundCyl(x) x) + cylsecs - 1) / cylsecs) * cylsecs)
if cylsecs is 0, guess what happens. We do similar things with
dos_cylsecs in init_sector0. There's also code in get_params() that
devides by dos_heads * 512 * dos_sectors:
static int
get_params()
{
int error;
u_int u;
off_t o;
error = ioctl(fd, DIOCGFWSECTORS, u);
if (error == 0)
sectors = dos_sectors = u;
error = ioctl(fd, DIOCGFWHEADS, u);
if (error == 0)
heads = dos_heads = u;
dos_cylsecs = cylsecs = heads * sectors;
disksecs = cyls * heads * sectors;
error = ioctl(fd, DIOCGSECTORSIZE, u);
if (error != 0)
u = 512;
error = ioctl(fd, DIOCGMEDIASIZE, o);
if (error == 0) {
disksecs = o / u;
cyls = dos_cyls = o / (u * dos_heads * dos_sectors);
}
return (disksecs);
}
fdisk likely should do something sane in the face of such insanity,
but it is unclear what and fdisk is a royal pita to work on anyway :-(
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: GEOM/libdisk problem on pc98
In message [EMAIL PROTECTED], Takahashi Yoshihiro
writes:
The test program for libdisk is a failure in pc98 disks.
I wonder at why pc98 disks don't have their type ('ty') in the result
of kern.geom.conftxt, but i386 disks have.
I still have practically no documentation of the PC98 format and no
hardware I can test on, so I am pretty unable to do anything sane.
Feel free to fix this and submit patches to me for review: I want
to make sure we don't adversely affect the platforms which work at
this late point i the release-process.
--
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: WIne freezes -current for half a year
On Sun, 3 Nov 2002 18:26:50 -0800 Alex Zepeda [EMAIL PROTECTED] wrote: Actually, I think he's complaining that WINE isn't working in -current. Yup. That's about right. Last time I tried Wine (sometime within the past three or four months) I was trying to install either Free Agent or WinMX. The thing caused my 'puter to just reboot. I haven't felt like trying it since (especially now that current isn't hanging nearly as often otherwise). i have similar problems on -stable. the last Wine snapshot that ran Forte Agent fine was 2002.05.09, all newer Wine versions crash/hang when i try to reply to someone (Agent creates a new window/thread(??) and then wine goes nuts :( To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean diskbroken
Well the short version of the problem is that fdisk -BI disk works on -stable to get a FreeBSD partition on the Compact Flash. This does not work on -current anymore. I have traced that back to the commit in umass.c rev 1.61 that removed the fake geometry setting and just leave the cylinders, heads and sectors_per_track zero. This cause fdisk to coredump with a floating point error. Hm, strange. I would think that a compact flasg is an ATAPI over CBI device (see attach message in your dmesg). If that is the case, the 'fake setting' was not done in STABLE either and I would expect the problem to be somewhere else. But that would contradict your research. Nick To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/fs/specfs spec_vnops.c
On Mon, Nov 04, 2002 at 08:48:01AM +0100, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Doug Barton writes: Kirk, I'm adding a bunch of people to the list who were involved in a thread on -current on this topic. I also tried this change and noticed that things did seem a tiny bit snappier (although my system is slow enough that it could have just been my imagination). All things considered, I think we should just pla to leave it this way for 5.0-R. Until now people were used to wait for fsck to finish, at least now they can do something in while it runs. Well... like I indicated earlier in the thread on -CURRENT, things were definitely *slow*. I also said I would try to provide benchmarks if people told me how to do that (and what to time). In any case, as a rough measurement, starting X on -CURRENT took about 2-3 seconds vs. about half a second on -STABLE on the exact same hardware. It was even measurable on a simple 'ls' in a large directory. I think if this is left in as is, people 'new' to FreeBSD will think it's dead slow, and move on elsewhere. I belive GEOM provides the framework where we can properly tag I/O requests with a priority, propagate that priority down to the device drivers and act accordingly in the disksort disk-scheduling code. If that's the case, I'd like to see it in 5.0R. That would allow us to address not only the bgfsck but also things like silly-seek-syndrome and other sub-optimal issues in our current I/O system. That would be great. --Stijn -- The right half of the brain controls the left half of the body. This means that only left handed people are in their right mind. msg46035/pgp0.pgp Description: PGP signature
Re: umass CF geometry problems, was Re: fdisk -BI ob clean diskbroken
Let's work on the 'proper' solution first. What SCSI commands are suitable for getting the geometry, generically on a device? Nick fdisk likely should do something sane in the face of such insanity, but it is unclear what and fdisk is a royal pita to work on anyway :-( Warner -- [EMAIL PROTECTED] http://www.van-laarhoven.org/ [EMAIL PROTECTED]http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ssh-agent broken with pam_ssh for xdm (+ fix for ssh-agent.c)
yes, geteuid() could work, too, but why is ssh-agent running
with a privileged user id? shouldn't both the real and
effective user id be the uid of the user?
On Sun, Nov 03, 2002 at 08:49:02PM +0100, Alexander Leidinger wrote:
Hi,
[Markus: this is on FreeBSD-current with
$OpenBSD: ssh-agent.c,v 1.105 2002/10/01 20:34:12 markus Exp $]
I use pam_ssh in pam.d/xdm and after an update to todays -current, it
doesn't add my key anymore. In /var/log/messages I see the following if
I try a ssh-add -l:
---snip---
ssh-agent[6438]: error: uid mismatch: peer euid 1000 != uid 0
---snip---
ssh-agent.c:after_select() contains:
---snip---
if ((euid != 0) (getuid() != euid)) {
error(uid mismatch:
peer euid %u != uid %u,
(u_int) euid, (u_int) getuid());
close(sock);
break;
}
---snip---
As ssh_agent gets startet from pam_ssh in xdm (which runs as root -
getuid() = 0, geteuid() = 1000), it is obvious why it doesn't work.
At the moment I have this piece of code commented out, but I think this
should get changed to use geteuid() instead of getuid(). Or did I
misunderstood the idea behind the above code?
Bye,
Alexander.
--
Loose bits sink chips.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean disk broken
Well the short version of the problem is that fdisk -BI disk works on -stable to get a FreeBSD partition on the Compact Flash. This does not work on -current anymore. I have traced that back to the commit in umass.c rev 1.61 that removed the fake geometry setting and just leave the cylinders, heads and sectors_per_track zero. This cause fdisk to coredump with a floating point error. Hm, strange. I would think that a compact flasg is an ATAPI over CBI device (see attach message in your dmesg). If that is the case, the 'fake setting' was not done in STABLE either and I would expect the problem to be somewhere else. But that would contradict your research. Maybe the short version was too short. :-) The CF is behind a SanDisk ImageMate (I have two different ones), which emulates SCSI according to dmesg. I don't know if they use BBB or CBI. I don't know what the difference is either. :-) umass0: SanDisk ImageMate CF-SD, rev 1.10/0.12, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: SanDisk ImageMate CF-SD1 0100 Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 61MB (125440 512 byte sectors: 0H 0S/T 0C) umass0: at uhub0 port 1 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached umass0: SanDisk Corporation ImageMate CompactFlash USB, rev 1.10/0.09, addr 2 umass0: Get Max Lun not supported (STALLED) da0 at umass-sim0 bus 0 target 0 lun 0 da0: SanDisk ImageMate II 1.30 Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: 61MB (125441 512 byte sectors: 0H 0S/T 0C) # John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Weird NFS Client behaviour?
I'm seeing some very dodgy behaviour in my home NFS environment. I have a 4.7-RC2 box serving up /export, and this machine is called 'thefather'. I have my laptop, 5.0-CURRENT (a day or two stale), and this machine is called 'luna'. I also have a 4.7-STABLE (a week or two stale) box, called 'dalek'. Now, I have a mount of thefather:/export on /mnt on luna, and the mount is there, and gtk-gnutella is running with its download directory in /mnt/@shared/download, and so on. Gtk-Gnutella is still running and downloading files fine. However if I try to df -h or ls -lart / or ls /mnt/@shared/unsorted, the process in question will block indefinitely in the NFS lock recv code, but yet if I ssh to dalek and try to do the same, it works fine and dandy. Note that this problem just appeared about 20 minutes ago, and is still occurring, and I've had it happen before... Anyone seen this or have any clue? I'm vaguely familiar with the lock stuff in nfs_socket.c on the client side, but I've still got no idea what is going on... Could it be because I'm using TCP nfs, rather than UDP, and that somehow affects statep for multiple concurrent requests? Thanks, juli. -- Juli Mallett [EMAIL PROTECTED] | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger [EMAIL PROTECTED] http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WIne freezes -current for half a year
Alex Zepeda wrote: On Sun, Nov 03, 2002 at 02:36:41PM -0800, Terry Lambert wrote: My understanding of his post was that, 6 months later, the machine unfreezes, and everything works normally... 8-) 8-). Actually, I think he's complaining that WINE isn't working in -current. Yup. That's about right. Last time I tried Wine (sometime within the past three or four months) I was trying to install either Free Agent or WinMX. The thing caused my 'puter to just reboot. I haven't felt like trying it since (especially now that current isn't hanging nearly as often otherwise). It'd probably be a good idea to try it again before reporting it as if it were still not working. It may or may not have been fixed by the signal and FP register state commits, etc., so just because it was broken doesn't mean it's broken now. Even if it *is* still broken, it could be broken in an entirely different way... 8-). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
alpha tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Mon Nov 4 03:05:00 PST 2002 -- Kernel build for GENERIC completed on Mon Nov 4 03:35:31 PST 2002 -- Kernel build for LINT started on Mon Nov 4 03:35:31 PST 2002 -- === vinum Makefile, line 4517: warning: duplicate script for target geom_bsd.o ignored cc1: warnings being treated as errors /h/des/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_alloc': /h/des/src/sys/dev/aic7xxx/aic79xx.c:4208: warning: unsigned int format, different type arg (arg 3) /h/des/src/sys/dev/aic7xxx/aic79xx.c:4208: warning: unsigned int format, different type arg (arg 4) /h/des/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_init_scbdata': /h/des/src/sys/dev/aic7xxx/aic79xx.c:4601: warning: unsigned int format, different type arg (arg 3) *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ssh-agent broken with pam_ssh for xdm (+ fix for ssh-agent.c)
Markus Friedl [EMAIL PROTECTED] writes: yes, geteuid() could work, too, but why is ssh-agent running with a privileged user id? shouldn't both the real and effective user id be the uid of the user? There seems to be a bug in our pam_ssh(8). It switches to user privileges when reading the user's keys, but switches back before starting the agent, instead of after. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/fs/specfs spec_vnops.c
On Mon, Nov 04, 2002 at 09:49:06AM +0100, Stijn Hoop wrote: On Mon, Nov 04, 2002 at 08:48:01AM +0100, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Doug Barton writes: Kirk, I'm adding a bunch of people to the list who were involved in a thread on -current on this topic. I also tried this change and noticed that things did seem a tiny bit snappier (although my system is slow enough that it could have just been my imagination). All things considered, I think we should just pla to leave it this way for 5.0-R. Until now people were used to wait for fsck to finish, at least now they can do something in while it runs. Well... like I indicated earlier in the thread on -CURRENT, things were definitely *slow*. I also said I would try to provide benchmarks if people told me how to do that (and what to time). In any case, as a rough measurement, starting X on -CURRENT took about 2-3 seconds vs. about half a second on -STABLE on the exact same hardware. It was even measurable on a simple 'ls' in a large directory. I think if this is left in as is, people 'new' to FreeBSD will think it's dead slow, and move on elsewhere. Whoops, monday morning brain fart. Ignore my previous mail, I didn't get the fact that the switch defaulted to *off*. Am I reading it correctly now, that the ioslow sleep is therefore also not enabled by default? --Stijn -- The most reliable proof that there are extraterrestrial intelligent lifeforms out there is that nobody actually tries to get in contact with us. -- Dirk Mueller msg46045/pgp0.pgp Description: PGP signature
Ports funkyness
OK, so I update my ancient -current box and then realise I have to update all my packages too.. No problem except I get funky stuff like - [guppy 23:02] /usr/ports/sysutils/portupgrade sudo portupgrade windowmaker-0.65.1_1 [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 98 packages found (-61 +4) (...)(? mkisofs-1.15.a21)(? sysutils/pkg_tarup) done] anonymous: Not in due form: name-version Hmm.. OK, lets do some package deletion manually.. [guppy 23:03] /var/db/pkg sudo pkg_delete mozilla-headers-1.0.rc1_1,1 pkg_delete: package 'mozilla-headers-1.0.rc1_1,1' doesn't have a prefix OK, maybe -f will work [guppy 23:03] /var/db/pkg sudo pkg_delete -f mozilla-headers-1.0.rc1_1,1 pkg_delete: package 'mozilla-headers-1.0.rc1_1,1' doesn't have a prefix [guppy 23:03] /var/db/pkg ls -la /var/db/pkg/mozilla-headers-1.0.rc1_1,1 total 7 -rw-r--r--1 root wheel52 May 9 21:56 +COMMENT -rw-r--r--1 root wheel 0 Nov 3 15:59 +CONTENTS -rw-r--r--1 root wheel83 May 9 21:56 +DESC drwxr-xr-x2 root wheel 512 Nov 3 15:59 . drwxr-xr-x 100 root wheel 4096 Nov 4 23:02 .. Guess not. Now what do I do? :) Ahh, hmm.. guess that zero length +CONTENTS might have something to do with it. Yech, wonder how that happened :( Lots of my ports appear to be damaged the same way :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ssh-agent broken with pam_ssh for xdm (+ fix for ssh-agent.c)
On Mon, 04 Nov 2002 12:11:40 +0100 Dag-Erling Smorgrav [EMAIL PROTECTED] wrote: Dag-Erling Smorgrav [EMAIL PROTECTED] writes: There seems to be a bug in our pam_ssh(8). It switches to user privileges when reading the user's keys, but switches back before starting the agent, instead of after. Umm, wait, that was too easy. It doesn't. I got the start_agent and !start_agent cases mixed up. Alexander, could you check what UID ssh-agent runs as (ps auxw | grep agent)? What version of XFree86 do It runs with my UID: ---snip--- (5) netchild@ttyp2 % ps auxww |grep \[s\]sh-agent netchild 757 0.0 0.2 1976 1188 ?? Is9:00am 0:00.01 ssh-agent ---snip--- you run, and did you compile it yourself or did you install binaries? Myself. How long ago did you install it? What does 'ldd /usr/X11R6/bin/xdm' Oct 25. say? If it's pretty old, it might still be using Linux-PAM and an old No, it uses our PAM: ---snip--- libpam.so.2 = /usr/lib/libpam.so.2 (0x281eb000) (6) netchild@ttyp0 % ll /usr/lib/libpam.* -r--r--r-- 1 root wheel127K 3 Nov 20:04 /usr/lib/libpam.a lrwxr-xr-x 1 root wheel 11B 3 Nov 20:04 /usr/lib/libpam.so@ - libpam.so.2 -r--r--r-- 1 root wheel 25K 3 Nov 20:04 /usr/lib/libpam.so.2 ---snip--- non-credential-dropping pam_ssh(8). Bye, Alexander. -- Press every key to continue. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current on PPC
Hi Paolo, What's the status of FreeBSD-CURRENT on PPC (mainly PowerMac stuff)? It's riding out the storm of all the recent -current changes. There should be another snapshot available soon - details will be posted on freebsd-ppc. later, Peter. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
cdrecord-ProDVD ready
Hi all, I just put out a cdrecord-ProDVD binary for FreeBSD on ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ProDVD/ It has been compiled on 4.4 but also runs on curent. Note that there is not yet a version for commercial use. The recent binary will only work with the free private/research/educational_non-commercial_use key. As the unmainteined so called free hack on cdrecord only works with a Pioneer A03, this seems to be a big step forward for FreeBSD users. Cdrecord-ProDVD runs with _all_ Pioneer drives (S101,S201,A03,A04) the Panasonic drive, the new Sony drive and the new Toshiba drive. Writing with the Toshiba has not been tested yet but it looks promising. Jörg EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED] (uni) If you don't have iso-8859-1 [EMAIL PROTECTED] (work) chars I am Jorg Schilling URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean disk broken
Let's work on the 'proper' solution first.
What SCSI commands are suitable for getting the geometry, generically
on a device?
Hmmm, I made an interesting discovery. I searched through some of the
scsi drivers, sys/dev/{aha|ahb|aic*|sym}, looking for XPT_CALC_GEOMETRY
and they all fake the geometry. :-/
fdisk likely should do something sane in the face of such insanity,
but it is unclear what and fdisk is a royal pita to work on anyway :-(
John
--
John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean disk broken
In message [EMAIL PROTECTED], John Hay wri
tes:
Let's work on the 'proper' solution first.
What SCSI commands are suitable for getting the geometry, generically
on a device?
Hmmm, I made an interesting discovery. I searched through some of the
scsi drivers, sys/dev/{aha|ahb|aic*|sym}, looking for XPT_CALC_GEOMETRY
and they all fake the geometry. :-/
I noticed this too recently when studying PC98 related disk code.
Solaris on the other hand, pokes some random mode-page which contains
some numbers which may, but more likely may not, have any relationship
to the real hardwares format. Few if any drives have constant number
of sectors per track these days.
At least our scsi code never returns degenerate numbers.
Anyway, what I really wanted to say is that the reason I put the
FW in the name of the DIOCGFW{SECTORS,HEADS} ioctls was that at
this time and date, the only possible utility of such archaic values
are to avoid breaking stupid firmware.
--
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
USB problem (Who owns USB code in -current?)
Dear Hackers, Who owns USB code in -current? I need an USB expert advice on the FreeBSD specific USB problem. Basically whenever i put my laptop into docking station and try to plug Bluetooth USB dongle i get uhub1: device problem, disabling port 1 message. This problem *does not* exist when i try to connect the USB dognle directly to the laptop. My current theory is that extra USB hub in docking station somehow makes the difference. I have attached few files that might help. This problem is FreeBSD-specific and seems related to Bluetooth USB dongles only. I have been contacted by other people who have the same problem. I do not know what is so special about Bluetooth USB dongles. USB mouse, for example, works fine. Can it be power related? Both Windows and Linux do not have this problem which makes me think that there is something different about FreeBSD way of doing things. Please advice. I will try to read USB spec, but if someone could give me the right direction, that would be helpful. thanks, max boot-v.txt.gz Description: GNU Zip compressed data usb-messages.txt.gz Description: GNU Zip compressed data Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 uhub0 port 1 powered port 2 addr 2: full speed, self powered, config 1, UT-USB41 hub(0x1446), Texas Instruments(0x0451), rev 1.00 uhub1 port 1 powered port 2 powered port 3 powered port 4 powered
Re: Can't resolve hosts via dns on the command line with latest-current
On Mon, 4 Nov 2002, Giorgos Keramidas wrote:
On 2002-11-04 01:16, Hidetoshi Shimokawa [EMAIL PROTECTED] wrote:
I have the same problem and reverting rev. 1.134 of
/sys/kern/uipc_socket.c fixes the problem.
The change might have something wrong with a loopback interface.
True. I had been seeing problems with network connections the last
days, and was already in the process of backing out changes one by one
when I saw this. Reverting 1.134 fixes things here. If I put it back
in, strange DNS failures start causing troubles with almost everything
(including Sendmail, fetchmail, ssh).
Giorgos.
I've had this running on multiple machines for weeks without problems. What
is your resolve.conf and nsswitch.conf? Curious,
Kelly
--
Kelly Yancey -- kbyanc@{posi.net,FreeBSD.org}
Join distributed.net Team FreeBSD: http://www.posi.net/freebsd/Team-FreeBSD/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Patch for fetch
The attached is a quick patch for fetch(1). It adds a new option (-g)
that forces the transfer progress to be printed, even if it thinks that
stderr is not a tty or that it is not the foreground process.
This is useful for me in a program that runs make fetch in a port
directory through a pipe and wants to keep tabs on the download
progress. Modifying fetch seemed to be the simplest and most
straightforward of all my options; rather than requiring wget or
re-implementing some of make's logic.
Hopefully this will be useful to someone in a similar situation.
Craig Boston
Index: fetch.1
===
RCS file: /home/ncvs/src/usr.bin/fetch/fetch.1,v
retrieving revision 1.48
diff -u -r1.48 fetch.1
--- fetch.1 2002/04/19 23:35:12 1.48
+++ fetch.1 2002/11/04 16:39:37
-102,6 +102,8
on the remote host.
This option is deprecated and is provided for backward compatibility
only.
+.It Fl g
+Force output of transfer progress even if stderr is not a tty.
.It Fl h Ar host
The file to retrieve is located on the host
.Ar host .
Index: fetch.c
===
RCS file: /home/ncvs/src/usr.bin/fetch/fetch.c,v
retrieving revision 1.54
diff -u -r1.54 fetch.c
--- fetch.c 2002/10/27 17:33:08 1.54
+++ fetch.c 2002/11/04 16:39:37
-58,6 +58,7
int d_flag; /*-d: direct connection */
int F_flag; /*-F: restart without checking mtime */
char *f_filename; /*-f: file to fetch */
+int g_flag; /*-g: force progress output */
char *h_hostname; /*-h: host to fetch from */
int l_flag; /*-l: link rather than copy file: URLs */
int m_flag; /* -[Mm]: mirror mode */
-128,12 +129,12
struct timeval now;
int ctty_pgrp;
- if (!v_tty || !v_level)
+ if (!g_flag (!v_tty || !v_level))
return;
/* check if we're the foreground process */
- if (ioctl(STDERR_FILENO, TIOCGPGRP, ctty_pgrp) == -1 ||
- (pid_t)ctty_pgrp != pgrp)
+ if (!g_flag (ioctl(STDERR_FILENO, TIOCGPGRP, ctty_pgrp) == -1 ||
+ (pid_t)ctty_pgrp != pgrp))
return;
gettimeofday(now, NULL);
-669,7 +670,7
int c, e, r;
while ((c = getopt(argc, argv,
- 146AaB:bc:dFf:Hh:lMmnPpo:qRrS:sT:tUvw:)) != -1)
+ 146AaB:bc:dFf:gHh:lMmnPpo:qRrS:sT:tUvw:)) != -1)
switch (c) {
case '1':
once_flag = 1;
-706,6 +707,9
break;
case 'f':
f_filename = optarg;
+ break;
+ case 'g':
+ g_flag = 1;
break;
case 'H':
warnx(the -H option is now implicit,
Re: Can't resolve hosts via dns on the command line with latest-current
On Mon, 4 Nov 2002, Hidetoshi Shimokawa wrote:
I have the same problem and reverting rev. 1.134 of
/sys/kern/uipc_socket.c fixes the problem.
The change might have something wrong with a loopback interface.
/\ Hidetoshi Shimokawa
\/ [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html
Index: uipc_socket.c
===
RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v
retrieving revision 1.135
diff -u -r1.135 uipc_socket.c
--- uipc_socket.c 2 Nov 2002 05:14:30 - 1.135
+++ uipc_socket.c 3 Nov 2002 14:45:16 -
@@ -1784,7 +1784,11 @@
{
struct socket *so = (struct socket *)kn-kn_fp-f_data;
+#if 0
kn-kn_data = so-so_rcv.sb_cc - so-so_rcv.sb_ctl;
+#else
+ kn-kn_data = so-so_rcv.sb_cc;
+#endif
if (so-so_state SS_CANTRCVMORE) {
kn-kn_flags |= EV_EOF;
kn-kn_fflags = so-so_error;
I suspect something in lib/libc/net/res_send.c is using special knowledge of
the contents of the socket buffer so calculate the real amount of data that
can be read (which this patch does automatically). I'm looking into it.
At Sun, 03 Nov 2002 05:39:48 -0800,
Doug Barton wrote:
Howdy,
With -current built from sources updated at around 8pm PST, I can't
resolve hosts on the command line if /etc/resolv.conf points to a name
server running on the local host. The local name server itself is
working fine, and I can reach any host in /etc/hosts as well.
ktrace /sbin/ping hub.freebsd.org
^C
kdump
651 ktrace RET ktrace 0
651 ktrace CALL execve(0xbfbffb03,0xbfbff9e4,0xbfbff9f0)
651 ktrace NAMI /sbin/ping
What is this supposed to demonstrate?
/etc/nsswitch.conf is unchanged, and contains only:
hosts: files dns
It doesn't matter if /etc/resolv.conf points to 127.0.0.1, or the IP of
the box. As soon as I point /etc/resolv.conf at a name server on another
host, it works.
My -current system from last weekend worked just fine.
Doug
Thanks. I'll let you know what I find,
Kelly
--
Kelly Yancey -- kbyanc@{posi.net,FreeBSD.org}
FreeBSD, The Power To Serve: http://www.freebsd.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: libc size
Miguel Mendez wrote:
Tim Kientzle [EMAIL PROTECTED] wrote:
1) Fragility. Could a naive sysadmin (or a dying
disk) break /[s]bin?
What if the ldconfig hints files were hosed?
Is ld-elf.so truly bulletproof?
Agreed, and, fortunately, that was taken into account with the
introduction of the /rescue dir:
christine: {48} du -h /rescue
2.4M/rescue
Oh. So the real size of NetBSD's /bin and /sbin includes
another 2.4M for /rescue. That makes it less
impressive. I don't find the duplication appealing, either.
(Why not just put the /rescue versions directly
into /bin and /sbin? That would be smaller still,
wouldn't it?)
2) Security. Can LD_LIBRARY_PATH (or other mechanisms)
be used to deliberately subvert any of these programs?
(especially the handful of suid/sgid programs here)
Several people have pointed out that FreeBSD has
certain protections against LD_LIBRARY_PATH exploits,
but there are still real questions here. (Kernel
races, possibly?) Privilege elevation is an
interesting idea, but tricky to audit.
the results from ls -l /bin on your NetBSD system
christine: {66} ls -l /bin
-r-xr-xr-x 1 root wheel8480 Oct 29 22:59 cat
-r-xr-xr-x 1 root wheel4892 Oct 29 23:00 echo
-r-xr-xr-x 1 root wheel5568 Oct 29 23:01 rmdir
-r-xr-xr-x 1 root wheel5892 Oct 29 23:02 sleep
-r-xr-xr-x 1 root wheel4652 Oct 29 23:02 sync
[[ others omitted ]]
sigh I've been looking at some of the FreeBSD standard utils,
and with a very little bit of work got this:
-rwxr-xr-x 1 tim tim 9552 Nov 4 11:10 cat
-rwxr-xr-x 1 tim tim 2776 Nov 4 11:10 echo
-rwxr-xr-x 1 tim tim 3288 Nov 1 13:48 rmdir
-rwxr-xr-x 1 tim tim 2904 Nov 4 11:10 sleep
-rwxr-xr-x 1 tim tim 2424 Nov 4 11:10 sync
All statically linked, all portable C, with identical
functionality to the originals. If statically-linked
versions can be 1/2 the size of the dynamic versions,
then I _really_ don't see the advantage of dynamic linking.
Perhaps some more careful programming is all that's needed? ;-)
(Admittedly, a space-conscious overhaul of sh, csh, or ed
is not entirely trivial; but most of /bin and /sbin is pretty simple
to prune down.)
rcNG has been in work for a long time. Is it worth it? Absolutely,
try it once and you'll wonder how you could live with the old system, or
even with the sysV symlink crazyness.
As it happens, I've been looking closely at RCng
just recently. Though I really like the core design, I do
have some quibbles with the implementation. It
is usable today, and does address the worst problems
of SysV-style init. Still needs some work, though. ;-)
Tim Kientzle
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean diskbroken
Hm, the only one that does something different is the iir/iir.c driver.
I guess the best thing is to just copy what's in the aha driver.
Nick
Let's work on the 'proper' solution first.
What SCSI commands are suitable for getting the geometry, generically
on a device?
Hmmm, I made an interesting discovery. I searched through some of the
scsi drivers, sys/dev/{aha|ahb|aic*|sym}, looking for XPT_CALC_GEOMETRY
and they all fake the geometry. :-/
fdisk likely should do something sane in the face of such insanity,
but it is unclear what and fdisk is a royal pita to work on anyway :-(
John
--
[EMAIL PROTECTED] http://www.van-laarhoven.org/
[EMAIL PROTECTED]http://www.etla.net/~n_hibma/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest-current
On Sun, 3 Nov 2002, Doug Barton wrote:
On Mon, 4 Nov 2002, Hidetoshi Shimokawa wrote:
I have the same problem and reverting rev. 1.134 of
/sys/kern/uipc_socket.c fixes the problem.
Confirmed here too, thanks for the tip. I had looked over the recent
commits to /etc/lib/*, but none of them looked guilty.
Doug
Ah, I'm able to recreate the problem now. It is odd that it only occurs on
loopback, but it doesn't appear specific to DNS. :| I'm on it. Thanks,
Kelly
--
Kelly Yancey -- kbyanc@{posi.net,FreeBSD.org}
FreeBSD, The Power To Serve: http://www.freebsd.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest-current
Kelly Yancey wrote: I suspect something in lib/libc/net/res_send.c is using special knowledge of the contents of the socket buffer so calculate the real amount of data that can be read (which this patch does automatically). I'm looking into it. ...To ensure that the read does not block, and is not issued until sufficient data exists. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WIne freezes -current for half a year
It'd probably be a good idea to try it again before reporting it as if it were still not working. It may or may not have been fixed by the signal and FP register state commits, etc., so just because it was broken doesn't mean it's broken now. Even if it *is* still broken, it could be broken in an entirely different way... 8-). It is broken with the same symtoms for the last months. a) FreeBSD freezes... you've to do a cold start, no keys or anything work b) FreeBSD reboots after a few secs of doing nothin' c) wine / wineserver process hangs in the background, doing nothing, consuming cpu time and cant be killed by kill -9 . My system is from 26. October. Not new enough? Tonight .i'll get the newest one and recompile the newest wine and tomorrow (8.00 CET) you'll get a dmesg / uname -a /sysctl -a for my system, i'm sure with a non-working wine. Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: fdisk -BI ob clean disk broken
On Sat, 2 Nov 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], John Hay wri tes: Hmmm. I just noticed that the disks probe with zero values for the heads, sectors/track and cylinders. I have tried two different USB CF readers and both do it. On 4.x it probes with the correct values on the same machine and the same devices. So why do they probe wrong? I have no idea either, but the answer must be somewhere in the da driver... Please don't assume. It's up to the transport driver to support the XPT_CALC_GEOMETRY command and umass removed its preliminary support without providing a working alternative. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean diskbroken
See XPT_CALC_GEOMETRY in /sys/dev/aic7xxx/aic7xxx_osm.c On Mon, 4 Nov 2002, Nick Hibma wrote: Let's work on the 'proper' solution first. What SCSI commands are suitable for getting the geometry, generically on a device? Nick fdisk likely should do something sane in the face of such insanity, but it is unclear what and fdisk is a royal pita to work on anyway :-( Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean diskbroken
On Mon, 4 Nov 2002, John Hay wrote:
Let's work on the 'proper' solution first.
What SCSI commands are suitable for getting the geometry, generically
on a device?
Hmmm, I made an interesting discovery. I searched through some of the
scsi drivers, sys/dev/{aha|ahb|aic*|sym}, looking for XPT_CALC_GEOMETRY
and they all fake the geometry. :-/
That's the currently the only correct way to do it. Geometry means
nothing in SCSI, everything is linear block address. For an example of
how to convert from LBA to C/H/S, see p. 92 of CAM2.
---
SETSIZE converts a read capacity value to int 13h head-cylinder-sector
requirements. It minimizes the value for number of heads and maximizes
the number of cylinders. This supports very large disks before the number
of heads will not fit in 4 bits (or 6 bits). This algorithm also
minimizes the number of sectors that are unused at the end of the disk
while allowing for large disks to be accommodated. This algorithm does
not use physical geometry.
---
It might be more useful for GEOM to query the BIOS for the physical values
and provide a way for upper levels (like CAM) to retrieve this. I'm not
familiar with what GEOM provides so far so perhaps someone can speak up
with a better way. I'm also not sure why someone would need the physical
values.
-Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean disk broken
In message [EMAIL PROTECTED], Nate Lawson writ es: It might be more useful for GEOM to query the BIOS for the physical values and provide a way for upper levels (like CAM) to retrieve this. This is a driver task. besides GEOM is above CAM, not below it. -- 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: libc size
On Mon, Nov 04, 2002 at 11:32:38AM -0800, Tim Kientzle wrote: Oh. So the real size of NetBSD's /bin and /sbin includes another 2.4M for /rescue. That makes it less impressive. I don't find the duplication appealing, either. (Why not just put the /rescue versions directly into /bin and /sbin? That would be smaller still, Because that would nullify one of the big reasons for making /bin and /sbin shared -- so one can dlopen(3). We can't, for instance, get a proper nsswitch implementation until we make /bin and /sbin dynamic. Before someone says you can dlopen() from static binaries in order to implement nsswitch, please provide the patch proving it. Our best FreeBSD minds don't think it can be done properly and sanely. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean diskbroken
That wasn't quite what I meant. I was referring to SCSI commands that are sent to the device that return info that would be usable as the number of heads and cylinders. But I guess faking them like the ah[abc] drivers do will work, as this is what many systems are already running with. Nick See XPT_CALC_GEOMETRY in /sys/dev/aic7xxx/aic7xxx_osm.c On Mon, 4 Nov 2002, Nick Hibma wrote: Let's work on the 'proper' solution first. What SCSI commands are suitable for getting the geometry, generically on a device? Nick fdisk likely should do something sane in the face of such insanity, but it is unclear what and fdisk is a royal pita to work on anyway :-( Warner -- [EMAIL PROTECTED] http://www.van-laarhoven.org/ [EMAIL PROTECTED]http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean diskbroken
On Mon, 4 Nov 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Nate Lawson writ es: It might be more useful for GEOM to query the BIOS for the physical values and provide a way for upper levels (like CAM) to retrieve this. This is a driver task. besides GEOM is above CAM, not below it. Ok. There are two things that would be useful: 1. Merging the multiple LBA to C/H/S calculations (aic7xxx, umass, ...) to one CAM convenience routine. 2. Adding a MI way to call an MD routine that will get the disk's physical geometry. I don't know much about the best way to do this. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest-current
On Mon, 4 Nov 2002, Terry Lambert wrote:
Kelly Yancey wrote:
I suspect something in lib/libc/net/res_send.c is using special knowledge of
the contents of the socket buffer so calculate the real amount of data that
can be read (which this patch does automatically). I'm looking into it.
...To ensure that the read does not block, and is not issued
until sufficient data exists.
-- Terry
It doesn't matter. It isn't just DNS lookups, mountd fails to run too
because it cannot connect to portmap via localhost. Oddly, in both cases
sendto() is returning with errno = 49 (EADDRNOTAVAIL). I've tracked it down
to this code in sys/netinet/ip_output.c:
/* 127/8 must not appear on wire - RFC1122. */
if ((ntohl(ip-ip_dst.s_addr) IN_CLASSA_NSHIFT) == IN_LOOPBACKNET ||
(ntohl(ip-ip_src.s_addr) IN_CLASSA_NSHIFT) == IN_LOOPBACKNET) {
if ((ifp-if_flags IFF_LOOPBACK) == 0) {
ipstat.ips_badaddr++;
error = EADDRNOTAVAIL;
goto bad;
}
}
Which was last modified in revision 1.150 back in February. However, I
still don't see how adding an extra counter to the sockbuf could possibly
change the set of events required to get to this code, but it is certainly
what is causing EADDRNOTAVAIL to be returned. Needless to say, I'm still
researching it.
Kelly
--
Kelly Yancey -- kbyanc@{posi.net,FreeBSD.org}
FreeBSD, The Power To Serve: http://www.freebsd.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean diskbroken
Nate Lawson wrote: 2. Adding a MI way to call an MD routine that will get the disk's physical geometry. I don't know much about the best way to do this. Perhaps we could invent a Common Access Method (CAM), and make it part of that API... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
alpha tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Mon Nov 4 15:10:42 PST 2002 -- Kernel build for GENERIC completed on Mon Nov 4 15:43:15 PST 2002 -- Kernel build for LINT started on Mon Nov 4 15:43:15 PST 2002 -- === vinum Makefile, line 4517: warning: duplicate script for target geom_bsd.o ignored cc1: warnings being treated as errors /h/des/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_alloc': /h/des/src/sys/dev/aic7xxx/aic79xx.c:4208: warning: unsigned int format, different type arg (arg 3) /h/des/src/sys/dev/aic7xxx/aic79xx.c:4208: warning: unsigned int format, different type arg (arg 4) /h/des/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_init_scbdata': /h/des/src/sys/dev/aic7xxx/aic79xx.c:4601: warning: unsigned int format, different type arg (arg 3) *** Error code 1 Stop in /h/des/obj/h/des/src/sys/LINT. *** Error code 1 Stop in /h/des/src. *** Error code 1 Stop in /h/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest-current
Kelly Yancey wrote:
It doesn't matter. It isn't just DNS lookups, mountd fails to run too
because it cannot connect to portmap via localhost. Oddly, in both cases
sendto() is returning with errno = 49 (EADDRNOTAVAIL). I've tracked it down
to this code in sys/netinet/ip_output.c:
/* 127/8 must not appear on wire - RFC1122. */
if ((ntohl(ip-ip_dst.s_addr) IN_CLASSA_NSHIFT) == IN_LOOPBACKNET ||
(ntohl(ip-ip_src.s_addr) IN_CLASSA_NSHIFT) == IN_LOOPBACKNET) {
if ((ifp-if_flags IFF_LOOPBACK) == 0) {
ipstat.ips_badaddr++;
error = EADDRNOTAVAIL;
goto bad;
}
}
Which was last modified in revision 1.150 back in February. However, I
still don't see how adding an extra counter to the sockbuf could possibly
change the set of events required to get to this code, but it is certainly
what is causing EADDRNOTAVAIL to be returned. Needless to say, I'm still
researching it.
Pretty clear, I should think:
IF the source address is a loopback address
OR the destination address is a loopback address
THEN
IF the interface does not have the IFF_LOOBACK flag
return EADDRNOTAVAIL
...pretty clearly, the new loopback interface doe not set the flag
IFF_LOOPBACK on the interface, as it is supposed to do.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
5.0 Current experiences
I've been hammering 5.0 current for about two months now and I have to say, it's been working really well for me. Are there any gotchas or things I can help test out? I did have a problem on a build as of 10/28 where enabling the MAC functionality in rc.conf would send the system into never never land and require a hard boot. Turning the option off made the problem go away. I noticed there have been some committs to the mac code, so it may be fixed already. My hats off to you guys and gals! Jerry Bell [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest -current
On Mon, Nov 04, 2002 at 10:45:42AM -0800, Kelly Yancey wrote: On Mon, 4 Nov 2002, Giorgos Keramidas wrote: On 2002-11-04 01:16, Hidetoshi Shimokawa [EMAIL PROTECTED] wrote: I have the same problem and reverting rev. 1.134 of /sys/kern/uipc_socket.c fixes the problem. The change might have something wrong with a loopback interface. ... I've had this running on multiple machines for weeks without problems. What is your resolve.conf and nsswitch.conf? Curious, A better question is why you are fixing a non-critical, over-1-year-old bug in networking code this close to the release??? Networking is our bread and butter, and changes to it can be tricky. A known non-critical bug that has existed at least since FBSD 4.2 is better than an unknown one. At this point it time, it is better to just not touch things. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
SIO Overflows in -Current
Is there any way to eliminate (or reduce) the SIO serial overflows that seem to occu often on several FreeBSD systems that I have. It seems to limit remote kernel debugging to about 19.2 Kbaud.. Thanks, -- Glenn Gombert [EMAIL PROTECTED] Never trust any operating system you don't have the source code for -- http://fastmail.fm - Consolidate POP email and Hotmail in one place To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest -current
On 2002-11-04 10:45, Kelly Yancey [EMAIL PROTECTED] wrote:
On Mon, 4 Nov 2002, Giorgos Keramidas wrote:
True. I had been seeing problems with network connections the last
days, and was already in the process of backing out changes one by one
when I saw this. Reverting 1.134 fixes things here. If I put it back
in, strange DNS failures start causing troubles with almost everything
(including Sendmail, fetchmail, ssh).
I've had this running on multiple machines for weeks without
problems. What is your resolve.conf and nsswitch.conf? Curious,
I am running a local named that listens on { 127.0.0.1; }.
My nsswitch.conf contains:
hosts: files dns
and resolv.conf is:
search sea.gr freebsd.org irc.gr ceid.upatras.gr
nameserver 127.0.0.1
The curious thing is that Sendmail or ssh fail to look up hostnames,
while running host(1) works. I don't know if this is of any help, but
if you need more data about the local setup let me know.
Thanks for looking into this,
Giorgos.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
uuid.h is not C++ safe
I was just about to put the new DCE 1.1 UUID functions into use in some C++ code, but linking fails because the function prototypes in uuid.h are not protected with the __cplusplus/extern C bits. It's easy enough for me to fix my local copy, but I'm sure this same thing could trip up other people. -Patrick -- Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED]| 2274 Howe Hall Room 2624 PGP: http://www.137.org/patrick/pgp.txt | T: +1.515.294.4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest-current
On Mon, 4 Nov 2002, Terry Lambert wrote:
Kelly Yancey wrote:
It doesn't matter. It isn't just DNS lookups, mountd fails to run too
because it cannot connect to portmap via localhost. Oddly, in both cases
sendto() is returning with errno = 49 (EADDRNOTAVAIL). I've tracked it down
to this code in sys/netinet/ip_output.c:
/* 127/8 must not appear on wire - RFC1122. */
if ((ntohl(ip-ip_dst.s_addr) IN_CLASSA_NSHIFT) == IN_LOOPBACKNET ||
(ntohl(ip-ip_src.s_addr) IN_CLASSA_NSHIFT) == IN_LOOPBACKNET) {
if ((ifp-if_flags IFF_LOOPBACK) == 0) {
ipstat.ips_badaddr++;
error = EADDRNOTAVAIL;
goto bad;
}
}
Which was last modified in revision 1.150 back in February. However, I
still don't see how adding an extra counter to the sockbuf could possibly
change the set of events required to get to this code, but it is certainly
what is causing EADDRNOTAVAIL to be returned. Needless to say, I'm still
researching it.
Pretty clear, I should think:
IF the source address is a loopback address
OR the destination address is a loopback address
THEN
IF the interface does not have the IFF_LOOBACK flag
return EADDRNOTAVAIL
...pretty clearly, the new loopback interface doe not set the flag
IFF_LOOPBACK on the interface, as it is supposed to do.
-- Terry
No, it turns out I'm an idiot: somehow the address on loopback got deleted
so it was trying to use my default route. So I was on a wild goose chase. :|
Oddly enough, though, once I re-added 127.0.0.1/8 to my localhost:
# cat resolv.conf
search nttmcl.com
nameserver 127.0.0.1
# ps auwwwx | grep named
root 320 0.0 0.8 2600 2160 ?? Is5:11PM 0:00.03 named
# ping www.freebsd.org
PING www.freebsd.org (216.136.204.117): 56 data bytes
64 bytes from 216.136.204.117: icmp_seq=0 ttl=50 time=16.343 ms
64 bytes from 216.136.204.117: icmp_seq=1 ttl=50 time=8.764 ms
^C
--- www.freebsd.org ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 8.764/12.553/16.343/3.789 ms
# ping www.yahoo.com
blocks forever
Go figure. I've said it before and I'll say it again...I'm working on it.
:|
Kelly
--
Kelly Yancey -- kbyanc@{posi.net,FreeBSD.org}
Though [the people] may acquiesce, they cannot approve what they do not
understand. --Thomas Jefferson, 1792.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest-current
On Mon, 4 Nov 2002, David O'Brien wrote:
On Mon, Nov 04, 2002 at 10:45:42AM -0800, Kelly Yancey wrote:
On Mon, 4 Nov 2002, Giorgos Keramidas wrote:
On 2002-11-04 01:16, Hidetoshi Shimokawa [EMAIL PROTECTED] wrote:
I have the same problem and reverting rev. 1.134 of
/sys/kern/uipc_socket.c fixes the problem.
The change might have something wrong with a loopback interface.
...
I've had this running on multiple machines for weeks without problems. What
is your resolve.conf and nsswitch.conf? Curious,
A better question is why you are fixing a non-critical, over-1-year-old
bug in networking code this close to the release??? Networking is our
bread and butter, and changes to it can be tricky. A known non-critical
bug that has existed at least since FBSD 4.2 is better than an unknown
one. At this point it time, it is better to just not touch things.
I'm not trying to fix a bug in ancient code. I'm trying to track down a
very specific bug that is reported to be related to a commit I made last
week. However, so far, I have not found how the two are related. I've just
been trying to keep the people who are affected by the bug in the loop while
I'm tracking it down.
Kelly
--
Kelly Yancey -- kbyanc@{posi.net,FreeBSD.org}
Join distributed.net Team FreeBSD: http://www.posi.net/freebsd/Team-FreeBSD/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest-current
On Tue, 5 Nov 2002, Giorgos Keramidas wrote:
On 2002-11-04 10:45, Kelly Yancey [EMAIL PROTECTED] wrote:
On Mon, 4 Nov 2002, Giorgos Keramidas wrote:
True. I had been seeing problems with network connections the last
days, and was already in the process of backing out changes one by one
when I saw this. Reverting 1.134 fixes things here. If I put it back
in, strange DNS failures start causing troubles with almost everything
(including Sendmail, fetchmail, ssh).
I've had this running on multiple machines for weeks without
problems. What is your resolve.conf and nsswitch.conf? Curious,
I am running a local named that listens on { 127.0.0.1; }.
My nsswitch.conf contains:
hosts: files dns
and resolv.conf is:
search sea.gr freebsd.org irc.gr ceid.upatras.gr
nameserver 127.0.0.1
The curious thing is that Sendmail or ssh fail to look up hostnames,
while running host(1) works. I don't know if this is of any help, but
if you need more data about the local setup let me know.
Thanks for looking into this,
Giorgos.
Thanks for the info. Are you sure that you only reverted the one delta?
Oddly, when I do the same I still have trouble resolving via localhost (i.e.
with or without revision 1.134). I can only get DNS via localhost working
again by explicitely adding 127.0.0.1 to lo0.
If anything I suspect that something is preventing 127.0.0.1 from being
assigned to lo0 at boot (maybe my commit, but I don't see how). But again,
I'm still looking into it. :|
Kelly
--
Kelly Yancey -- kbyanc@{posi.net,FreeBSD.org}
Visit the BSD driver database: http://www.posi.net/freebsd/drivers/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest -current
On Mon, Nov 04, 2002 at 05:47:39PM -0800, Kelly Yancey wrote: A better question is why you are fixing a non-critical, over-1-year-old bug in networking code this close to the release??? Networking is our bread and butter, and changes to it can be tricky. A known non-critical bug that has existed at least since FBSD 4.2 is better than an unknown one. At this point it time, it is better to just not touch things. I'm not trying to fix a bug in ancient code. I'm trying to track down a very specific bug that is reported to be related to a commit I made last week. However, so far, I have not found how the two are related. I've just been trying to keep the people who are affected by the bug in the loop while I was speaking of your commit last week to uipc_socket.c: revision 1.134 date: 2002-11-01 21:27:59; author: kbyanc; state: Exp; lines: +1 -1 ... PR: 30634 PR 30634 is over a year old and is classified as non-critical. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest -current
On 2002-11-04 18:38, Kelly Yancey [EMAIL PROTECTED] wrote: Thanks for the info. Are you sure that you only reverted the one delta? Yes. I just recompiled the kernel from -rHEAD and started logging things while I connected to my dialup provider. Apparently lo0 does have the 127.0.0.1 address *and* the LOOPBACK flag but somehow fails. When (near the end of the following log) I back only this change out, the problems go away :/ The strange thing is that my named listening on lo0 DOES reply, as you can see from the tcpdump output, but the reply never reaches the ssh process that initiated the query. = keramida@gray[05:05]/home/keramida$ ssh -l charon -p 666 -v labs.gr OpenSSH_3.5p1 FreeBSD-20021029, SSH protocols 1.5/2.0, OpenSSL 0x0090607f debug1: Reading configuration data /home/keramida/.ssh/config debug1: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: ssh_connect: needpriv 0 ^C root@gray[05:04]/root# tcpdump -i lo0 -s 128 -v -n tcpdump: listening on lo0 05:05:34.616515 127.0.0.1.49181 127.0.0.1.53: [udp sum ok] 24818+ ? labs.gr. (25) (ttl 64, id 20931, len 53) 05:05:34.618115 127.0.0.1.53 127.0.0.1.49181: [udp sum ok] 24818 0/1/0 (66) (ttl 64, id 2744, len 94) 05:05:34.619452 127.0.0.1.49182 127.0.0.1.53: [udp sum ok] 24819+ A? labs.gr. (25) (ttl 64, id 63225, len 53) 05:05:34.621080 127.0.0.1.53 127.0.0.1.49182: 24819 1/6/6 labs.gr. A 62.103.160.6 (279) (ttl 64, id 1753, len 307) 05:05:39.621503 127.0.0.1.49183 127.0.0.1.53: [udp sum ok] 24819+ A? labs.gr. (25) (ttl 64, id 31195, len 53) 05:05:39.623584 127.0.0.1.53 127.0.0.1.49183: 24819 1/6/6 labs.gr. A 62.103.160.6 (279) (ttl 64, id 5785, len 307) 05:05:49.621965 127.0.0.1.49184 127.0.0.1.53: [udp sum ok] 24819+ A? labs.gr. (25) (ttl 64, id 34796, len 53) 05:05:49.624029 127.0.0.1.53 127.0.0.1.49184: 24819 1/6/6 labs.gr. A 62.103.160.6 (279) (ttl 64, id 60299, len 307) ^C 8 packets received by filter 0 packets dropped by kernel root@gray[05:07]/usr/src/sys/kern# cvs -qR diff -kk -u -r1.133 -r1.134 uipc_socket.c | patch -p0 -R ... root@gray[05:07]/usr/src/sys/kern# cd ../i386/conf root@gray[05:08]/usr/src/sys/i386/conf# config -g -d /usr/obj/usr/src/sys/GRAY GRAY Kernel build directory is /usr/obj/usr/src/sys/GRAY Don't forget to do a ``make depend'' root@gray[05:08]/usr/src/sys/i386/conf# cd /usr/obj/usr/src/sys/GRAY root@gray[05:08]/usr/obj/usr/src/sys/GRAY# rm uipc_socket.o root@gray[05:08]/usr/obj/usr/src/sys/GRAY# make -DNO_MODULES all make -DNO_MODULES install [ reboot after backout ] keramida@gray[05:12]/home/keramida$ ssh -l charon -p 666 -v labs.gr OpenSSH_3.5p1 FreeBSD-20021029, SSH protocols 1.5/2.0, OpenSSL 0x0090607f debug1: Reading configuration data /home/keramida/.ssh/config debug1: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: ssh_connect: needpriv 0 debug1: Connecting to labs.gr [62.103.160.6] port 666. debug1: Connection established. ... [ and it works ] = To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest-current
On Mon, 4 Nov 2002, David O'Brien wrote:
On Mon, Nov 04, 2002 at 05:47:39PM -0800, Kelly Yancey wrote:
A better question is why you are fixing a non-critical, over-1-year-old
bug in networking code this close to the release??? Networking is our
bread and butter, and changes to it can be tricky. A known non-critical
bug that has existed at least since FBSD 4.2 is better than an unknown
one. At this point it time, it is better to just not touch things.
I'm not trying to fix a bug in ancient code. I'm trying to track down a
very specific bug that is reported to be related to a commit I made last
week. However, so far, I have not found how the two are related. I've just
been trying to keep the people who are affected by the bug in the loop while
I was speaking of your commit last week to uipc_socket.c:
revision 1.134
date: 2002-11-01 21:27:59; author: kbyanc; state: Exp; lines: +1 -1
...
PR: 30634
PR 30634 is over a year old and is classified as non-critical.
It was important to me. I ran into the problem independently and have been
running the committed patches for 2 weeks on multiple machines. However, none
of the machines made UDP connections via lo0 so I didn't spot the bug before
commit. However, since commit I have seen 4 reports of people having trouble
resolving via localhost, 2 of which claim the backing out the commit solves
their problems. I'm actively tracking it down (as my numerous updates
throughout the day should indicate) and if I don't find the problem soon I
will revert the delta in question. This is code we use at work and I
certainly want to fix the bug if it turns out to be related to my commit.
Kelly
--
Kelly Yancey -- kbyanc@{posi.net,FreeBSD.org}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest-current
On Tue, 5 Nov 2002, Giorgos Keramidas wrote:
On 2002-11-04 18:38, Kelly Yancey [EMAIL PROTECTED] wrote:
Thanks for the info. Are you sure that you only reverted the one delta?
Yes. I just recompiled the kernel from -rHEAD and started logging
things while I connected to my dialup provider. Apparently lo0 does
have the 127.0.0.1 address *and* the LOOPBACK flag but somehow fails.
When (near the end of the following log) I back only this change out,
the problems go away :/
Thanks for the great trace and your patience. I believe I found the root of
the problem. Could you please try the attached patch? I'm afraid that
if I hadn't gotten thown off this morning be my lo0 lacking a
127.0.0.1 address I probably would have found it much, much sooner
(it's pretty obvious in hindsight). At the very least, I also caught a
couple of pieces of code that are manipulating the socket buffer behind
sballoc() and sbfree()'s back so I've modified them to update the sb_cc
counter directly also.
Let me know if this fixes things for you. Thanks,
Kelly
--
Kelly Yancey -- kbyanc@{posi.net,FreeBSD.org}
Democracy is a device that insures we shall be governed no better than we
deserve. -- George Bernard Shaw
Index: kern/uipc_socket.c
===
RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v
retrieving revision 1.135
diff -u -p -r1.135 uipc_socket.c
--- kern/uipc_socket.c 2 Nov 2002 05:14:30 - 1.135
+++ kern/uipc_socket.c 5 Nov 2002 04:14:20 -
@@ -1794,7 +1794,7 @@ filt_soread(struct knote *kn, long hint)
return (1);
if (kn-kn_sfflags NOTE_LOWAT)
return (kn-kn_data = kn-kn_sdata);
- return (kn-kn_data = so-so_rcv.sb_lowat);
+ return (so-so_rcv.sb_cc = so-so_rcv.sb_lowat);
}
static void
Index: kern/uipc_socket2.c
===
RCS file: /home/ncvs/src/sys/kern/uipc_socket2.c,v
retrieving revision 1.105
diff -u -p -r1.105 uipc_socket2.c
--- kern/uipc_socket2.c 2 Nov 2002 05:14:30 - 1.105
+++ kern/uipc_socket2.c 5 Nov 2002 04:19:05 -
@@ -705,6 +705,8 @@ sbcompress(sb, m, n)
(unsigned)m-m_len);
n-m_len += m-m_len;
sb-sb_cc += m-m_len;
+ if (m-m_type != MT_DATA)
+ sb-sb_ctl += m-m_len;
m = m_free(m);
continue;
}
@@ -774,6 +776,8 @@ sbdrop(sb, len)
m-m_len -= len;
m-m_data += len;
sb-sb_cc -= len;
+ if (m-m_type != MT_DATA)
+ sb-sb_ctl -= len;
break;
}
len -= m-m_len;
minor nit in /usr/src/usr.sbin/apm/apm.c
Stupid question perhaps, but was the inclusion of sys/file.h and sys/ioctl.h twice in /usr/src/usr.sbin/apm/apm.c done intentionally? Thanks Andrew Lankford To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest -current
At Tue, 5 Nov 2002 03:12:05 +0200, Giorgos Keramidas wrote: The curious thing is that Sendmail or ssh fail to look up hostnames, while running host(1) works. I don't know if this is of any help, but if you need more data about the local setup let me know. host(or dig, nslookup) doesn't use resolver in libc. The change affects processes which uses kevent(). /\ Hidetoshi Shimokawa \/ [EMAIL PROTECTED] PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
What's the status of devfs(8)?
When I try commands like: #devfs rule add path speaker mode 666 I get the following reply: devfs rule: ioctl DEVFSIO_RADD: Input/output error but /dev/devctl is in my /dev (devfs) partition. My kernel: FreeBSD bogushost2 5.0-CURRENT FreeBSD 5.0-CURRENT #17: Mon Nov 4 20:27:52 EST 2002 root@bogushost2:/usr/obj/usr/src/sys/ARL5KERNEL i386 Anyway I've tried a couple of buildworlds over the past week or two and still get the same behavior. How do I go about debugging this? Andrew Lankford To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest -current
At 08:25 PM 11/4/2002 -0800, Kelly Yancey wrote:
On Tue, 5 Nov 2002, Giorgos Keramidas wrote:
On 2002-11-04 18:38, Kelly Yancey [EMAIL PROTECTED] wrote:
Thanks for the info. Are you sure that you only reverted the one delta?
Yes. I just recompiled the kernel from -rHEAD and started logging
things while I connected to my dialup provider. Apparently lo0 does
have the 127.0.0.1 address *and* the LOOPBACK flag but somehow fails.
When (near the end of the following log) I back only this change out,
the problems go away :/
Thanks for the great trace and your patience. I believe I found the root of
the problem. Could you please try the attached patch? I'm afraid that
if I hadn't gotten thown off this morning be my lo0 lacking a
127.0.0.1 address I probably would have found it much, much sooner
(it's pretty obvious in hindsight). At the very least, I also caught a
couple of pieces of code that are manipulating the socket buffer behind
sballoc() and sbfree()'s back so I've modified them to update the sb_cc
counter directly also.
Let me know if this fixes things for you. Thanks,
Kelly
--
Kelly Yancey -- kbyanc@{posi.net,FreeBSD.org}
Democracy is a device that insures we shall be governed no better than we
deserve. -- George Bernard Shaw
This patch fixes a bug I've noticed for the past few days.
Connecting to a FreeBSD current box via ssh2 from Win-2000 (local network)
It just started happening in the past few days.
I could connect but it would take about a minute to connect.
Now it's back instant connect with patch
Manfred
==
|| [EMAIL PROTECTED] ||
|| Ph. (415) 681-6235 ||
==
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: WIne freezes -current for half a year
On Mon, 2002-11-04 at 22:00, Jan Stocker wrote: It'd probably be a good idea to try it again before reporting it as if it were still not working. It may or may not have been fixed by the signal and FP register state commits, etc., so just because it was broken doesn't mean it's broken now. Even if it *is* still broken, it could be broken in an entirely different way... 8-). It is broken with the same symtoms for the last months. a) FreeBSD freezes... you've to do a cold start, no keys or anything work b) FreeBSD reboots after a few secs of doing nothin' c) wine / wineserver process hangs in the background, doing nothing, consuming cpu time and cant be killed by kill -9 . My system is from 26. October. Not new enough? Tonight .i'll get the newest one and recompile the newest wine and tomorrow (8.00 CET) you'll get a dmesg / uname -a /sysctl -a for my system, i'm sure with a non-working wine. We've a compile problem for wine, which should be fixed first before we con continue this thread Jan FYI: text_i386.o context_i386.c context_i386.c: In function `get_thread_context': context_i386.c:376: structure has no member named `dr0' context_i386.c:377: structure has no member named `dr1' context_i386.c:378: structure has no member named `dr2' context_i386.c:379: structure has no member named `dr3' context_i386.c:380: structure has no member named `dr6' context_i386.c:381: structure has no member named `dr7' context_i386.c: In function `set_thread_context': context_i386.c:440: structure has no member named `dr0' context_i386.c:441: structure has no member named `dr1' context_i386.c:442: structure has no member named `dr2' context_i386.c:443: structure has no member named `dr3' context_i386.c:444: structure has no member named `dr4' context_i386.c:445: structure has no member named `dr5' context_i386.c:446: structure has no member named `dr6' context_i386.c:447: structure has no member named `dr7' gmake[1]: *** [context_i386.o] Error 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Why is my -current system Hard Locking?
On Mon, 4 Nov 2002, Joel M. Baldwin wrote: I'm getting quite frustrated with -current. I've been running it for years and had relatively few problems. However for quite some time now I've had a problem with Hard Locks. By Hard Lock I mean that the system doesn't respond to ether traffic, the keyboard doesn't respond, the capslock, numlock, and scroll lock keys do nothing, the corresponding LEDs don't light, and ctrl/alt/del doesn't reboot the system. The only out is to hit reset. I have the same problem on a pair uniprocessor i810s with Celeron 500's (not OC either). It used to happen every night. The power light turns off on the front of the case but everything else is still running. Numlock is frozen and only a hard power down does anything. I've left one or the other of the boxes running -stable for over 30 days uptime without a problem. I disabled ACPI and now the box runs for a week before doing the same thing. I have no way to get a trace or anything. Very frustrating to debug. Any ideas? -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WIne freezes -current for half a year
We've a compile problem for wine, which should be fixed first before we con continue this thread Jan FYI: text_i386.o context_i386.c context_i386.c: In function `get_thread_context': context_i386.c:376: structure has no member named `dr0' context_i386.c:377: structure has no member named `dr1' context_i386.c:378: structure has no member named `dr2' context_i386.c:379: structure has no member named `dr3' context_i386.c:380: structure has no member named `dr6' context_i386.c:381: structure has no member named `dr7' context_i386.c: In function `set_thread_context': context_i386.c:440: structure has no member named `dr0' context_i386.c:441: structure has no member named `dr1' context_i386.c:442: structure has no member named `dr2' context_i386.c:443: structure has no member named `dr3' context_i386.c:444: structure has no member named `dr4' context_i386.c:445: structure has no member named `dr5' context_i386.c:446: structure has no member named `dr6' context_i386.c:447: structure has no member named `dr7' gmake[1]: *** [context_i386.o] Error 1 Custom patch using something like (from machine/reg.h) #define DBREG_DRX(d,x) (d-dr[(x)]) /* reference dr0 - dr7 by register number */ has disappeared. Will fix and send a pr tonight. Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: umass CF geometry problems, was Re: fdisk -BI ob clean disk broken
In message [EMAIL PROTECTED], Nate Lawson writ es: On Mon, 4 Nov 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Nate Lawson writ es: It might be more useful for GEOM to query the BIOS for the physical values and provide a way for upper levels (like CAM) to retrieve this. This is a driver task. besides GEOM is above CAM, not below it. Ok. There are two things that would be useful: 1. Merging the multiple LBA to C/H/S calculations (aic7xxx, umass, ...) to one CAM convenience routine. Well, it will have to be MD, because PC98 seems to prefer different geometries than PC bios. -- 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: libc size
hi, there! On Mon, Nov 04, 2002 at 01:57:35PM -0800, David O'Brien wrote: another 2.4M for /rescue. That makes it less impressive. I don't find the duplication appealing, either. (Why not just put the /rescue versions directly into /bin and /sbin? That would be smaller still, Because that would nullify one of the big reasons for making /bin and /sbin shared -- so one can dlopen(3). We can't, for instance, get a proper nsswitch implementation until we make /bin and /sbin dynamic. Before someone says you can dlopen() from static binaries in order to implement nsswitch, please provide the patch proving it. Our best FreeBSD minds don't think it can be done properly and sanely. I have the patch. Currently it is made against RELENG_4 and I have a couple of questions about alpha (however it works on alpha too with a few hacks). Unfortunately, jdp does not have enough time to review it and I have lack of time to port it to -current (that would not be that hard but since sparc64 is now Tier-1 platform the patch should be ported to sparc64 too but I do not have sparc64 hardware and access to panther is very slow from my home). What is the right place to post the patch and test program demonstrating dlopen for statically linked programs? /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Can't resolve hosts via dns on the command line with latest-current
Kelly Yancey wrote: Thanks for the great trace and your patience. I believe I found the root of the problem. Could you please try the attached patch? Works for me, thanks. Doug To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: libc size
Apparently, On Tue, Nov 05, 2002 at 12:54:54PM +0600, Max Khon said words to the effect of; hi, there! On Mon, Nov 04, 2002 at 01:57:35PM -0800, David O'Brien wrote: another 2.4M for /rescue. That makes it less impressive. I don't find the duplication appealing, either. (Why not just put the /rescue versions directly into /bin and /sbin? That would be smaller still, Because that would nullify one of the big reasons for making /bin and /sbin shared -- so one can dlopen(3). We can't, for instance, get a proper nsswitch implementation until we make /bin and /sbin dynamic. Before someone says you can dlopen() from static binaries in order to implement nsswitch, please provide the patch proving it. Our best FreeBSD minds don't think it can be done properly and sanely. I have the patch. Currently it is made against RELENG_4 and I have a couple of questions about alpha (however it works on alpha too with a few hacks). Unfortunately, jdp does not have enough time to review it and I have lack of time to port it to -current (that would not be that hard but since sparc64 is now Tier-1 platform the patch should be ported to sparc64 too but I do not have sparc64 hardware and access to panther is very slow from my home). What is the right place to post the patch and test program demonstrating dlopen for statically linked programs? Put it up somehere on the web or email it to the list. I'd be interested in looking at it. Jake To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: libc size
hi, there! On Tue, Nov 05, 2002 at 02:18:23AM -0500, Jake Burkholder wrote: Before someone says you can dlopen() from static binaries in order to implement nsswitch, please provide the patch proving it. Our best FreeBSD minds don't think it can be done properly and sanely. I have the patch. Currently it is made against RELENG_4 and I have a couple of questions about alpha (however it works on alpha too with a few hacks). Unfortunately, jdp does not have enough time to review it and I have lack of time to port it to -current (that would not be that hard but since sparc64 is now Tier-1 platform the patch should be ported to sparc64 too but I do not have sparc64 hardware and access to panther is very slow from my home). What is the right place to post the patch and test program demonstrating dlopen for statically linked programs? Put it up somehere on the web or email it to the list. I'd be interested in looking at it. Ok, I put the patch and test program to http://people.freebsd.org/~fjoe/libdl.tar.bz2. Patches are made against RELENG_4 (and all tests were done on RELENG_4) but it will not be that hard to port everything to -CURRENT. This is just a proof-of-concept work-in-progress. The plan is to add this stuff (rtld sources with -DLIBDL) to libc.a so statically linked programe will have dlopen/dlsym etc. Problems with current patches are: - I do not know what to do on alpha with _GOT_END_ and _GLOBAL_OFFSET_TABLE_ symbols. I had to use ld.so.script to solve missing _GOT_END_ problem and ifdef out _GLOBAL_OFFSET_TABLE_ usage from alpha/reloc.c for second problem. An advice from alpha rtld guru will be very useful - gdb support for shared objects dlopened from statically linked program is broken - rtld_exit() is not called on exit so fini functions are not called on exit - probably more stuff could be #ifdef'ed out from rtld when it is compiled with -DLIBDL - xmalloc and friends names in rtld sources probably should be prepended with an underscore to prevent name clashes (if this stuff will be included in libc.a) Any comments, suggestions, patches will be very appreciated. /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
