On Tuesday, May 5, 2020, Lucas wrote:
> Hello bugs@,
>
> I'm maybe feeding the troll, so to say, but wanted to give it a chance.
> After all, it might be correct, right?
Check the mailing list archives for his name, he's a recurrent troll
>
> So, what do we have? A partial traceback, a
Hello bugs@,
I'm maybe feeding the troll, so to say, but wanted to give it a chance.
After all, it might be correct, right?
So, what do we have? A partial traceback, a partial input, and a partial
OS version. Subject: line indicates it's v6.6-stable, which, according
to [1], is 6.6 plus errata
Rupert, please go away.
You are not useful, and you're being an asshole.
You belong in a different community.
Please go rant somewhere else about how horrible we are,
and stop abusing our volunteer developers with your
abuse.
-Bob
On Tue, May 05, 2020 at 08:09:44AM +, Rupert
How about clearing your head from all those irrelevant questions of yours, and
focus instead on the info you already have in the OP?
It is a shame for obsd's kernel to crash when mounting a disk image, so focus
on the actual kernel crash to figure out a way to prevent this problem from
>> bsd.rd, as well as everything else not in the OP, is irrelevant. I was not
>> running bsd.rd and I was not mounting its disk image, so stop asking for it.
> If you already know that it's irrelevant, then maybe don't bother asking for
> help on a mailing list which specifically asks you to
> Maybe it's a CPU related bug, who knows.
Maybe you are using powerpc or arch64 and your bug isn't reproducible on amd64.
No, the CPU is an amd64. It is was something else, I would have mentioned it.
> There is a page explaining how to report bug properly
> https://www.openbsd.org/report.html
On 2020/05/04 23:03, Rupert Gallagher wrote:
> > Maybe it's a CPU related bug, who knows.
> Maybe you are using powerpc or arch64 and your bug isn't reproducible on
> amd64.
>
> No, the CPU is an amd64. It is was something else, I would have mentioned it.
You aren't going to get accurate
On 2020/05/04 22:57, Rupert Gallagher wrote:
> > So you don't think there could be something odd in the bsd.rd so you would
> > write
> "download bsd.rd #234234 from ftp.unsynchedmirror.com or my copy here"
> Perhaps this was fixed in 6.5 and you are running something older?
>
> Why bothering
> dmesg, bsd.rd version, hw info? Missing
HW info, boot dmesg and bsd.rd are irrelevant in this case. The hw works very
well with obsd, and the crash occurred when *I* was mounting a disk image.
> Steps to repro? Missing
I assume bug@ knows how to mount a disk image.
> The page
Le Mon, 04 May 2020 10:11:02 +,
Rupert Gallagher a écrit :
> > dmesg, bsd.rd version, hw info? Missing
>
> HW info, boot dmesg and bsd.rd are irrelevant in this case. The hw
> works very well with obsd, and the crash occurred when *I* was
> mounting a disk image.
Maybe it's a CPU related
# INPUT
Mounting ramdisk kernel.
# OUTPUT
...
mode = 0100644, inum = 173, fs = /mnt/vnd0a
panic: ffs_valloc: dup alloc
Stopped at db_enter+0x10: popq%rbp
TIDPIDUID PRFLAGS PFLAGS CPU COMMAND
* 69200 60093 0 0x3 00K install
db_enter() at
11 matches
Mail list logo
