On Wed, Jan 22, 2003 at 08:59:51PM +0100, Thomas Moestl wrote:
On Tue, 2003/01/21 at 17:33:42 +, [EMAIL PROTECTED] wrote:
Hi
cvsup'd to . today on an E220R, single CPU with two Symbios scsi cards.
Box had been running fine with RC3, but would not boot with -CURRENT
kernel:
On Fri, 2003/01/24 at 11:54:41 +, Steven Haywood wrote:
hme6: Sun HME 10/100 Ethernet mem 0xc80-0xc807fff irq
26 at device 1.1 on
pci2
hme6: DMA buffer map load error 12
hme6: could not be configured
On Fri, Jan 24, 2003 at 05:10:07PM +0100, Thomas Moestl wrote:
This is probably easy to work around for you by increasing the amount
of available DVMA:
--
diff -u -r1.26 psycho.c
--- sparc64/pci/psycho.c 21 Jan 2003 08:56:14 - 1.26
+++ sparc64/pci/psycho.c 24 Jan 2003
In the last episode (Jan 23), Vincent Poy said:
Greetings everyone,
With the latest -CURRENTs ever since atleast September 12, 2002
that I have tested on several different machines ranging from
PII/PIII/PIV Desktop and Notebooks, whenever the following option is
added to the GENERIC
On Thu, Jan 23, 2003 at 05:40:16PM -1000, Vincent Poy wrote:
/boot/kernel/acpi.ko text=0x2fab4 data=-0x1a84+0x6e0
syms=[0x4+0x5540+0x702d|]
snip
embedded 0 6 A 0x60 3 4 5 6 7 9 10 11 12 14 15
panic: pmap_mapdev: Couldn't alloc kernel virtual memory
Debugger(panic)
Stopped at
On Tue, 2003/01/21 at 17:33:42 +, [EMAIL PROTECTED] wrote:
Hi
cvsup'd to . today on an E220R, single CPU with two Symbios scsi cards.
Box had been running fine with RC3, but would not boot with -CURRENT
kernel:
Current:
hme4: Ethernet address: 08:00:20:b7:ef:44
miibus4: MII bus on
Hi
cvsup'd to . today on an E220R, single CPU with two Symbios scsi cards.
Box had been running fine with RC3, but would not boot with -CURRENT
kernel:
Current:
hme4: Ethernet address: 08:00:20:b7:ef:44
miibus4: MII bus on hme4
ukphy3: Generic IEEE 802.3u media interface on miibus4
ukphy3:
Hi,
FreeBSD bree.elfwind.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Jan 18 09:05:06 GMT
2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/RV i386
Just received a kernel panic (don't do that) whilst attemping to
upload the firmware for an Alcatel USB ADSL modem.
#10 0xc024fa3b in panic (fmt=0x0
hi
I'm getting kernel panic on Compaq evo n1020v notebook when trying to boot
with ACPI enabled. Last message from kernel is
psm0: unable to allocate IRQ
without acpi it gets assigned IRQ without problems. Panic is however probably
unrelated to psm problem - it paniced the same way when I
through the first round
of Extracting into /, I got a page fault/kernel panic and a reboot.
Unfortunately, no other useful information was presented. This problem is
limited to 5.0 as I am able to recover a usable machine by installing 4.7
Release using the same method.
Has anyone else
I recently rebuilt my kernel to HEAD and configured my kernel to support the
Dual 200Mhz PPro's. upon restart, I recieved the kernel panic below.
panic: CPU APIC ID out of range (0..15)
cpuid = 0; lapic.id =
Debugger(panic)
Stopped at Debugger+0x55;xchgl%ebx
to support
the Dual 200Mhz PPro's. upon restart, I recieved the kernel panic below.
panic: CPU APIC ID out of range (0..15)
cpuid = 0; lapic.id =
Debugger(panic)
Stopped atDebugger+0x55;xchgl%ebx,in_Debugger.0
db trace
Debugger(c03ca5f6,0,c03e2f29,c0537d04,1
I get this when I try to enable bridging:
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:232
#1 0xc01f5f8e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:364
#2 0xc01f61d3 in panic () at /usr/src/sys/kern/kern_shutdown.c:517
#3 0xc0239317 in bremfree (bp=0xcae72988) at
On Thu, 26 Dec 2002, Peter Schultz wrote:
Are you actually using IPV6 or do you have IPV6 on your network segment?
It'd be nice to know wheich modules are loaded at 0xc04a0a74, 0xc04a0b20
and 0xc04a0e51. There is some way to make gdb know abouth the modules
too but I haven't kept up with it.
hiya folks
I've just tried booting the freebsd 5-rc2 ISO on my sony vaio srx51p from
the firewire cdrw/dvd. I wasn't really expecting to be able to install
from the firewire drive but I thought it might get far enough to net
install, however the rc2 iso has done the same on boot as the other 5
I fixed a serious DMA physical address translation bug in OHCI today.
Look on the lists today for this message. Message and patch enclosed.
Note that this fixes one bug in FreeBSD's implementation and a second
bug that is NetBSD/OpenBSD specific. I would appreciate it if someone
I have a CURRENT system that is panicing on me every couple of days. I have
enabled crash dumps in the rc.conf file, but when the system is rebooted,
savecore doesn't find any core files on the swap partition. The system has
128M RAM installed, and the swap partion is ~512M.
I am using a
On Tue, 2002-12-10 at 18:43, Paul A. Mayer wrote:
Greetings,
Congratulations on RC1! I've found an issue! :-)
I just upgraded my ASUS LC3800 portable to 5.0-RC1 from 5.0-DP2. The
new kernel panics shortly after booting up and drops into the debugger.
The messages look something like
On Wed, 2002-12-11 at 13:07, Koop Mast wrote:
Got the same laptop here, with the same problem.
Dmesg and some debug info attached.
For more debugging info or patch testing just ask.
Paul:
I found a little work around for this problem.
Just boot de laptop without de AC connector.
After
Greetings,
Congratulations on RC1! I've found an issue! :-)
I just upgraded my ASUS LC3800 portable to 5.0-RC1 from 5.0-DP2. The
new kernel panics shortly after booting up and drops into the debugger.
The messages look something like this:
Fatal trap 12
Page fault in kernel mode fault
Hello,
You need to prepare a kernel dump. Pardon the self-promotion:
http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html
http://www.onlamp.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html
With a full bug report, we can address this.
Thanks!
On Tue, Dec 10, 2002 at 06:43:55PM
Hi,
One of my FreeBSD-current test machines panicked upon
bootup. The message which appeared before the panic was:
imode = 041777, inum = 61, fs = /var
panic: ffs_valloc: dup alloc
I am attaching the ddb trace, the gdb trace,
and some Fault trap 12 messages that appeared in the console.
Any
Hi,
Can someone give me some ideas for how to debug a kernel
panic and isolate where the problem could be?
I've been trying out the Netgraph ATM stuff for a while,
and things have been working fine for a number of weeks.
However, when I cvsup'd -CURRENT from a few days ago,
I have one of my
Brian Fundakowski Feldman [EMAIL PROTECTED] wrote:
I can't get more info because crash dumps don't work when this happens, but
for what it's worth, here's a traceback which shows what happens when I
attempt to use my da0: SanDisk ImageMate II 1.30 Removable Direct Access
SCSI-2 device on an
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
umass_bbb_state
usb_transfer_complete
On Sat, 28 Sep 2002, Lars Eggert wrote:
I'm seeing a kernel panic on -current (9/26) when booting with a SanDisk
ImageMate II USB comact flash reader plugged in. The panic occurs after
the kernel has loaded when the first rc.d scripts execute (dumpon,
vinum, etc).
If I boot
Nate Lawson wrote:
On Sat, 28 Sep 2002, Lars Eggert wrote:
I'm seeing a kernel panic on -current (9/26) when booting with a SanDisk
ImageMate II USB comact flash reader plugged in. The panic occurs after
the kernel has loaded when the first rc.d scripts execute (dumpon,
vinum, etc
Hello,
Just bought a CNet WLAN card, and it makes -CURRENT panic when inserted,
or if it is inserted while booting.
Userland installed from 20021101 snapshot.
Kernel from today: FreeBSD 5.0-CURRENT #0: Sat Nov 2 09:50:05 CET 2002
(second panic from me issuing panic from ddb)
Fatal trap 12:
Does this happen with OLDCARD? I have a couple of cards that do this,
but haven't been able to track down why this happens.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Hello,
With OLDCARD it does not crash!
After crafting a pccard.conf entry for the card, wi does not
successfully attach to the card. Do you think it is feasible to add
support for this card in the wi driver?
Please don't hesitate to ask me for more information if you need it,
thanks! If there
In message: [EMAIL PROTECTED]
Frode Nordahl [EMAIL PROTECTED] writes:
: With OLDCARD it does not crash!
I'll answer this twice...
Can I ask you to do the following:
pccardc pccard_mem
pccardc pccard_mem 0xf800
pccardc dumpcis
(well, where 0xf800 is the same address that
In message: [EMAIL PROTECTED]
Frode Nordahl [EMAIL PROTECTED] writes:
: I get the following output from the driver:
: wi0 at port 0x240-0x27f irq 11 slot 1 on pccard1
: wi0: timeout in wi_cmd 0x; event status 0x
: wi0: timeout in wi_cmd 0x; event status 0x
: wi0:
On Sun, 2002-11-03 at 00:16, M. Warner Losh wrote:
pccardc pccard_mem
# pccardc pccardmem
PCCARD Memory address set to 0xd
pccardc pccard_mem 0xf800
# pccardc pccardmem 0xf800
PCCARD Memory address set to 0xf800
pccardc dumpcis
# pccardc pccardmem
PCCARD Memory address set
On Tue, Oct 22, 2002 at 12:10:25AM +0200, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Lars Eggert writes:
umass0: SanDisk Corporation ImageMate CompactFlash USB, rev 1.10/0.09,
addr 5
umass0: Get Max Lun not supported (STALLED)
da2 at umass-sim0 bus 0 target 0 lun 0
da2:
Bernd Walter wrote:
It's just the Name that don't exist.
Some time ago I was told to just open the device even if there is no
node listable in /dev.
E.g. mount_msdosfs /dev/da2s1 /mnt
Yes, this works (Terry also pointed this out.) I wish this could be
wired to the media change signal somehow.
On Tue, Oct 22, 2002 at 10:23:06AM -0700, Lars Eggert wrote:
Bernd Walter wrote:
It's just the Name that don't exist.
Some time ago I was told to just open the device even if there is no
node listable in /dev.
E.g. mount_msdosfs /dev/da2s1 /mnt
Yes, this works (Terry also pointed this
Bernd Walter wrote:
On Sat, Sep 28, 2002 at 07:20:08PM -0700, Lars Eggert wrote:
I'm seeing a kernel panic on -current (9/26) when booting with a SanDisk
ImageMate II USB comact flash reader plugged in. The panic occurs after
the kernel has loaded when the first rc.d scripts execute (dumpon
In message [EMAIL PROTECTED], Lars Eggert writes:
umass0: SanDisk Corporation ImageMate CompactFlash USB, rev 1.10/0.09,
addr 5
umass0: Get Max Lun not supported (STALLED)
da2 at umass-sim0 bus 0 target 0 lun 0
da2: SanDisk ImageMate II 1.30 Removable Direct Access SCSI-2 device
da2: 1.000MB/s
Does this happen on a current with this patch applied too?
Index: usb_port.h
===
RCS file: /home/ncvs/src/sys/dev/usb/usb_port.h,v
retrieving revision 1.58
diff -u -r1.58 usb_port.h
--- usb_port.h 2 Oct 2002 07:44:20 -
Josef Karthauser [EMAIL PROTECTED] wrote:
Does this happen on a current with this patch applied too?
I'm certain I tried this already :(
--
Brian Fundakowski Feldman \'[ FreeBSD ]''\
[EMAIL PROTECTED] [EMAIL PROTECTED] \ The Power to Serve! \
jroberson I suspect that there is some other bug then. 1/2 of your
jroberson memory should not be consumed by kernel malloc. Do you
jroberson have an abnormally large MD or something?
MD devices are used to create installation floppies but no, it should
be 1.44MB/2.88MB size, relatively small
Makoto Matsushita wrote:
jroberson I suspect that there is some other bug then. 1/2 of your
jroberson memory should not be consumed by kernel malloc. Do you
jroberson have an abnormally large MD or something?
MD devices are used to create installation floppies but no, it should
be
tlambert2 The worst case failure with my Ugly patch should be that
tlambert2 things hang, and quit running completey.
I've emailed to the list that I've tried your patch but it cannot boot
(actually it boots, but panics immediately.) Maybe I'm using
different time of source code. Which
Makoto Matsushita wrote:
tlambert2 The worst case failure with my Ugly patch should be that
tlambert2 things hang, and quit running completey.
I've emailed to the list that I've tried your patch but it cannot boot
(actually it boots, but panics immediately.) Maybe I'm using
different time
On Tue, 15 Oct 2002, Makoto Matsushita wrote:
I'm now trying Terry's patch (just rebuilding a kernel).
jroberson You are using 100mb of KVA for malloc(9)? Are you certain
jroberson that you don't have a memory leak?
Maybe there's a chance of a memory leakage by GLOBAL, but I don't sure.
After upgrading my 5-current box (as of late September 2002), the
kernel panics periodically with following message:
panic: kmem_malloc(4096): kmem_map too small: 107651072 total allocated
The number '4096' and '107651072' is always the same. What am I
missing something?
-- -
Makoto
Makoto Matsushita wrote:
After upgrading my 5-current box (as of late September 2002), the
kernel panics periodically with following message:
panic: kmem_malloc(4096): kmem_map too small: 107651072 total allocated
The number '4096' and '107651072' is always the same. What am I
On Mon, 14 Oct 2002, Makoto Matsushita wrote:
After upgrading my 5-current box (as of late September 2002), the
kernel panics periodically with following message:
panic: kmem_malloc(4096): kmem_map too small: 107651072 total allocated
The number '4096' and '107651072' is always the
I'm now trying Terry's patch (just rebuilding a kernel).
jroberson You are using 100mb of KVA for malloc(9)? Are you certain
jroberson that you don't have a memory leak?
Maybe there's a chance of a memory leakage by GLOBAL, but I don't sure.
jroberson How much memory is in this machine?
tlambert2 This was recently discussed on -current. I posted a dumb
tlambert2 patch that fixes the problem.
(stuff deleted)
tlambert2 See the archive of the posting, for more details:
Thank you, I'll try it right now.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
matusita Thank you, I'll try it right now.
Unfortunately, kernel panics soon after it wakes up... maybe I've
still missed something.
-- -
Makoto `MAR' Matsushita
Booting [/boot/kernel/kernel]...
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989,
the ddb trace. it may not be exactly accurate because i don't
have a serial ddb and therefore have to copy the output from the screen.
+++ ddb output from kernel panic +++
panic: kmem_malloc(4096): kmem_map too small: 23134208 total allocated
Debugger(panic)
Stopped at Debugger+0q45: xchgl %ebx
and therefore have to copy the output from the screen.
+++ ddb output from kernel panic +++
panic: kmem_malloc(4096): kmem_map too small: 23134208 total allocated
Debugger(panic)
Stopped atDebugger+0q45: xchgl %ebx,in_Debugger.0
db trace
Debugger(c02cd335) at Debugger+0x45
panic
On Sun, 6 Oct 2002, fergus wrote:
i have a crash dump for this now if anyone is interested. it's not
exactly the same trace as it seems to originate from a VOP_LINK request
this time but i guess it's the same problem.
To be honest, it sounds like something is simply leaking kernel
I can't get more info because crash dumps don't work when this happens, but
for what it's worth, here's a traceback which shows what happens when I
attempt to use my da0: SanDisk ImageMate II 1.30 Removable Direct Access
SCSI-2 device on an OHCI-based controller. This was working just a few
On Sunday, 6 October 2002 at 18:25:08 -0400, Robert Watson wrote:
On Sun, 6 Oct 2002, fergus wrote:
i have a crash dump for this now if anyone is interested. it's not
exactly the same trace as it seems to originate from a VOP_LINK request
this time but i guess it's the same problem.
To
Hi. See pr kern/43462. Happens to me. I wish it would get fixed :)
On Sun, 6 Oct 2002, Brian Fundakowski Feldman wrote:
I can't get more info because crash dumps don't work when this happens, but
for what it's worth, here's a traceback which shows what happens when I
attempt to use my da0:
the kernel trace for this (i'm rebuilding to get
one) and the dump's not making it to disk. perhaps someone else could
try and verify in the mean time.
+++ kernel panic message +++
panic: kmem_malloc(4096): kmem_map to small: 23179264 total allocated
syncing disks... panic: allocbuf: buffer not busy
On Saturday, 5 October 2002 at 22:16:10 +0100, n0g0013 wrote:
got panic from vinum on a small striped drive with small dump/restores
-- dump of usr fs to file and restore to vinum volume. dump file is
about 120m.
kernel built from about -0230 sources but i've been seeing them since
first
On Sat, Sep 28, 2002 at 07:20:08PM -0700, Lars Eggert wrote:
Hi,
I'm seeing a kernel panic on -current (9/26) when booting with a SanDisk
ImageMate II USB comact flash reader plugged in. The panic occurs after
the kernel has loaded when the first rc.d scripts execute (dumpon,
vinum, etc
Hi,
I'm seeing a kernel panic on -current (9/26) when booting with a SanDisk
ImageMate II USB comact flash reader plugged in. The panic occurs after
the kernel has loaded when the first rc.d scripts execute (dumpon,
vinum, etc).
If I boot with the device disconnected, I can plug
leeloo kernel: trap number = 12
Sep 25 12:05:19 leeloo kernel: panic: page fault
Sep 25 12:05:19 leeloo kernel:
Sep 25 12:05:19 leeloo kernel: syncing disks... panic: bremfree: bp 0xd381a080 not
locked
Sep 25 12:05:19 leeloo kernel: Uptime: 2h22m51s
Sep 25 12:05:19 leeloo kernel
Hi,
I have been working onder -current for about 4 weeks.
But for some reason evoltion seems to make my system panic
I use the 1.1.1 beta version, I can't clearly remember what
evo 1.0.8 behavior was.
I have include the last panic, i get al lot of panics that include
bremfree, and always under
On Wed, 11 Sep 2002, Nate Lawson wrote:
This is being worked on. See msg thread in cvs-all, starting with:
[EMAIL PROTECTED]. You can back out the
change (1.49) if you need to get running.
Sorry, 1.50 fixed the problem. I reverted back to kernel.old
anyways which was from a
Revelent info:
* $FreeBSD: src/sys/kern/kern_acct.c,v 1.49 2002/09/11 04:10:41 arr Exp $
Console output...
Starting syslogd.
Sep 11 12:35:51 bigbang syslogd: kernel boot file is /boot/kernel/kernel
Starting named.
Starting ntpdate.
Turning on accounting.
recursed on non-recursive lock (sleep
This is being worked on. See msg thread in cvs-all, starting with:
[EMAIL PROTECTED]. You can back out the
change (1.49) if you need to get running.
-Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Hi Folks,
I got this kernel panic yesterday and this has happened twice in the
last two days.
--
/usr/src/sys/vm/uma_core.c:1332: could sleep with inp locked from
/usr/src/sys/netinet/tcp_usrreq.c:1013
Fatal trap 12: page fault while in kernel
An Mon, Aug 12, 2002 at 09:35:34AM +0530, Sid Carter schreib :
I got this kernel panic yesterday and this has happened twice in the
last two days.
--
/usr/src/sys/vm/uma_core.c:1332: could sleep with inp locked from
/usr/src/sys/netinet
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounters tick every 10.000 msec
Fatal trap 9: general protection fault while in kernel mode
instruction pointer = 0x8:0xc4109ac1
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounters tick every 10.000 msec
Fatal trap 9: general protection fault while in kernel mode
instruction pointer =
Mitsuru IWASAKI wrote:
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounters tick every 10.000 msec
Fatal trap 9: general protection fault while in kernel mode
instruction pointer
On Thu, Aug 01, 2002 at 10:14:34PM +0900, Mitsuru IWASAKI wrote:
Hmmm, I don't think so. How about typing
unset acpi_load
in loader prompt, and see if this panic disappear or still happen?
Where is it documented what to do to stop the autoloading of acpi.ko?
To Unsubscribe: send mail
Terry Lambert wrote:
Michael Nottebrock wrote:
I tweaked my BIOS to assign a different irq (9) to
the NIC and now the kernel boots and runs my old userland quite nicely.
The old kernel ran perfectly well with the NIC on irq10 ... strange.
None of your other postings identified the devices
Michael Nottebrock wrote:
I tweaked my BIOS to assign a different irq (9) to
the NIC and now the kernel boots and runs my old userland quite nicely.
The old kernel ran perfectly well with the NIC on irq10 ... strange.
None of your other postings identified the devices also on
IRQ10. If
2 18:32:24 calvin kernel: /var: bad dir ino 18826 at offset 44:
mangled entry
Jul 2 18:32:24 calvin kernel: panic: ufs_dirbad: bad dir
Jul 2 18:32:24 calvin kernel:
Jul 2 18:32:24 calvin kernel: syncing disks... panic: bremfree: bp 0xc76b3530 n
ot locked
Jul 2 18:32:24 calvin kernel: Uptime
I'm not sure this is related to Julian's commit,
but the kernel sources are post-kse III commit.
I have the kernel and core file if more info
or access is needed.
--
Steve
http://troutmask.apl.washington.edu/~kargl/
Script started on Sat Jun 29 18:36:22 2002
GNU gdb 5.2.0 (FreeBSD) 20020627
it definitly looks like one for me
if you have the core file, can you find the line in fill_kinfo_proc
that exploded?
up 15
list
should do
I think I saw this once myself but wasn't able to reproduce it again.
On Sat, 29 Jun 2002, Steven G. Kargl wrote:
I'm not sure this is related to
boot file is /boot/kernel/kernel
Jun 25 17:52:14 calvin kernel: Memory modified after free 0xc2bb6c00(252)
Jun 25 17:52:14 calvin kernel: panic: Most recently used by file desc
Jun 25 17:52:14 calvin kernel:
Jun 25 17:52:14 calvin kernel:
Jun 25 17:52:14 calvin kernel: syncing disks... panic: bremfree
Hello everybody,
I upgraded to today's -CURRENT and upon reboot with the new kernel,
experienced a panic. Since I did not see it reported here yet, here is
some info. More available on request, but I do not have a serial console
and therefore had to transcribe everything by hand. Also, there was
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 =
calvin kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep with
process lock locked from /usr/src/sys/kern/kern_prot.c:613
Jun 11 19:02:20 calvin kernel: Memory modified after free
0xd33f5900(252)
Jun 11 19:02:20 calvin kernel: panic: Most recently used by kqueue
Jun 11 19:02:20 calvin kernel:
Jun
from /usr/src/sys/kern/kern_prot.c:511
| Jun 11 19:00:00 calvin kernel: /usr/src/sys/vm/uma_core.c:1327: could sleep
| with
| process lock locked from /usr/src/sys/kern/kern_prot.c:613
| Jun 11 19:02:20 calvin kernel: Memory modified after free
| 0xd33f5900(252)
| Jun 11 19:02:20 calvin kernel
On Tue, Jun 11, 2002 at 09:13:44AM -0700, Edwin Culp wrote:
My laptop is rebooting with todays current/kernel in ifconfig. I just
got it up with an old kernel and am checking now. It will run with the
new kernel if I don't try to configure the network. I may have something
wrong though.
Hi,
I have a problem with DRM, I have ATI Xpert2000 AGP card,
in 4.5-RELEASE I used r128.ko , and all was fine, in current my kernel hangs up
saying: malloc type lacks magic number.
I have compiled the kernel with 'device agp' so what can be wrong?
To Unsubscribe: send mail to [EMAIL
This is a new problem beginning after a buildworld and build
kernel yesterday, May 08 (still the old gcc 2.95.4):
The system is quite stable until I mount an ext2 partition and
attempt to list its directory. Immediately I get this error:
syncing disks... panic: bdwrite: buffer is not busy.
If
Following are observed with 5-current kernel as of Apr/25/2002.
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x6
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01898d1
stack pointer = 0x10:0xc9476b24
frame
matusita I must provide more detailed information, but here's quick report.
Using trace command, this panic is caused by:
usbd_open_pipe_ival(c40416e0, 1, c8148858, ) at
usbd_open_pipe_ival+0x1d
usbd_open_pipe(c40416e0, 81, 1, c8148858, c40769c0, c8148880, 2, 1,
Has anyone seen mounting an NTFS drive casing a kernel panic? I'd
love to give the output, but I'm not sure how to redirect the output
into a file so I can post it here.
--
David W. Chapman Jr.
[EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net
[EMAIL PROTECTED
On Tue, Mar 26, 2002 at 10:08:20AM +1030, Greg 'groggy' Lehey wrote:
On Monday, 25 March 2002 at 9:41:09 -0600, David W. Chapman Jr. wrote:
Has anyone seen mounting an NTFS drive casing a kernel panic? I'd
love to give the output, but I'm not sure how to redirect the output
into a file
On Monday, 25 March 2002 at 9:41:09 -0600, David W. Chapman Jr. wrote:
Has anyone seen mounting an NTFS drive casing a kernel panic? I'd
love to give the output, but I'm not sure how to redirect the output
into a file so I can post it here.
You need to take a dump and analyse it. There's
It could be this problem is a result of the loadable VFS module bug
hacked/fixed in the tree this morning. Was the NTFS driver being loaded
as a module, or compiled into the kernel? If a loadable module, could you
try compiling it into the kernel, or updating past the fix? If already
Having determined that the last bootable install image was 20020311,
I have network booted my Sony VAIO PCG-SRX7E/P using pxeboot and the
contents of the boot.flp image on an NFS mount.
If the boot process is allowed to progress without interruption, the
kernel panics:
[...]
vga0: Generic ISA
In message: [EMAIL PROTECTED]
Jeff Kletsky [EMAIL PROTECTED] writes:
: As in the past, Werner Losh's recommended
: OK set hw.pcic.intr_path=1
: OK set hw.pcic.irq=0
: OK boot
You might try current after March 16th to see if this is still
needed. I just fixed what I think was a
* Emiel Kollof ([EMAIL PROTECTED]) wrote:
exclusive (sleep mutex) Giant (0xc0462c00) locked @
/usr/src/sys/i386/i386/trap.c:1102
panic: system call pwrite returning with mutex(s) held
Hmm, erm, go kick Alfred really hard. :) This function locks Giant and then
doesn't ever unlock
* Emiel Kollof [EMAIL PROTECTED] [020116 13:29] wrote:
* Emiel Kollof ([EMAIL PROTECTED]) wrote:
exclusive (sleep mutex) Giant (0xc0462c00) locked @
/usr/src/sys/i386/i386/trap.c:1102
panic: system call pwrite returning with mutex(s) held
Hmm, erm, go kick Alfred really hard.
* Alfred Perlstein [EMAIL PROTECTED] [020116 13:30] wrote:
* Emiel Kollof [EMAIL PROTECTED] [020116 13:29] wrote:
* Emiel Kollof ([EMAIL PROTECTED]) wrote:
exclusive (sleep mutex) Giant (0xc0462c00) locked @
/usr/src/sys/i386/i386/trap.c:1102
panic: system call pwrite returning
* Alfred Perlstein ([EMAIL PROTECTED]) wrote:
It would help if someone cc'd me on these. :P
Fix should be in now.
Great! Thanks! Remind me to buy you a beer if I ever get to meet you in
real life :-)
Right.. cvsup it is...
Cheers,
Emiel
--
If you can survive death, you can probably
On Mon, 19 Nov 2001, Bob Vaughan wrote:
sources from yesterday evening. rebuild with kernel sources from tonight.
same results.
vt0: unknown trident VGA, 80 columns, color, 8 screens, unknown keyboard
Warning: Driver mistake: repeat make_dev (ttyv0)
panic: don't do that
Debugger
sources from yesterday evening. rebuild with kernel sources from tonight.
same results.
vt0: unknown trident VGA, 80 columns, color, 8 screens, unknown keyboard
Warning: Driver mistake: repeat make_dev (ttyv0)
panic: don't do that
Debugger (panic
stopped at debugger+0x44 pushl %ebx
Bob Vaughan [EMAIL PROTECTED] wrote:
sources from yesterday evening. rebuild with kernel sources from tonight.
same results.
vt0: unknown trident VGA, 80 columns, color, 8 screens, unknown keyboard
Warning: Driver mistake: repeat make_dev (ttyv0)
Does this only happen with a recent
601 - 700 of 851 matches
Mail list logo
