Processed: your mail

2007-09-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 close 436387
Bug#436387: linux-modules-extra-2.6: FTBFS: unmet b-dep linux-support-2.6.21-2
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Lucas Nussbaum [EMAIL PROTECTED]
Removed pending tag.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#441179: linux-image-2.6.22-2-k7: new firewire drivers not yet stable

2007-09-08 Thread Michael Stone

On Fri, Sep 07, 2007 at 12:39:00PM +0200, maximilian attems wrote:

this has already been discussed, we have a solid faith that the yuyu
stack is advancing in good state. use latest trunk and if you have
still trouble holler on bugzilla.kernel.org
trunk apt lines - http://wiki.debian.org/DebianKernel


Ok, the 2.6.23-rc5 package fixes the problem. One question--where does 
the linux-kbuild package that the associated headers depend on live?


Mike Stone


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



Bug#419482: Kernel 2.6.18 - ALI15X3 driver too optmistic about UDMA

2007-09-08 Thread Alan Cox
 if (m5229_revision = 0x20) {
 return 0;
 } else if ((m5229_revision  0xC2) 

So 0xC1 takes this path

 Looking back at the equivalent code in 2.4.27 (the previous kernel
 this machine ran), that's rather different:
 
 if (m5229_revision  0xC1) {/* According to ALi */
 return 0;
 } else if ((m5229_revision  0xC2) 

And 0xC1 takes the same path.

 So it would seem there has been a regression here - the assumption now
 is that versions between 0x20 and 0xC1 can use UDMA fine unless there
 is a WDC drive attached, but the old code wouldn't try UDMA at all on
 chips older than rev C1.

There are no versions between 0x21 and 0xC0.

 I have the machine out and ready to experiment with if any more
 details are needed to help solve this problem.

Interesting report as we've had essentially no corruption reports
equivalent to this on common architectures for a long time and the
hardware is in a huge number of PC systems. Also UDMA transfers are CRC
protected by hardware at each end.

That makes me wonder if you have a platform or endian bug, or indeed your
firmware isn't setting up all the chipset as required by the ALi chipset
and BIOS documentation (which unfortunately is NDA)

Alan


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



Bug#441206: linux-image-2.6.22-2-k7: Firewire 400 external HD fails to be recognized

2007-09-08 Thread Paulo Marcel Coelho Aragao
On Fri, Sep 07, 2007 at 06:36:34PM +0200, maximilian attems wrote:
[...]
 can you be so kind and test tomorrow's build,
 just to know that git firewire doesn't rebork. ;)

I've just installed and rebooted today's kernel build
(2.6.23~rc5-1~experimental.1~snapshot.9473), and... FIREWIRE IS STILL
WORKING !!! Here are the syslog messages:

Sep  8 12:49:19 monk kernel: scsi0 : SBP-2 IEEE-1394
Sep  8 12:49:19 monk kernel: firewire_core: created new fw device fw1 (0 config 
rom retries, S400)
Sep  8 12:49:19 monk kernel: firewire_core: phy config: card 0, new root=ffc0, 
gap_count=5
Sep  8 12:49:21 monk kernel: firewire_sbp2: orb reply timed out, rcode=0x11
Sep  8 12:49:21 monk kernel: firewire_sbp2: logged in to fw1.1 LUN  (1 
retries)
Sep  8 12:49:27 monk kernel: firewire_sbp2: sbp2_scsi_abort
Sep  8 12:49:32 monk kernel: scsi 0:0:0:0: Direct-Access WD   5000AAKS 
Externa 107a PQ: 0 ANSI: 4
Sep  8 12:49:32 monk kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware 
sectors (500108 MB)
Sep  8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Write Protect is off
Sep  8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Mode Sense: 11 00 00 00
Sep  8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Cache data unavailable
Sep  8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Assuming drive cache: write 
through
Sep  8 12:49:32 monk kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware 
sectors (500108 MB)
Sep  8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Write Protect is off
Sep  8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Mode Sense: 11 00 00 00
Sep  8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Cache data unavailable
Sep  8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Assuming drive cache: write 
through
Sep  8 12:49:32 monk kernel:  sda: sda1 sda2
Sep  8 12:49:32 monk kernel: sd 0:0:0:0: [sda] Attached SCSI disk

This snapshot of the firewire_sbp2 module still doesn't have the
'workaround' parameter. Here's the dmesg message:

firewire_sbp2: Unknown parameter `workaround'

I'm currently tracking unstable. When will this kernel snapshot hit
unstable ? May I bump into problems if I go on booting kernel snapshot
and continue to track unstable ?

Thanks a lot for fixing this, Maks !
Paulo


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



Bug#441327: unionfs: NFS kernel crashes when loaded during boot

2007-09-08 Thread Petter Reinholdtsen

Package: unionfs-modules-2.6.18-5-486
Version: 2.6.18+1.4+debian-7+etch3
Severity: important

When trying to set up a NFS server using the live-helper scripts
(Debian Edu Main-Server), the DVD boots just fine, but the NFS server
do not start.  There is a kernel OOPS related to unionfs when it
starts.  This is the messages that seem related in /var/log/syslog:

Sep  8 14:34:11 debian kernel: Installing knfsd (copyright (C) 1996 [EMAIL 
PROTECTED]).
Sep  8 14:34:12 debian kernel: BUG: unable to handle kernel NULL pointer 
dereference at virtual address 0094
Sep  8 14:34:12 debian kernel:  printing eip:
Sep  8 14:34:12 debian kernel: cd0c28fe
Sep  8 14:34:12 debian kernel: *pde = 
Sep  8 14:34:12 debian kernel: Oops:  [#1]
Sep  8 14:34:12 debian kernel: Modules linked in: nfsd exportfs lockd nfs_acl 
sunrpc ppdev lp button ac battery autofs4 cpufreq_userspace cpufreq_stats 
freq_table cpufreq_powersave cpufreq_ondemand cpufreq_conservative ipv6 
dm_snapshot dm_mirror dm_mod fuse tsdev floppy parport_pc psmouse parport 
serio_raw i2c_piix4 pcspkr i2c_core evdev squashfs loop unionfs nls_iso8859_1 
isofs ide_cd cdrom ne2k_pci 8390 piix generic ide_core thermal processor fan 
vga16fb vgastate
Sep  8 14:34:12 debian kernel: CPU:0
Sep  8 14:34:12 debian kernel: EIP:0060:[cd0c28fe]Not tainted VLI
Sep  8 14:34:12 debian kernel: EFLAGS: 0202   (2.6.18-5-486 #1) 
Sep  8 14:34:12 debian kernel: EIP is at unionfs_file_revalidate+0x522/0x866 
[unionfs]
Sep  8 14:34:12 debian kernel: eax:    ebx: c162022c   ecx:    
edx: cc0b5360
Sep  8 14:34:12 debian kernel: esi: caa6c614   edi: 1000   ebp: c09c6000   
esp: c09c7f4c
Sep  8 14:34:12 debian kernel: ds: 007b   es: 007b   ss: 0068
Sep  8 14:34:12 debian kernel: Process exportfs (pid: 4759, ti=c09c6000 
task=c03dcab0 task.ti=c09c6000)
Sep  8 14:34:12 debian kernel: Stack: 0001 caa075c0 cbf6200d cc02f000 
caa6c614  c9c20790 0001 
Sep  8 14:34:12 debian kernel:cd0c2fae 0001 cc02f000 0008 
caa075c0 cbf1fe40 1000 c09c6000 
Sep  8 14:34:12 debian kernel:cd0c2fce cbf1fe40 08050538 caa075c0 
cbf1fe40 1000 c09c6000 c0147553 
Sep  8 14:34:12 debian kernel: Call Trace:
Sep  8 14:34:12 debian kernel:  [cd0c2fae] unionfs_file_release+0x18b/0x195 
[unionfs]
Sep  8 14:34:12 debian kernel:  [cd0c2fce] unionfs_flush+0x16/0xd4 [unionfs]
Sep  8 14:34:12 debian kernel:  [c0147553] filp_close+0x2f/0x54
Sep  8 14:34:12 debian kernel:  [c0102a47] syscall_call+0x7/0xb
Sep  8 14:34:12 debian kernel: Code: 10 8b 46 4c 8b 90 48 01 00 00 89 c8 c1 e0 
04 03 42 18 f6 40 0c 02 0f 84 c6 02 00 00 8d 04 8d 00 00 00 00 03 43 24 8b 00 
8b 40 08 8b 80 94 00 00 00 f6 40 30 01 0f 85 a7 02 00 00 e9 87 02 00 00 
Sep  8 14:34:12 debian kernel: EIP: [cd0c28fe] 
unionfs_file_revalidate+0x522/0x866 [unionfs] SS:ESP 0068:c09c7f4c

I've already added the fsid=42 flag to /etc/exports, but that did not
solve the problem.  It did solve part of the problem, though, as it is
now possible to start the NFS server after the boot (manually).  But
during the boot, it refuses to start properly.

The live image with the problem is available from
URL:http://ftp.skolelinux.no/cd-etch-live/ (the
edulive-Main-Server+Thin-Client-Server images). if you want to test
it.

Happy hacking,
-- 
Petter Reinholdtsen


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



Processing of openais_0.81-1_powerpc.changes

2007-09-08 Thread Archive Administrator
openais_0.81-1_powerpc.changes uploaded successfully to localhost
along with the files:
  openais_0.81-1.dsc
  openais_0.81.orig.tar.gz
  openais_0.81-1.diff.gz
  openais_0.81-1_powerpc.deb
  libopenais2_0.81-1_powerpc.deb
  libopenais-dev_0.81-1_powerpc.deb

Greetings,

Your Debian queue daemon


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



openais_0.81-1_powerpc.changes is NEW

2007-09-08 Thread Debian Installer
(new) libopenais-dev_0.81-1_powerpc.deb optional libdevel
Standards-based cluster framework (developer files)
 The openais project is a project to implement a production quality
 Revised BSD licensed implementation of the SA Forum's Application
 Interface Specification. The project implements cutting edge research
 on virtual synchrony to provide 100% correct operation in the face of
 failures or partitionable networks with excellent performance
 characteristics.
 .
 The Application Interface Specification is a software API and policies
 which are used to develop applications that maintain service during
 faults.
 The API consists of Availability Management Framework (AMF) which
 provides application failover, Cluster Membership (CLM),
 Checkpointing (CKPT), Event (EVT), Messaging (MSG), and
 Distributed Locks (DLOCK).
 .
 This package contains header files required to build clients for the
 openais infrastructure.
(new) libopenais2_0.81-1_powerpc.deb optional libs
Standards-based cluster framework (libraries)
 The openais project is a project to implement a production quality
 Revised BSD licensed implementation of the SA Forum's Application
 Interface Specification. The project implements cutting edge research
 on virtual synchrony to provide 100% correct operation in the face of
 failures or partitionable networks with excellent performance
 characteristics.
 .
 The Application Interface Specification is a software API and policies
 which are used to develop applications that maintain service during
 faults.
 The API consists of Availability Management Framework (AMF) which
 provides application failover, Cluster Membership (CLM),
 Checkpointing (CKPT), Event (EVT), Messaging (MSG), and
 Distributed Locks (DLOCK).
 .
 This package contains libraries that should be used by openais clients.
(new) openais_0.81-1.diff.gz optional admin
(new) openais_0.81-1.dsc optional admin
(new) openais_0.81-1_powerpc.deb optional admin
Standards-based cluster framework (daemon and modules)
 The openais project is a project to implement a production quality
 Revised BSD licensed implementation of the SA Forum's Application
 Interface Specification. The project implements cutting edge research
 on virtual synchrony to provide 100% correct operation in the face of
 failures or partitionable networks with excellent performance
 characteristics.
 .
 The Application Interface Specification is a software API and policies
 which are used to develop applications that maintain service during
 faults.
 The API consists of Availability Management Framework (AMF) which
 provides application failover, Cluster Membership (CLM),
 Checkpointing (CKPT), Event (EVT), Messaging (MSG), and
 Distributed Locks (DLOCK).
 .
 This package contains the aisexec daemon and modules
(new) openais_0.81.orig.tar.gz optional admin
Changes: openais (0.81-1) unstable; urgency=low
 .
  * Initial Release (closes: #421816).
- Pull tarball from Ubuntu.


Override entries for your package:

Announcing to [EMAIL PROTECTED]
Closing bugs: 421816 


Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the override file about once a week.

You may have gotten the distribution wrong.  You'll get warnings above
if files already exist in other distributions.


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



Bug#430941: linux-image-2.6.21-2-686: no-name USB 2.0 flash drive gets unknown partition table until BLKRRPART ioctl is issued

2007-09-08 Thread Simon McVittie
On Mon, 06 Aug 2007 at 16:28:15 +0200, maximilian attems wrote:
 On Thu, 28 Jun 2007, Simon McVittie wrote:
  I have a cheap USB stick (an Integral 512M USB2.0 stick, specifically)
  which appears with unknown partition table when inserted. If the
  BLKRRPART ioctl is issued, the partition table is re-read correctly,
  /dev/sdx1 appears, HAL activates and the stick is auto-mounted correctly.
 
 could you test against newer kernel from unstable 2.6.22.
 it installs just fine and if still reproducible trunk
 see apt lines
 - http://wiki.debian.org/DebianKernel

Sorry for the delay, I don't reboot my laptop very often! I can confirm
that this bug still exists in linux-image-2.6.22-2-686 version 2.6.22-4,
and in linux-image-2.6.23-rc5-686 version
2.6.23~rc5-1~experimental.1~snapshot.9462.

Simon


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



Bug#441179: linux-image-2.6.22-2-k7: new firewire drivers not yet stable

2007-09-08 Thread maximilian attems
On Sat, Sep 08, 2007 at 09:23:47AM -0400, Michael Stone wrote:
 On Fri, Sep 07, 2007 at 12:39:00PM +0200, maximilian attems wrote:
 this has already been discussed, we have a solid faith that the yuyu
 stack is advancing in good state. use latest trunk and if you have
 still trouble holler on bugzilla.kernel.org
 trunk apt lines - http://wiki.debian.org/DebianKernel
 
 Ok, the 2.6.23-rc5 package fixes the problem.

good as i told you, please have a bit more confidence in our decisions.
cool thanks for feedback.

 One question--where does 
 the linux-kbuild package that the associated headers depend on live?
 
well that one is never really tracked due to almost weekly rc releases.
so on trunk you'd better not need oot modules.

best regards

-- 
maks


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



Bug#441206: linux-image-2.6.22-2-k7: Firewire 400 external HD fails to be recognized

2007-09-08 Thread maximilian attems
On Sat, 08 Sep 2007, Paulo Marcel Coelho Aragao wrote:

 On Fri, Sep 07, 2007 at 06:36:34PM +0200, maximilian attems wrote:
 [...]
  can you be so kind and test tomorrow's build,
  just to know that git firewire doesn't rebork. ;)
 
 I've just installed and rebooted today's kernel build
 (2.6.23~rc5-1~experimental.1~snapshot.9473), and... FIREWIRE IS STILL
 WORKING !!! Here are the syslog messages:

*very happy*
 
snipp dmesg
 This snapshot of the firewire_sbp2 module still doesn't have the
 'workaround' parameter. Here's the dmesg message:
 
 firewire_sbp2: Unknown parameter `workaround'

yo my error, the param is named `workarounds'
   ^
workarounds=1
but anyway not needed in your case and would lower your performance:
Firewire-sbp2 defaults to the SCSI stack's maximum transfer size per
command, while sbp2 limits them to 128 kBytes.
Flag 1 accomplishes just that.

 I'm currently tracking unstable. When will this kernel snapshot hit
 unstable ? May I bump into problems if I go on booting kernel snapshot
 and continue to track unstable ?

not that soon as 2.6.22 might be scheduled by the next d-i beta release.
and for sure not before the release itself,
usualy we upload the next day after the release, unless d-i blocks..

snapshots are working in etch too.
 
happy weekend

-- 
maks


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



Re: initramfs-tools / cryptoroot

2007-09-08 Thread maximilian attems
hello daniel,

On Sat, 08 Sep 2007, Daniel Reichelt wrote:

  hmmm doesn't copy_exec already put the needed libraries without
 It's a pitty, but no.

i see, will investigate but really low priority right now, see
- http://lists.debian.org/debian-kernel/2007/09/msg00140.html

but yeah the ugly seding might need some refinments.. ;)
will be away next week so soon..
 
  cool and how does it work out?

 From what I've seen so far it works just fine. I'm going to do the next
 release as a real .deb package (presumably in 1-2 weeks).

very nice,
holler if you get to some limits or bugs :)

bon weekend
 
-- 
maks


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



Bug#439892: linux-image-2.6.21-2-amd64: random crashes/hangs on dual-core AMD64 under heavy disk write load (local and NFS)

2007-09-08 Thread Graham Cobb
I have been running 2.6.22 (from unstable) for one week now and this problem 
has not recurred.  When will 2.6.22 make it into lenny?

Graham


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



Processed: tagging 439397

2007-09-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.10.7
 tags 439397 pending
Bug#439397: initramfs-tools: split networking code into separate function
There were no tags set.
Tags added: pending


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processed: tagging 441211

2007-09-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.10.7
 tags 441211 pending
Bug#441211: system unbootable: MODULES=dep creates initrd without ext3.ko 
(RAID-only system here)
There were no tags set.
Tags added: pending


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processed: tagging 440694

2007-09-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.10.7
 tags 440694 - wontfix
Bug#440694: initramfs-tools MODULES=dep support new mdadm naming scheme
Tags were: wontfix
Tags removed: wontfix


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processed: tagging 421658

2007-09-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.10.7
 tags 421658 pending
Bug#421658: Please export MODULES to hook scripts
There were no tags set.
Tags added: pending


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Processed: tagging 431291

2007-09-08 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.10.7
 tags 431291 help
Bug#431291: initramfs-tools: booting with root=UUID=... does not work with 
version 0.88
Tags were: unreproducible moreinfo
Tags added: help


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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