Bug#566727: linux-image-2.6.32 missing memory cgroup controllers

[Ben Hutchings]

I tried benchmarking this:

Hardware: Thinkpad T61, Core 2 Duo T7100, 2 GB RAM
Kernel version: trunk
Kernel config: i386 686-flavour

I started the system in runlevel 1, ran a clean build of a kernel tree
configured as 'allnoconfig', and then timed 5 more clean builds ('make
clean && time make -j4').

With cgroups disabled at build time:

135.72user 12.59system 1:16.17elapsed 194%CPU (0avgtext+0avgdata 
119248maxresident)k
135.93user 12.13system 1:15.65elapsed 195%CPU (0avgtext+0avgdata 
119264maxresident)k
135.78user 12.17system 1:15.61elapsed 195%CPU (0avgtext+0avgdata 
119248maxresident)k
135.52user 12.42system 1:16.03elapsed 194%CPU (0avgtext+0avgdata 
119264maxresident)k
135.97user 12.04system 1:15.54elapsed 195%CPU (0avgtext+0avgdata 
119264maxresident)k

With cgroups enabled at build time, disabled at init time:

136.11user 12.33system 1:15.82elapsed 195%CPU (0avgtext+0avgdata 
119264maxresident)k
136.01user 12.35system 1:15.93elapsed 195%CPU (0avgtext+0avgdata 
119248maxresident)k
135.66user 12.72system 1:16.09elapsed 195%CPU (0avgtext+0avgdata 
119264maxresident)k
135.54user 12.82system 1:16.34elapsed 194%CPU (0avgtext+0avgdata 
119248maxresident)k
135.95user 12.31system 1:15.93elapsed 195%CPU (0avgtext+0avgdata 
119264maxresident)k

System time is about 2% higher on average, but I think the times are
variable enough that this may not be statistically significant.  Could
someone who remembers some statistics tell me how many times I need to
repeat this to be able to tell?

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?


signature.asc
Description: This is a digitally signed message part

Processed: tagging 567435

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 567435 moreinfo
Bug #567435 [linux-2.6] linux-image-2.6.32-trunk-686: address space collision
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#567435: linux-image-2.6.32-trunk-686: address space collision

[Ben Hutchings]

On Fri, 2010-01-29 at 03:10 +, Alter Ego wrote:
> Package: linux-2.6
> Version: 2.6.32-5
> Justification: breaks the whole system

That means 'breaks any system it is installed on', which is not actually
the case.

> Severity: critical
> 
> After last "aptitude full-upgrade" the new kernel 
> "linux-image-2.6.32-trunk-686" was installed on my Debian squeeze system.
> 
> But every time I boot from the refered new kernel, I see the following 
> error message at the very beginning of the boot process:
> 
> "pci :02:05.0: BAR 6: address space collision on of device 
> [0xfeaa-0xfeab]"

This message is very likely harmless and unrelated to the hang.

> I also get that message by running the following command after booting:
> 
> dmesg | grep -i collision
> 
> After showing that message, the system boots apparently normal and I'm 
> able to graphically login via Gnome or LXDE.
> 
> But, after using the system for some minutes (it varies... could be 10 
> m, 30 m...) the system hangs completely, to the point that I can't even 
> kill X server (even via Ctrl+Alt+Backspace or Alt+SysRq+K) or start 
> another TTY console.
> Also the "Num Lock" and "Caps Lock" lights on the keyboard start blinking.
> 
> So the only option is to turn off the computer by pressing the button on 
> the computer case!
[...]

Can you try setting up a netconsole to capture information about the
crash?  Netconsole setup is explained in
.

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?


signature.asc
Description: This is a digitally signed message part

Bug#567433: marked as done (firmware-linux-nonfree: huge increase in used memory (RAM) right after system startup)

[Debian Bug Tracking System]

Your message dated Fri, 29 Jan 2010 03:48:27 +
with message-id <1264736907.373.597.ca...@localhost>
and subject line Re: Bug#567433: firmware-linux-nonfree: huge increase in used 
memory (RAM) right after system startup
has caused the Debian Bug report #567433,
regarding firmware-linux-nonfree: huge increase in used memory (RAM) right 
after system startup
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
567433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: firmware-linux-nonfree
Version: 0.22
Severity: normal

I was using the following kernel: "linux-image-2.6.30-2-686".

After last "aptitude full-upgrade" the new kernel 
"linux-image-2.6.32-trunk-686" was installed, and I'm using it since then.


This new kernel is "binary blob free", and the eventually required 
firmware files are now in user land, inside packages "firmware-linux" 
and "firmware-linux-nonfree".


I have the following graphics card: ATI RV350 AP.
ATI RV350 AP needs the firmware file "R300_cp.bin", which is included in 
package "firmware-linux-nonfree".

R300_cp.bin is the only firmware file my system needs.

So I had to install the package "firmware-linux", which automatically 
installed package "firmware-linux-nonfree" and updated initramfs image.


And now, when I run the command "dmesg | grep -i firmw" I see that 
"R300_cp.bin" is requested and loaded in memory (so everything is fine).


Everything is fine except the used memory...
As a matter of fact, the memory (RAM) used right after gnome or lxde 
login is now 32 MB more than the memory used before installing 
"firmware-linux" and "firmware-linux-nonfree" !


I see this by running the command "free -m" right after system startup.
Before installing "firmware-linux" the system was using 97 MB in Gnome 
and 65 MB in LXDE.
After installing "firmware-linux" the system began using 129 MB in Gnome 
and 97 MB in LXDE!
Unistalling "firmware-linux" brings the used memory to 97 MB in Gnome 
and 65 MB in LXDE.


I have found the culprit is only the file "R300_cp.bin".
Removing all files and directories inside /lib/firmware/ except the file 
"R300_cp.bin" (which resides in /lib/firmware/radeon/) mantains the 
system in the "memory hog state" (129 MB in Gnome and 97 MB in LXDE).
Removing from /lib/firmware/ only the file "R300_cp.bin" (which resides 
in /lib/firmware/radeon/) brings the system (after next startup, of 
course) back to normal used memory state (97 MB in Gnome and 65 MB in LXDE).


Another thing very strange is the fact the size of firmware file 
"R300_cp.bin" is only 2,0 KB! So how can the system be using 32 MB just 
for loading a 2,0 KB file??


This is of great concern mainly because many old systems have 256 MB of 
RAM or even less... So a 32 MB increase in memory right after system 
startup in unaceptable. And this in order for the user to have exactly 
the same functionality he had with the refered firmware binary blob 
included in the kernel!



-- System Information:
Debian Release: squeeze/sid
 APT prefers testing
 APT policy: (900, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores)
Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

firmware-linux-nonfree depends on no packages.

firmware-linux-nonfree recommends no packages.

Versions of packages firmware-linux-nonfree suggests:
ii  initramfs-tools 0.93.4   tools for generating an 
initramfs
ii  linux-image-2.6.30-2-68 2.6.30-8squeeze1 Linux 2.6.30 image on 
PPro/Celeron

ii  linux-image-2.6.32-trun 2.6.32-5 Linux 2.6.32 for modern PCs

-- no debconf information


--- End Message ---
--- Begin Message ---
On Fri, 2010-01-29 at 03:08 +, Alter Ego wrote:
> Everything is fine except the used memory...
> As a matter of fact, the memory (RAM) used right after gnome or lxde 
> login is now 32 MB more than the memory used before installing 
> "firmware-linux" and "firmware-linux-nonfree" !
> 
> I see this by running the command "free -m" right after system startup.

You need to understand how the kernel manages memory before doing
anything with those figures.

> Before installing "firmware-linux" the system was using 97 MB in Gnome 
> and 65 MB in LXDE.
> After installing "firmware-linux" the system began using 129 MB in Gnome 
> and 97 MB in LXDE!
> Unistalling "firmware-linux" brings the used memory to 97 MB in Gnome 
> and 65 MB in LXDE.
> 
> I have found the culprit is only the file "R300_cp.bin".

No, this file is needed to e

Processed: severity of 567435 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 567435 important
Bug #567435 [linux-2.6] linux-image-2.6.32-trunk-686: address space collision
Severity set to 'important' from 'critical'

> thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#567435: linux-image-2.6.32-trunk-686: address space collision

[Alter Ego]

Package: linux-2.6
Version: 2.6.32-5
Justification: breaks the whole system
Severity: critical

After last "aptitude full-upgrade" the new kernel 
"linux-image-2.6.32-trunk-686" was installed on my Debian squeeze system.


But every time I boot from the refered new kernel, I see the following 
error message at the very beginning of the boot process:


"pci :02:05.0: BAR 6: address space collision on of device 
[0xfeaa-0xfeab]"


I also get that message by running the following command after booting:

dmesg | grep -i collision

After showing that message, the system boots apparently normal and I'm 
able to graphically login via Gnome or LXDE.


But, after using the system for some minutes (it varies... could be 10 
m, 30 m...) the system hangs completely, to the point that I can't even 
kill X server (even via Ctrl+Alt+Backspace or Alt+SysRq+K) or start 
another TTY console.

Also the "Num Lock" and "Caps Lock" lights on the keyboard start blinking.

So the only option is to turn off the computer by pressing the button on 
the computer case!


Note:
I have 2 other computers, with different hardware (different graphics 
card, etc), but they are also running Debian Squeeze and with similar 
installation and configuration.
On one of them I don't get this bug. On the other of them I get 
precisely this same bug.



-- Package-specific info:
** Version:
Linux version 2.6.32-trunk-686 (Debian 2.6.32-5) (b...@decadent.org.uk) 
(gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 06:32:16 UTC 2010


** Command line:
BOOT_IMAGE=//vmlinuz-2.6.32-trunk-686 root=/dev/mapper/hda2_crypt ro quiet

** Not tainted

** Kernel log:
[3.432218] usb usb4: Product: UHCI Host Controller
[3.43] usb usb4: Manufacturer: Linux 2.6.32-trunk-686 uhci_hcd
[3.432226] usb usb4: SerialNumber: :00:1d.2
[3.432332] usb usb4: configuration #1 chosen from 1 choice
[3.432383] hub 4-0:1.0: USB hub found
[3.432397] hub 4-0:1.0: 2 ports detected
[3.432473] uhci_hcd :00:1d.3: PCI INT A -> GSI 16 (level, low) 
-> IRQ 16

[3.432482] uhci_hcd :00:1d.3: setting latency timer to 64
[3.432488] uhci_hcd :00:1d.3: UHCI Host Controller
[3.432505] uhci_hcd :00:1d.3: new USB bus registered, assigned 
bus number 5

[3.432531] uhci_hcd :00:1d.3: irq 16, io base 0xef40
[3.432583] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[3.432588] usb usb5: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1

[3.432593] usb usb5: Product: UHCI Host Controller
[3.432597] usb usb5: Manufacturer: Linux 2.6.32-trunk-686 uhci_hcd
[3.432601] usb usb5: SerialNumber: :00:1d.3
[3.432721] usb usb5: configuration #1 chosen from 1 choice
[3.432772] hub 5-0:1.0: USB hub found
[3.432784] hub 5-0:1.0: 2 ports detected
[3.462019] SCSI subsystem initialized
[3.489580] libata version 3.00 loaded.
[3.510229] ide-cd driver 5.00
[3.514448] ide-gd driver 1.18
[3.514499] hda: max request size: 512KiB
[3.514926] hda: 234441648 sectors (120034 MB) w/2048KiB Cache, 
CHS=16383/255/63

[3.515068] hda: cache flushes supported
[3.515135]  hda:
[3.520090] ide-cd: hdc: ATAPI 48X DVD-ROM drive, 256kB Cache
[3.520099] Uniform CD-ROM driver Revision: 3.20
[3.520281]  hda1 hda2 hda3
[3.867258] device-mapper: uevent: version 1.0.3
[3.867692] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) 
initialised: dm-de...@redhat.com

[   21.534816] EXT4-fs (dm-0): mounted filesystem with ordered data mode
[   23.697805] udev: starting version 150
[   24.315218] input: PC Speaker as /devices/platform/pcspkr/input/input3
[   24.358559] processor LNXCPU:00: registered as cooling_device0
[   24.359031] processor LNXCPU:01: registered as cooling_device1
[   24.439641] i801_smbus :00:1f.3: PCI INT B -> GSI 17 (level, low) 
-> IRQ 17
[   24.451810] input: GenPS/2 Genius Mouse as 
/devices/platform/i8042/serio1/input/input4

[   24.499201] parport_pc 00:0a: reported by Plug and Play ACPI
[   24.499316] parport0: PC-style at 0x378 (0x778), irq 7 
[PCSPP,TRISTATE,EPP]

[   24.534474] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[   24.537490] intel_rng: FWH not detected
[   24.604346] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   25.416088] Intel ICH :00:1f.5: PCI INT B -> GSI 17 (level, low) 
-> IRQ 17

