| From | Subject | Date |
|---|---|---|
| Pyun YongHyeon | Call for bge(4) testers
Hi,
I have been working on bge(4) for a while to support a new Broadcom
controller. Before doing that I committed many fundamental changes
to bge(4) in order to make it easy to add more controllers. Because
bge(4) supports many variants of controllers and have lots of
workaround for specific controller revisions it is possible for me
to break something on certain controllers. If you have bge(4)
controller please give it try and let me know how it ...
| Oct 11, 4:47 pm 2010 |
| Steve Kargl | recent bge(4) changes causing problems
It seems recent changes to the bge driver are causing
some problems with my hardware where the watchdog is
now timing out.
/var/log/messages contains
14:23:14 kernel: SMP: AP CPU #1 Launched!
14:23:14 kernel: Trying to mount root from ufs:/dev/ad6s1a
14:23:15 kernel: bge1: link state changed to UP
14:23:15 lpd[1190]: lpd startup: logging=0
14:23:15 ntpd[1224]: ntpd 4.2.4p5-a (1)
14:23:15 kernel: bge0: link state changed to UP
14:23:24 ntpd[1225]: time reset -0.677316 s
14:23:24 ...
| Oct 11, 3:53 pm 2010 |
| Pyun YongHyeon | Re: recent bge(4) changes causing problems
The icmp unreach has nothing to do with bge(4). Check whether a
server that listens on an UDP port is still alive on your box.
What worries me is bge(4) watchdog timeouts. It looks like your
controller is BCM5704. I also have bge(4) regression report from
marius on sparc64. He said r213945 seemed to cause the issue and
I'm working on the issue. Could you also try the attached patch?
| Oct 11, 4:16 pm 2010 |
| barbara | Re:HEADS UP: device name checking on device registration
Hi,
I faced that kind of panic today and now I'm able to boot again into CURRENT after applying the patch and rebuilding kernel.
The panic is caused by:
g_dev_taste(): make_dev_p() failed (gp->name=ext2fs//, error=22)
as I have a linux partition (I swear, it's for my mom!) on the same machine.
As I don't care about that partition (being ext4 I can't even mount it), is there any solution other then applying the patch after every ...
| Oct 11, 2:02 pm 2010 |
| Sam Fourman Jr. | nfs zfs lockup
I believe NFS is upsetting ZFS v15 on FreeBSD current (kernel sources
from today)
this happened while trying to sftp a 4gb file
here is a back trace
# procstat -k 2675 2436 1081 18 5 0
PID TID COMM TDNAME KSTACK
2675 100292 sftp-server - mi_switch sleepq_wait
_cv_wait txg_wait_open zfs_freebsd_write VOP_WRITE_APV vn_write
dofilewrite kern_writev write syscallenter syscall Xfast_syscall
2436 100337 cvsup - mi_switch ...
| Oct 11, 1:45 pm 2010 |
| Paul B Mahol | panic on kthread_exit under INVARIANTS
Hi,
If kernel threads were created via kproc_kthread_add()
when last kernel thread exits it will trigger panic.
It panics in queue.h .... probably introduced with recent commit.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 11, 10:34 am 2010 |
| Ed Schouten | truss calls setpgid()
Hi all,
I've been seeing this bug for a very long time, but I was too lazy to
figure out the root cause earlier. It is TTY related, but in this case
the TTY layer is not to blame. It does things correctly.
When you run a command in truss which calls ioctls on TTYs, it just
locks up. This is because truss runs jobs in a separate process group.
This also means you cannot send signals to it:
truss sleep 10000
Pressing ^C here won't work.
I've fixed it locally like this:
Index: ...
| Oct 11, 6:17 am 2010 |
| John Baldwin | Re: truss calls setpgid()
It was added in the switch from procfs to ptrace(), but it's not clear why the
child has a new process group. It doesn't look like truss ever tries to kill
the entire group for example.
--
John Baldwin
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 11, 8:13 am 2010 |
| Anonymous | Re: system hangs after logging into gdm
Do you have local patches to make it compile on /head? Could they be the
cause of the hang? 260.19.04 and 260.19.06 use taskqueue_run(9) that
was removed in /head@r210377.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 11, 11:49 am 2010 |
| Ivan Klymenko | Re: system hangs after logging into gdm
В Mon, 11 Oct 2010 08:37:05 -0700
Thank you!
I'll try to recompile the kernel with DDB shortly and after blocking
press ctrl+alt+esc, which would show the trace output...
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 11, 11:43 am 2010 |
| Garrett Cooper | Re: system hangs after logging into gdm
That seems a bit interesting.
The other thing you can do is start running a binary search on the
breakage because you have a range of good versions vs bad versions to
If you have ddb compiled into the kernel (and you should) try
CTRL-ALT-ESC after the lockup. You may also want to try KGDB instead,
which would require a serial connection (RS-232 or IEEE-1394).
HTH,
-Garrett
_______________________________________________
freebsd-current@freebsd.org mailing ...
| Oct 11, 8:37 am 2010 |
| Ivan Klymenko | Re: system hangs after logging into gdm
В Mon, 11 Oct 2010 11:10:17 -0400
Yes, of course.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 11, 11:36 am 2010 |
| Andriy Gapon | Re: system hangs after logging into gdm
If you can access the system remotely or quickly switch to console, then you
should be able to examine state of your system and get some facts.
--
Andriy Gapon
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 11, 2:04 am 2010 |
| Ivan Klymenko | Re: system hangs after logging into gdm
В Sun, 10 Oct 2010 15:37:55 -0700
NVIDIA Driver Version: 260.19.06
but Xorg successfully starts and GDM login screen appears
system hangs after a few seconds after entering the password ...
I noticed the following: gvfsd does not create a directory of the
form / var/tmp/gvfs-<username>-<hash> may hang system due to gvfsd?
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any ...
| Oct 11, 12:59 am 2010 |
| John Baldwin | Re: system hangs after logging into gdm
Did you recompile the nvidia.ko module after upgrading?
--
John Baldwin
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 11, 8:10 am 2010 |
| Ivan Klymenko | Re: system hangs after logging into gdm
В Mon, 11 Oct 2010 22:49:29 +0400
patches exist, but the cause is not in them - as Xorg starts, the
system hangs after a few seconds after entering the password box to
login gdm
without a password - it works
--- src/nvidia_os.c.orig 2010-09-15 01:26:27.000000000 +0300
+++ src/nvidia_os.c 2010-09-15 01:27:51.000000000 +0300
@@ -13,6 +13,67 @@
#include "nv.h"
#include "nv-freebsd.h"
+struct taskqueue {
+ STAILQ_HEAD(, task) tq_queue;
+ const char ...
| Oct 11, 12:18 pm 2010 |
| Simon L. B. Nielsen | Re: OpenSSL 1.0
If you need a newer version of OpenSSL in FreeBSD 7 you should try the OpenSSL ports. FreeBSD 7 will probably get the latest 0.9.8 before FreeBSD 7.4, but it won't get OpenSSL 1.0 (and neither will FreeBSD 8 for that matter).
--
Simon L. B. Nielsen
Hat: OpenSSL maintainer
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 11, 12:37 pm 2010 |
| Simon L. B. Nielsen | Re: OpenSSL 1.0
Hey,
Yes, the current plan is to have it in 9.0, but when it will be imported I can't say yet as it depends on having a good continuos chunk of time, which I haven't had too much of lately.
I had hoped to get around to looking at it during EuroBSDCon 2010, but I didn't.
--
Simon L. B. Nielsen
Hat: OpenSSL maintainer
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send ...
| Oct 11, 12:37 pm 2010 |
| Marek 'Buki' Kozlovský | Re: OpenSSL 1.0
Buki
--
PGP public key: http://dev.null.cz/buki.asc
/"\
\ / ASCII Ribbon Campaign
X Against HTML & Outlook Mail
/ \ http://www.thebackrow.net
| Oct 10, 6:05 pm 2010 |
| John Baldwin | Re: fcntl always fails to delete lock file, and PID is a ...
POSIX doesn't say that F_SETLK returns a valid l_pid, so I think FreeBSD's
current behavior is fine.
--
John Baldwin
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 11, 8:50 am 2010 |
| Pawel Jakub Dawidek | Re: letting glabel recognise a media change
Right, but I still wonder if we could execute provider orphan and
retaste on various events like media insertion or removal. If media is
removed we orphan provider and recreate it, which will trigger retaste,
and this is fine there will be nothing to read from or write to (we will
simply return errors as we do now, I think). This way we nicely
co-operate with GEOM, but also with other tools that don't require media
to be present (if there is no media devfs entry still exists and handles
ioctls, ...
| Oct 11, 1:11 pm 2010 |
| John Baldwin | Re: letting glabel recognise a media change
With CD drives you are also rather stuck in that the existing ABI for
controlling CD drives (e.g. ioctls in 3rd party software to eject a CD) are
done on the /dev/cdX device. Ideally enclosures for removable media would
be separate devices from the removable media itself, but a lot of existing
software for CD's would break if this changes now.
--
John Baldwin
_______________________________________________
freebsd-current@freebsd.org mailing ...
| Oct 11, 8:03 am 2010 |
| Søren Schmidt | Re: letting glabel recognise a media change
Think burning data on empty media.
-Søren
"Any sufficiently advanced technology is indistinguishable from magic."
--
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 11, 12:46 am 2010 |
| Sam Fourman Jr. | Re: -current under Xen
For what it is worth, I have the same shutdown issues on real hardware
using 9 CURRENT
eg
dell 6450 (old p3 xeon)
dell 2650
as well as a white box (below is a partial dmesg)
Copyright (c) 1992-2010 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.0-CURRENT #20: Mon Oct 11 07:57:28 CDT 2010
...
| Oct 11, 9:46 am 2010 |
| Andriy Gapon | Re: -current under Xen
Breaking into ddb at that point and examining stacks of all threads[*] would
greatly help to pinpoint the issue.
[*] or forcing a dump for postmortem examination with kgdb.
--
Andriy Gapon
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 11, 2:56 pm 2010 |
| jhell | Re: [RFC] ifconfig description support in rc.d
Is that the dynamic routes only or also the static routes ?
Either or if it would be any of the above it would be nice if these were
kept if it was only a restart of the interface, but offhand nothing
comes to mind that could prevent this from happening since the routes
are acting according to when the interface becomes inactive then the
route becomes meaningless.
Maybe if the action of 'restart' to etc/rc.d/netif could also call
etc/rc.d/routing with 'restart' if the configuration of the ...
| Oct 10, 10:30 pm 2010 |
| jhell | Re: [RFC] ifconfig description support in rc.d
That has been something that has bugged me for a while. Ill take a look
at some possibilities (with just the scripts in rc.d) that might be a
solution to this soon as I get a chance over this next week. It might
just be meaningful to merge the correct areas of the routing script into
the netif scripts restart and relevant sections. Ill look at this as
soon as I get a chance.
Unless if someone has another theory about whether those routes should
be deleted at all if the ifnet address still ...
| Oct 10, 10:45 pm 2010 |
| Garrett Cooper | Re: [RFC] ifconfig description support in rc.d
I just tested it on my test machine and it happens with static
routes; dynamic routes automatically get reset by dhclient, et all. It
used to be for both though in earlier versions of FreeBSD, IIRC.
Thanks!
-Garrett
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 10, 10:34 pm 2010 |
| Hiroki Sato | Re: [RFC] ifconfig description support in rc.d
Hi,
pluknet <pluknet@gmail.com> wrote
in <AANLkTintgji3vzrb8XuUQHWp+7YDvHtd7ynP0MmV0oZr@mail.gmail.com>:
pl> On 27 August 2010 00:09, Doug Barton <dougb@freebsd.org> wrote:
pl> > On 08/26/2010 12:53 PM, pluknet wrote:
pl> >>
pl> >> [cc'ing current@ as rc@ looks too quite]
pl> >>
pl> >> Hi.
pl> >>
pl> >> Since ifconfig has grown to label interfaces with
pl> >> ifconfig $ifname description "foobar", what about
pl> >> to give it more life and store i/face descriptions
pl> >> ...
| Oct 11, 3:29 am 2010 |
| previous day | today | next day |
|---|---|---|
| October 10, 2010 | October 11, 2010 | October 12, 2010 |
