Working Reiser4 patch for kernel 2.6.6(-mm2)?

Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Raymond A. Meijer]

Hi,

Can someone point me to a WORKING Reiser4 patch for kernel 2.6.6 or 2.6.6-mm2?

I have tried the reiser4-2004.05.31-19.36-linux-2.6.6-mm2.diff.gz patch  from 
http://www.namesys.com/auto-snapshots/ and it compiles and boots cleanly, but 
it won't mount my Reiser4 partitions :(

Does anybody have a working patch? I cannot use BitKeeper to download it.


Thanks,

Ray (still stuck on kernel 2.6.5)

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Alex Zarochentsev]

On Wed, Jun 02, 2004 at 03:54:11PM +0300, Raymond A. Meijer wrote:
> Hi,
> 
> Can someone point me to a WORKING Reiser4 patch for kernel 2.6.6 or 2.6.6-mm2?
> 
> I have tried the reiser4-2004.05.31-19.36-linux-2.6.6-mm2.diff.gz patch  from 
> http://www.namesys.com/auto-snapshots/ and it compiles and boots cleanly, but 
> it won't mount my Reiser4 partitions :(

what reiser4 messages were in the log? 

-- 
Alex.

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Raymond A. Meijer]

On Wed 2 June 2004 15:56, Alex Zarochentsev wrote:

> > I have tried the reiser4-2004.05.31-19.36-linux-2.6.6-mm2.diff.gz patch 
> > from http://www.namesys.com/auto-snapshots/ and it compiles and boots
> > cleanly, but it won't mount my Reiser4 partitions :(

> what reiser4 messages were in the log?

I didn't write it down...and nothing was written to the logs because all 
partitions except the root partition are Reiser4.

But there was a kernel Oops and something like:

"page_extent: trying to read past end of device. Want=23252123 Limit=83380"

I can try again and write down the messages if you want...


Thanks,

Ray

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Alex Zarochentsev]

On Wed, Jun 02, 2004 at 04:03:46PM +0300, Raymond A. Meijer wrote:
> On Wed 2 June 2004 15:56, Alex Zarochentsev wrote:
> 
> > > I have tried the reiser4-2004.05.31-19.36-linux-2.6.6-mm2.diff.gz patch 
> > > from http://www.namesys.com/auto-snapshots/ and it compiles and boots
> > > cleanly, but it won't mount my Reiser4 partitions :(
> 
> > what reiser4 messages were in the log?
> 
> I didn't write it down...and nothing was written to the logs because all 
> partitions except the root partition are Reiser4.
> 
> But there was a kernel Oops and something like:
> 
> "page_extent: trying to read past end of device. Want=23252123 Limit=83380"

It would be fine to see a (decoded) stack trace.
> 
> I can try again and write down the messages if you want...

Does the snapshot from 2004.04.21 or from 2004.03.26 work still ?

> Thanks,
> Ray

-- 
Alex.

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[mjt]

On Wed, Jun 02, 2004 at 08:02:34PM +0400, Alex Zarochentsev wrote:
>> But there was a kernel Oops and something like:
>> "page_extent: trying to read past end of device. Want=23252123 Limit=83380"
>It would be fine to see a (decoded) stack trace.

Not that I would have had this problem, but are there some general
guidelines/FAQ-like answer on how to acquire this?

>> I can try again and write down the messages if you want...
>Does the snapshot from 2004.04.21 or from 2004.03.26 work still ?

It's against 2.6.5, not 2.6.6, and I think that was the general idea...

-- 
mjt

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Alex Zarochentsev]

On Wed, Jun 02, 2004 at 07:23:48PM +0300, Markus Törnqvist wrote:
> On Wed, Jun 02, 2004 at 08:02:34PM +0400, Alex Zarochentsev wrote:
> >> But there was a kernel Oops and something like:
> >> "page_extent: trying to read past end of device. Want=23252123 Limit=83380"
> >It would be fine to see a (decoded) stack trace.

<linux source dir>/Documentation/oops-tracing.txt 