[   25.416166] Intel ICH :00:1f.5: setting latency timer to 64
[   25.744020] intel8x0_measure_ac97_clock: measured 54447 usecs (2624 
samples)

[   25.744026] intel8x0: clocking to 48000
[   27.392792] loop: module loaded
[   27.899877] EXT4-fs (hda1): mounted filesystem with ordered data mode
[   27.952783] Adding 1984016k swap on /dev/mapper/hda3_crypt.  
Priority:-1 extents:1 across:1984016k

[   28.453119] ip_tables: (C) 2000-2006 Netfilter Core Team
[   28.494326] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   28.494970] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. 
Pleas

Bug#567433: firmware-linux-nonfree: huge increase in used memory (RAM) right after system startup

[Alter Ego]

Package: firmware-linux-nonfree
Version: 0.22
Severity: normal

I was using the following kernel: "linux-image-2.6.30-2-686".

After last "aptitude full-upgrade" the new kernel 
"linux-image-2.6.32-trunk-686" was installed, and I'm using it since then.


This new kernel is "binary blob free", and the eventually required 
firmware files are now in user land, inside packages "firmware-linux" 
and "firmware-linux-nonfree".


I have the following graphics card: ATI RV350 AP.
ATI RV350 AP needs the firmware file "R300_cp.bin", which is included in 
package "firmware-linux-nonfree".

R300_cp.bin is the only firmware file my system needs.

So I had to install the package "firmware-linux", which automatically 
installed package "firmware-linux-nonfree" and updated initramfs image.


And now, when I run the command "dmesg | grep -i firmw" I see that 
"R300_cp.bin" is requested and loaded in memory (so everything is fine).


Everything is fine except the used memory...
As a matter of fact, the memory (RAM) used right after gnome or lxde 
login is now 32 MB more than the memory used before installing 
"firmware-linux" and "firmware-linux-nonfree" !


I see this by running the command "free -m" right after system startup.
Before installing "firmware-linux" the system was using 97 MB in Gnome 
and 65 MB in LXDE.
After installing "firmware-linux" the system began using 129 MB in Gnome 
and 97 MB in LXDE!
Unistalling "firmware-linux" brings the used memory to 97 MB in Gnome 
and 65 MB in LXDE.


I have found the culprit is only the file "R300_cp.bin".
Removing all files and directories inside /lib/firmware/ except the file 
"R300_cp.bin" (which resides in /lib/firmware/radeon/) mantains the 
system in the "memory hog state" (129 MB in Gnome and 97 MB in LXDE).
Removing from /lib/firmware/ only the file "R300_cp.bin" (which resides 
in /lib/firmware/radeon/) brings the system (after next startup, of 
course) back to normal used memory state (97 MB in Gnome and 65 MB in LXDE).


Another thing very strange is the fact the size of firmware file 
"R300_cp.bin" is only 2,0 KB! So how can the system be using 32 MB just 
for loading a 2,0 KB file??


This is of great concern mainly because many old systems have 256 MB of 
RAM or even less... So a 32 MB increase in memory right after system 
startup in unaceptable. And this in order for the user to have exactly 
the same functionality he had with the refered firmware binary blob 
included in the kernel!



-- System Information:
Debian Release: squeeze/sid
 APT prefers testing
 APT policy: (900, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores)
Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

firmware-linux-nonfree depends on no packages.

firmware-linux-nonfree recommends no packages.

Versions of packages firmware-linux-nonfree suggests:
ii  initramfs-tools 0.93.4   tools for generating an 
initramfs
ii  linux-image-2.6.30-2-68 2.6.30-8squeeze1 Linux 2.6.30 image on 
PPro/Celeron

ii  linux-image-2.6.32-trun 2.6.32-5 Linux 2.6.32 for modern PCs

-- no debconf information



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#565353: Offer of testing

[Ben Hutchings]

On Wed, 2010-01-27 at 16:19 +, Tim Small wrote:
> I have a Dell PowerEdge R210 (with 2 onboard BCM5716s) which I was just 
> trying to PXE-install.  I'd be happy to test the modified packages if 
> you like.

You can build a package from svn with the following commands:

apt-get -d source linux-2.6=2.6.26-19lenny2
sudo apt-get install build-essential fakeroot rsync
sudo apt-get build-dep linux-2.6=2.6.26-19lenny2
svn co svn://svn.debian.org/svn/kernel/dists/lenny/linux-2.6
cd linux-2.6
debian/rules orig
debian/rules debian/control
debian/rules source
fakeroot make -f debian/rules.gen binary-arch_i386_none_686

You may want to change the target name in the last command, e.g. to
'binary-arch_i386_none_686-bigmem' or 'binary-arch_amd64_none_amd64'.

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?


signature.asc
Description: This is a digitally signed message part

Re: Debian 2.6.32 CONFIG_WIRELESS_OLD_REGULATORY, wireless-regdb and crda

[Paul Wise]

On Fri, 2010-01-29 at 10:57 +0800, Paul Wise wrote:

