Hi,
Just checked out r243529, this only happens when the kernel is compiled
by clang, and only on i386, either recompiling the kernel with gcc or
booting from a UFS root works fine. Is it a known problem?
Thanks,
--
WARNING:
On Mon, Nov 26, 2012 at 06:31:34AM -0800, sig6247 wrote:
Hi,
Just checked out r243529, this only happens when the kernel is compiled
by clang, and only on i386, either recompiling the kernel with gcc or
booting from a UFS root works fine. Is it a known problem?
It looks like that clang
On Mon, 26 Nov 2012, Konstantin Belousov wrote:
On Mon, Nov 26, 2012 at 06:31:34AM -0800, sig6247 wrote:
Just checked out r243529, this only happens when the kernel is compiled
by clang, and only on i386, either recompiling the kernel with gcc or
booting from a UFS root works fine. Is it a
I upgraded my kernel yesterday, after testing alc@'s patch for mmu_oea
(PowerPC 32-bit, AIM), and now I'm seeing the kernel panic in the subject.
Unfortunately, I didn't keep my knonw-good working kernel from prior to
testing alc@'s patch, so the most recent kernel I have that works is from
over
On 06/26/12 22:29, Kenneth D. Merry wrote:
On Tue, Jun 26, 2012 at 19:41:07 -0400, Benjamin Kaduk wrote:
On Tue, 26 Jun 2012, Michael Butler wrote:
As follows, in g_disk_providergone, a NULL pointer reference?:
g_disk_providergone() is new in r237518 (by ken); ken cc'd.
Can you try the
On Wed, Jun 27, 2012 at 10:22:59 -0400, Michael Butler wrote:
On 06/26/12 22:29, Kenneth D. Merry wrote:
On Tue, Jun 26, 2012 at 19:41:07 -0400, Benjamin Kaduk wrote:
On Tue, 26 Jun 2012, Michael Butler wrote:
As follows, in g_disk_providergone, a NULL pointer reference?:
As follows, in g_disk_providergone, a NULL pointer reference?:
imb@toshi:/home/imb sudo less /var/crash/core.txt.4
toshi.auburn.protected-networks.net dumped core - see /var/crash/vmcore.4
Tue Jun 26 08:59:01 EDT 2012
FreeBSD toshi.auburn.protected-networks.net 10.0-CURRENT FreeBSD
10.0-CURRENT
On Tue, 26 Jun 2012, Michael Butler wrote:
As follows, in g_disk_providergone, a NULL pointer reference?:
g_disk_providergone() is new in r237518 (by ken); ken cc'd.
-Ben Kaduk
imb@toshi:/home/imb sudo less /var/crash/core.txt.4
toshi.auburn.protected-networks.net dumped core - see
On Tue, Jun 26, 2012 at 19:41:07 -0400, Benjamin Kaduk wrote:
On Tue, 26 Jun 2012, Michael Butler wrote:
As follows, in g_disk_providergone, a NULL pointer reference?:
g_disk_providergone() is new in r237518 (by ken); ken cc'd.
Can you try the attached patch to sys/geom/geom_disk.c?
Also,
On Tuesday, September 27, 2011 1:46:19 am Eitan Adler wrote:
My computer recently paniced and broke into ddb after spamming my
console with swap zone exhausted, increase kern.maxswzone
Immediately prior to the panic X was killed and I was able to switch
to vty1 and log in as root (I planned on
My computer recently paniced and broke into ddb after spamming my
console with swap zone exhausted, increase kern.maxswzone
Immediately prior to the panic X was killed and I was able to switch
to vty1 and log in as root (I planned on killing runaway programs)
I called doadump and have the saved
I forgot to add. Following
http://lists.freebsd.org/pipermail/freebsd-current/2011-September/027059.html
I disabled vboxdrv and cuse4bsd modules.
On Sun, Sep 18, 2011 at 12:44 PM, Piotr Kubaj pku...@gmail.com wrote:
I upgraded on 16th September to the newest snapshot. Everything
compiled well,
1. It's in the dump file.
2. In BEASTIE.
3. As I wrote before, 9.0-BETA1, but I had used this kernel with 8.2-RELEASE
and 8.2-STABLE (only did slight modifications for 9.0).
4. I'm not really into it, what exactly do you mean?
BEASTIE
Description: Binary data
dump
Description: Binary data
On 2 September 2011 15:41, Piotr Kubaj freebsd.current.l...@gmail.com wrote:
1. It's in the dump file.
2. In BEASTIE.
3. As I wrote before, 9.0-BETA1, but I had used this kernel with 8.2-RELEASE
and 8.2-STABLE (only did slight modifications for 9.0).
4. I'm not really into it, what exactly do
On Fri, Sep 2, 2011 at 1:49 PM, Sergey Kandaurov pluk...@gmail.com wrote:
On 2 September 2011 15:41, Piotr Kubaj freebsd.current.l...@gmail.com
wrote:
1. It's in the dump file.
2. In BEASTIE.
3. As I wrote before, 9.0-BETA1, but I had used this kernel with
8.2-RELEASE
and 8.2-STABLE
] On Behalf Of
Adrian Chadd
Sent: Wednesday, August 31, 2011 6:26 PM
To: Mike Tancsa
Cc: Edgar Martinez; freebsd-current@freebsd.org
Subject: Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on
ALIX)
This the key here:
atrtc0: at port 0x70 irq 8 on isa0
Event timer RTC frequency
found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on
ALIX)
This the key here:
atrtc0: at port 0x70 irq 8 on isa0
Event timer RTC frequency 32768 Hz quality 0
Edgar, are you missing a device entry for the RTC?
Do you have device.hints in /boot ?
GENERIC.hints:hint.atrtc.0.at=isa
I've upgraded today to beta 2 (with the newest sources atm). The procedure was
as described in the handbook: make buildworld -j3; make buildkernel -j3
KERNCONF=MYKERNEL; make installkernel KERNCONF=MYKERNEL (the kernel I used was
the same as for beta 1, for which it worked flawlessly); reboot
On Thu, Sep 1, 2011 at 4:06 PM, Piotr Kubaj
freebsd.current.l...@gmail.com wrote:
I've upgraded today to beta 2 (with the newest sources atm). The procedure
was as described in the handbook: make buildworld -j3; make buildkernel -j3
KERNCONF=MYKERNEL; make installkernel KERNCONF=MYKERNEL (the
GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2011 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 is a registered
Just to clarify for Edgar,
His 9.0 build isn't finding any valid timers; hence why the thing
panics upon boot.
Since I've got a few Alix boards I'd like to use for 11n testing, i'd
like to know how to make this work.
Does anyone know the relevant magic to see which timers are available,
and
On 8/31/2011 12:27 PM, Adrian Chadd wrote:
Just to clarify for Edgar,
His 9.0 build isn't finding any valid timers; hence why the thing
panics upon boot.
Since I've got a few Alix boards I'd like to use for 11n testing, i'd
like to know how to make this work.
Does anyone know the
: Mike Tancsa [mailto:m...@sentex.net]
Sent: Wednesday, August 31, 2011 10:53 AM
To: Adrian Chadd
Cc: Edgar Martinez; freebsd-current@freebsd.org
Subject: Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on
ALIX)
On 8/31/2011 12:27 PM, Adrian Chadd wrote:
Just to clarify
=
kdb_why
Is still the result..
-Original Message-
From: Mike Tancsa [mailto:m...@sentex.net]
Sent: Wednesday, August 31, 2011 10:53 AM
To: Adrian Chadd
Cc: Edgar Martinez; freebsd-current@freebsd.org
Subject: Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic
31, 2011 12:57 PM
To: Edgar Martinez
Cc: Adrian Chadd; freebsd-current@freebsd.org
Subject: Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic
on ALIX)
On 8/31/2011 3:25 PM, Edgar Martinez wrote:
Nope..I rebuilt with both options..and just one at a time..
Strange
: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on
ALIX)
Nope..I rebuilt with both options..and just one at a time..
panic: No usable event timer found!
KDB: stack backtrace:
X_db_sym_numargs(c0758a2d) at 0xc0471f85 = X_db_sym_numargs+0x135
kdb_backtrace(c2820d38,1,fff,c2820d40
timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on
ALIX)
On 8/31/2011 3:25 PM, Edgar Martinez wrote:
Nope..I rebuilt with both options..and just one at a time..
Strange,
My kernel is not so different from GENERIC. I added it to the bottom of
http://www.tancsa.com/beta2.html
Perhaps
Subject: Re: No valid timers found on ALIX (was Re: 9.0-BETA2 - Kernel Panic on
ALIX)
On 8/31/2011 3:57 PM, Edgar Martinez wrote:
Latest ALIX firmware? .99h?
I'm using the below board...
http://pcengines.ch/alix2d2.htm
Thats pretty well the same board as me, except I dont have the 2
mini-pci
This the key here:
atrtc0: at port 0x70 irq 8 on isa0
Event timer RTC frequency 32768 Hz quality 0
Edgar, are you missing a device entry for the RTC?
Do you have device.hints in /boot ?
GENERIC.hints:hint.atrtc.0.at=isa
GENERIC.hints:hint.atrtc.0.port=0x70
GENERIC.hints:hint.atrtc.0.irq=8
And
Cc: freebsd-current@freebsd.org
Subject: RE: Kernel panic rtfree 2
Hi,
Please re-enable RADIX_MPATH option in your kernel config file, and
try the following patch:
http://people.freebsd.org/~qingli/radix_mpath.c.diff
and let me know if it works out for you.
I performed
On Sat, 20 Aug 2011 19:35:16 +0100, Alvaro Castillo wrote:
VirtualBox Version: 4.0.12_OSE r72916
uname -a: FreeBSD shuttle0.lan 9.0-BETA1 FreeBSD 9.0-BETA1 #1: Wed Aug
17 01:21:47 WEST 2011
net...@shuttle0.lan:/usr/obj/usr/src/sys/GALILEO amd64
The kernel panic is occurred when I start
/GALILEO amd64
The kernel panic is occurred when I start a virtual machine with boot
from CD/DVD burner/reader device.
With or without passthrough.
Kernel panic http://pastie.org/private/0nxanttdmtc9zvtllg0rw
atapicam is loaded and hald is working.
I've added the bugreport
VirtualBox Version: 4.0.12_OSE r72916
uname -a: FreeBSD shuttle0.lan 9.0-BETA1 FreeBSD 9.0-BETA1 #1: Wed Aug
17 01:21:47 WEST 2011
net...@shuttle0.lan:/usr/obj/usr/src/sys/GALILEO amd64
The kernel panic is occurred when I start a virtual machine with boot
from CD/DVD burner/reader device
Hi,
Could you please let me know if the patch fixes your crash problem ?
Thanks,
--Qing
-Original Message-
From: Li, Qing
Sent: Friday, August 12, 2011 6:29 PM
To: Li, Qing; Luiz Otavio O Souza; Andrey Smagin
Cc: freebsd-current@freebsd.org
Subject: RE: Kernel panic rtfree 2
uname -a: FreeBSD shuttle0.lan 9.0-BETA1 FreeBSD 9.0-BETA1 #2: Mon Aug
8 17:05:59 WEST 2011
net...@shuttle0.lan:/usr/obj/usr/src/sys/HYDROGEN amd64
kernel panic:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x
fault code
On Sun Aug 14 11, Alvaro Castillo wrote:
uname -a: FreeBSD shuttle0.lan 9.0-BETA1 FreeBSD 9.0-BETA1 #2: Mon Aug
8 17:05:59 WEST 2011
net...@shuttle0.lan:/usr/obj/usr/src/sys/HYDROGEN amd64
kernel panic:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault
On Sun, 14 Aug 2011 07:07:57 +0100
Alvaro Castillo gobl...@gmail.com wrote:
uname -a: FreeBSD shuttle0.lan 9.0-BETA1 FreeBSD 9.0-BETA1 #2: Mon Aug
8 17:05:59 WEST 2011
net...@shuttle0.lan:/usr/obj/usr/src/sys/HYDROGEN amd64
kernel panic:
Fatal trap 12: page fault while in kernel mode
Before all upgrade system never crash.
After upgrade system month ago happens every day Kernel panic rtfree 2 at
rtfree
route_output
sosend_generic
soo_write
dofilewrite
kernwrite
write
syscallenter
syscall
Xfast_syscall
Now I upgraded to FreeBSD 9.0-BETA1 #32 r224760M and problem exist
It would help to know your configuration. Also, can you furnish us with a core?
On Fri, Aug 12, 2011 at 9:02 AM, Andrey Smagin samsp...@mail.ru wrote:
Before all upgrade system never crash.
After upgrade system month ago happens every day Kernel panic rtfree 2 at
rtfree
route_output
options IPFIREWALL_FORWARD
options IPFIREWALL_NAT
options ROUTETABLES=16
options DEVICE_POLLING
On Fri, Aug 12, 2011 at 9:02 AM, Andrey Smagin samsp...@mail.ru wrote:
Before all upgrade system never crash.
After upgrade system month ago happens every day Kernel panic rtfree 2 at
rtfree
On Aug 12, 2011, at 11:32 AM, Andrey Smagin wrote:
12 августа 2011, 16:31 от Kip Macy kip.m...@gmail.com:
It would help to know your configuration. Also, can you furnish us with a
core?
This is my kernel conf:
cpu HAMMER
ident SAM
[snip]
options RADIX_MPATH
Can you try it without
12 августа 2011, 19:05 от Luiz Otavio O Souza lists...@gmail.com:
On Aug 12, 2011, at 11:32 AM, Andrey Smagin wrote:
12 августа 2011, 16:31 от Kip Macy kip.m...@gmail.com:
It would help to know your configuration. Also, can you furnish us with a
core?
This is my kernel conf:
cpu
AM
To: Andrey Smagin
Cc: freebsd-current@freebsd.org
Subject: Re: Kernel panic rtfree 2
On Aug 12, 2011, at 11:32 AM, Andrey Smagin wrote:
12 августа 2011, 16:31 от Kip Macy kip.m...@gmail.com:
It would help to know your configuration. Also, can you furnish us
with a core?
This is my
Hi,
Please re-enable RADIX_MPATH option in your kernel config file, and
try the following patch:
http://people.freebsd.org/~qingli/radix_mpath.c.diff
and let me know if it works out for you.
I performed very limited testing.
Thanks,
--Qing
Please help! Can't load system after update on r224468
mount partition is UFS, no startup settings changed,
no CONF file changed.
make buildworld buildkernel installworld installkernel
now I loaded old r221725.
___
freebsd-current@freebsd.org mailing
Sorry for panic. I have another HDD with partition s1a, after update, HDD
renumerated.
vfs.root.mountfrom in loader.conf solved my problem
28 июля 2011, 01:02 от Andrey Smagin samsp...@mail.ru:
Please help! Can't load system after update on r224468
mount partition is UFS, no startup settings
that time my router
issues kernel panic once or twice a day with Fatal trap 12: page fault
while in kernel mode and (nfe0 taskq) is the current process.
Updating to the latest stable doesn't help. I don’t know what to do next,
any help would be much appreciated. Below is kgdb backtrace, dmesg
Booting from FreeBSD-9.0-CURRENT-201105-amd64-memstick
the kernel panics:
panic: m_getzone: m_getjcl: invalid cluster type
http://www.flickr.com/photos/opensolaris/5818432532/in/photostream
The hardware is:
http://www.supermicro.com/products/motherboard/QPI/5500/X8DTL-3F.cfm
The cpu's are
On Fri, June 10, 2011 11:22 am, Kim Culhan wrote:
Booting from FreeBSD-9.0-CURRENT-201105-amd64-memstick
the kernel panics:
panic: m_getzone: m_getjcl: invalid cluster type
Found a ps2 keyboard works in the debugger (not usb) and backtrace is here:
This recent commit changed the way that the value for size being
passed to m_getjcl is initialized. Not seeing any obvious bugs, and
not having any additional context I would guess that that you're
receiving an interrupt before adapter-rx_mbuf_sz is set. I trust jfv@
to look in to this shortly.
Interrupts are not enabled til after that is set, so I don't think this
theory
works, sorry.
Jack
On Fri, Jun 10, 2011 at 12:48 PM, K. Macy km...@freebsd.org wrote:
This recent commit changed the way that the value for size being
passed to m_getjcl is initialized. Not seeing any obvious
On 10 June 2011 19:48, K. Macy km...@freebsd.org wrote:
This recent commit changed the way that the value for size being
passed to m_getjcl is initialized. Not seeing any obvious bugs, and
not having any additional context I would guess that that you're
receiving an interrupt before
Hi all,
The following script seems to cause a guaranteed kernel panic on 8.1-R,
8.2-R and 8-STABLE as of today (2011-03-16), with both ZFS v14/15, and
v28 on 8.2-R with mm@ patches from 2011-03. I suspect it may also affect
9-CURRENT but have not tested this yet.
#!/usr/local/bin/bash
export
On Fri, Oct 01, 2010 at 11:06:58PM +, Bjoern A. Zeeb wrote:
On Fri, 1 Oct 2010, Andrey Chernov wrote:
Pinging nonexistent IPv6 adress withing the same prefixlen 64 (i.e.
nonexistent neighbor) immediately cause kernel panic in nd6_output_lle()
See
http://img837.imageshack.us/img837
Pinging nonexistent IPv6 adress withing the same prefixlen 64 (i.e.
nonexistent neighbor) immediately cause kernel panic in nd6_output_lle()
See
http://img837.imageshack.us/img837/7496/01102010f.jpg
Please fix.
--
http://ache.pp.ru/
___
freebsd
On Fri, 1 Oct 2010, Andrey Chernov wrote:
Pinging nonexistent IPv6 adress withing the same prefixlen 64 (i.e.
nonexistent neighbor) immediately cause kernel panic in nd6_output_lle()
See
http://img837.imageshack.us/img837/7496/01102010f.jpg
want to try the patch from kern/148857?
/bz
Installed a kernel based on yesterday's src/ tree.
The kernel panicked and the generated core seems
to be corrupt. Is there a known issue with getting
core dumps on x86_64 freebsd? The top of the
core.txt.0 file shows
troutmask.apl.washington.edu dumped core - see /usr/tmp/vmcore.0
Fri Aug
Hello Andriy!
On Aug 18, 2010, at 7:30 PM, Andriy Gapon wrote:
on 13/08/2010 00:45 Alexey Tarasov said the following:
Fatal trap 1: privileged instruction fault while in kernel mode
cpuid = 1; apic id = 01
instruction pointer = 0x20:0xff8040d2cc83
stack pointer =
on 13/08/2010 00:45 Alexey Tarasov said the following:
Fatal trap 1: privileged instruction fault while in kernel mode
cpuid = 1; apic id = 01
instruction pointer = 0x20:0xff8040d2cc83
stack pointer = 0x28:0xff8040d2ca80
frame pointer = 0x28:0xff0060c0b740
Hello.
I have a couple of Supermicro servers which got the similar kernel panic with
all FreeBSD versions I tried since 6.4.
Now I want to investigate into the problem.
The servers get into panic with similar workload: file server with a lot of
files and connections. Web server software
Hi,
K3b is causing FreeBSD to panic with a recent amd64 custom kernel from
current. The kernel is from ~ 1 July) and does include the changes from
r209590. Some of the changes I made include:
options ATA_CAM
and I have one DVD-RW installed:
# dmesg | grep 'cd[0-9]'
cd0 at ata0 bus
Bernd Walter [EMAIL PROTECTED] wrote:
On Fri, Nov 21, 2003 at 12:35:50PM -0500, Brian F. Feldman wrote:
Doug White [EMAIL PROTECTED] wrote:
The OHCI driver is largely synced with NetBSD so you might see if they
have the same bug.
I'll look around for a bootable NetBSD CD.
NetBSD
On Sat, Nov 22, 2003 at 08:08:29AM -0500, Brian F. Feldman wrote:
Found it!!! Definitely a problem created then...
--- ohci.c 12 Nov 2003 01:40:11 - 1.138
+++ ohci.c 22 Nov 2003 03:28:42 -
@@ -569,7 +569,7 @@
cur-td.td_cbp = htole32(dataphys);
On Sat, Nov 22, 2003 at 08:08:29AM -0500, Brian F. Feldman wrote:
We never did any page crossing on ohci/ehci bevor the newbus change
took place.
Found it!!! Definitely a problem created then...
--- ohci.c 12 Nov 2003 01:40:11 - 1.138
+++ ohci.c 22 Nov 2003
The OHCI driver is largely synced with NetBSD so you might see if they
have the same bug.
This might be the underlying wierdness we were seeing in gtetlow's
microdrive with transfers over 8k. The one-page-crossing ohci limitation
is really annoying.
On Thu, 20 Nov 2003, Brian F. Feldman wrote:
Doug White [EMAIL PROTECTED] wrote:
The OHCI driver is largely synced with NetBSD so you might see if they
have the same bug.
I'll look around for a bootable NetBSD CD.
This might be the underlying wierdness we were seeing in gtetlow's
microdrive with transfers over 8k. The
Whoops. http://damien.bergamini.free.fr/ueagle/download.html.
BMS
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Fri, Nov 21, 2003 at 09:11:33AM -0800, Doug White wrote:
The OHCI driver is largely synced with NetBSD so you might see if they
have the same bug.
This might be the underlying wierdness we were seeing in gtetlow's
microdrive with transfers over 8k. The one-page-crossing ohci limitation
On Fri, Nov 21, 2003 at 12:35:50PM -0500, Brian F. Feldman wrote:
Doug White [EMAIL PROTECTED] wrote:
The OHCI driver is largely synced with NetBSD so you might see if they
have the same bug.
I'll look around for a bootable NetBSD CD.
NetBSD is different in that point.
This might be
Bernd Walter [EMAIL PROTECTED] wrote:
On Fri, Nov 21, 2003 at 12:35:50PM -0500, Brian F. Feldman wrote:
Doug White [EMAIL PROTECTED] wrote:
The OHCI driver is largely synced with NetBSD so you might see if they
have the same bug.
I'll look around for a bootable NetBSD CD.
NetBSD
Brian F. Feldman [EMAIL PROTECTED] writes:
Jeez, it's been broken a year and it's almost 5.2-RELEASE now. Does anyone
have ANY leads on these problems? I know precisely nothing about how my USB
hardware is supposed to work, but this OHCI+EHCI stuff definitely doesn't,
and it's really not
In message [EMAIL PROTECTED], Brian F. Feldman
writes:
Jeez, it's been broken a year and it's almost 5.2-RELEASE now. Does anyone
have ANY leads on these problems? I know precisely nothing about how my USB
hardware is supposed to work, but this OHCI+EHCI stuff definitely doesn't,
and it's
Jeez, it's been broken a year and it's almost 5.2-RELEASE now.
See for example the page for the FreeBSD eagle driver:
http://damien.bergamini.free.fr/ueagle/
end notably the OHCI patches in
http://damien.bergamini.free.fr/ueagle/download.html
At least for the eagle USB ADSL modem, these patches
Alexander Leidinger [EMAIL PROTECTED] writes:
I have no problem using my printer:
[...]
ulpt0: Hewlett-Packard DeskJet 895C, rev 1.00/1.00, addr 4, iclass 7/1
ulpt0: using uni-directional mode
Sure, I can do that:
ulpt0: Hewlett-Packard officejet d series, rev 1.10/1.00, addr 3, iclass 7/1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 20 Nov 2003 10:20, Dag-Erling Smørgrav wrote:
Sure, I can do that:
ulpt0: Hewlett-Packard officejet d series, rev 1.10/1.00, addr 3, iclass
7/1 ulpt0: using bi-directional mode
but it still won't print. Sometimes it works (albeit
Mark Dixon [EMAIL PROTECTED] writes:
When it works, is that when you have been using it in another operating
system, and then reboot into FreeBSD and try it?
I don't think so.
BTW, I just reinstalled cups to give the printer another try, and it
now seems to work in -CURRENT (knock on wood).
On Thu, Nov 20, 2003 at 11:20:18AM +0100, Dag-Erling Smørgrav wrote:
Alexander Leidinger [EMAIL PROTECTED] writes:
I have no problem using my printer:
[...]
ulpt0: Hewlett-Packard DeskJet 895C, rev 1.00/1.00, addr 4, iclass 7/1
ulpt0: using uni-directional mode
Sure, I can do that:
Thanks for the patches to try! They unfortunately didn't fix the crash I
have, but I found out why it's occurring.
See ohci.c:1389:
if (std-td.td_cbp != 0)
len -= le32toh(std-td.td_be) -
le32toh(std-td.td_cbp) + 1;
In one
Brian F. Feldman [EMAIL PROTECTED] wrote:
Thanks for the patches to try! They unfortunately didn't fix the crash I
have, but I found out why it's occurring.
See ohci.c:1389:
if (std-td.td_cbp != 0)
len -= le32toh(std-td.td_be) -
Nate Lawson wrote:
On Tue, 18 Nov 2003, Eric Anderson wrote:
Nate Lawson wrote:
cvsup to -current as of today would be a good first start. The code was
committed Nov 15. Then boot with acpi enabled and post the output of
sysctl hw.acpi.cpu. You can try different levels by doing sysctl
Josef Karthauser [EMAIL PROTECTED] wrote:
On Sun, Nov 17, 2002 at 01:18:00PM -0500, Brian F. Feldman wrote:
ohci_alloc_std_chain+0xf5 (calling a DMAADDR() function, I believe)
ohci_device_bulk_start+0x0d
ohci_device_bulk_transfer+0x27
usbd_transfer+0xc0
umass_setup_transfer+0x4f
On Tuesday 18 November 2003 18:58, you wrote:
On Tue, 18 Nov 2003, Harald Schmalzbauer wrote:
On Tuesday 18 November 2003 03:37, you wrote:
Sorry I wasn't more clear. I need you to print the contents like this:
print *cpu_cx_count
cpu_cx_count 1
cpu_cx_lowest 0
cpu_idle_hook
Harald Schmalzbauer wrote:
On Tuesday 18 November 2003 18:58, you wrote:
On Tue, 18 Nov 2003, Harald Schmalzbauer wrote:
On Tuesday 18 November 2003 03:37, you wrote:
Sorry I wasn't more clear. I need you to print the contents like this:
print *cpu_cx_count
cpu_cx_count
On Wednesday 19 November 2003 02:09, Eric Anderson wrote:
Harald Schmalzbauer wrote:
On Tuesday 18 November 2003 18:58, you wrote:
On Tue, 18 Nov 2003, Harald Schmalzbauer wrote:
On Tuesday 18 November 2003 03:37, you wrote:
Sorry I wasn't more clear. I need you to print the contents like
On Tue, 18 Nov 2003, Eric Anderson wrote:
And here is what you requested in your first patch:
cale:~ sysctl hw.acpi.cpu
hw.acpi.cpu.cx_supported: C1/0
hw.acpi.cpu.cx_lowest: 0
hw.acpi.cpu.cx_history: 0/0
Ok - what do I need to do to try this new acpi stuff out? I'm running
-current as
Nate Lawson wrote:
Ok - what do I need to do to try this new acpi stuff out? I'm running
-current as of Nov 14th, and I'd like to help debug/test this on my
notebook..
cvsup to -current as of today would be a good first start. The code was
committed Nov 15. Then boot with acpi enabled and
On Tue, 18 Nov 2003, Eric Anderson wrote:
Nate Lawson wrote:
cvsup to -current as of today would be a good first start. The code was
committed Nov 15. Then boot with acpi enabled and post the output of
sysctl hw.acpi.cpu. You can try different levels by doing sysctl
hw.acpi.cpu.cx_lowest=x
On Mon, 17 Nov 2003, Harald Schmalzbauer wrote:
On Sunday 16 November 2003 21:11, Nate Lawson wrote:
The panic you see is a result of the new acpi_cpu driver, not ULE. In any
case, it appears that acpi_cpu_idle is being called and trying to read one
of the processor control registers
On Monday 17 November 2003 18:45, Nate Lawson wrote:
On Mon, 17 Nov 2003, Harald Schmalzbauer wrote:
On Sunday 16 November 2003 21:11, Nate Lawson wrote:
The panic you see is a result of the new acpi_cpu driver, not ULE. In
any case, it appears that acpi_cpu_idle is being called and
On Sunday 16 November 2003 05:32, Harald Schmalzbauer wrote:
Hi,
I saw that something has changed on ULE and wanted to give it a try but
with sources from ~ So 16 Nov 2003 04:00 UTC I get the following kernel
panic just before disk/geom and after Timecounter TSC frequency
1095341787 Hz
The panic you see is a result of the new acpi_cpu driver, not ULE. In any
case, it appears that acpi_cpu_idle is being called and trying to read one
of the processor control registers before they are present. Please send
me privately the output of:
acpidump -t -d harald-MachineType.asl
As a
On Sunday 16 November 2003 21:11, Nate Lawson wrote:
The panic you see is a result of the new acpi_cpu driver, not ULE. In any
case, it appears that acpi_cpu_idle is being called and trying to read one
of the processor control registers before they are present. Please send
me privately the
Hi,
I saw that something has changed on ULE and wanted to give it a try but with
sources from ~ So 16 Nov 2003 04:00 UTC I get the following kernel panic just
before disk/geom and after Timecounter TSC frequency 1095341787 Hz quality
800:
Fatal trap 12 :page fault while in kernel mode
fault
with makeoptions debug but I don't have a
serial terminal nor firewire.
Could you show the output from running the following command in gdb -k
kernel.debug:
l *0xc056c706
This will tell us where in the kernel the instruction pointer in question
was. For whatever reason, your kernel panic doesn't
pointer in question
was. For whatever reason, your kernel panic doesn't seem to have dropped
you into DDB (at least, the output looks that way). If you did get into
ddb, the results of the trace command would be very helpful. As you
have no serial console, it's probably sufficient to just
On Sunday 16 November 2003 05:40, Craig Rodrigues wrote:
On Sun, Nov 16, 2003 at 05:32:03AM +0100, Harald Schmalzbauer wrote:
instruction pointer =0x8:0xc056c706
stack pointer =0x10:0xcdca4ca4
frame pointer =0x10:0xcdca4ca4
Do you have a file:
us where in the kernel the instruction pointer in question
was. For whatever reason, your kernel panic doesn't seem to have dropped
you into DDB (at least, the output looks that way). If you did get into
ddb, the results of the trace command would be very helpful. As you
have no serial
Hello!
I'm having some trouble booting the 5.1-RELEASE
installation floppies on an old AST Premmia GX P/133
SMP machine.
The system is currently running 3.5-STABLE without any
problems.
Any ideas anyone??
dmesg output follows:
FreeBSD/i386 boot
Default: 0:fd(0,a)/boot/loader
boot:
For the past few weeks my -CURRENT system has been locking up. With a
recent kernel (from 11/2) the following appears:
Fault trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc049d0db
stack pointer
Steve Ames [EMAIL PROTECTED] wrote:
For the past few weeks my -CURRENT system has been locking up. With a
recent kernel (from 11/2) the following appears:
Fault trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code = supervisor read, page not present
401 - 500 of 851 matches
Mail list logo