> Not that I would have had this problem, but are there some general
> guidelines/FAQ-like answer on how to acquire this?
> 
> >> I can try again and write down the messages if you want...
> >Does the snapshot from 2004.04.21 or from 2004.03.26 work still ?
> 
> It's against 2.6.5, not 2.6.6, and I think that was the general idea...

Do you use RAID or LVM ?

> -- 
> mjt
> 

-- 
Alex.

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Alex Zarochentsev]

On Wed, Jun 02, 2004 at 08:34:45PM +0400, Alex Zarochentcev wrote:
> On Wed, Jun 02, 2004 at 07:23:48PM +0300, Markus Törnqvist wrote:
> > On Wed, Jun 02, 2004 at 08:02:34PM +0400, Alex Zarochentsev wrote:
> > >> But there was a kernel Oops and something like:
> > >> "page_extent: trying to read past end of device. Want=23252123 Limit=83380"
> > >It would be fine to see a (decoded) stack trace.
> 
> <linux source dir>/Documentation/oops-tracing.txt 
> 
> > Not that I would have had this problem, but are there some general
> > guidelines/FAQ-like answer on how to acquire this?
> > 
> > >> I can try again and write down the messages if you want...
> > >Does the snapshot from 2004.04.21 or from 2004.03.26 work still ?
> > 
> > It's against 2.6.5, not 2.6.6, and I think that was the general idea...
> 
> Do you use RAID or LVM ?

Sorry Markus, the last question is not for you.  But why do you think
2.6.6 is the point? 

> -- 
> Alex.

-- 
Alex.

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[mjt]

On Wed, Jun 02, 2004 at 08:39:13PM +0400, Alex Zarochentsev wrote:
>Sorry Markus, the last question is not for you.  But why do you think
>2.6.6 is the point? 

This is from the original mail:
Can someone point me to a WORKING Reiser4 patch for kernel 2.6.6 or 2.6.6-mm2?

And:
Subject: Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

;)

Besides that, maybe some other bugfix that's not easily included or
just the desire to ride the bleeding edge...

-- 
mjt

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Raymond A. Meijer]

On Wed 2 June 2004 19:34, Alex Zarochentsev wrote:

> > >> But there was a kernel Oops and something like:
> > >> "page_extent: trying to read past end of device. Want=23252123
> > >> Limit=83380"

> > >It would be fine to see a (decoded) stack trace.

I mounted the partition that causes the Oops (/dev/sys/usr on /usr) and tried
to run gcc from it. This was the result:

# /usr/bin/gcc
attempt to access beyond end of device
dm-3: rw=0, want=16777224, limit=8388608
attempt to access beyond end of device
dm-3: rw=0, want=16777224, limit=8388608
reiser4[bash(80)]: read_extent (fs)reiser4/plugin/item/extent_file_ops.c:993)[jmacd-97178]:
WARNING: extent_read: page is not up to date
bash: /usr/bin/gcc: cannot execute binary file
#

After that the kernel basically hangs...both 2.6.6-mm2 and 2.6.7-rc1. Exactly
the same message. So maybe there is something wrong with the filesystem after
all.

> Do you use RAID or LVM ?

I use LVM2:

  --- Logical volume ---
  LV Name                /dev/sys/usr
  VG Name                sys
  LV UUID                IskqlG-zNsy-4qIB-1Y6O-dlbQ-ciDT-OT4svJ
  LV Write Access        read/write
  LV Status              available
  # open                 4
  LV Size                4.00 GB
  Current LE             128
  Segments               1
  Allocation             next free (default)
  Read ahead sectors     0
  Block device           254:3

The weird thing is, though, that I cannot fsck this partition properly:

# fsck.reiser4 /dev/sys/usr
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************

Fscking the /dev/sys/usr block device.
Will check the consistency of the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): Yes
***** Opening the fs.
Reiser4 journal (journal40) on /dev/sys/usr: 0 transactions replayed of the total 0 blocks.
Reiser4 fs was detected on /dev/sys/usr.
Master super block (16):
magic:          ReIsEr4
blksize:        4096
format:         0x0 (format40)
uuid:           0a8cc420-fbe3-4e91-97f4-f6748e0bc243
label:          <none>

