Kris Kennaway wrote:
On Tue, Feb 15, 2005 at 04:11:31PM +, John wrote:
Another data point - I see this in my nightly security logs:
swap_pager: indefinite wait buffer: device: ad0s1f, blkno: 28190, size: 4096
maybe there's a bad block on the swap partition??
That's what this usually means, yes
* Karl M. Joch <[EMAIL PROTECTED]>:
> i had the verion 1 of the freenet6 client running for a long time. now,
> after upgrading to 2.1.1 on a 5.2.1 box the tspc client dumps core.
What does the coredump say?
Volker
--
http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME
__
Hi,
I have a problem that arises once in a while with my IDE drives under
FreeBSD 5.3
uname:
FreeBSD bastion 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #23: Mon Feb 7
13:28:32 UTC 2005
I have two large disks:
/dev/ad2 144G124G9.2G93%/mnt/sp1604n
/dev/ad3 226G202G
--- Mars Trading <[EMAIL PROTECTED]> wrote:
> This idea may seem useless but what have you got to
> lose?
>
> Have you tried changing bios setting for hard drive
> mode to "auto" or
> something other than "LBA"? Maybe "LARGE" or "CHS"?
Is there a risk that I lose all data on my disk, when
chan
On Friday, 11. February 2005 00:25, Karl M. Joch wrote:
> Hello,
>
> i had the verion 1 of the freenet6 client running for a long time. now,
> after upgrading to 2.1.1 on a 5.2.1 box the tspc client dumps core.
Works fine on a 5.2.1 box of mine, FWIW.
--
,_, | Michael Nottebrock
Dear Doug,
trying to boot RELENG_4 kernel with your patches (sata_7) on our FTP I got
kernel panic (page fault in kernel mode, pid 2, no dump possible). Hardware
involved:
[EMAIL PROTECTED]:~# grep ata /var/run/dmesg.boot
atapci0: port
0xa000-0xa03f,0x9c00-0x9c03,0x9800-0x9807,0x9400-0x9403,
At 08:47 2/16/2005, Rob wrote:
--- Mars Trading <[EMAIL PROTECTED]> wrote:
> This idea may seem useless but what have you got to
> lose?
>
> Have you tried changing bios setting for hard drive
> mode to "auto" or
> something other than "LBA"? Maybe "LARGE" or "CHS"?
Is there a risk that I lose all
Ramiro Aceves wrote:
>
> I have read that others had this problem before. I
> just write this report for you to know.
>
> When I installed FreeBSD 5.3 R, I get some errors
> like this, but I could end the install:
>
> ad0: WARNING -READ_DMA UDMA ICRC error (retrying
> request) LBA=53135
I have this problem too...
-- # dmesg | egrep "(ata|ad0)" --
atapci0: port
0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
ad0: FAILURE - SET_MULTI status=51 error=4
ad0: 9787MB [19885/16/63] at
ata0-master PIO4
Mou
Dmitry Morozovsky writes:
| Dear Doug,
|
| trying to boot RELENG_4 kernel with your patches (sata_7) on our FTP I got
| kernel panic (page fault in kernel mode, pid 2, no dump possible). Hardware
| involved:
|
| [EMAIL PROTECTED]:~# grep ata /var/run/dmesg.boot
| atapci0: port
0xa000-0xa03f,
I remember having the same problem on a machine once.
Replacing the IDE cable with a known good one helped.
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily
On Wed, 16 Feb 2005, Doug Ambrisko wrote:
DA> | trying to boot RELENG_4 kernel with your patches (sata_7) on our FTP I
got
DA> | kernel panic (page fault in kernel mode, pid 2, no dump possible).
Hardware
DA> | involved:
DA> |
DA> | [EMAIL PROTECTED]:~# grep ata /var/run/dmesg.boot
DA> | ata
On Wed, 2005-02-16 at 06:31 -0800, Rob wrote:
> Ramiro Aceves wrote:
> >
> > I have read that others had this problem before. I
> > just write this report for you to know.
> >
> > When I installed FreeBSD 5.3 R, I get some errors
> > like this, but I could end the install:
> >
> > ad0: WARNING -
On Wed, 16 Feb 2005 14:02:12 +0100, Charles Erik McDonald
<[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have a problem that arises once in a while with my IDE drives under
> FreeBSD 5.3
>
> uname:
> FreeBSD bastion 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #23: Mon Feb 7
> 13:28:32 UTC 2005
>
> I have
In message: <[EMAIL PROTECTED]>
Takahashi Yoshihiro <[EMAIL PROTECTED]> writes:
: In article <[EMAIL PROTECTED]>
: Warner Losh <[EMAIL PROTECTED]> writes:
:
: > > The following is the result when use SATA 200GB disk on pc98. It is
: > > clearly that recognizing a geometry fails.
: > >
Dmitry Morozovsky writes:
| On Wed, 16 Feb 2005, Doug Ambrisko wrote:
|
| DA> | trying to boot RELENG_4 kernel with your patches (sata_7) on our FTP I
got
| DA> | kernel panic (page fault in kernel mode, pid 2, no dump possible).
Hardware
| DA> | involved:
| DA> |
| DA> | [EMAIL PROTECTED]:~#
Just wondering if any work is being done on this that will allow mlxcontrol
to do raid configuration? It looks like the source has been "dead" for a
few years, with this still listed in the "bugs" section of the manpage.
So far the only SCSI RAID controllers I've used that have any sort of
sup
On Wed, Feb 16, 2005 at 04:41:14PM +0900, Eitarou Kamo wrote:
> I got an io error
> "xf86EnableIO: Fatal to open /dev/io for extended I/O"
> when running "Xorg -configure".
>
> Has this snapshot been fixed this problem?
Do you have a /dev/io?
Do you have "device io" in your kernel configuration?
On Wed, 16 Feb 2005, Doug Ambrisko wrote:
[snip]
DA> You are not using any SATA drives or have any SATA adapters correct.
DA> I haven't tried using vinum with my patch set. That might be a problem.
DA> I'm not sure if anyone has tried vinum with my patch set most people use
DA> ata-raid if any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 16 Feb 2005 09:45:40 -0600, Scot Hetzel <[EMAIL PROTECTED]> wrote:
> > I have two large disks:
> >
> > /dev/ad2 144G124G9.2G93%/mnt/sp1604n
> > /dev/ad3 226G202G5.2G98%/mnt/wd2500pb
>
> Did you use
> -Original Message-
> From: David O'Brien [mailto:[EMAIL PROTECTED]
>
> On Tue, Feb 15, 2005 at 04:53:24PM -, Alan Jay wrote:
> > I had major problems installing with more than 4Gb but once I moved to
> stable
> > we seemed to have a stable platform when doing basic stuff - we have tw
TB --- 2005-02-16 17:45:04 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-02-16 17:45:04 - starting RELENG_5 tinderbox run for alpha/alpha
TB --- 2005-02-16 17:45:04 - checking out the source tree
TB --- 2005-02-16 17:45:04 - cd /home/tinderbox/RELENG_5/alpha/alpha
TB --- 2005-02-
I test with ATA mkIII patch. FAILURE is gone and have few WARNING messages.
My test is generate 6Gb file with dd if=/dev/zero of=file
# dmesg | egrep -i "(ata|ad0)"
atapci0: port
0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0
ata0: on atapci0
ata1: on atapci0
ad0: FAILU
TB --- 2005-02-16 18:45:44 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-02-16 18:45:44 - starting RELENG_5 tinderbox run for amd64/amd64
TB --- 2005-02-16 18:45:44 - checking out the source tree
TB --- 2005-02-16 18:45:44 - cd /home/tinderbox/RELENG_5/amd64/amd64
TB --- 2005-02-
TB --- 2005-02-16 19:49:29 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-02-16 19:49:29 - starting RELENG_5 tinderbox run for i386/i386
TB --- 2005-02-16 19:49:29 - checking out the source tree
TB --- 2005-02-16 19:49:29 - cd /home/tinderbox/RELENG_5/i386/i386
TB --- 2005-02-16 1
> >> Do you have any error messages related to ad2 or ad3 in
/var/log/messages?
no.
> >>I have two large disks:
> >>
> >>/dev/ad2 144G124G9.2G93%/mnt/sp1604n
> >>/dev/ad3 226G202G5.2G98%/mnt/wd2500pb
>
> >Did you use disklabel on these disks (/dev/ad2s1
TB --- 2005-02-16 20:52:31 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-02-16 20:52:31 - starting RELENG_5 tinderbox run for i386/pc98
TB --- 2005-02-16 20:52:31 - checking out the source tree
TB --- 2005-02-16 20:52:31 - cd /home/tinderbox/RELENG_5/i386/pc98
TB --- 2005-02-16 2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 16 Feb 2005 21:58:37 +0100, Charles Erik McDonald
<[EMAIL PROTECTED]> wrote:
> bastion(root):#mount -t ufs /dev/ad3s1 /mnt/wd2500pb/
> mount: /dev/ad3s1 on /mnt/wd2500pb: incorrect super block
> bastion(root):#mount -t ufs /dev/ad3s1c /mnt/wd
TB --- 2005-02-16 21:55:31 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-02-16 21:55:31 - starting RELENG_5 tinderbox run for ia64/ia64
TB --- 2005-02-16 21:55:31 - checking out the source tree
TB --- 2005-02-16 21:55:31 - cd /home/tinderbox/RELENG_5/ia64/ia64
TB --- 2005-02-16 2
On Wed, 16 Feb 2005, Rong-En Fan wrote:
> Hello,
>
> This is a 5.3-RELEASE-p5/amd64 on IBM X236 (EM64T) with 2GB RAM
> and a LSI 21320 rmpt(4) running at 160MB/s with a hardware
> RAID (da0, da1). HTT is enabled. When I run benchmark/blogbench on
> /da0/ I can *reproduce* this panic again and agai
Marcus Grando wrote:
> I test with ATA mkIII patch. FAILURE is gone and
have
> few WARNING messages.
>
> My test is generate 6Gb file with
>dd if=/dev/zero of=file
Very interesting indeed. I have two questions:
1) Which patch did you apply and from where did you
get it?
2) Af
TB --- 2005-02-16 23:09:49 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2005-02-16 23:09:49 - starting RELENG_5 tinderbox run for sparc64/sparc64
TB --- 2005-02-16 23:09:49 - checking out the source tree
TB --- 2005-02-16 23:09:49 - cd /home/tinderbox/RELENG_5/sparc64/sparc64
TB ---
On Thu, 17 Feb 2005 03:12, Ceri Davies wrote:
> On Wed, Feb 16, 2005 at 04:41:14PM +0900, Eitarou Kamo wrote:
> > I got an io error
> > "xf86EnableIO: Fatal to open /dev/io for extended I/O"
> > when running "Xorg -configure".
> >
> > Has this snapshot been fixed this problem?
>
> Do you have a /d
ATA mkIII has improved my Toshiba Tecra M2V running RELENG_5.
Before, it would complain about "ATAPI_IDENTIFY TIMED OUT" on
ata1-slave (the cdrom is ata1-master) when booting (but still would
work). Even worse, when resuming from a memory suspend (S3) it would
lose ad0 and hence crash, with messa
Hi,
In /boot/defaults/loader.conf there's the line:
#init_path="[...skip...]:/stand/sysinstall"
I wonder if /stand/sysinstall is still appropriate
as one of the defaults in the init path.
There has been a plan to remove /stand/ altogether
after install, or even have it completely replaced
by /
On Thu, 10 Feb 2005 14:41:10 +0100, Søren Schmidt <[EMAIL PROTECTED]> wrote:
> Freddie Cash wrote:
> >>New version that fixes known problems so far etc now available:
> >
> >
> > Just curious if this includes support for new chipsets or not. Not a
> > big deal if it doesn't, just curious.
> >
> >
36 matches
Mail list logo