Bug#542902: linux-image-2.6.26-2-686: local e1000e clobbered in update

[Tim Sadler]

Package: linux-image-2.6.26-2-686
Version: 2.6.26-17lenny2
Severity: normal

Hi,

With this package as the only kernel installed, and hence the running kernel, 
an upgrade replaces the locally built driver for the e1000e module.

In my case, I have compiled the module locally as the packaged version (0.3.3 i 
think) doesn't support the option of disabling the MSI interupts and hence the 
system panics.  I have compiled and installed the latest version from the Intel 
website (version 1.0.2.5) which does support this option.  Obviously, this 
replaces the packaged file.  The replacement file is a different size, 
date/time stamp and a different module version.

By replacing the locally built module a reboot causes a panic.

Shouldn't the package respect local changes such as this and not overwrite the 
changed module?

Regards,
Tim

-- Package-specific info:
** Version:
Linux version 2.6.26-2-686 (Debian 2.6.26-17lenny2) (da...@debian.org) (gcc 
version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Fri Aug 14 
01:27:18 UTC 2009

** Command line:
root=/dev/md0 ro acpi=on console=ttyS0,38400

** Not tainted

** Kernel log:
[   14.921551] md: md4 stopped.
[   15.196354] md: bind
[   15.204721] md: bind
[   15.212950] usb 1-2: configuration #1 chosen from 1 choice
[   15.247511] raid1: raid set md4 active with 2 out of 2 mirrors
[   15.680012] kjournald starting.  Commit interval 5 seconds
[   15.700255] EXT3-fs: mounted filesystem with ordered data mode.
[   16.831534] hiddev96hidraw0: USB HID v1.10 Device [American Power Conversion 
Back-UPS RS 500 FW:30.j5.I USB FW:j5] on usb-:00:10.0-2
[   16.870394] usb 1-2: New USB device found, idVendor=051d, idProduct=0002
[   16.890427] usb 1-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[   16.911759] usb 1-2: Product: Back-UPS RS 500 FW:30.j5.I USB FW:j5
[   16.930240] usb 1-2: Manufacturer: American Power Conversion
[   16.947162] usb 1-2: SerialNumber: BB0522001803  
[   17.196055] usb 2-1: new full speed USB device using uhci_hcd and address 2
[   17.362962] usb 2-1: not running at top speed; connect to a high speed hub
[   17.421056] usb 2-1: configuration #1 chosen from 1 choice
[   17.441668] usb 2-1: New USB device found, idVendor=04b8, idProduct=0007
[   17.461799] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   17.483160] usb 2-1: Product: USB2.0 Printer
[   17.495921] usb 2-1: Manufacturer: EPSON
[   17.507654] usb 2-1: SerialNumber: L53010309051407480
[   17.582344] udevd version 125 started
[   17.914036] usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 
0x04B8 pid 0x0007
[   17.939357] usbcore: registered new interface driver usblp
[   19.239414] Linux agpgart interface v0.103
[   19.260012] agpgart: Detected VIA VT3314 chipset
[   19.284001] agpgart: AGP aperture is 128M @ 0xf000
[   19.376226] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[   19.489823] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   19.549868] input: Power Button (FF) as /class/input/input0
[   19.614319] ACPI: Power Button (FF) [PWRF]
[   19.626771] input: Sleep Button (CM) as /class/input/input1
[   19.849287] ACPI: Sleep Button (CM) [SLPB]
[   19.861698] input: Power Button (CM) as /class/input/input2
[   20.153783] ACPI: Power Button (CM) [PWRB]
[   21.091473] input: PC Speaker as /class/input/input3
[   21.198340] Error: Driver 'pcspkr' is already registered, aborting...
[   21.246645] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip 
loaded successfully
[   21.278547] flexcop-pci: will use the HW PID filter.
[   21.293419] flexcop-pci: card revision 2
[   21.305166] ACPI: PCI Interrupt :05:08.0[A] -> GSI 17 (level, low) -> 
IRQ 17
[   21.419065] e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2.5-NAPI
[   21.437961] e1000e: Copyright(c) 1999 - 2009 Intel Corporation.
[   21.512193] DVB: registering new adapter (FlexCop Digital TV device)
[   21.536016] b2c2-flexcop: MAC address = 00:d0:d7:0d:d6:3a
[   21.552244] b2c2-flexcop: i2c master_xfer failed
[   21.565399] b2c2-flexcop: i2c master_xfer failed
[   21.579204] CX24123: cx24123_i2c_readreg: reg=0x0 (error=-121)
[   21.596638] CX24123: wrong demod revision: 87
[   21.735111] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
[   21.831729] b2c2-flexcop: i2c master_xfer failed
[   22.048190] b2c2-flexcop: i2c master_xfer failed
[   22.097489] b2c2-flexcop: found 'Zarlink MT352 DVB-T' .
[   22.114223] DVB: registering frontend 0 (Zarlink MT352 DVB-T)...
[   22.134281] b2c2-flexcop: initialization of 'Air2PC/AirStar 2 DVB-T' at the 
'PCI' bus controlled by a 'FlexCopIIb' complete
[   22.167991] ACPI: PCI Interrupt :03:00.0[A] -> GSI 16 (level, low) -> 
IRQ 16
[   22.190224] PCI: Disallowing DAC for device :03:00.0
[   22.206217] PCI: Setting latency timer of device :03:00.0 to 64
[   22.206388] :03:00.0: : Failed to initialize MSI interrupts.  Falling 
back to legacy interrupts.
[   22.236269] flexcop-pc

Bug#494913: Suspend-to-RAM resume fails after undocking

[Eric Price]

On 2009-08-15 20:05 +0200, Moritz Muehlenhoff wrote:
> On Tue, Aug 12, 2008 at 09:44:20PM -0400, Eric Price wrote:
> > Package: acpi-support
> > Version: 0.109-5
> > 
> > My suspend-to-RAM works reliably most of the time, but always fails on
> > resuming the first sleep after I remove my laptop from its dock.  The
> > sleep icon switches to the battery icon, but the screen remains black
> > and doesn't respond to anything other than a hard shutdown.  Nothing
> > is logged to syslog during the resume; how can I help debug this?
> > 
> > This happens with all the SUSPEND_METHODS in
> > /etc/default/acpi-support.
> > 
> > I'm using Lenny on a Thinkpad X60s.
> 
> Does this error still occur with more recent kernel versions?

It still happens in 2.6.29-bpo.2-686.

Eric



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

Bug#512960: marked as done (Realtek r8169: icmp6 neighbor discovery doesn't work)

[Debian Bug Tracking System]

Your message dated Sat, 22 Aug 2009 02:15:13 +0100
with message-id <1250903713.16001.216.ca...@localhost>
and subject line Re: Realtek r8169: icmp6 neighbor discovery doesn't work
has caused the Debian Bug report #512960,
regarding Realtek r8169: icmp6 neighbor discovery doesn't work
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.)


-- 
512960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-13
Severity: normal

Dear Maintainers,

the RealTek RTL-8169 Gigabit Ethernet driver (r8169.ko) doesn't work
properly with icmp6.

I can't see any incoming icmp6 neighbor solicitation with tcpdump. But,
when I switch the interface in allmulticast mode:

ip set link allmulticast on dev eth0

everythink works. I can see icmp6 neighbor solicitations and appropriate
neighbor advertisements.

Is there some hardware limitation or is this a driver bug?

(Mainboard is an Asus M3A78 PRO)


Regards
Friedemann

-- Package-specific info:
** Version:
Linux version 2.6.26-1-amd64 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 
4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 17:57:00 UTC 
2009

** Command line:
root=/dev/md0 ro 

** Not tainted

** Kernel log:
[6.494554] r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
[6.494611] ACPI: PCI Interrupt :02:00.0[A] -> GSI 18 (level, low) -> 
IRQ 18
[6.494694] PCI: Setting latency timer of device :02:00.0 to 64
[6.494976] eth0: RTL8168c/8111c at 0xc2c38000, 00:22:15:fd:b1:0d, 
XID 3c4000c0 IRQ 1277
[   36.801716] r8169: eth0: link up
[   36.805223] r8169: eth0: link up

** Loaded modules:
Module  Size  Used by
sg 36448  0 
kvm_amd29580  0 
kvm   127464  1 kvm_amd
ip6t_REJECT 8320  2 
xt_NFLOG6400  2 
ip6table_filter 7296  1 
ip6_tables 23056  1 ip6table_filter
xt_tcpudp   7680  1 
ipt_REJECT  7552  2 
ipt_ULOG   13736  3 
iptable_filter  7424  1 
ip_tables  21520  1 iptable_filter
x_tables   25224  7 
ip6t_REJECT,xt_NFLOG,ip6_tables,xt_tcpudp,ipt_REJECT,ipt_ULOG,ip_tables
nfsd  248360  17 
auth_rpcgss47520  1 nfsd
exportfs8704  1 nfsd
nfs   251696  0 
lockd  68560  2 nfsd,nfs
nfs_acl 7552  2 nfsd,nfs
sunrpc197480  14 nfsd,auth_rpcgss,nfs,lockd,nfs_acl
bridge 53544  0 
xfs   475432  7 
aes_x86_64 12416  4 
aes_generic32552  1 aes_x86_64
xts 7680  2 
gf128mul   12800  1 xts
dm_crypt   17032  1 
crypto_blkcipher   21636  4 xts,dm_crypt
ipv6  288328  67 ip6t_REJECT
loop   19468  0 
snd_hda_intel 434904  0 
serio_raw   9860  0 
pcspkr  7040  0 
psmouse42268  0 
k8temp  9216  0 
snd_pcm81672  1 snd_hda_intel
snd_timer  25744  1 snd_pcm
snd63688  3 snd_hda_intel,snd_pcm,snd_timer
soundcore  12064  1 snd
snd_page_alloc 13072  2 snd_hda_intel,snd_pcm
i2c_piix4  13072  0 
i2c_core   27936  1 i2c_piix4
wmi11712  0 
button 11680  0 
shpchp 34080  0 
pci_hotplug32056  1 shpchp
evdev  14208  0 
ext3  125072  5 
jbd51240  1 ext3
mbcache12804  1 ext3
dm_mirror  20608  0 
dm_log 13956  1 dm_mirror
dm_snapshot19400  0 
dm_mod 58864  31 dm_crypt,dm_mirror,dm_log,dm_snapshot
raid456   125984  1 
async_xor   8448  1 raid456
async_memcpy6912  1 raid456
async_tx   11764  3 raid456,async_xor,async_memcpy
xor 9744  2 raid456,async_xor
raid1  24192  3 
md_mod 80164  6 raid456,raid1
usb_storage94528  0 
ata_generic10116  0 
ide_pci_generic 9220  0 [permanent]
atiixp  8324  0 [permanent]
ide_core  128284  2 ide_pci_generic,atiixp
ehci_hcd   36108  0 
ohci_hcd   25092  0 
r8169  31492  0 
sd_mod 29376  12 
thermal22688  0 
processor  42304  1 th

Bug#538431: I got a similar error

[Harry]

After installing the module, I issued the command:
sudo modprobe fglrx


The error is :

FATAL: Error inserting fglrx 
(/lib/modules/2.6.30-1-686/nonfree/fglrx/fglrx.ko): Cannot allocate memory



The machine is with ATI x700.

Hope this is helpful.

Regards,

Harry



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

Bug#506149: Sony W980 mobile phone in mass storage mode does not initialise and mount

[Moritz Muehlenhoff]

On Tue, Nov 18, 2008 at 12:21:18PM -0800, Stuart Chalmers wrote:
> Package: Unknown
> Version Unknown
> 
> Hi,
> 
> Description:
> 
> Connect Sony W980 phone to up to date Lenny as at 17/11/2008.  It does
> not detect and auto mount in the Gnome (2.22) desktop (clean install from 
> Debian installer RC1 DVD followed by online update to 17/11/08).  The phone's 
> mass storage worked from
> Etch installation around one week previously.

[..]

> It would be very much appreciated is this could be looked at.

Sorry for the late response. Many USB mass storage devices are not fully
compliant and require various quirks. 

For starters, please test an 2.6.31-rcX kernel from trunk:
http://wiki.debian.org/DebianKernel 

If the problem persists, please file a bug report at bugzilla.kernel.org,
so that the necessary quirk can be identified and associated to your
device.

Cheers,
Moritz



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

Bug#504677: linux-image-2.6.24: Nov 4 09:43:03 localhost kernel: Pid: 28888, comm: rsync Not tainted 2.6.24 #1

[Moritz Muehlenhoff]

On Thu, Nov 06, 2008 at 10:28:05AM +0800, root wrote:
> Package: linux-image-2.6.24
> Version: custom.1.0
> Severity: normal
> 
> 
> v  4 09:43:03 localhost kernel: Pid: 2, comm: rsync Not tainted
> 2.6.24 #1
> Nov  4 09:43:03 localhost kernel:  []
> xfs_trans_cancel+0x59/0xe2 [xfs]
> Nov  4 09:43:03 localhost kernel:  [] xfs_create+0x3e5/0x458
> [xfs]
> Nov  4 09:43:03 localhost kernel:  [] xfs_create+0x3e5/0x458
> [xfs]
> Nov  4 09:43:03 localhost kernel:  [] xfs_vn_mknod+0x150/0x252
> [xfs]
> Nov  4 09:43:03 localhost kernel:  [] vfs_create+0xb6/0xfc
> Nov  4 09:43:03 localhost kernel:  [] open_namei+0x16d/0x52e
> Nov  4 09:43:03 localhost kernel:  [] do_filp_open+0x25/0x39
> Nov  4 09:43:03 localhost kernel:  []
> get_unused_fd_flags+0x4c/0xb9
> Nov  4 09:43:03 localhost kernel:  [] do_sys_open+0x44/0xc5
> Nov  4 09:43:03 localhost kernel:  [] sys_open+0x1c/0x1e
> Nov  4 09:43:03 localhost kernel:  []
> sysenter_past_esp+0x5f/0x85
> Nov  4 09:43:04 localhost kernel:  [] sigd_send+0x200/0x2ab
> Nov  4 09:43:04 localhost kernel:  ===
> Nov  4 09:43:04 localhost kernel: xfs_force_shutdown(md0,0x8) called
> from line 1164 o
> f file fs/xfs/xfs_trans.c.  Return address = 0xe0cdc19c
> Nov  4 09:45:25 localhost kernel: xfs_force_shutdown(md0,0x1) called
> from line 420 of
>  file fs/xfs/xfs_rw.c.  Return address = 0xe0ce66a0
>  Nov  4 09:45:25 localhost kernel: xfs_force_shutdown(md0,0x1) called
>  from line 420 of
>   file fs/xfs/xfs_rw.c.  Return address = 0xe0ce66a0

Do you still run Etch? If so, does this error still show up with
the official 2.6.24 kernel?

If you've upgraded in the mean time, has this been fixed by upstream
changes?

Cheers,
Moritz



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

Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.

[Moritz Muehlenhoff]

On Wed, Nov 05, 2008 at 10:10:54PM +0100, Frans Pop wrote:
> reassign 504016 linux-2.6
> thanks
> 
> On Saturday 01 November 2008, Hans-Joachim Zierke wrote:
> > But I found it by completely disabling almost everything in the BIOS,
> > getting a success, then systematically reenabling stuff.
> >
> > It's the Promise ATA-100 BIOS. If I reset that BIOS from "Auto" to
> > "Disabled", then I get the
> >
> >   Ok, booting the kernel
> >
> > message. The A7V Board has an ATA-66 controller in the chipset, plus an
> > additional ATA-100 Promise controller on the motherboard.
> 
> The strange thing is that your initial report shows that the initrd and 
> kernel do get loaded from the CD; it just fails to take the next step.
> 
> As this really looks like a kernel issue, I'm reassigning your report to 
> the kernel team. Maybe they can offer additional help.
> 
> > > It could also possibly an isolinux problem. have you tried installing
> > > the Lenny kernel on your Etch system and booting that?
> >
> > I won't even know how to do that.  ;-)  I know how to compile a kernel
> > for the running system with make-kpkg, but that's it.
> 
> Just download the package from packages.debian.org and install it 
> using 'dpkg -i '.
> 
> > I'm not a Linux freak, but a user. When I looked for Lenny news on the
> > website, I read that we should try the installer, so I did.
> 
> Thanks a lot for testing it. We do appreciate that and the fact that you 
> filed your installation report.
> 
> Unfortunately when you do run into such a problem with Linux it's 
> basically up to the user to find the correct person to look into the 
> problem and to provide any needed info to track it down. Depending on the 
> issue, that can require a significant amount of effort on the user's 
> part.

Hans-Joachim, did you try later versions of the installer on this
system? Did any of them succeed?

Cheers,
Moritz



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

Bug#504584: [kernel] mount.cifs fails to mount MS DFS shares (object is remote)

[Moritz Muehlenhoff]

On Thu, Jun 18, 2009 at 03:43:07PM +0200, Bastian Blank wrote:
> On Wed, Nov 05, 2008 at 12:35:05PM +0100, ulrich.me...@ulmeco.ch wrote:
> > unable to mount microsoft dfs share
> 
> Please install keyutils and fix /etc/request-key.conf according to the
> cifs.upcall manpage.

Ulrich, did you test this?

Cheers,
Moritz



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

Bug#504016: marked as done (Lenny Beta II + daily build, kernel dies after initrd.gz....ready.)

[Debian Bug Tracking System]

Your message dated Sat, 22 Aug 2009 00:47:40 +0200
with message-id <20090821224740.ga11...@galadriel.inutil.org>
and subject line Re: Bug#504016: Lenny Beta II + daily build, kernel dies after 
initrd.gzready.
has caused the Debian Bug report #504016,
regarding Lenny Beta II + daily build, kernel dies after initrd.gzready.
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.)


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

Boot method: Booted from CD
 The following is copied from Etch dmesg

 sym0: <810a> rev 0x12 at pci :00:0c.0 irq 11
 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking
 sym0: SCSI BUS has been reset.
 scsi0 : sym-2.2.3
   Vendor: PLEXTOR   Model: CD-ROM PX-40TSRev: 1.01
   Type:   CD-ROM ANSI SCSI revision: 02
 target0:0:1: Beginning Domain Validation
 target0:0:1: asynchronous
 target0:0:1: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 8)

 BIOS is SDMS 4.12.0.0, and reports "No Emulation" mode on 
 BIOS screen while booting.


Image version: 157034496 2008-10-28 22:11 debian-LennyBeta2-i386-netinst.iso

   Second try with daily build
   debian-testing-i386-netinst.iso
   from
   
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/

   But it is also reproducible with a Knoppix CD, and 
   therefore probably a general Isolinux problem not 
   limited to the Debian Installer.   
   
Date:  Oct 29

Machine:   Homebuilt 24/7 machine, motherboard ASUS A7V 1.04 with 
   latest BIOS 1011 from 2002, running under Debian Etch 
   normally.

   SCSI controller is an ASUS SC-200, 
   SDMS BIOS 4.12.0.0 is delivered by the motherboard, as usual
   for these controllers.
   

Processor: Duron 600

   CPU: After generic identify, caps: 0183f9ff c1c7f9ff  
   
   CPU: After vendor identify, caps: 0183f9ff c1c7f9ff  
   
   CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
   CPU: L2 Cache: 64K (64 bytes/line)
   CPU: After all inits, caps: 0183f9ff c1c7f9ff  0420 
  
   Intel machine check architecture supported.
   Intel machine check reporting enabled on CPU#0.
   CPU: AMD Duron(tm) Processor stepping 00
   Checking 'hlt' instruction... OK.

Memory:SDRAM 100

   383MB LOWMEM available.

Partitions:FilesystemType   1K-blocks  Used Available Use% Mounted 
on
   /dev/hda1 ext321342047   456  15813206  22% /
   tmpfstmpfs  193452 0193452   0% 
/lib/init/rw
   udev tmpfs   1024084 10156   1% /dev
   tmpfstmpfs  193452 8193444   1% /dev/shm
   /dev/hdc2 ext391658564  44736272  42266256  52% /home
   /dev/hde1 ext3   476750548 341159516 111373448  76% 
/home/hajo/Archiv
   /dev/hdf1 ext3   240362656 143533616  84619240  63% 
/home/hajo/Archiv/Bahn


Output of lspci -knn (or lspci -nn):

00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] 
[1106:0305] (rev 02)
00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] 
[1106:8305]
00:04.0 ISA bridge [0601]: VIA Technologies, Inc. VT82C686 [Apollo Super South] 
[1106:0686] (rev 22)
00:04.1 IDE interface [0101]: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 10)
00:04.2 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 
Controller [1106:3038] (rev 10)
00:04.3 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 
Controller [1106:3038] (rev 10)
00:04.4 Bridge [0680]: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] 
[1106:3057] (rev 30)
00:09.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video 
Capture [109e:036e] (rev 02)
00:09.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture 
[109e:0878] (rev 02)
00:0a.0 Multimedia controller [0

Bug#351685: marked as done (udev storm: pcmcia CF adapter device file constantly deleted, recreated)

[Debian Bug Tracking System]

Your message dated Sat, 22 Aug 2009 00:33:46 +0200
with message-id <20090821223346.ge15...@galadriel.inutil.org>
and subject line Re: Bug#351685: udev storm: pcmcia CF adapter device file 
constantly deleted, recreated
has caused the Debian Bug report #351685,
regarding udev storm: pcmcia CF adapter device file constantly deleted, 
recreated
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.)


-- 
351685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=351685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pcmciautils
Version: 012-3
Severity: normal

I inserted a pcmcia CF adapter containing a partition with a FAT filesystem
and tried to mount it, but /dev/hde1 was not there, though /dev/hde was.
I eventually realised that hde1 was being constantly deleted and
recreated over and over. ls showed it there and missing, randomly.

r...@dragon:/>while :; do ls /dev/hde*; done
/dev/hde
/dev/hde
/dev/hde
/dev/hde
/dev/hde
/dev/hde
/dev/hde  /dev/hde1
ls: /dev/hde1: No such file or directory
/dev/hde
/dev/hde
/dev/hde
/dev/hde
/dev/hde  /dev/hde1
/dev/hde  /dev/hde1
/dev/hde  /dev/hde1
ls: /dev/hde1: No such file or directory
/dev/hde
/dev/hde
/dev/hde
/dev/hde
/dev/hde
/dev/hde

I manually used mknod to create the device file in /tmp, and then was
able to mount and access it with no difficulty.

Here's the kernel log:

Feb  6 12:27:23 dragon kernel: pccard: PCMCIA card inserted into slot 0
Feb  6 12:27:23 dragon kernel: pcmcia: registering new device pcmcia0.0
Feb  6 12:27:24 dragon kernel: Probing IDE interface ide2...
Feb  6 12:27:24 dragon kernel: hde: Renesas XX.V.3.5.0.0, CFA DISK drive
Feb  6 12:27:25 dragon kernel: ide2 at 0x100-0x107,0x10e on irq 3
Feb  6 12:27:25 dragon kernel: hde: max request size: 128KiB
Feb  6 12:27:25 dragon kernel: hde: 2002896 sectors (1025 MB) w/1KiB Cache, 
CHS=1987/16/63
Feb  6 12:27:25 dragon kernel: hde: cache flushes not supported
Feb  6 12:27:25 dragon kernel:  hde: hde1
Feb  6 12:27:25 dragon kernel: ide-cs: hde: Vcc = 3.3, Vpp = 0.0
Feb  6 12:27:25 dragon kernel:  hde: hde1
Feb  6 12:29:16 dragon kernel:  hde: hde1
Feb  6 12:29:21 dragon last message repeated 37 times
Feb  6 12:29:46 dragon kernel:  hde: hde1
Feb  6 12:30:16 dragon last message repeated 148 times
Feb  6 12:31:17 dragon last message repeated 386 times
Feb  6 12:32:01 dragon last message repeated 300 times
Feb  6 12:32:01 dragon kernel:  hde: hde1
Feb  6 12:32:06 dragon last message repeated 28 times
Feb  6 12:32:06 dragon kernel:  hde: hde1
Feb  6 12:32:37 dragon last message repeated 145 times
Feb  6 12:33:38 dragon last message repeated 349 times
Feb  6 12:34:36 dragon last message repeated 442 times

Apparently each of these "hde: hde1" printk's corresponds to a deletion
and recretion of the device node. After I mounted the device, used it for
a while, and unmounted it, this activity had stopped, now /dev/hde1 is stable.

If I eject and re-insert the card, the same problem occurs. If I eject
the card while this storm is ongoing, my system freezes hard with the
pcmcia activity LED showing constant pcmcia activity.

I don't really know if this is a pcmciautils, udev, kernel, or all three
bug. Using the 2.4 kernel and pcmcia-cs, this card works fine.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages pcmciautils depends on:
ii  libc6 2.3.5-12   GNU C Library: Shared libraries an
ii  libsysfs1 1.3.0-7interface library to sysfs
ii  module-init-tools 3.2.2-1tools for managing Linux kernel mo

Versions of packages pcmciautils recommends:
ii  udev  0.084-1/dev/ and hotplug management daemo

-- no debconf information

Here's what the kernel has to say about my pcmcia at boot:

Yenta: CardBus bridge found at :00:0c.0 [10cf:10c6]
Yenta: adjusting diagnostic: 41 -> 61
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket :00:0c.0, mfunc 0x00c61d22, devctl 0x46
Yenta: ISA IRQ mask 0x0cf8, PCI irq 9
Socket status: 3006

-- 
see shy jo


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 2.6.26-1

On Fri, Aug 21, 2009 at 06:17:47PM -0400, Joey Hess wrote:
> Moritz Muehlenhoff wrote:
> > Joey, does t

Bug#351685: udev storm: pcmcia CF adapter device file constantly deleted, recreated

[Joey Hess]

Moritz Muehlenhoff wrote:
> Joey, does this still persist?

Dug the ancient laptop out; cannot reproduce with the 2.6.26 from 2008
that is on it.

Can't tell if that's due to udev's mitigation of the kernel bug, or the
kernel bug being fixed though.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#351685: udev storm: pcmcia CF adapter device file constantly deleted, recreated

[Moritz Muehlenhoff]

On Sun, Aug 09, 2009 at 05:41:31PM -0700, Bill Wohler wrote:
> Moritz Muehlenhoff  wrote:
> 
> > On Fri, Mar 10, 2006 at 10:40:58AM +0100, Marco d'Itri wrote:
> > > On Mar 09, Bill Wohler  wrote:
> > > 
> > > > I see this bug was moved to linux-2.6. However, there is also a udev bug
> > > > #350235 filed for the same problem. While it appears there is a major
> > > > udev component (the UI always gets the heat), it also appears to be a
> > > > kernel component as well since a kernel oops was reported. Since this
> > > Let's get the facts straight: this is not an udev bug, not even close.
> > > udev just has a workaround to prevent it from triggering the first
> > > kernel bug.
> > > The first bug is the events loop caused by ide-cs and ide-floppy when
> > > udev opens the block device, and the second bug is the oops which
> > > happens after this.
> > 
> > Does this still occur with more recent kernels?
> 
> Hi Moritz, unfortunately, I have a new laptop that comes with nice card
> slots built-in, so I haven't had the opportunity to test PCMCIA. I
> haven't seen any oops with this laptop, so I guess you could close this
> bug on my account. However, it would be good to confirm with Joey since
> he reported the original behavior.

Ok, adding him on CC.

Joey, does this still persist?

Cheers,
Moritz



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

Bug#459861: marked as done (linux-image-2.6.18-5-amd64: usb 2 uses irq 7, with no 2.0 device attached, irq 7 disabled, "nobody cared")

[Debian Bug Tracking System]

Your message dated Fri, 21 Aug 2009 20:41:47 +0200
with message-id <20090821184147.gb5...@galadriel.inutil.org>
and subject line Re: Bug#541441: CVE-2009-2726: Asterisk SIP Channel Driver 
Denial of   Service
has caused the Debian Bug report #459861,
regarding linux-image-2.6.18-5-amd64: usb 2 uses irq 7, with no 2.0 device 
attached, irq 7 disabled, "nobody cared"
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.)


-- 
459861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.18-5-amd64
Version: 2.6.18.dfsg.1-17
Severity: normal

I have a usb 2.0 160 GB disk drive which I've been trying to use with my
HP laptop, but after some period of time (usually short, less than 2
minutes) the disk would "die".

Research led to a possible solution, using sdparm to clear STANDBY,
which is set by default for this drive (Seagate Freeagent Go).  This
seemed to work, initially, but it didn't "hold".  Checked the STANDBY
state, it was still cleared.

And, other usb 2.0 devices also failed to work.  Extensive further
research and testing showed that all these devices would work for a
short period of time before failing.

The light dawned when I noted that the usb 2.0 interface uses IRQ 7,
which was getting disabled shortly after startup, due to a spurious
interrupt (nobody cared).

With a usb device inserted while booting, or quickly attached after
booting, along with mounting the disk device, there were no spurious
interrupts, and the device remained usable.  That is, until it/they
waswere unmounted, at which point, with no usb 2.0 devices, a spurious
interrupt would happen and usb 2.0 would not work any more.

As proof of concept, I've moved my full system to the Freeagent disk and
can boot to it, and run for hours, without issues.

I have also booted a Suse 9.1 Live CD and have used the usb 2.0 devices
without problems, even though dmesg does have one spurious interrupt
error related to irq 7.  The kernel version is 2.6.4

My system is an HP Pavilion dv9000.  The usb 2.0 hardware is reported as:

00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)\
  (prog-if 20 [EHCI])
Subsystem: Hewlett-Packard Company Unknown device 30b7
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 7
Memory at b0005000 (32-bit, non-prefetchable)[size=256]
Capabilities: [44] Debug port
Capabilities: [80] Power Management version 2

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-5-amd64 depends on:
ii  cor 5.97-5.3 The GNU core utilities
ii  deb 1.5.11etch1  Debian configuration management sy
ii  e2f 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 ext2 file system utilities and lib
ii  ini 0.85htools for generating an initramfs
ii  mod 3.3-pre4-2   tools for managing Linux kernel mo

linux-image-2.6.18-5-amd64 recommends no packages.

-- debconf information:
  linux-image-2.6.18-5-amd64/postinst/create-kimage-link-2.6.18-5-amd64: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-5-amd64/postinst/old-system-map-link-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/initrd-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/preinst/elilo-initrd-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/postinst/depmod-error-2.6.18-5-amd64: false
  linux-image-2.6.18-5-amd64/preinst/bootloader-initrd-2.6.18-5-amd64: true
* linux-image-2.6.18-5-amd64/preinst/already-running-this-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/prerm/removing-running-kernel-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/lilo-initrd-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/abort-overwrite-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/preinst/failed-to-move-modules-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/prerm/would-invalidate-boot-loader-2.6.18-5-amd64: 
true
  linux-image-2.6.18-5-amd64/postinst/bootloader-error-2.6.18-5-amd64:
  linux-image-2.6.18-5-amd64/postinst/old-initrd-link-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/overwriting-modules-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/postinst/old-dir-initrd-link-2.6.18-5-amd64: true
  linux-image-2.6.18-5-amd64/preinst/lilo-has-ramdisk:
  linux-image-2.6.18-5-amd64/postinst/depmod-error-initrd-2.6.18-5

Processed: forcibly merging 464197 493928

[Debian Bug Tracking System]

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

> forcemerge 464197 493928
Bug#464197: snd-cs46xx.ko module seems to be missing from 
linux-image-2.6.24-1-686
Bug#493928: linux-image-2.6.26-1-686: driver snd-cs46xx.ko should be compiled 
by default.
Bug#430017: kernel: Recording silence, chipset: Cirrus Logic CS 4614/22/24 
[CrystalClear SoundFusion Audio Accelerator]
Bug#455092: Please continue to provide cs46xx sound module
Bug#462035: linux-image-2.6.23-1-686: snd_cs46xx missing
Bug#468151: Files missing for SND_CS46XX module
Bug#476672: linux-image-2.6.24-1-686: alsa snd-cs46xx module missing (all 
linux-image packages)
Bug#477409: linux-image-2.6.24-1-686: Sound stopped working with new kernel
Bug#493924: linux-image-2.6.25-2-686: driver snd-cs46xx.ko should be compiled 
by default.
Bug#493926: linux-image-2.6.26-1-686: driver snd-cs46xx.ko should be compiled 
by default.
Forcibly Merged 430017 455092 462035 464197 468151 476672 477409 493924 493926 
493928.

>
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

Bug#508599: linux-image-2.6.26-1-686: Increase power_up delay to fix TI readers

[Moritz Muehlenhoff]

On Sat, Dec 13, 2008 at 01:05:12PM +0100, Moritz Muehlenhoff wrote:
> On Fri, Dec 12, 2008 at 11:35:06PM +0100, Geert Stappers wrote:
> > Package: linux-image-2.6.26-1-686
> > Version: 2.6.26-11
> > Severity: normal
> > Tags: patch
> > 
> > Hello Kernel maintainers,
> > 
> > To get a SD cardreader working I needed to do
> > 
> > diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
> > index 01ced4c..11f050c 100644
> > --- a/drivers/mmc/core/core.c
> > +++ b/drivers/mmc/core/core.c
> > @@ -492,7 +492,7 @@ static void mmc_power_up(struct mmc_host *host)
> >  * This delay must be at least 74 clock sizes, or 1 ms, or the
> >  * time required to reach a stable voltage.
> >  */
> > -   mmc_delay(2);
> > +   mmc_delay(10);
> >  }
> >  
> >  static void mmc_power_off(struct mmc_host *host)
> 
> Please send this patch to the kernel subsystem maintainer 
> (Pierre Ossman ) for review/merge.

Pierre Ossman no longer maintains the MMC subsystem, please contact
linux-...@vger.kernel.org instead.
 
