On 2 May, Rod Taylor wrote:
= As a side note to this long conversation, I'll mention that I've
= downgraded that box back to 3.4 and it now works properly again.
>From my experience, you could've just used the old wd driver instead of
the new ata stuff and ignore the config's warnings.
I
Well I actually have two prior crashes that I did save before I turned off
the dumpsaves to avoid running out of drive space, and as I am by no means
a gdb user if you could tell me what your looking for I'll be happy to fire
up gdb and send you the info.
Here is what I grabbed out of the /va
Hello,
I know I posted a few messages here in the past, but maybe someone who is
good at tracking kernel problems can step up and lend a hand.
I have a machine running FBSD 4.0-STABLE, and have been experiencing almost
daily kernel panics or reboots on the machine. I have replaced ALL of
On Wednesday, 3 May 2000 at 3:48:42 -0400, Howard Leadmon wrote:
>
>Hello,
>
> I know I posted a few messages here in the past, but maybe someone who is
> good at tracking kernel problems can step up and lend a hand.
>
> I have a machine running FBSD 4.0-STABLE, and have been experiencing
| Well, perhaps not. Running the old firmware, 2.39, my install of 4.0
fails
| early on copying files:
|
| bus_dmamap_load : Too many segs! buf_len = 0x1
| mlx0 : I/O error -- attempt to write beyond end of drive
|
| Any idea what these mean?
|
| I flashed it with the newest Mylex firmwar
>
> | Well, I have good news, I think. The mlx driver _seems_ to work as-is
> (from
> | a kernel built with 4.0-STABLE). I get a warning about an old BIOS rev,
> but
> | it looks functional. The driver reported the correct logical drive size
> and
> | no other errors.
>
> Well, perhaps not.
Has any progress been made on the parallel port zip problem?
jm
--
---
Jonathon McKitrick -- [EMAIL PROTECTED]
I am a bomb technician. If you see me running, try to keep up.
--
Brad Knowles wrote:
> At 1:55 AM -0400 2000/5/3, spork wrote:
>
> > Last I looked though, vinum cannot protect you from loss of your boot
> > device.
>
> I am told that in FreeBSD 4.0, vinum now has the ability to
> mirror the root filesystem. I don't know if this addresses the issue
>
> > Well, perhaps not. Running the old firmware, 2.39, my install of 4.0 fails
> > early on copying files:
> >
> > bus_dmamap_load : Too many segs! buf_len = 0x1
> > mlx0 : I/O error -- attempt to write beyond end of drive
> >
> > Any idea what these mean?
>
> The 2.x firmware only suppor
> > > Well, perhaps not. Running the old firmware, 2.39, my install of 4.0 fails
> > > early on copying files:
> > >
> > > bus_dmamap_load : Too many segs! buf_len = 0x1
> > > mlx0 : I/O error -- attempt to write beyond end of drive
> > >
> > > Any idea what these mean?
> >
> > The 2.x fi
At 1:19 PM -0400 2000/5/3, Charles N. Owens wrote:
> Do you have any pointers to such information (ideally, something like a
> "how-to")?
Greg is the one who told me about it, and this was the kicker
behind my finally getting off my butt and giving 4.0 a try, although
I have yet to a
Judging by your original bug report, Howard, it seems likely that either
the machine or the network the machine is sitting on is being attacked
and the machine is running out of some resource (probably network mbufs).
Increasing the NMBCLUSTERS any more will probably not help.
I have strange problems under 4.0-STABLE with this drive
CD-RW at ata1-master using PIO4
when recodring CDs.
I put in the blank CD, and the drive spins for about a minute until it
settles and seems to recognize the blank. I then do:
hbo# burncd -s 8 audio *raw fixate
which results in this mess
- Original Message -
From: "Mike Smith" <[EMAIL PROTECTED]>
| > Ok. I know how I'm going to have to deal with this; the problem is that
| > we only use 16 of the 17 available S/G segments (so I can pack the S/G
| > tables without crossing page boundaries). This is going to take a
littl
14 matches
Mail list logo
