Kernel messages in the syslog
hi
i have a sun e250 mit 2 CPU´s (SPARC) and 1024 MB RAM.
I compilied a new kernel 2.4.18 and 2.4.19 , with both i have the same
problem.
I compilied the new Kernel with the debien sources and the xfs patch and
the egcs64 package. I take the xfs patch from stable for the 2.4.18
and the xfs patch from testing for the 2.4.19. I compilied the kernel
with xfs and raid 1 support. i don´t change more in the configuration.
Then i make the package with make-kpkg --subarch=sun4u --arch_in_name
--revision=custom.1 kernel_image.
Now i try to build a mirror, with the RAIDTools2. When i build the
mirror i don´t have problems. The problem beginns when i put a
filesystem on
the metadevice. Then i get the following entries in the syslog. And when
i tried to mount the metadevices the command wich try to use the meta-
device is frozen.But i don`get a kernelpanic.
Jan 12 17:03:45 brudertuck kernel: EXT3 FS 2.4-0.9.17, 10 Jan 2002 on
md(9,0), internal journal
Jan 12 17:03:45 brudertuck kernel: EXT3-fs: mounted filesystem with
ordered data mode.
Jan 12 17:03:57 brudertuck kernel: data_access_exception:
SFSR[0000000000801009] SFAR[fffff808c9509efc], going.
Jan 12 17:03:57 brudertuck kernel: \|/ ____ \|/
Jan 12 17:03:57 brudertuck kernel: "@'/ .. \`@"
Jan 12 17:03:57 brudertuck kernel: /_| \__/ |_\
Jan 12 17:03:57 brudertuck kernel: \__U_/
Jan 12 17:03:58 brudertuck kernel: ls(335): Dax
Jan 12 17:03:58 brudertuck kernel: CPU[1]: local_irq_count[0]
irqs_running[0]
Jan 12 17:03:58 brudertuck kernel: TSTATE: 0000004411009607 TPC:
0000000002022dbc TNPC: 0000000002022dc0 Y: 07000000 Not tainted
Jan 12 17:03:58 brudertuck kernel: g0: fffff8003d412e11 g1:
fffff8003e5de018 g2: 0000000000000001 g3: ffffffffffffffe4
Jan 12 17:03:58 brudertuck kernel: g4: fffff80000000000 g5:
fffee0088af2bf00 g6: fffff8003d410000 g7: 0000000000000000
Jan 12 17:03:58 brudertuck kernel: o0: 000000000000020e o1:
fffff8003e5de01c o2: fffff8003e1df9c0 o3: fffff8003cbfa1c0
Jan 12 17:03:58 brudertuck kernel: o4: 0000000000000002 o5:
0000000000750f28 sp: fffff8003d412e61 ret_pc: fffff8003e5de020
Jan 12 17:03:58 brudertuck kernel: l0: fffff8003e5de000 l1:
fffff8003e5de448 l2: 000000000065c000 l3: fffff8003e5de418
Jan 12 17:03:59 brudertuck kernel: l4: 0000000000000002 l5:
fffff8000137e030 l6: 0000000000000094 l7: fffff8003f71d5a0
Jan 12 17:03:59 brudertuck kernel: i0: 000000000000001c i1:
fffee0088af2bedc i2: 0000000000000000 i3: 0000000000000000
Jan 12 17:03:59 brudertuck kernel: i4: 0000000000000002 i5:
fffff8003e5de000 i6: fffff8003d412f21 i7: 0000000002022fd0
Jan 12 17:03:59 brudertuck kernel: Caller[0000000002022fd0]
Jan 12 17:03:59 brudertuck kernel: Caller[00000000020123c0]
Jan 12 17:03:59 brudertuck kernel: Caller[0000000000548230]
Jan 12 17:03:59 brudertuck kernel: Caller[0000000000548320]
Jan 12 17:03:59 brudertuck kernel: Caller[00000000005484fc]
Jan 12 17:03:59 brudertuck kernel: Caller[000000000203b5c4]
Jan 12 17:03:59 brudertuck kernel: Caller[00000000020382ac]
Jan 12 17:03:59 brudertuck kernel: Caller[0000000000480ad4]
Jan 12 17:03:59 brudertuck kernel: Caller[0000000000481030]
Jan 12 17:03:59 brudertuck kernel: Caller[0000000000410974]
Jan 12 17:03:59 brudertuck kernel: Caller[00000000700f67e4]
Jan 12 17:03:59 brudertuck kernel: Instruction DUMP: f84763d8 b2067fdc
84073fff <c606400f> 80a0e000 12480013 b938a000 c4064009 80a0a000
Jan 12 17:03:59 brudertuck kernel: CPU[0]: local_irq_count[0]
irqs_running[0]
Jan 12 17:03:59 brudertuck kernel: TSTATE: 0000000411009605 TPC:
000000000203e8f4 TNPC: 000000000203e8f8 Y: 15c00000 Not tainted
Jan 12 17:03:59 brudertuck kernel: g0: 0000000000001000 g1:
0000000000000079 g2: fffff8003f167600 g3: 0000000000000000
Jan 12 17:03:59 brudertuck kernel: g4: fffff80000000000 g5:
0000000000000001 g6: fffff8003e478000 g7: 00000000000000ff
Jan 12 17:03:59 brudertuck kernel: o0: 0000000100000000 o1:
00000000efffedc8 o2: 0000000000000006 o3: 0000000000000000
Jan 12 17:03:59 brudertuck kernel: o4: 00000000006ca000 o5:
00000000636b0000 sp: fffff8003e47b1c1 ret_pc: 0000000000013090
Jan 12 17:03:59 brudertuck kernel: l0: 00000000efffed78 l1:
0000000000000000 l2: 0000000000000000 l3: 00000000efffedc8
Jan 12 17:03:59 brudertuck kernel: l4: 0000000000000000 l5:
0000000000000000 l6: 0000000000000000 l7: 0000000000000000
Jan 12 17:03:59 brudertuck kernel: i0: fffff8003e43aa40 i1:
000000000203e500 i2: 0000000000000002 i3: 0000000000000000
Jan 12 17:03:59 brudertuck kernel: i4: fffffffffefefeff i5:
0000000000000000 i6: fffff8003e47b281 i7: 00000000004867d0
To put a xfs filesystem on the metadevice is not possible then i get
these message.Also on a not a metadevice.
brudertuck:/home/riasol# mkfs.xfs -f /dev/sdf1
mkfs.xfs: warning - cannot set blocksize on block device /dev/sdf1:
Invalid argument
meta-data=/dev/sdf1 isize=256 agcount=17, agsize=131072
blks
data = bsize=8192 blocks=2210222, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=0
naming =version 2 bsize=8192
log =internal log bsize=8192 blocks=1000
realtime =none extsz=65536 blocks=0, rtextents=0
and these in the syslog.
Jan 12 17:14:22 brudertuck kernel: sys32_ioctl(mkfs.xfs:357): Unknown
cmd fd(4) cmd(80041271) arg(efffe6e4)
Jan 12 17:14:22 brudertuck kernel: sys32_ioctl(mkfs.xfs:357): Unknown
cmd fd(5) cmd(40041272) arg(efffe6e0)
Jan 12 17:14:41 brudertuck kernel: sys32_ioctl(mkfs.xfs:358): Unknown
cmd fd(4) cmd(80041271) arg(efffe6e4)
Jan 12 17:14:41 brudertuck kernel: sys32_ioctl(mkfs.xfs:358): Unknown
cmd fd(5) cmd(40041272) arg(efffe6e0)
what´s wrong with my system?
sorry for my bad english.
thx
kai
Reply to: