Re: there is a bug in twe driver or disk subsystem for sure

I have some more info about this problem.
I have figured that clicking very fast
"Download Extended Error Log" link on
the alarm page of 3DM is causing panic with the message
below withing 5-30 seconds. Sometimes even on the
second click. So, i guess the problem may be related
to:
1) 3dm working badly with memory
2) freebsd 5.2 not being stable
3) twe driver (what does it have to do with the error log, but twe_ioctl
is mentioned on the stack in debugger).

However, if this is just a 3dm problem then why kernel panics, not just
3dm page faults or something like that?

Also, i hardly can reboot cleanly. Almost every time it either cannot
flush all buffers and gives up on, say, 100 buffers, or
panics at reboot complaining about page not being valid.
Maybe i shoudl just cvs in a week or so? It seems like general
fbsd5.2-current instability. Or I am wrong?

Artem


----- Original Message -----
From: "Vinod Kashyap" <vkashyap_at_3WARE.com>
To: "'Artem Koutchine'" <matrix_at_itlegion.ru>; <freebsd-current_at_freebsd.org>
Cc: <freebsd-bugs_at_freebsd.org>
Sent: Friday, April 02, 2004 11:10 PM
Subject: RE: there is a bug in twe driver or disk subsystem for sure


>
> The 3ware (twe) driver is obviously not causing this panic.
> It's something else (at line 128 in file /usr/src/sys/udm_dbg.c).
>
> Every time you try deleting a unit with mounted filesystems,
> or shutdown the system with mounted filesystems on 3ware units,
> you will see the message you mention, since the driver tries
> to delete the unit, but finds it to be busy.  Don't let the system
> panic, and simply shut it down.  You should still see the message.
>
>
> -Vinod.
>
>
> -----Original Message-----
> From: Artem Koutchine [mailto:matrix_at_itlegion.ru]
> Sent: Friday, April 02, 2004 9:05 AM
> To: freebsd-current_at_freebsd.org
> Subject: there is a bug in twe driver or disk subsystem for sure
>
>
> I am running 5.2-CURRENT. The box has 3w 8506-4LP
> SATA raid controller and freebsd is install onto raid5 array.
>
> Almost everytime i pull a hotswap disk (one out of four)
> or when very heavy disk activity (like background fsck after
> crashing on a 310GB label) i get the following after 10 or
> so minutes of uptime:
>
> Memory modified after free 0x788f400(508) val=20202020 _at_ 0xe788f400
> panic: Most recently used by devbuf
> at line 128 in file /usr/src/sys/udm_dbg.c
> cpu=0;
> Debugger ("panic")
> Stopped at Debugger +0.46: xchgl %ebx, in_Debugger.0
>
> and i typed 'c' in debugger:
>
> the system started to shutdown and here is what i saw:
>
> twe0: failed to delete unit 0
> stray irq9
>
>
> The box is:
> permicro X5DPE-G2 motherboard
> DUAL XEON 2.66Ghz (HT enabled) 533Mhz bus
> 2GB RAM
> 4 SATA SEAGTE 120GB DRIVES
> 3WARE 8506-4LP SATA RAID5 CONTROLLER
>
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>
>
> DISCLAIMER: The information contained in this electronic mail transmission
> is intended by 3ware for the use of the named individual or entity to
which
> it is directed and may contain information that is confidential or
> privileged and should not be disseminated without prior approval from
3ware
>
>
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"