Bug#750360: systemd-sysv: breaks NFS root systems

2014-08-03 Thread Steve M. Robbins
On Tue, Jun 03, 2014 at 07:49:08PM +0200, maximilian attems wrote:
 
 thank you very much, pushed out to initramfs repo:
 http://anonscm.debian.org/gitweb/?p=kernel/initramfs-tools.git
 
 will upload soonish.

Hi.  It's two months later and people (e.g. me!) are being bitten by
this bug when upgrading to systemd.  Can I help with getting this fix
uploaded?

Thanks,
-Steve


signature.asc
Description: Digital signature


Bug#714497: More info: not found in 3.8-2-amd64

2013-07-01 Thread Steve M. Robbins
Hi,

I booted my old kernel (3.8-2) and the problem has gone away, so it is 
definitely something in the 3.9 kernel.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201307012203.16387.st...@sumost.ca



Bug#714497: kernel BUG at /build/linux-eHaf39/linux-3.9.6/include/drm/drm_mm.h:100

2013-06-29 Thread Steve M. Robbins
Package: src:linux
Version: 3.9.6-1
Severity: important
File: /boot/vmlinuz-3.9-1-amd64

Hi,

I shut off the monitors and leave my computer running when not using
it (still logged into the X session).  Four times in the past week,
I've returned (hours or days later) to find that the X session is
'locked up': the display looks OK, but does not respond to mouse
motion or keyboard input.  I've simply power-cycled the machine to
recover.

Below is a sample sequence from kern.log.  All four instances look
similar and all start with Failed to find memory space 