Format super block (17):
plugin:         format40
description:    Disk-format for reiser4, ver. 0.5.4
magic:          ReIsEr40FoRmAt
flushes:        0
mkfs id:        0x1b371ddb
blocks:         1048576
free blocks:    511894
root block:     47189
tail policy:    0x4 (smart)
next oid:       0x64322
file count:     127474
tree height:    4
key policy:     LARGE

***** Tree Traverse Pass: scanning the reiser4 internal tree.
        Read nodes 87921
        Nodes left in the tree 87921
                Leaves of them 86219, Twigs of them 1673
        Time interval: Thu Jun  3 13:58:24 2004 - Thu Jun  3 13:59:30 2004
***** TwigScan Pass: checking extent pointers of all twigs.
        Read twigs 1673
        Time interval: Thu Jun  3 13:59:30 2004 - Thu Jun  3 13:59:30 2004
***** Semantic Traverse Pass: reiser4 semantic tree checking.
Segmentation fault

I will try the reiser4progs-0.5.4_convertion.patch that Vitaly posted to see
if that makes any difference...


Ray

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Raymond A. Meijer]

On Thu 3 June 2004 14:07, Raymond A. Meijer wrote:

> ***** Semantic Traverse Pass: reiser4 semantic tree checking.
> Segmentation fault
> 
> I will try the reiser4progs-0.5.4_convertion.patch that Vitaly posted to
> see if that makes any difference...

Aha:

# fsck.reiser4 /dev/sys/usr
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************

Fscking the /dev/sys/usr block device.
Will check the consistency of the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): Yes
***** Opening the fs.
Reiser4 journal (journal40) on /dev/sys/usr: 0 transactions replayed of the total 0 blocks.
Reiser4 fs was detected on /dev/sys/usr.
Master super block (16):
magic:          ReIsEr4
blksize:        4096
format:         0x0 (format40)
uuid:           0a8cc420-fbe3-4e91-97f4-f6748e0bc243
label:          <none>

Format super block (17):
plugin:         format40
description:    Disk-format for reiser4, ver. 0.5.4
magic:          ReIsEr40FoRmAt
flushes:        0
mkfs id:        0x1b371ddb
blocks:         1048576
free blocks:    511894
root block:     47189
tail policy:    0x4 (smart)
next oid:       0x64322
file count:     127474
tree height:    4
key policy:     LARGE

***** Tree Traverse Pass: scanning the reiser4 internal tree.
Error: Can't open node 186461.
Error: Node (186461): failed to open the node pointed by the node (179889), item (24), unit (0) on the level (2). The whole subtree is
skipped.
Error: Can't open node 187038.
Error: Node (187038): failed to open the node pointed by the node (179889), item (25), unit (0) on the level (2). The whole subtree is
skipped.
Error: Can't open node 187044.
Error: Node (187044): failed to open the node pointed by the node (179889), item (26), unit (0) on the level (2). The whole subtree is
skipped.
The tree height 4 found in the format is wrong. Should be 3.
        Read nodes 2387
        Nodes left in the tree 2387
                Leaves of them 2329, Twigs of them 57
        Invalid node pointers 3
        Time interval: Thu Jun  3 14:16:33 2004 - Thu Jun  3 14:16:35 2004
***** TwigScan Pass: checking extent pointers of all twigs.
        Read twigs 57
        Time interval: Thu Jun  3 14:16:35 2004 - Thu Jun  3 14:16:35 2004

Fatal corruptions were found. Semantic pass is skipped.
Free block count 511894 found in the format is wrong. Sould be 1005780.
***** fsck.reiser4 finished at Thu Jun  3 14:16:35 2004
Closing fs...done

3 fatal corruptions were detected in FileSystem. Run with --build-fs option to fix them.

I'll reboot into single user mode, rebuild the FS and try again to boot into
2.6.6 and 2.6.7-rc1...

Keeping you posted...


Ray

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Raymond A. Meijer]

