Bug#964866: Acknowledgement (When upgrade from Stretch to Buster my development environment stop working and Arm (sama5d3) never mount his root on NFS) - Solved
Dear maintainer, please close the bug I found a solution. It looks like that Root on NFS require NFSv2. But on Buster is disabled. To enable it add to /etc/default/nfs-kernel-server RPCNFSDOPTS="-V 2" and restart /etc/init.d/nfs-kernel-server . Regards Dan -- Mydatex s r.o. http://www.mydatex.cz email: smo...@mydatex.cz mob: 604200362
Bug#525496: winbind: windbindd crashes after start with SIGBUS
Steve Langasek napsal(a): Dan, Will you please provide the log files that I requested? This bug is probably very easy to fix with the backtraces; it's impossible to fix without them. Sorry I don't reproduce it now. Winbind only crashes when I run it with strace. I cann't reproduce it without strace. Backtrace which I get under strace is unusable I mean. May be I have some bug in configuration. Please close this bug now. Thanks Dan -- Mydatex s r.o. http://www.mydatex.cz email: smo...@mydatex.cz mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525496: [Pkg-samba-maint] Bug#525496: winbind: windbindd crashes after start with SIGBUS
Christian Perrier napsal(a): Quoting Steve Langasek (vor...@debian.org): severity 525496 grave tags 525496 moreinfo thanks On Sat, Apr 25, 2009 at 01:52:20AM +0200, Dan Smolik wrote: Package: winbind Version: 2:3.3.3-1 Severity: critical Justification: breaks unrelated software winbindd crashes after start with SIGBUS. On lenny and squeeze crashes with the same error. Please provide a backtrace for the crash in question. And maybe some more information? We have tons of users who are happily using winbind, so I'm even very tempted to lower the severity to important. The context would then help. What are you using winbind for? What is the output of testparm -s (better than the raw smb.conf file)? Excerpts from the logs would also help (first activate log level = 10) and, in case you can do this, install the samba-dbg package so that we can get more debug information about the crash. Yes I can. But this classic align bug on SPARC I see and report this problem in other packages. It crashes because some data are not aligned to address divide by 4. Regards Dan -- Mydatex s r.o. http://www.mydatex.cz email: smo...@mydatex.cz mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522211: initscripts: System doesn't boot when serial console and bootlogd enabled
Package: initscripts Version: 2.86.ds1-61 Severity: critical Justification: breaks the whole system When use serial console for kernel appending console=ttyS0,115200n8 to kernel command line system boots but stops booting after starting bootlogd. Bootlogd prints some unknown characters to console and system stops. Ctrl-C breaks bootlogd and system boots again. Solution is disable bootlogd when use serial console. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2) Shell: /bin/sh linked to /bin/bash Versions of packages initscripts depends on: ii debianutils 2.30Miscellaneous utilities specific t ii e2fsprogs1.41.3-1ext2/ext3/ext4 file system utiliti ii libc62.7-18 GNU C Library: Shared libraries ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip ii mount2.13.1.1-1 Tools for mounting and manipulatin ii sysvinit-utils 2.86.ds1-61 System-V-like utilities Versions of packages initscripts recommends: ii psmisc22.6-1 Utilities that use the proc filesy initscripts suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522211: initscripts: System doesn't boot when serial console and bootlogd enabled
Petter Reinholdtsen napsal(a): [Daniel Smolik] Solution is disable bootlogd when use serial console. Your solution is correct. Perhaps we should just drop bootlogd completely? It has been badly maintained for years, and upstream recommend against using it. Happy hacking, When don't use serial console it works good for me. I don't know. Regards Dan -- Mydatex s r.o. http://www.mydatex.cz email: smo...@mydatex.cz mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#488669: sparc X server bug
Gaudenz Steinlin napsal(a): Hi Daniel Thanks for your testing. On Tue, Oct 28, 2008 at 11:02:14PM +0100, Daniel Smolik wrote: Hi Gaudenz, I am happy to help you solve this problem on SPARC machine. There is attached log from my E250. I run self compiled 2.6.26.1 kernel. For testing I upgrade machine to Does your self compiled kernel have the patch from http://lkml.org/lkml/2008/6/3/147 reverted or not? If not, could you try a self compiled kernel with this patch reverted? I don't use this patch now. latest SID and run debian kernel to test Xorg. But this kernel crash with: [ 184.755527] irq 13: nobody cared (try booting with the irqpoll option) [ 184.762164] Call Trace: [ 184.764589] [00484538] note_interrupt+0x23c/0x288 [ 184.770057] [00484b5c] handle_fasteoi_irq+0xcc/0xf0 [ 184.775699] [0042d500] handler_irq+0xac/0xd4 [ 184.780733] [004208b4] tl0_irq5+0x1c/0x20 [ 184.785507] [004e9d58] pde_users_dec+0x0/0x34 [ 184.790629] [004be2e0] alloc_inode+0x1c/0x17c [ 184.795749] [004beb7c] iget_locked+0x48/0x124 [ 184.800869] [004e9e14] proc_get_inode+0x38/0x13c [ 184.806251] [004ee3fc] proc_lookup_de+0x68/0xac [ 184.811546] [004ea430] proc_root_lookup+0x14/0x2c [ 184.817014] [004b29f0] do_lookup+0xbc/0x1d8 [ 184.821961] [004b4f00] __link_path_walk+0x890/0xd78 [ 184.827604] [004b541c] path_walk+0x34/0x88 [ 184.832464] [004b574c] do_path_lookup+0x134/0x1cc [ 184.837932] [004b62cc] __path_lookup_intent_open+0x3c/0x88 [ 184.844183] [004b63f0] do_filp_open+0x78/0x7a8 [ 184.849391] handlers: [ 184.851647] [10041934] (sym53c8xx_intr+0x8/0x68 [sym53c8xx]) [ 184.858175] Disabling IRQ #13 Is this with the kernel from the Debian archive or with the kernel I iled for testing purpose and put at http://people.debian.org/~gaudenz/sparc/ ? Your kernel boots fine, but now I have Xorg from experimental. And it's doesn't work too. I dmesg I found this: sunik login: [ 192.328556] PCI: Cannot allocate resource (bogus alignment) 6 [1ff8180:1ff8180] (flags 6200) of :00:05.0 [ 192.339862] PCI: Cannot allocate resource (bogus alignment) 6 [1ff8180:1ff8180] (flags 6200) of :00:05.0 I now try downgrade Xorg from experimental to SID. Dan I must say again that problem on SPARC machines with Xorg is problem with Xorg not with kernel. In principle I agree with you. But to fix the X server side of the problem we would have to upgrade to the X server currently in experimental. I don't think that it's possible to upgrade lenny to this version at this moment right before the release. So I'm trying to find out if the problem is also solved by reverting the problematic kernel change. And as you have noticed yourself, the X server in experimental has other problems. So it's not really suitable for a release. Please look at http://lkml.org/lkml/2008/6/3/147 http://lkml.org/lkml/2008/6/3/147 I'm already aware of this. Gaudenz -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488669: sparc X server bug
Gaudenz Steinlin napsal(a): Hi Daniel Thanks for your testing. On Tue, Oct 28, 2008 at 11:02:14PM +0100, Daniel Smolik wrote: Hi Gaudenz, I am happy to help you solve this problem on SPARC machine. There is attached log from my E250. I run self compiled 2.6.26.1 kernel. For testing I upgrade machine to Does your self compiled kernel have the patch from http://lkml.org/lkml/2008/6/3/147 reverted or not? If not, could you try a self compiled kernel with this patch reverted? latest SID and run debian kernel to test Xorg. But this kernel crash with: [ 184.755527] irq 13: nobody cared (try booting with the irqpoll option) [ 184.762164] Call Trace: [ 184.764589] [00484538] note_interrupt+0x23c/0x288 [ 184.770057] [00484b5c] handle_fasteoi_irq+0xcc/0xf0 [ 184.775699] [0042d500] handler_irq+0xac/0xd4 [ 184.780733] [004208b4] tl0_irq5+0x1c/0x20 [ 184.785507] [004e9d58] pde_users_dec+0x0/0x34 [ 184.790629] [004be2e0] alloc_inode+0x1c/0x17c [ 184.795749] [004beb7c] iget_locked+0x48/0x124 [ 184.800869] [004e9e14] proc_get_inode+0x38/0x13c [ 184.806251] [004ee3fc] proc_lookup_de+0x68/0xac [ 184.811546] [004ea430] proc_root_lookup+0x14/0x2c [ 184.817014] [004b29f0] do_lookup+0xbc/0x1d8 [ 184.821961] [004b4f00] __link_path_walk+0x890/0xd78 [ 184.827604] [004b541c] path_walk+0x34/0x88 [ 184.832464] [004b574c] do_path_lookup+0x134/0x1cc [ 184.837932] [004b62cc] __path_lookup_intent_open+0x3c/0x88 [ 184.844183] [004b63f0] do_filp_open+0x78/0x7a8 [ 184.849391] handlers: [ 184.851647] [10041934] (sym53c8xx_intr+0x8/0x68 [sym53c8xx]) [ 184.858175] Disabling IRQ #13 Is this with the kernel from the Debian archive or with the kernel I compiled for testing purpose and put at http://people.debian.org/~gaudenz/sparc/ ? I downgraded Xorg to SID and there is a result: ==) Log file: /var/log/Xorg.0.log, Time: Thu Oct 30 21:36:11 2008 (++) Using config file: /root/xorg.conf.new (WW) INVALID MEM ALLOCATION b: 0x2 e: 0x3 correcting mmap failure: Invalid argument Fatal server error: xf86MapDomainMem(): mmap() failure sunik:~# uname -a Linux sunik 2.6.26-1-sparc64 #1 Sun Oct 26 17:42:45 UTC 2008 sparc64 GNU/Linux I mean that patch doesn't help. Dan I must say again that problem on SPARC machines with Xorg is problem with Xorg not with kernel. In principle I agree with you. But to fix the X server side of the problem we would have to upgrade to the X server currently in experimental. I don't think that it's possible to upgrade lenny to this version at this moment right before the release. So I'm trying to find out if the problem is also solved by reverting the problematic kernel change. And as you have noticed yourself, the X server in experimental has other problems. So it's not really suitable for a release. Please look at http://lkml.org/lkml/2008/6/3/147 http://lkml.org/lkml/2008/6/3/147 I'm already aware of this. Gaudenz -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488669: sparc X server bug
Gaudenz Steinlin napsal(a): Hi Daniel Thanks for your testing. On Tue, Oct 28, 2008 at 11:02:14PM +0100, Daniel Smolik wrote: Hi Gaudenz, I am happy to help you solve this problem on SPARC machine. There is attached log from my E250. I run self compiled 2.6.26.1 kernel. For testing I upgrade machine to Does your self compiled kernel have the patch from http://lkml.org/lkml/2008/6/3/147 reverted or not? If not, could you try a self compiled kernel with this patch reverted? latest SID and run debian kernel to test Xorg. But this kernel crash with: [ 184.755527] irq 13: nobody cared (try booting with the irqpoll option) [ 184.762164] Call Trace: [ 184.764589] [00484538] note_interrupt+0x23c/0x288 [ 184.770057] [00484b5c] handle_fasteoi_irq+0xcc/0xf0 [ 184.775699] [0042d500] handler_irq+0xac/0xd4 [ 184.780733] [004208b4] tl0_irq5+0x1c/0x20 [ 184.785507] [004e9d58] pde_users_dec+0x0/0x34 [ 184.790629] [004be2e0] alloc_inode+0x1c/0x17c [ 184.795749] [004beb7c] iget_locked+0x48/0x124 [ 184.800869] [004e9e14] proc_get_inode+0x38/0x13c [ 184.806251] [004ee3fc] proc_lookup_de+0x68/0xac [ 184.811546] [004ea430] proc_root_lookup+0x14/0x2c [ 184.817014] [004b29f0] do_lookup+0xbc/0x1d8 [ 184.821961] [004b4f00] __link_path_walk+0x890/0xd78 [ 184.827604] [004b541c] path_walk+0x34/0x88 [ 184.832464] [004b574c] do_path_lookup+0x134/0x1cc [ 184.837932] [004b62cc] __path_lookup_intent_open+0x3c/0x88 [ 184.844183] [004b63f0] do_filp_open+0x78/0x7a8 [ 184.849391] handlers: [ 184.851647] [10041934] (sym53c8xx_intr+0x8/0x68 [sym53c8xx]) [ 184.858175] Disabling IRQ #13 Is this with the kernel from the Debian archive or with the kernel I compiled for testing purpose and put at http://people.debian.org/~gaudenz/sparc/ ? I must say again that problem on SPARC machines with Xorg is problem with Xorg not with kernel. In principle I agree with you. But to fix the X server side of the problem we would have to upgrade to the X server currently in experimental. I don't think that it's possible to upgrade lenny to this version at this moment right before the release. So I'm trying to find out if the problem is also solved by reverting the problematic kernel change. And as you have noticed yourself, the X server in experimental has other problems. So it's not really suitable for a release. Please look at http://lkml.org/lkml/2008/6/3/147 http://lkml.org/lkml/2008/6/3/147 I remember that I can't get X working when I upgrade my Sparc machines from 2.4 to 2.6. I mean that on multi domain PCI machines Xorg never work on 2.6.x. I ,may be year ago, try XFree86 and it's work. Regards Dan -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488669: sparc X server bug
Gaudenz Steinlin napsal(a): Hi Daniel back in September you exchanged some mails with Riku Voipio about a bug in the X server on SPARC. In order to resolve this bug I need some further information. First of all I'm not really sure if bug in which you participated[1] is really the same as another SPARC X server issue (see [2]) which is clearly caused by the kernel change you refer to in the bug log. The first bug reporter seems to be running a kernel version which shouldn't be affected by the kernel change. It could well be that this is an entirely different bug. Also the X server logs in the two bugs don't really match. Therefore I would be interested in the log of the failing X server. You will usually find the log in /var/log/Xorg.0.log. Also it would be interesting if you only experience the bug with kernels 2.6.26-rc1 and above or if it also exists with older kernels on your machine. Thanks for your cooperation. Hi Gaudenz, today I updated Xorg to experimental as situation is better. Card is now first time detected but Xserver crash: II) Loading /usr/lib/xorg/modules/input//kbd_drv.so (II) Module kbd: vendor=X.Org Foundation compiled for 1.4.99.906, module version = 1.3.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 2.1 (II) GLINT: driver for 3Dlabs chipsets: gamma, gamma2, ti_pm2, ti_pm, r4, pm4, pm3, pm2v, pm2, pm, 300sx, 500tx, mx, delta (II) Primary Device is: PCI [EMAIL PROTECTED]:05:0 (WW) Falling back to old probe method for glint (--) Assigning device section with no busID to primary device (--) Chipset pm2v found (II) resource ranges after xf86ClaimFixedResources() call: (II) resource ranges after probing: (==) GLINT(0): Depth 8, (--) framebuffer bpp 8 (==) GLINT(0): Default visual is PseudoColor (==) GLINT(0): Using gamma correction (1.0, 1.0, 1.0) (==) GLINT(0): Using HW cursor (--) GLINT(0): Not using Linux framebuffer device (--) GLINT(0): Chipset: pm2v (--) GLINT(0): Linear framebuffer at 0x100 (--) GLINT(0): MMIO registers at 0x3 Backtrace: Fatal server error: Caught signal 11. Server aborting Dan -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488669: sparc X server bug
Gaudenz Steinlin napsal(a): Hi Daniel back in September you exchanged some mails with Riku Voipio about a bug in the X server on SPARC. In order to resolve this bug I need some further information. First of all I'm not really sure if bug in which you participated[1] is really the same as another SPARC X server issue (see [2]) which is clearly caused by the kernel change you refer to in the bug log. The first bug reporter seems to be running a kernel version which shouldn't be affected by the kernel change. It could well be that this is an entirely different bug. Also the X server logs in the two bugs don't really match. Therefore I would be interested in the log of the failing X server. You will usually find the log in /var/log/Xorg.0.log. Also it would be interesting if you only experience the bug with kernels 2.6.26-rc1 and above or if it also exists with older kernels on your machine. Hi Gaudenz, I am happy to help you solve this problem on SPARC machine. There is attached log from my E250. I run self compiled 2.6.26.1 kernel. For testing I upgrade machine to latest SID and run debian kernel to test Xorg. But this kernel crash with: [ 184.755527] irq 13: nobody cared (try booting with the irqpoll option) [ 184.762164] Call Trace: [ 184.764589] [00484538] note_interrupt+0x23c/0x288 [ 184.770057] [00484b5c] handle_fasteoi_irq+0xcc/0xf0 [ 184.775699] [0042d500] handler_irq+0xac/0xd4 [ 184.780733] [004208b4] tl0_irq5+0x1c/0x20 [ 184.785507] [004e9d58] pde_users_dec+0x0/0x34 [ 184.790629] [004be2e0] alloc_inode+0x1c/0x17c [ 184.795749] [004beb7c] iget_locked+0x48/0x124 [ 184.800869] [004e9e14] proc_get_inode+0x38/0x13c [ 184.806251] [004ee3fc] proc_lookup_de+0x68/0xac [ 184.811546] [004ea430] proc_root_lookup+0x14/0x2c [ 184.817014] [004b29f0] do_lookup+0xbc/0x1d8 [ 184.821961] [004b4f00] __link_path_walk+0x890/0xd78 [ 184.827604] [004b541c] path_walk+0x34/0x88 [ 184.832464] [004b574c] do_path_lookup+0x134/0x1cc [ 184.837932] [004b62cc] __path_lookup_intent_open+0x3c/0x88 [ 184.844183] [004b63f0] do_filp_open+0x78/0x7a8 [ 184.849391] handlers: [ 184.851647] [10041934] (sym53c8xx_intr+0x8/0x68 [sym53c8xx]) [ 184.858175] Disabling IRQ #13 I must say again that problem on SPARC machines with Xorg is problem with Xorg not with kernel. Please look at http://lkml.org/lkml/2008/6/3/147 http://lkml.org/lkml/2008/6/3/147 Thanks Dan X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-7) Current Operating System: Linux sunik 2.6.26 #2 SMP Mon Jul 21 19:49:01 CEST 2008 sparc64 Build Date: 01 October 2008 03:55:43PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Oct 28 20:57:48 2008 (II) No APM support in BIOS or kernel (II) Loader magic: 0x1c0c78 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: pcidata (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 1.4.2, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (--) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:01:0: chip 108e,1000 card , rev 01 class 06,80,00 hdr 80 (II) PCI: 00:01:1: chip 108e,1001 card , rev 01 class 02,00,00 hdr 80 (II) PCI: 00:03:0: chip 1000,000f card , rev 14 class 01,00,00 hdr 80 (II) PCI: 00:03:1: chip 1000,000f card , rev 14 class 01,00,00 hdr 80 (II) PCI: 00:04:0: chip 1000,000f card 1000,1000 rev 14 class 01,00,00 hdr 80 (II) PCI: 00:04:1: chip 1000,000f card 1000,1000 rev 14 class 01,00,00 hdr 80 (II) PCI: 00:05:0: chip 3d3d,0009 card 1227,0006 rev 01 class 03,80,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,0), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:5:0) 3DLabs Permedia II 2D+3D rev 1, Mem @ 0x0002/17, 0x0080/23, 0x0100/23, BIOS @ 0x0180/16 List of video drivers: rendition mach64 neomagic r128 sunffb glint apm ati ark mga radeon chips cirrus dummy i128 i740 imstt nv radeonhd s3virge savage tdfx trident v4l siliconmotion suntcx suncg6 sunbw2 suncg14 suncg3 sunleo fbdev vesa vga (II) LoadModule: rendition (II) Loading
Bug#488669: xserver-xorg: X fails to start on a SUN ULTRA 5
Riku Voipio napsal(a): On Thu, Sep 04, 2008 at 09:24:05PM +0200, Daniel Smolik wrote: Riku Voipio napsal(a): xf86DomainMem() : mmap() failure Can you try strace X to see what exactly is being mmap'd? Also, can you try if upgrading to 2.6.26-4 kernel helps? Yes it looks like that driver starts open some files in proc: open(/proc/bus/pci/:00/01.7, O_RDONLY) = -1 ENOENT (No such file or direc stat64(/proc/bus/pci/:00, {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0 open(/proc/bus/pci/:00/02.0, O_RDONLY) = -1 ENOENT (No such file or direc stat64(/proc/bus/pci/:00, {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0 open(/proc/bus/pci/:00/02.0, O_RDONLY) = -1 ENOENT (No su but this files doesn't exists. It's not unusual, X and other applications try open a lot of files that may not exist. What we are interested is the strace messages around the mmap() error. If unsure, just pass the entire strace log as a attachment. Yes you are rigt. I read some posts in Sparc64 mailing list and mean that only solution for this problem is newer Xserver that uderstand new kernel interface. do you have poiters to these discussions? Yes there David Miller explain this problem. http://lkml.org/lkml/2008/6/3/147 Regards Dan -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488669: xserver-xorg: X fails to start on a SUN ULTRA 5
Riku Voipio napsal(a): xf86DomainMem() : mmap() failure Can you try strace X to see what exactly is being mmap'd? Also, can you try if upgrading to 2.6.26-4 kernel helps? Yes it looks like that driver starts open some files in proc: open(/proc/bus/pci/:00/01.7, O_RDONLY) = -1 ENOENT (No such file or direc stat64(/proc/bus/pci/:00, {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0 open(/proc/bus/pci/:00/02.0, O_RDONLY) = -1 ENOENT (No such file or direc stat64(/proc/bus/pci/:00, {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0 open(/proc/bus/pci/:00/02.0, O_RDONLY) = -1 ENOENT (No su but this files doesn't exists. I read some posts in Sparc64 mailing list and mean that only solution for this problem is newer Xserver that uderstand new kernel interface. Regards Dan -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493887: xserver-xorg-video-glint: Crash after start message output ****INVALID MEM ALLOCATION****
Julien Cristau napsal(a): On Tue, Aug 5, 2008 at 20:14:38 +0200, Dan Smolik wrote: Package: xserver-xorg-video-glint Version: 1:1.1.1-3 Severity: grave Justification: renders package unusable This driver was long time unusable on multidomain PCI platform like Sun E250/450. But after rewrote PCI code in Xorg situation goes to better. The PCI code rewrite you're talking about lands in xserver 1.5, which you don't seem to be using. Sorry I don't uderstand Xserver versioning very well. I hope than Xserver version 1.5 will go to SID now or in near future. Because now Xserver crashed from version to version diferently. Now is card detected but Xserver crashed with (EE) Failed to load module type1 (module does not exist, 0) (WW) INVALID MEM ALLOCATION b: 0x2 e: 0x3 correcting (WW) INVALID MEM ALLOCATION b: 0x80 e: 0xff correcting (WW) INVALID MEM ALLOCATION b: 0x100 e: 0x17f correcting Backtrace: Fatal server error: Caught signal 11. Server aborting NeúspϚnÏ ukonèen (SIGABRT) In reportbug is system impropertly detected: Right is: Linux sunik 2.6.26 #2 SMP Mon Jul 21 19:49:01 CEST 2008 sparc64 GNU/Linux davem probably changed something in the kernel that broke this. *shrug* Use an old kernel, I guess. Yes I know. But it doesn't work on any 2.6 on Sun platform I mean. Cheers Dan Cheers, Julien -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452069: nfs-kernel-server: broken NFS server on Thecus N2100
Martin Michlmayr napsal(a): * Daniel Smolik [EMAIL PROTECTED] [2007-11-20 11:35]: I read this bug report, but I mean that this is problem nfsd. I just transfered 9 GB from my PC to the N2100 without any problems. I used an unreleased kernel (2.6.23 plus some patches) though. Great, can you give me link to this patchset ? Can you tell me a) how much data you usually transfer to see this problem and b) what options you have listed in /etc/exports. I try one 750M file and transfer never complete . cat /etc/exports /home/zaloha *(rw,no_root_squash,no_subtree_check) If you copy large file did you see this situation? 1) Copying start very fast and in mc shows 50Mbs 2) after while stops and wait 3) speed slowdown to ~ 8Mbs 4) get i/o error. Regards Dan Smolik -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452069: nfs-kernel-server: broken NFS server on Thecus N2100
Martin Michlmayr napsal(a): * Daniel Smolik [EMAIL PROTECTED] [2007-11-21 22:00]: I just transfered 9 GB from my PC to the N2100 without any problems. I used an unreleased kernel (2.6.23 plus some patches) though. Great, can you give me link to this patchset ? Only if you have (or can make) a serial console for your N2100 (in case something goes wrong when installing the package). No problem of course I have serial console :-) I load kernel with tftp :-) Dan -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452069: nfs-kernel-server: broken NFS server on Thecus N2100
Martin Michlmayr napsal(a): * Martin Michlmayr [EMAIL PROTECTED] [2007-11-21 21:43]: I just transfered 9 GB from my PC to the N2100 without any problems. I used an unreleased kernel (2.6.23 plus some patches) though. OK, I see it with 2.6.22... and it happens quite often too. And with 2.6.23 is it OK ? Dan -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452069: nfs-kernel-server: broken NFS server on Thecus N2100
New infomation switching to nfs-user-server solve the problem. CPU usage is high but work without problem. Regards Dan Smolik -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452069: broken NFS server on Thecus N2100
Samba works OK too. Dan -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452069: nfs-kernel-server: broken NFS server on Thecus N2100
Package: nfs-kernel-server Version: 1:1.1.1-3 Severity: critical Justification: causes serious data loss When I transfer files from an x86 machine to the arm nfs server, files arrive corrupted (md5sum mismatch) and dmesg/syslog shows: kernel: nfsd: non-standard errno: -14 A try upload data with ftp and it works OK but may be slow 5MB/s on 100Mbit network. Reading data from NFS share is broken too. I get the same messages from NFS server. I try Etch an Sid a situation is the same. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: arm (armv5tel) Kernel: Linux 2.6.22-3-iop32x Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages nfs-kernel-server depends on: ii libblkid1 1.40.2-1 block device id library ii libc6 2.6.1-6GNU C Library: Shared libraries ii libcomerr21.40.2-1 common error description library ii libgssglue1 0.1-1 mechanism-switch gssapi library ii libkrb53 1.6.dfsg.3~beta1-2 MIT Kerberos runtime libraries ii libnfsidmap2 0.20-0 An nfs idmapping library ii librpcsecgss3 0.17-1 allows secure rpc communication us ii libwrap0 7.6.dbs-14 Wietse Venema's TCP wrappers libra ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip ii nfs-common1:1.1.1-3 NFS support files common to client ii ucf 3.003 Update Configuration File: preserv nfs-kernel-server recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452069: nfs-kernel-server: broken NFS server on Thecus N2100
Martin Michlmayr napsal(a): * Daniel Smolik [EMAIL PROTECTED] [2007-11-20 09:44]: Package: nfs-kernel-server When I transfer files from an x86 machine to the arm nfs server, files arrive corrupted (md5sum mismatch) and dmesg/syslog shows: kernel: nfsd: non-standard errno: -14 We had #404447 in the past, a problem on NSLU2 (arm) with the same error message. However, in that case, we were fairly sure in the end that it was due to the Ethernet driver. I'm not sure this applies to this bug since you say that nfs-user-server works. The other curious thing is that I tried NFS on Thecus N2100 when I investigated #404447 and it worked fine for me (but that was with 2.6.17 or 2.6.18). I read this bug report, but I mean that this is problem nfsd. I try ftp upload/download, smb upload/download, nfs-user-server upload/download and all works. But when switch to nfs-kernel-server and copying files with mc, copying starts very fast and after this stops, wait while, slowdown and after while I get i/o error. Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452069: nfs-kernel-server: broken NFS server on Thecus N2100
Martin Michlmayr napsal(a): * Daniel Smolik [EMAIL PROTECTED] [2007-11-20 11:35]: I read this bug report, but I mean that this is problem nfsd. Just to make sure, do you think you could also try with 2.6.18? Yes as I wrote, I previous run Etch with 2.6.18. And symptom are the same. Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419874: amavis-stat patch
Here is patch made with diff -ur then solves my problem. Dan --- amavis-stats.php 2006-12-04 08:24:00.0 +0100 +++ amavis-stats.php.new 2007-06-20 11:24:57.0 +0200 @@ -57,7 +57,7 @@ */ global $asVersion; -$asVersion = ; +$asVersion = 0.1.12-7.4; // The rrdstep value MUST match that which is used by the perl script. // don't change one without the other. @@ -106,7 +106,7 @@ } array_shift($output); - + foreach ($output as $index = $value) { $retval[calcpr][$index] = $value; } @@ -645,7 +645,7 @@ $opts[] = COMMENT:\\n; $opts[] = COMMENT:amavis-stats v$asVersion ; -$opts[] = COMMENT:$enddate \\r; +$opts[] = COMMENT:. str_replace(:, \:, $enddate) . \\r; asDbg($opts); $ret = rrd_graph(/usr/share/amavis-stats/$img , $opts, count($opts)); @@ -769,7 +769,7 @@ } */ $opts[] = COMMENT:amavis-stats v$asVersion ; -$opts[] = COMMENT:$enddate . str_replace(:, \:, $enddate) . \\r; +$opts[] = COMMENT:. str_replace(:, \:, $enddate) . \\r; /* * debugging - graph definitions
Bug#423222: Acknowledgement (SIGBUS in _nss_mdns4_gethostbyaddr_r on SPARC)
Main problem is name of second server. If I rename it to some name without numbers crash stops. Regards Dan Smolik -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419459: Addning info
Hi, I am 100% sure that my colleague found fundamentals of this bug. On SPARC linux is used thread safe version of gethostbyname genthostbyname_r. This function have third argument char buffer. But if this buffer is not correctly aligned (on SPARC / 4 ) program crashed with BUSS ERROR. I attach demonstrate program to test this issue. If you change size of buffer from 1002 to 1000 program start working. I mean that simple workaround on SPARC is not use gethostbyname_r. Regards Dan -- Mydatex s r.o. http://www.mydatex.cz email: [EMAIL PROTECTED] mob: 604200362 tel: 226210085 #includestdio.h #includenetdb.h #include sys/socket.h #include netdb.h #include netinet/in.h #include netinet/tcp.h #include arpa/inet.h extern int h_errno; int main(void) { int ret; const char *name=karotka; char buf[1002]; int tmp_errno,buflen; struct hostent tmp_hostent,*hp; //struct hostent_data hd; int size; buflen=1000; //size=sizeof(struct hostent_data); //printf(size=%d\n,size); printf(Align buff result=%p,buffer=%p,buflen=%d\n,tmp_hostent,buf,buflen); ret=gethostbyname_r(name,tmp_hostent, buf,buflen,hp,tmp_errno); printf(ret:=%d\n,ret); if(ret==0) { if(hp) { printf(Lenght:=%d\n,hp-h_length); printf(Addr:=%X\n,hp-h_addr); printf(Name:=%s\n,hp-h_name); } } return(ret); }
Bug#386541: After latest upgrade mozilla crash when access slovnik.seznam.cz and click to some select button
Package: mozilla Version: 2:1.7.8-1sarge7.2.1 Severity: grave Justification: renders package unusable After upgrade to latest debian package mozilla crasehs when access http://slovnik.seznam.cz and click to any select box. I run strace an see that mozilla get SIGSEGV -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17.9 Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2) Versions of packages mozilla depends on: ii dpkg 1.10.28 Package maintenance system for Deb ii mozilla-browser 2:1.7.8-1sarge7.2.1 The Mozilla Internet application s ii mozilla-mailnews 2:1.7.8-1sarge7.2.1 The Mozilla Internet application s ii mozilla-psm 2:1.7.8-1sarge7.2.1 The Mozilla Internet application s -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386541: Firefox crashed too
A tested Firefox from Sarge on slovnik.seznam.cz and crashed too. Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386541: downgrade to 1.7.8-1sarge7.1 helps
I use previous version of mozilla from http://snapshot.debian.net/ (great site) and it works without problem. Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386541: downgrade to 1.7.8-1sarge7.1 helps
Alexander Sack - Debian Bugmail napsal(a): On Fri, Sep 08, 2006 at 02:24:58PM +0200, Daniel Smolik wrote: I use previous version of mozilla from http://snapshot.debian.net/ (great site) and it works without problem. Dan new packages are on its way. You can get a cure on i386 now by using packages from my security preview archive http://www.asoftsite.org/apt-archives.html. If you like, keep the apt lines and report issues with packages from there to me or file a bug. Testers (like you) are most critical to prevent such glitches to happen in future. - Alexander p.s. please take care that the bug is listed as To: or CC: when replying to this mail (e.g. /reply-all/). Thanks for fast response. I am not at home now but I test 1sarge7.2.2 as soon as possible. Regards Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386541: downgrade to 1.7.8-1sarge7.1 helps
Alexander Sack - Debian Bugmail napsal(a): On Fri, Sep 08, 2006 at 02:24:58PM +0200, Daniel Smolik wrote: I use previous version of mozilla from http://snapshot.debian.net/ (great site) and it works without problem. Dan new packages are on its way. You can get a cure on i386 now by using packages from my security preview archive http://www.asoftsite.org/apt-archives.html. If you like, keep the apt lines and report issues with packages from there to me or file a bug. Testers (like you) are most critical to prevent such glitches to happen in future. - Alexander p.s. please take care that the bug is listed as To: or CC: when replying to this mail (e.g. /reply-all/). I test mozilla form your archive and problem that I have with previous version was solved. Super. I will keep your archive in my sources.list. Regards Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]