Date: Wed, 19 Jan 2022 10:58:31 +0000 From: bugzilla-noreply@freebsd.org To: standards@FreeBSD.org Subject: [Bug 255072] boot (legacy): no progress beyond 'BIOS DRIVE D: is disk1' Message-ID: <bug-255072-99-SM5KW513v1@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255072-99@https.bugs.freebsd.org/bugzilla/> References: <bug-255072-99@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255072 --- Comment #35 from spell@itl.ua --- (In reply to Toomas Soome from comment #30) >If the INT call will actually use more of that memory, then we may be in=20 >trouble. I guess the only way to detect how much buffer memory was actuall= y=20 >used, can be detected by storing know value into entire buffer, and test=20 >how big are it is where the buffer is changed. Can't implement this test because bd_edd_io() does not return (the crash oc= curs inside of it), so I can't check the buffer state after this crashing INT. Is there any way to look into the INT of itself? >did you see comment in bd_io()? >It is about proliant and large disk Can you please explain what a buffer overrun happens on that Proliant and h= ow does bd_io_workaround() solve the poblem and whether it just alleviates (as said in the comment) or totally excludes the buffer overrun? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255072-99-SM5KW513v1>