Cheers,
Moritz



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

Bug#539226: marked as done (aufs: FTBFS armel)

[Debian Bug Tracking System]

Your message dated Fri, 21 Aug 2009 19:24:19 +0200
with message-id <20090821172419.ga1...@galadriel.inutil.org>
and subject line Closing
has caused the Debian Bug report #539226,
regarding aufs: FTBFS 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.)


-- 
539226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aufs-source
Severity: serious

Hi,

aufs FTBFS on armel:
https://buildd.debian.org/fetch.cgi?pkg=linux-modules-extra-2.6;ver=2.6.30-1;arch=armel;stamp=1248004900

Reegards,
Daniel

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  daniel.baum...@panthera-systems.net
Internet:   http://people.panthera-systems.net/~daniel-baumann/


--- End Message ---
--- Begin Message ---
Version: 2.6.30-4

--- End Message ---

Processed: reassign 493928 to linux-2.6

[Debian Bug Tracking System]

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

> reassign 493928 linux-2.6
Bug #493928 [linux-image-2.6.26-1-686] linux-image-2.6.26-1-686: driver 
snd-cs46xx.ko should be compiled by default.
Bug reassigned from package 'linux-image-2.6.26-1-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.26-1.
>
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 471495

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny3
> tags 471495 + pending
Bug #471495 [linux-2.6] linux-2.6: please add Vcs-* fields/headers to 
debian/control file
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 535646

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny3
> tags 535646 + pending
Bug #535646 [linux-2.6] lm-sensors: module w83627ehf fails to load
Ignoring request to alter tags of bug #535646 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 518710

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny3
> tags 518710 + pending
Bug #518710 [linux-2.6] /bin/ip: ip missed inet6 addr preferred_lft wrap around
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

Bug#494573: [linux-image-2.6.26-1-686] ACPI unsupportet Model --> DSDT

[Moritz Muehlenhoff]

On Sun, Aug 10, 2008 at 08:31:19PM +0200, wic...@gmx.at wrote:
> Package: linux-image-2.6.26-1-686
> Version: 2.6.26-1
> Severity: normal
> 
> In dmesg:
> [   19.026944] Asus Laptop ACPI Extras version 0.30
> [   19.030945]   unsupported model X55SV, trying default values
> [   19.030945]   send /proc/acpi/dsdt to the developers
> 
> This Notebook is a Asus X55SV-AP166C 
> May this help you to support this Model

Is this model supported in more recent kernel versions, like
the 2.6.30 kernel from unstable or the trunk snapshot kernels
from http://wiki.debian.org/DebianKernel?

If not, please bring it to the attention of the Linux kernel
developers by opening a bug at http://bugzilla.kernel.org.
Afterwards please send us the bug number.

Cheers,
Moritz



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

Bug#506223: I can confirm that

[Moritz Muehlenhoff]

On Thu, Feb 19, 2009 at 09:10:47PM +, Marcin Owsiany wrote:
> I just wiped my etch installation and replaced it with a fresh lenny
> installation. The installer auto-detected my wifi card and used the
> rt2500pci driver.
> 
> By default it achieves:
>  - 1Mbps rate (as reported by iwconfig - I can only download at max.
>~20KBps)
>  - approx "50% link quality"
> 
> When I manually set it to "rate 11M", the reported bit rate goes to 11M,
> the real download speed improves by about 50% and the "link quality"
> goes to about 70%, but it's still a far cry from what the card can
> achieve.
> 
> It works just fine using ndiswrapper...

Has this been fixed in later kernels like the 2.6.30 from unstable or
backports.org? There have been many changes since the Lenny kernel.

Cheers,
Moritz



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

Bug#506153: marked as done (linux-image-2.6.26-1-parisc64: SCTP packets have invalid checksum)

[Debian Bug Tracking System]

Your message dated Fri, 21 Aug 2009 19:03:14 +0200
with message-id <20090821170314.ga25...@galadriel.inutil.org>
and subject line Re: Bug#506153: Acknowledgement 
(linux-image-2.6.26-1-parisc64: SCTP packets have invalid checksum)
has caused the Debian Bug report #506153,
regarding linux-image-2.6.26-1-parisc64: SCTP packets have invalid checksum
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.)


-- 
506153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-1-parisc64
Version: 2.6.26-8
Severity: normal


The SCTP packets sent have invalid checksum. It seems as if the SCTP packet
checksum is in wrong byte order (checksum on packet is 0xd9f4c234 and it
should be 0x34c2f4d9). 

The bug causes all SCTP connection attempts (packets with INIT chunks) made
from this host to be silently ignored by the destination. Also all connection
attempts to this host get dropped even if they have valid SCTP checksum. 

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: hppa (parisc64)

Kernel: Linux 2.6.26-1-parisc64
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 linux-image-2.6.26-1-parisc64 depends on:
ii  debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92j  tools for generating an initramfs
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo

linux-image-2.6.26-1-parisc64 recommends no packages.

Versions of packages linux-image-2.6.26-1-parisc64 suggests:
pn  linux-doc-2.6.26   (no description available)
ii  palo  1.16+nmu1  Linux boot loader for parisc/hppa

-- debconf information:
  linux-image-2.6.26-1-parisc64/preinst/lilo-has-ramdisk:
  
linux-image-2.6.26-1-parisc64/prerm/removing-running-kernel-2.6.26-1-parisc64: 
true
  linux-image-2.6.26-1-parisc64/preinst/lilo-initrd-2.6.26-1-parisc64: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.26-1-parisc64/postinst/kimage-is-a-directory:
  linux-image-2.6.26-1-parisc64/preinst/abort-install-2.6.26-1-parisc64:
  linux-image-2.6.26-1-parisc64/preinst/already-running-this-2.6.26-1-parisc64:
  linux-image-2.6.26-1-parisc64/postinst/old-initrd-link-2.6.26-1-parisc64: true
  linux-image-2.6.26-1-parisc64/preinst/bootloader-initrd-2.6.26-1-parisc64: 
true
  linux-image-2.6.26-1-parisc64/postinst/bootloader-error-2.6.26-1-parisc64:
  linux-image-2.6.26-1-parisc64/postinst/old-dir-initrd-link-2.6.26-1-parisc64: 
true
  
linux-image-2.6.26-1-parisc64/preinst/failed-to-move-modules-2.6.26-1-parisc64:
  linux-image-2.6.26-1-parisc64/preinst/elilo-initrd-2.6.26-1-parisc64: true
  linux-image-2.6.26-1-parisc64/postinst/depmod-error-initrd-2.6.26-1-parisc64: 
false
  
linux-image-2.6.26-1-parisc64/postinst/bootloader-test-error-2.6.26-1-parisc64:
  linux-image-2.6.26-1-parisc64/postinst/create-kimage-link-2.6.26-1-parisc64: 
true
  linux-image-2.6.26-1-parisc64/postinst/depmod-error-2.6.26-1-parisc64: false
  linux-image-2.6.26-1-parisc64/preinst/initrd-2.6.26-1-parisc64:
  linux-image-2.6.26-1-parisc64/postinst/old-system-map-link-2.6.26-1-parisc64: 
true
  linux-image-2.6.26-1-parisc64/preinst/abort-overwrite-2.6.26-1-parisc64:
  linux-image-2.6.26-1-parisc64/preinst/overwriting-modules-2.6.26-1-parisc64: 
true
  
linux-image-2.6.26-1-parisc64/prerm/would-invalidate-boot-loader-2.6.26-1-parisc64:
 true


--- End Message ---
--- Begin Message ---
Version: 2.6.29-1

On Tue, Feb 03, 2009 at 01:10:32PM +0200, Jukka Taimisto wrote:
> A patch for this issue has been submitted to linux-2.6, available at
> 

Thanks, marking as fixed for unstable.

Cheers,
   Moritz

--- End Message ---

Bug#504391: Please enable CONFIG_MMC_UNSAFE_RESUME

[Moritz Muehlenhoff]

severity 504391 wishlist
tags 504391 wontfix
thanks

On Mon, Nov 03, 2008 at 11:21:15AM +, Ross Burton wrote:
> Package: linux-image-2.6.26-1-686
> Version: 2.6.26-9
> Severity: normal
> 
> At present if I suspend and resume with a SD card inserted, the MMC driver
> crashes.  There is an "unsafe" option which can be enabled to fix this:
> CONFIG_MMC_UNSAFE_RESUME.  I have no idea why enabling this is considered
> unsafe, it took me several failed suspends (and the resulting data loss) to
> discover that the cause was a mounted SD card.

The Kconfig description explicitly describes this as a potentially
harmful option:

