On Friday, 19 March 1999 at 23:30:44 -0600, Russell Neeper wrote:
> I decided to give vinum a try a few days ago and ran into the same
> problem as Vallo - after using it for a short period of time it caused
> a kernel panic due to a page fault.
>
> I spent some time with kgdb today and believe tha
I decided to give vinum a try a few days ago and ran into the same
problem as Vallo - after using it for a short period of time it caused
a kernel panic due to a page fault.
I spent some time with kgdb today and believe that I have found the bug.
On Thu, Mar 18, 1999 at 01:31:23PM +1030, Greg Leh
Is there any IPSEC support available for current? I've found support for
2.2.8, but not so far for current.
Steven P. Donegan email: done...@quick.net
Sr. Network Infrastructure Engineer ICBM: N 33' 47.538/W 117' 59.687
WANG Global
Andrew Heybey writes:
| When the deadlock does occur, "ps" (in ddb) says that there are many
| processes in vmwait. The pagedaemon is in an inode wait. The stack
| trace is in default_halt() (which I assume just means that there are
| no runnable processes). The system is not short of memory (un
> In article <199903171103.naa13...@ceia.nordier.com> you wrote:
> > Søren Schmidt wrote:
> >
> >> OK, easy enough, this is what I want to do:
> >>
> >> Boot from an ata disk on major# 30, device name "ad", plain and simple.
> >
> > I'd be inclined to handle this outside the boot code, by trea
In article <199903171103.naa13...@ceia.nordier.com> you wrote:
> Søren Schmidt wrote:
>
>> OK, easy enough, this is what I want to do:
>>
>> Boot from an ata disk on major# 30, device name "ad", plain and simple.
>
> I'd be inclined to handle this outside the boot code, by treating the
> passe
[Meta question: should I send this kind of thing to -current or
-stable? I experienced it under 3.1, but I don't know if the people
who are working on the VM and/or IO systems read -stable?]
I can wedge my 3.1-RELEASE system under the following conditions:
Two fxp fast ethernet interfaces, each
I have an LS-120 and I'd be happy to test the new boot code with it.
Bob
--
Bob Willcox The man who follows the crowd will usually get no
b...@luke.pmr.comfurther than the crowd. The man who walks alone is
Austin, TX likely to find himself in places no one has
On Thu, Mar 18, 1999 at 06:36:09PM -0800, Matthew Dillon wrote:
# :On Thu, Mar 18, 1999 at 12:28:35PM +0300, Mikhail A. Sokolov wrote:
# :# Hello,
# :# panic: ffs_valloc: dup alloc
# :
# :And a brand new one (for today):
# :
# :IdlePTD 2682880
# :initial pcb at 21c7b8
# :panicstr: ffs_blkfree: free
>I get very consistant panics when doing ``find . -type f |xargs grep
>foo'' on a Solaris CDROM in my Plextor 8x CDROM drive (device cd0). I'm
>not sure how to proceed in fixing this.
This should be fixed now. I got very consistent panics for
`cd /dosD/windows; find . | xargs cksum' on an msdosf
On Fri, Mar 19, 1999 at 01:11:17AM -0800, David O'Brien wrote:
> I get very consistant panics when doing ``find . -type f |xargs grep
> foo'' on a Solaris CDROM in my Plextor 8x CDROM drive (device cd0). I'm
> not sure how to proceed in fixing this.
On another machine (CVSuped and make world on T
I get very consistant panics when doing ``find . -type f |xargs grep
foo'' on a Solaris CDROM in my Plextor 8x CDROM drive (device cd0). I'm
not sure how to proceed in fixing this.
The core files from the panic seem to be useless -- I can't get anything
useful out of ``where'' with a kernel w/deb
12 matches
Mail list logo
