On Monday, 19 August 2024 at 21:14:58 -0500, Larry Rosenman wrote:
> gpg: Good signature from "Larry Rosenman " [expired]
> ...
> gpg: Note: This key has expired!
>
> shows up , doesn't ping -- ifconfig up brings it back for ~4 packets
>
> ifconfig_re0="DHCP"
> ifconfig_re0_ipv6="inet6 accept_rtadv
On Wednesday, 27 September 2023 at 22:30:43 -0500, Kyle Evans wrote:
> On 9/27/23 21:40, Jamie Landeg-Jones wrote:
>> When using color=always and a regex of '.' (for example), output lines
>> are duplicated.
>>
>> $ grep --version
>> grep (BSD grep, GNU compatible) 2.6.0-FreeBSD
>>
>> E.G.:
>>
>> $
On Monday, 14 August 2023 at 17:34:12 -0700, Kevin Bowling wrote:
> On Mon, Aug 14, 2023 at 4:45 PM Greg 'groggy' Lehey wrote:
>> Thanks. Let me know when you have something and I'll test it.
>
> I went ahead and reverted: 797e480cba8834e584062092c098e60956d281
[moving to current as requested by bz@]
On Monday, 14 August 2023 at 10:09:22 -0700, Kevin Bowling wrote:
>
> I'm able to replicate this on my I217 using iperf3. It happens
> quickly with flow control enabled (default) and takes about 15 minutes
> of line rate with flow control disabled. I am lo
I've spent the last couple of days chasing random hangs on my -CURRENT
box. It seems to be related to the Ethernet driver (em). I've been
trying without much success to chase it down, and I'd be grateful.
The box is headless, and all communication is via the net, which
doesn't make it any easier.
On Saturday, 20 May 2023 at 17:15:25 -0400, Mike Jakubik wrote:
> On Sat, May 20, 2023 at 4:49 PM Yuri wrote:
>> Mike Jakubik wrote:
>>>
>>> Thanks for the info. At least I know it's not specific to my parts. Is
>>> there any knob one can turn in the BIOS to enable/disable this feature?
>>> iirc U
On Thursday, 23 June 2022 at 6:03:20 +0200, Polytropon wrote:
> On Thu, 23 Jun 2022 13:01:18 +1000, Greg 'groggy' Lehey wrote:
>> [...] I personally find that prepending
>> ">" to the original message works best. Leaving white space after
>> the
On Wednesday, 22 June 2022 at 15:41:39 -0400, grarpamp wrote:
> Around 6/2x/22, Many rammed their horribly formed
> msgs upon others to parse:
> ...
> FreeBSD needs to add an entire section on the
> email post formatting netiquette to the Handbook,
> and link it on the List Subscription pages, and
On Friday, 1 April 2022 at 9:38:07 -0700, Cy Schubert wrote:
> In message <20220401064816.gs60...@eureka.lemis.com>, Greg 'groggy' Lehey
> write
> s:
>>
>> --TSQPSNmi3T91JED+
>> Content-Type: text/plain; charset=us-ascii
>> Content-Disposition:
On Friday, 1 April 2022 at 5:58:39 +, Alexey Dokuchaev wrote:
> On Fri, Apr 01, 2022 at 02:20:31PM +0900, Yasuhiro Kimura wrote:
>> Hi Glen,
>>
>> From: Glen Barber
>> Subject: Considering stepping down from all of my FreeBSD responsibilities
>> Date: Fri, 1 Apr 2022 00:15:02 +
>>
>>> De
On Thursday, 25 February 2021 at 21:22:43 -0500, Ed Maste wrote:
> On Thu, 25 Feb 2021 at 19:23, John Kennedy wrote:
>>
>> Not sure if Ed Maste just wants to make sure that all the executables
>> are rebuilt as PIE (vs hit-and-miss) or there is a sneaker corner-case that
>> he knows about.
>
> T
On Thursday, 25 February 2021 at 15:58:07 -0500, Ed Maste wrote:
> As of 9a227a2fd642 (main-n245052) base system binaries are now built
> as position-independent executable (PIE) by default, for 64-bit
> architectures. PIE executables are used in conjunction with address
> randomization as a mitiga
On Tuesday, 1 September 2020 at 13:14:10 -0400, Ed Maste wrote:
> We've been updating the svn-git converter and pushing out a new
> converted repo every two weeks, and are now approaching the time where
> we'd like to commit to the tree generated by the exporter,
> ...
Somehow I've missed this de
On Wednesday, 11 March 2020 at 0:20:03 +, Poul-Henning Kamp wrote:
[originally sent to current@]
> I just updated my laptop from source, and somewhere along the way
> the key-codes Xorg sees changed.
Indeed. This doesn't just affect -CURRENT: it happened to me on
-STABLE last week, so I'm c
On Saturday, 7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote:
[much irrelevant text deleted]
People, please trim your replies. Only relevant text should remain
> On Sat, 07 Mar 2020 11:30:58 -0400 Waitman Gobble wrote:
>>
>> I installed 12.1 on a new laptop yesterday, I have not experien
On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote:
> On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote:
>>
>> Any workarounds in the meantime? This must affect a lot of people,
>> including those who use 12-:
>>
>>
On Monday, 2 March 2020 at 17:58:01 +, marco wrote:
> On Sun, Mar 01, 2020 at 04:50:59PM -0500, you (Brennan Vincent) sent the
> following to [freebsd-current] :
>> Apparently something has its ABI erroneously listed as FreeBSD:13.0:amd64
>> instead of FreeBSD:13:amd64.
>>
>> ```
>> $ sudo pk
On Thursday, 13 December 2018 at 13:07:54 +, Bob Bishop wrote:
> Hi,
>
> Please could somebody take a look at
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
>
> It???s been open for over a year with a patch that solves the problem.
>
> Failing to install out of the box on commodity
On Monday, 23 April 2018 at 9:55:40 +0200, Mariusz Zaborski wrote:
> On Mon, Apr 23, 2018 at 05:51:01PM +1000, Greg 'groggy' Lehey wrote:
>> On Monday, 23 April 2018 at 9:00:33 +0200, O. Hartmann wrote:
>>> On Sun, 22 Apr 2018 14:38:55 +0200 Mariusz Zaborski
>
On Monday, 23 April 2018 at 9:00:33 +0200, O. Hartmann wrote:
> On Sun, 22 Apr 2018 14:38:55 +0200
> Mariusz Zaborski wrote:
>
>> Hi,
>>
>> Normally I build my CURRENT by myself from Xorg - r332861.
>> But I also tried latest SNAPSHOT.
>
> All my boxes running with nVidia hardware running most re
On Sunday, 22 April 2018 at 12:42:37 +0200, Mariusz Zaborski wrote:
> Hello,
>
> I upgraded my FreeBSD to CURRENT and nvidia-drvier-390.48. But it's
> stop working.
> I tried also nvidia-driver-390.25 without luck as well.
Yes, I've had this trouble as well with -STABLE. It happened some
time in
On Saturday, 19 August 2017 at 16:00:28 +0100, tech-lists wrote:
> Hello list,
>
> (freebsd-current is r317212 on this machine)
>
> I have a machine with 128GB RAM. When 12-current was installed, for some
> reason the swap partition was set to 4GB. I see sometimes via top and
> also via daily statu
On Friday, 5 August 2016 at 18:56:33 +0300, Andrey A. Chernov wrote:
> On 05.08.2016 18:44, Mark Martinec wrote:
>> On 2016-08-05 17:23, Andrey Chernov wrote:
>>> On 05.08.2016 17:47, Mark Martinec wrote:
[Bug 211598]
date(1) default format in en_EN locale breaks compatibility with 10.
[line lengths recovered]
On Sunday, 1 May 2016 at 20:16:38 -0700, Jordan Hubbard wrote:
>
>> On May 1, 2016, at 5:49 PM, Warren Block wrote:
>>
>> The first quarter of 2016 showed that FreeBSD retains a strong sense of
>> ipseity. Improvements were pervasive, lending credence to the concept
On Tuesday, 10 February 2015 at 23:38:54 +0100, Baptiste Daroussin wrote:
> Hi,
>
> I would like to start using bmake only syntax on our infrastructure for that I
> want to make sure noone is using the old make, so I plan to remove the old
> make
> from base, I plan to do it by Feb 16th.
How does
On Tuesday, 13 November 2012 at 9:11:21 +0200, Alexander Yerenkow wrote:
> Hello there!
> I sometimes see in this list such mails:
> "I got problem with rXX"
> "It's known, it's fixed in rYY".
>
> Sometimes it's my problem, sometimes it's problem of other peoples.
>
> How about make simple
On Friday, 9 November 2012 at 13:52:24 +0100, Dimitry Andric wrote:
> On 2012-11-09 08:26, Greg 'groggy' Lehey wrote:> On Thursday, 8 November
> 2012 at 22:58:37 -0800, Manfred Antar wrote:
>>> Sometime in the last week calendar stopped working.
>>> not s
On Thursday, 8 November 2012 at 22:58:37 -0800, Manfred Antar wrote:
> Sometime in the last week calendar stopped working.
> not sure the cause
> here is some of the output:
> /usr/share/calendar/calendar.music:231:17: warning: missing terminating '
> character [-Winvalid-pp-token]
> 12/16 Don
[Text formatting recovered]
On Thursday, 8 November 2012 at 9:23:11 -0600, Larry Rosenman wrote:
> On 2012-11-08 09:20, Edward Tomasz Napiera??a wrote:
>> Wiadomo napisana przez Andriy Gapon w dniu 8 lis 2012, o godz. 15:17:
>>> Just curious why lsof can't use interfaces that e.g.
>>> fstat/
On Wednesday, 7 November 2012 at 16:35:22 -0600, Larry Rosenman wrote:
> On 2012-11-07 15:39, Greg 'groggy' Lehey wrote:
>> On Wednesday, 7 November 2012 at 10:32:23 -0500, Benjamin Kaduk
>> wrote:
>>>
>>> Once again, attempting to use kernel internals
On Sunday, 29 July 2012 at 0:53:55 -0400, David J. Weller-Fahy wrote:
> So, I recently updated and encountered a panic on boot which is
> reproducible, and wanted to see if anyone's encountered this before I
> file a PR. I found a problem in (I think) recent changes to the e1000
> driver. I'm ru
On Monday, 1 December 2003 at 17:12:23 -0700, Scott Long wrote:
> On Tue, 2 Dec 2003, Greg 'groggy' Lehey wrote:
>> On Monday, 1 December 2003 at 10:01:23 -0500, Robert Watson wrote:
>>> This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
>
On Monday, 1 December 2003 at 10:01:23 -0500, Robert Watson wrote:
> This is an automated bi-weekly mailing of the FreeBSD 5.2 open issues list.
>
> Show stopper defects for 5.2-RELEASE
>
> ++
> | Issue | Status |Re
On Thursday, 27 November 2003 at 0:13:09 -0600, Cosmin Stroe wrote:
> On Thu, 27 Nov 2003, Greg 'groggy' Lehey wrote:
>
>> On Wednesday, 26 November 2003 at 12:04:52 -0600, Cosmin Stroe wrote:
>>>
>>> I am using vinum atm, and I am having serious prob
On Wednesday, 26 November 2003 at 12:04:52 -0600, Cosmin Stroe wrote:
>
> I am using vinum atm, and I am having serious problems with it. After
> about 16 hrs of writing data to a vinum volume via NFS at a constant data
> stream of 200k/sec and reading at 400k/sec at the same time, the whole
> mac
On Tuesday, 25 November 2003 at 10:48:44 -0600, Eric Anderson wrote:
>
>> Could a vinum guru please contact me via email?
>>
>> I've lost 2 vinum volumes as a result of the latest fiasco and naturally
>> am eager to figure out what's going on and recover the data.
>
> This isn't necessarily directe
On Sunday, 23 November 2003 at 22:46:30 +0100, Matthias Schuendehuette wrote:
> Hello,
>
> I just built a new world+kernel after the commit of grogs corrections
> but I still get:
>
> [EMAIL PROTECTED] - ~
> 503 # vinum start
> ** no drives found: No such file or directory
Yes. The fix wasn't eno
On Friday, 21 November 2003 at 15:42:12 -0800, Marcus Reid wrote:
> Hello,
>
> I just upgraded a -CURRENT box this afternoon to discover that vinum
> is broken. If I hadn't done dumps of my working world beforehand I
> would be in pretty sad shape. Should UPDATING make note of this
> breakage?
No.
Following on from the panic on a week-old -CURRENT, I note that
camcontrol rescan doesn't do the right thing either. On yesterday's
kernel, I did:
- remove a disk from a string
- run camcontrol rescan. No change "Re-scan of bus 1 was successful",
but the device entry was still there.
- Ran d
I'm running a -CURRENT kernel built about a week ago, and on
'camcontrol devlist' I get the following repeatable panic:
#10 0xc063b1d5 in panic (fmt=0xc084458e "vmapbuf")
at /src/FreeBSD/5-CURRENT-WANTADILLA/src/sys/kern/kern_shutdown.c:534
#11 0xc0684d4e in vmapbuf (bp=0xc4659400) at
/src/Fr
On Wednesday, 8 October 2003 at 2:08:55 +1000, Bruce Evans wrote:
> On Tue, 30 Sep 2003, Sam Leffler wrote:
>
>> It reliably locks up for me when you break into a running system; set a
>> breakpoint; and then continue. Machine is UP+HTT. Haven't tried other
>> machines.
>
> This seems to be bec
On Tuesday, 14 October 2003 at 18:46:44 +0200, Balazs Nagy wrote:
> Hi,
>
> I had a -CURRENT setting with an Abit BE7-S and two SATA disks with
> vinum configuration. It worked very well until a power failure, and
> the mainboard died. Yesterday I got a replacement mainboard, the only
> type met
On Tuesday, 30 September 2003 at 16:13:09 -0400, Andrew Gallatin wrote:
>
> Sam Leffler writes:
>> It reliably locks up for me when you break into a running system; set a
>> breakpoint; and then continue. Machine is UP+HTT. Haven't tried other
>> machines.
>
> Perhaps related, perhaps a red-herri
On Tuesday, 30 September 2003 at 16:23:35 +1000, Bruce Evans wrote:
> On Mon, 29 Sep 2003, Greg 'groggy' Lehey wrote:
>
>> After building a new kernel, remote serial gdb no longer works. When
>> I issue a 'continue' command, I lose control of the system, bu
After building a new kernel, remote serial gdb no longer works. When
I issue a 'continue' command, I lose control of the system, but it
doesn't continue running. Has anybody else seen this?
Greg
--
See complete headers for address and phone numbers.
NOTE: Due to the currently active Microsoft-ba
On Sunday, 28 September 2003 at 19:46:20 -0400, Robert Watson wrote:
>
> On Mon, 29 Sep 2003, Greg 'groggy' Lehey wrote:
>
>> On Sunday, 28 September 2003 at 23:22:07 +0200, Poul-Henning Kamp wrote:
>>> Basically:
>>>
>>> 3. If you do a &quo
On Sunday, 28 September 2003 at 23:22:07 +0200, Poul-Henning Kamp wrote:
> Basically:
>
> 3. If you do a "normal" device driver, cache the result
> from when you call make_dev().
> ...
>
> ./dev/vinum
> Failure to cache result of make_dev() ?
Where should this be
On Friday, 26 September 2003 at 22:08:25 -0400, David Gilbert wrote:
>> "Greg" == Greg Lehey writes:
>
> Greg> Don't hold your breath. This will probably happen in the course
> Greg> of migrating Vinum functionality to GEOM.
>
> So... is vinum-as-we-know-it going to disappear into the GEOM
>
On Friday, 26 September 2003 at 19:28:45 -0400, David Gilbert wrote:
>> "Robert" == Robert Watson <[EMAIL PROTECTED]> writes:
>
> Robert> On Fri, 26 Sep 2003, David Gilbert wrote:
>
>>> Recent changes to -CURRENT prohibit vinum swap:
>>>
>>> [1:6:[EMAIL PROTECTED]:~> swapon /dev/vinum/swapmu sw
On Friday, 26 September 2003 at 18:38:48 -0400, Robert Watson wrote:
>
> On Fri, 26 Sep 2003, David Gilbert wrote:
>
>> Recent changes to -CURRENT prohibit vinum swap:
>>
>> [1:6:[EMAIL PROTECTED]:~> swapon /dev/vinum/swapmu swapon: /dev/vinum/swapmu:
>> Operation not supported by device
>
> In ord
On Thursday, 25 September 2003 at 1:12:21 -0400, Lanny Baron wrote:
> On Wed, 2003-09-24 at 22:42, Greg 'groggy' Lehey wrote:
>> On Thursday, 25 September 2003 at 3:04:52 +0200, Willem Jan Withagen wrote:
>>> Hi,
>>>
>>> I'm trying to upgrade
On Thursday, 25 September 2003 at 3:04:52 +0200, Willem Jan Withagen wrote:
> Hi,
>
> I'm trying to upgrade my firewall/router to 5.x but I'm getting caught by
> the fact that I cannot find a 'sl0' interface.
Are you really still using SLIP? What's wrong with PPP?
> I've tried the both with if_
On Saturday, 23 August 2003 at 5:05:11 -0700, Rostislav Krasny wrote:
> When FreeBSD 5.0-RELEASE had been released I tried to install it from
> floppies. I got system panic and then reported this problem into
> [EMAIL PROTECTED] mailing list. You can find this report in
> http://www.atm.tut.fi/lis
Some changes in device driver locking recently broke Vinum for a short
period of time. The problem is now fixed. If you have any problems
with a recent version of Vinum, please let me know.
Greg
--
See complete headers for address and phone numbers
pgp0.pgp
Description: PGP signature
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
>>>
[Format recovered--see http://www.lemis.com/email/email-format.html]
Long/short syndrome.
On Tuesday, 12 August 2003 at 20:49:05 -0400, James Quick wrote:
>
> I am seeking feedback on the status of vinum, and whether the
> following plan makes sense as an upgrade plan for a host with a
> light lo
On Thursday, 7 August 2003 at 18:23:10 -0600, Aaron Wohl wrote:
> I just cvsuped -current this afternoon to get about 1 weeks updates.
> After that the kernel panics booting starting vinum. I removed the one
> vinum volume (reformated as UFS2) I had for testing. And it still panics.
> I changed
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 c
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:
>>>>
>>&
On Friday, 8 August 2003 at 10:27:31 +0200, Erwin Lansing wrote:
> On Fri, Aug 08, 2003 at 10:22:06AM +0200, Poul-Henning Kamp wrote:
>> In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes:
>>> I just cvsuped -current this afternoon to get about 1 weeks updates.
>>> After that the kernel panics bo
On Monday, 4 August 2003 at 11:37:44 +0200, Brad Knowles wrote:
> At 11:51 PM -0600 2003/08/03, M. Warner Losh wrote:
>
>> In message: <[EMAIL PROTECTED]>
>> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
>>
>>>
On Sunday, 3 August 2003 at 23:51:55 -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
>> On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote:
>>> Hey,
&
On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote:
> Hey,
>
> I have a few Orinoco cards, and they 'work' in both ad-hoc and
> infrastructure mode. However with dhclient it gets tricky, because it
> will only work the first time dhclient assigns an address to the card.
> Whenever it
On Sunday, 3 August 2003 at 11:17:49 +0200, Eivind Olsen wrote:
> --On 3. august 2003 09:37 +0930 Greg 'groggy' Lehey <[EMAIL PROTECTED]>
> wrote:
>> Read the links I just sent you. You haven't loaded the Vinum symbols.
>
> I'm not sure exactly wh
On Sunday, 3 August 2003 at 0:31:45 -0400, John Baldwin wrote:
>
> On 03-Aug-2003 Greg 'groggy' Lehey wrote:
>> On Saturday, 2 August 2003 at 16:47:13 +0200, Eivind Olsen wrote:
>>> [EMAIL PROTECTED]:~/tmp/debug > gdb -k kernel.debug
>>> (kgdb) lis
On Saturday, 2 August 2003 at 18:36:24 -0700, Terry Lambert wrote:
> Greg 'groggy' Lehey wrote:
>>> The information I gave him gets him to lines of source code, instead
>>> of just function names with strange hexadecimal numbers that resolve
>>> to instruc
On Saturday, 2 August 2003 at 18:06:36 -0700, Terry Lambert wrote:
> Greg 'groggy' Lehey wrote:
>>> Please take a look at an older thread named (IIRC) vinum or geom bug?
>>> Greg asked for special debug output, but it never happened again for me.
>>>
On Saturday, 2 August 2003 at 17:56:49 -0700, Terry Lambert wrote:
> Greg 'groggy' Lehey wrote:
>>> You don't actually need a crash dump to debug a stack traceback.
>>
>> Great! So you know the answer? Please submit a patch.
>>
>> Ser
On Saturday, 2 August 2003 at 17:54:03 -0700, Terry Lambert wrote:
> Eivind Olsen wrote:
>> (kgdb) list *(launch_requests+448)
>> No symbol "launch_requests" in current context.
>> (kgdb) list *(vinumstart+2b2)
>> No symbol "vinumstart" in current context.
>> (kgdb)
>>
>> If anyone wants to take a
On Saturday, 2 August 2003 at 16:47:13 +0200, Eivind Olsen wrote:
> --On 2. august 2003 02:11 -0700 Terry Lambert <[EMAIL PROTECTED]>
> wrote:
>>> db> trace
>>> g_dev_strategy(c2156024,c2153800,0,cfb528d0,c2099eca) at
>>> g_dev_strategy+0x29 launch_requests(c299bf00,0,1,,47) at
>>> lau
On Saturday, 2 August 2003 at 17:00:59 +0200, Eivind Olsen wrote:
> --On 2. august 2003 11:16 +0200 Bernd Walter <[EMAIL PROTECTED]>
> wrote:
>>> Looks like a problem in vinum. The other backtrace was the same, right?
>> Please take a look at an older thread named (IIRC) vinum or geom bug?
>> Gre
On Saturday, 2 August 2003 at 2:11:24 -0700, Terry Lambert wrote:
> Eivind Olsen wrote:
>> Can anyone suggest what I do next to find out about this crash?
>
>> Fatal trap 12: page fault while in kernel mode
>> fault virtual address = 0x14
>
> Dereference of NULL pointer; reference is for elemen
Earlier this month I sent a message saying that my wireless card
(Orinoco) doesn't work at all any more. In the meantime, I've
narrowed the problem down to IBSS ("ad-hoc") mode: it works fine in
BSS (base station) mode. I'd like to know if *anybody* is using IBSS
(maybe with Orinoco cards) on a -
On Sunday, 27 July 2003 at 22:32:42 -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
>> On Sunday, 27 July 2003 at 22:17:32 -0600, M. Warner Losh wrote:
>>> In messa
On Sunday, 27 July 2003 at 22:17:32 -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
>> On Sunday, 27 July 2003 at 22:11:29 -0600, M. Warner Losh wrote:
>>> Wher
On Sunday, 27 July 2003 at 22:11:29 -0600, M. Warner Losh wrote:
> Where are you getting the data? A windows tool?
If you're talking about the BIOS contents I'm printing, yes, I'm using
a Microsoft tool called DEBUG (which has been around since before
Microsoft bought DOS :-).
Greg
--
See comple
On Sunday, 27 July 2003 at 22:03:57 -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
>> Sure. The data at offset 0xc are:
>>
>> C000: 55 AA 78 E9 44 06 00
On Sunday, 27 July 2003 at 21:42:35 -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
>> On Saturday, 26 July 2003 at 22:18:59 -0600, M. Warner Losh wrote:
>>> In messa
On Saturday, 26 July 2003 at 22:18:59 -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
>> Presuming that it's the ROM driver, I get this in the dmesg I posted:
>> pn
On Saturday, 26 July 2003 at 11:00:40 -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "M. Warner Losh" <[EMAIL PROTECTED]> writes:
>> The reason I keep saying that is that nobody knows for sure. Nobody
>> has reverse engineered anything, got sued and won (or lost). Ju
On Saturday, 26 July 2003 at 19:47:50 -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
>> On Saturday, 26 July 2003 at 18:44:43 -0600, M. Warner Losh wrote:
>>>
On Saturday, 26 July 2003 at 18:44:43 -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
>> On Saturday, 26 July 2003 at 11:27:06 -0600, M. Warner Losh wrote:
>>>
On Saturday, 26 July 2003 at 11:27:06 -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
>> machine doesn't have a serial port, so I can't apply a kernel debugger
>&
On Saturday, 26 July 2003 at 9:41:14 +0100, Bruce M Simpson wrote:
> On Sat, Jul 26, 2003 at 05:32:17PM +0930, Greg 'groggy' Lehey wrote:
>> Can anybody point me in the right direction? Where should I be
>> looking for this? Is this memory mapped permanently, or is it
I've spent the last couple of days tracking down a problem starting X
on a Dell Inspiron 5100. I've got as far as discovering that the
video BIOS is not being completely mapped: it's 60 kB long, but only
48 kB are being mapped into memory. To make matters worse, the
machine doesn't have a serial
On Wednesday, 9 July 2003 at 21:40:43 +0100, Chris Hedley wrote:
> Hi all,
>
> I had a quick look for the subject topic but didn't find anything, so...
> is anybody aware of outstanding problems with vinum? I'm getting sporadic
> crashes (see below) and vinum frequently fails to start properly, l
On Thursday, 3 July 2003 at 16:33:30 +0200, Harti Brandt wrote:
> On Thu, 3 Jul 2003, M. Warner Losh wrote:
>
> MWL>In message: <[EMAIL PROTECTED]>
> MWL>Harti Brandt <[EMAIL PROTECTED]> writes:
> MWL>: I think the same problem was reported by Rob Holmes two weeks ago and by
> MWL>: me
I've just upgraded my laptop to a recent -CURRENT, and since then I've
been having a lot of network problems. Here's a rough chronology:
- Machine is a Dell Inspiron 7500, which I've been using with releases
4 and 5 of FreeBSD without problems for the last 3 years. It's
usually connected to
On Tuesday, 10 June 2003 at 14:05:11 +0200, Bernd Walter wrote:
>
> fatal kernel trap:
>
> Stopped at g_dev_strategy+0x44:stq t0,0x20(v0) <0x20>
>
> db> trace
> g_dev_strategy() at g_dev_strategy+0x44
> launch_requests() at launch_requests+0x390
> prologue botch: displacement 12
On Monday, 2 June 2003 at 10:54:06 +0930, Greg 'groggy' Lehey wrote:
> I've just cvsupped the latest -CURRENT, and it dies on me in
> gnu/usr.bin/gperf/doc:
*sigh*
Yes, of course I saw the dialogue between DES and obrien, and the
subsequent commit, so I re-supped and cvs
I've just cvsupped the latest -CURRENT, and it dies on me in
gnu/usr.bin/gperf/doc:
===> gnu/usr.bin/gperf/doc
c++ -O -pipe -std=iso9899:1999
-I/usr/obj/src/FreeBSD/5-CURRENT-ZAPHOD/src/i386/legacy/usr/include
-I/src/FreeBSD/5-CURRENT-ZAPHOD/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib
-
On Wednesday, 26 March 2003 at 13:35:28 +, Jason Morgan wrote:
> I just got a panic. As I have never had one before, I don't know what to
> do. It's on another system so I don't have to reboot immediately (that
> would solve the problem temporarily, wouldn't it?) if someone would give
> me some
On Tuesday, 25 March 2003 at 18:44:03 +0100, Hartmut Brandt wrote:
>
> Hi,
>
> when calling 'vinum start' it responds with
>
> usage: read drive [drive ...]
>
> from looking at the code, it appears that it cannot find the disk drives
> to read the configuration from.
>
> vinum read da0 da1
>
> just
On Monday, 24 March 2003 at 19:07:56 -0500, Hiten Pandya wrote:
> Hi Gang!
>
> I was wondering, what's the point of making Vinum use a totally
> different SYSINIT type? Isn't there a possibility it can just use
> SI_SUB_RAID?
Probably. SI_SUB_VINUM was there first.
Greg
--
See complete headers
On Monday, 17 March 2003 at 23:02:38 -0500, Jeff Roberson wrote:
> On Mon, 17 Mar 2003, Terry Lambert wrote:
>
>> Jeff Roberson wrote:
>>> On Mon, 17 Mar 2003, Brooks Davis wrote:
I am still intrested in improvements to fsck since I'm planning to buy
several systems with two 1.4TB IDE RAI
On Monday, 17 March 2003 at 22:39:02 +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Bakul Shah writes:
>
>> UFS is the real problem here, not fsck. Its tradeoffs for
>> improving normal access latencies may have been right in the
>> past but not for modern big disks. The seek t
On Saturday, 15 March 2003 at 23:56:24 +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey"
> writes:
>
>>> Ok, I'll try to simulate the disk failure by switching off the
>>> power, then.
>>
>>
On Saturday, 15 March 2003 at 10:34:54 +0200, Vallo Kallaste wrote:
> On Sat, Mar 15, 2003 at 12:02:23PM +1030, Greg 'groggy' Lehey
> <[EMAIL PROTECTED]> wrote:
>
>>> -current, system did panic everytime at the end of
>>> initialisation of parity (raid
On Friday, 14 March 2003 at 10:05:28 +0200, Vallo Kallaste wrote:
> On Fri, Mar 14, 2003 at 01:16:02PM +1030, Greg 'groggy' Lehey
> <[EMAIL PROTECTED]> wrote:
>
>>> So I did. Loaned two SCSI disks and 50-pin cable. Things haven't
>>> improved a bi
On Saturday, 1 March 2003 at 20:43:10 +0200, Vallo Kallaste wrote:
> On Thu, Feb 27, 2003 at 11:53:02AM +0200, Vallo Kallaste wrote:
>
The vinum R5 and system as a whole were stable without
softupdates. Only one problem remained after disabling softupdates,
while being online and u
1 - 100 of 161 matches
Mail list logo