>   * wireless-regdb could check at build time if the source database
> has been modified and a new binary database been rebuilt
>   * If so
>   * generate a new temporary key at build time
>   * sign the new binary database with the temporary
> key
>   * install the temporary public key
> to /etc/crda/keys/
>   * throw away the temporary private key
>   * If not
>   * install the (unmodified) pre-built binary
> database

Woops, should have read your references, it seems that something like
this is already enabled by the patch from[1] that is merged upstream?

 1. http://bugs.debian.org/536502

-- 
bye,
pabs

http://bonedaddy.net/pabs3/


signature.asc
Description: This is a digitally signed message part

Re: Debian 2.6.32 CONFIG_WIRELESS_OLD_REGULATORY, wireless-regdb and crda

[Paul Wise]

[Please keep me in CC for this thread]

There is a technical change coming in Debian that may mean one key for
the pkg-wpa folks will be more problematic; it is planned that
maintainer-built .debs are to be thrown away on upload (but still
required) and all packages rebuilt on the buildds. There will probably
be the possibility to have exceptions though, so this may turn out to be
a non-issue or less of an issue.

Also, IIRC I wasn't fully happy with the way the signature stuff worked.
My main issue was that the trusted RSA public keys are/were embedded
into the crda binary at build time. I would have much preferred that
they be split out into a set of directories. Something
like /etc/crda/keys/ could be the default. This allows packages to drop
new keys in and for sysadmins to also do that as needed, as well as for
sysadmins to disable keys that have been compromised or similar. With
the dir list and the upcoming buildd change, Debian could use something
like Fedora's option;

  * wireless-regdb could check at build time if the source database
has been modified and a new binary database been rebuilt
  * If so
  * generate a new temporary key at build time
  * sign the new binary database with the temporary
key
  * install the temporary public key
to /etc/crda/keys/
  * throw away the temporary private key
  * If not
  * install the (unmodified) pre-built binary
database

I imagine the OpenSSL stuff in crda 1.1.1 would enable this kind of
option. In addition, crda should have a directory for the sysadmin to
drop in a replacement binary database if for example they wanted to
replace their distro's binary database with a newer version from John
Linville. Since the distros should install John's RSA key, new versions
of the pre-built binary database would be trusted. If the sysadmin
wanted to build their own binary database they would install the
temporary key generated above as well as their new database.

What is the point of having the CFG80211_INTERNAL_REGDB option? That
sounds like a silly thing to do since there is crda and wireless-regdb.
Since 2.6.33 isn't yet released, I assume there is time to change the
behaviour of CFG80211_INTERNAL_REGDB (or remove it). Does
CFG80211_INTERNAL_REGDB mean that crda will be consulted first and if it
cannot be contacted, then the internal copy will be used? You mentioned
the embedded world, I suppose that is the target for it?

Any idea what proportion of wireless card firmware will respect what
Linux and crda tell it? I guess users of old wireless cards with
abandoned or hard-coded firmware will not benefit from crda &
wireless-regdb. I speak here as a user of the ar6000 on the OpenMoko
FreeRunner and a friend of people with ipw2x00-based cards on laptops.
I'm using an iwl3945-based card, do you know if Intel plan to implement
support for this stuff in their firmware?

I thank you very much for working on this stuff.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#565639: marked as done (SunBlade 1000 installation report - boot fails after installation)

[Debian Bug Tracking System]

Your message dated Fri, 29 Jan 2010 02:49:27 +
with message-id <1264733367.373.569.ca...@localhost>
and subject line Re: SunBlade 1000 installation report - boot fails after 
installation
has caused the Debian Bug report #565639,
regarding SunBlade 1000 installation report - boot fails after installation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
565639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: Jan 14th netinst daily image for sparc
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/sparc/iso-cd/debian-testing-sparc-netinst.iso
Date: Sun Jan 17 15:37:37 GMT 2010
Machine: SunBlade 1000, same as in http://bugs.debian.org/562594

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[E]

Comments/Problems:

Now that http://bugs.debian.org/562594 is fixed, I was able to 
continue the installation and it all went fine until the end. 
However, after finishing the installation machine fails to boot with 
messages:

SUNW,Sun-Blade-1000 (2 X UltraSPARC-III) , No Keyboard
Copyright 1998-2004 Sun Microsystems, Inc.  All rights reserved.
OpenBoot 4.16.4, 2048 MB memory installed, Serial #51831895.
Ethernet address 0:3:ba:16:e4:57, Host ID: 8316e457.



Rebooting with command: boot  
Boot device: disk  File and args: 
 ERROR: Last Trap: Fast Data Access MMU Miss

Error -256 
{0} ok 

I thought it was some kind of random hardware quirk, so I tried 
reinstalling a few times, but always got the same result, even if I 
was zero-filling the first 200M of the hard drive before partitioning. 
I then tried Lenny netinst CD (debian-503-sparc-netinst.iso), and it 
worked without problems, so it must be some regression in the recent 
CD images. At this point I have no clue what might be causing it, as 
both Lenny and the current CD builds install the same SILO version and 
partitions are set up identically (~100MB ext2 /boot partition is set 
up to hold the boot files in both cases). I'm going to ask on 
debian-sparc whether anyone can reproduce it.

Another minor detail: serial console output in daily builds is 
black-and-white, while Lenny installer was showing up in color (at 
least, red/blue where appropriate).   
-- 
Jurij Smakov   ju...@wooyd.org
Key: http://www.wooyd.org/pgpkey/  KeyID: C99E03CC


--- End Message ---
--- Begin Message ---
Version: 2.6.32-3

The change to uname was fixed by:

commit 3263c617570ed7c7292ea484d1fdf31687d110ee
Author: David S. Miller 
Date:   Sat Dec 5 17:17:55 2009 -0800

sparc: Set UTS_MACHINE correctly.

in upstream stable release 2.6.32.2.

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Processed: tagging 566547

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 566547 + pending
Bug #566547 [linux-2.6] linux-image-2.6.32-trunk-amd64: Segmentation fault 
during halt
Ignoring request to alter tags of bug #566547 to the same tags previously set
>
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 debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: tagging 567098

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 567098 moreinfo
Bug #567098 [linux-2.6] linux-image-2.6.26-2-ixp4xx: adm8511/pegasus usb 
ethernet device loses mac on nslu2 when cold-plugged
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#567098: linux-image-2.6.26-2-ixp4xx: adm8511/pegasus usb ethernet device loses mac on nslu2 when cold-plugged

[Ben Hutchings]

On Wed, 2010-01-27 at 02:19 -0800, Devin Carraway wrote:
> Package: linux-image-2.6.26-2-ixp4xx
> Version: 2.6.26-19lenny2
> Severity: normal
> 
> 
> I've been experimenting with a Pegasus-chipset USB ethernet adapter on
> an NSLU2 unit.  If the adapter is connected prior to system boot, although it
> will be recognized by the kernel and udev, it starts out with a MAC address of
> 00:00:00:00:00:00.
[...]

Is this reproducible if you plug the adapter into a PC?

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?


signature.asc
Description: This is a digitally signed message part

Re: Uploading linux-2.6

[dann frazier]

On Thu, Jan 28, 2010 at 10:50:16PM +, Ben Hutchings wrote:
> On Mon, 2010-01-25 at 20:19 +0100, Andreas Barth wrote:
> > * Ben Hutchings (b...@decadent.org.uk) [100125 20:14]:
> > > On Mon, Jan 25, 2010 at 08:02:31PM +0100, Andreas Barth wrote:
> > > > * Julien Cristau (jcris...@debian.org) [100125 19:27]:
> > > > > On Mon, Jan 25, 2010 at 18:56:47 +0100, Luk Claes wrote:
> > > > > 
> > > > > > I guess this means that the next version is no candidate for the 
> > > > > > release
> > > > > > unless it gets a stable ABI (versioning) and should block the kernel
> > > > > > from migrating for the time being?
> > > > > > 
> > > > > The 2.6.30 kernel and the current 2.6.32 one aren't candidates either,
> > > > > so I'm not sure what difference blocking the next one makes.
> > > > 
> > > > That our testing users don't have to life with strange error messages
> > > > they wouldn't get if the abi would be bumped properly.
> > > 
> > > OK, maybe we should start numbering ABIs with this next version.
> > 
> > I'd appreciate that very much.
> 
> There has been some argument over whether we should do this or not.
> Bastian and Max seem to think that many more ABI-changing config changes
> will still be needed

seems likely

> and do not want to start numbering yet.  I'm not
> convinced that changing the ABI number repeatedly in testing/unstable
> will even hurt that much since we no longer have to worry about
> dependent module packages in the archive.  It may add to cruft on users'
> systems but this can be fixed after a reboot with 'apt-get autoremove'.

yeah, i think people running sid/testing who do use oot modules
shouldn't have much problem w/ frequent module rebuilds - esp if the
abi is silently changing and they may really need to rebuild anyway.
[Like with a module on my mythbox recently :)]

> I do want to see this argument resolved before building and uploading,
> but I also don't want to hold back security and stability fixes.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#563847: Please enable the f-trace tracers

[dann frazier]

On Tue, Jan 05, 2010 at 12:53:23PM -0700, Troy Heber wrote:
> Source: linux-2.6
> Version: 2.6.32-3
> Severity: wishlist
> 
> Currently Ftrace is enabled in the kernel, CONFIG_FTRACE=y and
> CONFIG_DYNAMIC_FTRACE=y. However, some the most useful tracers, such
> as CONFIG_FUNCTION_TRACER and CONFIG_STACK_TRACER, are disabled. For
> example:
> 
>   CONFIG_FTRACE=y
>   # CONFIG_FUNCTION_TRACER is not set
>   # CONFIG_IRQSOFF_TRACER is not set
>   # CONFIG_SYSPROF_TRACER is not set
>   # CONFIG_SCHED_TRACER is not set
>   # CONFIG_FTRACE_SYSCALLS is not set
>   ...
>   # CONFIG_POWER_TRACER is not set
>   # CONFIG_STACK_TRACER is not set
> 
> Since Dynamic Ftrace is already enabled, I can't think of down side to
> enabling the actual tracers. Please consider this a wishlist request
> to enabled them.

Of FUNCTION_TRACER, Kconfig says:
 If it's runtime disabled
   (the bootup default), then the overhead of the instructions is very
 small and not measurable even in micro-benchmarks.

And for STACK_TRACER:
 If this is configured with DYNAMIC_FTRACE then it will not have any
 overhead while the stack tracer is disabled.

So I've gone ahead and enabled them in svn.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: reassign 567098 to linux-2.6, found 567098 in 2.6.26-19lenny2, found 567098 in 2.6.32-5

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 567098 linux-2.6
Bug #567098 [linux-2.6] linux-image-2.6.26-2-ixp4xx: adm8511/pegasus usb 
ethernet device loses mac on nslu2 when cold-plugged
Ignoring request to reassign bug #567098 to the same package
> found 567098 2.6.26-19lenny2
Bug #567098 [linux-2.6] linux-image-2.6.26-2-ixp4xx: adm8511/pegasus usb 
ethernet device loses mac on nslu2 when cold-plugged
There is no source info for the package 'linux-2.6' at version 
'2.6.26-19lenny2' with architecture ''
Unable to make a source version for version '2.6.26-19lenny2'
Ignoring request to alter found versions of bug #567098 to the same values 
previously set
> found 567098 2.6.32-5
Bug #567098 [linux-2.6] linux-image-2.6.26-2-ixp4xx: adm8511/pegasus usb 
ethernet device loses mac on nslu2 when cold-plugged
There is no source info for the package 'linux-2.6' at version '2.6.32-5' with 
architecture ''
Unable to make a source version for version '2.6.32-5'
Bug Marked as found in versions 2.6.32-5.
> thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: reassign 567098 to linux-2.6, found 567098 in 2.6.26-19lenny2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 567098 linux-2.6
Bug #567098 [linux-image-2.6.32-trunk-ixp4xx] linux-image-2.6.26-2-ixp4xx: 
adm8511/pegasus usb ethernet device loses mac on nslu2 when cold-plugged
Bug reassigned from package 'linux-image-2.6.32-trunk-ixp4xx' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.32-5.
> found 567098 2.6.26-19lenny2
Bug #567098 [linux-2.6] linux-image-2.6.26-2-ixp4xx: adm8511/pegasus usb 
ethernet device loses mac on nslu2 when cold-plugged
There is no source info for the package 'linux-2.6' at version 
'2.6.26-19lenny2' with architecture ''
Unable to make a source version for version '2.6.26-19lenny2'
Bug Marked as found in versions 2.6.26-19lenny2.
> thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#567098: linux-image-2.6.26-2-ixp4xx: adm8511/pegasus usb ethernet device loses mac on nslu2 when cold-plugged

[Ben Hutchings]

On Wed, 2010-01-27 at 10:03 -0800, Devin Carraway wrote:
> reassign 567098 linux-image-2.6.32-trunk-ixp4xx 2.6.32-5
> quit
> 
> This also manifests with linux-image-2.6.32-trunk-ixp4xx 2.6.32-5 from sid;
> reassigning there since it's not locked up in stable-land.

Please assign kernel bugs to 'linux-2.6' (the source package name) and
not to a binary package.  I'll fix this one now.

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?


signature.asc
Description: This is a digitally signed message part

Bug#567212: rt73usb with 2.6.32-trunk kernel

[Ben Hutchings]

On Thu, 2010-01-28 at 01:01 +0100, Dawid wrote:
> Package: linux-image-2.6.32-trunk-686
> Version: 2.6.32-5
> Debian Squeeze
> 
> I use Edimax EW-7318USg  usb wifi adapter with rt73 chipset  - i use
> default rt73usb driver that is built in kernel and standard firmware
> from non-free repository package: firmware-ralink (0.22)  - on new
> 2.6.32 trunk kernel, connection is very unstable - i can connect to my
> access point but i get disconnected periodicly in about 6 to 10
> seconds and get connected again afer about 4 seconds. This process
> repeats itself continously. I use WPAPSK autentication TKIP encryption
> in managed mode - with wpa_supplicant - encryption works but i guess
> becouse of such frequent disconnetions dhclient can't get IP and i
> can't connect to internet. 

Please follow-up using 'reportbug -N 567212', which will include more
information about your system.  If you cannot do that then at least send
a copy of the kernel log from 2.6.32-5.

> On previous 2.6.30 kernel and same configuration, everything works
> fine and connection is stable.
[...]

Were you using the rt73usb driver (from Debian kernel packages) or the
rt73 driver (from rt73-source or from Ralink)?

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?


signature.asc
Description: This is a digitally signed message part

Processed: tagging 563847

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 563847 + pending
Bug #563847 [src:linux-2.6] Please enable the f-trace tracers
Added tag(s) 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 debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: tagging 558237

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 558237 + pending
Bug #558237 [linux-2.6] linux-source-2.6.32: X with xserver-xorg-video-intel 
does not work any longer
Bug #566376 [linux-2.6] linux-image-2.6.32-trunk-amd64: X unconditionally hangs 
up on bootup
Ignoring request to alter tags of bug #558237 to the same tags previously set
Ignoring request to alter tags of bug #566376 to the same tags previously set
>
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 debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: tagging 567352

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 567352 + pending
Bug #567352 [linux-2.6] linux-image-2.6.32-trunk-686-bigmem: DRM failure during 
boot
Added tag(s) 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 debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Uploading linux-2.6

[Ben Hutchings]

On Mon, 2010-01-25 at 20:19 +0100, Andreas Barth wrote:
> * Ben Hutchings (b...@decadent.org.uk) [100125 20:14]:
> > On Mon, Jan 25, 2010 at 08:02:31PM +0100, Andreas Barth wrote:
> > > * Julien Cristau (jcris...@debian.org) [100125 19:27]:
> > > > On Mon, Jan 25, 2010 at 18:56:47 +0100, Luk Claes wrote:
> > > > 
> > > > > I guess this means that the next version is no candidate for the 
> > > > > release
> > > > > unless it gets a stable ABI (versioning) and should block the kernel
> > > > > from migrating for the time being?
> > > > > 
> > > > The 2.6.30 kernel and the current 2.6.32 one aren't candidates either,
> > > > so I'm not sure what difference blocking the next one makes.
> > > 
> > > That our testing users don't have to life with strange error messages
> > > they wouldn't get if the abi would be bumped properly.
> > 
> > OK, maybe we should start numbering ABIs with this next version.
> 
> I'd appreciate that very much.

There has been some argument over whether we should do this or not.
Bastian and Max seem to think that many more ABI-changing config changes
will still be needed and do not want to start numbering yet.  I'm not
convinced that changing the ABI number repeatedly in testing/unstable
will even hurt that much since we no longer have to worry about
dependent module packages in the archive.  It may add to cruft on users'
systems but this can be fixed after a reboot with 'apt-get autoremove'.

I do want to see this argument resolved before building and uploading,
but I also don't want to hold back security and stability fixes.

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?


signature.asc
Description: This is a digitally signed message part

Processed: tagging 567391

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 567391 + pending
Bug #567391 [linux-2.6] Please update aufs2 to new upstream snapshot (aufs2-32 
branch)
Added tag(s) 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 debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Debian 2.6.32 CONFIG_WIRELESS_OLD_REGULATORY, wireless-regdb and crda

[John W. Linville]

On Fri, Jan 29, 2010 at 06:11:50AM +1000, Kel Modderman wrote:

> There are potentially lots of people who could be building/uploading these
> packages and having the same private key for all people to sign regulatory.bin
> may not be feasible.
> 
> Generating a one time private key requires that wireless-regdb and crda are
> built in the same sourceful upload afaik.

I think you've identified the nut of the problem.  AFAICT, you need to
pick either one of the above options or you need to accept using an
unsigned regulatory.bin.

