Bug#403364: SunBlade 150 problems - can anyone confirm?

On 17/12/2006, at 5:55 AM, Thomas Köllmann wrote: On Sat, 16 Dec 2006 10:38:58 -0800 Jurij Smakov <[EMAIL PROTECTED]> wrote: Please try booting it with the boot parameter video=atyfb:off, i.e. instead of just pressing enter at the silo boot prompt type Linux video=atyfb:off Yes, that works.

Bug#403224: initramfs-tools: confirmation with sarge testing

On Sat, Dec 16, 2006 at 09:38:49PM +0100, Thomas Koch wrote: > Package: initramfs-tools > Version: 0.85d > Followup-For: Bug #403224 > > I'm running a Debian testing with all packages updated to the newest version. > I made the last update this morning and I think that it included also > initramf

Bug#403426: linux-image-2.6.18-3-ixp4xx: kernel corrupts LUKS partition header on arm NSLU2

Just an addendum that once the partition is actually mounted using the straced cryptsetup, everything seems to work ok, I can't get corruption. I just saw the discussion on #394392 mm/msync issue... this may be the same thing presumably strace changes the timing... If so, this may be a good t

Bug#403426: linux-image-2.6.18-3-ixp4xx: kernel corrupts LUKS partition header on arm NSLU2

Package: linux-image-2.6.18-3-ixp4xx Version: 2.6.18-8 Severity: critical Justification: causes serious data loss This is on an NSLU2, I wanted to use it to access some disks that I had used previously on another system that had encrypted partitons. However, when I tried cryptsetup luksOpen, I go

Bug#403224: initramfs-tools: confirmation with sarge testing

On Sat, Dec 16, 2006 at 09:38:49PM +0100, Thomas Koch wrote: > Package: initramfs-tools > Version: 0.85d > Followup-For: Bug #403224 > > I'm running a Debian testing with all packages updated to the newest version. > I made the last update this morning and I think that it included also > initramf

Bug#402707: reproducible: hash check failed

