[current tinderbox] failure on sparc64/sparc64
TB --- mkdir /home/des/tinderbox/CURRENT/sparc64 TB --- mkdir /home/des/tinderbox/CURRENT/sparc64/sparc64 TB --- 2003-08-05 21:42:24 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-08-05 21:42:24 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs checkout -P -A src TB --- 2003-08-05 21:46:08 - building world TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1: legacy release compatibility shims >>> 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/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/include >>> stage 4: building libraries >>> stage 4: make dependencies >>> stage 4: building everything.. TB --- 2003-08-05 22:42:02 - building generic kernel TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Aug 5 22:42:02 GMT 2003 >>> Kernel build for GENERIC completed on Tue Aug 5 22:50:50 GMT 2003 TB --- 2003-08-05 22:50:50 - generating LINT kernel config TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/conf TB --- /usr/bin/make -B LINT TB --- 2003-08-05 22:50:50 - building LINT kernel TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Aug 5 22:50:50 GMT 2003 [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/cs/if_cs.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/cs/if_cs_isa.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/cs/if_cs_pccard.c cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/dev -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/
Re: vinum problems with todays current
On Friday, 8 August 2003 at 16:04:05 +0200, Rob wrote:
> Greg 'groggy' Lehey wrote:
>> On Tuesday, 5 August 2003 at 22:21:41 +0200, Rob wrote:
>>> Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, Rob writes:
> Hi all,
>
> After cvs'upping (about 12 hours ago) and building world/kernel vinum
> stopped working. It does show my two disks but nothing more. I also
> get an error message right after the bootloader:
Can you try this patch:
>>>
>>> I noticed I had an older version of spec_vnops.c (1.205), so I
>>> cvsupped again and build kernel, this gave me the same msgbuf error,
>>> but with different values. Then I applied your patch and the error
>>> messgae disapeared, but still my vinum doesn't come up.
>>
>> Can I assume that this is related to GEOM, and not to Vinum?
>
> After investigating a little further today, I found the config info
> on the drives to be mangled.
>
> --
> # rm -f log
> # for i in /dev/da0s1h /dev/da1s1h /dev/da2s1h /dev/da3s1h; do
> (dd if=$i skip=8 count=6|tr -d '\000-\011\200-\377'; echo) >> log
> done
> # cat log
> IN VINOx-server.debank.tvbC<>c3??Z${m5?
> IN VINOx-server.debank.tvaC<><3?WPZ${m5?
> --
>
> I guess the drives can't be started again unless I have the
> parameters which I used during install (please say I'm wrong).
Hmm. That doesn't look good. No trace of the original config?
Greg
--
See complete headers for address and phone numbers
pgp0.pgp
Description: PGP signature
Re: Dhclient fix for systems with media settings
Hi,
Is this going to cure the cases where using DHCP results in my network
link going dead about ~30 minutes after getting a lease? At that point
it starts spitting out timeout errors and stuff, and i have to
unplug/replug the card and re-start dhclient to get connectivity again..
Thanks for the efforts =)
/Eirik
On Tue, 5 Aug 2003 10:45:18 +0200 (CEST)
Martin Blapp <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> If you used wi(4) or en(4) wavelan cards and you had problems with
> dhclient, you should try this patch, which treats interfaces with
> media settings differently.
>
> http://people.freebsd.org/~mbr/patches/dhclient-interfacepolling-fixup.diff
>
> I'll produce a more clean patch this evening, and also adapt the patch
> to the ISC style, so it can be submitted again.
>
> --- src/contrib/isc-dhcp/includes/dhcpd.h.origMon Aug 4 23:57:06 2003
> +++ src/contrib/isc-dhcp/includes/dhcpd.h Mon Aug 4 23:57:37 2003
> @@ -782,6 +782,7 @@
> char name [IFNAMSIZ]; /* Its name... */
> int linkstatus; /* Link status */
> int ieee802;/* True if media is ieee802 */
> + int mediaflag; /* True if dhclient.conf has media settings */
> int index; /* Its index. */
> int rfdesc; /* Its read file descriptor. */
> int wfdesc; /* Its write file descriptor, if
> --- src/contrib/isc-dhcp/client/dhclient.c.orig Tue Aug 5 00:42:37 2003
> +++ src/contrib/isc-dhcp/client/dhclient.cTue Aug 5 10:01:17 2003
> @@ -257,7 +257,9 @@
> log_fatal ("%s: interface name too long (max %ld)",
> argv [i], (long)strlen (argv [i]));
> strlcpy (tmp -> name, argv [i], IFNAMSIZ);
> - set_ieee802(tmp);
> +#ifdef __FreeBSD__
> + set_ieee80211(tmp);
> +#endif
> tmp->linkstatus = interface_active(tmp);
> if (interfaces) {
> interface_reference (&tmp -> next,
> @@ -412,7 +414,16 @@
>INTERFACE_AUTOMATIC)) !=
>INTERFACE_REQUESTED))
> continue;
> - set_ieee802(ip);
> +#ifdef __FreeBSD__
> + set_ieee80211(ip);
> +#endif
> +#ifdef ENABLE_POLLING_MODE
> + if (ip -> client -> config -> media != NULL)
> + ip->mediaflag = 1;
> + else
> + ip->mediaflag = 0;
> +#endif /* ifdef ENABLE_POLLING_MODE */
> +
> script_init (ip -> client,
>"PREINIT", (struct string_list *)0);
> if (ip -> client -> alias)
> @@ -1385,9 +1396,6 @@
> int interval;
> int increase = 1;
>
> - if (interface_active(client -> interface) == 0)
> - return;
> -
> /* Figure out how long it's been since we started transmitting.
> */ interval = cur_time - client -> first_sending;
>
> @@ -1427,6 +1435,9 @@
> }
> }
>
> + if (interface_active(client -> interface) == 0)
> + return;
> +
> /* If we're supposed to increase the interval, do so. If it's
> currently zero (i.e., we haven't sent any packets yet), set
> it to one; otherwise, add to it a random number between
> @@ -3215,14 +3226,29 @@
> if (ifmr.ifm_status & IFM_AVALID) {
> if (ip->ieee802) {
> if ((IFM_TYPE(ifmr.ifm_active) == IFM_IEEE80211) &&
> - (ifmr.ifm_status & IFM_ACTIVE))
> + (ifmr.ifm_status & IFM_ACTIVE)) {
> + if (ip->mediaflag &&
> + ip -> client -> state != S_BOUND)
> + return (2);
> return (1);
> + }
> } else {
> - if (ifmr.ifm_status & IFM_ACTIVE)
> + if (ifmr.ifm_status & IFM_ACTIVE) {
> + if (ip->mediaflag &&
> + ip -> client -> state != S_BOUND)
> + return (2);
> return (1);
> + }
> }
> }
>
> + /*
> + * If dhclient.conf contains media settings, we cannot
> + * abort if the interface is not set to active mode.
> + */
> + if (ip->mediaflag && ip -> client -> state != S_BOUND)
> + return (1);
> +
> return (0);
> #else /* ifdef __FreeBSD__ */
>
> @@ -3231,7 +3257,7 @@
> }
>
> #ifdef __FreeBSD__
> -set_ieee802 (struct interface_info *ip) {
> +set_ieee80211 (struct interface_info *ip) {
>
> struct ieee80211req ireq;
> u_int8_tdata[32
RE: Best Known Methods for dual booting WinXP + -current
You are right, thanks for the correction! > -Original Message- > From: Wilko Bulte [mailto:[EMAIL PROTECTED] > Sent: Friday, August 08, 2003 4:41 AM > To: David O'Brien; Cagle, John (ISS-Houston); John Reynolds; > [EMAIL PROTECTED] > Subject: Re: Best Known Methods for dual booting WinXP + -current > > > On Thu, Aug 07, 2003 at 06:49:55PM -0700, David O'Brien wrote: > > On Thu, Aug 07, 2003 at 03:40:27PM -0500, Cagle, John > (ISS-Houston) wrote: > > > Had to use FFS filesystem since Grub doesn't support UFS. > > ^^^ > > UFS1 > ^^^ > UFS2 > -- > | / o / /_ _ [EMAIL PROTECTED] > |/|/ / / /( (_) Bulte > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
usbd does not use detach
Does nobody has this problem or does noone use this feature? Jan On Sat, 2003-08-02 at 14:47, Jan Stocker wrote: > Hi, > my usbd on -current does not call my script (or any command) given in > the detach-value in usbd.conf. This is the output > > > usbd: ucom0 matches ucom0 > usbd: Found action 'Palm Handheld Device' for Palm Handheld, Palm, Inc. > at ucom0usbd: action 0: Palm Handheld Device > vndr=0x0830 prdct=0x0060 > devname: ucom0 > attach='/usr/sbin/ppp -auto palm' > detach='/test.sh' > usbd: Setting DEVNAME='ucom0' > usbd: Executing '/usr/sbin/ppp -auto palm' > Working in auto mode > Using interface: tun0 > usbd: '/usr/sbin/ppp -auto palm' is ok > usbd: processing event queue on /dev/usb > usbd: driver-detach event cookie=3217029340 devname=ucom0 > USB_EVENT_DRIVER_DETACH > > > > > P.S. i am tring to get my usb palm working with FreeBSD. The most > prefered solution is doing this with a ppp connection and a network sync > (all solutions i found in web are not correct but a good advice). > Does anyone has a USB palm directly syncing over USB? -- Jan Stocker <[EMAIL PROTECTED]> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
"got bad cookie" warnings/errors?
Hi gang, I've been seeing lots of these lately: got bad cookie vp 0xc2f40b68 bp 0xc929a1e8 got bad cookie vp 0xc318d124 bp 0xc91d4240 ... I grepped around, and it seems it has something to do with NFS (well, I found this being printf'ed in src/sys/nfsclient/nfs_bio.c I have two NFS machines from which I mount, a 4.8-STABLE machine and a NetBSD 1.6.1 box. I haven't seen any dataloss or panics. But still, should I be worried? How serious is this message? I'm running a very recent CURRENT, cvsupped this week, and a kernel wih Soeren's ATAng patches (which seem to work very well). Cheers, Emiel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Best Known Methods for dual booting WinXP + -current
Try GAG-> GAG.SF.NET -> works with charm. I use it to boot Solaris,FreeBSD and Gates crap with minor fixes. Requires restoring Win MBR, not installing a FreeBSD bootloader, if on the same disk. You can set passwords to all ;p Other thing I'm grasping is a guide in OBSD FAQ for multibooting with NT loader. Happy hacking and peace! DVV ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
openpam_load_module():no pam_wheel.so found
When I do an su command from a normal user on my 5.1-current of yesterday I'm getting a segfault/core dump. /var/log/messages then shows: Aug 10 15:27:44 kukuboo2k su: in openpam_load_module(): no pam_wheel.so found Aug 10 15:27:44 kukuboo2k kernel: pid 54586 (su), uid 0: exited on signal 10 (core dumped) I also get this when I try to do a sh /etc/periodic/weekly/310.locate. I almost there again with 5.1-current and X on my notebook after a disk crash and data loss. Compiled the XFree86-4.3.1 tree and NVIDIA drivers today after a complete cvsup and kernel build yesterday. -- Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
X11 fonts ugly
I compiled XFree86/4.3.1 and installed mozilla 1.4 as package and when I start mozilla fonts show up unevenly weighted (rounding problems?) I wonder if this is a problem with the installed fonts themselves, or with X11? XF86Config looks like this (regarding fontpath): Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" #FontPath "unix/:-1" FontPath"/usr/X11R6/lib/X11/fonts/local/" FontPath"/usr/X11R6/lib/X11/fonts/misc/" FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/Type1/" FontPath"/usr/X11R6/lib/X11/fonts/CID/" FontPath"/usr/X11R6/lib/X11/fonts/Speedo/" FontPath"/usr/X11R6/lib/X11/fonts/75dpi/" FontPath"/usr/X11R6/lib/X11/fonts/100dpi/" EndSection I read somewhere of antialiasing can be switched on or of but I forgot whether it was with X11, mozilla or NVIDIA driver compilation. -- Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usbd does not use detach
> - --- usbd.c.orig Thu Aug 7 18:46:47 2003
> +++ usbd.c Thu Aug 7 18:52:33 2003
> @@ -911,7 +911,7 @@
> break;
> case USB_EVENT_DRIVER_ATTACH:
> if (verbose)
> - - printf("USB_EVENT_DRIVER_DETACH\n");
> + printf("USB_EVENT_DRIVER_ATTACH\n");
> break;
> case USB_EVENT_DRIVER_DETACH:
> if (verbose)
It's here not a second attach output looks like the same:
[EMAIL PROTECTED]:/usr/src/usr.sbin/usbd $ /usr/sbin/usbd -c /etc/usbd.conf
-vvv -d usbd: opened /dev/usb0
usbd: reading configuration file /etc/usbd.conf
usbd: action 1: ActiveWire board, firmware download
vndr=0x0854 prdct=0x0100 rlse=0x
attach='/usr/local/bin/ezdownload -f
/usr/local/share/usb/firmware/0854.0100.0_01.hex ${DEVNAME}'
usbd: action 2: Entrega Serial with UART
vndr=0x1645 prdct=0x8001 rlse=0x0101
attach='/usr/sbin/ezdownload -v -f
/usr/share/usb/firmware/1645.8001.0101 /dev/${DEVNAME}'
usbd: action 3: USB ethernet
devname: [ackr]ue[0-9]+
attach='/etc/pccard_ether ${DEVNAME} start'
detach='/etc/pccard_ether ${DEVNAME} stop'
usbd: action 4: Handspring Visor
vndr=0x082d prdct=0x0100 rlse=0x0100
devname: ugen[0-9]+
attach='/usr/local/bin/coldsync -md -p /dev/${DEVNAME} -t usb'
usbd: action 5: Mouse
devname: ums[0-9]+
attach='/usr/sbin/moused -p /dev/${DEVNAME} -I
/var/run/moused.${DEVNAME}.pid ; /usr/sbin/vidcontrol -m on'
usbd: action 6: Palm Handheld Device
vndr=0x0830 prdct=0x0060
devname: ucom0
attach='/usr/sbin/ppp -auto palm'
detach='/test.sh'
usbd: action 7: USB device
usbd: 7 actions
usbd: opened /dev/usb
usbd: processing event queue on /dev/usb
usbd: driver-attach event cookie=3217029324 devname=ucom0
USB_EVENT_DRIVER_ATTACH
usbd: processing event queue on /dev/usb
usbd: device-attach event at 1060502709.481417000, Palm Handheld, Palm,
Inc.:
vndr=0x0830 prdct=0x0060 rlse=0x0100 clss=0x subclss=0x
prtcl=0x
device names: ucom0
usbd: ucom0 matches ucom0
usbd: Found action 'Palm Handheld Device' for Palm Handheld, Palm, Inc.
at ucom0
usbd: action 0: Palm Handheld Device
vndr=0x0830 prdct=0x0060
devname: ucom0
attach='/usr/sbin/ppp -auto palm'
detach='/test.sh'
usbd: Setting DEVNAME='ucom0'
usbd: Executing '/usr/sbin/ppp -auto palm'
Working in auto mode
Using interface: tun0
Warning: No default entry found in config file.
usbd: '/usr/sbin/ppp -auto palm' is ok
usbd: processing event queue on /dev/usb
usbd: driver-detach event cookie=3217029324 devname=ucom0
USB_EVENT_DRIVER_DETACH
usbd: doing timeout discovery on /dev/usb0
usbd: processing event queue due to timeout on /dev/usb
usbd: doing timeout discovery on /dev/usb0
usbd: processing event queue due to timeout on /dev/usb
usbd: doing timeout discovery on /dev/usb0
usbd: processing event queue due to timeout on /dev/usb
--
Jan Stocker <[EMAIL PROTECTED]>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0 driver
> "Sam" == Sam Leffler <[EMAIL PROTECTED]> writes:
>> I just have to ask: is this in any way related to the a/b/g network
>> card in my laptop that shows up as:
>>
>> [EMAIL PROTECTED]:3:0: class=0x028000 card=0x00011028 chip=0x432414e4
>> rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' class = network
Sam> if ("broadcom" == "atheros") use ath driver; else ask broadcom
Sam> for specs on their hardware.
I was hoping for some more contructive help on that... like how I
might figure this out.
Dave.
--
|David Gilbert, Independent Contractor. | Two things can only be |
|Mail: [EMAIL PROTECTED]| equal if and only if they |
|http://daveg.ca | are precisely opposite. |
=GLO
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "Invalid partition table" error when creating more than oneslice during install?
On Sun, 10 Aug 2003, Darren Pilgrim wrote: > On 2003-08-10, at 15:29:32, Doug White <[EMAIL PROTECTED]> wrote: > > >On Sat, 9 Aug 2003, Darren Pilgrim wrote: > > > >> I'm trying to get 5.1-R installed, but I've run into a problem I don't > >> understand. The disk layout I want should look like this: > >> > >> s1: 20gb, FreeBSD > >> s2: 10gb, Windows > >> s3: ~83gb (the rest of the disk), data > > > >with what tool are you creating s2 and s3? It sounds like the last thing > >that touches it is not creating a proper partition table and your BIOS is > >unhappy. > > Sysinstall, as part of the installation process. Hm. sysinstall is famously bad at making slice tables. The usual solution is to make the Windows partitions first using DOS FDISK on a zeroed disk -- it can usually get the geometry right. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with PS/2 mouse driver in XFree86 4.3.0
--- Mike Bohan <[EMAIL PROTECTED]> wrote:
> That indeed fixed the problem. It does appear like the problem relates
> to a
> specific BIOS version. I'm wondering if there's a certain set of people
> I
> should forward this information on to? It would be nice if a fix like
I have reported this problem two times, but seems got no interest. Here's the last
message I sent
to the list regarding this.
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1580299+0+archive/2003/freebsd-current/20030427.freebsd-current
> this could
> find its way into the -current tree. Thank you Shizuka for your
> intuitive thinking,
> otherwise I surely never would have found a practical solution.
>
> -Mike Bohan
>
>
>
> On Sun, 2003-08-10 at 11:35, Shizuka Kudo wrote:
>
> > --- Mike Bohan <[EMAIL PROTECTED]> wrote:
> > > Yes, adding hint.acpi.0.disabled="1" to /boot/device.hints fixed the
> > > mouse problem.
> >
> > Try this patch on acpi and see if it solves your problem.
> >
> > --- sys/dev/acpica/acpi_pci_link.c.orig Thu Jan 2 02:48:49 2003
> > +++ sys/dev/acpica/acpi_pci_link.c Fri Feb 28 15:18:55 2003
> > @@ -461,7 +461,10 @@
> > return_ACPI_STATUS (error);
> > }
> >
> > +/*
> > if (!(sta & (ACPI_STA_PRESENT | ACPI_STA_FUNCTIONAL))) {
> > +*/
> > + if (!(sta & ACPI_STA_ENABLE)) {
> > ACPI_DEBUG_PRINT((ACPI_DB_ERROR,
> > "PCI interrupt link is not functional - %s\n",
> > acpi_name(handle)));
> >
> >
> > > While this is somewhat pleasing, it also leaves me with uncertainty. I
> > > tried tweaking
> > > basically every CMOS combination I could think of. Do you suppose this
> > > is an
> > > incompatability between the apci driver and my motherboard? The behavior
> >
> > I bet you might have problem with parallel port as well. My machine suffered
> > from this behaviour when someone made the change as shown on the patch. I just
> > reverted that one. If the patch solves your problem, I believe that this is
> > related to BIOS not chipset. I have a Celeron on i815ep and the acpi message is
> > shown below. I just notice that you have a similar acpi signature like mime.
> >
> > acpi0: on motherboard
> > pcibios: BIOS version 2.10
> > Using $PIR table, 10 entries at 0xc00fded0
> >
> > Good luck.
> >
> > > makes
> > > it appear as if something else is fighting over the same resources that
> > > the mouse uses.
> > > This would explain why it can only access the device once a second.
> > > When BIOS
> > > initializes, it does not list any other device with an IRQ of 12 (which
> > > I believe is the mouse interface).
> > > Does anyone have any experience with devices such as mice flaking out
> > > with apci?
> > > Thanks again!
> > >
> > > -Mike Bohan
> > >
> > >
> > > On Sun, 2003-08-10 at 04:02, Shizuka Kudo wrote:
> > >
> > > > --- Mike Bohan <[EMAIL PROTECTED]> wrote:
> > > > > Hello,
> > > > >
> > > > > I have an Abit KT266 based motherboard and am having some trouble using
> > > > > the PS/2 mouse driver under XFree86. I have the protocol set to "auto",
> > > > > and the device set to /dev/psm0. This configuration has worked with
> > > > > this same Intellimouse in the past. The symptoms are that that when the
> > > > > mouse is moved, the cursor is only updated about once a second. After
> > > > > searching google, I found the following URL in which another person
> > > > > experienced the same problem (from freebsd-bugs). Apparently it only
> > > > > shows up on certain chipsets (VIA based). I tried several other PS/2
> > > > > mice, to no avail (same outcome). My system is running a day old
> > > > > -current build, but this other fellow reported the problem in 5.0 (does
> > > > > not affect 4.x). I'm wondering if anyone else has experienced this
> > > > > problem, and if so, are there any work-arounds? I've attached my
> > > > > 'dmesg' output, in the hopes that the information will be of value.
> > > > > Thank you in advance!
> > > > >
> > > >
> > > > Does disabling acpi make your mouse working?
> > > >
> > > > > URL:
> > > > > http://lists.freebsd.org/pipermail/freebsd-bugs/2003-April/000426.html
> > > > >
> > > > > -Mike Bohan
> > > > >
> > > > > Copyright (c) 1992-2003 The FreeBSD Project.
> > > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> > > > > The Regents of the University of California. All rights
> > > > > reserved.
> > > > > FreeBSD 5.1-CURRENT #3: Fri Aug 8 09:10:54 EDT 2003
> > > > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CABOOSE
> > > > > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0424000.
> > > > > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0424244.
> > > > > Timecounter "i8254" frequency 1193182 Hz
> > > > > CPU: AMD Athlon(tm) processor (1333.91-MHz 686-cl
ACPI sleep_delay caused reboot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I cvsup'd over the weekend and my laptop started to reboot after the second resume. I checked the hw.acpi.sleep_delay and the default value seems to be changed to 5. This would happen with earlier ACPI imports, but the default was zero, so it would be fine. Can't seem to get and crash dumps since it just restarts. I'll send the dmesg and acpidump info when I'm back at home. - -- Anish Mistry -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/N7z4xqA5ziudZT0RAlb0AKCAVDQfin+UDf0aoE7NirEU39cqyACePN9h J6wZj2Ngd5WNrsb9qJN8g8w= =pKDO -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Adaptec AIC7902 Ultra320 Problems
On Mon, Aug 11, 2003 at 11:14:49AM -0600, Justin T. Gibbs wrote: > > I've got another drive now to mess about with: > > > > da0: Fixed Direct Access SCSI-3 device > > > > And I get the same problems. > > I would have to see the driver messages to verify that. > > You are running down rev. firmware on this drive and early Daytona > firmware revs had some serious problems. Have you contacted > Hitachi (they bought the IBM drive division) for a firmware update? You can get firmware and drivers for these drives from Hitachi: http://www.hgst.com/support/ -- Craig Rodrigues http://crodrigues.org [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
LOR (vm_fault.c:286 and vm_kern.c:323)
I don't think I've seen this i386 traceback before. Is it harmless as well? Kris lock order reversal 1st 0xc4797e74 vm object (vm object) @ /a/asami/portbuild/i386/src-client/sys/vm/vm_fault.c:286 2nd 0xc082f110 system map (system map) @ /a/asami/portbuild/i386/src-client/sys/vm/vm_kern.c:323 db> trace Debugger(c041242d,c082f110,c044fd31,c044fd31,c044fbb2) at Debugger+0x54 witness_lock(c082f110,8,c044fbb2,143,c028160b) at witness_lock+0x687 _mtx_lock_flags(c082f110,0,c044fbb2,143,3) at _mtx_lock_flags+0xba _vm_map_lock(c082f0b0,c044fbb2,143,c04ad840,2b3) at _vm_map_lock+0x36 kmem_malloc(c082f0b0,1000,101,d8f38ae4,c03ad756) at kmem_malloc+0x3a page_alloc(c083a1c0,1000,d8f38ad7,101,0) at page_alloc+0x27 slab_zalloc(c083a1c0,101,8,c0451605,673) at slab_zalloc+0xc6 uma_zone_slab(c083a1c0,101,c0451605,673,0) at uma_zone_slab+0xe8 uma_zalloc_internal(c083a1c0,0,101,6f7,0) at uma_zalloc_internal+0x4f uma_zfree_arg(c40e19a0,d7a9e450,0,851,8000) at uma_zfree_arg+0x2c3 swp_pager_meta_ctl(c4797e74,0,0,2,d8f38cbc) at swp_pager_meta_ctl+0x10f swap_pager_unswapped(c0c50200,1,c0438248,b4,d8f38c54) at swap_pager_unswapped+0x2a vm_fault(c48a1b00,284d5000,2,8,c4f7e720) at vm_fault+0x1182 trap_pfault(d8f38d48,1,284d5660,280,284d5660) at trap_pfault+0xe9 trap(2f,807002f,bfbf002f,0,28094630) at trap+0x1f3 calltrap() at calltrap+0x5 --- trap 0xc, eip = 0x284d3040, esp = 0xbfbff3bc, ebp = 0xbfbff3c4 --- db> pgp0.pgp Description: PGP signature
Re: New panics
On Sun, 10 Aug 2003, Lukas Ertl wrote: > 5.1-CURRENT FreeBSD 5.1-CURRENT #12: Wed Aug 6 21:49:32 CEST 2003 > > Fatal trap 12: page fault while in kernel mode > cpuid = 3; lapic.id = 0700 > fault virtual address = 0xbfcb09a0 > fault code= supervisor read, page not present > instruction pointer = 0x8:0xc035ea65 > stack pointer = 0x10:0xe0ba4acc > frame pointer = 0x10:0xe0ba4ad8 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 40 (bufdaemon) > trap number = 12 > panic: page fault > cpuid = 3; lapic.id = 0700 > boot() called on cpu#3 > > syncing disks, buffers remaining... > > Fatal trap 12: page fault while in kernel mode > cpuid = 3; lapic.id = 0700 > fault virtual address = 0x24 > fault code= supervisor read, page not present > instruction pointer = 0x8:0xc01f8ddb > stack pointer = 0x10:0xdf150b74 > frame pointer = 0x10:0xdf150b88 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 3 (g_up) > trap number = 12 > panic: page fault > cpuid = 3; lapic.id = 0700 > boot() called on cpu#3 > Uptime: 1d0h49m45s > Dumping 1023 MB > 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 > 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 > 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008 > --- Forget that backtrace, at least for this current problem, it seems like the kernel panicked inside the coredump routine again, and I got the coredump of the second panic :-/. (This would correspond to the instruction pointer of the second panic, which shows as "propagate_priority" in "nm kernel". If I run "nm /usr/local/crash/kernel.3 | grep c035e" (the IP of the first panic message), I get this: c035ef70 t i386_protection_init c035e030 T pmap_change_wiring c035ecf0 T pmap_clear_modify c035ee30 T pmap_clear_reference c035e0a0 T pmap_copy c035e690 T pmap_copy_page c035e9f0 T pmap_is_modified c035efb0 T pmap_mapdev c035e7e0 T pmap_page_exists_quick c035ea90 T pmap_page_protect c035e840 T pmap_remove_pages c035ebf0 T pmap_ts_referenced c035e390 T pmap_zero_page c035e4c0 T pmap_zero_page_area c035e5f0 T pmap_zero_page_idle c035e350 t pmap_zpi_switchin12 c035e370 t pmap_zpi_switchin2 c035e380 t pmap_zpi_switchin3 Closest comes pmap_is_modified, I guess. regards, le -- Lukas Ertl eMail: [EMAIL PROTECTED] UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: JAIL and SSH out?
From: <[EMAIL PROTECTED]> > Is there a way to ssh out from a jail? > > jail$ ssh otherhost > Permission denied, please try again. > Permission denied, please try again. > Permission denied (publickey,password). > jail$ ssh -V > OpenSSH_3.6.1p1 FreeBSD-20030423, SSH protocols 1.5/2.0, OpenSSL 0x0090701f > > jail$ mount > ... > devfs on /10.1.1.1/dev (devfs, local) > ... Yes, you can use ssh to access other systems from a jail. I currently have 4 jails runing on one host and can ssh from any of them. jail -> remote jail -> jailN jail -> host host -> jail remote -> jail Do you have sshd running on 'otherhost'? Scot ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: openpam_load_module():no pam_wheel.so found
On Sun, Aug 10, 2003 at 10:08:15AM -0400, Robert Watson wrote: > > On Sun, 10 Aug 2003, Christoph Kukulies wrote: > > > When I do an su command from a normal user on my 5.1-current of > > yesterday I'm getting a segfault/core dump. > > > > /var/log/messages then shows: > > Aug 10 15:27:44 kukuboo2k su: in openpam_load_module(): no pam_wheel.so found > > Aug 10 15:27:44 kukuboo2k kernel: pid 54586 (su), uid 0: exited on signal 10 (core > > dumped) > > > > I also get this when I try to do a sh /etc/periodic/weekly/310.locate. > > > > Did you mergemaster when updating last? pam_wheel has, I believe, been > replaced with pam_group. A coredump is an undesirable result, of course, > but I suspecft that this is the trigger. If you want to follow up on the > core dump, build a copy of su with debugging symbols, and enable > kern.sugid_coredump to get a coredump and stack tracfe from su (turn it > off again when done). Thanks again for the intermediate help (to look in /etc/pam.d) and this directory didn't get updated. There was the old 5.0 stuff in it. Now su works again. -- Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI battery state and resume not working on Inspiron 5150
> Date: Sat, 9 Aug 2003 23:17:57 -0400 > From: Scott Lambert <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > On Sat, Aug 09, 2003 at 08:53:54PM -0400, David Gilbert wrote: > > > "Kevin" == Kevin Oberman <[EMAIL PROTECTED]> writes: > > > > Kevin> Sorry, Joe. By the way, are you suspending with "acpiconf -s3"? > > Kevin> Have you tried creating a hibernation partition (slice) and > > Kevin> using -s4? That appears to work better than suspend on most > > Kevin> platforms that support it at all. > > Kevin> > > Kevin> -- R. Kevin Oberman, Network Engineer > > > > What does a hibernation partition look like? > > > > My dell has a 31 meg partition that I havn't touched and my FreeBSD > > partition. > > And can you determine what the hibernation partition should look like > from an acpidump? I have a toshiba that only lists : > > hw.acpi.supported_sleep_state: S1 S4 S5 > > And I wiped the disk so fast after I bought it, that I've never seen the > hibernation setup that originally came with it. I hope my response to David Gilbert answered this, as well. S4 is "hibernate" and S3 is suspend. S1 simply stops the CPU clock and is, as far as I can tell, useless. Since your system lacks S3, it does not look like suspend is an option. Most systems don't come with a hibernation partition as hibernation is a BIOS function and Windows now has the ability to hibernate to a file in any Windows partition. Try checking with the manufacturer's web site or tech support to see if they have a tool to do this or information on using fdisk to do it. Since your BIOS lists S4, it should do it. I believe that all that is required is a slice slightly bigger (one page bigger?) than the total memory size with a special type field (not FAT32, FAT16, NTFS, FreeBSD or any other normal ID). BIOS sees this in the partition table for the disk and initiates the memory dump when S4 is requested. If no suitable partition is found, it should ignore the request. -- 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
GEOM/vinum compatibility (was: vinum lock panic at startup -current)
On Friday, 8 August 2003 at 15:24:09 +0200, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes: > >> Panicstring: mutex Giant owned at /usr/src/sys/geom/geom_dev.c:198 > > Ok, then I think I know what it is. > > Vinum appearantly does not go through SPECFS but rather calls into > the disk device drivers directly. That is a pretty wrong thing to > do, It used to be the standard. What's the issue? > and it seems that vinum does not respect the D_NOGIANT flag which > GEOM recently started setting. Probably because it didn't know about it. As I've said before, it would be nice to be informed about the changes you're making, particularly given your stated intention of doing no work on Vinum. Could you please give details (privately if you want, but I think this could be of interest to other people too). Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: Problem with PS/2 mouse driver in XFree86 4.3.0
--- Mike Bohan <[EMAIL PROTECTED]> wrote: > Hello, > > I have an Abit KT266 based motherboard and am having some trouble using > the PS/2 mouse driver under XFree86. I have the protocol set to "auto", > and the device set to /dev/psm0. This configuration has worked with > this same Intellimouse in the past. The symptoms are that that when the > mouse is moved, the cursor is only updated about once a second. After > searching google, I found the following URL in which another person > experienced the same problem (from freebsd-bugs). Apparently it only > shows up on certain chipsets (VIA based). I tried several other PS/2 > mice, to no avail (same outcome). My system is running a day old > -current build, but this other fellow reported the problem in 5.0 (does > not affect 4.x). I'm wondering if anyone else has experienced this > problem, and if so, are there any work-arounds? I've attached my > 'dmesg' output, in the hopes that the information will be of value. > Thank you in advance! > Does disabling acpi make your mouse working? > URL: > http://lists.freebsd.org/pipermail/freebsd-bugs/2003-April/000426.html > > -Mike Bohan > > Copyright (c) 1992-2003 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD 5.1-CURRENT #3: Fri Aug 8 09:10:54 EDT 2003 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CABOOSE > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0424000. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0424244. > Timecounter "i8254" frequency 1193182 Hz > CPU: AMD Athlon(tm) processor (1333.91-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x644 Stepping = 4 > > Features=0x183fbff > AMD Features=0xc044 > real memory = 268369920 (255 MB) > avail memory = 256196608 (244 MB) > Pentium Pro MTRR support enabled > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > pcibios: BIOS version 2.10 > Using $PIR table, 8 entries at 0xc00fdef0 > acpi0: power button is handled as a fixed feature programming model. > Timecounter "ACPI-fast" frequency 3579545 Hz > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > acpi_cpu0: on acpi0 > acpi_tz0: on acpi0 > acpi_button0: on acpi0 > acpi_button1: on acpi0 > pcib0: port > 0x5000-0x500f,0x4080-0x40ff,0x4000-0x407f,0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib0: slot 8 INTA is routed to irq 10 > pcib0: slot 9 INTA is routed to irq 5 > pcib0: slot 11 INTA is routed to irq 10 > agp0: mem 0xe800-0xebff at > device 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pcib0: slot 1 INTA is routed to irq 11 > pcib1: slot 0 INTA is routed to irq 11 > pci1: at device 0.0 (no driver attached) > dc0: port 0xd000-0xd0ff mem > 0xef00-0xef0003ff irq 10 at device 8.0 on pci0 > dc0: Ethernet address: 00:04:5a:40:b5:0d > miibus0: on dc0 > ukphy0: on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > dc1: port 0xd400-0xd4ff mem > 0xef001000-0xef0010ff irq 5 at device 9.0 on pci0 > dc1: Ethernet address: 00:a0:cc:34:54:93 > miibus1: on dc1 > dcphy0: on miibus1 > dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > dc2: <82c169 PNIC 10/100BaseTX> port 0xd800-0xd8ff mem > 0xef002000-0xef0020ff irq 10 at device 11.0 on pci0 > dc2: Ethernet address: 00:a0:cc:d6:ea:b4 > miibus2: on dc2 > bmtphy0: on miibus2 > bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > isab0: at device 17.0 on pci0 > isa0: on isab0 > atapci0: port 0xdc00-0xdc0f at device > 17.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > fdc0: port > 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > 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 IntelliMouse, device ID 3 > orm0: at iomem 0xc-0xcbfff on isa0 > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on > isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > Timecounter "TSC" frequency 1333905046 Hz > Timecounters tick every 1.000 msec > DUMMYNET initialized (011031) > ipfw2 initialized, divert disabled, rule-based forwarding enabled, > default to accept, logging disabled > IP Filter: v3.4.31 initialized. Default = pass all, Logging = enabled > acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0% > ad0: 39083MB [79408/16/63] at ata0-master UDMA100 > ad1: 29333MB [59598/16/63] at ata0-slave UDMA66 > ad2: 43979MB [89355/16/63] at ata1-master UDMA100 > ad3: 43979MB [89355/16/63] at ata1-slave UDMA100 > Mounting root from ufs:/dev/ad0s1a > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsub
Re: 5.1, Data Corruption, Intel, Oh my! [patch]
Since some people have gotten back to me telling me that they have apparently been able to boot with the patch, I have a suspicion that it could be something in your config files. The other submitter already sent me his, so can you please send me yours (along with a 'dmesg' when you boot with a clean -current, without the patch) so that I can try building something similar here to hopefully track this down? (send them off-list, please) If anyone else is seeing something similar, also please send me your kernel config files with stock -current 'dmesg' output off-list. Thanks, Bosko On Mon, Aug 11, 2003 at 05:14:14PM -0700, Kevin Oberman wrote: > Bosko, > > I am seeing a very similar thing on my CURRENT system after applying > your patch It's also when probing APM. I suspect it's not an issue with > ACPI. > > It is also at least very similar to the crash I see when I add > DISABLE_PSE to my kernel. > > Here is mine, as transcribed by hand from my IBM T30 with P4-M > uniprocessor: > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x1c > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc06492a0 > stack pointer = 0x10:0xc0c219a2 > frame pointer = 0x10:0xc0c21b0e > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags= interrupt enabled, resume, IOPL = 0 > current process = 0 (swapper) > kernel: type 12 trap, code=0 > Stopped at vm_fault+0x240: cmpxchgl #edx,0x1c(%ecx) > db> trace > vm_fault(c102f000,c000,2,0,c07470a0) at vm_fault+240 > trap_pfault(c0c21b9e,0,c4d8,10,c4d8) at trap_pfault+0x1e3 > trap(1bc40018,10,6fe40060,1c,0) at trap+0x2cd > calltrap() at calltrap+0x5 > --- trap 0xc, eip = 0x58de, esp = 0xc0c21bde, epb = 0xc0c21be4 --- > (null)(1bf80058,0,530e0102,80202,5059f6) at 0x58de > db> > > The kernel was cvsuped this afternoon and patched only with your > patch. I had to panic twice to get a core dump and I have doubts about > its validity. > -- > 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 -- Bosko Milekic * [EMAIL PROTECTED] * [EMAIL PROTECTED] TECHNOkRATIS Consulting Services * http://www.technokratis.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
acpica/acfreebsd.h bug with boot code (stand.h)
/usr/src/sys/contrib/dev/acpica/acfreebsd.h includes ctype.h which is incompatible with its redefinition in /usr/include/stand.h As result we got: ===> i386/libi386 cc -O -pipe -march=pentium3 -ffreestanding -DCOMPORT=0x3f8 -DCOMSPEED=9600 -DTERM_EMU -I/usr/src/sys/boot/i386/libi386/../../common -I/usr/src/sys/boot/i386/libi386/../btx/lib -I/usr/src/sys/boot/i386/libi386/../../../contrib/dev/acpica -I/usr/src/sys/boot/i386/libi386/../../.. -I. -I/usr/src/sys/boot/i386/libi386/../../../../lib/libstand/ -ffreestanding -mpreferred-stack-boundary=2 -c /usr/src/sys/boot/i386/libi386/biosacpi.c In file included from /usr/src/sys/contrib/dev/acpica/acfreebsd.h:165, from /usr/src/sys/boot/i386/libi386/biosacpi.c:33: /usr/include/ctype.h:88: syntax error before "int" *** Error code 1 Please fix it somehow. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SAN disk with freebsd?
In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes: >Anyone using a storage area network with freebsd (or linux)? Anything to >recommend as working well or to stay way from? I have a customer doing that. Works ok. You need qlogic 2300 cards and the isp driver which Matt Jacob maintains. -- 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Porting 4.x code to 5.x: zfreei, zinit, struct vm_zone
Hi, I am trying to port Randall Stewart's SCTP implementation from -STABLE to -CURRENT. The code makes use of zfreei(), zinit(), etc. and struct vm_zone. How can I port this code to -CURRENT? Can I start by replacing these calls be directly replaced with the uma_* versions: zinit->uma_zcreate zfreei ->uma_zfree How do I deal with the struct vm_zone? Thanks. -- Craig Rodrigues http://crodrigues.org [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: smp in 5.1
I've been running 5.1-Current since its release on a Dell Precision 410 with dual P-III 500's No SMP problems here at all.. Its been extremely stable for me thus far. Darin - -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Kargl Sent: Monday, August 11, 2003 7:10 PM To: Andy Farkas Cc: [EMAIL PROTECTED]; Eriq Lamar Subject: Re: smp in 5.1 On Tue, Aug 12, 2003 at 08:25:38AM +1000, Andy Farkas wrote: > On Mon, 11 Aug 2003, Eriq Lamar wrote: > > > Is there any advantage in 5.1 over 4.8 for two amd mp's. and if so > > could someone tell what they are. I am interested in building dual > > system using mp's but not sure which version would be better. > > Scheduling in 5.1 is broken (sched_ule doesn't even work*). > > Stick with 4.8. > > * for me, sched_ule completely locks up my box, no ping, no keybd. > Exact same kernel with sched_4bsd works fine. > Strange. ULE has worked fine on my UP system for several months and the SMP system I recently obtained from a co-worker hasn't panicked while running ULE. Can you drop into ddb and trace the problem with ULE on your system? -- Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: help me out please : contigmalloc1: size must not be 0
On Sun, 10 Aug 2003, S. Koers wrote: > I am receiving this error while booting from the 5.0 miniinst.iso CD: contigmalloc1: > size must not be 0 > My pc is a IBM a30 notebook. > > Please help me, so I can install FreeBSD on that machine, Try 5.1? :) > > thanks > Sjoerd, Amsterdam > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Best Known Methods for dual booting WinXP + -current
Hi, You can boot FreeBSD from the XP boot manager: see http://bsdvault.net/sections.php?op=viewarticle&artid=88 [This used to be in the FAQ and perhaps should be resurrected there.] At 21:10 7/8/03, John Reynolds wrote: hello all, Having had a positive experience thus far with 5.1-RELEASE and -current beyond that on one of the new boxes I recently built, it is now time to build up the dual-boot system (BSD for me, WinXP for the wife ;). I've read different reports (some from laptop users) about using the WinXP loader to boot FreeBSD and I've also read reports that people used the standard boot-easy to boot both (while even others using GRUB). Are there currently any issues with dual-booting 5.1-RELEASE and/or -current along with Windows XP (probably SP1)? This would be on the same physical disk. What do you other -current users who are faced with dual booting XP do for the most part? Thanks, -Jr -- John & Jennifer Reynolds johnjen at reynoldsnet.orgwww.reynoldsnet.org Sr. Physical Design Engineer - WCCG/CCE PDE jreynold at sedona.ch.intel.com Running FreeBSD since 2.1.5-RELEASE. FreeBSD: The Power to Serve! "Unix is user friendly, it's just particular about the friends it chooses." ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED] fax +44 (0)118 989 4254 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
emacs21 TCP connection failed after update.
Hi, after I updated the system, I try to use navi2ch, a client for WWW based BBS system written in emacs-lisp, and found It often failes to connect to the server with EALREADY. Then I investigate the problem, I found the code(open-network-stream function @emacs21.3/src/process.c) assumes that connection attempt is aborted when a program got any signal during connect(2) is issued and the next attempt to connect(2) fails with EALREADY after a connect(2) is interrupted. What shall we do? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: INET6 in world
On Fri, Aug 08, 2003 at 12:40:06AM -0700, Terry Lambert wrote: > 6)The last time I tried the "experimental" version, it did > not correctly interoperate with AIX or FreeBSD, but worked > fine Windows-to-Windows, so they've done *something* to it > to embrace and extend it. I find the AIX IPv6 stack "special", but I've only used it under 4.3.3. The XP and 2003 IPv6 stacks have worked fine for me (though, as you say, they don't have an iked yet): they both autoconfigure from a FreeBSD router, do putty, dns, http and lpd over IPv6, and I've had samba talk to the 2003 box over IPv6. David. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
