It seems Nate Lawson wrote:
> > > * Panic occurs after ATAFD fails to probe. Last event: 2003/10/6
> > > I have no ATAFD device on my system and normally no messages are printed
> > > about it on boot. However, periodically ATAFD will print a bunch of
> > > messages on console about failing to pr
TB --- 2003-10-25 08:01:33 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-10-25 08:01:33 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-10-25 08:01:33 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs
TB --- 2003-10-25 08:35:34 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-10-25 08:35:34 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-10-25 08:35:34 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64
TB --- /usr/bin/cvs -f -R -q
Hiya
> I'm running:
>
> pcm0: mem 0xfea0-0xfeaf,0xfe00-0xfe3f irq
> 9 at device 8.1 on pci0
> pcm0:
>
> on a Sony VAIO ...
Just wondering: had you applied the IRQ rerouting patch to get your sound
working? I got caught out by this when I upgraded my VAIO and ended up
getting m
Howdy,
For some reason, GBDE does not want to initialize the g partition om a
disk. Am I overlooking something or is this an undocumented feature?
grizzly# ls -l /dev/ad0s2g
crw-r- 1 root operator4, 19 Oct 22 09:30 /dev/ad0s2g
grizzly# gbde init /dev/ad0s2g -i -L /etc/gbde/ad0s1g
gbde:
In message <[EMAIL PROTECTED]>, Erwin Lansing writes:
>For some reason, GBDE does not want to initialize the g partition om a
>disk. Am I overlooking something or is this an undocumented feature?
>
>grizzly# ls -l /dev/ad0s2g
>crw-r- 1 root operator4, 19 Oct 22 09:30 /dev/ad0s2g
>grizzl
Hi,
some severe problems with a brand new DELL Latitude D600 laptop.
It has a Broadcom BCM5702 Gigabit Ethernet, ASIC rev. 0x1002,
on board.
On the 1st boot FreeBSD 5.1-current from a self made CD-ROM
(-current from yesterday) paniced during 1st boot from CD (just
before installation). It had a F
Hello.
Already reported?
~~~cut~~~
lock order reversal
1st 0xc3931818 vm object (vm object) @ /usr/src/sys/vm/vm_object.c:1512
2nd 0xc102f110 system map (system map) @ /usr/src/sys/vm/vm_kern.c:328
Stack backtrace:
backtrace(c08727f8,c102f110,c088694e,c088694e,c08867e9) at backtrace+0x17
witnes
On Friday 24 October 2003 22:47, Eric Anholt wrote:
> 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 0
On Sat, Oct 25, 2003 at 02:07:34PM +0200, Poul-Henning Kamp wrote:
>
> Can you check with diskinfo that the partition has the right size ?
>
grizzly# diskinfo -v /dev/ad0s2g
/dev/ad0s2g
512 # sectorsize
55658270720 # mediasize in bytes
108707560 # med
Hi there,
I have a D-Link g650 cardbus atheros wireless device and I have been getting serious
problems with it.
It attaches fine, then I configure it, it connects to the USR8054 AP, or in fact any
AP I have tested
it against, then soon after it stops working. Sometimes after transferring data
Since the drm updates to 5-CURRENT I'm getting multiple instances of the
following at boot (and not trap 12 :-) ):
from dmesg
drm0: port 0xc800-0xc8ff mem 0xff48-0xff4f,
0xe80-0xefff irq 11 at device 0.0 on pci1
info: [drm] AGP at 0xf800 64MB
info: [drm] Initalized ra
Hi,
I followed the meaningful instructions from
http://www.shadowcom.net/freebsd-oracle9i/
All worked well until the installer tried to launch netca. The netca GUI
never appeared.
Then OUI tried to launch dbca. A blank windows appeared, and a few
second later the system rebooted.
I uninstalled t
actually, just upgraded the machine and everything appears fine now ...
what IRQ rerouting patch? )
On Sat, 25 Oct 2003 [EMAIL PROTECTED] wrote:
> Hiya
>
>
> > I'm running:
> >
> > pcm0: mem 0xfea0-0xfeaf,0xfe00-0xfe3f irq
> > 9 at device 8.1 on pci0
> > pcm0:
> >
> > on a Sony
In message <[EMAIL PROTECTED]>, Erwin Lansing writes:
>
>--BXVAT5kNtrzKuDFl
>Content-Type: text/plain; charset=us-ascii
>Content-Disposition: inline
>Content-Transfer-Encoding: quoted-printable
>
>On Sat, Oct 25, 2003 at 02:07:34PM +0200, Poul-Henning Kamp wrote:
>>=20
>> Can you check with diskinf
TB --- 2003-10-25 16:00:01 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-10-25 16:00:01 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-10-25 16:00:01 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/
Subject: Re: fresh -current trap,
On Sat, 25 Oct 2003 04:50:30 +0900, Shin-ichi Yoshimoto wrote:
> I'm using a radeon DRM module.
Now DRM work fine. But some kernel messages found my log like this.
kernel: error: [drm:pid38523:radeon_ioctl] *ERROR* can't find
authenticator
Is this OK ?
--
Shi
My /etc/make.conf is empty.
c++ -pg -O -pipe -mcpu=pentiumpro -DIN_GLIBCPP_V3 -DHAVE_CONFIG_H
-I/home/src/gnu/lib/libstdc++
-I/home/src/gnu/lib/libstdc++/../../../contrib/libstdc++/libsupc++
-I/home/src/gnu/lib/libstdc++/../../../contrib/gcc -fno-implicit-templates
-ffunction-sections -fdata-s
On Sat, Oct 25, 2003 at 02:18:41PM +0200, [EMAIL PROTECTED] wrote:
> Hello.
>
> Already reported?
Yeah, about once a day ;-)
~~~cut~~~
> panic: Hey partner, hold on there!
>
> syncing disks, buffers remaining... panic: sleeping thread (pid 25) owns
> a mutex
> Uptime: 50m30s
> panic: sleeping
TB --- 2003-10-25 18:23:28 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-10-25 18:23:28 - starting CURRENT tinderbox run for i386/i386
TB --- 2003-10-25 18:23:28 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/i386
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs
Hey Guys,
i got this panic on doing "shutdown -r now".
Fatal trap 12: page fault while in kernel mode
cpuid = 1; lapic.id = 0100
fault virtual address = 0xdeadc0de
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0521678
stack pointer =
I should have added that this is a kernel todays sources on an smp system.
FreeBSD bender 5.1-CURRENT FreeBSD 5.1-CURRENT #73: Sat Oct 25
20:30:56 CEST 2003 [EMAIL PROTECTED]:/space/obj/space/src/sys/BENDER i386
Florian C. Smeets wrote:
Hey Guys,
i got this panic on doing "shutdown -r now"
TB --- 2003-10-25 19:36:41 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-10-25 19:36:41 - starting CURRENT tinderbox run for i386/pc98
TB --- 2003-10-25 19:36:41 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/pc98
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs
TB --- 2003-10-25 20:47:09 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-10-25 20:47:09 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-10-25 20:47:09 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs
I'm having a problem on my IBM Thinkpad X31.
The laptop lid, when shut freezes everything.
The same thing goes for the standby and power buttons.
Even pressing the little flashligt button freezes everything.
Standby and Hibernate don't work in the least bit.
I can't shut down properly.
I solved th
I'm having a problem on my IBM Thinkpad X31.
The laptop lid, when shut freezes everything.
The same thing goes for the standby and power buttons.
Even pressing the little flashligt button freezes everything.
Standby and Hibernate don't work in the least bit.
I can't shut down properly.
I solved th
TB --- 2003-10-25 22:08:45 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-10-25 22:08:45 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-10-25 22:08:45 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64
TB --- /usr/bin/cvs -f -R -q
Saturday, October 25, 2003, 7:51:58 AM, you wrote:
>>> * Resume fails, hanging with drive light on. Last event: 2003/10/2
>>> Appears to be a lost interrupt during reset.
>>
>> I've just committed some changes that makes suspend/resume work just
>> fine on the notebooks I have access to.
>
> This
Shin-ichi Yoshimoto wrote:
Now DRM work fine. But some kernel messages found my log like this.
kernel: error: [drm:pid38523:radeon_ioctl] *ERROR* can't find
authenticator
Is this OK ?
DRM is working again for me as well, but I'm also seeing a lot of these
error messages with my Radeon 9000 Mobi
Janet Sullivan
>
> Shin-ichi Yoshimoto wrote:
> > Now DRM work fine. But some kernel messages found my log like this.
> >
> > kernel: error: [drm:pid38523:radeon_ioctl] *ERROR* can't find
> > authenticator
>
> DRM is working again for me as well, but I'm also seeing a lot of these
> error mess
TB --- 2003-10-26 04:00:01 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-10-26 04:00:01 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-10-26 04:00:01 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/
31 matches
Mail list logo