t's UDP, and you insist on it working, you might want to
> make sure that the packet goes through the UDP fragmentation
> and NFS rsize/wsize limitation code.
>
I noticed in src/sys/dev/em/README that there are problems with jumbograms
and UDP so I use TCP.
--
Michal Mer
sover cable, I could not get the
> adapters to go to 1000, only 100. That might have been the cable,
> or not.
I can confirm it works equally well with crossover as with straight cable.
--
Michal Mertl
___
[EMAIL PROTECTED] mailing list
http://li
On Thu, 30 Oct 2003, Doug Ambrisko wrote:
> Michal Mertl writes:
> | On Thu, 30 Oct 2003, Sam Leffler wrote:
> |
> | > On Thursday 30 October 2003 04:46 am, Michal Mertl wrote:
> | > > I wanted to test gigabit network performance and found out that current
> | > >
On Thu, 30 Oct 2003, Sam Leffler wrote:
> On Thursday 30 October 2003 04:46 am, Michal Mertl wrote:
> > I wanted to test gigabit network performance and found out that current
> > (from 5.0 to up to date -current) doesn't fully work with jumbograms (MTU
> > set to 600
e I later see 'nfs server
10.0.0.2:/usr: not responding'. The interface is stuck for some time - can
be revived by changing mtu back to 1500 and down/up sequence.
--
Michal Mertl
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman
On Wed, 3 Sep 2003, Jens Rehsack wrote:
> Michal Mertl wrote:
> > I found 2 bugs and some potential problems in bktr(4) code.
> >
> > Bug 1:
> > Compilation with options BKTR_USE_FREEBSD_SMBUS failes. Error is
> > that code tries to use iicbus which isn't defi
should be able to see an idle kthread with 'top -S'
eating 100% of CPU 1. You can toggle HTT on/off at any time with 'sysctl
machdep.hlt_logical_cpus=0|1'.
I think that when hlt_logical_cpus == 1 system shouldn't account for
logical CPUs' idle time because
On Tue, 4 Mar 2003, Giorgos Keramidas wrote:
> On 2003-03-02 17:34, Michal Mertl <[EMAIL PROTECTED]> wrote:
> : Imagine you decided to go with modular kernel. You comment out 'device
> : random' in your kernel-config and place 'random_load="YES"'
> How about `unset XX_load' ?
It works only for acpi.
--
Michal Mertl
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
quot;' work. The other fix (probably more difficult to do)
would be to make all modules loading/linking fail when they're
statically compiled in.
--
Michal Mertl
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
tr(4) unit limited to 0-15"
+ fi
mknod bktr$unit c 92 `unit2minor $unit`
mknod tuner$unit c 92 `unit2minor $((16 + $unit))`
mknod vbi$unit c 92 `unit2minor $((32 + $unit))`
--
Michal Mertl
[EMAIL PROTECTED]
*** dev/bktr/bktr_reg.h.ori Sun Dec 8 10:40
ed=1 to /boot/loader.conf[.local]. I also have
hint.atkbd.0.flags="0x3" in there which helps with using my m700 with the
docking station BTW.
--
Michal Mertl
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
his general VFS problem, so details there
> would be very useful.
May be the attached one will allow someone to track something down.
PS: Sorry if you have problems with attachment, I myself find them
difficult to read (I'm receivind digest of this list - isn't there a
possibility to hav
On Sat, 30 Nov 2002, Michal Mertl wrote:
Including rwatson because of the thread on hackers@.
Sorry for follow-up to myself.
> Recently there was a discussion about jails on some freebsd list. Someone
> recommended vnconfig(8)ed file-backed disk for jail file systems. Terry
> wrote
Subject says it all.
I wanted to make vnode-backed md(4) and forgot to specify size, thas it
after 'touch mdfile;mdconfig -a -t vnode -f mdfile' mdconfig process can't
be killed. It's wchan ('ps axO wchan|grep mdconf') is mddest.
--
Michal Mertl
[EMAIL PROTECTED]
e
0 c0394720 c04ff0000 0 0 0000200 norm[SLPQ sched
c0394720][SLP] swapper
--
Michal Mertl
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ed but I suppose it's going to be
general problem - I've seen it mentioned (at least the pcm one) several
times.
Thanks.
--
Michal Mertl
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
mber allowed on each CPU list: 128
Maximum possible: 17280
1% of cluster map consumed
516 KBytes of wired memory reserved (37% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines
--
Michal Mertl
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RT_TAIL(&head->so_comp, so, so_list);
> so->so_state |= SS_COMP;
>
This patch fixes the panics for me. Thanks a lot. I believe it should be
commited.
BTW: I get about 850 fetches pers second on UP an 600 SMP (the same
machine and settings). Don't know if it's ex
/ip_input.c:916
#17 0xc0235234 in ipintr () at /usr/src/sys/netinet/ip_input.c:934
#18 0xc02295f3 in swi_net (dummy=0x0) at /usr/src/sys/net/netisr.c:97
#19 0xc01a8dc4 in ithread_loop (arg=0xc162b400)
at /usr/src/sys/kern/kern_intr.c:535
#20 0xc01a7c54 in fork_exit (callout=0xc01a8bf0 , arg=0x0,
On Fri, 6 Sep 2002, Alfred Perlstein wrote:
Alfred (thanks) found a bug in my code. Sorry for the fuss folks :-(.
> * Michal Mertl <[EMAIL PROTECTED]> [020906 06:10] wrote:
> > There seems to be bug in $SUBJ. When I run attached program on recent
> > -CURRENT, it always (
rogram for a
minute?
--
Michal Mertl
[EMAIL PROTECTED]
#include
#include
#include
#include
#include
#include
#include
#include
#include
#define MY_SHM_MAGIC 0x56d9f13b
typedef struct {
struct shmid_ds shm_ds;
struct semid_ds sem_ds;
ke sure it's owned by
root and has suid bit set (or always run it as root). This easily may be
security hole if there's bug in the program.
HTH
--
Michal Mertl
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
#x27;\002', slot = 0 '\000',
func = 0 '\000', pp_cap = 65041, pp_status = 224 'ŕ', pp_pmcsr = 226
'â', pp_data = 0 '\000'}, conf = {pc_sel = {
pc_bus = 2 '\002', pc_dev = 0 '\000', pc_func = 0 '\000'}, pc_hdr =
0 '\000', pc_subvendor = 4445,
pc_subdevice = 4481, pc_vendor = 4445, pc_device = 3, pc_class = 2
'\002', pc_subclass = 0 '\000',
pc_progif = 0 '\000', pc_revid = 3 '\003', pd_name = '\000' , pd_unit = 0}}
--
Michal Mertl
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
work
in progress to make it behave more like OLDCARD ?
--
Michal Mertl
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, 31 Dec 2001, Michal Mertl wrote:
Sorry to bloat the list but I forgot to mention that the panics occur when
I actually try to read from ntfs partition (after appliing pach from
previous email). cd works ok but ls panics the kernel.
--
Michal Mertl
[EMAIL PROTECTED]
To Unsubscribe
On Sun, 30 Dec 2001, Terry Lambert wrote:
> Michal Mertl wrote:
> >
> > I wrote about the issue once before but now I know more about the
> > problem.
> >
> > I have ntfs partition mounted ro on current. I can read from it without
> > problems. But I noti
On Sun, 30 Dec 2001, Sheldon Hearn wrote:
>
>
> On Sun, 30 Dec 2001 01:53:08 +0100, Michal Mertl wrote:
>
> > I have ntfs partition mounted ro on current. I can read from it without
> > problems. But I noticed I get corrupted data (the corrupted file has
> > right
retty sure the problem is thus in sendfile(2) and/or ntfs fs support.
--
Michal Mertl
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
but there must be something important in a
way ftpd reads files to serve.
I can give you all the info you would need.
--
Michal Mertl
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
30 matches
Mail list logo