On Fri, 10 Oct 2003, Soren Schmidt wrote:
> It seems Nate Lawson wrote:
> > Here is an updated status of ATAng for me. I periodically test it to see
> > if any of the following problems go away.
> >
> > * Panic occurs after ATAFD fails to probe. Last event: 2003/10/6
> > I have no ATAFD device on
TB --- 2003-10-25 04:32:16 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-10-25 04:32:16 - starting CURRENT tinderbox run for amd64/amd64
TB --- 2003-10-25 04:32:16 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64
TB --- /usr/bin/cvs -f -R -q -d/home/
TB --- 2003-10-25 04:00:00 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-10-25 04:00:00 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-10-25 04:00:00 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/
On Fri, 24 Oct 2003, Munish Chopra wrote:
> On 2003-10-24 23:39 -0300, Marc G. Fournier wrote:
> >
> > Just noticed that sound isnt' working on my laptop since my last upgrade
> > (Oct 16), and one of our desktop's at the office is exhibiting the same
> > thing ...
> >
> > Just CVSup new sources
On 2003-10-24 23:39 -0300, Marc G. Fournier wrote:
>
> Just noticed that sound isnt' working on my laptop since my last upgrade
> (Oct 16), and one of our desktop's at the office is exhibiting the same
> thing ...
>
> Just CVSup new sources, and see nothing sound related having changed since
> my
Just noticed that sound isnt' working on my laptop since my last upgrade
(Oct 16), and one of our desktop's at the office is exhibiting the same
thing ...
Just CVSup new sources, and see nothing sound related having changed since
my last one, so is this an isolated thing that nobody else is seein
On Fri, Oct 24, 2003 at 04:14:02PM -0500, Greg Hogan wrote:
> I am pretty new to buildworld and I am having the following problem:
>
> whenever I run 'make buildworld' I get errors when it gets to libfetch.
> Specifically, i get compile errors in the file
> /usr/src/lib/libfetch/common.c on lin
> > Fatal trap 12: page fault while in kernel mode
>
> I just committed a fix for this to CVS. Sorry for the trouble.
>
> --
> Eric Anholt[EMAIL PROTECTED]
This looks like the bug that was causing me trouble.
Mike Squires
_
Hi,
Any objections if I commit the below diff, and add the attached file as
src/etc/periodic/daily/405.status-ata_raid ?
Index: defaults/periodic.conf
===
RCS file: /home/ncvs/src/etc/defaults/periodic.conf,v
retrieving revision 1.25
Hardware: Soekris Net4801 (ComBIOS 1.21), SanDisk 512MB Ultra Compact Flash
Software: 5.1-CURRENT
Symptom:ad0: FAILURE - SET_MULTI status=51
error=4
GEOM: create disk ad0 dp=0xc47ffb70
ad0: 488MB [993/16/63] at ata0-master PIO4
Result: system boo
On Fri, 24 Oct 2003, Greg Hogan wrote:
> I am pretty new to buildworld and I am having the following problem:
>
> whenever I run 'make buildworld' I get errors when it gets to libfetch.
> Specifically, i get compile errors in the file
> /usr/src/lib/libfetch/common.c on lines 58-63. See the follo
TB --- 2003-10-24 22:04:38 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-10-24 22:04:38 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-10-24 22:04:38 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64
TB --- /usr/bin/cvs -f -R -q
TB --- 2003-10-24 21:33:34 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-10-24 21:33:34 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-10-24 21:33:34 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs
On Fri, 2003-10-24 at 05:39, Sergey A. Osokin wrote:
> Hello,
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x60
> fault core= supervisor read, page not present
> instruction pointer = 0x8:0xc04d6d42
> stack pointer = 0x10:0xde5b7624
> frame poi
* Nate Lawson <[EMAIL PROTECTED]> [2003-10-24 22:57]:
> Type "tr" at the DDB prompt to get a trace of what is hanging.
At the time of the hang a 'ps' in DDB shows two screenful's of
processes. Doing a simple 'tr' just gives the backtrace of how I got
into DDB which - I presume - is not relevant to
I am pretty new to buildworld and I am having the following problem:
whenever I run 'make buildworld' I get errors when it gets to libfetch.
Specifically, i get compile errors in the file
/usr/src/lib/libfetch/common.c on lines 58-63. See the following links for
relevent information:
http://
On Sat, Oct 25, 2003 at 06:06:24AM +0900, Hajimu UMEMOTO wrote:
> Hi,
>
> > On Fri, 24 Oct 2003 23:03:31 +0200
> > Wilko Bulte <[EMAIL PROTECTED]> said:
>
> wkb> ll -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libfetch/common.c
> wkb> /usr/src/lib/libfetch/common.c:58: error: `EAIN
Hi,
> On Fri, 24 Oct 2003 23:03:31 +0200
> Wilko Bulte <[EMAIL PROTECTED]> said:
wkb> ll -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libfetch/common.c
wkb> /usr/src/lib/libfetch/common.c:58: error: `EAINONAME' undeclared here (not
It was fixed already. Please re-cvsup.
Sorry for
On Fri, Oct 24, 2003 at 11:03:31PM +0200, Wilko Bulte wrote:
> ll -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libfetch/fetch.c
> cc -O -pipe -mcpu=ev6 -mieee -I. -DINET6 -DWITH_SSL -Wsystem-headers -Werror
> -Wa
> ll -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libfetch/common.c
> /u
ll -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libfetch/fetch.c
cc -O -pipe -mcpu=ev6 -mieee -I. -DINET6 -DWITH_SSL -Wsystem-headers -Werror
-Wa
ll -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libfetch/common.c
/usr/src/lib/libfetch/common.c:58: error: `EAINONAME' undeclared here (no
-CURRENT as of 10/17 is not a problem, kernel just compiled with SMP
support today after cvsup at about 2 PM EST (10/24) panics.
Nothing shows up in the logs (of course?). I'm recompiling with no SMP
support and will report if that dies also.
Hardware is the oddball SM P6DGH dual PIII/850 with b
On Fri, 2003-10-24 at 13:40, Arjan van Leeuwen wrote:
> On Friday 24 October 2003 19:30, Kris Kennaway wrote:
> > On Fri, Oct 24, 2003 at 10:13:34AM -0700, Janet Sullivan wrote:
> > > Kris Kennaway wrote:
> > > >On Fri, Oct 24, 2003 at 04:39:14PM +0400, Sergey A. Osokin wrote:
> > > >>Fatal trap 12
On Friday 24 October 2003 19:30, Kris Kennaway wrote:
> On Fri, Oct 24, 2003 at 10:13:34AM -0700, Janet Sullivan wrote:
> > Kris Kennaway wrote:
> > >On Fri, Oct 24, 2003 at 04:39:14PM +0400, Sergey A. Osokin wrote:
> > >>Fatal trap 12: page fault while in kernel mode
> > >
> > >Looks like it might
Hi,
Once again we cvsupped latest ATA code changes and nothing much
changed. Only after couple minutes of stress testing system will
freeze. Though error message is little different than before.
Tomppa
ad5: TIMEOUT - READ_DMA retrying (2 retries left)
ata2: resetting devices ..
ata2: reset t
Thanks again for looking at this problem
Doug White wrote:
> On Thu, 23 Oct 2003, othermark wrote:
> Onboard fiber? What kind of system is this?
They're wired to the board. I'd probably break the connector if I remove
it. This box has custom hardware attached, I don't expect any of the
driv
I also trapped same problem.
Subject: Re: fresh -current trap,
On Fri, 24 Oct 2003 10:00:57 -0700, Kris Kennaway wrote:
> Looks like it might be related to the DRM import from yesterday.
> You're not using any modules, are you?
I'm using a radeon DRM module.
--
Shin-ichi YOSHIMOTO <[EMAIL PROTE
On Fri, 2003/10/24 at 09:09:25 +0400, Alex Deiter wrote:
> panic: trap: fast data access mmu miss
> cpuid = 0;
> Debugger("panic")
> Stopped at Debugger+0x1c: ta %xcc, 1
> db> tr
> panic() at panic+0x174
> trap() at trap+0x394
> -- fast data access mmu miss tar=0 %o7=0xc018b820 -
On Fri, 2003-10-24 at 00:13, Thomas Schwarzkopf wrote:
> On Friday 24 October 2003 02:00, James Tanis wrote:
>
> > From the log file:
> > (II) Primary Device is:
> > (--) Assigning device section with no busID to primary device
> > (WW) RADEON: No matching Device section for instance (BusID
> >
Hi,
I've just committed to switch Advanced Sockets API for IPv6 from
RFC2292 to RFC3542 (aka RFC2292bis). Though I believe this commit
doesn't break backward compatibility againt existing binaries, it
breaks backward compatibility of API.
Now, the applications which use Advanced Sockets API such
Eric, I updated my 5.1-RELEASE system to CURRENT dated today at
approx. 9:10 CDT to give your changes a try. I had a bit of a fright at
first with kernel panics right at the end of the boot sequence but it turned
out I had forgotten to disable the ltmdm code -- the kernel module
compiled under -RE
Il Ven, 2003-10-24 alle 17:47, Michael L. Squires ha scritto:
> Tinderbox
> > /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libfetch/common.c:60:
> error: initializer element is not constant
>
> Under 5.1-CURRENT or i386 cvsuped on 10/23 I get the same failure, with
> the additio
On Fri, Oct 24, 2003 at 10:13:34AM -0700, Janet Sullivan wrote:
>
> Kris Kennaway wrote:
> >On Fri, Oct 24, 2003 at 04:39:14PM +0400, Sergey A. Osokin wrote:
> >>
> >>Fatal trap 12: page fault while in kernel mode
>
> >Looks like it might be related to the DRM import from yesterday.
> >You're not
On Fri, Oct 24, 2003 at 04:39:14PM +0400, Sergey A. Osokin wrote:
> Hello,
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x60
> fault core= supervisor read, page not present
> instruction pointer = 0x8:0xc04d6d42
> stack pointer = 0x10:0xde5b762
On Fri, Oct 24, 2003 at 10:47:22AM -0500, Michael L. Squires wrote:
> Tinderbox
> > /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libfetch/common.c:60:
> error: initializer element is not constant
>
> Under 5.1-CURRENT or i386 cvsuped on 10/23 I get the same failure, with
> the a
On Fri, Oct 24, 2003 at 09:44:45AM +0200, Pawel Jakub Dawidek wrote:
> Hello.
>
> It was reported already?
Yes, n times.
Kris
pgp0.pgp
Description: PGP signature
[ add compatability hacks to libm ]
> > We tried this at usenix, but it still didn't work. Obviously there is more
> > going on.
> >
> > Before anybody goes and bumps libraries etc, it would be useful to know if
> > running a statically linked jvm will work on -current.
>
> This sounds like a go
On Thu, 23 Oct 2003, othermark wrote:
> these are fibre 1000 base sx connections. They don't attach correctly in
> the 5.0-release kernel as well (with the exact same error), but it does
> continue to boot correctly. These are hardwired into the bus, and I'm
> unable to disable them. :(
Onboard
Tinderbox
> /vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libfetch/common.c:60:
> error: initializer element is not constant
Under 5.1-CURRENT or i386 cvsuped on 10/23 I get the same failure, with
the additional error message
/usr/src/lib/libfetch/common.c:58: error: 'EAINON
Hi, thanks for taking a gander at my problem. The original panic
can be reviewed here:
http://article.gmane.org/gmane.os.freebsd.current/31913
now to answer your query...
Doug Rabson wrote:
> On Thu, 2003-10-23 at 22:45, othermark wrote:
>> I wrote:
>> > I will try seeing how far I can go up the
Hello,
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x60
fault core = supervisor read, page not present
instruction pointer = 0x8:0xc04d6d42
stack pointer = 0x10:0xde5b7624
frame pointer = 0x10:0xde5b764c
code segment= ba
On Fri, Oct 24, 2003 at 01:30:18PM +0200, Poul-Henning Kamp wrote:
> You may want to try this patch, Kirk sent it to me in response to a
> case where my NFS-server hung during snapshot processing.
>
> I have only just managed to put it on my server so I don't know if
> it solves the problem or not
In message <[EMAIL PROTECTED]>, Marc Olzheim writes:
>On Thu, Oct 23, 2003 at 10:53:29PM +0200, Soren Schmidt wrote:
>> Yes, NFS is locking up here as well between current machines thats been
>> updated in the last 24 hours...
>
>In kernels since about october 17th, until upto an hour ago, it's st
On Thu, Oct 23, 2003 at 10:53:29PM +0200, Soren Schmidt wrote:
> Yes, NFS is locking up here as well between current machines thats been
> updated in the last 24 hours...
In kernels since about october 17th, until upto an hour ago, it's still
reproducable here as well..
Zlo
_
At Thu, 23 Oct 2003 20:00:38 -0400,
James Tanis wrote:
>
> Attempted this, first did a deinstall of XFree86-Server and then
> built/installed XFree86-Server-snap. It built and installed perfectly fine,
> from what I can see it runs fine too.. but I get the same error. You
> weren't wro
I was playing a bit with USB (had a umass device attached)
and while still being unsure whether I had device umass in kernel
I typed the line
camcontrol rescan all
and that gave:
panic:vmapbuf
db>
--
Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de
__
On Fri, Oct 24, 2003 at 09:31:52AM +0200, Hans Lambermont wrote:
> I also added to /boot/device.hints :
> hint.fxp.0.prefer_iomap="1"
this never helped for me to fix the fxp timeout problem. it is necessary
for me to the get the pccard buses to work though.
> Tobias Roth wrote on 18 Jul 2003 abo
On Thu, 2003-10-23 at 22:45, othermark wrote:
> I wrote:
> > I will try seeing how far I can go up the list of snapshots until I
> > encounter the first boot -s panic.
>
> Well I walked up the available snapshots and the first panic occurs with
> the snapshot from the 17th of October. Reviewing t
On Fri, 24 Oct 2003 00:40:24 -0300
Roberto de Iriarte <[EMAIL PROTECTED]> wrote:
> a) Problem
> Right upon installing mozilla 1.5 from ports, i installed
> flashpluginwrapper-20031006, and found out that mozilla would fail to
> exit eating up CPU as if stuck in an infinite loop (Usage per top went
Hello.
It was reported already?
1st 0xc0c1ede0 vm object (vm object) @ /usr/src/sys/vm/swap_pager.c:1134
2nd 0xc0c2f110 system map (system map) @ /usr/src/sys/vm/vm_kern.c:328
Stack backtrace:
backtrace(c05cce28,c0c2f110,c05d72b0,c05d72b0,c05d7147) at backtrace+0x17
witness_lock(c0c2f110,8,c05d
Hi list,
My fxp0: device timeout problems are back (and I found a workaround, but
the matter still deserves attention for 5.2, hence this email)
Some info. This is an IBM T30 with :
fxp0: port 0x8000-0x803f mem
0xd020-0xd0200fff irq 11 at device 8.0 on pci2
I also added to /boot/device.hint
On Friday 24 October 2003 02:00, James Tanis wrote:
> From the log file:
> (II) Primary Device is:
> (--) Assigning device section with no busID to primary device
> (WW) RADEON: No matching Device section for instance (BusID
> PCI:1:0:1) found (EE) No devices detected.
>
> I did not att
51 matches
Mail list logo
