I wonder if people are aware of this issue and if anyone is looking into it.
I got notified about it by Jenkins after an unrelated commit (ichwd).
panic: Memory modified after free 0xfe002efc8ed0(8) val=deadc0df @
0xfe002efc8ed0
11:51:33 cpuid = 0
11:51:33 time = 1544788293
11:51:33
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 a
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
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
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
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
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 the commit logs between
the 16th and the 17th I note the fo
panic:
Memory modified after free 0xc4987800(2044) val=c4986800 @ 0xc4987950
panic: Most recently used by bus
Debugger("panic")
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
db> where
Debugger(c083db04,c08ffbc0,c0855049,d782662c,100) at Debugger+0x54
panic(c0855049,c081f6e0,7fc,
Thanks for looking at this. I'm still scratching my head on it.
Doug White wrote:
> On Mon, 20 Oct 2003, othermark wrote:
>> I have a strange panic during the isa pnp code that does not occur with a
>> 5.0-release kernel.
...
> Can you pull out or disable the gig-e card? Its having trouble
> i
On Mon, 20 Oct 2003, othermark wrote:
> I have a strange panic during the isa pnp code that does not occur with a
> 5.0-release kernel. I have tried enabling and disabling acpi. it does
> not effect this panic one way or another. This is a kernel from -current
> 10/20 (today). I'm not sure how
I have a strange panic during the isa pnp code that does not occur with a
5.0-release kernel. I have tried enabling and disabling acpi. it does
not effect this panic one way or another. This is a kernel from -current
10/20 (today). I'm not sure how to get this to boot with no way to disable
pnp
n
> > using the console, but lasts upto 10 minutes when in use over ssh)
> > Running "make deinstall" triggered this panic:
> >
> > Memory modified after free 0xc1891c00(1020)
> > panic: Most recently used by none
>
> Update: I re-cvsupped (to 19 Dec 14:0
onsole, but lasts upto 10 minutes when in use over ssh)
> Running "make deinstall" triggered this panic:
>
> Memory modified after free 0xc1891c00(1020)
> panic: Most recently used by none
>[snip backtrace]
> The machine seems perfectly stable in single user mode. It
nning "make deinstall" triggered this panic:
Memory modified after free 0xc1891c00(1020)
panic: Most recently used by none
#10 0xc0204cfb in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:503
#11 0xc032c7dd in mtrash_ctor (mem=0xc1891c00, size=0, arg=0x0)
at /usr/src/sys/vm/um
14 matches
Mail list logo