Hi, I just wanted to note that I've been seeing the same error on my unstable amd64 system for a few days now, with stock Debian kernel version 2.6.18-3-amd64 I'm nor sure which kernel revision introduced the problem, but it likely was on december 12th where it first occurred for me (I'm not using

Bug#403405: video1394 broken on linux-image-2.6.18-3-686

severity 403405 important thanks On Sat, Dec 16, 2006 at 11:41:37PM +0100, Holger Levsen wrote: > grabbing video from a machine with the attached configuration doesnt work > with > the kernel currently in etch. > > videoetch:~# dvgrab --size 0 --format qt foo > "" 0.00 MB 0 frames

Bug#403405: video1394 broken on linux-image-2.6.18-3-686

package: linux-2.6 version: 2.6.18-7 severity: serious Hi, grabbing video from a machine with the attached configuration doesnt work with the kernel currently in etch. videoetch:~# dvgrab --size 0 --format qt foo "" 0.00 MB 0 frames

Re: Recent mm changes leading to filesystem corruption?

* Peter Zijlstra <[EMAIL PROTECTED]> [2006-12-16 21:55]: > What is not clear from all these reports is what architectures this is > seen on. I suspect some of them are i686, which together with the > explicit mention of ARM make it a cross platform issue. Problems have been seen at least on x86, x

Re: Recent mm changes leading to filesystem corruption?

On Sat, 2006-12-16 at 16:50 +0100, Martin Michlmayr wrote: > Debian recently applied a number of mm changes that went into 2.6.19 > to their 2.6.18 kernel for LSB 3.1 compliance (msync() had problems > before). Since then, some filesystem corruption has been observed > which can be traced back to

Bug#403224: initramfs-tools: confirmation with sarge testing

Package: initramfs-tools Version: 0.85d Followup-For: Bug #403224 I'm running a Debian testing with all packages updated to the newest version. I made the last update this morning and I think that it included also initramfs-tools. Afterwards I couldn't boot anymore. Using the initrd...bak file

Processed: this appears to be a fuse error

Processing commands for [EMAIL PROTECTED]: > retitle 402876 cannot stat FUSE mounts (e.g. sshfs, encfs) Bug#402876: encfs: cannot stat mounts on ARM Changed Bug title. > reassign 402876 linux-image-2.6.18-3-iop32x Bug#402876: cannot stat FUSE mounts (e.g. sshfs, encfs) Bug reassigned from packag

Bug#334104: RFC: workaround for dmfe/tulip module problem

On Fri, Dec 15, 2006 at 10:13:53PM +, Richard Mortimer wrote: > Hi Jurij, > > Did you get around to building the mini-iso image? I'm happy to test > when you have it ready. Hi Richard, Sorry for the delay. The mini.iso (5.4M) with the kernel modules which have the proposed patch incorporate

Re: Recent mm changes leading to filesystem corruption?

On Sat, 16 Dec 2006, Martin Michlmayr wrote: > * Hugh Dickins <[EMAIL PROTECTED]> [2006-12-16 18:20]: > > Very disturbing. I'm not aware of any problem with them, and we > > surely wouldn't have released 2.6.19 with any known-corrupting patches > > in. There's some doubts about 2.6.19 itself in t

Bug#403364: SunBlade 150 problems - can anyone confirm?

On Sat, Dec 16, 2006 at 07:55:13PM +0100, Thomas Köllmann wrote: > > Please try booting it with the boot parameter video=atyfb:off, i.e. > > instead of just pressing enter at the silo boot prompt type > > > > Linux video=atyfb:off > > Yes, that works. > > Does this have any drawbacks regardin

Bug#403364: SunBlade 150 problems - can anyone confirm?

On Saturday 16 December 2006 17:58, Jurij Smakov wrote: > Since you are the only person who reported such a problem so far, I > feel that severity is a bit too high, so I'm dropping it to > 'important' for now. I'm also CC'ing this message to the debian-sparc > mailing list to ask whether anybody e

Bug#403364: SunBlade 150 problems - can anyone confirm?

On Sat, 16 Dec 2006 10:38:58 -0800 Jurij Smakov <[EMAIL PROTECTED]> wrote: > On Sat, Dec 16, 2006 at 07:32:29PM +0100, Thomas Köllmann wrote: > > > atyfb: 3D RAGE XL (Mach64 GR, PCI-33) [0x4752 rev 0x27] > > atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 235 MHz PLL, 83 Mhz MCLK, 63 > > MHz XCLK Cons

Re: Recent mm changes leading to filesystem corruption?

* Hugh Dickins <[EMAIL PROTECTED]> [2006-12-16 18:20]: > Very disturbing. I'm not aware of any problem with them, and we > surely wouldn't have released 2.6.19 with any known-corrupting patches > in. There's some doubts about 2.6.19 itself in the links below: were > it not for those, I'd suspect

Bug#401006: Related issue reported on lmkl

Here's something that could be related (APT seems to call msync as well): -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#403364: SunBlade 150 problems - can anyone confirm?

On Sat, Dec 16, 2006 at 07:32:29PM +0100, Thomas Köllmann wrote: > No, only the onboard ATI card: > > atyfb: 3D RAGE XL (Mach64 GR, PCI-33) [0x4752 rev 0x27] > atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 235 MHz PLL, 83 Mhz MCLK, 63 MHz > XCLK > Console: switching to colour frame buffer device 14

Bug#403364: SunBlade 150 problems - can anyone confirm?

Hi, Jurij! On Sat, 16 Dec 2006 08:58:55 -0800 Jurij Smakov <[EMAIL PROTECTED]> wrote: > Since you are the only person who reported such a problem so far, I > feel that severity is a bit too high, so I'm dropping it to > 'important' for now. Sure, whatever you feel is in order. > Do you have

Re: Recent mm changes leading to filesystem corruption?

On Sat, 16 Dec 2006, Martin Michlmayr wrote: > Debian recently applied a number of mm changes that went into 2.6.19 > to their 2.6.18 kernel for LSB 3.1 compliance (msync() had problems > before). Since then, some filesystem corruption has been observed > which can be traced back to these mm chan

Re: [patch, attach, RFC] usb-serial: ti_usb removing firmware

On 12/16/06, Al Borchers <[EMAIL PROTECTED]> wrote: Oleg -- Some comments. I will be away until next Tuesday, when I can do more with this. Thanks. * We can't remove the compiled in firmware--that would break things until users get and install the firmware images. * What I did in my pat

Bug#403364: SunBlade 150 problems - can anyone confirm?

severity 403364 important thanks Hi Thomas, On Sat, Dec 16, 2006 at 06:05:52PM +0100, Thomas Koellmann wrote: > Package: linux-image-2.6.18-3-sparc64 > Version: 2.6.18-7 > Severity: critical > Justification: breaks the whole system Since you are the only person who reported such a problem so far

Processed: SunBlade 150 problems - can anyone confirm?

Processing commands for [EMAIL PROTECTED]: > severity 403364 important Bug#403364: linux-image-2.6.18-3-sparc64: Does not boot on a Sun Blade 150 Severity set to `important' from `critical' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system a

Bug#403364: linux-image-2.6.18-3-sparc64: Does not boot on a Sun Blade 150

Package: linux-image-2.6.18-3-sparc64 Version: 2.6.18-7 Severity: critical Justification: breaks the whole system This kernel, which seems currently to be the latest in testing/etch, hangs on my Sun Blade 150 after displaying "Booting Linux" (at that stage where linux-image-2.6.16-2-sparc64 switc

Recent mm changes leading to filesystem corruption?

Debian recently applied a number of mm changes that went into 2.6.19 to their 2.6.18 kernel for LSB 3.1 compliance (msync() had problems before). Since then, some filesystem corruption has been observed which can be traced back to these mm changes. Is anyone aware of problems with these patches?

Re: Scheduling linux-2.6 2.6.18-9

* Holger Levsen wrote: > On Friday 15 December 2006 18:08, Frederik Schueler wrote: > > 1. new vserver patch, breaks ABI > > which version of the patch is it? >2.0.2.2-rc6 and <2.0.2.2-rc9 has > a critical bug which causes kernel oops if there is other traffic > while restarting vservers. http://

Bug#403224: initramfs-tools: Unbootable after today Sid dist-upgrade (version 0.85d)

On Sat, 16 Dec 2006, Benjamí Villoslada wrote: > El Dissabte 16 Desembre 2006 08:45, maximilian attems va escriure: > > sh -x mkinitramfs -o /tmp/foo > > Is long long, I attach it :) ok thanks, still no evident error at any places that changed for 0.85d, nor at any other place. can you please s

Re: Scheduling linux-2.6 2.6.18-9

Hi, On Friday 15 December 2006 18:08, Frederik Schueler wrote: > 1. new vserver patch, breaks ABI which version of the patch is it? >2.0.2.2-rc6 and <2.0.2.2-rc9 has a critical bug which causes kernel oops if there is other traffic while restarting vservers. regards, Holger pgpi5ig9

Bug#403224: initramfs-tools: Unbootable after today Sid dist-upgrade (version 0.85d)

ou are not allowed to store it in your Windows computer. MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_/r+gFn8n9xu7wkl" Message-Id: <[EMAIL PROTECTED]> X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.or

Bug#401980: kernel and d-i testing

Let's add this to the bug report: * Gordon Farquharson <[EMAIL PROTECTED]> [2006-12-16 04:00]: > > it would still be nice if you could identify _which_ of the mm > > patches is responsible. > > 2.6.18-8 with just the first patch > (features/mm-tracking-shared-dirty-pages.patch) applied causes the

Re: Scheduling linux-2.6 2.6.18-9

* Aneesh Kumar K.V wrote: > Frederik Schueler wrote: > > If you have any last minute changes which are that important they > > cannot wait for the first point release kernel, please list them > > here so we can discuss them. > > You may want to apply this patch. This problem was reported before >

Re: [patch, attach, RFC] usb-serial: ti_usb removing firmware

Oleg -- Some comments. I will be away until next Tuesday, when I can do more with this. * We can't remove the compiled in firmware--that would break things until users get and install the firmware images. * What I did in my patch at www.brimson.com/downloads/ti_usb_multitech-1.1.tgz is to u

Processed: Re: Bug#394392: mm/msync in recent kernel broken?

Processing commands for [EMAIL PROTECTED]: > reassign 401006 linux-2.6 Bug#401006: libtorrent9: safe_sync errors Bug#402707: rtorrent: Hash check fails on every download with kernel 2.6.19 Bug reassigned from package `libtorrent9' to `linux-2.6'. > severity 401006 grave Bug#401006: libtorrent9: s

Processed: kernel

Processing commands for [EMAIL PROTECTED]: > reassign 394392 linux-2.6 Bug#394392: msync() in recent kernels fails LSB Warning: Unknown package 'linux-image-2.6.17-2-686' Bug reassigned from package `linux-image-2.6.17-2-686' to `linux-2.6'. > -- Stopping processing here. Please contact me if yo

Re: Bug#394392: mm/msync in recent kernel broken?

reassign 401006 linux-2.6 severity 401006 grave retitle 401006 mm/msync leading to filesystem corruption thanks Seems other people see problems with mm/msync too. * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2006-12-16 13:32]: > I think something got wrong with this change, regarding mmap/msync on

Re: Scheduling linux-2.6 2.6.18-9

Frederik Schueler wrote: Hello, I would like to schedule the upload of the next linux-2.6 2.6.18 version, with the following changes: 1. new vserver patch, breaks ABI 2. new Xen patch 3. Activate PAE on i386 Xen subarch, breaks ABI 4. arm changes 5. 2.6.18.5 ABI breaking patch (Honour source ro