As Andrey V. Elsukov wrote:
> > Anyway, it appears to be a software bug. Ah, OK, it's quite possible
> > the bug has always been there, even in RELENG_7 ... I just never
> > tested that one against INVARIANTS.
>
> I committed the fix in the r83, can you test it?
Works fine!
--
cheers, J"or
As Andrey V. Elsukov wrote:
> > Anyway, it appears to be a software bug. Ah, OK, it's quite possible
> > the bug has always been there, even in RELENG_7 ... I just never
> > tested that one against INVARIANTS.
>
> I committed the fix in the r83, can you test it?
Спасибо, I'll test it tonigh
On 25.05.2011 15:15, Joerg Wunsch wrote:
>> Or maybe you added options INVARIANTS
>> to your kernel?
>
> I did (for other rasons, which you can read about in the freebsd-scsi
> list).
>
> Anyway, it appears to be a software bug. Ah, OK, it's quite possible
> the bug has always been there, even i
As Andrey V. Elsukov wrote:
> Are you sure that it is RELENG_8?
Yes, I am.
> Or maybe you added options INVARIANTS
> to your kernel?
I did (for other rasons, which you can read about in the freebsd-scsi
list).
Anyway, it appears to be a software bug. Ah, OK, it's quite possible
the bug has al
On 25.05.2011 13:36, Joerg Wunsch wrote:
> Well, the workaround is easy (just return -1 from gv_taste() when
> noticing the offset is not on a sector boundary - this can never be a
> valid gvinum device anyway), but I'm curious about why this panic now
> happens in RELENG_8 when it didn't before.
As Jeremy Chadwick wrote:
> Just an informational note about inducing a panic: I tend to, once at
> the db> prompt, do "bt" then immediately "call doadump". That induces
> memory being written to swap, then do "reboot".
OK, reproduced the panic (which was easy ;), and did it that way.
Now, the s
Am 24.05.2011 10:53, schrieb Jeremy Chadwick:
> On Tue, May 24, 2011 at 09:26:18AM +0200, Joerg Wunsch wrote:
>> As Andriy Gapon wrote:
>>
panic: wrong offset 4096 for sectorsize 2352
Any ideas why this happens, and how to avoid it?
>>
>>> Backtrace would be a first thing.
>>
>> OK,
On Tue, May 24, 2011 at 09:26:18AM +0200, Joerg Wunsch wrote:
> As Andriy Gapon wrote:
>
> > > panic: wrong offset 4096 for sectorsize 2352
> > >
> > > Any ideas why this happens, and how to avoid it?
>
> > Backtrace would be a first thing.
>
> OK, here we go (the core has been dumped from with
on 24/05/2011 10:26 Joerg Wunsch said the following:
> As Andriy Gapon wrote:
>
>>> panic: wrong offset 4096 for sectorsize 2352
>>>
>>> Any ideas why this happens, and how to avoid it?
>
>> Backtrace would be a first thing.
>
> OK, here we go (the core has been dumped from within a serial conso
As Andriy Gapon wrote:
> > panic: wrong offset 4096 for sectorsize 2352
> >
> > Any ideas why this happens, and how to avoid it?
> Backtrace would be a first thing.
OK, here we go (the core has been dumped from within a serial console
BREAK DDB entry, I'm omitting the frames related to that):
on 24/05/2011 08:54 Joerg Wunsch said the following:
> After I recently (finally) upgraded my main machine to RELENG_8, I
> tried to rip a CD today, using abcde, and got
>
> panic: wrong offset 4096 for sectorsize 2352
>
> Any ideas why this happens, and how to avoid it?
>
> (I've got a coredump
After I recently (finally) upgraded my main machine to RELENG_8, I
tried to rip a CD today, using abcde, and got
panic: wrong offset 4096 for sectorsize 2352
Any ideas why this happens, and how to avoid it?
(I've got a coredump of the kernel, so I could analyze it if
someone has got an idea wher
12 matches
Mail list logo