config MMC_UNSAFE_RESUME
bool "Allow unsafe resume (DANGEROUS)"
help
  If you say Y here, the MMC layer will assume that all cards
  stayed in their respective slots during the suspend. The
  normal behaviour is to remove them at suspend and
  redetecting them at resume. Breaking this assumption will
  in most cases result in data corruption.

  This option is usually just for embedded systems which use
  a MMC/SD card for rootfs. Most people should say N here.

Marking as wontfix, you should rather unplug your MMC card before
suspending.

But maybe you can file bugs against hibernate and graphical suspend
frontends to warn users if a plugged-in MMC card is detected.

Cheers,
Moritz



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

Bug#494249: (no subject)

[Moritz Muehlenhoff]

On Tue, Sep 02, 2008 at 11:33:43PM +0200, Ultrakiller pippo wrote:
> 
> the monitor does not turn off with image>= 2.6.23
> 
> in my kernel (compiled with vanilla) 2.6.26.1 the monitor works well, with 
> the debian linux-image-2.6.26-*86 the monitor does not work.
> 
> last kernel working kernel is  linux-image-2.6.22-486

Does this work with the final Lenny kernel or later kernel
versions?

Cheers,
Moritz



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

Processed: control

[Debian Bug Tracking System]

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

> severity 376999 wishlist
Bug #376999 [linux-2.6] linux-image-2.6.16-2-686: 'ov511' module seems to lack 
compression.
Severity set to 'wishlist' from 'normal'

>
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

Bug#506424: marked as done (linux-image-2.6.26: copying /proc/*/pagemap leads to resource consumption because of uninitialized struct)

[Debian Bug Tracking System]

Your message dated Fri, 21 Aug 2009 18:49:58 +0200
with message-id <20090821164958.gc15...@inutil.org>
and subject line Re: linux-image-2.6.26: copying /proc/*/pagemap leads to 
resource consumption because of uninitialized struct
has caused the Debian Bug report #506424,
regarding linux-image-2.6.26: copying /proc/*/pagemap leads to resource 
consumption because of uninitialized struct
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.)


-- 
506424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: linux-image-2.6.26: copying /proc/*/pagemap leads to resource 
consumption because of uninitialized struct
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-10
Severity: normal
File: linux-image-2.6.26

*** Please type your report below this line ***

The VMware support script copies various files from /proc to the report 
directory. Copying 
/proc/*/pagemap takes forever and produces a large file, probably filled with 
garbage.

Steps to reproduce:
# cp /proc/self/pagemap /tmp/self.pagemap

I found a LKML thread regarding the problem:
http://lkml.indiana.edu/hypermail/linux/kernel/0807.2/0262.html


-- Package-specific info:
** Version:
Linux version 2.6.26-1-amd64 (Debian 2.6.26-10) (wa...@debian.org) (gcc version 
4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Sat Nov 8 18:25:23 UTC 
2008

** Command line:
root=/dev/sda1 ro quiet

** Not tainted

** Kernel log:
[4.816513] sd 2:0:0:0: [sdb] 312573616 512-byte hardware sectors (160038 MB)
[4.823053] sd 2:0:0:0: [sdb] Write Protect is off
[4.823053] sd 2:0:0:0: [sdb] Mode Sense: 00 56 00 00
[4.838462] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[4.887176] sd 2:0:0:0: [sdb] 312573616 512-byte hardware sectors (160038 MB)
[4.895176] sd 2:0:0:0: [sdb] Write Protect is off
[4.895176] sd 2:0:0:0: [sdb] Mode Sense: 00 56 00 00
[4.911586] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[4.911586]  sdb: unknown partition table
[4.943327] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[4.943327] sd 2:0:0:0: Attached scsi generic sg3 type 0
[4.943327] ACPI: PCI Interrupt :00:1f.5[C] -> GSI 18 (level, low) -> 
IRQ 18
[4.943327] ata_piix :00:1f.5: MAP [ P0 -- P1 -- ]
[5.156285] PCI: Setting latency timer of device :00:1f.5 to 64
[5.160267] scsi3 : ata_piix
[5.160267] scsi4 : ata_piix
[5.160766] ata3: SATA max UDMA/133 cmd 0x1c68 ctl 0x1c5c bmdma 0x1c30 irq 18
[5.160766] ata4: SATA max UDMA/133 cmd 0x1c60 ctl 0x1c58 bmdma 0x1c38 irq 18
[5.508787] ata3: SATA link down (SStatus 0 SControl 300)
[5.836785] ata4: SATA link down (SStatus 0 SControl 300)
[6.428775] Uniform Multi-Platform E-IDE driver
[6.428775] ide: Assuming 33MHz system bus speed for PIO modes; override 
with idebus=xx
[6.442692] Driver 'sr' needs updating - please use bus_type methods
[6.452995] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda 
tray
[6.452999] Uniform CD-ROM driver Revision: 3.20
[6.456539] sr 1:0:0:0: Attached scsi CD-ROM sr0
[6.743231] kjournald starting.  Commit interval 5 seconds
[6.746589] EXT3-fs: mounted filesystem with ordered data mode.
[8.98] udevd version 125 started
[9.236855] input: Power Button (FF) as /class/input/input2
[9.249569] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[9.283521] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[9.307342] ACPI: Power Button (FF) [PWRF]
[9.307426] input: Power Button (CM) as /class/input/input3
[9.373793] ACPI: Power Button (CM) [PWRB]
[9.413194] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.03 (30-Apr-2008)
[9.413194] iTCO_wdt: Found a ICH9R TCO device (Version=2, TCOBASE=0x1060)
[9.413194] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[9.426292] i801_smbus :00:1f.3: enabling device (0001 -> 0003)
[9.426292] ACPI: PCI Interrupt :00:1f.3[B] -> GSI 17 (level, low) -> 
IRQ 17
[9.494924] input: PC Speaker as /class/input/input4
[9.550176] pnp: the driver 'parport_pc' has been registered
[9.550195] parport_pc 00:0b: reported by Plug and Play ACPI
[9.550295] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP]
[9.608522] Error: Driver 'pcspkr' is already registered, aborting...
[9.654145] parport_pc 00:0b: driver attached
[   11.184238] Adding 1951888k swap on /dev/sda2.  Priority:-1 extents:1 
across:1951888k
[   11.992962] EXT

Processed: bug 542551 is forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=13933

[Debian Bug Tracking System]

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

> forwarded 542551 http://bugzilla.kernel.org/show_bug.cgi?id=13933
Bug #542551 [linux-image-2.6.30-1-686] linux-image-2.6.30-1-686: System lockup 
(kernel freeze, soft lockup) on dual (multi) processor since 2.6.30
Set Bug forwarded-to-address to 
'http://bugzilla.kernel.org/show_bug.cgi?id=13933'.
>
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

Bug#507030: marked as done ([linux-image-2.6.26-1-686] iwl3945 does not follow channel changes)

[Debian Bug Tracking System]

Your message dated Fri, 21 Aug 2009 18:50:34 +0200
with message-id <20090821165034.ge15...@inutil.org>
and subject line Re: [linux-image-2.6.26-1-686] iwl3945 does not follow channel 
changes
has caused the Debian Bug report #507030,
regarding [linux-image-2.6.26-1-686] iwl3945 does not follow channel changes
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.)


-- 
507030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-1-686
Version: 2.6.26-8
Severity: normal

--- Please enter the report below this line. ---

On a Thinkpad t60 with intel's 3945ABG connection is lost when the 
channel is changed on the wifi access point. Ifdown/ifup in itself does 
not help, the iwl3945 module must be removed and inserted.

Relevant line from lspci:

03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG 
[Golan] Network Connection (rev 02)

# lsmod | grep iwl
iwl394578772  0
firmware_class  6816  2 pcmcia,iwl3945
mac80211  139680  1 iwl3945
cfg80211   21576  2 iwl3945,mac80211
led_class   3908  2 thinkpad_acpi,iwl3945

# lsmod | grep thinkpad
thinkpad_acpi  49632  0
led_class   3908  2 thinkpad_acpi,iwl3945
nvram   7116  1 thinkpad_acpi

This is with firmware-iwlfifi 0.13.

--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.26-1-686

Debian Release: lenny/sid
  900 testing www.debian-multimedia.org 
  900 testing security.debian.org 
  900 testing ftp.hu.debian.org 
   50 unstableftp.hu.debian.org 

--- Package information. ---
Depends (Version) | Installed
=-+-=
module-init-tools | 3.4-1
initramfs-tools(>= 0.55)  | 0.92j
 OR yaird(>= 0.0.13)  | 
 OR linux-initramfs-tool  | 



