Garance A Drosihn wrote:
At 1:01 AM -0600 12/7/04, Tim Welch wrote:
I'm getting NID not found/DMA errors on 5-STABLE with a Seagate 200gb
sata drive:
ad2: FAILURE - WRITE_DMA status=51
error=10 LBA=268435455
This appears to be a result of 48-bit addressing. Any time a write is
attempted to th
> The problem just resurfaced when I built a custom 5.3 kernel. It turns
> put that the problem was never fixed. The kernel on the 5.3 release
> installation disk now just rejects the floppy drive when it configures
> the floppy controller and the system comes up without the floppy drive,
> some
- Original Message -
From: <[EMAIL PROTECTED]>
To: "whitevamp" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, December 08, 2004 4:43 PM
Subject: Re: no internet after build world-kern install
> > I have done a buildworld from 4.9 to 5.3 and also installed a new
custom ker
Hi,
In /boot/loader.conf, I have
hw.ata.ata_dma="0"
to prevent a WRITE_DMA failure crash at bootup.
Unfortunately, this forces my UDMA100 harddisk to operate
at PIO4 speed.
There are patches flying around on this mailing list that might
solve the problem. I'm very keen on testing such patches, bu
At 1:01 AM -0600 12/7/04, Tim Welch wrote:
I'm getting NID not found/DMA errors on 5-STABLE with a Seagate 200gb
sata drive:
ad2: FAILURE - WRITE_DMA status=51
error=10 LBA=268435455
This appears to be a result of 48-bit addressing. Any time a write is
attempted to the sector above, I get mul
ok i still havent got this resolved yet , heres an up date of things i have
tryed to no avail , swaped out eth cards, swaped out cables, hooked up the
box straight upto the dsl modem, looked around on the box to see if a
firewall was getting started some ware and couldnt find one .
so heres a recap
On Thu, Dec 09, 2004 at 01:42:21AM -0200, Crist?v?o Dalla Costa wrote:
> Hello, this is just to report back that disabling hyper-threading in the
> BIOS made the problem go away completely. I'm sorry I didn't generate a
> core dump but because I installed four swap partitions each with half
> th
Hello, this is just to report back that disabling hyper-threading in the
BIOS made the problem go away completely. I'm sorry I didn't generate a
core dump but because I installed four swap partitions each with half
the size of the RAM and the handbook says I needed one swap partition
with at le
> I have done a buildworld from 4.9 to 5.3 and also installed a new custom
> kernel and
> after all whent ok i rebooted the box and goto ping yahoo.com and i cant get
> out ,
> and i also tryed pinging my outhere ip address and nothing on eathere one it
> just
> say destination unreachable. so
Booting safe mode actually works. Heck, I even got to
use sysinstall. =}
I shall try to replicate the stuff that gets set in
beastie.4th and slap it into my loader.conf. Hopefully
that should be enough to get me by.
Thanks!
--- Lapo Nustrini <[EMAIL PROTECTED]> wrote:
> Have you tried booting
On Wednesday, 8 December 2004 at 11:20:34 +, Robert Watson wrote:
>
> On Tue, 7 Dec 2004, Michael Nottebrock wrote:
>
>> I recently enabled SW_WATCHDOG in my kernel, but when watchdog triggers
>> a panic, no crashdump is taken although dumps are enabled. What could be
>> causing this?
>
> If y
Hi,
Once again I ran into WRITE_DMA failure at bootup with one of my PCs.
Motherboard: LGM-VBX6
Twin Processor /* not dual */
VIA 82C693 Apollo Pro AGPset
2Mb Flash ROM BIOS
UDMA66 support
BIOS: Award Software Inc. v4.51PG
Harddisk: IBM-DTLA-307045/TX6OA50C 43979M
At 08:15 PM 08/12/2004, Cristóvão Dalla Costa wrote:
I've disabled SMP with the kern.smp.disabled=1 sysctl and I'll see what
happens next. Strangely though the kernel seems to think the system has
only one cpu despite it being hyperthreaded:
You want to turn HT off in the BIOS. The scheduler wil
Brooks Davis wrote:
On Wed, Dec 08, 2004 at 10:21:24PM -0200, Cristóvão Dalla Costa wrote:
I just installed 5.3 RELEASE on a new server today and everytime I try
to compile someting for more than five minutes it crashes.
This sounds like hardware, but it could be a bug related to your
part
On Wednesday 08 December 2004 04:21 pm, Nuno Teixeira wrote:
> Hello to all,
>
> I'm runinng RELENG_5 and I noticed that ULE scheduler is broken.
> Shouldn't this be documented in UPDATING?
>
> Thanks very much,
>
> Nuno Teixeira
It's documented in errata:
(1 Nov 2004) The ULE schedu
I shall try this. Do you have any idea what differs
for the IDE driver (I presume ATAng) when booting into
safe mode?
--- Lapo Nustrini <[EMAIL PROTECTED]> wrote:
> Have you tried booting up in safe mode?
> I have a similar issue running 5.3 STABLE on a
> machine which runs fine
> with 5.3 BETA7
On Wed, Dec 08, 2004 at 10:21:24PM -0200, Cristóvão Dalla Costa wrote:
> I just installed 5.3 RELEASE on a new server today and everytime I try
> to compile someting for more than five minutes it crashes.
This sounds like hardware, but it could be a bug related to your
particular system. Do you
Hello
I just installed 5.3 RELEASE on a new server today and everytime I try
to compile someting for more than five minutes it crashes.
The message it said in the console is something like "page fault while
in kernel mode", excuse-me if I don't remember it verbatim but I just
drove home from th
On Wed, Dec 08, 2004 at 10:21:02PM +, Nuno Teixeira wrote:
>
> Hello to all,
>
> I'm runinng RELENG_5 and I noticed that ULE scheduler is broken.
> Shouldn't this be documented in UPDATING?
Yes. I thought it was, but you are correct in asserting that it isn't.
Ceri
--
Only two things are
Hello to all,
I'm runinng RELENG_5 and I noticed that ULE scheduler is broken.
Shouldn't this be documented in UPDATING?
Thanks very much,
Nuno Teixeira
--
SDF Public Access UNIX System - http://sdf.lonestar.org
___
[EMAIL PROTECTED] maili
* nicky <[EMAIL PROTECTED]> [20041203 11:47]:
> Joan Picanyol wrote:
> >* Michael Nottebrock <[EMAIL PROTECTED]> [20041203 10:52]:
> >>Joan Picanyol wrote:
> # grep atapi /usr/src/sys/i386/conf/LILO
> device atapicd # ATAPI CDROM drives
>
> >>>You don't need thi
I have done a buildworld from 4.9 to 5.3 and also installed a new custom
kernel and after all whent ok i rebooted the box and goto ping yahoo.com and i
cant get out , and i also tryed pinging my outhere ip address and nothing on
eathere one it just say destination unreachable. so i whent back a
On Wed, 8 Dec 2004, David Gilbert wrote:
> > "Robert" == Robert Watson <[EMAIL PROTECTED]> writes:
>
> Robert> This is a NULL pointer dereference; you can use addr2line or
> Robert> gdb on your kernel.debug to turn it into a line number even
> Robert> without a core. That might well be wort
Have you tried booting up in safe mode?
I have a similar issue running 5.3 STABLE on a machine which runs fine
with 5.3 BETA7.
Booting into safe mode works fine. Any other way, and it gets ATAPI
errors or SCSI errors (if I take all ATAPI stuff out of the kernel).
Still trying to find the real
Frank Mayhar wrote:
cat /etc/devfs.rules
[devfsrules_local=15]
add path 'bpf*' mode 0660
add path 'ugen*' mode 0664
add path 'cd*' mode 0664
For example. For some hints, 'man devfs' and /etc/defaults/devfs.rules.
Oh, and for this example, don't forget to add
devfs_system_ruleset="devfsru
> "Robert" == Robert Watson <[EMAIL PROTECTED]> writes:
Robert> This is a NULL pointer dereference; you can use addr2line or
Robert> gdb on your kernel.debug to turn it into a line number even
Robert> without a core. That might well be worth doing, as we might
Robert> be able to debug that ev
Frank Mayhar wrote:
> Ivan Voras wrote:
> [ Charset ISO-8859-2 unsupported, converting... ]
> > Is there a canonical way of preserving devfs rules (device permissions
> > actually) across reboots?
>
> >cat /etc/devfs.rules
> [devfsrules_local=15]
> add path 'bpf*' mode 0660
> add path 'ugen*' mo
Ivan Voras wrote:
[ Charset ISO-8859-2 unsupported, converting... ]
> Is there a canonical way of preserving devfs rules (device permissions
> actually) across reboots?
>cat /etc/devfs.rules
[devfsrules_local=15]
add path 'bpf*' mode 0660
add path 'ugen*' mode 0664
add path 'cd*' mode 0664
For
On Wednesday, 8. December 2004 17:55, Ivan Voras wrote:
> Is there a canonical way of preserving devfs rules (device permissions
> actually) across reboots?
>
> It seems devd.conf works only for "static" devices, not hotplugged,
> while devfs rules works for those, but they vanish on reboot.
You c
Ivan Voras wrote:
Is there a canonical way of preserving devfs rules (device permissions
actually) across reboots?
It seems devd.conf works only for "static" devices, not hotplugged,
^
this should have been "devfs.conf"
while devfs(8) rules work for those, but they vani
Is there a canonical way of preserving devfs rules (device permissions
actually) across reboots?
It seems devd.conf works only for "static" devices, not hotplugged,
while devfs rules works for those, but they vanish on reboot.
___
[EMAIL PROTECTED] mai
I played around with the kernel debug options a little and found peculiar
things:
- With just options KDB (and no debugger backend specified), a panic will just
cause some output scroll very fast on the console - perhaps kdb is trying to
enter a nonexisting debugger backend and loops?
- With
On Wednesday, 8. December 2004 13:38, Robert Watson wrote:
Okay, I've now enabled the following in the kernel:
options KDB
options KDB_TRACE
options DDB
> So I'm thinking it
> would be nice to know:
>
> - Can you enter and continue from kdb normally using the sysctl.
Yes
Hi,
Ihas following System dmesg:
Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.10-STABLE #1: Tue Nov 30 14:26:29 CET 2004
[EMAIL PROTECTE
On Wednesday, 8. December 2004 13:38, Robert Watson wrote:
> ULE is temporarily without an owner, but Jeff and others have expressed
> interest in working on it further. I'd not run it for the time being, but
> it's probably not a hopeless case. Does the above statement mean that the
> hangs or p
On Wed, 8 Dec 2004, Michael Nottebrock wrote:
> > > I don't have kdb enabled in my kernel configuration at all...
> >
> > I'm guessing it might be useful at this point, if possible :-).
>
> Useful for what exactly? I'm mainly interested in getting this machine
> to auto-reboot after a (watchdog-
Hi,
Ihas following System dmesg:
Copyright (c) 1992-2004 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.10-STABLE #1: Tue Nov 30 14:26:29 CE
On Wednesday, 8. December 2004 13:16, Michael Nottebrock wrote:
> > > panic: page fault
> >
> > This is a NULL pointer dereference; you can use addr2line or gdb on your
> > kernel.debug to turn it into a line number even without a core. That
> > might well be worth doing, as we might be able to d
On Wednesday, 8. December 2004 12:54, Robert Watson wrote:
> On Wed, 8 Dec 2004, Michael Nottebrock wrote:
> > On Wednesday, 8. December 2004 12:20, Robert Watson wrote:
> > > On Tue, 7 Dec 2004, Michael Nottebrock wrote:
> > > > I recently enabled SW_WATCHDOG in my kernel, but when watchdog
> > >
On Wed, 8 Dec 2004, Michael Nottebrock wrote:
> On Wednesday, 8. December 2004 12:20, Robert Watson wrote:
> > On Tue, 7 Dec 2004, Michael Nottebrock wrote:
> > > I recently enabled SW_WATCHDOG in my kernel, but when watchdog triggers
> > > a panic, no crashdump is taken although dumps are enabled
On Wednesday, 8. December 2004 12:28, Robert Watson wrote:
> On Wed, 8 Dec 2004, Robert Watson wrote:
> > On Tue, 7 Dec 2004, Michael Nottebrock wrote:
> > > I recently enabled SW_WATCHDOG in my kernel, but when watchdog triggers
> > > a panic, no crashdump is taken although dumps are enabled. What
On Wednesday, 8. December 2004 12:20, Robert Watson wrote:
> On Tue, 7 Dec 2004, Michael Nottebrock wrote:
> > I recently enabled SW_WATCHDOG in my kernel, but when watchdog triggers
> > a panic, no crashdump is taken although dumps are enabled. What could be
> > causing this?
>
> If you drop to th
On Wed, 8 Dec 2004, Robert Watson wrote:
> On Tue, 7 Dec 2004, Michael Nottebrock wrote:
>
> > I recently enabled SW_WATCHDOG in my kernel, but when watchdog triggers
> > a panic, no crashdump is taken although dumps are enabled. What could be
> > causing this?
>
> If you drop to the debugger b
On Tue, 7 Dec 2004, Michael Nottebrock wrote:
> I recently enabled SW_WATCHDOG in my kernel, but when watchdog triggers
> a panic, no crashdump is taken although dumps are enabled. What could be
> causing this?
If you drop to the debugger by using the debug.kdb.enter sysctl, and do
"call doadum
On Tue, 7 Dec 2004 15:48, Daniel O'Connor wrote:
> > Needless to say that is quite untested/unsupported by us, and if you've
> > been using any packages there's a good chance things aren't fitting
> > together so well. I do hope Xorg 6.8.1 won't break KDE on 4.x once it's
> > in ports, but I can't
On Tuesday, 7. December 2004 21:54, Michael Nottebrock wrote:
> I recently enabled SW_WATCHDOG in my kernel, but when watchdog triggers a
> panic, no crashdump is taken although dumps are enabled. What could be
> causing this?
FWIW, I got a "real" panic today (page fault) and no dump was taken the
(I am posting this message to freebsd-stable because release 5.3 is
allegedly now stable and freebsd-current is now beginning to concern
itself with things that will belong to release 6.0. Let me know if
another mailing list would be more appropriate.)
When FreeBSD 5.3-RC1 was being tested I repo
[ freebsd-stabl@ is now the right place for RELENG_5 ].
On Tue, Dec 07, 2004 at 11:48:40PM -0700, Travis Poppe wrote:
> Hello all,
>
> Back in October, I contacted the list and described a problem I was
> having with FreeBSD 5.X (now 5.3-RELEASE) and sound. I will reiterate
> the problem one more
48 matches
Mail list logo
