Displaying 20 results from an estimated 1300 matches similar to: "Corrupted index files"
2005 Nov 17
2
Dovecot LDA config problem on RHEL 4 x86_64
Hello,
Has anyone succeeded on configuring and compiling Sieve capable Dovecot
LDA on RHEL 4 x86_64 platform?
I am having problems with configure script hanging on sed while creating
Makefiles.
# ./configure --with-dovecot=../dovecot
..
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking for library containing
2004 Jun 28
0
Dovecot on Redhat GFS
Now that Redhat released GFS to GLP has anyone gotten around to
test Dovecot on top of that?
-- 
Tomi Hakala
2004 Sep 12
0
1.0-test41
http://dovecot.org/test/
I think this release should be quite stable one.
- fixes parsing mails with header lines longer than 8192 bytes
- cache file corruption fixes
- fixed "corrupted offset in mbox file" errors
- don't return extra INBOX replies in LIST
Those mbox and cache problems were pretty tricky to figure out. Thanks 
to Tomi Hakala for tons of testing while I tried to
2005 Aug 31
4
Oddities with Debian unstable dovecot
Hello,
I'm running an Debian etch box with unstable and ever since the last upgrade to dovecot, I've seen odd things.  At times, I would see emails would go missing from the Inbox or other folders, and I couldn't move emails that were moved from the Inbox to another folder back into the Inbox.   These have seen gone away since I removed all dovecot.* files and .index* files from my
2020 Oct 30
1
[PATCH] fbcon: Disable accelerated scrolling
On 29/10/2020 15:22, Daniel Vetter wrote:
> So ever since syzbot discovered fbcon, we have solid proof that it's
> full of bugs. And often the solution is to just delete code and remove
> features, e.g.  50145474f6ef ("fbcon: remove soft scrollback code").
> 
> Now the problem is that most modern-ish drivers really only treat
> fbcon as an dumb kernel console until
2024 Sep 26
1
[PATCH v5 79/80] drm/omapdrm: Remove struct drm_fb_helper from struct omap_fbdev.
Hi,
On 24/09/2024 10:13, Thomas Zimmermann wrote:
> Store instances of drm_fb_helper and struct omap_fbdev separately.
> This will allow omapdrm to use the common fbdev client, which allocates
> its own instance of struct drm_fb_helper.
> 
> There is at most one instance of each per DRM device, so both can be
> referenced directly from the omap and DRM device structures. A later
2025 Jan 09
1
[PATCH v2 15/25] drm/omapdrm: Compute dumb-buffer sizes with drm_mode_size_dumb()
Call drm_mode_size_dumb() to compute dumb-buffer scanline pitch and
buffer size. Align the pitch to a multiple of 8.
Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de>
Cc: Tomi Valkeinen <tomi.valkeinen at ideasonboard.com>
---
 drivers/gpu/drm/omapdrm/omap_gem.c | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)