--- End Message ---
--- Begin Message ---
On Sat, Mar 28, 2009 at 11:36:12AM +0100, maximilian attems wrote:
> can you reproduce that on a more recent linux image like 2.6.29?

No further feedback, closing the bug. Please reopen if the problem
persists.

Cheers,
Moritz

--- End Message ---

Bug#500797: marked as done (linux-image-2.6.25-2-686: fails to initialize(?) USB phone)

[Debian Bug Tracking System]

Your message dated Fri, 21 Aug 2009 18:48:44 +0200
with message-id <20090821164844.ga15...@inutil.org>
and subject line Re: linux-image-2.6.25-2-686: fails to initialize(?) USB phone
has caused the Debian Bug report #500797,
regarding linux-image-2.6.25-2-686: fails to initialize(?) USB phone
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.)


-- 
500797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.25-2-686
Version: 2.6.25-7
Severity: normal


This (and earlier) version seem to fail to initialize windows mobile
phones:
[21122.825772] usb 5-6.3.3: new full speed USB device using ehci_hcd and
address 9
[21122.897761] usb 5-6.3.3: device descriptor read/64, error -71
[21123.073789] usb 5-6.3.3: device descriptor read/64, error -71
[21123.249820] usb 5-6.3.3: new full speed USB device using ehci_hcd and
address 10
[21123.321817] usb 5-6.3.3: device descriptor read/64, error -71
[21123.497834] usb 5-6.3.3: device descriptor read/64, error -71
[21123.673826] usb 5-6.3.3: new full speed USB device using ehci_hcd and
address 11
[21124.081643] usb 5-6.3.3: device not accepting address 11, error -32
[21124.153895] usb 5-6.3.3: new full speed USB device using ehci_hcd and
address 12
[21124.561643] usb 5-6.3.3: device not accepting address 12, error -32
[21124.561872] hub 5-6.3:1.0: unable to enumerate USB device on port 3

I tried it with a Samsung i900 as well as a HTC E650.
Occasionally (1 in hundred) it works. Removing and re-inserting a couple
of times or rebooting or whatever doesn't help.