John
-- 
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com  might be all we have.  Be ready.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Debian 2.6.32 CONFIG_WIRELESS_OLD_REGULATORY, wireless-regdb and crda

[Kel Modderman]

On Friday 29 January 2010 04:10:04 Luis R. Rodriguez wrote:
> I asked Kel Modderman [3] about the packages and it seems he is really
> busy with quite a few moves he has been doing and just lacks time to
> get wireless-regdb and crda packaged into Debian. I am the upstream
> CRDA maintainer and have already provided a sample debian/ directory
> for simple packaging for both wireless-regdb and CRDA. When reviewing
> debian packaging before though there were some technical details which
> needed to be ironed out over using an RSA private key to digitally
> sign the wireless-regdb database and then using the public key to read
> the and trust the key with CRDA [4]. Paul Wise also had some good
> feedback and I hope we have addressed it all now. Kel's last iteration
> consisted of creating a private/public RSA key for the pkg-wpa-devel
> team. Technical issue with this is the issues faced when doing
> automatic builds, unless you can get the automatic builds to
> incorporate your key somehow.

I mistakingly overlooked, when writing [3], that wireless-regdb is arch
independent and thus does not get rebuilt upon upload (at least for now,
but this may possibly change in the future).
The issue is more that :

There are potentially lots of people who could be building/uploading these
packages and having the same private key for all people to sign regulatory.bin
may not be feasible.

Generating a one time private key requires that wireless-regdb and crda are
built in the same sourceful upload afaik.

Just installing the prebuilt regulatory.bin doesn't feel very Debian, I am
pretty sure Debian would like to build that binary from its source and reserve
the right to patch that source and rebuild the binary for a variety of reasons.

Thanks, Kel.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#567391: Please update aufs2 to new upstream snapshot (aufs2-32 branch)

[Julian Andres Klode]

Package: linux-2.6
Version: 2.6.32-5
Severity: wishlist

Hi,

please update aufs2 to a newer upstream code. The latest upstream
release (i.e. git push) was on Jan 25 and the next one is expected
for Feb 2 (next monday).