diff --git
2025 Jan 15
1
[PATCH v2 25/25] drm/xlnx: Compute dumb-buffer sizes with drm_mode_size_dumb()
Hi,
On 15/01/2025 12:26, Thomas Zimmermann wrote:
> Hi
> 
> 
> Am 15.01.25 um 11:13 schrieb Tomi Valkeinen:
>> Hi!
>>
>> On 09/01/2025 16:57, Thomas Zimmermann wrote:
>>> Call drm_mode_size_dumb() to compute dumb-buffer scanline pitch and
>>> buffer size. Align the pitch according to hardware requirements.
>>>
>>> Signed-off-by:
2025 Jan 15
1
[PATCH v2 25/25] drm/xlnx: Compute dumb-buffer sizes with drm_mode_size_dumb()
Hi
Am 15.01.25 um 11:13 schrieb Tomi Valkeinen:
> Hi!
>
> On 09/01/2025 16:57, Thomas Zimmermann wrote:
>> Call drm_mode_size_dumb() to compute dumb-buffer scanline pitch and
>> buffer size. Align the pitch according to hardware requirements.
>>
>> Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de>
>> Cc: Laurent Pinchart <laurent.pinchart
2025 Jan 20
1
[PATCH v2 25/25] drm/xlnx: Compute dumb-buffer sizes with drm_mode_size_dumb()
Hi,
On 20/01/2025 09:49, Thomas Zimmermann wrote:
> Hi
> 
> 
> Am 16.01.25 um 11:03 schrieb Tomi Valkeinen:
> [...]
>> Aligning video= and dumb buffers almost sounds like going backwards. 
>> video= parameter is bad,
> 
> Who told you that? Video= is still the way to specify an initial display 
> mode to the kernel and it will remain so.
You did =). "It
2008 Jan 20
4
v1.1.beta14 released (Compile Error)
On Jan 20, 2008, at 12:15 PM, dovecot-request at dovecot.org wrote:
>
> Message: 5
> Date: Sun, 20 Jan 2008 15:48:09 +0200
> From: Timo Sirainen <tss at iki.fi>
> Subject: [Dovecot] v1.1.beta14 released
> To: dovecot at dovecot.org
> Message-ID: <1200836889.12450.99.camel at hurina>
> Content-Type: text/plain; charset="us-ascii"
>
>
2005 Jul 12
5
mysql
Hello,
Does dovecot require mysql in order to work? Fedora rpms are claiming
mysql dependencies.
I'm sure you're aware of the long-lived arguement of postgresql v. mysql.
If it wasn't your intention to force this, then please snarl at Red Hat.
If it was your intention, then grrrrr!
Thanks for this product. I like it for it's speed and stability.
Jim Edwards
2025 Jan 20
1
[PATCH v2 25/25] drm/xlnx: Compute dumb-buffer sizes with drm_mode_size_dumb()
Hi
Am 16.01.25 um 11:03 schrieb Tomi Valkeinen:
[...]
> Aligning video= and dumb buffers almost sounds like going backwards. 
> video= parameter is bad,
Who told you that? Video= is still the way to specify an initial display 
mode to the kernel and it will remain so.
Of course, it is better to auto-detect settings, but that's for a 
different use case.
Best regards
Thomas
>
2005 Aug 29
2
Sig11 and some corrupted indexes after 1.0-stable -> 1.0.alpha1
I just upgraded my production box from 1.0-stable to 1.0.alpha1.  I've
noted some new errors in my dovecot logs:
Aug 28 23:23:56 cliff dovecot: IMAP(rsferra): Corrupted index cache
file /mail/mcad.edu/rsferra/Maildir/.Sent Items/dovecot.index.cache:
indexid changed
Aug 28 23:33:57 cliff dovecot: IMAP(acarr): Corrupted transaction log
file /mail/mcad.edu/acarr/Maildir/.Deleted
2025 Jan 15
1
[PATCH v2 25/25] drm/xlnx: Compute dumb-buffer sizes with drm_mode_size_dumb()
Hi!
On 09/01/2025 16:57, Thomas Zimmermann wrote:
> Call drm_mode_size_dumb() to compute dumb-buffer scanline pitch and
> buffer size. Align the pitch according to hardware requirements.
> 
> Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de>
> Cc: Laurent Pinchart <laurent.pinchart at ideasonboard.com>
> Cc: Tomi Valkeinen <tomi.valkeinen at
2025 Jan 19
1
[PATCH v2 25/25] drm/xlnx: Compute dumb-buffer sizes with drm_mode_size_dumb()
Hi,
On 19/01/2025 13:29, Sui Jingfeng wrote:
> Hi,
> 
> On 2025/1/16 18:35, Dmitry Baryshkov wrote:
>> On Thu, Jan 16, 2025 at 11:17:50AM +0100, Geert Uytterhoeven wrote:
>>> On Thu, Jan 16, 2025 at 11:03?AM Tomi Valkeinen
>>> <tomi.valkeinen at ideasonboard.com> wrote:
>>>> On 16/01/2025 10:09, Thomas Zimmermann wrote:
>>>>> Am
2025 Jan 15
1
[PATCH v2 25/25] drm/xlnx: Compute dumb-buffer sizes with drm_mode_size_dumb()
Hi,
On 15/01/2025 14:34, Thomas Zimmermann wrote:
> Hi
> 
> 
> Am 15.01.25 um 13:06 schrieb Tomi Valkeinen:
>> Hi,
>>
>> On 15/01/2025 13:37, Thomas Zimmermann wrote:
>>> Hi
>>>
>>>
>>> Am 15.01.25 um 11:58 schrieb Tomi Valkeinen:
>>> [...]
>>>>> These are all good points. Did you read my discussion with
2025 Jan 19
1
[PATCH v2 25/25] drm/xlnx: Compute dumb-buffer sizes with drm_mode_size_dumb()
Hi,
On 2025/1/19 20:18, Tomi Valkeinen wrote:
> Hi,
>
> On 19/01/2025 13:29, Sui Jingfeng wrote:
>> Hi,
>>
>> On 2025/1/16 18:35, Dmitry Baryshkov wrote:
>>> On Thu, Jan 16, 2025 at 11:17:50AM +0100, Geert Uytterhoeven wrote:
>>>> On Thu, Jan 16, 2025 at 11:03?AM Tomi Valkeinen
>>>> <tomi.valkeinen at ideasonboard.com> wrote:
2025 Jan 16
3
[PATCH v2 25/25] drm/xlnx: Compute dumb-buffer sizes with drm_mode_size_dumb()
On Thu, Jan 16, 2025 at 11:03?AM Tomi Valkeinen
<tomi.valkeinen at ideasonboard.com> wrote:
> On 16/01/2025 10:09, Thomas Zimmermann wrote:
> > Am 15.01.25 um 15:20 schrieb Tomi Valkeinen:
> > [...]
> >>
> >> My point is that we have the current UAPI, and we have userspace using
> >> it, but we don't have clear rules what the ioctl does with
2025 Jan 15
1
[PATCH v2 25/25] drm/xlnx: Compute dumb-buffer sizes with drm_mode_size_dumb()
On Wed, 15 Jan 2025 at 14:20, Tomi Valkeinen
<tomi.valkeinen at ideasonboard.com> wrote:
> No disagreement there, we need CREATE_DUMB2.
>
> My point is that we have the current UAPI, and we have userspace using
> it, but we don't have clear rules what the ioctl does with specific
> parameters, and we don't document how it has to be used.
>
> Perhaps the situation