On Thu 3 June 2004 14:17, Raymond A. Meijer wrote:

> I'll reboot into single user mode, rebuild the FS and try again to boot into
> 2.6.6 and 2.6.7-rc1...
> 
> Keeping you posted...

There were MANY errors, but fsck.reiser4 fixed them all.

But it didn't help...still the same errors in 2.6.6-mm2 and 2.6.7-rc1-mm2...

I even reformatted the partition and restored a backup, and it still wouldn't
work!

However, I just discovered that my CFLAGS environment variable is by default
set to "-O3 -Wall -march=i686 -mcpu=i686 -msse2 -mfpmath=sse"!

So, I'll recompile a vanilla kernel with no optimisations and only the mm and
Reiser4 patches applied...

Here we go again! :)


Ray

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Raymond A. Meijer]

On Thu 3 June 2004 15:51, Raymond A. Meijer wrote:

> So, I'll recompile a vanilla kernel with no optimisations and only the mm
> and Reiser4 patches applied...

No, still the same: Oops errors when the kernel tries to mount Reiser4 
filesystems...

...but then I converted most of the system partitions (/var, /home, /usr) to 
ReiserFS and kept some other partitions in Reiser4 format (/backup, /tmp,
/var/spool/squid) and now it DOES work properly!

2.6.6-mm2 boots up fine, mounts everything and starts everything. I'm actually 
sending this mail with KMail on KDE 3.2.2 on kernel 2.6.6-mm2...

Any ideas as to what happened?! :)


Ray

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Alex Zarochentsev]

On Thu, Jun 03, 2004 at 05:04:09PM +0300, Raymond A. Meijer wrote:
> On Thu 3 June 2004 15:51, Raymond A. Meijer wrote:
> 
> > So, I'll recompile a vanilla kernel with no optimisations and only the mm
> > and Reiser4 patches applied...
> 
> No, still the same: Oops errors when the kernel tries to mount Reiser4 
> filesystems...
> 
> ...but then I converted most of the system partitions (/var, /home, /usr) to 
> ReiserFS and kept some other partitions in Reiser4 format (/backup, /tmp,
> /var/spool/squid) and now it DOES work properly!
> 
> 2.6.6-mm2 boots up fine, mounts everything and starts everything. I'm actually 
> sending this mail with KMail on KDE 3.2.2 on kernel 2.6.6-mm2...
> 
> Any ideas as to what happened?! :)

Seems we made a disk format change accidentally.  
details later. or a fix may be.

> Ray

-- 
Alex.

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Alex Zarochentsev]

On Thu, Jun 03, 2004 at 06:30:57PM +0400, Alex Zarochentcev wrote:
> On Thu, Jun 03, 2004 at 05:04:09PM +0300, Raymond A. Meijer wrote:
> > On Thu 3 June 2004 15:51, Raymond A. Meijer wrote:
> > 
> > > So, I'll recompile a vanilla kernel with no optimisations and only the mm
> > > and Reiser4 patches applied...
> > 
> > No, still the same: Oops errors when the kernel tries to mount Reiser4 
> > filesystems...
> > 
> > ...but then I converted most of the system partitions (/var, /home, /usr) to 
> > ReiserFS and kept some other partitions in Reiser4 format (/backup, /tmp,
> > /var/spool/squid) and now it DOES work properly!
> > 
> > 2.6.6-mm2 boots up fine, mounts everything and starts everything. I'm actually 
> > sending this mail with KMail on KDE 3.2.2 on kernel 2.6.6-mm2...
> > 
> > Any ideas as to what happened?! :)
> 
> Seems we made a disk format change accidentally.  
> details later. or a fix may be.

please try this patch:
=================================================
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
#   2004/06/03 19:04:55+04:00 zam@crimson.namesys.com 
#   enum item_id: restore disk format. 
# 
# forward.h
#   2004/06/03 19:04:51+04:00 zam@crimson.namesys.com +10 -9
#   enum item_id: restore disk format. 
# 
diff -Nru a/forward.h b/forward.h
--- a/forward.h	Thu Jun  3 19:20:36 2004
+++ b/forward.h	Thu Jun  3 19:20:36 2004
@@ -174,16 +174,17 @@
 	SQUEEZE_CONTINUE = 3
 } squeeze_result;
 