Regards,
Julian

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (350, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.


signature.asc
Description: Digital signature

Bug#567352: linux-image-2.6.32-trunk-686-bigmem: DRM failure during boot

[Ben Hutchings]

On Thu, Jan 28, 2010 at 06:47:26PM +0200, George K. wrote:
> Package: linux-2.6
> Version: 2.6.32-5
> Severity: important
> 
> There is a regression from linux-image-2.6.31-1-686-bigmem to 
> linux-image-2.6.32-trunk-686-bigmem. DRM fails during boot. 
[...]

We already have the fix for this; it will be in the next upload.

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Debian kernel image for amd64 version 2.6.31

[Ben Hutchings]

On Thu, Jan 28, 2010 at 04:39:53PM +0100, Michael Reincke wrote:
> On Thu, 2010-01-28 at 15:48 +0100, Ben Hutchings wrote:
> > On Thu, 2010-01-28 at 13:06 +0100, Michael Reincke wrote:
> > > Hallo,
> > > 
> > > could anyone provide me an Debian kernel image for amd64 kernel version
> > > 2.6.31?
> > >
> > > On debian ftp i only could find 2.6.26 and 2.6.32.
> > 
> > And the problem with 2.6.32 is...?
> > 
> I tried to install debian testing on an new notebook (ASUS UL80) which
> has a Atheros ethernet adapter. The driver for the network adapter
> failed to initialize.
> The netinst cd for contains kernel version 2.6.32.
> So i want to give kernel prior 2.6.32 a change.

Please report this as a bug (run 'reportbug linux-2.6', or send mail to
sub...@bugs.debian.org beginning with 'Package: linux-2.6').  Please include
the information listed in 
if possible.  You can build and test earlier kernel versions if you want,
but we really need to fix 2.6.32.

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#567359: marked as done (linux-image-2.6-686: rt2860sta module fails to load - firmware)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2010 20:13:18 +0100
with message-id <20100128191318.gk17...@wavehammer.waldi.eu.org>
and subject line Re: Bug#567359: linux-image-2.6-686: rt2860sta module fails to 
load - firmware
has caused the Debian Bug report #567359,
regarding linux-image-2.6-686: rt2860sta module fails to load - firmware
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
567359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6-686
Version: 2.6.32+23
Severity: important

The kernel package currently in sid fails to run the rt2860sta wireless driver 
module.

dmesg | grep rt2860
[3.392468] rt2860sta: module is from the staging directory, the quality is 
unknown, you have been warned.
[3.425258] rt2860 :01:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[3.425871] rt2860 :01:00.0: setting latency timer to 64
[   23.450597] rt2860 :01:00.0: firmware: requesting rt2860.bin
[   23.581824] rt2860 :01:00.0: firmware file rt2860.bin request failed (-2)
[   29.198604] rt2860 :01:00.0: firmware: requesting rt2860.bin
[   29.203053] rt2860 :01:00.0: firmware file rt2860.bin request failed (-2)
[   32.586283] rt2860 :01:00.0: firmware: requesting rt2860.bin

I'm fully aware of the prompted message at the top but it might be usefull to 
report it.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-2.6-686 depends on:
ii  linux-image-2.6.32-trunk-686  2.6.32-5   Linux 2.6.32 for modern PCs

linux-image-2.6-686 recommends no packages.

linux-image-2.6-686 suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
On Thu, Jan 28, 2010 at 06:35:14PM +0100, Andreas Marschke wrote:
> The kernel package currently in sid fails to run the rt2860sta wireless 
> driver module.

Install firmware-ralink.

> I'm fully aware of the prompted message at the top but it might be usefull to 
> report it.

No, except if you can show what is wrong with it.

Closing, no bug.

Bastian

-- 
It would be illogical to kill without reason.
-- Spock, "Journey to Babel", stardate 3842.4

--- End Message ---

[bts-link] source package linux-2.6

[bts-link-upstream]

#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #566547 (http://bugs.debian.org/566547)
#  * http://bugzilla.kernel.org/show_bug.cgi?id=15117
#  * remote status changed: (?) -> NEW
usertags 566547 + status-NEW

# remote status report for #566376 (http://bugs.debian.org/566376)
#  * https://bugs.freedesktop.org/show_bug.cgi?id=25510
#  * remote status changed: (?) -> RESOLVED
#  * remote resolution changed: (?) -> FIXED
usertags 566376 + status-RESOLVED resolution-FIXED

# remote status report for #566376 (http://bugs.debian.org/566376)
#  * https://bugs.freedesktop.org/show_bug.cgi?id=25510
#  * remote status changed: (?) -> RESOLVED
#  * remote resolution changed: (?) -> FIXED
usertags 566376 + status-RESOLVED resolution-FIXED

thanks


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Debian 2.6.32 CONFIG_WIRELESS_OLD_REGULATORY, wireless-regdb and crda

[Luis R. Rodriguez]

Hey folks,

I wanted to try to help Debian in ways in which I can with the new
regulatory infrastructure upstream on the Linux kernel. As of recent
(>= 2.6.34) the old regulatory stuff has been deprecated and replaced
completely for CFG80211_INTERNAL_REGDB, the old regulatory framework
was also disabled by default as of the 2.6.30 kernel release [1]. A
user on linux-wireless recently reported that
CONFIG_WIRELESS_OLD_REGULATORY was enabled on their debian squeeze
2.6.32 kernel [2]. I think its time for a change and wanted to help
address questions and help ensure userspace is ready as well for now
and in the future.

I asked Kel Modderman [3] about the packages and it seems he is really
busy with quite a few moves he has been doing and just lacks time to
get wireless-regdb and crda packaged into Debian. I am the upstream
CRDA maintainer and have already provided a sample debian/ directory
for simple packaging for both wireless-regdb and CRDA. When reviewing
debian packaging before though there were some technical details which
needed to be ironed out over using an RSA private key to digitally
sign the wireless-regdb database and then using the public key to read
the and trust the key with CRDA [4]. Paul Wise also had some good
feedback and I hope we have addressed it all now. Kel's last iteration
consisted of creating a private/public RSA key for the pkg-wpa-devel
team. Technical issue with this is the issues faced when doing
automatic builds, unless you can get the automatic builds to
incorporate your key somehow.

Fedora seems to solves this by generating new keys on each build but
always trusting John Linville's public key therefore allowing end
users to download new upstream wireless-regdb binaries as well as
using updates from their own repositories. Ubuntu simply packages both
wireless-regdb and CRDA into one package, wireless-crda, and simply
just trust John's key. That's all.

As of the CRDA 1.1.1 release if you use OpenSSL you can now also
dynamically read public keys at runtime, not sure if this is something
that might help with packaging. As a last resort there is also the
ability to just use the CFG80211_INTERNAL_REGDB that John Linville
added recently but that won't be around until 2.6.34 and lacks the
ability to update regulatory updates through userspace -- you'd have
to provide a new kernel every time wireless regulatory updates are
made, which is why we decided to move the regulatory database to
userspace in the first place. I prefer to just recommend this kconfig
option to embedded users. The other option is to just not use the RSA
key stuff, but as noted on the documentation I advise against it as
using it ensure we are doing best effort on our part in the FOSS
community for the best regulatory compliance we can implement. With
the RSA key stuff we get both authorship verification and file
integrity checks without having to keep CRC checks around, it covers
both with one solution. It is not designed to be bullet proof, anyone
can hack their own regulatory database and we've even documented
exactly how to do this [6] as there are real world examples for why a
third party would do this, but by using the RSA key stuff we are doing
best effort on ensuring authorship and file integrity prior to passing
information to the kernel.

We've tried to document as best as we can the new regulatory
infrastructure [5], our motivation for it [6] and upstream commitment
for it [7]. Please let me know if there are any questions, I'd be glad
to help in any way I can.

[1] 
http://wireless.kernel.org/en/developers/Regulatory#Old_regulatory_implementation
[2] http://marc.info/?l=linux-wireless&m=126444734215577&w=2
[3] http://marc.info/?l=linux-wireless&m=126468708719138&w=2
[4] http://lists.alioth.debian.org/pipermail/pkg-wpa-devel/2009-May/002266.html
[5] http://wireless.kernel.org/en/developers/Regulatory
[6] 
http://wireless.kernel.org/en/developers/Regulatory#Custom_regulatory_information
[7] http://wireless.kernel.org/en/vendors/VendorSupport
[8] http://wireless.kernel.org/en/developers/Regulatory/statement

  Luis


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#567359: linux-image-2.6-686: rt2860sta module fails to load - firmware

[Andreas Marschke]

Package: linux-image-2.6-686
Version: 2.6.32+23
Severity: important

The kernel package currently in sid fails to run the rt2860sta wireless driver 
module.

dmesg | grep rt2860
[3.392468] rt2860sta: module is from the staging directory, the quality is 
unknown, you have been warned.
[3.425258] rt2860 :01:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[3.425871] rt2860 :01:00.0: setting latency timer to 64
[   23.450597] rt2860 :01:00.0: firmware: requesting rt2860.bin
[   23.581824] rt2860 :01:00.0: firmware file rt2860.bin request failed (-2)
[   29.198604] rt2860 :01:00.0: firmware: requesting rt2860.bin
[   29.203053] rt2860 :01:00.0: firmware file rt2860.bin request failed (-2)
[   32.586283] rt2860 :01:00.0: firmware: requesting rt2860.bin

I'm fully aware of the prompted message at the top but it might be usefull to 
report it.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-2.6-686 depends on:
ii  linux-image-2.6.32-trunk-686  2.6.32-5   Linux 2.6.32 for modern PCs

linux-image-2.6-686 recommends no packages.

linux-image-2.6-686 suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#567357: initramfs-tools: after installing new kernel does normal boot instead of resume

[Michal Suchanek]

Package: initramfs-tools
Version: 0.92o
Severity: important


This is a regression since I recall initramfs stopping when the resume
would fail.

However, after installing the 2.6.32 Debian kernel the box would not
resume with the old kernle nor stop when resuming is not possible.

Obviously this loses state of any applications running before suspend.


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-amd64 
root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro quiet

-- /proc/filesystems
ext3
fuseblk
reiserfs

-- lsmod
Module  Size  Used by
tun10828  10 
binfmt_misc 6431  1 
ib_iser24674  0 
rdma_cm20454  1 ib_iser
ib_cm  26176  1 rdma_cm
iw_cm   6371  1 rdma_cm
ib_sa  16103  2 rdma_cm,ib_cm
ib_mad 29809  2 ib_cm,ib_sa
ib_core40855  6 ib_iser,rdma_cm,ib_cm,iw_cm,ib_sa,ib_mad
ib_addr 4373  1 rdma_cm
iscsi_tcp   8097  0 
libiscsi_tcp   10994  1 iscsi_tcp
libiscsi   29318  3 ib_iser,iscsi_tcp,libiscsi_tcp
scsi_transport_iscsi25004  4 ib_iser,iscsi_tcp,libiscsi
bridge 39582  0 
stp 1440  1 bridge
reiserfs  193866  1 
fuse   50078  1 
coretemp4165  0 
hwmon_vid   1828  0 
loop   11767  0 
firewire_sbp2  11450  0 
snd_hda_codec_realtek   235095  1 
asus_atk01107686  0 
snd_hda_intel  18147  0 
snd_hda_codec  54212  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep   5364  1 snd_hda_codec
snd_pcm_oss32399  0 
snd_mixer_oss  12606  1 snd_pcm_oss
snd_pcm60615  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
processor  29479  0 
button  4634  0 
snd_timer  15502  1 snd_pcm
wacom  17752  0 
snd44718  8 
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
i2c_i8017766  0 
soundcore   4598  1 snd
parport_pc 18839  0 
snd_page_alloc  6217  2 snd_hda_intel,snd_pcm
joydev  8411  0 
i2c_core   15584  1 i2c_i801
intel_agp  25521  0 
rng_core2990  0 
psmouse49521  0 
parport27938  1 parport_pc
agpgart24733  1 intel_agp
serio_raw   3752  0 
evdev   7336  8 
ext3  106454  4 
jbd37037  1 ext3
mbcache 4970  1 ext3
ide_cd_mod 24744  0 
cdrom  29399  1 ide_cd_mod
usbhid 31196  0 
hid62745  1 usbhid
sd_mod 29673  7 
crc_t10dif  1276  1 sd_mod
piix4568  0 
ide_pci_generic 2788  0 
ide_core   76802  3 ide_cd_mod,piix,ide_pci_generic
ata_piix   19757  7 
ata_generic 2983  0 
ehci_hcd   30578  0 
uhci_hcd   18457  0 
firewire_ohci  19452  0 
libata131655  2 ata_piix,ata_generic
firewire_core  36560  2 firewire_sbp2,firewire_ohci
crc_itu_t   1307  1 firewire_core
atl1   25970  0 
mii 3210  1 atl1
usbcore   121687  5 wacom,usbhid,ehci_hcd,uhci_hcd
nls_base6377  1 usbcore
scsi_mod  121909  7 
ib_iser,iscsi_tcp,libiscsi,scsi_transport_iscsi,firewire_sbp2,sd_mod,libata
thermal11674  0 
fan 3346  0 
thermal_sys11878  3 processor,thermal,fan

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = update-grub
postrm_hook   = update-grub

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
BOOT=local
DEVICE=eth0
NFSROOT=auto


-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'testing'), (300, 'unstable'), (290, 
'stable-i386'), (280, 'testing-i386'), (270, 'unstable-i386'), (102, 
'experimental'), (1, 'experimental-i386')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages initramfs-tools depends on:
ii  cpio  2.9-13 GNU cpio -- a program to manage ar
ii  findutils 4.4.0-2utilities for finding files--find,
ii  klibc-utils   1.5.12-2   small utilities built with klibc f
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo
ii  udev   

Bug#567352: linux-image-2.6.32-trunk-686-bigmem: DRM failure during boot

[George K.]

Package: linux-2.6
Version: 2.6.32-5
Severity: important

There is a regression from linux-image-2.6.31-1-686-bigmem to 
linux-image-2.6.32-trunk-686-bigmem. DRM fails during boot. 

here's the excerpt from dmesg:

[0.967942] [drm] set up 15M of stolen space
[0.968030] nommu_map_sg: overflow 13d80+4096 of device mask 
[0.968085] [drm:drm_agp_bind_pages] *ERROR* Failed to bind AGP memory: -12
[0.968159] [drm:i915_driver_load] *ERROR* failed to init modeset
[0.973067] i915: probe of :00:02.0 failed with error -28

on linux-image-2.6.32-trunk-686 drm works fine:
[0.973466] [drm] set up 15M of stolen space
[1.907642] [drm] TV-16: set mode NTSC 480i 0
[2.137173] [drm] LVDS-8: set mode 1280x800 1f
[2.193497] Console: switching to colour frame buffer device 160x50
[2.197435] fb0: inteldrmfb frame buffer device
[2.197436] registered panic notifier
[2.197442] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on mi

There's a bug report and patch at freedesktop.org which seems to have solved 
the issue: http://bugs.freedesktop.org/show_bug.cgi?id=25690




