On Mon, May 26, 2008 at 02:23:11PM +1200, Mark Kirkwood wrote:
> Peter Holm wrote:
> >On Sun, May 25, 2008 at 08:33:01PM +1200, Mark Kirkwood wrote:
> >
> >>I wrote:
> >>
> >>>John Baldwin wrote:
> >>>
> >>&
ck...
>
> Cheers
>
> Mark
I did 18 boots with and with out John's patch. With the patch I got 6
actual boots and 12 hangs in the loaders progress bar.
Without the patch I got 10 boots and 8 hangs.
But, my Tyan M/B is old and with known ACPI issues so I'm not sure if
this i
ters Tyan S2720, I'll double check I
> didn't fat finger applying the patch (mind you the Tyan has AMI BOIS -
> same as my Supermicro P3TDERs that *do* work ok with current 7-STABLE,
> whereas the P3TDDE has Award BIOS).
>
> Any
>
> > When I worked on my version of the realbtx, I sometimes experienced hangs
> > when
> > vm86 btx run before real-mode btx. I did not investigated it then, only
> > noted
> > the issue.
> >
>
> Try this patch. I'm not 100% certain this will fix it as I can't reproduce
> the issue, but I think it might help. Specifically, when the boot code makes
> a v86 call, the loader/boot2/whatever swaps in/out a new set of registers via
> the v86 structure including the eflags register. However, none of the boot
> programs actually initialized the v86 structure. Thus, the BIOS routines
> would start off running with whatever garbage was in v86.efl when each boot
> program started. This meant that we could end up invoking BIOS routines with
> interrupts disabled, and I think this might explain a hard hang (if a BIOS
> routine was waiting for an interrupt the interrupt would never fire). The
> patch fixes all the boot programs to initialize v86 to a better known state.
> At the least it sets v86.efl to a sane value (0x202) rather than random. (The
> random might have always been 0x0 BTW, not sure on that one.)
>
I can confirm that this patch fixes the loader problem seen with
my old Tyan S2720 MB.
- Peter
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On May 22, 2008, at 1:31 PM, Alexander Leidinger wrote:
Quoting Miroslav Lachman <[EMAIL PROTECTED]> (from Thu, 22 May 2008
13:19:55 +0200):
Peter Ankerstål wrote:
http://wiki.freebsd.org/JailResourceLimits
If the are somebody with skills and time to resurrect some
mentioned pr
If the are somebody with skills and time to resurrect some mentioned
projects, I am willing to help with testing.
I will also be happy to help in whatever way I can. I have no coding-
experience to talk about. But testing in various env
and so on. (and help with docs/wiki)
--
Peter
http://wiki.freebsd.org/JailResourceLimits
Is this anthing people are working on? Is it on its way to RELENG_7?
Is there a 7-version of the patch or anything? This would be a _VERY_
useful feature.
--
Peter Ankerstål
[EMAIL PROTECTED]
___
freebsd
shell is bash.
As Mark pointed out, this just means bash is broken.
Note that the FreeBSD build toolset is designed to work with sh - if
you've managed to convince make to use bash, you may have run into
an incompatibility that is causing your buildworld failures.
--
Peter Jeremy
Please
sr/obj and then run 'make clean'. My
guess is that you have some cruft in your /usr/src.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgpU4xKEcmIrh.pgp
Description: PGP signature
On Apr 29, 2008, at 2:08 PM, Jeremy Chadwick wrote:
I'd recommend staying away from Realtek NICs. Pick up an Intel Pro/
1000
GT or PT. Realtek has a well-known history of issues.
Just wanted to tell you guys that so far a em(4) seems to have fixed
the problem.
--
Peter Anke
lly somewhat worse than this: When compiling a new port with
dependencies, the internal foo_DEPENDS logic will detect the i386 .so
but the port's own configuration tools or build process will normally
die in interesting ways when they can't actually use that .so.
--
Peter Jeremy
Please e
On Apr 29, 2008, at 2:08 PM, Jeremy Chadwick wrote:
tcpdump reporting "bad cksum" can occur due to TX/RX checksum
offloading. Do you not see this message normally, but only when the
problem begins?
Have you tried turning off TX/RX offloading to see if the erroneous
behaviour goes away?
Hav
Hi,
Im using a built in re(4) card and it seems like its causes data-
corruption as soon as it gets some load (or after a few hours online)
The machine is running FreeBSD 7.0R:
FreeBSD ninja 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Wed Apr 16 22:49:15
CEST 2008 [EMAIL PROTECTED]:/usr/obj/us
No need - just download the image, burn it to a CD and boot the CD.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgpqzyXS7Xktp.pgp
Description: PGP signature
h would
>quickly cause a panic).
No. All ports are bus-powered.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgpqlYtd7DHID.pgp
Description: PGP signature
refuses to acknowledge EHCI devices - it just reports timeouts and
disables that USB port. [See my recent posting to -amd64].
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgpwvI0ALZw9N.pgp
Description: PGP signature
e but:
1) The Ultra 25 is UltraSPARC IIIi based. This CPU is not supported
by FreeBSD as Sun will not release necessary documentation.
2) Sun states they support both RHEL and SuSE ES on both the U20 and
U40 so I would expect they are stable and all hardware supported,
at least on those
iminish the strength of a lockdown, but it depends on what
you're trying to achieve. eg: If you're trying to prevent your users
from downloading a self-built irc client or bot and running it, then
yes, requiring signed binaries would be useful.
In any case, there are legitimate uses
tp.conf (optional)
- run "ntptime -f 0"
- run "/etc/rc.d/ntpdate start"
- run "/etc/rc.d/ntpd start"
This will force ntpd to re-calibrate and, hopefully, it will stabilise,
though this can take a day or so.
You can monitor the NTP PLL behaviour via the loopstats file.
ed could
> cause what you're seeing -- you'll have to trust us. Can you do that?
Was the file system on a machine that was upgraded from 4.x by any
chance? There were some header changes a while ago that could cause
pervasive accounting problems. A fsck fixes that one.
--
Peter W
! Try the rev. 1.24 of the devfs_rule.c. In fact, it is fixed by somewhat
! bigger patch that I inlined below. It is already in CURRENT and RELENG_7.
Thanks, this is cool: it seems to work on Rel. 6.3. :)
rgds,
PMc
___
freebsd-stable@freebsd.org mailing
On Wed, Mar 26, 2008 at 10:06:04PM +0100, Kris Kennaway wrote:
! Software always has bugs, and it is a mistake to think that the "stable"
! designation does not mean "has no bugs". It's unfortunate that you have
! hit a couple of them, but please continue to work through the process of
! docume
On Wed, Mar 26, 2008 at 05:00:12PM -0400, John Baldwin wrote:
! Try this patch for de(4).
Thanks fpr the reply. I'll try this patch at next reboot.
! You need to supply the panic details for the devfs
! one (I've used devfs rules w/o issue on lots of machines
! via /etc/devfs.conf).
I have fo
Dear all,
I have two computers.
Both of them were running Release 5.5, and they were doing all that
is needed, and I was perfectly happy with this.
Now, as we know, security support for Release 5.5 will terminate
during this spring, and as my computers are exposed to the Internet,
this means
And the party continues...
When starting my usual environment, there is already the next pagefault
kernel panic!
Tracking it down... it's the "type" keyword in devfs rules. According
to the manpage, support for this was _not_ withdrawn.
But actually, entering something like
devfs rule
you can't
upgrade any single port without re-building everything - for reasons
that have been spelled out elsewhere in this thread.
FWIW, the move to versioned symbols should (in theory) remove the
need to need to do a future complete recompile once you've rebuilt
all your ports again
On Tue, 18 Mar 2008, Kevin Oberman wrote:
Date: Mon, 17 Mar 2008 21:23:09 -0800 (AKDT)
From: peter stern <[EMAIL PROTECTED]>
This is an ugly way to have to deal with X. So this definitely means the
mga driver is broken?
I would appreciate a copy of your xorg.conf
Thanks for your sugge
your xorg.conf
Thanks for your suggestions.
peter
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Mon, 17 Mar 2008, Brad Pitney wrote:
On Mon, Mar 17, 2008 at 5:29 AM, peter stern <[EMAIL PROTECTED]> wrote:
I'd appreciate suggestions on how to get a working xorg from the mess 6.3
shipped with. I've been using FreeBSD since 2.2 and have never had much
trouble with it un
alling xorg from ports by running make
deinstall and make reinstall but with no change in behavior.
My hardware has no problems running Slackware 12 or Openbsd 4.2. Under
those OSs, X11 works fine and configures without problems.
What has happened to quality control in th
emails and gets i the queue, then sends with
the right address and it goes through. Later on, the message is
approved and we get a duplicate on the list.
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the s
onably certain my
cable-modem doesn't either so IPv6 connectivity would entail some
sort of tunnel.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgpy4B0Xu1cau.pgp
Description: PGP signature
... but it might have come from a
>dump -L.
dump -L will create a snapshot and, if aborted, may leave it behind.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgpZUX82XwK8o.pgp
Description: PGP signature
e with source routing in both
ipv4 and ipv6 when it is enabled. OS developers can make the same
mistakes parsing options in both. And so on. (Who remembers the ipv4
'ping of death' in the early 90's? you could send a packet with a
zero-length option to random hosts and instantly
On Wed, Mar 5, 2008 at 1:44 PM, Dimitry Andric <[EMAIL PROTECTED]> wrote:
> On 2008-03-05 22:42, Peter Wemm wrote:
> > Oh, one more thing. If you are IPv6-enabled, you get to bypass the 10
> > minute greylisting delay on mx1.freebsd.org. Your email goes through
>
On Wed, Mar 5, 2008 at 1:39 PM, Peter Wemm <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 5, 2008 at 6:32 AM, Mark Andrews <[EMAIL PROTECTED]> wrote:
> > There is a reasonable chance that this mail will leave here
> > over IPv6 for some of the
t the email. And that is because I had
127.0.0.1 hard coded in a config file.
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
"If Java had true garbage collectio
Have I somehow damaged my
>ufs2+softupdates filesystem by losing its inode #5 containing snapshot
>data?
No and no. You can have multiple snapshots in a filesystem.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821
e problem
still occurs. I have bumped into problems with umass on my son's SMP
laptop which don't show up on my UP laptop.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behavi
uarantees that it won't work.
>I indirectly answered this in my 2nd paragraph. Welcome to the UNIX
>equivalent of "DLL Hell" on Windows -- and why you should *always*
>recompile programs when the major version of a shared library (.so)
>changes. I cannot stress this e
I think you'll need a serial console to continue.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgpk8sZBj4PaO.pgp
Description: PGP signature
/boot/device.hints. What am I
>missing to allow serial input when the debugger starts?
This means that the serial port is expecting to talk to a remote GDB
session, not a serial console. You probably want:
- 'hint.sio.0.flags="0x10"' [no 'set'] in /boot/device.hint
ses?
If you built your own world, are you sure a NOINET6 hasn't snuck in
somewhere?
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgpiNSfeBdIvV.pgp
Description: PGP signature
improve performance but not reduce the memory required.
Note that this advice is relevant for UFS1 only. In UFS2, '-c'
specifies the cylinder group size in _BLOCKS_ not cylinders and
defaults to the maximum size for the given blocksize and IPG etc.
--
Peter Jeremy
Please excuse any dela
stuff, I finally fell for
the 'rm -rf *' in / classic newbie blunder. On the plus side, it was
my netboot environment for doing machine migration/installations. On
the minus side, I took out 12 other machines at once. Oops.
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAI
the port
build process had found a 6.x/i386 version of a dependency - which
causes the port build to fail at some later point.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed beh
hout
softupdates, even when I run the filesystem out of inodes. I have also
tried filling '/'ä and rebooting to no avail.
That said, I did run into a bug where, for some time after deleting the
files from a soft-updates partition, 'df' would report that the inodes
were freed
t;clean yet. The boxes in question both run 6.2-RELEASE, at various kernel
>release patchsets:
...
>With an i386 binary running on an amd64 host, when we write a small
>double, with value close to 0.1, to a C++ iostream, it is formatted
>incorrectly.
See kern/102424 and amd64/11.
get a crash, can you please display
the backtrace in ddb and then use addr2line or similar to convert the
addresses into line numbers. This will allow us to determine the correct
backtrace.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA th
mention the ATAPI DMA
changes so it's not clear whether this is an oversight or deliberate.
I do recall that there have been problems in the past with ATAPI
drives that would advertise DMA capabilities but would misbehave if
you used DMA (atapi_dma was disabled by default in 5.x for this
reason).
ther the kgdb output you included or
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/vm/vm_map.c?annotate=1.366.2.3
both of which show a call to vm_map_lock_read() at line 3074. I can't
find anywhere that vm_map_lookup() calls vm_map_unlock() - it always
calls vm_map_unlock_read().
--
Peter
infinity kB
>> datasize 33554432 kB
These are defaults and so are unlikely to be causing problems.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgpmNLKxxDg9t.pgp
Description: PGP signature
On Wed, Jan 30, 2008 at 08:06:40PM +0300, Ruslan Ermilov wrote:
> On Thu, Sep 21, 2006 at 05:16:36PM +0200, Peter Holm wrote:
> > On Thu, Sep 21, 2006 at 05:15:47PM +0400, Ruslan Ermilov wrote:
> > > On Thu, Sep 21, 2006 at 11:14:33AM +0100, Gavin Atkinson wrote:
> > >
e that CFLAGS is passed to the linker step.
>back burner. Which is to create a port of Apache that will run 2 versions
>of PHP consecutively.
Sounds interesting.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC28
amily release, upgrade to to the current 2.2
version as soon as possible."
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgp5TNEY54C5g.pgp
Description: PGP signature
166181300
>
>These numbers are quite worrysome-- they should be zero or nearly so in a
>healthy drive.
I see similarly wierd values from a basically new drive. I'm not sure
that there's a requirement that the raw values start from 0 and increment
on each detected event.
oats the reported VSZ but
the additional address space is never accessed so the overal impact
is negligible.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgpwZHS2VPGnr.pg
natory to me and has been the case for over
two years. (The relevant test is at the end of the "gecko-post-patch"
target in www/mozilla/Makefile.common).
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-complia
On Fri, Jan 18, 2008 at 02:18:40PM -0500, Ken Smith wrote:
> http://www.freebsd.org/releases/6.3R/announce.html
Thank you.
One question: What has happened to iA64? I notice it has been removed
from the release notes. Is it running late or dead?
--
Peter Jeremy
Please excuse any delays
be to put #ifdef amd64 around the error message
>in link_elf.c.
If there's a possibility that multiple ELF linkers could be required in
the future, a cleaner option might be to make link_elf_error() just cache
the error message and only report it after all possible linkers have
refused to l
; > WBR
> > --
> > Boris Samorodov (bsam)
> > Research Engineer, http://www.ipt.ru Telephone & Internet SP
> > FreeBSD committer, http://www.FreeBSD.org The Power To Serve
> > ___
> > freebsd-stable@freebsd.org m
vnode pager pages paged in
0 vnode pager pageouts
0 vnode pager pages paged out
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgphFm24TLtfp.pgp
Description: PGP signature
no_tsch.tar.gz
https://www.nan-elmoth.net/fbsd/makeinstallworld.tar.gz
Help on the above issues would be appreciated. I can provide more info
as needed or troubleshoot further if you provide me exactly what you
want me to do.
Thanks,
-Peter
___
freebs
heh I had the same prob a couple days back. Check the archives last
week, 10DEC07 "Re: Various Issues with 7.0-BETA4"
Step by step directions on how to fix
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-sta
h high resolution.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgpCXh5EuAxtY.pgp
Description: PGP signature
7;t run on FreeBSD/i386.
And, quite apart from the linker issues, 'cc -m32' is using the wrong
include files: All the machine-dependent types are defined in terms of
I32LP64 primitives whilst 'cc -m32' uses ILP32 primitives.
The current suggestion is to perform i386 compiles in
> Do you have zfs_load="YES" in /boot/loader.conf?
Scot: Shouldn't have to do this as zfs in compiled in.
> Did you create the zfs structures and file system while in single user
> mode with root mounted read-only? If so, this is a "known feature" and
If so not intentionally ... don't remember t
fo
as needed or troubleshoot further if you provide me exactly what you
want me to do.
Thanks,
-Peter
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Sat, Dec 01, 2007 at 09:49:55PM +0800, Ariff Abdullah wrote:
> On Sat, 1 Dec 2007 12:35:23 +0100
> Oliver Peter <[EMAIL PROTECTED]> wrote:
> > On Mon, Nov 19, 2007 at 10:22:33AM -0800, Kip Macy wrote:
> > > On Nov 19, 2007 9:53 AM, Anish Mistry <[EMAIL PROTECTED]&g
f6,0x170-0x177,0x376,0x1810-0x181f at device 31.2 on pci0
ata0: on atapci0
ata0: [ITHREAD]
ata1: on atapci0
ata1: [ITHREAD]
ichsmb0: port 0x18a0-0x18bf irq 11 at device 31.3 on pci0
ichsmb0: [GIANT-LOCKED]
ichsmb0: [ITHREAD]
smbus0: on ichsmb0
acpi_tz0: on acpi0
atkbdc0: port 0x60,0x64 irq 1 on acpi0
atkbd0: irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model Generic PS/2 mouse, device ID 0
battery0: on acpi0
acpi_acad0: on acpi0
pmtimer0 on isa0
ichwd0: on isa0
ichwd0: Intel ICH6M watchdog timer (ICH6 or equivalent)
orm0: at iomem
0xc-0xce7ff,0xd-0xd0fff,0xdc000-0xd,0xe-0xe pnpid ORM
on isa0
sc0: at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
ugen0: on uhub2
Timecounter "TSC" frequency 1596012590 Hz quality 800
Timecounters tick every 1.000 msec
ad0: 57231MB at ata0-master UDMA100
--
Oliver PETER, eMail: [EMAIL PROTECTED], ICQ# 113969174
"Worker bees can leave. Even drones can fly away.
The Queen is their slave."
pgpmEDQnxiWjW.pgp
Description: PGP signature
imilar to a single 'make cleandir', though it will also delete the
kernel build count (the #nn in "uname -a").
Note that the second 'make cleandir' is still necessary in case any cruft
has been created inside /usr/src.
--
Peter Jeremy
Please excuse any delay
on FreeBSD than on Linux. Robert Watson (if I recall
correctly) has done some work on building a framework to allow a
choice between slow-and-accurate and fast-and-less-precise timestamps.
I don't have the reference to hand but a check of the archives should
turn it up.
--
Peter Jeremy
Please excu
sing __INITIAL_NPXCW__ in
ia32_setregs(), though I'm not sure how difficult this is in reality.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgps0pNqgm4ZO.pgp
Description: PGP signature
lem is that the amd64 FPU is initialised to 64-bit
precision mode, whilst the i386 FPU is initialised to 53-bit precision
mode (__INITIAL_FPUCW__ in amd64/include/fpu.h vs __INITIAL_NPXCW__ in
i386/include/npx.h). It looks like the FPU is initialised during the
machine-dependent CPU initialisation and
e completely undefined. Unfortunately, I
can't explain why an i386 would be different to an amd64 in i386 mode.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
pgp9NYp3Hzs1H.pgp
Description: PGP signature
can also invoke the drive's internal self-tests.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an RFC2821-compliant MTA.
pgpwBTlncTJ8j.pgp
Description: PGP signature
2007/11/7, Peter Wullinger <[EMAIL PROTECTED]>:
>
> In epistula a David Taylor, die horaque Wed, Nov 07, 2007 at 06:18:57PM
> +:
> > Hello,
> >
> > I've tried compiling java/jdk15 and java/jdk16 bootstrapping with
> > all three binary jdks (diablo
a PR for that currently, so I don't know if this is known
(and both problems are the same).
Regards,
PEter
--
Alte Leute sind gefährlich, denn sie fürchten sich nicht vor der
Zukunft.
-- Sir Peter Ustinov
___
freebsd-stable@freebsd.o
e
re(4)/rl(4) and sym(4)/ncr(4) where some chips are supported by two
drivers - though generally only one driver fully supports the chip.
This sort of thing is confusing for end users.
--
Peter
pgppmaW0m5gG6.pgp
Description: PGP signature
On Mon, Oct 29, 2007 at 11:41:56PM +0100, Oliver Peter wrote:
> iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in
> /boot/loader.conf.
>
> And I have the following entry in /boot/loader.conf
>
> # intel/wireless
> set legal.intel_iwi.license_
tions.
--
Oliver PETER, eMail: [EMAIL PROTECTED], ICQ# 113969174
"Worker bees can leave. Even drones can fly away.
The Queen is their slave."
pgpZKpBhfctUj.pgp
Description: PGP signature
in a couple of
spots in /sys/i386/isa/clock.c to only have the 24hr bit set. I'm not
sure what modern Windows expects but the DST rules embedded in the
MC146818 are now accurate for only a fairly small part of the world.
--
Peter
pgpsuNB1LD4Xr.pgp
Description: PGP signature
s meaning....
--
Peter
pgpksQObtZJ0o.pgp
Description: PGP signature
eligible for an MFC to 6.x? It makes reading
kdump output much easier. The only downside is that it might break
scripts that people might use to postprocess kdump output.
--
Peter Jeremy
pgpwSLgLnvhiG.pgp
Description: PGP signature
ere can be a problem in the future because I switched from
8.0-SUPRISE to 7.0-STABLE...
--
Oliver PETER, eMail: [EMAIL PROTECTED], ICQ# 113969174
"Worker bees can leave. Even drones can fly away.
The Queen is their slave."
pgpaHbQJNK7Cm.pgp
Description: PGP signature
es. In this case though, it was truly
silent corruption. No indications of errors, or strange performance
characteristics.
--
/ Peter Schuller
PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>'
Key retrieval: Send an E-Mail to [EMAIL PROTECTED]
E-Mail: [EMAI
same PCI slot - no corruption, and no DMA
timeouts and whatnot that I was expecting from a SiI card.
This was on amd64, RELENG_7. Same SATA cables used on all
drives. Drives on TX4 were also in a Supermicro hotswap enclosure,
which may or may not be related (but again, no problem with SiI).
--
/ Peter Sc
ive
will help some people.
Thanks a lot!
--
/ Peter Schuller
PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>'
Key retrieval: Send an E-Mail to [EMAIL PROTECTED]
E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org
pgpi0g0zTbdZn.pgp
Description: PGP signature
ather than RELENG_7;
unfortunately I am not sure which X server I started when I started up
my desktop last.
--
/ Peter Schuller
PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>'
Key retrieval: Send an E-Mail to [EMAIL PROTECTED]
E-Mail: [EMAIL PROTECTED]
ged shmid_ds size (though this would also
affect semctl() and msgctl().
--
Peter Jeremy
pgp1C21pynGL7.pgp
Description: PGP signature
igned' and translates to 'int' rather
than 'long' on i386 so this printf will report a warning. I suggest
printf(" %12lu", (unsigned long)kshmptr->u.shm_segsz); or similar.
--
Peter Jeremy
pgpBidj3poDj6.pgp
Description: PGP signature
, mmap(2) or
malloc(3). The downside is that a process may be killed without
notice when it writes to some previously allocated but unused part
of its address space. See the archives for the full bikeshed.
--
Peter Jeremy
pgpC1oPyT0BbR.pgp
Description: PGP signature
ee for flags
This will let you indentify shared vs private space as well as whether
it's file or swap backed.
--
Peter Jeremy
pgpTgKJQKBT1Q.pgp
Description: PGP signature
storm" or
how it might be related to acpi. And 7.0 isn't stable yet.
The default HZ is 1000 so unless you explicitly change it in your
kernel config, you should have 1000 clock interrupts/sec.
--
Peter Jeremy
pgpinGFhpu8Dx.pgp
Description: PGP signature
nvestigate and correct the underlying problem.
--
Peter Jeremy
pgp6R2uYZaWqf.pgp
Description: PGP signature
= 0xff0039bd7228
},
sysctl_tree = 0xffb30600
}
(kgdb)
Is this behaviour expected?
--
Peter Jeremy
pgpIYSxHJT549.pgp
Description: PGP signature
e the core available for further debugging
if necessary.
Thanks,
Peter
# sudo kgdb kernel.debug /work/vmcore.3
kgdb: kvm_nlist(_stopped_cpus):
kgdb: kvm_nlist(_stoppcbs):
[GDB will not be able to debug user-mode threads:
/usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"
ac70
}
(kgdb) p callwheel[0x5ebf]
$7 = {
tqh_first = 0x400,
tqh_last = 0x98d6ac90
}
(kgdb) p callwheel[0x5ec0]
$8 = {
tqh_first = 0x400,
tqh_last = 0x98d6aca0
}
(kgdb) p callwheel[0x5ec1]
$9 = {
tqh_first = 0xff00287cdb20,
tqh_last = 0xff00287cdb20
}
(kgdb)
-
drives?
--
/ Peter Schuller
PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>'
Key retrieval: Send an E-Mail to [EMAIL PROTECTED]
E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org
___
freebsd-stable@freebsd.org m
t root operators
make changes on a glacial scale. There is a reason for that. ;)
Best Wishes - Peter
--
[EMAIL PROTECTED] | ISC | OpenPGP 0xE8048D08 | "The bits must flow"
signature.asc
Description: OpenPGP digital signature
601 - 700 of 1261 matches
Mail list logo
