Re: some 5.0 oddities
> >
> > 1/ Everytime I ssh to the box there are 4 connection attempts to UDP
> > port 53 from itself. ie:
> >
> > Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53
>from 172.22.2.12:49205
> > Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53
>from 172.22.2.12:49206
> > Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53
>from 172.22.2.12:49207
> > Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53
>from 172.22.2.12:49208
> >
> > I have log_in_vain="1" and /etc/resolv.conf points to 172.22.2.1 only.
>
> Is there any case 172.22.2.1 redirects DNS queries back to 172.22.2.22
> for some subdomain that it believes 172.22.2.22 is more fit to reply
> for? What is the setup of 172.22.2.1?
>
No.
172.22.2.1 is authorative for 172.22.2/24 and will only forward requests
upstream.
> > 2/ The console doesn't "wake up" if its in screensaver mode (I use
> > warp_saver.ko) when messages are sent to it (like the ones above).
>
> This is a result of th following sysctl:
>
> hw.syscons.saver.keybonly: 1
>
> It defaults to 1 so you will have to edit your /etc/sysctl.conf and
> set it to zero to enable the old behavior of syscons.
>
Thanks. One wonders why the old default behaviour was changed though...
> > 3/ 'ps ul' repeats columns: PID, VSZ, RSS, TT, STAT, TIME, COMMAND
> > (hmm, this also happens on 4.7)
>
> I'm not sure about this one. It seems to me that "ps l" prints a lot
> of the information that "ps u" would print already. The repetition is
> most likely a ps bug though.
>
Yes, its a bug - [EMAIL PROTECTED] has fixed it now.
> > 4/ You can't interrupt the BTX loader anymore. Used to be able to
> > get the ':' prompt before the kernel loaded.
>
> I regularly interrupt my loader at any stage.
> Can you elaborate a bit on this one?
>
When 4.7 boots, the 'propeller' starts spinning, then momentarily stops.
When you press a key, you get a ':' prompt. Otherwise it continues to load
kernel.
I'll have to reboot a box to fully explain, which I cant do right now...
> > 5/ disklabel doesn't work: [...]
>
> ENOCLUE.
>
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: some 5.0 oddities
Andy Farkas wrote: 5/ disklabel doesn't work: team2# disklabel ad4 disklabel: ioctl DIOCGDINFO: Operation not supported by device team2# disklabel -r ad4 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) I think you need to give the full device name like "disklabel ad4s1". Here is a snippet from the release notes: * Note:* GEOM-enabled kernels no longer support ``compatability slices''. This feature (supported on the i386 and pc98 only) allowed a user to refer to a disk partition without specifying an MBR slice (e.g. /dev/ad0a); the kernel would automatically find the first applicable FreeBSD slice and use it. On GEOM-enabled kernels (the default), only the full partition names (e.g. /dev/ad0s1a) are allowed when referring to partitions within MBR slices. This change should affect very few users. Andy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How to build -current and install to empty slice?
On Fri, Jan 17, 2003 at 01:40:43PM -0800, Darren Pilgrim wrote: > I'd like to try out -current, however I'm not willing to clobber by working > 4.7 install. How do build -current on 4.7p3 away from my RELENG_4_7 > source, then install to a seperate, pre-partitioned slice? I haven't tried it, but perhaps you could cvs co/cvsup the -current tree to, say, /usr/current, then use the DESTDIR knob to installworld/installkernel to your target mount. See jail(8) for more ideas, including how to initialise /etc. If it doesn't work, file a PR :) > Is it ok to create the filesystems with 4.7p3's newfs? I don't see why not. 5.0 will happily mount a UFS partition created by 4.X. Joshua To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: some 5.0 oddities
On 2003-01-18 13:12, Andy Farkas <[EMAIL PROTECTED]> wrote: > > Some of observations of 5.0-RELEASE: > > 1/ Everytime I ssh to the box there are 4 connection attempts to UDP > port 53 from itself. ie: > > Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53 >from 172.22.2.12:49205 > Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53 >from 172.22.2.12:49206 > Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53 >from 172.22.2.12:49207 > Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53 >from 172.22.2.12:49208 > > I have log_in_vain="1" and /etc/resolv.conf points to 172.22.2.1 only. Is there any case 172.22.2.1 redirects DNS queries back to 172.22.2.22 for some subdomain that it believes 172.22.2.22 is more fit to reply for? What is the setup of 172.22.2.1? > 2/ The console doesn't "wake up" if its in screensaver mode (I use > warp_saver.ko) when messages are sent to it (like the ones above). This is a result of th following sysctl: hw.syscons.saver.keybonly: 1 It defaults to 1 so you will have to edit your /etc/sysctl.conf and set it to zero to enable the old behavior of syscons. > 3/ 'ps ul' repeats columns: PID, VSZ, RSS, TT, STAT, TIME, COMMAND > (hmm, this also happens on 4.7) I'm not sure about this one. It seems to me that "ps l" prints a lot of the information that "ps u" would print already. The repetition is most likely a ps bug though. > 4/ You can't interrupt the BTX loader anymore. Used to be able to > get the ':' prompt before the kernel loaded. I regularly interrupt my loader at any stage. Can you elaborate a bit on this one? > 5/ disklabel doesn't work: [...] ENOCLUE. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
tunefs using libufs.
Can I get some tests of these changes to make tunefs use libufs?
Thanx,
juli.
%%%
Index: Makefile
===
RCS file: /home/ncvs/src/sbin/tunefs/Makefile,v
retrieving revision 1.6
diff -d -u -r1.6 Makefile
--- Makefile4 Dec 2001 02:19:58 - 1.6
+++ Makefile18 Jan 2003 05:08:29 -
@@ -3,5 +3,6 @@
PROG= tunefs
MAN= tunefs.8
+LDADD= -lufs
.include
Index: tunefs.c
===
RCS file: /home/ncvs/src/sbin/tunefs/tunefs.c,v
retrieving revision 1.33
diff -d -u -r1.33 tunefs.c
--- tunefs.c27 Nov 2002 02:18:57 - 1.33
+++ tunefs.c18 Jan 2003 05:08:29 -
@@ -60,6 +60,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -69,26 +70,17 @@
/* the optimization warning string template */
#defineOPTWARN "should optimize for %s with minfree %s %d%%"
-union {
- struct fs sb;
- char pad[MAXBSIZE];
-} sbun;
-#definesblock sbun.sb
+struct uufsd disk;
+#definesblock disk.d_fs
int fi;
long dev_bsize = 1;
-void bwrite(ufs2_daddr_t, const char *, int);
-int bread(ufs2_daddr_t, char *, int);
-void getsb(struct fs *, const char *);
-void putsb(struct fs *, const char *, int);
void usage(void);
void printfs(void);
int
-main(argc, argv)
- int argc;
- char *argv[];
+main(int argc, char *argv[])
{
char *special;
const char *name;
@@ -227,7 +219,12 @@
}
if (fs == NULL && (st.st_mode & S_IFMT) == S_IFDIR)
errx(10, "%s: unknown file system", special);
- getsb(&sblock, special);
+ if (ufs_disk_fillout(&disk, special) == -1) {
+ if (disk.d_error != NULL)
+ errx(11, "%s: %s", special, disk.d_error);
+ else
+ err(12, "%s", special);
+ }
if (pflag) {
printfs();
@@ -362,7 +359,7 @@
}
}
- putsb(&sblock, special, Aflag);
+ sbwrite(&disk, Aflag);
if (active) {
bzero(&args, sizeof(args));
if (mount("ufs", fs->fs_file,
@@ -374,7 +371,7 @@
}
void
-usage()
+usage(void)
{
fprintf(stderr, "%s\n%s\n%s\n",
"usage: tunefs [-A] [-a enable | disable] [-e maxbpg] [-f avgfilesize]",
@@ -383,66 +380,8 @@
exit(2);
}
-/*
- * Possible superblock locations ordered from most to least likely.
- */
-static int sblock_try[] = SBLOCKSEARCH;
-static ufs2_daddr_t sblockloc;
-
-void
-getsb(fs, file)
- struct fs *fs;
- const char *file;
-{
- int i;
-
- fi = open(file, O_RDONLY);
- if (fi < 0)
- err(3, "cannot open %s", file);
- for (i = 0; sblock_try[i] != -1; i++) {
- if (bread(sblock_try[i], (char *)fs, SBLOCKSIZE))
- err(4, "%s: bad super block", file);
- if ((fs->fs_magic == FS_UFS1_MAGIC ||
-(fs->fs_magic == FS_UFS2_MAGIC &&
- fs->fs_sblockloc == sblock_try[i])) &&
- fs->fs_bsize <= MAXBSIZE &&
- fs->fs_bsize >= sizeof(struct fs))
- break;
- }
- if (sblock_try[i] == -1)
- err(5, "Cannot find file system superblock");
- dev_bsize = fs->fs_fsize / fsbtodb(fs, 1);
- sblockloc = sblock_try[i] / dev_bsize;
-}
-
void
-putsb(fs, file, all)
- struct fs *fs;
- const char *file;
- int all;
-{
- int i;
-
- /*
-* Re-open the device read-write. Use the read-only file
-* descriptor as an interlock to prevent the device from
-* being mounted while we are switching mode.
-*/
- i = fi;
- fi = open(file, O_RDWR);
- close(i);
- if (fi < 0)
- err(3, "cannot open %s", file);
- bwrite(sblockloc, (const char *)fs, SBLOCKSIZE);
- if (all)
- for (i = 0; i < fs->fs_ncg; i++)
- bwrite(fsbtodb(fs, cgsblock(fs, i)),
- (const char *)fs, SBLOCKSIZE);
- close(fi);
-}
-
-void
-printfs()
+printfs(void)
{
warnx("ACLs: (-a) %s",
(sblock.fs_flags & FS_ACLS)? "enabled" : "disabled");
@@ -466,35 +405,4 @@
if (sblock.fs_minfree < MINFREE &&
sblock.fs_optim == FS_OPTTIME)
warnx(OPTWARN, "space", "<", MINFREE);
-}
-
-void
-bwrite(blk, buf, size)
- ufs2_daddr_t blk;
- const char *buf;
- int size;
-{
-
- if (lseek(fi, (off_t)blk * dev_bsize, SEEK_SET) < 0)
- err(6, "FS SEEK");
- if (write(fi, buf, size) != size)
- err(7, "FS WRITE");
-}
-
-int
-bread(bno, buf, cnt)
- ufs2_daddr_t bno;
- char *buf;
- int cnt;
-{
- int i;
-
- if (lseek(fi, (off_t)bno * dev_bsize, SEEK_SET) < 0)
- return(
5.0sparc - panic #2
BTW it's a Ultra10. Please cc: your replies to me since I am not subscribed to this list. Tkx To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
5.0sparc panic
Hi all
During a make clean or a make update with cvsup (not sure now since they were
being run by a script), 5.0-current from a few days go just panic :
panic: hme_txdma_callback: missed end of packet!
Debugger("panic")
Stopped at Debugger+0x1c: ta%xcc, 1
db>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
panic: malloc(M_WAITOK) returned NULL
I just got the following on axp1: panic: malloc(M_WAITOK) returned NULL db_print_backtrace() at db_print_backtrace+0x18 panic() at panic+0x104 malloc() at malloc+0x1a8 initiate_write_inodeblock_ufs1() at initiate_write_inodeblock_ufs1+0xc4 softdep_disk_io_initiation() at softdep_disk_io_initiation+0xa4 spec_strategy() at spec_strategy+0x158 spec_vnoperate() at spec_vnoperate+0x2c bwrite() at bwrite+0x3dc vfs_bio_awrite() at vfs_bio_awrite+0x30c spec_fsync() at spec_fsync+0x1f4 spec_vnoperate() at spec_vnoperate+0x2c sched_sync() at sched_sync+0x1d0 fork_exit() at fork_exit+0x100 exception_return() at exception_return --- root of call graph --- panic Stopped at Debugger+0x34: zapnot v0,#0xf,v0 Any ideas? Kris msg50456/pgp0.pgp Description: PGP signature
some 5.0 oddities
Some of observations of 5.0-RELEASE:
1/ Everytime I ssh to the box there are 4 connection attempts to UDP port
53 from itself. ie:
Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53
from 172.22.2.12:49205
Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53
from 172.22.2.12:49206
Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53
from 172.22.2.12:49207
Jan 18 12:45:17 team2 kernel: Connection attempt to UDP 172.22.2.12:53
from 172.22.2.12:49208
I have log_in_vain="1" and /etc/resolv.conf points to 172.22.2.1 only.
2/ The console doesn't "wake up" if its in screensaver mode (I use
warp_saver.ko) when messages are sent to it (like the ones above).
3/ 'ps ul' repeats columns: PID, VSZ, RSS, TT, STAT, TIME, COMMAND
(hmm, this also happens on 4.7)
4/ You can't interrupt the BTX loader anymore. Used to be able to get the
':' prompt before the kernel loaded.
5/ disklabel doesn't work:
team2# disklabel ad4
disklabel: ioctl DIOCGDINFO: Operation not supported by device
team2# disklabel -r ad4
disklabel: bad pack magic number (label is damaged, or pack is unlabeled)
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: alpha tinderbox failure
On 2003-01-17 16:24, Kris Kennaway <[EMAIL PROTECTED]> wrote: > On Fri, Jan 17, 2003 at 04:16:14PM -0800, Dag-Erling Smorgrav wrote: > > ===> vinum > > "Makefile", line 4437: warning: duplicate script for target "geom_bsd.o" [...] > > /h/des/src/sys/dev/lmc/if_lmc.c:32:2: warning: #warning "The lmc driver i [...] > > /h/des/src/sys/dev/pdq/pdq.c: In function `pdq_initialize': > > /h/des/src/sys/dev/pdq/pdq.c:1606: warning: cast discards qualifiers from [...] > > /h/des/src/sys/pci/meteor.c:149:2: warning: #warning "The meteor driver i [...] > > /h/des/src/sys/pci/simos.c:30:2: warning: #warning "The simos driver is b [...] > > cc1: warnings being treated as errors > > /h/des/src/sys/dev/advansys/adv_isa.c: In function `adv_isa_probe': > > /h/des/src/sys/dev/advansys/adv_isa.c:232: warning: overflow in implicit [...] > > *** Error code 1 > > Am I the only one who thinks that the error message truncation makes > it difficult to see the error? I'm not a kernel hacker, so I might be a bit confused by this because of my lack of kernel foo, but it *is* a bit difficult to read. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
netgraph/usb broken?
There's typos in this, because it didn;t cut/paste properly, but you get the picture. this is cvsup as of about 2 hours ago (and earlier today) linking kernel.debug udbp.o: In function `udbp_attach': /admins/src/sys/dev/usb/udbp.c:358: undefined reference to `ng_newtype' /admins/src/sys/dev/usb/udbp.c:364: undefined reference to `ng_make_node_common' /admins/src/sys/dev/usb/udbp.c:367: undefined reference to `ng_name_node' udbp.o: In function `udbp_attach': /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /admins/src/sys/netgraph/netgraph.h:457: undefined reference to `ng_unref_node' /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' udbp.o: In function `udbp_detach': /admins/src/sys/dev/usb/udbp.c:432: undefined reference to `ng_rmnode_self' udbp.o: In function `udbp_detach': /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /admins/src/sys/netgraph/netgraph.h:457: undefined reference to `ng_unref_node' udbp.o: In function `udbp_in_transfer_cb': /admins/src/sys/dev/usb/udbp.c:513: undefined reference to `ng_package_data' /admins/src/sys/dev/usb/udbp.c:513: undefined reference to `ng_address_hook' /admins/src/sys/dev/usb/udbp.c:513: undefined reference to `ng_snd_item' udbp.o: In function `ng_udbp_newhook': /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /admins/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' udbp.o: In function `ng_udbp_rcvmsg': /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' udbp.o: In function `ng_udbp_rcvmsg': /admins/src/sys/dev/usb/udbp.c:686: undefined reference to `M_NETGRAPH_MSG' /admins/src/sys/dev/usb/udbp.c:714: undefined reference to `ng_address_ID' /admins/src/sys/dev/usb/udbp.c:714: undefined reference to `ng_snd_item' udbp.o: In function `ng_udbp_rcvmsg': /admins/src/sys/netgraph/netgraph.h:689: undefined reference to `dumpitem' udbp.o: In function `ng_udbp_rcvmsg': /admins/src/sys/dev/usb/udbp.c:714: undefined reference to `ng_free_item' /admins/src/sys/dev/usb/udbp.c:715: undefined reference to `M_NETGRAPH_MSG' udbp.o: In function `ng_udbp_rcvdata': /admins/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /admins/src/sys/netgraph/netgraph.h:689: undefined reference to `dumpitem' udbp.o: In function `ng_udbp_rcvdata': /admins/src/sys/dev/usb/udbp.c:734: undefined reference to `ng_free_item' /admins/src/sys/dev/usb/udbp.c:764: undefined reference to `M_NETGRAPH_META' udbp.o: In function `ng_udbp_rmnode': /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /admins/src/sys/netgraph/netgraph.h:457: undefined reference to `ng_unref_node' udbp.o: In function `ng_udbp_rmnode': /admins/src/sys/dev/usb/udbp.c:798: undefined reference to `ng_make_node_common' /admins/src/sys/dev/usb/udbp.c:801: undefined reference to `ng_name_node' udbp.o: In function `ng_udbp_rmnode': /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /admins/src/sys/netgraph/netgraph.h:457: undefined reference to `ng_unref_node' /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' udbp.o: In function `ng_udbp_connect': /admins/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' /admins/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' udbp.o: In function `ng_udbp_disconnect': /admins/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /admins/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /admins/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' /admins/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /admins/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' /admins/src/sys/netgraph/netgraph.h:248: undefined reference to `ng_rmnode_self' udbp.o: In function `udbp_match': /admins/src/sys/dev/usb/udbp.c:223: undefined reference to `ng_parse_int32_type' /admins/src/sys/dev/usb/udbp.c:224: undefined reference to `ng_parse_int32_type' /admins/src/sys/dev/usb/udbp.c:228: undefined reference to `ng_parse_struct_type' /admins/src/sys/dev/usb/udbp.c:249: undefined reference to `ng_parse_int32_type' umass.o: In function `umass_cam_attach_sim': /admins/src/sys/dev/usb/umass.c:2067: undefined reference to `cam_simq_alloc' /admins/src/sys/dev/usb/umass.c:2071: undefined reference to `cam_sim_alloc' /admins/src/sys/dev/usb/umass.c:2077: undefined reference to `cam_simq_free' /admins/src/sys/dev/usb/umass.c:2081: undefined reference to `xpt_bus_register' umass.o: In function `umass_cam_rescan_callback': /admin
Re: VM_METER no longer defined?
On Fri, 17 Jan 2003, Scott Long wrote:
> Craig Rodrigues wrote:
> > Index: vm_param.h
> > ===
> > RCS file: /home/ncvs/src/sys/vm/vm_param.h,v
> > retrieving revision 1.16
> > diff -u -r1.16 vm_param.h
> > --- vm_param.h 2003/01/11 07:29:46 1.16
> > +++ vm_param.h 2003/01/17 23:25:52
> > @@ -89,6 +89,8 @@
> > #define VM_SWAPPING_ENABLED11 /* swapping enabled */
> > #defineVM_MAXID12 /* number of valid vm ids */
> >
> > +#define VM_METER VM_TOTAL /* backwards compatibility, struct vmmeter */
> > +
> > #define CTL_VM_NAMES { \
> > { 0, 0 }, \
> > { "vmtotal", CTLTYPE_STRUCT }, \
> >
> > The only place where VM_METER is used in this directory was in vm_meter.c:
> >
> > 240 SYSCTL_PROC(_vm, VM_METER, vmmeter, CTLTYPE_OPAQUE|CTLFLAG_RD,
> > 241 0, sizeof(struct vmtotal), vmtotal, "S,vmtotal",
> > 242 "System virtual memory statistics");
> >
> > This changed to:
> >
> > 240 SYSCTL_PROC(_vm, VM_TOTAL, vmtotal, CTLTYPE_OPAQUE|CTLFLAG_RD,
> > 241 0, sizeof(struct vmtotal), vmtotal, "S,vmtotal",
> > 242 "System virtual memory statistics");
The sysctl name was changed too (from the confusing but compatible
"vm.vmmeter" to "vm.vmtotal".
The change was mainly about printing the results of the sysctl in sysctl(8).
See followup mail.
> This is ugly and only further perpetuates what appears to be a
> gratuitous API
> change. Let's wait to hear from the submitter (Hiten) and committer
> (Matt) to
> see why this was needed in the first place.
If this change is kept, don't forget to keep the man page (sysctl.3)
to be consistent with the code again.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: alpha tinderbox failure
On Fri, Jan 17, 2003 at 04:16:14PM -0800, Dag-Erling Smorgrav wrote: > ===> vinum > "Makefile", line 4437: warning: duplicate script for target "geom_bsd.o" [...] > /h/des/src/sys/dev/lmc/if_lmc.c:32:2: warning: #warning "The lmc driver i [...] > /h/des/src/sys/dev/pdq/pdq.c: In function `pdq_initialize': > /h/des/src/sys/dev/pdq/pdq.c:1606: warning: cast discards qualifiers from [...] > /h/des/src/sys/pci/meteor.c:149:2: warning: #warning "The meteor driver i [...] > /h/des/src/sys/pci/simos.c:30:2: warning: #warning "The simos driver is b [...] > cc1: warnings being treated as errors > /h/des/src/sys/dev/advansys/adv_isa.c: In function `adv_isa_probe': > /h/des/src/sys/dev/advansys/adv_isa.c:232: warning: overflow in implicit [...] > *** Error code 1 Am I the only one who thinks that the error message truncation makes it difficult to see the error? Kris msg50451/pgp0.pgp Description: PGP signature
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 Fri Jan 17 15:08:43 PST 2003 -- >>> Kernel build for GENERIC completed on Fri Jan 17 15:44:03 PST 2003 -- >>> Kernel build for LINT started on Fri Jan 17 15:44:04 PST 2003 -- ===> vinum "Makefile", line 4437: warning: duplicate script for target "geom_bsd.o" [...] /h/des/src/sys/dev/lmc/if_lmc.c:32:2: warning: #warning "The lmc driver i [...] /h/des/src/sys/dev/pdq/pdq.c: In function `pdq_initialize': /h/des/src/sys/dev/pdq/pdq.c:1606: warning: cast discards qualifiers from [...] /h/des/src/sys/pci/meteor.c:149:2: warning: #warning "The meteor driver i [...] /h/des/src/sys/pci/simos.c:30:2: warning: #warning "The simos driver is b [...] cc1: warnings being treated as errors /h/des/src/sys/dev/advansys/adv_isa.c: In function `adv_isa_probe': /h/des/src/sys/dev/advansys/adv_isa.c:232: warning: overflow in implicit [...] *** 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
STABLE->CURRENT rl fails
Trial upgrade from a laptop running stable just fine for the last six months to current (GENERIC) is still failing with the same symptoms: On board rl0 comes up just fine, but a transfer hangs after about 150KB or so. After a minute or two, the laptop reboots. That's at 100BaseTX, plus the various mediaopts. At 10BaseT, it takes longer during a file transfer to trigger the problem, but it gets there after a megabyte or so. I've attached a dmesg, interesting "lock order reversal" item in it. I'm willing to dedicate a week or so to get this thing up because it's one of those ACPI only laptops. Tell me what to do to get better info... Thank you, Russell Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Fri Jan 17 08:55:47 MST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src-current/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc06c3000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06c30a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1991920132 Hz CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz (1991.92-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febf9ff real memory = 520093696 (496 MB) avail memory = 497917952 (474 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 Using $PIR table, 7 entries at 0xc00fdf50 Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe800-0xe8ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 2.0 on pci0 isa0: on isab0 ohci0: mem 0xe900-0xe9000fff irq 11 at device 2.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Mitsumi Mitsumi Quick Scroll Mouse (USB), rev 1.00/1.05, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. ohci1: mem 0xe9001000-0xe9001fff irq 10 at device 2.3 on pci0 usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered atapci0: port 0x1000-0x100f at device 2.5 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 2.7 (no driver attached) rl0: port 0x1400-0x14ff mem 0x6004800-0x60048ff irq 11 at device 10.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:90:f5:12:59:3b miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at device 11.0 (no driver attached) cbb0: mem 0x8800-0x88000fff irq 5 at device 12.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 acpi_button0: on acpi0 acpi_button1: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_lid0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A acpi_ec0: port 0x66,0x62 on acpi0 orm0: at iomem 0xdc000-0xd,0xc-0xcbfff on isa0 pmtimer0 on isa0 fdc0: cannot reserve I/O port range (6 ports) ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec acpi_cpu: CPU throttling available, 8 steps from 100% to 12.5% ad0: 28615MB [58140/16/63] at ata0-master UDMA100 acd0: CD-RW at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a lock order reversal 1st 0xc4013068 process lock (process lock) @ /usr/src-current/src/sys/kern/ker n_descrip.c:2100 2nd 0xc4030134 filedesc structure (filedesc structure) @ /usr/src-current/src/sys/kern/kern_descrip.c:2107 rl0: discard oversize frame (ether type fbf7 flags 3 len 2992 > max 1514) rl0: discard oversize frame (ether type fbf7 flags 3 len 2992 > max 1514) rl0: discard oversize frame (ether type 2e3d flags 3 len 55442 > max 1514) rl0: discard oversize frame (ether type 904 flags 3 len 36106 > max 1514) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x46 fault code = supervisor read, page not present instruction pointer = 0x8:0xc02f19c0 stac
Re: bad ACPL asl's on motherboards
On 17-Jan-2003 Terry Lambert wrote: > John Baldwin wrote: >> > For Intel, this is a win-win. >> > >> > For FreeBSD, unless Windows adopts the same code (which it will >> > not do, since doing so will limit their market, just as using >> > the code is currently limiting FreeBSD's market), it's a lose-lose. >> >> Are you offering to write a new ACPI parser? If not, then put up or >> shut up. It's not exactly a trivial task. > > This was in the context of a discussion about what could be > done about the problem. It's really the original poster > you should be asking to write code. That's basically what > I was doing (asking him to write the code) by posting the > list of available options. > > I was under the impression that the Intel ACPI parser was > source code? > > So what we're really talking about here is taking over the > maintenance of, and forking, the Intel code, unless you think > Microsoft wrote their code from scratch... I do think M$ wrote their code from scratch prior to the existence of the Intel ACPICA code. > In any case, for anything for which there is a specification, > was long as the specification is complete, implementation is > really pretty trivial. Haha, you are full of it if you say that. The _exact_ problem here is that M$'s ACPI interpreter is buggy and _doesn't_ follow the spec, and so BIOS writer's have hacked their AML's to work around the bugs in M$ interpreter. Thus, if you were to write an interpreter _to the spec_, you end up with what Intel has, and certain machines don't work with it. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use 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
unable to install freebsd-5.0-rc3 on 2.5"hdd in usb2.0 external enclosure
Hello, I uses a 2.5"hdd in an external enclosure with usb2.0 interface on my system. So far, I was not able to install freebsd-5.0-rc3 to this disk - system would panic due to page fault. No such issue occurred under 4.7, but I need the cardbus support under 5.0 :( boot detection messages under 5.0-rc3: ... ohci0: mem 0xec00-0xec000fff irq11 at device 14.0 on pci0 usb1: OHCI version 1.0, legacy support usb1: on ohci0 usb1: USB revision 1.0 uhub2: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 3 ports with 3 removable, self powered umass0: In-System Design USB storage Adapter, rev 2.0/11.05, addr 2 ... da0 at umass-sim0 bus0 target0 lun0 da0: Fixed Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 19077MB (39070080 512 byte sectors: 64H 32S/T 19077C) The only difference I noticed in the above between 5.0-rc3 and 4.7 is: da0:650kB/s transfers under 4.7. When 5.0-rc3 panic, the folllowing is echoed: syncing disks, buffers remaining... panic: bdwrite: buffer is not busy... Anyone have similar experience? solutions I can try? know what changed between 5.0 and 4.7? Thanks in advance. __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VM_METER no longer defined?
Craig Rodrigues wrote:
On Fri, Jan 17, 2003 at 10:26:10AM -0800, Will Andrews wrote:
>Of course, these things can be fixed. But I consider this change
>gratuitous and it breaks standard compatability rules: deprecate
>for one major version and remove in the second. I haven't seen
>any reason why this couldn't be added to vm/vm_param.h:
>
>#define VM_METER VM_TOTAL
>
>for compatability purposes. This change is way too sudden in an
>external API (if it's supposed to be internal, then protect it
>with an #ifdef _KERNEL already!).
How about this then:
Index: vm_param.h
===
RCS file: /home/ncvs/src/sys/vm/vm_param.h,v
retrieving revision 1.16
diff -u -r1.16 vm_param.h
--- vm_param.h 2003/01/11 07:29:46 1.16
+++ vm_param.h 2003/01/17 23:25:52
@@ -89,6 +89,8 @@
#define VM_SWAPPING_ENABLED 11 /* swapping enabled */
#define VM_MAXID 12 /* number of valid vm ids */
+#define VM_METER VM_TOTAL /* backwards compatibility, struct vmmeter */
+
#define CTL_VM_NAMES { \
{ 0, 0 }, \
{ "vmtotal", CTLTYPE_STRUCT }, \
The only place where VM_METER is used in this directory was in vm_meter.c:
240 SYSCTL_PROC(_vm, VM_METER, vmmeter, CTLTYPE_OPAQUE|CTLFLAG_RD,
241 0, sizeof(struct vmtotal), vmtotal, "S,vmtotal",
242 "System virtual memory statistics");
This changed to:
240 SYSCTL_PROC(_vm, VM_TOTAL, vmtotal, CTLTYPE_OPAQUE|CTLFLAG_RD,
241 0, sizeof(struct vmtotal), vmtotal, "S,vmtotal",
242 "System virtual memory statistics");
This is ugly and only further perpetuates what appears to be a
gratuitous API
change. Let's wait to hear from the submitter (Hiten) and committer
(Matt) to
see why this was needed in the first place.
Hiten? Matt?
Scott
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: bad ACPL asl's on motherboards
John Baldwin wrote: > > For Intel, this is a win-win. > > > > For FreeBSD, unless Windows adopts the same code (which it will > > not do, since doing so will limit their market, just as using > > the code is currently limiting FreeBSD's market), it's a lose-lose. > > Are you offering to write a new ACPI parser? If not, then put up or > shut up. It's not exactly a trivial task. This was in the context of a discussion about what could be done about the problem. It's really the original poster you should be asking to write code. That's basically what I was doing (asking him to write the code) by posting the list of available options. I was under the impression that the Intel ACPI parser was source code? So what we're really talking about here is taking over the maintenance of, and forking, the Intel code, unless you think Microsoft wrote their code from scratch... In any case, for anything for which there is a specification, was long as the specification is complete, implementation is really pretty trivial. If you're serious about such a project, and you are willing to dual-license the code, and you have access to the specifications without non-disclosure being required, and you will provide them or they are not very expensive, you can count me in on joining your project. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VM_METER no longer defined?
On Fri, Jan 17, 2003 at 10:26:10AM -0800, Will Andrews wrote:
> Of course, these things can be fixed. But I consider this change
> gratuitous and it breaks standard compatability rules: deprecate
> for one major version and remove in the second. I haven't seen
> any reason why this couldn't be added to vm/vm_param.h:
>
> #define VM_METER VM_TOTAL
>
> for compatability purposes. This change is way too sudden in an
> external API (if it's supposed to be internal, then protect it
> with an #ifdef _KERNEL already!).
How about this then:
Index: vm_param.h
===
RCS file: /home/ncvs/src/sys/vm/vm_param.h,v
retrieving revision 1.16
diff -u -r1.16 vm_param.h
--- vm_param.h 2003/01/11 07:29:46 1.16
+++ vm_param.h 2003/01/17 23:25:52
@@ -89,6 +89,8 @@
#define VM_SWAPPING_ENABLED11 /* swapping enabled */
#defineVM_MAXID12 /* number of valid vm ids */
+#define VM_METER VM_TOTAL /* backwards compatibility, struct vmmeter */
+
#define CTL_VM_NAMES { \
{ 0, 0 }, \
{ "vmtotal", CTLTYPE_STRUCT }, \
The only place where VM_METER is used in this directory was in vm_meter.c:
240 SYSCTL_PROC(_vm, VM_METER, vmmeter, CTLTYPE_OPAQUE|CTLFLAG_RD,
241 0, sizeof(struct vmtotal), vmtotal, "S,vmtotal",
242 "System virtual memory statistics");
This changed to:
240 SYSCTL_PROC(_vm, VM_TOTAL, vmtotal, CTLTYPE_OPAQUE|CTLFLAG_RD,
241 0, sizeof(struct vmtotal), vmtotal, "S,vmtotal",
242 "System virtual memory statistics");
--
Craig Rodrigues
http://home.attbi.com/~rodrigc
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: How to build -current and install to empty slice?
> Date: Fri, 17 Jan 2003 13:40:43 -0800 > From: Darren Pilgrim <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > I'd like to try out -current, however I'm not willing to clobber by working > 4.7 install. How do build -current on 4.7p3 away from my RELENG_4_7 source, > then install to a seperate, pre-partitioned slice? > > Is it ok to create the filesystems with 4.7p3's newfs? > > Also, how do I cvsup a developer preview? To answer the last question first, The developers previews are old and crufty compared to RC3. To get close to that, specify a tag of RELENG_5_0 to get close. The actual RC3 ISO images were just a snapshot of the tree at some point in time, not anything that is tagged. RELENG_5_0 is the code that is intended to be in 5.0-Release and has a number of fixes that were added after RC3 came out, but it's as close as you are likely to get. Changes to RELENG_5_0 are very controlled, so anything in that branch is likely to be a bit more stable or more complete than what was on the RC3 CDs. The first question is a bit tougher. The easiest technique is to use a separate disk. I assume that you don't want/can't do this. In that case, I'd download the RC3 ISO images and burn the CDs. Then just boot it and install in a different slice. If you want you personal file to be available, mount the partition they are in on the V5 system and make a softlink to your home directory there. Building on another partition might be a bit tricky. You might just create a new slice and copy your 4.7r3 slice to it. Then boot it and cvsup RELENG_5_0 and follow the upgrade instructions. If you make the new slice the same size as the existing 4.7 slice, you can use dd to copy it very easily. I did see a fairly detailed post on how to do this about a month ago. You might want to check the archives. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No way to disable loading of agp.1 on boot?
On Fri, 17 Jan 2003, David Spreen wrote: > "Coercitas Temet'Nosce" <[EMAIL PROTECTED]> writes: > > hw.pci.enables_io_modes=0 > > This value doesn't seem to exist on the bootprompt. show > hw.pci.enables_io_modes is the correct name? > > And isn't set name the command I have to type? > > set hw.pci.enables_io_modes=0 doesn't help. That's a typo, should be "enable", not "enables". -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0 Freezes under high load with SMP.
On Fri, 17 Jan 2003, Paul Richards wrote: > On Tue, Jan 14, 2003 at 05:19:36PM -0800, wade wrote: > > I tried this, but when the box froze, the keyboard was completely > > unresponsive, no numlock, nothing. > > No interrupts getting serviced. > > I don't know if it's the same bug or not but writing a CD with burncd > lock my box up solid as well. Strangely, I can do an erase pass but as > soon as I start a data pass it locks up. > > I think there's a general problem somewhere though because I've been > experiencing lockups when running X and doing heavy disk activity as > well. This answer is not intended for the original poster but I'd recommend you try atacontrol mode UDMA33 and see if that affects things. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD 5.0-RC2
Hello, I'am writing about a serious problem in the release I`ve wrote in subject. It's about sound and that /dev/dsp hangs used. I can`t udnerstand why it goes so, because i used lsof tu check whether some programs use the /dev/dsp or /dev/dspx.x, but nothing does this and it just hangs sometimes. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
How to build -current and install to empty slice?
I'd like to try out -current, however I'm not willing to clobber by working 4.7 install. How do build -current on 4.7p3 away from my RELENG_4_7 source, then install to a seperate, pre-partitioned slice? Is it ok to create the filesystems with 4.7p3's newfs? Also, how do I cvsup a developer preview? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bad ACPL asl's on motherboards
On 17-Jan-2003 Peter Schultz wrote: > John Baldwin wrote: > >> On 16-Jan-2003 Terry Lambert wrote: >> >> >"Joel M. Baldwin" wrote: >> > >> >>I gather that there are quite a few Motherboards with bad ACPI asl's >> >>on them. I know that my Abit BP6 sure has problems. As a result I >> >>can't run ACPI. >> >> >> >>What are those of us with these motherboards supposed to to? >> >> >> >>I realize that we can use acpidump to get the asl, correct it, >> >>and then recompile it using iasl from the acpicatools port, to >> >>generate the aml that can be used during boot. >> > >> >There are several things you can do, one of which is what you >> >have suggested, though you do not go far enough: >> > >> >1)Correct the ASL, make a file modification so that >> > FreeBSD can run on the system with the incorrect >> > ASL, and then *notify the motherboard and BIOS >> > vendors of the correction, and the reason for it*. >> > >> >2)The ASL works *fine* with the Windows ACPI code; >> > *correct* the FreeBSD code so that it *also* works >> > fine for FreeBSD (i.e. if the FreeBSD code were a >> > line-for-line duplicate of the Windows code, then >> > FreeBSD would not be having these problems, where >> > Windows does not, would it...). >> >> >> Well, the problem here is that we don't write this code, Intel >> does. >> > The problem is that Mike Smith quit. If I remember correctly, he fixed > two of these for me when he was working on CURRENT. Googling `Mike > Smith freebsd acpi' gets 482 results. If someone can get close to him, > this stuff might get solved. The folks on acpi-jp@ are fairly good at fixing problems with ACPI. Mike did do a lot of work, but he wasn't the only one working on this. The [EMAIL PROTECTED] guys have found and fixed several bugs in Intel's code and helped track down problems in BIOS ASL's. Mike didn't write the whole ACPICA stack by himself. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use 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: Somebody: port this: http://www.theinquirer.net/?article=7231
On Fri, 17 Jan 2003 10:25:08 -0500 (EST) Andrew Gallatin <[EMAIL PROTECTED]> wrote: > Let me know if you hear anything. Actually I'm downloading it at the moment. First I got a response "it may need upto 24h until you can download it after registration" and then a "try again, it should work now". I will open up an issue regarding the lack of open source kernel drivers... but first I download it. Not that I don't trust Marius when he says that the beta doesn't come with the sources, it's because I want to say "hey, I tried to port it to freebsd like I did with icc, but I can't because of ...". Bye, Alexander. -- I believe the technical term is "Oops!" 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: bad ACPL asl's on motherboards
John Baldwin wrote: On 16-Jan-2003 Terry Lambert wrote: >"Joel M. Baldwin" wrote: > >>I gather that there are quite a few Motherboards with bad ACPI asl's >>on them. I know that my Abit BP6 sure has problems. As a result I >>can't run ACPI. >> >>What are those of us with these motherboards supposed to to? >> >>I realize that we can use acpidump to get the asl, correct it, >>and then recompile it using iasl from the acpicatools port, to >>generate the aml that can be used during boot. > >There are several things you can do, one of which is what you >have suggested, though you do not go far enough: > >1)Correct the ASL, make a file modification so that > FreeBSD can run on the system with the incorrect > ASL, and then *notify the motherboard and BIOS > vendors of the correction, and the reason for it*. > >2)The ASL works *fine* with the Windows ACPI code; > *correct* the FreeBSD code so that it *also* works > fine for FreeBSD (i.e. if the FreeBSD code were a > line-for-line duplicate of the Windows code, then > FreeBSD would not be having these problems, where > Windows does not, would it...). Well, the problem here is that we don't write this code, Intel does. The problem is that Mike Smith quit. If I remember correctly, he fixed two of these for me when he was working on CURRENT. Googling `Mike Smith freebsd acpi' gets 482 results. If someone can get close to him, this stuff might get solved. Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bad ACPL asl's on motherboards
On 16-Jan-2003 Terry Lambert wrote: > Nate Lawson wrote: >> On Thu, 16 Jan 2003, Terry Lambert wrote: >> > Repeat: These machines work fine under Windows; the problem >> > is not the BIOS, it's the OS's ASL interpreter. >> >> There's another wrinkle in that the interpreter is supplied by Intel. >> Some difficulties were _introduced_ by them, notably the strict var scope >> checking. > > That's a good idea. > > For them. > > For FreeBSD, it means eating the pain, so that Intel gets what > it wants: technical people bitching at vendors to conform to > the standard, while not impacting the vast majority of Windows > and other non-technical customers. > > For Intel, this is a win-win. > > For FreeBSD, unless Windows adopts the same code (which it will > not do, since doing so will limit their market, just as using > the code is currently limiting FreeBSD's market), it's a lose-lose. Are you offering to write a new ACPI parser? If not, then put up or shut up. It's not exactly a trivial task. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use 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: bad ACPL asl's on motherboards
On 16-Jan-2003 Terry Lambert wrote: > "Joel M. Baldwin" wrote: >> I gather that there are quite a few Motherboards with bad ACPI asl's >> on them. I know that my Abit BP6 sure has problems. As a result I >> can't run ACPI. >> >> What are those of us with these motherboards supposed to to? >> >> I realize that we can use acpidump to get the asl, correct it, >> and then recompile it using iasl from the acpicatools port, to >> generate the aml that can be used during boot. > > There are several things you can do, one of which is what you > have suggested, though you do not go far enough: > > 1)Correct the ASL, make a file modification so that > FreeBSD can run on the system with the incorrect > ASL, and then *notify the motherboard and BIOS > vendors of the correction, and the reason for it*. > > 2)The ASL works *fine* with the Windows ACPI code; > *correct* the FreeBSD code so that it *also* works > fine for FreeBSD (i.e. if the FreeBSD code were a > line-for-line duplicate of the Windows code, then > FreeBSD would not be having these problems, where > Windows does not, would it...). Well, the problem here is that we don't write this code, Intel does. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use 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: VM_METER no longer defined?
On Fri, Jan 17, 2003 at 01:02:07PM -0500, Joe Marcus Clarke wrote: > It looks like Matt did this to fix vm.vmtotal. From sys/vm/vm_param.h: > > Make 'sysctl vm.vmtotal' work properly using updated patch from Hiten. > (the patch in the PR was stale). > > It looks to have been replaced by VM_TOTAL. I fixed libgtop[2] by > checking for VM_TOTAL, and using that instead of VM_METER. This seems > to work. Of course, these things can be fixed. But I consider this change gratuitous and it breaks standard compatability rules: deprecate for one major version and remove in the second. I haven't seen any reason why this couldn't be added to vm/vm_param.h: #define VM_METER VM_TOTAL for compatability purposes. This change is way too sudden in an external API (if it's supposed to be internal, then protect it with an #ifdef _KERNEL already!). Regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VM_METER no longer defined?
On Fri, 2003-01-17 at 12:42, Scott Long wrote: > Conrad Sabatier wrote: > > > Pardon me if I missed something, but what's become of the definition of > > VM_METER? It is nowhere to be found under /usr/include. This breaks > > a few > > ports, kdebase3 being one of the most notable. > > > I've got to admit that this one slipped in under my radar. Would the > committer and submitter please give an explanation of why VM_METER > was changed? It looks like Matt did this to fix vm.vmtotal. From sys/vm/vm_param.h: Make 'sysctl vm.vmtotal' work properly using updated patch from Hiten. (the patch in the PR was stale). It looks to have been replaced by VM_TOTAL. I fixed libgtop[2] by checking for VM_TOTAL, and using that instead of VM_METER. This seems to work. Joe > > Scott > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- PGP Key : http://www.marcuscom.com/pgp.asc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VM_METER no longer defined?
On Fri, Jan 17, 2003 at 10:42:27AM -0700, Scott Long wrote: > I've got to admit that this one slipped in under my radar. Would the > committer and submitter please give an explanation of why VM_METER > was changed? The commit which removed VM_METER is here: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1995623+0+archive/2003/cvs-all/20030112.cvs-all -- Craig Rodrigues http://home.attbi.com/~rodrigc [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No way to disable loading of agp.1 on boot?
Heyho, "M. Warner Losh" <[EMAIL PROTECTED]> writes: > OK. I misunderstood your message then. They were added relatively > recently to 5.0 (sometime just before RC1 or RC2 IIRC), so either they > do you no good because your problem is solved in different ways, or > you need to upgrade (or both). Well, I use 5.0RC3. But I wonder why my problem occurs while booting the miniinst iso, but not when I boot with the bootfloppies. thanks, David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VM_METER no longer defined?
Conrad Sabatier wrote: Pardon me if I missed something, but what's become of the definition of VM_METER? It is nowhere to be found under /usr/include. This breaks a few ports, kdebase3 being one of the most notable. I've got to admit that this one slipped in under my radar. Would the committer and submitter please give an explanation of why VM_METER was changed? Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No way to disable loading of agp.1 on boot?
In message: <[EMAIL PROTECTED]> David Spreen <[EMAIL PROTECTED]> writes: : Heyho, : : "M. Warner Losh" <[EMAIL PROTECTED]> writes: : > You misunderstand what you can set from the boot loader. You can set : > any variable you like at the ok prompt, even if you can't show it : > first: : : Of course, but those variables don't work for me, so I want to know if : I got something wrong. The kernel still hangs during that agp-pci-issue. : : any further suggestions? OK. I misunderstood your message then. They were added relatively recently to 5.0 (sometime just before RC1 or RC2 IIRC), so either they do you no good because your problem is solved in different ways, or you need to upgrade (or both). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No way to disable loading of agp.1 on boot?
Heyho, "M. Warner Losh" <[EMAIL PROTECTED]> writes: > You misunderstand what you can set from the boot loader. You can set > any variable you like at the ok prompt, even if you can't show it > first: Of course, but those variables don't work for me, so I want to know if I got something wrong. The kernel still hangs during that agp-pci-issue. any further suggestions? thanks for your help, David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: new wi driver
: dstumbler breaks; on startup it reports : "unable to ioctl device socket: Input/output error". As root or no? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: i386 boot failure
On Fri, 17 Jan 2003, Mark Murray wrote: > > I've recently been trying to bring a system of mine (4.7-R) up-to-date > > with -CURRENT by following the dotted lines in UPDATING; basically, > > everything up through 'make installkernel' and the 'make install' from > > /usr/src/sys/boot has gone fine; I reboot into loader(8) and 'boot -s', > > but literally just after printing its "I just loaded acpi.ko" message the > > system just hangs at a twiddle-prompt, forever stilled. Well, not quite: > > the keyboard lights blink once and the hard drives click, but no further > > response. This isn't an ACPI problem; I've unset acpi_load, and the only > > difference is that the system spins for half a second longer before dying. > > loader claims to have preloaded the (new) kernel already. > > [ snip ] > > > # Pseudo devices - the number indicates how many units to allocate.device > random # Entropy device > > This looks funny. What happens if you load the random device? Ack, sorry. That's a snipping artifact; the actual conf file has these as two separate lines, and random.ko is in fact present in /boot/kernel/. John. -- évana roì, séana coì, reìja venacoì u vëja haman. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: i386 boot failure
> I've recently been trying to bring a system of mine (4.7-R) up-to-date > with -CURRENT by following the dotted lines in UPDATING; basically, > everything up through 'make installkernel' and the 'make install' from > /usr/src/sys/boot has gone fine; I reboot into loader(8) and 'boot -s', > but literally just after printing its "I just loaded acpi.ko" message the > system just hangs at a twiddle-prompt, forever stilled. Well, not quite: > the keyboard lights blink once and the hard drives click, but no further > response. This isn't an ACPI problem; I've unset acpi_load, and the only > difference is that the system spins for half a second longer before dying. > loader claims to have preloaded the (new) kernel already. [ snip ] > # Pseudo devices - the number indicates how many units to allocate.device > random # Entropy device This looks funny. What happens if you load the random device? M -- Mark Murray iumop ap!sdn w,I idlaH To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: new wi driver
> > NB the new wi(4) is probably also an issue for ports/net/bsd-airtools,
> > to be resolved or documented before MFC. (copied maintainer)
>
> Why, did they not work/build after the commit? I didn't try all the ports
> that depend on the driver but the API (ioctls) should be unchanged except
> for the AP scanning stuff which is why I had to make mods to wicontrol.
Ok, this is what's up with bsd-airtools:
dstumbler breaks; on startup it reports
"unable to ioctl device socket: Input/output error".
I gross-hacked dstumbler to record what it is really trying to
do (I won't decipher the ioctl cmd just now):
ioctl(,
0x80206939,
);
the ifreq is initialized to zeros except ifr_data, which
points at a struct wi_req containing the following:
wi_req = {
0x0001, /* wi_len */
0xfce1, /* wi_type */
{
0x,
... /* full of zeros */
0x,
} /* wi_val[WI_MAX_DATALEN] */
}
The card is a Lucent Orinoco as follows:
wi0: at port 0x100-0x13f irq 11 function 0 config 1 on pccard1
wi0: 802.11 address: 00:02:2d:1d:25:98
wi0: using Lucent Technologies, WaveLAN/IEEE
wi0: Lucent Firmware: Station (8.10.1)
wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
Hope this helps,
Magnus
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Somebody: port this: http://www.theinquirer.net/?article=7231
Alexander Leidinger writes: > On Fri, 17 Jan 2003 10:01:35 -0500 (EST) > Andrew Gallatin <[EMAIL PROTECTED]> wrote: > > > I signed up and waded through tons of slow https js laden forms, only > > to finally be presented with nothing but a self-extracting .exe file > > which looks like a patch for the windows data-collector. > > Me too (but with a not so slow connection). > > > I do have a license key now. Just no software :( > > > > If anybody figure out how to get the actual download, please let me > > know! > > At the ftp site there's also only .exe files... > > I've opened up an issue at premier.intel.com because of this. Let me know if you hear anything. I'm hoping the port won't be much worse than Iprobe. (The alpha (linux/windows/vms/unix) profiling tool I ported to FreeBSD/alpha way back when.. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Somebody: port this: http://www.theinquirer.net/?article=7231
On Fri, 17 Jan 2003 10:01:35 -0500 (EST) Andrew Gallatin <[EMAIL PROTECTED]> wrote: > I signed up and waded through tons of slow https js laden forms, only > to finally be presented with nothing but a self-extracting .exe file > which looks like a patch for the windows data-collector. Me too (but with a not so slow connection). > I do have a license key now. Just no software :( > > If anybody figure out how to get the actual download, please let me > know! At the ftp site there's also only .exe files... I've opened up an issue at premier.intel.com because of this. BTW.: Even if this isn't on topic for FreeBSD: AMD has a free tool (maybe not as powerfull as vtune) for download at http://www.amd.com/us-en/Processors/DevelopWithAMD/0,,30_2252_3604,00.html unfortunately it's Windows only (and needs MSVC). But if you need a tool which is able to show you the utilisation of the CPU pipelines and you meet the necessary requirements, it may be of use. Bye, Alexander. -- I believe the technical term is "Oops!" 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: Somebody: port this: http://www.theinquirer.net/?article=7231
Alexander Leidinger writes: > On Wed, 15 Jan 2003 19:32:39 +0100 > Poul-Henning Kamp <[EMAIL PROTECTED]> wrote: > > > > > They have a beta test access to vtune: > http://www.intel.com/software/products/vtune/vlin/ > > Bye, > Alexander. > I signed up and waded through tons of slow https js laden forms, only to finally be presented with nothing but a self-extracting .exe file which looks like a patch for the windows data-collector. I do have a license key now. Just no software :( If anybody figure out how to get the actual download, please let me know! Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADSUP: CCD(4) changes.
I have started chipping away at GEOMification of CCD. For obscure technical reasons, I need to get the configuration ioctl for CCD "out of band" instead of "in band". This commit does that. Old and new kernels worl with both old and new ccdconfig(8) binaries, but there will be whinage and 30 seconds sleeps if they are not in sync as an incentive for people to upgrade. Poul-Henning --- Forwarded Message From: Poul-Henning Kamp <[EMAIL PROTECTED]> Date: Fri, 17 Jan 2003 06:53:53 -0800 (PST) To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: cvs commit: src/sys/dev/ccd ccd.c src/sbin/ccdconfig ccdconfig.c pathnames.h X-FreeBSD-CVS-Branch: HEAD Sender: [EMAIL PROTECTED] Precedence: bulk phk 2003/01/17 06:53:53 PST Modified files: sys/dev/ccd ccd.c sbin/ccdconfig ccdconfig.c pathnames.h Log: Find places to store the previously implicityly passed unit number in the three configuration ioctls which need a unit number. Add a "ccd.ctl" device for config operations. Implement ioctls on ccd.ctl which rely on the explicityly passed unit numbers. Update ccdconfig to use the new ccd.ctl interface. Add code to the kernel to detect old ccdconfig binaries, and whine about it. Add code to ccdconfig to detect old kernels, and whine about it. These two compatibility measures will be retained only for a limited period since they are in the way of GEOM'ification of ccd. Revision ChangesPath 1.26 +18 -18src/sbin/ccdconfig/ccdconfig.c 1.2 +3 -0 src/sbin/ccdconfig/pathnames.h 1.114 +122 -7src/sys/dev/ccd/ccd.c --- End of Forwarded Message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No way to disable loading of agp.1 on boot?
In message: <[EMAIL PROTECTED]> David Spreen <[EMAIL PROTECTED]> writes: : Heyho, : : "Coercitas Temet'Nosce" <[EMAIL PROTECTED]> writes: : > hw.pci.enables_io_modes=0 : : This value doesn't seem to exist on the bootprompt. show : hw.pci.enables_io_modes is the correct name? : : And isn't set name the command I have to type? : : set hw.pci.enables_io_modes=0 doesn't help. : : It's the same with your second variable. : : > hw.pci_allow_unsupported_io_range=1 : : Would be cool if you'd tell me what I got wrong. : : thanks for your help, You misunderstand what you can set from the boot loader. You can set any variable you like at the ok prompt, even if you can't show it first: ok show hw.pci_allow_unsupported_io_range ok set hw.pci_allow_unsupported_io_range 1 ok show hw.pci_allow_unsupported_io_range hw.pci_allow_unsupported_io_range=1 ok Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No way to disable loading of agp.1 on boot?
Heyho, "Coercitas Temet'Nosce" <[EMAIL PROTECTED]> writes: > hw.pci.enables_io_modes=0 This value doesn't seem to exist on the bootprompt. show hw.pci.enables_io_modes is the correct name? And isn't set name the command I have to type? set hw.pci.enables_io_modes=0 doesn't help. It's the same with your second variable. > hw.pci_allow_unsupported_io_range=1 Would be cool if you'd tell me what I got wrong. thanks for your help, David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PS/2 mouse problems with -CURRENT
On Fri, Jan 17, 2003 at 04:27:36PM +0300, Igor Roboul wrote: > Hello, > does anybody have problems with PS/2 mouse attached to PC with recent > -CURRENT? > > Mouse is recognized by kernel and moused, but cursor is moving VERY > slow, no visible reaction to buttons etc. This happens in text mode > and in X11. When in X11, it happens when > Option "Device" "/dev/sysmouse" > and when > Option "Device" "/dev/psm0" > with and without moused running > > Part of dmesg output of older -CURRENT: > > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model NetMouse/NetScroll Optical, device ID 0 > > Same part of newer -CURRENT (I have disable ACPI, but I get same > result with ACPI too): > > atkbdc0: at port 0x64,0x60 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model NetMouse/NetScroll Optical, device ID 0 On my desktop i had this problem only with enabled ACPI. When i disable ACPI, mouse works just fine. On other PC's i don't have this problem. -- Vitaly Markitantov mailto: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: 5.0 boot failure on laptop
Thanks John, a fresh install was probably a good idea anyway to at least get rid of all the junk that just seems to accumulate :) I now have 5.0 installed. I first tried a custom install booting from floppies and installing from the CD, but it still wouldn't mount the CD. So I put 4.7 back on (minimal) and created a new partition while I was at it. I mounted the CD and copied /cdrom/base and /cdrom/boot to it. Rebooted from floppies and installed successfully. After that I was able to add other distributions from the CD. Everything seems to be working with one small problem. Actually it's a big problem. No cardbus. Here's the boot messages (typed manually): cbb0: at device 19.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb: Unable to map IRQ... device_probe_and_attach: cbb0 attach returned 12 cbb0: mem 0x8800-0x88000fff at device 19.1 on pci0 cardbus1: on cbb0 pccard1: <16-bit PCCard bus> on cbb0 cbb: Unable to map IRQ... device_probe_and_attach: cbb0 attach returned 12 Later in the boot I had a few of those "can't assign resources" messages but digging thru the mail archives I found that they're nothing to worry about. The mouse port is one of them and the stick works fine. I have hw.pci.allow_unsupported_io_range set to 1 but upon further reading it was expected that it didn't change anything. I rebuilt the kernel (added sound support) but after reboot the above still happens. Does anyone have any suggestions (besides playing football with it)? Thanks in advance, Vince. On Thu, 16 Jan 2003, John Baldwin wrote: > > On 16-Jan-2003 Vince Vielhaber wrote: > > > > I'm not sure where to ask this. 5.0 isn't released yet so I don't think > > questions is the place but since it's on a laptop I'll try here. If > > there's a better list for it, let me know and I'll bounce it there too. > > Just before sending this I also included Current. > > > > I have a Micron Transport XPE. I need to run 5.0 for the cardbus support. > > It has the TI 1130 Cardbus in it. > > > > The problem is the CD won't boot. The 4.7 CD boots in it fine, and the > > 5.0 CD that I burned from the ISO image boots fine in another computer. > > I've tried both miniinst and disk1 images. > > > > I get the CD Loader message and everything up to Starting... Then it all > > goes downhill. > > > > BTX loader 1.00 BTX version is 1.01 > > > > int=0005 err=efl=00010286eip=0001768c > > eax= ebx=ecx=edx= > > esi= edi=epb=esp=00094824 > > > > cs=002b ds=0033 es=0033 fs=0033 gs=0033 ss=0033 > > > > cs:eip= 62 61 73 65 20 61 74 20-25 70 2c 20 74 6f 70 20 > > 61 74 20 25 70 0a 00 00-00 00 00 00 00 00 00 00 > > > > ss:esp= 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 > > 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 > > > > BTX halted > > > > Ugly, huh? > > Eek, your CD drive must be hosed or something. It's trying to > execute text: > > "base at %p, top at %p" (that's the stuff at CS:EIP) and is > getting badly confused as a result. > > > So I yank out the battery, run it on the AC adapter and plug > > in the floppy. Now I have the CD and the floppy to work with. > > I made up the two floppies, it boots up, it complains about not > > being able to load if_awi.ko, I tell it to keep going and up > > comes the menu. > > > > I select UPGRADE (it has 4.7 on it now), choose some distribution > > stuff, go into the label editor (there's no way to tell it what > > partition is the swap partition without deleting it and recreating > > it), set the mount point and hit Q. > > For an upgrade to 5.0, the upgrade facility is probably a bad idea. > Backing up your data and doing a fresh install is probably the safest > way to upgrade. :-/ > > -- > > John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > Vince. -- Fast, inexpensive internet service 56k and beyond! http://www.pop4.net/ http://www.meanstreamradio.com http://www.unknown-artists.com Internet radio: It's not file sharing, it's just radio. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PS/2 mouse problems with -CURRENT
Hello, does anybody have problems with PS/2 mouse attached to PC with recent -CURRENT? Mouse is recognized by kernel and moused, but cursor is moving VERY slow, no visible reaction to buttons etc. This happens in text mode and in X11. When in X11, it happens when Option "Device" "/dev/sysmouse" and when Option "Device" "/dev/psm0" with and without moused running Part of dmesg output of older -CURRENT: atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model NetMouse/NetScroll Optical, device ID 0 Same part of newer -CURRENT (I have disable ACPI, but I get same result with ACPI too): atkbdc0: at port 0x64,0x60 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model NetMouse/NetScroll Optical, device ID 0 Part of output from "moused -p /dev/psm0 -fd" on older kernel, I have moved mouse and pressed buttons: moused: proto params: f8 80 00 00 8 00 ff moused: port: /dev/psm0 interface: ps/2 type: sysmouse model: NetMouse/NetScr oll Optical moused: received char 0x83 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x7f moused: assembled full packet (len 8) 83,0,0,0,0,0,0,7f moused: tv: 1042657045 835587 moused: : 1042657044 592463 moused: flags:0001 buttons:0001 obuttons: moused: activity : buttons 0x0001 dx 0 dy 0 dz 0 moused: mstate[0]->count:1 ... For newer kernel and moused: moused: proto params: f8 80 00 00 8 00 ff moused: port: /dev/psm0 interface: ps/2 type: sysmouse model: NetMouse/NetScroll Op tical moused: received char 0x83 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x7f moused: assembled full packet (len 8) 83,0,0,0,0,0,0,7f moused: tv: 1042667542 735330 moused: : 1042667540 279868 moused: flags:0001 buttons:0001 obuttons: moused: activity : buttons 0x0001 dx 0 dy 0 dz 0 moused: mstate[0]->count:1 moused: button 1 count 1 moused: received char 0x87 ... Of course I could not make same mouse movements :-) I have booted newer system from live-5.0-RC-20021213-JPSNAP.iso Older -CURRENT is on my home PC's hard disk. Motherboard: MSI MS6337LE5 (i815 chipset) Mouse: Genius NetScroll+ -- Igor Roboul, System administrator at Speech Technology Center http://www.speechpro.com http://www.speechpro.ru To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RELENG_5 branch ?
Joao Pedras <[EMAIL PROTECTED]> writes: > > Hi all > > Will there be a RELENG_5 where we would get 5.0-STABLE ? Pretty much in the same > way it has been up until now... > > Is this code currently tagged with RELENG_5_0 ? This won't happen until after 5.1 or 5.2. For now we have 5.1-CURRENT or something like that. Best regards, Mike Barcroft 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 Fri Jan 17 03:03:53 PST 2003 -- >>> Kernel build for GENERIC completed on Fri Jan 17 03:36:34 PST 2003 -- >>> Kernel build for LINT started on Fri Jan 17 03:36:35 PST 2003 -- ===> vinum "Makefile", line : warning: duplicate script for target "geom_bsd.o" [...] /h/des/src/sys/dev/lmc/if_lmc.c:32:2: warning: #warning "The lmc driver i [...] /h/des/src/sys/dev/pdq/pdq.c: In function `pdq_initialize': /h/des/src/sys/dev/pdq/pdq.c:1606: warning: cast discards qualifiers from [...] /h/des/src/sys/pci/meteor.c:149:2: warning: #warning "The meteor driver i [...] /h/des/src/sys/pci/simos.c:30:2: warning: #warning "The simos driver is b [...] cc1: warnings being treated as errors /h/des/src/sys/dev/advansys/adv_isa.c: In function `adv_isa_probe': /h/des/src/sys/dev/advansys/adv_isa.c:232: warning: overflow in implicit [...] *** 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: Somebody: port this: http://www.theinquirer.net/?article=7231
On Wed, 15 Jan 2003 19:32:39 +0100 Poul-Henning Kamp <[EMAIL PROTECTED]> wrote: > They have a beta test access to vtune: http://www.intel.com/software/products/vtune/vlin/ Bye, Alexander. -- I believe the technical term is "Oops!" 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
VM_METER no longer defined?
Pardon me if I missed something, but what's become of the definition of VM_METER? It is nowhere to be found under /usr/include. This breaks a few ports, kdebase3 being one of the most notable. -- Conrad Sabatier <[EMAIL PROTECTED]> - "In Unix veritas" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
i386 boot failure
I've recently been trying to bring a system of mine (4.7-R) up-to-date with -CURRENT by following the dotted lines in UPDATING; basically, everything up through 'make installkernel' and the 'make install' from /usr/src/sys/boot has gone fine; I reboot into loader(8) and 'boot -s', but literally just after printing its "I just loaded acpi.ko" message the system just hangs at a twiddle-prompt, forever stilled. Well, not quite: the keyboard lights blink once and the hard drives click, but no further response. This isn't an ACPI problem; I've unset acpi_load, and the only difference is that the system spins for half a second longer before dying. loader claims to have preloaded the (new) kernel already. Here's the dmesg from 4.7's kernel.GENERIC: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x8800 real memory = 268369920 (262080K bytes) avail memory = 255954944 (249956K bytes) Preloaded elf kernel "/kernel.GENERIC" at 0xc050f000. K6-family MTRR support enabled (2 registers) md0: Malloc disk Using $PIR table, 5 entries at 0xc00fdcd0 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: (vendor=0x1106, dev=0x3040) at 7.3 pci0: (vendor=0x1102, dev=0x0002) at 8.0 irq 11 pci0: (vendor=0x1102, dev=0x7002) at 8.1 rl0: port 0xe000-0xe0ff mem 0xd7018000-0xd70180ff irq 5 at device 9.0 on pci0 rl0: Ethernet address: 00:a0:4c:39:10:cc miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: (vendor=0x12b9, dev=0x1006) at 10.0 irq 9 pcib1: on motherboard pci2: on pcib1 orm0: at iomem 0xc-0xc7fff on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ad0: 16124MB [32760/16/63] at ata0-master UDMA33 ad1: 29196MB [59320/16/63] at ata0-slave UDMA33 acd0: DVD-ROM at ata1-master PIO4 Mounting root from ufs:/dev/ad1s3a *** end-of-file *** ...and here's the kernel configuration which isn't working, with commented module-lines removed for your viewing convenience: # SMYRNO -- Standard kernel configuration for smyrno.tiercel.net # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.371 2002/12/28 06:22:17 scottl Exp $ machine i386 #cpuI486_CPU cpu I586_CPU cpu I686_CPU ident SMYRNO maxusers0 #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options MD_ROOT #MD is a potential root device #optionsNFSCLIENT #Network Filesystem Client #optionsNFSSERVER #Network Filesystem Server #optionsNFS_ROOT#NFS usable as root device, requires NFSCLIENT options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS#Pseudo-f
Re: 5.0 Freezes under high load with SMP.
On Tue, Jan 14, 2003 at 05:19:36PM -0800, wade wrote: > I tried this, but when the box froze, the keyboard was completely > unresponsive, no numlock, nothing. No interrupts getting serviced. I don't know if it's the same bug or not but writing a CD with burncd lock my box up solid as well. Strangely, I can do an erase pass but as soon as I start a data pass it locks up. I think there's a general problem somewhere though because I've been experiencing lockups when running X and doing heavy disk activity as well. Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