-- Package-specific info:
** Version:
Linux version 2.6.32-trunk-686-bigmem (Debian 2.6.32-5) (b...@decadent.org.uk) 
(gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 07:12:17 UTC 2010

** Command line:
BOOT_IMAGE=//vmlinuz-2.6.32-trunk-686-bigmem root=/dev/mapper/lnx-deb ro quiet 
splash

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[2.717089] usb 7-1: configuration #1 chosen from 1 choice
[2.968008] usb 7-2: new full speed USB device using uhci_hcd and address 3
[3.159024] usb 7-2: New USB device found, idVendor=05ac, idProduct=022a
[3.159027] usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[3.159029] usb 7-2: Product: Apple Internal Keyboard / Trackpad
[3.159031] usb 7-2: Manufacturer: Apple Computer
[3.159102] usb 7-2: configuration #1 chosen from 1 choice
[4.851098] udev: starting version 150
[5.319637] ACPI: AC Adapter [ADP1] (on-line)
[5.390526] applesmc: Apple MacBook 4 detected:
[5.390528] applesmc:  - Model with accelerometer
[5.390530] applesmc:  - Model without light sensors and backlight
[5.390531] applesmc:  - Model with 10 temperature sensors
[5.393953] applesmc: device has already been initialized (0xe0, 0x00).
[5.393955] applesmc: device successfully initialized.
[5.395385] applesmc: 1 fans found.
[5.397678] input: applesmc as /devices/platform/applesmc.768/input/input5
[5.397697] applesmc: driver successfully loaded.
[5.598854] ACPI: SSDT beecaa98 00340 (v01  APPLE  Cpu0Ist 3000 INTL 
20061109)
[5.599125] ACPI: SSDT beec8c18 002AD (v01  APPLE  Cpu0Cst 3001 INTL 
20061109)
[5.600686] Monitor-Mwait will be used to enter C-1 state
[5.600801] Monitor-Mwait will be used to enter C-2 state
[5.600846] Monitor-Mwait will be used to enter C-3 state
[5.600850] Marking TSC unstable due to TSC halts in idle
[5.600922] processor LNXCPU:00: registered as cooling_device0
[5.601235] ACPI: SSDT beec9f18 000C8 (v01  APPLE  Cpu1Ist 3000 INTL 
20061109)
[5.601442] ACPI: SSDT beec8f18 00085 (v01  APPLE  Cpu1Cst 3000 INTL 
20061109)
[5.601547] Switching to clocksource hpet
[5.602073] processor LNXCPU:01: registered as cooling_device1
[5.682155] ACPI: Battery Slot [BAT0] (battery present)
[5.892701] input: PC Speaker as /devices/platform/pcspkr/input/input6
[6.058556] usb 2-4: firmware: requesting isight.fw
[6.186894] i801_smbus :00:1f.3: PCI INT C -> GSI 20 (level, low) -> IRQ 
20
[6.186899] ACPI: I/O resource :00:1f.3 [0xefa0-0xefbf] conflicts with 
ACPI region SMBI [0xefa0-0xefaf]
[6.186976] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[6.281036] appletouch: Geyser mode initialized.
[6.281119] input: appletouch as 
/devices/pci:00/:00:1d.2/usb7/7-2/7-2:1.1/input/input7
[6.281199] usbcore: registered new interface driver appletouch
[6.408677] Unable to load isight firmware
[6.408759] usbcore: registered new interface driver isight_firmware
[6.471731] usbcore: registered new interface driver hiddev
[6.488533] input: HID 05ac:1000 as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1:1.0/input/input8
[6.488602] generic-usb 0003:05AC:1000.0001: input,hidraw0: USB HID v1.11 
Keyboard [HID 05ac:1000] on usb-:00:1a.0-1/input0
[6.488618] usbhid 3-1:1.1: couldn't find an input interrupt endpoint
[6.488767] usbcore: registered new interface driver usbhid
[6.488769] usbhid: v2.6:USB HID core driver
[6.517265] usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd hid2hci rqt 64 rq 0 
len 0 ret -84
[6.618163] apple 0003:05AC:8242.0002: hiddev96,hidraw1: USB HID v1.11 
Device [Apple Computer, Inc. IR Receiver] on usb-:00:1d.2-1/input0
[6.622321] input: Apple Computer Apple Internal Keyb

Re: Debian kernel image for amd64 version 2.6.31

[Michael Reincke]

On Thu, 2010-01-28 at 15:48 +0100, Ben Hutchings wrote:
> On Thu, 2010-01-28 at 13:06 +0100, Michael Reincke wrote:
> > Hallo,
> > 
> > could anyone provide me an Debian kernel image for amd64 kernel version
> > 2.6.31?
> >
> > On debian ftp i only could find 2.6.26 and 2.6.32.
> 
> And the problem with 2.6.32 is...?
> 
I tried to install debian testing on an new notebook (ASUS UL80) which
has a Atheros ethernet adapter. The driver for the network adapter
failed to initialize.
The netinst cd for contains kernel version 2.6.32.
So i want to give kernel prior 2.6.32 a change.


> Ben.
> 
Michael


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Bug#547503: git-core: "git clone" fails on armel

[Martin Michlmayr]

* Jonathan Nieder  [2010-01-27 16:50]:
> The bug is in your hands now. :) If you want to try to reproduce it,
> I'd suggest reverting that commit on an armel machine and watching the
> fireworks.  If you don't want to reproduce it, I think it should be
> pretty safe to close.

You showed that the bug is fixed in 2.6.32 and testing has 2.6.32 now,
so imho there's nothing left to do now.  Furthermore, it seems the bug
was in highmem code and none of the Debian armel kernels enable
highmem.  Closing.

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Debian kernel image for amd64 version 2.6.31

[Ben Hutchings]

On Thu, 2010-01-28 at 13:06 +0100, Michael Reincke wrote:
> Hallo,
> 
> could anyone provide me an Debian kernel image for amd64 kernel version
> 2.6.31?
>
> On debian ftp i only could find 2.6.26 and 2.6.32.

And the problem with 2.6.32 is...?

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?


signature.asc
Description: This is a digitally signed message part

Re: Bug#524003: FTBFS on armel

[Martin Michlmayr]

* Riku Voipio  [2010-01-28 09:18]:
> Would this be material for backporting to the 2.6.32-x debian kernels?

It sounds to me as if Andrew Morton is planning to submit it to the
stable branch, so we probably just need to wait.  If it doesn't show
up in -stable soon, we can add the patch to the Debian package
directly.

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Bug#524003: FTBFS on armel

[Ben Hutchings]

On Thu, 2010-01-28 at 09:18 +, Riku Voipio wrote:
> Hi, and thanks for tracing this bug down!
> 
> Quick summary for debian-kernel list - a patch in generic kernel code is
> needed to fix tokyocabinet FTBFS on armel.
> 
> On Thu, Jan 28, 2010 at 09:49:57AM +0100, Sebastian Andrzej Siewior wrote:
> > It is in queued in -mm [0] for .33, will be backportable if nobody has a
> > problem with it [1]. So we have patch now :)
> 
> Would this be material for backporting to the 2.6.32-x debian kernels?
> Since most buildd's run debian/stable kernels, until the next release
> tokyocabinet would need to be built manually on armel anyway. While
> inconvinient, it should still allow tokyocabinet back in testing.

If it's urgent we can cherry-pick this fix.  Otherwise we'll get this
via the 2.6.32-stable series after Linus accepts it.

> > I'm curious what can be done about the dependency of tokyocabinet. It
> > should depend on the kernel which has the patch because a user of the
> > library might get wrong results if it is using a kernel without the
> > patch on the affected architecture. However, there is no need to use a
> > debian kernel so users without a debian kernel would get it pulled in.
> > Plus even if the kernel is installed it is not necessary that this is
> > the kernel which booted the system.
>
> Best would be to have a runtime check in tokyocabinet that errs out if
> the kernel bug is seen.

I'm not sure that's possible.  But certainly a dependency is the wrong
way to do this.

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?


signature.asc
Description: This is a digitally signed message part

Bug#547503: marked as done (git-core: "git clone" fails on armel)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jan 2010 14:37:40 +
with message-id <20100128143734.gt30...@deprecation.cyrius.com>
and subject line Re: Bug#547503: git-core: "git clone" fails on armel
has caused the Debian Bug report #547503,
regarding git-core: "git clone" fails on armel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
547503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git-core
Version: 1:1.6.3.3-2
Severity: important


git clone fails on my Debian armel system:

sascha.si...@flatty:~$ git clone 
git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild
Initialized empty Git repository in /home/sascha.silbe/sugar-jhbuild/.git/
remote: Counting objects: 4772, done.
remote: Compressing objects: 100% (2079/2079), done.
error: inflate: data stream error (invalid distance too far back)
fatal: pack has bad object at offset 616818: inflate returned -3
fatal: index-pack failed
sascha.si...@flatty:~$ git clone git://git.gnome.org/jhbuild
Initialized empty Git repository in /home/sascha.silbe/jhbuild/.git/
remote: Counting objects: 19804, done.
remote: Compressing objects: 100% (6374/6374), done.
fatal: pack has bad object at offset 487227: inflate returned -5
fatal: index-pack failed
sascha.si...@flatty:~$ 


The same repositories can be checked out fine on a Debian i386 system (inside 
the same network):