Jun 26 23:02:23 localhost kernel: [370417.139471] [TTM] Failed to find memory 
space for buffer 0x88014da81448 eviction
Jun 26 23:02:23 localhost kernel: [370417.139476] [TTM] No space for 
88014da81448 (41832 pages, 167328K, 163M)
Jun 26 23:02:23 localhost kernel: [370417.139478] [TTM]   
placement[0]=0x00010002 (1)
Jun 26 23:02:23 localhost kernel: [370417.139480] [TTM] has_type: 1
Jun 26 23:02:23 localhost kernel: [370417.139481] [TTM] use_type: 1
Jun 26 23:02:23 localhost kernel: [370417.139482] [TTM] flags: 0x000A
Jun 26 23:02:23 localhost kernel: [370417.139483] [TTM] gpu_offset: 
0x2000
Jun 26 23:02:23 localhost kernel: [370417.139485] [TTM] size: 131072
Jun 26 23:02:23 localhost kernel: [370417.139486] [TTM] available_caching: 
0x0007
Jun 26 23:02:23 localhost kernel: [370417.139487] [TTM] default_caching: 
0x0001
Jun 26 23:02:23 localhost kernel: [370417.139523] [ cut here 
]
Jun 26 23:02:23 localhost kernel: [370417.139550] kernel BUG at 
/build/linux-eHaf39/linux-3.9.6/include/drm/drm_mm.h:100!
Jun 26 23:02:23 localhost kernel: [370417.139586] invalid opcode:  [#1] SMP 
Jun 26 23:02:23 localhost kernel: [370417.139609] Modules linked in: nls_utf8 
nls_cp437 vfat fat usb_storage tcp_diag inet_diag nfnetlink_queue nfnetlink_log 
nfnetlink parport_pc ppdev lp parport cuse tun cpufreq_userspace cp
ufreq_powersave cpufreq_stats cpufreq_conservative snd_hrtimer pci_stub 
vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc uinput nfsd 
auth_rpcgss nfs_acl nfs lockd dns_resolver fscache sunrpc loop firewire_sbp2 fu
se dm_crypt dm_mod snd_hda_codec_hdmi snd_hda_codec_analog uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media snd_usb_audio 
snd_usbmidi_lib snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_os
s snd_pcm coretemp kvm_intel snd_page_alloc snd_seq_midi snd_seq_midi_event 
iTCO_wdt radeon snd_rawmidi acpi_cpufreq mperf iTCO_vendor_support processor 
kvm snd_seq ttm pcspkr i2c_i801 lpc_ich mfd_core thermal_sys snd_seq_dev
ice snd_timer snd drm_kms_helper drm i2c_algo_bit i2c_core asus_atk0110 
soundcore evdev button ext4 crc16 jbd2 mbcache sg sr_mod sd_mod cdrom 
crc_t10dif ata_generic hid_generic usbhid hid pata_marvell firewire_ohci skge 
firew
ire_core crc_itu_t ahci libahci microcode sky2 ehci_pci uhci_hcd ehci_hcd 
libata scsi_mod usbcore usb_common
Jun 26 23:02:23 localhost kernel: [370417.140295] CPU 2 
Jun 26 23:02:23 localhost kernel: [370417.140307] Pid: 6141, comm: kwin 
Tainted: G   O 3.9-1-amd64 #1 Debian 3.9.6-1 System manufacturer 
P5Q-E/P5Q-E
Jun 26 23:02:23 localhost kernel: [370417.140356] RIP: 
0010:[a02104f3]  [a02104f3] drm_mm_hole_node_start+0x6/0x11 
[drm]
Jun 26 23:02:23 localhost kernel: [370417.140411] RSP: 0018:8801e08bf950  
EFLAGS: 00010246
Jun 26 23:02:23 localhost kernel: [370417.140436] RAX: ed73ed73 RBX: 
880224060180 RCX: 0007
Jun 26 23:02:23 localhost kernel: [370417.140468] RDX: ed73 RSI: 
a0289d2c RDI: 8802240600d0
Jun 26 23:02:23 localhost kernel: [370417.140500] RBP: a0289d2c R08: 
0002 R09: 814ec0f2
Jun 26 23:02:23 localhost kernel: [370417.140533] R10:  R11: 
8801b62ded00 R12: 880223faa640
Jun 26 23:02:23 localhost kernel: [370417.140565] R13:  R14: 
8802240600c0 R15: 880223faa9c0
Jun 26 23:02:23 localhost kernel: [370417.140598] FS:  7fb4f973f780() 
GS:88022fd0() knlGS:
Jun 26 23:02:23 localhost kernel: [370417.140634] CS:  0010 DS:  ES:  
CR0: 8005003b
Jun 26 23:02:23 localhost kernel: [370417.140660] CR2: 7fb4dce89ea0 CR3: 
0001e08ae000 CR4: 27e0
Jun 26 23:02:23 localhost kernel: [370417.140693] DR0:  DR1: 
 DR2: 
Jun 26 23:02:23 localhost kernel: [370417.140726] DR3:  DR6: 
0ff0 DR7: 0400
Jun 26 23:02:23 localhost kernel: [370417.140758] Process kwin (pid: 6141, 
threadinfo 8801e08be000, task 8801e0836830)
Jun 26 23:02:23 localhost kernel: [370417.140793] Stack:
Jun 26 23:02:23 localhost kernel: [370417.140804]  a0210789 
880224060180 8802240600c0 880223faa640
Jun 26 23:02:23 localhost kernel: [370417.140848]   

Bug#714497: More info: also found in RedHat

2013-06-29 Thread Steve M. Robbins
It seems this bug is reported at least four times to Fedora project, so it's 
likely an upstream issue.

Fedora references:

https://bugzilla.redhat.com/show_bug.cgi?id=964120
https://bugzilla.redhat.com/show_bug.cgi?id=967282
https://bugzilla.redhat.com/show_bug.cgi?id=975073
https://bugzilla.redhat.com/show_bug.cgi?id=976577


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201306291924.14122.st...@sumost.ca



Bug#436267: Firewire support in lenny

2008-04-20 Thread Steve M. Robbins
On Sun, Apr 20, 2008 at 11:04:31PM +0200, maximilian attems wrote:

 for most userspace apps there exist working patches as documented
 by post of libdc1394 maintainer.

That's irrelevant.  There is manifestly a problem with video.  It was
reported in August of last year.  You can't credibly continue to claim
8 months later that everything is hunky dory.  It was not then and is
not now.


 we reverted for etch+half, if userspace stays as lame as currently
 it is still an option for Lenny but we'd prefer out of several
 provided grounds not to be forced to do that.

Rather than complaining about the lame userspace, work with them to
apply the requisite patches.  Debian is about building a *system* in
support of our users.  Some of us want to use video out of the box.
It's not that much to ask, is it?

Chimo,
-Steve


signature.asc
Description: Digital signature


Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel

2007-12-16 Thread Steve M. Robbins
On Thu, Dec 13, 2007 at 04:59:37PM +0100, maximilian attems wrote:
 On Thu, Dec 13, 2007 at 09:50:56AM -0600, Steve M. Robbins wrote:
  
  Git repos are not relevant here.
 
 they are fucking important, but it seems that the firewire
 lib maintainers are quite lame.

I'm sad to read a response that seems to be blaming and
finger-pointing.  Debian is about building a *system* 
and we all need to work together to that end.

It seems to me that if you make a change that in turn requires a
change in other packages -- indeed, it explicitly *breaks* other
packages -- then it is incumbent on you to work with the other package
maintainers to achieve the required changes.  In the present case, it
appears that the libraw maintainer, for one, wasn't informed
(c.f. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453358).

-Steve


signature.asc
Description: Digital signature


Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel

2007-12-13 Thread Steve M. Robbins
On Thu, Dec 13, 2007 at 10:27:40AM +0100, maximilian attems wrote:
 On Wed, Dec 12, 2007 at 11:17:28PM -0600, Steve M. Robbins wrote:
  
  As noted by Guus Sliepen, switching from a functioning driver to an
  experimental driver with no library support is not going to cause the
  latter to be improved.  It's simply annoying to the user.
 
 that is a pretty bold incompetent statement,
 for all relevant libraries patches exists.
 take them out of the corresponding git repos.

By user, I meant Debian user.  There is manifestly 
no library support for the Debian user.

Git repos are not relevant here.

  
  The linux1394.org people say:
  
   At the time of this writing (12/2007), there are still multiple
   problems with the new FireWire kernel driver stack (alias Juju)
   compared to the old stack [...]
  
   Regarding Linux 2.6.22 and 2.6.23, the best advice to Linux
   distributors (kernel packagers) as well as to regular users is: Build
   only the old IEEE 1394 drivers.
  
   http://wiki.linux1394.org/JujuMigration
 
 et ceterum censo aboves quote is from 1 of the 2 maintainers.
 the other maintainer considered it fit enough for fedora stable
 release 7 and 8.

And the Fedora users are complaining as well.

I cannot see how you think it improves things to produce a system
(Debian Sid) with an unusable 1394 subsystem.  It is clearly not being
tested nor improved, since anyone who wants to use it is rebuilding
the kernel with the old drivers again!


 the new stack has many advantages:
 - leaner codebase (less than 8k lines of code compared to 30k lines of
   code in the old stack)
 - cleaned-up and improved in-stack APIs
   (with the side effect of getting rid of a bunch of old bugs)
 - design (no kernel threads, compared to one subsystem thread and one
   thread per FireWire controller in the old stack)

Those are all great theoretical advantages.  None of them matter
to me, as a user.  What matters is a working system.  And Debian
is -- allegedly -- about the users.  In that light, I would think
that the best approach is:

1. Make sure all libraries are patched.
2. Switch the kernel module.

Rather than the other way around.

Best regards,
-Steve


signature.asc
Description: Digital signature


Bug#436267: linux-image-2.6.22-1-686: IEEE1394 modules unbuilt in packaged kernel

2007-12-12 Thread Steve M. Robbins
On Tue, Dec 11, 2007 at 05:32:36PM +0100, maximilian attems wrote:
 hello,
 
 On Tue, Dec 11, 2007 at 05:20:26PM +0100, Laurent Bonnaud wrote:
  
  another application stopped working after this kernel change.  It is
  coriander.  I do not know if all applications must be fixed or if a fix
  in the 1394 libraries is enough.  Unfortunately libraries are not fixed
  yet, see bug #453358 :
  
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453358
 
 that is expected and thus the switch to juju is made early
 in the release cycle.
 enough time to fix those up.

As noted by Guus Sliepen, switching from a functioning driver to an
experimental driver with no library support is not going to cause the
latter to be improved.  It's simply annoying to the user.

The linux1394.org people say:

 At the time of this writing (12/2007), there are still multiple
 problems with the new FireWire kernel driver stack (alias Juju)
 compared to the old stack [...]

 Regarding Linux 2.6.22 and 2.6.23, the best advice to Linux
 distributors (kernel packagers) as well as to regular users is: Build
 only the old IEEE 1394 drivers.

 http://wiki.linux1394.org/JujuMigration

Please consider enabling the working driver until userspace
libraries exist for the new one.

Thanks,
-Steve



signature.asc
Description: Digital signature


Bug#303918: acknowledged by developer (closing 303918)

2007-09-18 Thread Steve M. Robbins
On Mon, Sep 17, 2007 at 06:51:22PM +, Debian Bug Tracking System wrote:
 This is an automatic notification regarding your Bug report
 #303918: Patch to support IT8212 on-board RAID controller,
 which was filed against the kernel package.
 
 It has been marked as closed by one of the developers, namely
 maximilian attems [EMAIL PROTECTED].
 
 You should be hearing from them with a substantive response shortly,
 in case you haven't already. If not, please contact them directly.

So the note in the bug report says presumably fixed.  Did you
find something in the kernel package to make you presume this?

Thanks,
-Steve



signature.asc
Description: Digital signature


Bug#303918: Patch to support IT8212 on-board RAID controller

2005-04-20 Thread Steve M. Robbins
On Sun, Apr 10, 2005 at 03:28:19PM +0200, maximilian attems wrote:
 On Sat, 09 Apr 2005, Steve M. Robbins wrote:
 
  Dear Debian Kernel Maintainers,
  
  Alan Cox has a patch against 2.6.10 that supports the IT 8212 RAID
  Controller, which is found on some motherboards.
 
 just checked it's not in 2.6.12-rc2 nor in the ide-dev tree.
 i guess alan hasn't submitted it yet to bart.
[ ... ]
 the patch will get into our tree as soon as it's accepted upstream.

The main point of my request is that the patch be applied to
Debian's kernel *before* it gets into the official sources.
Indeed, once it is in the official sources, there's no need
to patch Debian's kernel.

I've been running a kernel with this driver for several weeks now with
no ill effects -- in fact, my root partition is on a mirrored drive on
this controller.  Moreover, the patch simply adds one source file
and fixes the Makefile to build it.  It is quite safe for you
to apply it.

Regards,
-Steve



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#303918: Patch to support IT8212 on-board RAID controller

2005-04-09 Thread Steve M. Robbins
Package: kernel-image-2.6.10-i386
Severity: wishlist
Tags: patch

Dear Debian Kernel Maintainers,

Alan Cox has a patch against 2.6.10 that supports the IT 8212 RAID
Controller, which is found on some motherboards.

This patch (http://lkml.org/lkml/2004/12/28/79) applied with no
problem against the Debian kernel sources.  It just adds one extra
source file that builds one extra module so there is no concern about
code destabilization.  I'm using this module on my system now.


If you could include this in the debian sources and enable the module,
I'd be very much in your debt.  Thanks.


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10it8212
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]