On Wed, Nov 03, 2010 at 08:27:02AM +0100, Bernhard Schmidt wrote:
> ...
> There is ieee80211_notify_radio(), granted iwn(4) misses the calls.. that
> function is supposed to notify upper layers about the radio state (0 = off, 1
> = on). Anyways, once wpa_supplicant import/update is done, I'll pro
On Tue, Nov 02, 2010 at 06:30:10PM +0100, Bernhard Schmidt wrote:
>
> Thanks. I had quick look into that and I currently do not see an easy
> way to address that issue, as in tell wpa_supplicant about the device's
> state. This might change though once a newer wpa_supplicant has been
> importe
On Tue, Nov 02, 2010 at 08:40:54AM +0100, Bernhard Schmidt wrote:
>
> > > I have the switch on this laptop in position to disable the wireless
> > > device (iwn(4)). Is there some way wpa_supplicant (or something) might
> > > be able to recognize that this is a pointless exercise?
> >
> > We
FreeBSD 9.0-CURRENT #31 r214621M
Nov 1 15:09:40 d130 wpa_supplicant[569]: Failed to initiate AP scan.
Nov 1 15:10:10 d130 last message repeated 3 times
Nov 1 15:10:50 d130 last message repeated 4 times
...
Nov 1 15:11:00 d130 wpa_supplicant[569]: Failed to initiate AP scan.
Nov 1 15:11:10 d13
On Fri, Oct 01, 2010 at 08:56:13PM -0500, Brandon Gooch wrote:
> On Fri, Oct 1, 2010 at 8:33 PM, David Wolfskill wrote:
> > On Fri, Oct 01, 2010 at 04:30:01PM -0700, David Wolfskill wrote:
> >> ...
> >> I found the disabling the "Module Bay" appea
On Mon, Oct 04, 2010 at 10:44:18AM +0300, Andriy Gapon wrote:
> ...
> Interesting!
:-}
> So, init thread is blocked in vfs_mountroot()->g_waitidle() waiting for geom
> to
> complete probing cd device, but the latter is blocked in cam_periph_getccb()
> waiting for a ccb.
> Can you try to reproduc
On Sun, Oct 03, 2010 at 03:42:51PM -0700, Julian Elischer wrote:
> ...
> well you got the stacktrace of the keyboard handler since you got into
> ddb via the keyboard..
OK
> you need to see what ELSE is running.. especially the initial threads.
> and look at THOSE stacks
Ah. My lack of pr
On Sun, Oct 03, 2010 at 02:52:19PM +0300, Andriy Gapon wrote:
> on 03/10/2010 14:28 David Wolfskill said the following:
> [snipped]
>
> Can't you just drop to DDB prompt and examine where the threads are?
Eh -- thanks for the reality check; I needed that. :-}
OK; I enab
On Fri, Oct 01, 2010 at 08:38:59PM -0700, David Wolfskill wrote:
> On Fri, Oct 01, 2010 at 08:56:13PM -0500, Brandon Gooch wrote:
> > ...
> > > Any ideas on what mught be causing CURRENT to hang -- sometimes
> > > -- given that it appears to involve the Modular Bay (o
On Fri, Oct 01, 2010 at 08:37:50PM -0700, Garrett Cooper wrote:
> ...
> > albert(8.1-S)[11] ls -lT
> > total 196
> > -rw-r--r-- 1 david wheel 11497 Oct 1 20:19:06 2010 console.log
> > -rw-r--r-- 1 david wheel 60397 Oct 1 19:26:23 2010 dmesg.boot
> > -rw-r--r-- 1 david wheel 114752 Oct
On Fri, Oct 01, 2010 at 08:37:50PM -0700, Garrett Cooper wrote:
> ...
> This might sound like a stupid idea, but can you try booting with
> a CD/DVD in the drive?
Ah -- sorry about that. :-(
OK; it may be a bit before I get a successful verbose boot without
ATA_CAM and with the CD/DVD drive i
On Fri, Oct 01, 2010 at 08:56:13PM -0500, Brandon Gooch wrote:
> ...
> > Any ideas on what mught be causing CURRENT to hang -- sometimes
> > -- given that it appears to involve the Modular Bay (or the specific
> > device that is in the bay during the hang)?
> >
>
> If you haven't already, it may b
On Fri, Oct 01, 2010 at 07:22:33PM -0700, Garrett Cooper wrote:
> ...
> > Any ideas on what mught be causing CURRENT to hang -- sometimes
> > -- given that it appears to involve the Modular Bay (or the specific
> > device that is in the bay during the hang)?
>
> Do you have boot -v output?
Ye
On Fri, Oct 01, 2010 at 04:30:01PM -0700, David Wolfskill wrote:
> ...
> I found the disabling the "Module Bay" appears to avoid the hang --
> reliably.
>
> That appears to be the minimally-invasive change necessary to avoid the
> hang.
>
Until I realized what
On Fri, Oct 01, 2010 at 02:20:38PM -0700, David Wolfskill wrote:
> I have recently acquired a new laptop (to replace the "Frankenlaptop"
> I've been using for the last several years).
> ...
> While I'm not about to assume that this indicates something wrong
> wi
I have recently acquired a new laptop (to replace the "Frankenlaptop"
I've been using for the last several years).
The new machine is a Dell Precision M4400, so it's pretty recent
technology compared to what I'm used to. :-}
I installed FreeBSD 8.1-R on slice 1, customized it a bit to work in my
On Sat, Aug 14, 2010 at 07:05:40PM +0200, Bernhard Schmidt wrote:
> ...
> > OK; I reverted by doing this:
> >
> > g1-46(9.0-C)[1] cd /usr/src
> > g1-46(9.0-C)[2] svn merge -c -211295 file:///svn/freebsd/src/base/head
> > --- Reverse-merging r211295 into 'sys':
> > U sys/net80211/ieee80211_node.c
On Sun, Aug 15, 2010 at 12:07:13AM +0800, Adrian Chadd wrote:
> You should be able to revert the ath changes reasonably easy.
>
> Would you mind doing that and see if that fixes or contributes to the problem?
OK; I reverted by doing this:
g1-46(9.0-C)[1] cd /usr/src
g1-46(9.0-C)[2] svn merge -c
On Sun, Aug 15, 2010 at 12:07:13AM +0800, Adrian Chadd wrote:
> You should be able to revert the ath changes reasonably easy.
>
> Would you mind doing that and see if that fixes or contributes to the problem?
Will do; I'll report back when I have information to report -- probably
within 30 minute
Before I get to the "good stuff", I'll note that:
* I'm no longer running a VIMAGE kernel, so that possible source of
confusion should be absent.
* The hardware in question (a miniPCI device in my laptop) has been
working under stable/7 and stable/8 (so I believe that there should be
nothin
On Sat, Jul 31, 2010 at 12:12:50AM +0200, Marko Zec wrote:
>
> VIMAGE kernels do not properly set curvnet context when dynamically attaching
> devices (such as USB or pccard NICs), that's why the dereferencing V_if_index
> fails. You can use the "show pcpu" and "show vnets" DDB commands to
On Sat, Jul 31, 2010 at 12:12:50AM +0200, Marko Zec wrote:
> ...
> > Symptom is that I get a panic on insert (or kernel probe, if it's
> > inserted already at boot time) of a PCcard NIC.
>
>
> VIMAGE kernels
Oh -- right. I fogot that I had configured this kernel for VIMAGE so
Julian to demo som
On Fri, Jul 30, 2010 at 09:23:37PM +, Benjamin Stuppin wrote:
> ...
> when using tmpfs for /tmp i'd probably add the "mode=1777" option, else you
> would mount /tmp with default options and without the sticky bit which could
> cause some problems.
I have never needed to do that.
d254(9.0-C
On Thu, Jul 29, 2010 at 08:35:30AM -0700, gahn wrote:
> hi all:
>
> is it possible to create /tmp directory under swap space?
Certainly; case in point:
localhost(9.0-C)[4] uname -v
FreeBSD 9.0-CURRENT #71 r210558M: Wed Jul 28 07:46:04 PDT 2010
r...@localhost:/usr/obj/usr/src/sys/CANARY
loc
On Mon, Jul 26, 2010 at 10:47:58AM -0400, Michael Butler wrote:
> On 07/26/10 09:55, David Wolfskill wrote:
> > This is for GENERIC i386 kernel, running on head at r210462, sources
> > updated to r210495:
> [ .. ]
>
> > ===> usr.bin/kdump (depend)
> > sh /usr
This is for GENERIC i386 kernel, running on head at r210462, sources
updated to r210495:
>>> World build started on Mon Jul 26 05:12:42 PDT 2010
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the o
On Sat, Jun 26, 2010 at 12:10:57PM +0300, Daniel Braniss wrote:
> ...
> what do you see when you type boot0cfg -v ...?
> gpart show?
> then try
> gpart set -a active -i n aacd0
> n will probably be 5.
>
> bottom line, the MBR is NOT being updated by boot0cfg
OK; here's what I see -- note t
On Fri, Jun 25, 2010 at 08:37:36AM -0400, John Baldwin wrote:
> On Friday 25 June 2010 7:40:11 am David Wolfskill wrote:
> > Well, one one of my machines -- I realize that there are some
> > machines for which it's been problematic for a while. And all of
> > the mach
Well, one one of my machines -- I realize that there are some
machines for which it's been problematic for a while. And all of
the machines I'm using run FreeBSD/i386.
But it had been working on my build machine since I acquired it (a few
months ago) in daily use.
Of course, I didn't notice the
On Tue, May 11, 2010 at 08:30:09PM -0700, K. Macy wrote:
> Please try 207949
> ...
The panic (this time) didn't show up until about 10 seconds after the
login: prompt showed up on the serial console. Here's what it looks
like:
...
3 Select option, [Enter] for default 3
3 or [Space]
On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote:
> Could you please try with 207902?
> ...
I saved that environment (documented elsewhere ini the thread), then
performed the normal (for me) daily update, this time, to r207911.
Again, I see a panic during transition from single-user mode t
On Mon, May 10, 2010 at 03:52:07PM -0700, David Wolfskill wrote:
> On Mon, May 10, 2010 at 03:39:11PM -0700, K. Macy wrote:
> > Are you not able to dump core?
> >
>
> Here's the crash summary; I can put the dump on my Web server on request.
> (It weighs in
On Mon, May 10, 2010 at 02:32:14PM -0700, K. Macy wrote:
> Could you please try with 207902?
> ...
First, thanks for the response.
OK; I grabbed r207902 & applied it (via "patch -p1"), then rebuilt the
kernel & rebooted; here's the panic now:
3 Select option, [Enter] for default 3
3 or [
On Mon, May 10, 2010 at 08:22:43PM +0200, Ed Schouten wrote:
> ...
> You don't happen to have a backtrace?
Oops -- sorry; got caught up in getting ready to head in to work:
db> bt
Tracing pid 20 tid 100067 td 0xc5a19000
_mtx_lock_flags(58,0,c0cd2d5b,570,80,...) at _mtx_lock_flags+0x46
flowtable_f
During transition to multi-user mode on first reboot after upgrading
from r207812 -> r207844; from the sserial console:
3 Select option, [Enter] for default 3
3 or [Space] to pause timer 0 3
@DY
GDB: no debug ports present
KDB: debugger
On Fri, Apr 30, 2010 at 07:27:32PM +0300, Kostik Belousov wrote:
> ...
> Please try r207438.
OK; that worked -- thanks!
I actually merely hand-edited the one file & rebuilt the kernel; boot to
multi-user mode was uneventful, and:
FreeBSD freebeast.catwhisker.org 9.0-CURRENT FreeBSD 9.0-CURRENT #
This was during the single- to multi-user transition on boot; I was
going to skip the output from the LORs, but I suspect that some of
them might be relevant; see below.
I can leave the system in this state for a whle, but I normally power it
off (to reduce heat, noise, and electricity consumption
As these things go, this probably isn't as critical as most thinsg
disussed on this list, but I happened to notice it today, built a
debugging world and at least cornered the annoying little varmint.
Sorry; no patch at this time. :-(
Here's how to reproduce it: while running CURRENT, invoke dc(1)
On Fri, Mar 19, 2010 at 01:09:11PM +, Rui Paulo wrote:
> ...
> > Do you all have either out-of-tree modules or modules that you did not
> > re-build when re-compiling your kernel?
>
> I have in-tree modules, but I tried a clean build.
I corresponded with kmacy@ a bit yesterday.
Pending resol
On first reboot after building & installing; yesterday (@r205249) was OK:
3 1. Boot FreeBSD [default] 3 |_| |_| \___|\___|
3 2. Boot FreeBSD with ACPI disabled 3 _ _
3 3. Boot FreeBSD in Safe Mode 3 | _ \ / | __ \
3 4. Boot Fr
On Thu, Mar 11, 2010 at 09:04:40AM -0800, David Wolfskill wrote:
> My build machine (dmesg attached) is a dual CPU, single-core box; my
> laptop is a single CPU, single-core box. I track head on each daily;
> while the build machine has been locking up during the transition to
> mul
My build machine (dmesg attached) is a dual CPU, single-core box; my
laptop is a single CPU, single-core box. I track head on each daily;
while the build machine has been locking up during the transition to
multi-user mode since Tuesday (when I had built CURRENT at r204909;
previous was r204866, o
>Date: Mon, 24 Nov 2003 09:34:08 +0600 (NOVT)
>From: "Maxim M. Kazachek" <[EMAIL PROTECTED]>
> So, imagine, i'm accidentally deleted /bin with your most wanted
>static sh... And, of course, due to static nature of /bin/sh it was
>removed from /rescue? Nothing will protect you from shooting i
Perhaps it's unrealistic to expect this to work, but on each of the
machines where I run -CURRENT, I also run -STABLE (on other slices),
but I generally only build ports under -STABLE, and /usr/local is
common to both the -CURRENT and -STABLE environments. (I build -CURRENT
with "COMPAT4X= yes" sp
OK; I managed to build yesterday's -CURRENT (I update my local FreeBSD
CVS repository mirror from 0347 - 0354 hrs. US/Pacific, daily) on my
SMP "build" machine, and the resulting system appeared fairly normal:
it booted to multi-user mode, and I could login via the serial console.
(I wasn't expecti
>Date: Mon, 17 Nov 2003 23:11:00 -0700 (MST)
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: Re: Help getting Realtek 8129-based NIC recognized?
>From: "M. Warner Losh" <[EMAIL PROTECTED]>
>Have you tried re?
It's in the kernel config, yes:
device rl # RealTek 8129/
OK; now that I finally(!) got a version of -CURRENT built and running
in multi-user mode, I'll try to help identify a problem I've observed
since September, when Bill Paul committed src/sys/pci/if_rl.c rev.
1.119. And to the extent I'm able, I'd like to help with a solution. :-}
The machine in q
>Date: Wed, 24 Sep 2003 00:58:12 -0500
>From: "Conrad J. Sabatier" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: dhclient/ipfw conflict on boot
>I just ran into this today after upgrading. It seems that dhclient is
>unable to initialize properly at boot time, due to the prior initializati
This is on my (SMP) "build" machine; sources updated between 0347 - 0355
hrs. US/Pacific (7 hrs. W of GMT).
I had done the usual buildworld, kernel, installworld, mergemaster,
rebooted, ran "healthd -d" for a little while (enough to see some
plausible variation), then entered
sudo boot0c
>Date: Sat, 13 Sep 2003 16:26:58 -0700 (PDT)
>From: Nate Lawson <[EMAIL PROTECTED]>
>To: David Wolfskill <[EMAIL PROTECTED]>
>cc: [EMAIL PROTECTED]
>Subject: Re: page fault while in kernel mode: AcpiNsMapHandleToNode + 0x20
>Your backtrace shows that your acpi_tz_
Got today's (CVSup between 03:47 - 03:55 US/Pacific, 7 hrs. W of GMT)
-CURRENT built on the laptop (i5000e) without incident -- after having
built from similarly-updated source on my build machine without
incident.
On reboot, saw (hand-transcribed, so there may be transcription errors):
...
Start
My SMP (2x886 MHz PIII) "build" machine has a RealTek 8129 NIC; I generally
track -CURRENT (on slice 4) on a daily basis. Until yesterday (08 Sep,
as I write this), it had worked adequately for my purposes.
After the build & reboot yesterday (and again today), the NIC does not
seem to have been p
Running -CURRENT with sources updated between 0347 - 0356 hrs. PDT
(US/Pacific -- 7 hrs. west of GMT at this time of year) yesterday;
in the process of building today's -CURRENT. (Had a similar-looking
problem yesterday, but I got involved in some other things, and didn't
make the time to report i
>To: [EMAIL PROTECTED]
>From: Jesse Guardiani <[EMAIL PROTECTED]>
>Date: Tue, 17 Jun 2003 16:42:22 -0400
>Subject: ACPI mailling list?
>Reply-To: [EMAIL PROTECTED]
[I will Cc: -current despite that request.]
>Is there an ACPI mailling list I can join
>to help debug/test ACPI?
See http://www.jp.f
>From: "Roderick van Domburg" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Date: Fri, 13 Jun 2003 11:18:45 +0200
>Subject: Support DHCP in rc.firewall by default?
>Right now, rc.firewall isn't set up to support DHCP configurations although
>it could easily be done so.
More or less, depending on
>Date: Tue, 27 May 2003 12:17:18 -0400
>From: "Will Saxon" <[EMAIL PROTECTED]>
>> I cvsupped the source this morning and I get:
>> [...]
>> ===> firewire/firewire
>> ...
>> In file included from /usr/src/sys/dev/firewire/fwohci.c:72:
>> @/dev/firewire/fwdma.h:38: redefinition of `bus_dmasync_op_t
>Date: Fri, 28 Mar 2003 18:34:31 -0800 (PST)
>From: David Wolfskill <[EMAIL PROTECTED]>
>>Date: Fri, 28 Mar 2003 08:46:39 -0800 (PST)
>>From: David Wolfskill <[EMAIL PROTECTED]>
>[Yes, I'm responding to my own post]
Again.
Well, I tried "
>Date: Fri, 28 Mar 2003 08:46:39 -0800 (PST)
>From: David Wolfskill <[EMAIL PROTECTED]>
[Yes, I'm responding to my own post]
>Got -CURRENT (re-)built; booted, logged in, poked around, seemed OK;
>issued:
> sudo boot0cfg -s 1 ad0 && sudo halt -p
>
Been tracking -CURENT (& -STABLE, though that is of marginal relevance
to this) on a daily basis for a couple of years now. Gone fairly well,
usually; sometimes there's turbulence. I suspect this is just a bump,
though -- and it's the first one I've encountered in at least a couple
of weeeks.
So
>Date: Tue, 25 Mar 2003 13:47:18 -0800
>From: "Kevin Oberman" <[EMAIL PROTECTED]>
>> On Tue, Mar 25, 2003 at 01:14:26PM -0800, Kevin Oberman wrote:
>> > I've been seeing this for a couple of weeks since I updated my laptop to
>> > CURRENT. I do a normal shutdown (-p or -r) and reboot. The shutdown
>Date: Mon, 24 Feb 2003 07:39:08 -0800
>From: walt <[EMAIL PROTECTED]>
>After this morning's cvsup I now get a 'syncing disks...giving up
>on three buffers' error message when shutting down the system and
>the filesystem doesn't get properly dismounted.
>For the last four days I could never shut
>Date: Mon, 24 Feb 2003 15:43:34 +0100
>From: Christoph Kukulies <[EMAIL PROTECTED]>
>Freshly supped and got:
>===> libexec/pt_chown
>cc -O -pipe -mcpu=pentiumpro -Wformat=2 -Wno-format-extra-args -Werror -c
>/usr/src/libexec/pt_chown/pt_chown.c
>cc1: warnings being treated as errors
>/usr/sr
>Date: Thu, 30 Jan 2003 21:58:15 -0800
>From: David Schultz <[EMAIL PROTECTED]>
>I asked the question in hopes that there would be some neat
>feature of cvsup that mocked up some CVS metadata for me, but
>since nobody has mentioned any such thing, I guess I'm out of
>luck. Mirroring the entire re
>Date: Wed, 4 Dec 2002 15:17:39 +0200
>From: Vallo Kallaste <[EMAIL PROTECTED]>
>I'm using both -current and -stable on the same machine, very
>common. Boot0cfg has -s [12345] flag to set the slice to boot on and
>it has been working so far. Beginning from Dec 1, I'm unable to set
>the slice:
>ro
>Date: Mon, 02 Dec 2002 13:01:43 -0600
>From: "Alan L. Cox" <[EMAIL PROTECTED]>
>> kernel: recursed on non-recursive lock (sleep mutex) vm page queue mutex @
>> ../../../i386/i386/pmap.c:928
>> $FreeBSD: src/sys/vm/vm_map.c,v 1.273 2002/12/01 18:57:56 alc Exp $
>> $FreeBSD: src/sys/i386/i386/pmap
>Date: Fri, 29 Nov 2002 12:20:38 -0800
>From: Kris Kennaway <[EMAIL PROTECTED]>
>It's often more efficient to use binary installations/upgrades than
>source, on slow machines. For example, I build world on a fast
>machine, mount via NFS and then installworld on my slower machines.
Quite so -- no
>From: David Syphers <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>Date: Fri, 29 Nov 2002 13:04:47 -0600
[Well, I'm Cc:ing -current anyway -- dhw]
>Out of curiosity, how much slower is a 5.x kernel compilation than a 4.x, on
>average? My 486, 66 MHz and 16 MB RAM, compiles a 4.x kernel in ab
>Date: Mon, 25 Nov 2002 19:04:28 +0800
>From: Ying-Chieh Liao <[EMAIL PROTECTED]>
>On Fri, Nov 22, 2002 at 00:06:59 +0800, Ying-Chieh Liao wrote:
>> I'm in DP2, and cvsup and then make world...
>>
>> if [ -L /usr/share/examples/sunrpc ]; then rm -f /usr/share/examples/sunrpc; fi
>> if [ -L /usr
>Date: Sun, 17 Nov 2002 19:06:40 +0100
>From: Stefan Farfeleder <[EMAIL PROTECTED]>
>> g1-9(5.0-C)[2] file /tmp/install.*|* | grep data
>^
>> #SC.SAVE~: Command not found.
>Are these just typoes in the mail or did you really type this? :-)
I cut & pasted it.
>Date: Tue, 12 Nov 2002 10:18:03 -0800 (PST)
>From: David Wolfskill <[EMAIL PROTECTED]>
[Yes, replying to my own message, if not myself dhw]
>Here's an excerpt of the typescript from the "make installworld":
>---%<- snip! --
On Sat, Nov 16, 2002 at 12:29:20PM +0100, Oliver Fromme wrote:
> I've submitted a small patch (bin/45333) for both -stable
> and -current, but I haven't been able to test it under
> -current (due to lack of a spare machine). Would someone
> please give it a try and let me know if it compiles and
>
OK; this is a bit strange, and I've come up with a circumvention (read
"really ugly bloody hack"), but my real concern is that this may be a
manifestation or symptom of something broken in some subtle way. The
note is rather long- winded; sorry about that, but I didn't see a better
way to do this.
For various reasons (most of which are likely historical), I tend
to mount /tmp as a swap-backed memory file system (and allocate
quite a bit of space to swap). Thus, in -STABLE, I use an mfs; in
-CURRENT, I use a little shell script (cribbed almost verbatim from
"man mdconfig").
Some months back
Noticed a bunch of:
> Expensive timeout(9) function: 0xc0170e40(0xc274c000) 0.001114387
from running (yesterday's) -CURRENT, so I thought I'd check against
(yesterday's kernel.debug (before I replaced it with today's).
Per "nm -lan kernel.debug", I see:
c0170420 T an_attach/usr/src/sys/dev/
>Date: Wed, 16 Oct 2002 12:49:22 -0400 (EDT)
>From: John Baldwin <[EMAIL PROTECTED]>
>> I *believe* that I had successfully inserted the drive after "atacontrol
>> detach 1" shortly after the atacontrol-related changes were MFCed.
>You probably want to do things in the following sequence:
>- at
This happened to me about a week ago under -STABLE, and again today
under -STABLE, so I tried it under -CURRENT today (in single-user
mode, to reduce variables), and was able to re-create it.
I *believe* that I had successfully inserted the drive after "atacontrol
detach 1" shortly after the atac
On Fri, Oct 11, 2002 at 02:42:34AM -0700, David O'Brien wrote:
> On Fri, Oct 11, 2002 at 01:04:23AM -0700, David O'Brien wrote:
> > I've ended up hosing world with the Binutils upgrade.
>
> I think world is OK now.
Looks as if something is (still?) broken:
>>> stage 4: building everything..
...
I'm including [EMAIL PROTECTED] because there may well be some
interaction with the recently-imported acpica-unix-20021002. Please
be judicious with respect to where replies are directed.
The panic occurred with -CURRENT CVSupped around 0347 hrs. US/Pacific (7
hrs. west of GMT, at this time of y
>Date: Mon, 07 Oct 2002 12:48:33 +0800
>From: suken woo <[EMAIL PROTECTED]>
>xdm broken on current when login .
It isn't for me, and I've been tracking -CURRENT daily for some time.
>i knew this is the pam module
>problem,but how could i fix it?
Well, absent any clues as to why you think it
>Date: Wed, 2 Oct 2002 14:16:03 -0700 (PDT)
>From: David Wolfskill <[EMAIL PROTECTED]>
>Saw Alfred's commit to un-break -CURRENT, did likewise locally,
>built today's -CURRENT, and an attempted multi-user boot panics:
>
Today's -CURRENT did
Saw Alfred's commit to un-break -CURRENT, did likewise locally,
built today's -CURRENT, and an attempted multi-user boot panics:
...
Starting nfsd.
Updating motd.
Starting ntpd.
Configuring syscons: blanktime.
Starting sshd.
Expensive timeout(9) function: 0xc02bea10(0xc406a000) 0.006791320
g_dev_
OK; after building today's -CURRENt on my build machine, I had time to
try building the kernel again, but with GEOM.
3 observations so far:
* Nearly everything still works. :-)
* A verbose boot (my default on the machine in question, since I
often need to check things or quote boot messages)
OK; it's probably rather like a sledgehammer, but I got the kernel
to compile and run with the following patch:
Index: sys/net/if_ethersubr.c
===
RCS file: /cvs/freebsd/src/sys/net/if_ethersubr.c,v
retrieving revision 1.120
diff -u -
>From: "Mario Goebbels" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Date: Wed, 4 Sep 2002 11:27:52 +0200
>H. Is mergemaster really necessary? I mean when upgrading from a fresh
>4.6 install?
Note that this is posted to the -current list, so the context *I* infer
from this is that you're re
[I tried to send this unicast to [EMAIL PROTECTED], but the attempt was
rejected with an "reason: 550 5.7.1 Access denied" as the only excuse
given for the behavior. dhw]
Adding a "cleandepend" stanza similar to the just-added "cleandir"
stanza seems to get beyond that.
Cheers,
david
--
David
>Date: Sun, 18 Aug 2002 20:44:52 -0400 (EDT)
>From: "Matthew N. Dodd" <[EMAIL PROTECTED]>
>On Sat, 17 Aug 2002, Mark Murray wrote:
>> If I do a "make -jN world" build on my dual MMX/200 box, I usually end
>> up in tears (well, a panic anyway). This is completely reproducible, and
>> the panic alw
Symptom:
===> sbin/ifconfig
cc -O -pipe -DUSE_IF_MEDIA -DINET6 -DUSE_VLANS -DUSE_IEEE80211 -DNS -Wall
-Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wnested-externs -I..-c
/usr/src/sbin/ifconfig/ifconfig.c
cc -O -pipe -DUSE_IF_MEDIA -DINET6 -DUSE_VLANS -DUSE_IEEE80211 -DNS -Wall
-Wmi
>Date: Fri, 16 Aug 2002 08:03:06 -0700 (PDT)
>From: David Wolfskill <[EMAIL PROTECTED]>
>The following patch (from /usr/src) gets past the problem, but I
>don't know that it's correct:
Still don't know about "correct," but it was incomplete.
>Index
>>> stage 4: building libraries
...
cc -O -pipe -DLIBC_MAJOR=5 -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../.
./include -D__DBINTERFACE_PRIVATE -DINET6 -I/common/S4/obj/usr/src/lib/libc
-DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DPORTMAP
-DDES_BUILTIN -DYP -DHESIOD
Warning: this is ~200 lines long. Sorry. I think the issue raised
is worth maybe 10% of the bandwidth, but
>Date: Tue, 13 Aug 2002 18:33:33 +0200
>From: Szilveszter Adam <[EMAIL PROTECTED]>
>Thanks for getting back with the results. This points to the fatc that
>the instructions in UPDATI
>Date: Sun, 11 Aug 2002 21:41:19 +0200
>From: Szilveszter Adam <[EMAIL PROTECTED]>
>First off, sorry for the lot of snippage but this mail was really
>long...
Yeah, it was; sorry. That's what I get for trying to be complete. :-)
I was able to re-do the steps, and evtually get to a point:
fre
I've been tracking each of -STABLE & -CURRENT for a while now, so
it's been almost a year since I tried the -STABLE -> -CURRENT upgrade
path. Still, I was a bit skeptical when someone on the #FreeBSD
channel at irc.sage-members.org indicated that the "make installworld"
was failing for him, typic
>Date: Wed, 31 Jul 2002 11:58:04 -0700 (PDT)
>From: David Wolfskill <[EMAIL PROTECTED]>
>[Re: panic during probes at boot time for today's -CURRENT]
Well, absent any better ideas, I rebooted the laptop, but into
single-user mode. It came up just fine, so I did the &
CVSup was at the usual time, 0347 hrs. US/Pacific. SMP build machine
built, installed, and rebooted just fine.
Trying to do likewise on my (UP) laptop got as far as the reboot, which
got a panic. I don't have a serial console on the laptop, so I'm hand-
transcribing this:
...
pcm0: pch[2].offs
>Date: Sun, 28 Jul 2002 21:51:57 +0900
>From: Seigo Tanimura <[EMAIL PROTECTED]>
>If you are having a trouble of a broken thread state (eg a thread with
>TDS_RUNQ on no run queue) or a mysterious page fault on a kernel
>memory (probably in mi_switch()), you may want to try my patch at:
>http://p
OK; I built today's -CURRENT (running yesterday's, as usual) on my SMP
build machine without incident earlier today.
And, as usual, I'm trying the same thing with my (UP) laptop.
But this time, the sequence has come to a halt; here's what I see so far:
>>> stage 4: populating /usr/obj/usr/src/i
This is by no means critical; possibly not even "important" -- but
after using my SMP "build machine" to build today's -STBALE (on
slice 1) and today's -CURRENT (on slice 4) -- where "today" varies
per the calendar -- it is my usual practice to issue
sudo boot0cfg -s 1 ad0 && sudo halt -p
>Date: Mon, 8 Jul 2002 16:44:20 -0700 (PDT)
>From: David Wolfskill <[EMAIL PROTECTED]>
>OK; implementing rev. 1.12 of src/sys/vm/vm_zeroidle.c allowed me to
>boot my (SMP) build machine & login:
>freebeast(5.0-C)[1] uname -a
>FreeBSD freebeast.catwhisker.org 5.0-CU
OK; implementing rev. 1.12 of src/sys/vm/vm_zeroidle.c allowed me to
boot my (SMP) build machine & login:
freebeast(5.0-C)[1] uname -a
FreeBSD freebeast.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #9: Mon Jul 8
16:28:30 PDT 2002
[EMAIL PROTECTED]:/common/S4/obj/usr/src/sys/FREEBEAST i3
CVSup started at 0347 hrs. Pacfic Daylight (7 hrs. west of GMT/UTC)
from cvsup14.freebsd.org. Build/install/mergemaster was uneventful.
Reboot after mergemaster proceeded as if nothing strange was about
to happen, then (cut/pasted from serial console):
...
SMP: enabled INTs: 2, 3, 4, 6, 7, 9, 10
601 - 700 of 918 matches
Mail list logo