+/* Do not change items ids. If you do - there will be format change */
 typedef enum {
-	STATIC_STAT_DATA_ID,
-	SIMPLE_DIR_ENTRY_ID,
-	COMPOUND_DIR_ID,
-	NODE_POINTER_ID,
-	EXTENT_POINTER_ID,
-	FORMATTING_ID,
-	CTAIL_ID,
-	BLACK_BOX_ID,
-	LAST_ITEM_ID
+	STATIC_STAT_DATA_ID = 0x0,
+	SIMPLE_DIR_ENTRY_ID = 0x1,
+	COMPOUND_DIR_ID     = 0x2,
+	NODE_POINTER_ID     = 0x3,
+	EXTENT_POINTER_ID   = 0x5,
+	FORMATTING_ID       = 0x6,
+	CTAIL_ID            = 0x7,
+	BLACK_BOX_ID        = 0x8,
+	LAST_ITEM_ID        = 0x9
 } item_id;
 
 /* Flags passed to jnode_flush() to allow it to distinguish default settings based on
=================================================

> 
> > Ray
> 
> -- 
> Alex.

-- 
Alex.

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Raymond A. Meijer]

On Thu 3 June 2004 18:22, Alex Zarochentsev wrote:

> > > Any ideas as to what happened?! :)

> > Seems we made a disk format change accidentally.
> > details later. or a fix may be.

> please try this patch:

[forward.h patch]

Okay, patch applied and recompiling...


Thanks,

Ray

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Raymond A. Meijer]

On Fri 4 June 2004 10:29, Raymond A. Meijer wrote:

> > please try this patch:

> [forward.h patch]
>
> Okay, patch applied and recompiling...

So far so good. fsck.reiser4 found no errors, and everything mounted properly.


Thanks a lot!

Ray (from 2.6.6-mm2 :)

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Alex Zarochentsev]

On Fri, Jun 04, 2004 at 12:44:20PM +0300, Raymond A. Meijer wrote:
> On Fri 4 June 2004 10:29, Raymond A. Meijer wrote:
> 
> > > please try this patch:
> 
> > [forward.h patch]
> >
> > Okay, patch applied and recompiling...
> 
> So far so good. fsck.reiser4 found no errors, and everything mounted properly.
> Thanks a lot!

Thanks a lot for the report.

-- 
Alex.

Re: Working Reiser4 patch for kernel 2.6.6(-mm2)?

[Marcel Hilzinger]

May this be the same problem? I tried to repeat my "benchmark" with kernel 
2.6.7, but was not able to copy a directory to reiser4. I could create files 
with touch, but copying gave this error message (and the cp process hangs as 
D+): 
kernel 2.6.7-rc1
+ 2.6.7-rc1-mm1.bz2
+ reiser4-2004.06.02-19.39-linux-2.6.7-rc1-mm1.diff.gz
patching + compiling without errors

Jun  3 23:28:01 linux kernel: CPU:    0
Jun  3 23:28:01 linux kernel: EIP:    0060:[<00000000>]    Not tainted VLI
Jun  3 23:28:01 linux kernel: EFLAGS: 00010246   (2.6.7-rc1-mm1)
Jun  3 23:28:01 linux kernel: EIP is at 0x0
Jun  3 23:28:01 linux kernel: eax: efd4bae0   ebx: efd4bae0   ecx: efd4bad4   
edx: 00000000
Jun  3 23:28:01 linux kernel: esi: efd4bc7c   edi: c03b50e8   ebp: 00000001   
esp: efd4bad0
Jun  3 23:28:01 linux kernel: ds: 007b   es: 007b   ss: 0068
Jun  3 23:28:01 linux kernel: Process pdflush (pid: 38, threadinfo=efd4a000 
task=efd6f120)
Jun  3 23:28:01 linux kernel: Stack: c01ba127 00000000 00000000 00000000 
dd635b40 00000001 00000
105 ffffffff
Jun  3 23:28:01 linux kernel:        00000000 00000000 00000000 efd4bafc 
efd4bafc efd4bb04 efd4b
b04 efd4bb34
Jun  3 23:28:01 linux kernel:        00000000 efd4bc7c efd4bb34 efd4bcd4 
c01b9f15 00000000 c01b0
70d 00000000
Jun  3 23:28:01 linux kernel: Call Trace:
Jun  3 23:28:01 linux kernel:  [<c01ba127>] scan_by_coord+0xa7/0x2e0
Jun  3 23:28:01 linux kernel:  [<c01b9f15>] scan_unformatted+0x115/0x1b0
Jun  3 23:28:01 linux kernel:  [<c01b070d>] longterm_lock_znode+0xed/0x240
Jun  3 23:28:01 linux kernel:  [<c01acabd>] zload_ra+0x1d/0x20
Jun  3 23:28:01 linux kernel:  [<c01b9dad>] scan_common+0x2d/0x60
Jun  3 23:28:01 linux kernel:  [<c01b7dce>] jnode_flush+0x2ee/0x300
Jun  3 23:28:01 linux kernel:  [<c01b7fae>] flush_current_atom+0x1ae/0x220
Jun  3 23:28:01 linux kernel:  [<c01b5b91>] try_commit_txnh+0x161/0x180
Jun  3 23:28:01 linux kernel:  [<c01b5bdf>] commit_txnh+0x2f/0xa0
Jun  3 23:28:01 linux kernel:  [<c01b4e9e>] txn_end+0x2e/0x40
Jun  3 23:28:01 linux kernel:  [<c01b4eb8>] txn_restart+0x8/0x20
Jun  3 23:28:01 linux kernel:  [<c01b5588>] force_commit_atom_nolock+0x18/0x20
Jun  3 23:28:01 linux kernel:  [<c01b565e>] txnmgr_force_commit_all+0x9e/0xb0
Jun  3 23:28:01 linux kernel:  [<c01c2350>] writeout+0x20/0xb0
Jun  3 23:28:01 linux kernel:  [<c01c240c>] reiser4_sync_inodes+0x2c/0x50
Jun  3 23:28:01 linux kernel:  [<c01c23e0>] reiser4_sync_inodes+0x0/0x50
Jun  3 23:28:01 linux kernel:  [<c0169f39>] sync_sb_inodes+0x19/0x20
Jun  3 23:28:01 linux kernel:  [<c016a007>] sync_inodes_sb+0x67/0xa0
Jun  3 23:28:01 linux kernel:  [<c016b197>] mpage_writepages+0xf7/0x300
Jun  3 23:28:01 linux kernel:  [<c013a870>] pdflush+0x0/0x20
Jun  3 23:28:01 linux kernel:  [<c016a0c9>] sync_inodes+0x19/0x80
Jun  3 23:28:01 linux kernel:  [<c01505c1>] do_sync+0x11/0x60
Jun  3 23:28:01 linux kernel:  [<c015061a>] sys_sync+0xa/0x10
Jun  3 23:28:01 linux kernel:  [<c013a7c2>] __pdflush+0xd2/0x180
Jun  3 23:28:01 linux kernel:  [<c013a88a>] pdflush+0x1a/0x20
Jun  3 23:28:01 linux kernel:  [<c013a080>] laptop_flush+0x0/0x10
Jun  3 23:28:01 linux kernel:  [<c013a870>] pdflush+0x0/0x20
Jun  3 23:28:01 linux kernel:  [<c012ae9c>] kthread+0x7c/0xb0
Jun  3 23:28:01 linux kernel:  [<c012ae20>] kthread+0x0/0xb0
Jun  3 23:28:01 linux kernel:  [<c010424d>] kernel_thread_helper+0x5/0x18
Jun  3 23:28:01 linux kernel:
Jun  3 23:28:01 linux kernel: Code:  Bad EIP value.
-- 
Üdvözlettel -- Mit freundlichen Grüssen,
Marcel Hilzinger