diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/boot/1133 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/boot/1133')
| -rw-r--r-- | results/classifier/gemma3:12b/boot/1133 | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/boot/1133 b/results/classifier/gemma3:12b/boot/1133 new file mode 100644 index 000000000..b1738e93e --- /dev/null +++ b/results/classifier/gemma3:12b/boot/1133 @@ -0,0 +1,11 @@ + +unused memory filled with 0x00 instead of 0xFF +Description of problem: +Qemu, ever since it was made (so, since 2003), has this problem in DOS (either PC-DOS or MS-DOS and partly Windows 9x) not recognizing the memory available when the memory is filled with 0x00 but when it is filled with 0xFF it gets recognized properly, where should I patch qemu to solve this memory problem? + +Refer to +https://bugs.launchpad.net/qemu/+bug/1180923 +Steps to reproduce: +1. +2. +3. |