-- Package-specific info:
** Version:
Linux version 2.6.25-2-686 (Debian 2.6.25-7) (m...@debian.org) (gcc version 
4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Fri Jul 18 17:46:56 UTC 
2008

** Command line:
root=/dev/mapper/DebianFVHBps-LVROOT ro 

** Tainted: P (1)

** Kernel log:
[17133.092926] rtc: lost 1 interrupts
[17133.216369] rtc: lost 1 interrupts
[17154.307424] rtc: lost 1 interrupts
[17154.348108] rtc: lost 1 interrupts
[17182.239363] rtc: lost 1 interrupts
[17182.365761] rtc: lost 1 interrupts
[17182.379463] rtc: lost 1 interrupts
[17184.419470] rtc: lost 1 interrupts
[17184.437567] rtc: lost 1 interrupts
[17290.413463] rtc: lost 1 interrupts
[17290.437065] rtc: lost 1 interrupts
[17316.246870] rtc: lost 1 interrupts
[17376.683218] rtc: lost 1 interrupts
[17392.948474] rtc: lost 1 interrupts
[17406.737062] rtc: lost 1 interrupts
[17406.965286] rtc: lost 1 interrupts
[17635.011562] rtc: lost 1 interrupts
[17643.932364] rtc: lost 1 interrupts
[17643.992329] rtc: lost 1 interrupts
[17700.666539] rtc: lost 1 interrupts
[17830.605979] rtc: lost 1 interrupts
[17893.299842] rtc: lost 1 interrupts
[17893.319921] rtc: lost 1 interrupts
[17898.545863] rtc: lost 1 interrupts
[17898.556020] rtc: lost 2 interrupts
[17898.564018] rtc: lost 1 interrupts
[17898.572022] rtc: lost 2 interrupts
[17898.584015] rtc: lost 2 interrupts
[17898.592015] rtc: lost 1 interrupts
[17898.598989] rtc: lost 2 interrupts
[17898.607182] rtc: lost 2 interrupts
[17898.626535] rtc: lost 1 interrupts
[18035.660569] printk: 18 messages suppressed.
[18035.660569] rtc: lost 1 interrupts
[18152.508755] rtc: lost 1 interrupts
[18271.394772] rtc: lost 1 interrupts
[18301.484945] rtc: lost 1 interrupts
[18301.516989] rtc: lost 1 interrupts
[18301.525168] rtc: lost 1 interrupts
[18301.541130] rtc: lost 2 interrupts
[18301.573023] rtc: lost 1 interrupts
[18366.843938] rtc: lost 1 interrupts
[18583.793271] rtc: lost 1 interrupts
[18598.345876] rtc: lost 1 interrupts
[18599.230250] rtc: lost 1 interrupts
[19159.729849] rtc: lost 1 interrupts
[19303.019793] rtc: lost 1 interrupts
[19572.26] rtc: lost 1 interrupts
[19595.560995] rtc: lost 1 interrupts
[19595.580844] rtc: lost 1 interrupts
[19596.528877] rtc: lost 1 interrupts
[19596.568842] rtc: lost 1 interrupts
[19596.632545] rtc: lost 1 interrupts
[19596.650918] rtc: lost 1 interrupts
[19596.661187] rtc: lost 1 interrupts
[19596.769269] rtc: lost 2 interrupts
[19596.776752] rtc: lost 1 interrupts
[19596.896871] rtc: lost 1 interrupts
[19603.290548] printk: 2 messages suppressed.
[19603.290548] rtc: lost 1 interrupts
[20432.811682] printk: 1 messages suppressed.
[20432.811719] rtc: lost 1 interrupts
[20528.947086] rtc: lost 1 interrupts
[20540.515623] rtc: lost 1 interrupts
[20540.527502] rtc: lost 1 interrupts
[20540.531008] rtc: lost 1 interrupts
[20716.280111] rtc: lost 1 interrupts
[20716.316358] rtc: lost 1 interrupts
[20716.342835] rtc: lost 1 interrupts
[20716.590188] rtc: lost 1 interrupts
[2072

Processed: Re: Please enable CONFIG_MMC_UNSAFE_RESUME

[Debian Bug Tracking System]

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

> severity 504391 wishlist
Bug #504391 [linux-image-2.6.26-1-686] Please enable CONFIG_MMC_UNSAFE_RESUME
Severity set to 'wishlist' from 'normal'

> tags 504391 wontfix
Bug #504391 [linux-image-2.6.26-1-686] Please enable CONFIG_MMC_UNSAFE_RESUME
Added tag(s) wontfix.
> 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: bug 451045 is forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=14033

[Debian Bug Tracking System]

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

> forwarded 451045 http://bugzilla.kernel.org/show_bug.cgi?id=14033
Bug #451045 [linux-2.6] linux-image-2.6.22-3-amd64: snd-hda-intel: Speakers do 
not turn off when headphones plugged into front headphone jack
Set Bug forwarded-to-address to 
'http://bugzilla.kernel.org/show_bug.cgi?id=14033'.
>
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

Bug#520891: general: Data coruption on my /dev/sda - /dev/sdd sata_siil siil 3114 chip

[wylda]

Hi,

based on my deep testing during chasing other kernel bug 
(http://bugzilla.kernel.org/show_bug.cgi?id=13933),
i can tell, that i had no such problem at all with sata_sil. Tested
several days + checksuming.

I had no sata_sil problem with following kernels:

* 2.6.26.8
* 2.6.27.29
* 2.6.28.10
* 2.6.29.6
* 2.6.30.4
* 2.6.30.5
* 2.6.31-rc6


Regads,
Pavel Vilim





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

Processed: fixed 509199 in 2.6.26-18

[Debian Bug Tracking System]

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

> fixed 509199 2.6.26-18
Bug #509199 {Done: Moritz Muehlenhoff } [linux-2.6] 
installation-reports: Intel 82574L network card isn't supported by installation 
kernel (i486) nor i686 kernel
There is no source info for the package 'linux-2.6' at version '2.6.26-18' with 
architecture ''
Unable to make a source version for version '2.6.26-18'
Bug Marked as fixed in versions 2.6.26-18.
>
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

Bug#503292: [RFC] Bugs#503292: linux-latest-2.6: new dummy images for Samsung s3c24xx devices

[Otavio Salvador]

Hello Luca,

On Mon, Aug 17, 2009 at 1:43 PM, Luca Capello wrote:
> Is there any strong opposition to "s3c24xx"?
>

I fully agree that it looks the most logical name for it.

-- 
Otavio Salvador  O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br



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

Processed: reassign 534867 to wnpp, retitle 534867 to RFH: nvidia-graphics-drivers-legacy-96xx

[Debian Bug Tracking System]

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

> reassign 534867 wnpp
Bug #534867 [linux-headers-2.6.30-1-686] [linux-headers-2.6.30-1-686] Missed 
headers
Bug reassigned from package 'linux-headers-2.6.30-1-686' to 'wnpp'.
Bug No longer marked as found in versions linux-2.6/2.6.30-1.
> retitle 534867 RFH: nvidia-graphics-drivers-legacy-96xx
Bug #534867 [wnpp] [linux-headers-2.6.30-1-686] Missed headers
Changed Bug title to 'RFH: nvidia-graphics-drivers-legacy-96xx' from 
'[linux-headers-2.6.30-1-686] Missed headers'
>
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

Bug#534867: [linux-headers-2.6.30-1-686] Missed headers

[Julian Gilbey]

On Fri, Aug 21, 2009 at 09:42:05AM +0200, Bastian Blank wrote:
> severity 534867 wishlist
> tags 534867 wontfix
> thanks
> 
> On Fri, Aug 21, 2009 at 01:52:35AM +0100, Julian Gilbey wrote:
> > > I've reopened this bug because I've just been stung by it myself.  The
> > > issue seems to be not so much that the package I'm trying to build
> > > (nvidia graphics module, see http://bugs.debian.org/510961) is using
> > > references to linux/* rather than asm/*, but rather that it doesn't
> > > know about the linux-headers-*-common directory.
> 
> It doesn't need to. However it _must_ use Kbuild to get the correct
> include paths.

Please see http://bugs.debian.org/540838

nvidia uses Kbuild, but for some reason fails miserably.  I really
don't understand why or what's actually going on; it builds fine in a
complete source tree, apparently, and it builds fine if symlinks are
included.

   Julian



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

Bug#542769: cman: qdiskd fails to run when using device option. Already fixed in the source

[Mike Cardwell]

Package: cman
Version: 2.20081102-1
Severity: important


r...@haven:~# mkqdisk -c /dev/sdb1 -l qdisk
mkqdisk v2.03.09

Writing new quorum disk label 'qdisk' to /dev/sdb1.
WARNING: About to destroy all data on /dev/sdb1; proceed [N/y] ? y
Warning: Initializing previously initialized partition
Initializing status block for node 1...
Initializing status block for node 2...
Initializing status block for node 3...
Initializing status block for node 4...
Initializing status block for node 5...
Initializing status block for node 6...
Initializing status block for node 7...
Initializing status block for node 8...
Initializing status block for node 9...
Initializing status block for node 10...
Initializing status block for node 11...
Initializing status block for node 12...
Initializing status block for node 13...
Initializing status block for node 14...
Initializing status block for node 15...
Initializing status block for node 16...
r...@haven:~# qdiskd -fd
[15191] debug: Loading configuration information
[15191] debug: Heuristic: 'ping iscsi-target -c1 -t2' score=1 interval=2 tko=3
[15191] debug: 1 heuristics loaded
[15191] debug: Quorum Daemon: 1 heuristics, 1 interval, 10 tko, 1 votes
[15191] debug: Run Flags: 0034
[15191] crit: Specified device /dev/sdb1 does match kernel's reported sector 
size (0 != -1)
r...@haven:~#

This is an old bug which was fixed here:
https://bugzilla.redhat.com/show_bug.cgi?id=470553

The patch is here:
http://sourceware.org/ml/cluster-cvs/2008-q4/msg00260.html

-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages cman depends on:
ii  debconf [debconf-2. 1.5.24   Debian configuration management sy
ii  libc6   2.7-18   GNU C Library: Shared libraries
ii  libcman22.20081102-1 Red Hat cluster suite - cluster ma
ii  libdlm2 2.20081102-1 Red Hat cluster suite - distribute
ii  libnet-snmp-perl5.2.0-1  Script SNMP connections
ii  libnet-telnet-perl  3.03-3   Script telnetable connections
ii  libnss3-1d  3.12.0-6 Network Security Service libraries
ii  libopenais2 0.83-1   Standards-based cluster framework 
ii  libvirt00.4.6-10 library for interfacing with diffe
ii  libxml2 2.6.32.dfsg-5+lenny1 GNOME XML library
ii  openais 0.83-1   Standards-based cluster framework 
ii  python  2.5.2-3  An interactive high-level object-o
ii  python-pexpect  2.1-1Python module for automating inter
ii  sg3-utils   1.24-2   Utilities for working with generic

cman recommends no packages.

cman suggests no packages.

-- debconf-show failed



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

Re: Bug#542470: closed by maximilian attems (Re: Bug#542470: linux-image-2.6.30-1-686: IPv6 can not be disabled)

[Bjørn Mork]

advocatux  writes:

> Yep, I know I can add "ipv6.disable=1" in /boot/grub/menu.lst but this
> method doesn't work always, it depends on which 2.6.30 kernel version
> you're running.

It works with the 2.6.30 kernel in Debian.  I'm no DD but I believe that
is about as much as you can expect Debian to support...

>>> Yeah, just like having IPv4 enabled by default.  Given the number of
>>> attacks, I would say that IPv4 is much more dangerous and should be
>>> disabled immediately by any sane administrator :-)
>>
>> triple *lol* ;)
>
> Certainly that mockery doesn't fit with Debian community spirit, does
> it? and for sure doesn't help to fill bug reports.

I put the smiley there for a reason.  I apologize if my comment hurt you
in any way.

I'm sure the kernel team found your bug report very useful even if it
was closed.  It does help documenting the potential problems users may
face, and will serve as help to others having the same question as you.

> People analizing this bug in Ubuntu Bug System
> (https://bugs.launchpad.net/bugs/351656) changed the status from
> security vulnerability "no" to "yes", and that's because an initial
> machine running other kernel, with IPv4 traffic filtered and IPv6
> disabled, after install a 2.6.30 kernel ends with unfiltered ports
> listening to IPv6 traffic.

Well, AFAIK there is no change to a default Debian installation. IPv6 is
enabled by default both in 2.6.26 and 2.6.30 and there are no iptables
or ip6tables rules installed.

Something could of course have checked on upgrade whether the admin
chose to blacklist the ipv6 module and warn that this has no effect
anymore, but personally I don't see the need.  If you do, I'm pretty
sure that patches are welcome as usual.

For the record: Unfiltered ports are not a security problem.  Network
protocol support is not a security problem.  Debian is as secure with
IPv6 enabled as it is with IPv4 enabled.  If you think otherwise, then I
suggest you demonstrate the attack and file appropriate bugs against the
packages with the real security problem.  Security in Linux is not based
on the kernel preventing application abuse by disabling any useful
feature.



Bjørn


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

Bug#534867: [linux-headers-2.6.30-1-686] Missed headers

[Bastian Blank]

severity 534867 wishlist
tags 534867 wontfix
thanks

On Fri, Aug 21, 2009 at 01:52:35AM +0100, Julian Gilbey wrote:
> > I've reopened this bug because I've just been stung by it myself.  The
> > issue seems to be not so much that the package I'm trying to build
> > (nvidia graphics module, see http://bugs.debian.org/510961) is using
> > references to linux/* rather than asm/*, but rather that it doesn't
> > know about the linux-headers-*-common directory.

It doesn't need to. However it _must_ use Kbuild to get the correct
include paths.

Bastian

-- 
Love sometimes expresses itself in sacrifice.
-- Kirk, "Metamorphosis", stardate 3220.3



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

Processed: Re: Bug#534867: [linux-headers-2.6.30-1-686] Missed headers

[Debian Bug Tracking System]

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

> severity 534867 wishlist
Bug #534867 [linux-headers-2.6.30-1-686] [linux-headers-2.6.30-1-686] Missed 
headers
Severity set to 'wishlist' from 'serious'

> tags 534867 wontfix
Bug #534867 [linux-headers-2.6.30-1-686] [linux-headers-2.6.30-1-686] Missed 
headers
Added tag(s) wontfix.
> 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: Re: Bug#542250: repeatable crashes while copying 500G from NFS mount to local logical volume

[Debian Bug Tracking System]

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

> tags 542250 +patch
Bug #542250 [src:linux-2.6] repeatable crashes while copying 500G from NFS 
mount to local logical volume
Bug #516479 [src:linux-2.6] linux-image-2.6.26-1-xen-amd64: kernel-panic in 
xen_spin_wait an mutlicore dom0 with high load, not interruption save?
Ignoring request to alter tags of bug #542250 to the same tags previously set
Ignoring request to alter tags of bug #516479 to the same tags previously set
> 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