> > The problem was solved by using my own kernel, 2.6.18.
>
> Well, that means you've cathed this (git commit):
> b2ea401bac39e75ebb64038609ed22efbc799905
>
>
> Maybe it's worth to ask to be in next 2.6.17-stable ?
Yes, it will make sense to me. Problem is, that I cannot make any test,
becouse
On Sun, Sep 24, 2006 at 10:19:07PM +0200, Dan Ohnesorg wrote:
> Dne Sun, Sep 24, 2006 at 09:23:15PM +0200, Oleg Verych napsal:
>
> > Let's add XFS team in CC.
>
> There isn't
Yes, my MUA...
>
> > On 2006-09-24, Dan Ohnesorg <[EMAIL PROTECTED]> wrote:
> > > Package: linux-image-2.6-amd64
> > >
reassign 389232 linux-2.6
thanks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
> reassign 389232 linux-2.6
Bug#389232: linux-image-2.6-amd64: mounting xfs filesystem causes kernel oops
Bug reassigned from package `linux-image-2.6-amd64' to `linux-2.6'.
> thanks
Stopping processing here.
Please contact me if you
Dne Sun, Sep 24, 2006 at 09:23:15PM +0200, Oleg Verych napsal:
> Let's add XFS team in CC.
There isn't
> On 2006-09-24, Dan Ohnesorg <[EMAIL PROTECTED]> wrote:
> > Package: linux-image-2.6-amd64
> > Version: 2.6.17+2
> > Severity: critical
> > Justification: breaks the whole system
>
> More det
Let's add XFS team in CC.
On 2006-09-24, Dan Ohnesorg <[EMAIL PROTECTED]> wrote:
> Package: linux-image-2.6-amd64
> Version: 2.6.17+2
> Severity: critical
> Justification: breaks the whole system
More details, please.
What happend before this boot?
Why ext3 is recovering?
> raid1: raid set md
Package: linux-image-2.6-amd64
Version: 2.6.17+2
Severity: critical
Justification: breaks the whole system
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2
7 matches
Mail list logo