sascha.si...@caravan:/tmp/sascha_silbe/tmpbox.PjGIP1AEY7$ git clone 
git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild
Initialized empty Git repository in 
/tmp/sascha_silbe/tmpbox.PjGIP1AEY7/sugar-jhbuild/.git/
remote: Counting objects: 4772, done.
remote: Compressing objects: 100% (2079/2079), done.
remote: Total 4772 (delta 2815), reused 4486 (delta 2638)
Receiving objects: 100% (4772/4772), 1.88 MiB | 607 KiB/s, done.
Resolving deltas: 100% (2815/2815), done.
sascha.si...@caravan:/tmp/sascha_silbe/tmpbox.PjGIP1AEY7$ 


strace doesn't show anything unusual; ltrace seems stuck inside an infinite 
loop of "unexpected instruction 0xe5bcf76c at 0xac08" (addresses not changing) 
if given "-f" to trace children (and without "-f" doesn't show anything useful).


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: armel (armv5tel)

Kernel: Linux 2.6.31-rc9-flatty-ocf-1-00293-g53a104c (PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages git-core depends on:
ii  libc6   2.9-25   GNU C Library: Shared libraries
ii  libcurl3-gnutls 7.19.5-1.1   Multi-protocol file transfer libra
ii  libdigest-sha1-perl 2.12-1   NIST SHA-1 message digest algorith
ii  liberror-perl   0.17-1   Perl module for error/exception ha
ii  libexpat1   2.0.1-4  XML parsing C library - runtime li
ii  libgcc1 1:4.4.1-1GCC support library
ii  perl-modules5.10.0-25Core Perl modules
ii  zlib1g  1:1.2.3.3.dfsg-15+b2 compression library - runtime

Versions of packages git-core recommends:
ii  less436-1+b1 pager program similar to more
ii  openssh-client [ssh-client] 1:5.1p1-7+b1 secure shell client, an rlogin/rsh
ii  patch   2.5.9-5  Apply a diff file to an original
ii  rsync   3.0.6-1  fast remote file copy program (lik

Versions of packages git-core suggests:
pn  git-arch   (no description available)
pn  git-cvs(no description available)
pn  git-daemon-run (no description available)
pn  git-doc(no description available)
pn  git-email  (no description available)
pn  git-gui(no description available)
pn  git-svn(no description available)
pn  gitk   (no description available)
pn  gitweb (no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
* Jonathan Nieder  [2010-01-27 16:50]:
> The bug is in your hands now. :) If you want to try to reproduce it,
> I'd suggest reverting that commit on an armel machine and watching the
> fireworks.  If you don't want to reproduce it, I think it should be
> pretty safe to close.

You showed that the bug is fixed in 2.6.32 and testing has 2.6.32 now,
so imho there's nothing left to do now

Debian kernel image for amd64 version 2.6.31

[Michael Reincke]

Hallo,

could anyone provide me an Debian kernel image for amd64 kernel version
2.6.31?

On debian ftp i only could find 2.6.26 and 2.6.32.

Regards 

Michael Reincke

-- 
Michael Reincke 
ATLAS ELEKTRONIK GmbH


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#561552: linux-image-2.6.32-trunk-amd64: [agp/drm] agp + dri unavailable with testing X.org 1.6.5

[thomas schorpp]

Bob Calhoun wrote:

Mr. Schorpp,

On Wed, 27 Jan 2010, you wrote, "This has already been triaged to the 
broken firmware-loader if built as module, radeon cannot work without 
r300_cp.bin here, it is not built into debian kernels but in 
/lib/firmware/radeon, report it upstream, there's no config issue:" 


Now, 
I do not know what the problem is but the only Debian kernel I have ever 
had difficulties with is linux-image-2.6.32-trunk-amd64. My machine runs 
well with linux-image-2.6.30-2-amd64 but not with 
linux-image-2.6.32-trunk-amd64; according to the Xorg log, AGP failed to 
initialize.  Over on Debian User Forums, a number of posters are 
rejecting linux-image-2.6.32-trunk-amd64.


http://forums.debian.net/viewtopic.php?f=5&t=48790


We don't work with webforums here, they're inefficent and unergonomical 
for managing and using SW-QA-Processes.




As I said, I don't know where the problem is, but as things sit I cannot 
use this new kernel.


Regards,

Bob Calhoun



Don't call me 'Mr.' , don't mail me off-list and pls provide qualified extra info 
from Your machine using reportbug and tell the other guys in that forum to do so, thank You


cu
y
tom



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Add tag d-i

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 565639 d-i
Bug #565639 [linux-2.6] SunBlade 1000 installation report - boot fails after 
installation
Added tag(s) d-i.
>
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 debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed (with 5 errors): Re: Bug#565639: SunBlade 1000 installation report - boot fails after installation

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 565639 linux-2.6 2.6.30-8
Bug #565639 [installation-reports] SunBlade 1000 installation report - boot 
fails after installation
Bug reassigned from package 'installation-reports' to 'linux-2.6'.
Bug #565639 [linux-2.6] SunBlade 1000 installation report - boot fails after 
installation
There is no source info for the package 'linux-2.6' at version '2.6.30-8' with 
architecture ''
Unable to make a source version for version '2.6.30-8'
Bug Marked as found in versions 2.6.30-8.
> severity 565639 serious
Bug #565639 [linux-2.6] SunBlade 1000 installation report - boot fails after 
installation
Severity set to 'serious' from 'normal'

> affects 565639 debian-installer
Bug #565639 [linux-2.6] SunBlade 1000 installation report - boot fails after 
installation
Added indication that 565639 affects debian-installer
> On Sunday 24 January 2010, Jurij Smakov wrote:
Unknown command or malformed arguments to command.

> > Adding kernel team for comment: it looks like the value returned by
Unknown command or malformed arguments to command.

> > uname -m has changed from 'sparc64' in kernel 2.6.26 to 'sparc' in
Unknown command or malformed arguments to command.

> > 2.6.30 (and, probably, later ones). This breaks SILO, which uses this
Unknown command or malformed arguments to command.

> > value to determine what first-stage bootloader to install, as a result
Unknown command or malformed arguments to command.

Too many unknown commands, stopping here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Bug#565639: SunBlade 1000 installation report - boot fails after installation

[Frans Pop]

reassign 565639 linux-2.6 2.6.30-8
severity 565639 serious
affects 565639 debian-installer

On Sunday 24 January 2010, Jurij Smakov wrote:
> Adding kernel team for comment: it looks like the value returned by
> uname -m has changed from 'sparc64' in kernel 2.6.26 to 'sparc' in
> 2.6.30 (and, probably, later ones). This breaks SILO, which uses this
> value to determine what first-stage bootloader to install, as a result
> the sparc machines installed with current daily installer builds turn
> unbootable by the end of installation.

Thanks for tracing the cause to this.
Reassigning to the kernel team for further investigation.

Cheers,
FJP


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#524003: FTBFS on armel

[Riku Voipio]

Hi, and thanks for tracing this bug down!

Quick summary for debian-kernel list - a patch in generic kernel code is
needed to fix tokyocabinet FTBFS on armel.

On Thu, Jan 28, 2010 at 09:49:57AM +0100, Sebastian Andrzej Siewior wrote:
> It is in queued in -mm [0] for .33, will be backportable if nobody has a
> problem with it [1]. So we have patch now :)

Would this be material for backporting to the 2.6.32-x debian kernels?
Since most buildd's run debian/stable kernels, until the next release
tokyocabinet would need to be built manually on armel anyway. While
inconvinient, it should still allow tokyocabinet back in testing.

> I'm curious what can be done about the dependency of tokyocabinet. It
> should depend on the kernel which has the patch because a user of the
> library might get wrong results if it is using a kernel without the
> patch on the affected architecture. However, there is no need to use a
> debian kernel so users without a debian kernel would get it pulled in.
> Plus even if the kernel is installed it is not necessary that this is
> the kernel which booted the system.

Best would be to have a runtime check in tokyocabinet that errs out if
the kernel bug is seen.

> [0] http://marc.info/?l=linux-mm-commits&m=126454582727638&w=2
> [1] http://lkml.org/lkml/2010/1/27/344



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#524003: FTBFS on armel

[Sebastian Andrzej Siewior]

tags 524003 + patch
thanks.

* Sebastian Andrzej Siewior | 2010-01-26 23:09:59 [+0100]:

>fine. I don't patch tag since the two dcache flushes don't look right
>and upstream did not apply it yet. We will see.

It is in queued in -mm [0] for .33, will be backportable if nobody has a
problem with it [1]. So we have patch now :)

I'm curious what can be done about the dependency of tokyocabinet. It
should depend on the kernel which has the patch because a user of the
library might get wrong results if it is using a kernel without the
patch on the affected architecture. However, there is no need to use a
debian kernel so users without a debian kernel would get it pulled in.
Plus even if the kernel is installed it is not necessary that this is
the kernel which booted the system.

[0] http://marc.info/?l=linux-mm-commits&m=126454582727638&w=2
[1] http://lkml.org/lkml/2010/1/27/344

Sebastian



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: add the patch tag for 524003

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 524003 + patch
Bug #524003 [linux-2.6] tokyocabinet FTBFS on armel and hppa
Added tag(s) patch.
> thanks.
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org