In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes:
>I got a got this kernel panic:
>geom/geom_dev.c:("Negative bio_offset (%jd) on bio %p",
>
>Anyone seeing this also?
Please put DDB in your kernel and try to reproduce, then capture
traceback etc. (see handbook).
--
Poul-Henning Ka
I got a got this kernel panic:
geom/geom_dev.c:("Negative bio_offset (%jd) on bio %p",
Anyone seeing this also?
This is on a 2 processor XEON intel motherboard / adaptec 5400S raid /
AMD g2 console card.
The AMI g2 console card provides via USB a keyboard virtual cdrom etc.
Most of
I get this with a current kernel compiled just a few minute ago (SMP)
Can't get to debugger as keystyrokes don't work
Kernel from the 19th before UFS2 works fine.
Additional routing options:.
Mounting NFS file systems:.
Fatal trap 12: page fault while in kernel mode
cpuid = 1; lapic.id = 0c
Hi,
I'm getting the following panic when I run the following
command:
tar -cvf - . | compress | dd bs=64m of=/dev/sa0
running with a blocksize of 2,4,8,16, or 32meg on the dd
command run to completion with no problems.
Fatal trap 12: page fault while in kernel mode
fault virtual address
On Tue, Nov 07, 2000 at 02:29:40AM -0600, Michael C . Wu wrote:
> On Tue, Nov 07, 2000 at 04:13:37PM +0800, Clive Lin scribbled:
> | may panic because of several IPFIREWALL options. The panic message I could
> | tell is about trap 12, swi6: clock and page fault. And the machine hangs
> | solidly r
On Tue, Nov 07, 2000 at 04:13:37PM +0800, Clive Lin scribbled:
| may panic because of several IPFIREWALL options. The panic message I could
| tell is about trap 12, swi6: clock and page fault. And the machine hangs
| solidly right away, I have no idea how to provide a back trace :(
What is your m
Hi,
Sorry to bother/spam this mailing list again. In brief, rescent kernel
may panic because of several IPFIREWALL options. The panic message I could
tell is about trap 12, swi6: clock and page fault. And the machine hangs
solidly right away, I have no idea how to provide a back trace :(
