Bug#1029816: wifi: mt76: mt7612u/mt7610u - 6.1.x hard locking systems

[Stuart Read]

Source: linux
Version: 6.1.4-1
Severity: important

Dear Maintainer,

My Netgear A6210 (Mediatek MT7612U) hard locks the system on login. If I 
instead log in via console,
the first network access (such as ping) results in a kernel panic.

I found this upstream bug report: 
http://lists.infradead.org/pipermail/linux-mediatek/2022-December/054010.html

However it is unclear to me if or when the fix will be applied to the kernel.

Best,
Stuart

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1024718: Fwd: Bug#1024718: linux: Samsung PM9B1 NVMe fails changes NID when resuming from sleep

[Stuart]

-- Forwarded message -
From: Stuart 
Date: Fri, Dec 23, 2022 at 1:53 PM
Subject: Re: Bug#1024718: linux: Samsung PM9B1 NVMe fails changes NID when
resuming from sleep
To: Salvatore Bonaccorso 


Well it seems as of this message, it won't be accepted upstream due to
their policy on not accepting quirks for issues fixed in firmware
https://lore.kernel.org/all/20221221083102.ga23...@lst.de/

On Wed, Nov 23, 2022 at 7:55 PM Salvatore Bonaccorso 
wrote:

> Hi Stuart,
>
> Thanks for the report!
>
> On Wed, Nov 23, 2022 at 06:31:48PM +, Stuart Hayhurst wrote:
> > Source: linux
> > Version: 5.19.6-1
> > Severity: important
> > Tags: patch upstream
> > X-Debbugs-Cc: stuart.a.hayhu...@gmail.com
> >
> > Dear Maintainer,
> >
> > The Samsung PM9B1 misreports its NID when resuming from sleep,
> > causing the root filesystem to be unmounted, and the system left in
> > an unstable state. Mostly this results in the device crashing, but
> > if the device somehow continues running, it's incredibly unstable,
> > where basically nothing works. It's an OEM drive found in some newer
> > laptops (like my Lenovo Yoga 7 Gen 7)
> > There's a bug report and patch upstream for this, but personally I
> > think it might be a good idea to include it in Debian until it's
> > accepted, as machines with this drive are near-unusable.
> > Upstream issue:
> https://lore.kernel.org/all/20221116171727.4083-1-...@augustwikerfors.se/
> > I've tested the patch against the current Debian 6.1-rc5 kernel on
> > my laptop, and this fixes the problem without any other issues.
>
> On the other hand, we only should include it once we are fairly
> confident that upstream accepts the fix and will include.
>
> Can you ping this bug once upstream maintainers have acked the change
> and queued it?
>
> If you have tested the patch, then you can as well reply to the thread
> mentioning you sucessfully tested the patch adding a Tested-by tag.
>
> Regards,
> Salvatore
>

Bug#1024718: linux: Samsung PM9B1 NVMe fails changes NID when resuming from sleep

[Stuart Hayhurst]

Source: linux
Version: 5.19.6-1
Severity: important
Tags: patch upstream
X-Debbugs-Cc: stuart.a.hayhu...@gmail.com

Dear Maintainer,

The Samsung PM9B1 misreports its NID when resuming from sleep, causing the root 
filesystem to be unmounted, and the system left in an unstable state. Mostly 
this results in the device crashing, but if the device somehow continues 
running, it's incredibly unstable, where basically nothing works. It's an OEM 
drive found in some newer laptops (like my Lenovo Yoga 7 Gen 7)
There's a bug report and patch upstream for this, but personally I think it 
might be a good idea to include it in Debian until it's accepted, as machines 
with this drive are near-unusable.
Upstream issue: 
https://lore.kernel.org/all/20221116171727.4083-1-...@augustwikerfors.se/
I've tested the patch against the current Debian 6.1-rc5 kernel on my laptop, 
and this fixes the problem without any other issues.

Thanks :)

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#987083: iwlmvm: sometimes doesn't initialise on boot, requires a reboot

[Russell Stuart]

Package: src:linux
Version: 5.10.28-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

As of the upgrade 10 linux-image-5.10.0-6-amd64 the Intel AX200 WiFi
(0x8086 0x2723) doesn't work.  Network Manager doesn't find any Wireless
Networks.

rmmod'ing iwlmvm, iwlwifi, cfg80211, mac80211 and then modprob'ing
iwlmvm does not fix the problem.  I have to reboot.  This normally
happens on boot up, but has happened once when I changed to a
different SSID.


- -- Package-specific info:
** Version:
Linux version 5.10.0-6-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.28-1 (2021-04-09)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-6-amd64 
root=UUID=f58461ea-cd6d-434d-abf4-81ff52141b6b ro quiet

** Not tainted

** Kernel log:
[6.362591] NET: Registered protocol family 38
[6.375402] Bluetooth: RFCOMM TTY layer initialized
[6.375406] Bluetooth: RFCOMM socket layer initialized
[6.375409] Bluetooth: RFCOMM ver 1.11
[6.886692] rfkill: input handler disabled
[   10.226501] wlp82s0: authenticate with 9e:92:1f:4c:0b:b8
[   10.234700] wlp82s0: send auth to 9e:92:1f:4c:0b:b8 (try 1/3)
[   10.397715] wlp82s0: authenticated
[   10.401110] wlp82s0: associate with 9e:92:1f:4c:0b:b8 (try 1/3)
[   10.414197] wlp82s0: RX AssocResp from 9e:92:1f:4c:0b:b8 (capab=0x1431 
status=0 aid=1)
[   10.434958] wlp82s0: associated
[   10.566237] IPv6: ADDRCONF(NETDEV_CHANGE): wlp82s0: link becomes ready
[   11.036243] bridge: filtering via arp/ip/ip6tables is no longer available by 
default. Update your scripts to load br_netfilter if you need this.
[   11.301638] kauditd_printk_skb: 24 callbacks suppressed
[   11.301641] audit: type=1400 audit(1618641084.841:35): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="/usr/bin/lxc-start" pid=1520 comm="apparmor_parser"
[   11.353157] audit: type=1400 audit(1618641084.893:36): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="lxc-container-default" pid=1524 
comm="apparmor_parser"
[   11.353164] audit: type=1400 audit(1618641084.893:37): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="lxc-container-default-cgns" pid=1524 
comm="apparmor_parser"
[   11.353168] audit: type=1400 audit(1618641084.893:38): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="lxc-container-default-with-mounting" pid=1524 
comm="apparmor_parser"
[   11.353171] audit: type=1400 audit(1618641084.893:39): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="lxc-container-default-with-nesting" pid=1524 
comm="apparmor_parser"
[   18.283646] nouveau :01:00.0: fb: VPR locked, but no scrubber binary!
[   18.613288] rfkill: input handler enabled
[   20.405397] rfkill: input handler disabled
[  514.369698] usb 2-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[  514.391132] usb 2-2: New USB device found, idVendor=152d, idProduct=0578, 
bcdDevice= 2.09
[  514.391139] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  514.391143] usb 2-2: Product: USB to ATA/ATAPI Bridge
[  514.391146] usb 2-2: Manufacturer: JMicron
[  514.391148] usb 2-2: SerialNumber: 0123456789ABCDEF
[  514.421422] SCSI subsystem initialized
[  514.424884] usbcore: registered new interface driver usb-storage
[  514.428996] scsi host0: uas
[  514.429067] usbcore: registered new interface driver uas
[  514.429478] scsi 0:0:0:0: Direct-Access JMicron  Generic  0209 
PQ: 0 ANSI: 6
[  514.438420] scsi 0:0:0:0: Attached scsi generic sg0 type 0
[  516.823958] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 
GiB)
[  516.823965] sd 0:0:0:0: [sda] 4096-byte physical blocks
[  516.824148] sd 0:0:0:0: [sda] Write Protect is off
[  516.824152] sd 0:0:0:0: [sda] Mode Sense: 53 00 00 08
[  516.824547] sd 0:0:0:0: [sda] Disabling FUA
[  516.824551] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[  516.824889] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a 
multiple of physical block size (4096 bytes)
[  516.851569]  sda: sda1
[  516.853924] sd 0:0:0:0: [sda] Attached SCSI disk
[  755.948101] usb 2-2: USB disconnect, device number 2
[  755.949812] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  756.187902] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 1051.709005] nouveau :01:00.0: fb: VPR locked, but no scrubber binary!
[ 1476.739325] nouveau :01:00.0: fb: VPR locked, but no scrubber binary!
[ 1862.143451] nouveau :01:00.0: fb: VPR locked, but no scrubber binary!
[ 2783.993471] nouveau :01:00.0: fb: VPR locked, but no scrubber 

Bug#927078: linux-image-4.19.0-4-amd64: B43 wireless forced into non-working PIO mode with latest kernel

[Stuart Read]

Package: src:linux
Version: 4.19.28-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Upgraded to latest set of package in Testing. After this my B43 wireless card
failed to connect. The driver reported a warning:

b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be 
needed and will result in lower performance.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Booting with kernel parameter "intel-iommu=off" solved the problem.


-- Package-specific info:
** Version:
Linux version 4.19.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15)

** Command line:
BOOT_IMAGE=/root/boot/vmlinuz-4.19.0-4-amd64 
root=UUID=9febe37f-1974-414a-97cd-5e3249c39291 ro rootflags=subvol=root quiet

** Not tainted

** Kernel log:

** Model information
[6.711836] b43 ssb0:0: firmware: direct-loading firmware b43/ucode16_mimo.fw
[6.715796] b43 ssb0:0: firmware: direct-loading firmware b43/n0initvals16.fw
[6.717533] b43 ssb0:0: firmware: direct-loading firmware 
b43/n0bsinitvals16.fw
[6.742872] Bluetooth: hci0: BCM: chip id 254 build 0522
[6.745796] Bluetooth: hci0: BCM: product 05ac:8213
[6.778263] Bluetooth: hci0: BCM: features 0x00
[6.795868] Bluetooth: hci0: isbjorn
[6.824440] applesmc: key=271 fan=1 temp=14 index=14 acc=1 lux=2 kbd=1
[6.831783] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[6.858783] ACPI Warning: \_SB.PCI0.IXVE.IGPU._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20180810/nsarguments-66)
[6.858810] ACPI: \_SB_.PCI0.IXVE.IGPU: failed to evaluate _DSM
[6.858950] nouveau :02:00.0: enabling device (0002 -> 0003)
[6.859211] PCI Interrupt Link [LGPU] enabled at IRQ 20
[6.859396] checking generic (c001 64) vs hw (c000 1000)
[6.859397] fb: switching to nouveaufb from EFI VGA
[6.859453] Console: switching to colour dummy device 80x25
[6.871615] Adding 14679836k swap on /dev/sda4.  Priority:-2 extents:1 
across:14679836k SSFS
[6.878926] nouveau :02:00.0: NVIDIA MCP79/MCP7A (0ac180b1)
[6.907803] pstore: Registered efi as persistent store backend
[6.947520] nouveau :02:00.0: bios: version 62.79.40.00.01
[6.950279] input: applesmc as /devices/platform/applesmc.768/input/input9
[6.968848] applesmc applesmc.768: hwmon_device_register() is deprecated. 
Please convert the driver to use hwmon_device_register_with_info().
[6.979148] nouveau :02:00.0: fb: 256 MiB stolen system memory
[7.016102] snd_hda_codec_realtek hdaudioC0D0: ALC889A: SKU not ready 
0x40f0
[7.102992] audit: type=1400 audit(1555273331.408:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-oopslash" 
pid=449 comm="apparmor_parser"
[7.104451] [TTM] Zone  kernel: Available graphics memory: 3954374 kiB
[7.104453] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[7.104454] [TTM] Initializing pool allocator
[7.104460] [TTM] Initializing DMA pool allocator
[7.104489] nouveau :02:00.0: DRM: VRAM: 256 MiB
[7.104491] nouveau :02:00.0: DRM: GART: 1048576 MiB
[7.104496] nouveau :02:00.0: DRM: TMDS table version 2.0
[7.104499] nouveau :02:00.0: DRM: DCB version 4.0
[7.104502] nouveau :02:00.0: DRM: DCB outp 00: 01000123 00010014
[7.104505] nouveau :02:00.0: DRM: DCB outp 01: 02021232 0010
[7.104508] nouveau :02:00.0: DRM: DCB outp 02: 02021286 0f220010
[7.104510] nouveau :02:00.0: DRM: DCB conn 00: 0040
[7.104512] nouveau :02:00.0: DRM: DCB conn 01: a146
[7.106141] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[7.106142] [drm] Driver supports precise vblank timestamp query.
[7.108267] audit: type=1400 audit(1555273331.416:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=451 comm="apparmor_parser"
[7.109585] nouveau :02:00.0: DRM: MM: using M2MF for buffer copies
[7.115991] audit: type=1400 audit(1555273331.424:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=448 
comm="apparmor_parser"
[7.115997] audit: type=1400 audit(1555273331.424:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=448 
comm="apparmor_parser"
[7.115999] audit: type=1400 audit(1555273331.424:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=448 
comm="apparmor_parser"
[7.123196] audit: type=1400 audit(1555273331.432:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=454 comm="apparmor_parser"
[7.139098] audit: type=1400 audit(1555273331.448:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-soffice" 
pid=453 comm="apparmor_par

Bug#898021: linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail

[Stuart Young]

My workarounds for this at the moment are to install tools that increase
the kernel entropy pool.

If not a virtual machine, and `grep -i -o -m 1 rdrand /proc/cpuinfo`
returns 'rdrand', then I install the 'rng-tools5' package which uses the
hardware rng in many cpu's to provide entropy to the kernel.

If that fails or if it's a virtual machine, then I install the 'haveged'
package.

Note: Neither of these are fixes. They're work-arounds for the current
issue that allow somewhat normal operation. eg; Some people have issues
around how random the hardware rng is in some machines.

PS: Have seen a number of people suffering this issue in #debian on
freenode, and also on #debian & #debian-next on oftc.


On 10 May 2018 at 15:43,  wrote:

>
>
> I can reproduce the described delay behavior on a virtualized installation
> of testing using kvm after installing kernel 4.16.0-1-amd64. With
> 4.15.0-3-amd64 no problem.
>
> Chris
>
>
>


-- 
Stuart Young (aka Cefiar)

Bug#898021: linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail

[Stuart Young]

I'm seeing this on a few laptops with SSD's.

The behaviour is that if the device isn't interacted with in any way, the
machines hang for 2-4 mins at boot.

Seems to be related to the fix for CVE-2018-1108 - random: fix crng_ready()
test

https://security-tracker.debian.org/tracker/CVE-2018-1108

Pedro & Sten, can you try introducing entropy into the systems affected
when they appear to hang, to see if this reduces the delays?

eg: moving the mouse, tapping shift/ctrl/alt keys, pinging the device on
the network if network is already up, etc?

I suspect this bug can be merged with 897599, 897632 and 897917.

-- 
Stuart Young (aka Cefiar)

Bug#865984: linux-image-4.9.0-3-amd64: hairpin NAT doesn't work across bridges

[Russell Stuart]

On Mon, 2017-06-26 at 16:57 +0100, Ben Hutchings wrote:
> Control: tag -1 upstream wontfix

I'll file it upstream.  I'm never quite sure whether the maintainer is
supposed to do that or the bug submitter - it seems to vary by package.

Should I link the bug report here?

> You should put the WAN and LAN traffic on separate VLANs and set the
> router's switch port to trunked mode.

If the switch's port had a trunked mode that would be a good idea.  The
5 port switches we put in these "occasionally manned" offices don't
have them.

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

Bug#865984: linux-image-4.9.0-3-amd64: hairpin NAT doesn't work across bridges

[Russell Stuart]

Package: src:linux
Version: 4.9.30-2+deb9u1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Configuration:
  A box running 4.9.0-3-amd64 is acting as a NAT'ing router.  It has
  a single Ethernet NIC and a wireless NIC servicing the local LAN.
  These devices are bridged.  Since it has only one wired NIC it is
  used to connect to both the LAN and internet via a switch.  This
  means it must do hairpin NAT over the wired NIC.

  internet <--> modem<--> switch <--> LAN
[10.99.99.97/30] ^[10.91.91.0/24]
 |^
  +--+   ||
  |  [10.91.91.1/24] eth0=<--/  v antenna LAN |
  |  [10.99.99.98/30] br0<---+   |  | [10.91.91.0/24] |
  | wlan0=<-/ v
  |  |+---=--+
  | ip r a default via 10.99.99.97   || eth-lan0 |
  | iptables -t nat -A POSTROUTING \ || 10.91.91.129/24  |
  |   -s 10.91.91.0/24 -j MASQUERADE ||  |
  +--+| ip r a default \ |
  |  via 10.91.91.1  |
  +--+

  While wlan0 is the reason for bridge exists in my case it doesn't
  have to be a wireless connection.  Connecting any two Ethernet
  devices to the bridge (so it has to do some work) triggers the
  problem.

Problem:
  10.91.91.129 can not receive packets from the internet.  A packet
  arriving from the internet hits eth0, then br0, then is mangled by
  iptables nat, and then is supposed to be sent out br0, eth0 again.
  The mangled version never makes it out of eth0.
  
Possible cause:
  The bridge is implementing it's "never send a packet out over the
  interface it arrived on rule" but it this case it's misapplied the
  rule: the packet that is to be sent is not the same packet that
  arrived earlier on eth0. It has different source and destination IP
  addresses and MAC addresses, and in any case is not being reflected -
  it hit the INPUT chain, not the FORWARD chain.

Workarounds:
  Set the "hairpin" flag on br0.  This works if are to be no loops in
  the LAN wiring (which will normally be hidden by STP).  If there
  are a packet storm will soon ensue, followed in my case by chaos
  and panic.

  An alternate workaround that mostly works is the use ebtables to
  make internet packets bypass the bridge:

ebtables -t broute -A BROUTING -d Multicast -j ACCEPT 
ebtables -t broute -A BROUTING -p IPv4 --ip-dst 10.0.0.0/8 -j ACCEPT 
ebtables -t broute -A BROUTING -p IPv4 --ip-dst 172.16.0.0/12 -j ACCEPT 
ebtables -t broute -A BROUTING -p IPv4 --ip-dst 169.254.0.0/16 -j ACCEPT 
ebtables -t broute -A BROUTING -p IPv4 --ip-dst 192.168.0.0/16 -j ACCEPT 
ebtables -t broute -A BROUTING -p IPv4 --ip-src 10.0.0.0/8 -j ACCEPT 
ebtables -t broute -A BROUTING -p IPv4 --ip-src 172.16.0.0/12 -j ACCEPT 
ebtables -t broute -A BROUTING -p IPv4 --ip-src 169.254.0.0/16 -j ACCEPT 
ebtables -t broute -A BROUTING -p IPv4 --ip-src 192.168.0.0/16 -j ACCEPT 
ebtables -t broute -A BROUTING -p IPv4 -j DROP 
ebtables -t broute -A BROUTING -p IPv6 --ip6-dst fc00::/fc00:: -j ACCEPT 
ebtables -t broute -A BROUTING -p IPv6 --ip6-src fc00::/fc00:: -j ACCEPT 
ebtables -t broute -A BROUTING -p IPv6 -j DROP 

  It only "mostly" works because it fails with OpenVPN.  OpenVPN gets
  TLS errors if the incoming packets don't go via the bridge.

Reproducing:
  Run the attached shell script under Debian on a kernel with the
  problem.  The shell script sets up the configuration shown in the
  diagram above using containers created by systemd-nspawn.

  Invoking it using "hairpin-bug.sh bridge" creates the conditions
  show in the diagram and produces the following output (spurious
  selinux warnings produced by systemd-nspawn have been omitted for
  clarity):

  PING 10.99.99.90 (10.99.99.90) 56(84) bytes of data.

  --- 10.99.99.90 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  The script doesn't need an internet to connection to work as it
  "emulates" it.   10.99.99.90 is the one and only address on this
  emulated internet.

  Invoking it using "hairpin-bug.sh direct" creates the conditions
  show in the diagram, with one exception: the eth0 device is not
  connected to the br0, and IP addresses assigned to br0 have been
  moved to eth0.  The output in that case is:

  PING 10.99.99.90 (10.99.99.90) 56(84) bytes of data.
  64 bytes from 10.99.99.90: icmp_seq=1 ttl=63 time=0.080 ms

  --- 10.99.99.90 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.080/0.080/0.080/0.000 ms

  This invocation method is mostly a unit test for the s

Bug#865120: release-notes: document i386/amd64 kernel changes for jessie->stretch

[Stuart Prescott]

Package: release-notes
Severity: important

With Stretch, amd64 flavour kernels are no longer supplied within the i386
Debian architecture (i.e. for a 64 bit kernel with a 32 bit userspace). The
release notes should document that these kernel packages are no longer
offered so that users don't accidentally run unsupported kernels indefinitely
(hence severity:important).

The upgrade path is to enable amd64 as a foreign architecture and then install
the relevant amd64 kernel image.

A 0th draft at some wording for §4.6/4.6.1:

Users of the i386 port are advised that the amd64 flavour of kernel
is no longer included within the i386 port but that these kernels
should instead be installed directly from the amd64 port using the
ability for apt and dpkg to install foreign architecture packages
(known as multiarch).

- check if running i386 userspace with amd64 kernel:
`dpkg --print-architure` is i386, and
`uname -r` ends in amd64

- add amd64 as foreign architecture
`dpkg --add-architecture amd64; apt-get update`

- (install the appropriate kernel metapackage as described already)

cheers
Stuart

Bug#859611: linux-image-4.9.0-0.bpo.2-amd64: ipsec gre tunnel not receiving packets

[Russell Stuart]

On Tue, 2017-04-18 at 21:06 +1000, Russell Stuart wrote:
> I'll try it again with 4.9.18.

4.9.18 behaves identically.

However I loaded it on another machine, and it worked.  In fact it
worked with both 4.9.13 and 4.9.18.  These machines have very different
hardware, and are running running very different networking
configurations - but both are from the same image so only configuration
files are different.  Another way of saying the same thing is all non-
conf files installed by debian are identical.

Unfortunately while the software may be the same and the ipsec
configuration is almost identical (only my endpoint differs) the rest
of the networking configuration is very different. One is a AMD A10,
talking  to the internet over a single NIC using ADSL (pppoe).  The one
that doesn't work is a Dell dual Xeon, with a direct connection to the
internet over two bridged 10G NIC's with 3 different gateways.  I get
about 1 hour to a day to experiment with the machine that doesn't work,
and I don't have a clue where to start looking.

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

Bug#859611: linux-image-4.9.0-0.bpo.2-amd64: ipsec gre tunnel not receiving packets

[Russell Stuart]

Sorry, I missed your reply.

On Fri, 2017-04-07 at 20:40 +0100, Ben Hutchings wrote:
> Does the affected system have a firewall?

Yes, it does.

>   If so, you might need to
> load nf_conntrack_proto_gre explicitly now (explained in
> ).
> Although it isn't obvious why only some of the GRE tunnels would be
> affected.

As it happens I load all nf_conntrack modules at boot so they are
available to containers.  I've just checked, nf_conntrack_proto_gre is
definitely loaded.

I'll try it again with 4.9.18.

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

Bug#859611: linux-image-4.9.0-0.bpo.2-amd64: ipsec gre tunnel not receiving packets

[Russell Stuart]

Package: src:linux
Version: 4.9.13-1~bpo8+1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

We have a IPSec tunnel.  It works under 3.16, and doesn't work under
4.9.13.  Under 4.9.13 racoon reports the isakmp setup is successfull.
Looking at it with tcdump (I've got captures, with xfrm keys) 
under 4.9.13 I see ESP packets going out, but none coming in.

   /etc/racoon/racon.conf:

  remote "optus-lube4g"
  {
exchange_mode   main;
lifetimetime 24 hours;
my_identifier   address 113.52.1.20;
nat_traversal   off;
ph1id   0;
proposal_check  obey;
remote_address  119.225.62.29;
proposal {
  encryption_algorithm  3des;
  hash_algorithmsha1;
  authentication_method pre_shared_key;
  dh_group  1;
  lifetime  time 1 hour;
}
  }

  sainfo address 113.52.1.20 47 address 119.225.62.29 47
  {
authentication_algorithmhmac_sha1, hmac_md5, hmac_sha256, 
non_auth;
compression_algorithm   deflate;
encryption_algorithm3des, des, des_iv64, des_iv32, 
blowfish, null_enc, twofish, rijndael, aes;
lifetimetime 24 hours;
pfs_group   1;
remoteid0;
  }

  sainfo address 119.225.62.29 47 address 113.52.1.20 47
  {
authentication_algorithmhmac_sha1, hmac_md5, hmac_sha256, 
non_auth;
compression_algorithm   deflate;
encryption_algorithm3des, des, des_iv64, des_iv32, 
blowfish, null_enc, twofish, rijndael, aes;
lifetimetime 24 hours;
pfs_group   1;
remoteid0;
  }

  /etc/ipsec-tools.conf:

# ipsec tunnel optus-lube3g.
spdadd -4 203.217.12.211 119.225.62.29 gre -P out ipsec
  esp/tunnel/203.217.12.211-119.225.62.29/require;

spdadd -4 119.225.62.29 203.217.12.211 gre -P in ipsec
  esp/tunnel/119.225.62.29-203.217.12.211/require;

# ipsec tunnel optus-lube4g.
spdadd -4 113.52.1.20 119.225.62.29 gre -P out ipsec
  esp/tunnel/113.52.1.20-119.225.62.29/require;

spdadd -4 119.225.62.29 113.52.1.20 gre -P in ipsec
  esp/tunnel/119.225.62.29-113.52.1.20/require;

  ip tunnel show:

gre0: gre/ip  remote any  local any  ttl inherit  nopmtudisc
optus-lube4g: gre/ip  remote 119.225.62.29  local 113.52.1.20  ttl inherit 
(Plus lots of other un-encrypted GRE tunnels, all of which were
working.)


- -- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Dell Inc.
product_name: PowerEdge R420
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: 1.2.4
board_vendor: Dell Inc.
board_name: 072XWF
board_version: A01

** Network interface configuration:


auto lo
iface lo inet loopback

allow-hotplug br-eth0
auto br-eth0
iface br-eth0 inet static
pre-up  ip link set up dev eth0 || true
pre-up  ! ip link show | egrep --silent '^[0-9]+: eth0: ' || ip 
addr show dev eth0 | sed -n 's/^ *inet6\? \+\([^ ]*\) .*/\1/p' | while read 
addr; do ([ x"${VERBOSITY}" != x"1" ] || set -x; ip addr del "$addr" dev eth0 
|| :); done
pre-up  ip link set up dev eth1 || true
pre-up  ! ip link show | egrep --silent '^[0-9]+: eth1: ' || ip 
addr show dev eth1 | sed -n 's/^ *inet6\? \+\([^ ]*\) .*/\1/p' | while read 
addr; do ([ x"${VERBOSITY}" != x"1" ] || set -x; ip addr del "$addr" dev eth1 
|| :); done
bridge_portseth0 eth1
bridge_stp  on
bridge_fd   2
bridge_maxwait  2
pre-downip link set nomaster dev eth1 || true
pre-downip link set nomaster dev eth0 || true
post-down   ip link set down dev eth1 || true
post-down   ip link set down dev eth0 || true
address 113.52.1.20/28
post-up ip addr add 113.52.1.21/28 dev br-eth0 || true
post-up ip addr add 10.201.0.2/24 dev br-eth0 || true
post-down   ! ip link show | egrep --silent '^[0-9]+: br-eth0: ' || 
ip addr show dev br-eth0 | sed -n 's/^ *inet6\? \+\([^ ]*\) .*/\1/p' | while 
read addr; do ([ x"${VERBOSITY}" != x"1" ] || set -x; ip addr del "$addr" dev 
br-eth0 || :); done
post-up ip route add default via 113.52.1.17 src 113.52.1.20 
metric 20 || true
post-up ip route add default via 113.52.1.17 src 113.52.1.21 
metric 21 || true
post-up ip route add 58.178.242.194/32 via 113.52.1.17 dev 
br-eth0 src 113.52.1.21 || true
post-up ip route add 211.27.154.166/32 via 113.52.1.17 dev 
br-eth0 src 113.52.1.21 || true
post-up

Bug#842762: firmware-linux-nonfree: Please add video drivers for Intel Kabylake

[Russell Stuart]

Package: firmware-linux-nonfree
Version: 20160824-1
Severity: normal

Without this firmware the i915 driver crashes in about 10 minutes
after an external monitor is plugged in to a
Dell Inc. Inspiron 13-7378, causing both the LCD screen and the
external monitor to go blank.  The work around is to unplug the
HDMI cable and reconnect every 10 minutes or so.

The current firmware can be found here:


https://01.org/sites/default/files/downloads/intelr-graphics-linux/kbldmcver101.tar.bz2

The latest versions are listed on Intels open source site here:

https://01.org/linuxgraphics/downloads/


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages firmware-linux-nonfree depends on:
ii  firmware-amd-graphics  20160824-1
ii  firmware-misc-nonfree  20160824-1

Versions of packages firmware-linux-nonfree recommends:
ii  amd64-microcode  3.20160316.2
ii  intel-microcode  3.20160714.1

firmware-linux-nonfree suggests no packages.

-- no debconf information

Bug#780029: linux-image-3.19.0-trunk-amd64: btrfs snapshot of ecryptfs mount over btrfs gives kernel NULL pointer dereference

[Stuart Pook]

Package: src:linux
Version: 3.19-1~exp1
Severity: normal

Dear Maintainer,

I have these mounts

/dev/sdd2 on /disks/stuart type btrfs 
(rw,nosuid,noatime,ssd,discard,space_cache)
/home/stuart on /home/stuart type ecryptfs 
(rw,nosuid,nodev,noatime,ecryptfs_sig=5eba6a5037081fa6,ecryptfs_fnek_sig=50433870c3b6902a,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_passthrough,user=stuart)

I then do:

btrfs subvolume snapshot -r /home/stuart 
/disks/snapshots/stuart/2015-03-08T13:38:23.088363+

And I get a "BUG" and my system is unusable:

2015-03-08T14:20:19.5+01:00 kooka kernel: BTRFS info (device dm-0): disk space 
caching is enabled
2015-03-08T14:21:26.0+01:00 kooka kernel: BUG: unable to handle kernel NULL 
pointer dereference at 01f0
2015-03-08T14:21:26.0+01:00 kooka kernel: IP: [] 
btrfs_ioctl_snap_create_transid+0xbf/0x1a0 [btrfs]
2015-03-08T14:21:26.0+01:00 kooka kernel: PGD 144fcf067 PUD 1f80d8067 PMD 0 
2015-03-08T14:21:26.0+01:00 kooka kernel: Oops:  [#1] SMP 
2015-03-08T14:21:26.0+01:00 kooka kernel: Modules linked in: ext4 crc16 mbcache 
jbd2 cbc dm_crypt xts gf128mul algif_skcipher af_alg ecb binfmt_misc 
cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_conservative 
iptable_filter ip_tables x_tables asix libphy iTCO_wdt iTCO_vendor_support 
coretemp kvm_intel kvm pcspkr serio_raw i2c_i801 ir_xmp_decoder ir_lirc_codec 
lirc_dev ir_mce_kbd_decoder ir_sharp_decoder ir_sanyo_decoder ir_sony_decoder 
ir_jvc_decoder lpc_ich mfd_core ir_rc6_decoder ir_rc5_decoder ir_nec_decoder 
cdc_subset cdc_ether usbnet ftdi_sio usbserial rc_rc6_mce snd_usb_audio 
snd_usbmidi_lib iguanair rc_core snd_rawmidi snd_seq_device usbsevseg evdev 
xhci_pci xhci_hcd snd_hda_codec_realtek snd_hda_codec_generic 
snd_hda_codec_hdmi radeon 8250_fintek snd_hda_intel ttm drm_kms_helper 
snd_hda_controller snd_hda_codec
2015-03-08T14:21:26.0+01:00 kooka kernel:  drm snd_hwdep snd_pcm_oss 
i2c_algo_bit snd_mixer_oss i2c_core snd_pcm button snd_timer acpi_cpufreq snd 
soundcore processor thermal_sys shpchp loop fuse ecryptfs parport_pc ppdev lp 
parport autofs4 crc32c_generic btrfs xor raid6_pq dm_mod sg sd_mod sr_mod cdrom 
ata_generic hid_generic usbhid hid ahci libahci pata_jmicron r8169 mii libata 
scsi_mod ehci_pci uhci_hcd ehci_hcd usbcore usb_common
2015-03-08T14:21:26.0+01:00 kooka kernel: CPU: 1 PID: 5267 Comm: btrfs Not 
tainted 3.19.0-trunk-amd64 #1 Debian 3.19-1~exp1
2015-03-08T14:21:26.0+01:00 kooka kernel: Hardware name: Gigabyte Technology 
Co., Ltd. P35-DS3R/P35-DS3R, BIOS F13 06/19/2009
2015-03-08T14:21:26.0+01:00 kooka kernel: task: 8800dab80a20 ti: 
8801db78 task.ti: 8801db78
2015-03-08T14:21:26.0+01:00 kooka kernel: RIP: 0010:[]  
[] btrfs_ioctl_snap_create_transid+0xbf/0x1a0 [btrfs]
2015-03-08T14:21:26.0+01:00 kooka kernel: RSP: 0018:8801db783cc8  EFLAGS: 
00010206
2015-03-08T14:21:26.0+01:00 kooka kernel: RAX:  RBX: 
88009bb57500 RCX: 0020
2015-03-08T14:21:26.0+01:00 kooka kernel: RDX: 880202e04c00 RSI: 
a02abc50 RDI: 0004
2015-03-08T14:21:26.0+01:00 kooka kernel: RBP: 880054f19038 R08: 
 R09: 0001
2015-03-08T14:21:26.0+01:00 kooka kernel: R10:  R11: 
 R12: 8801f4250100
2015-03-08T14:21:26.0+01:00 kooka kernel: R13:  R14: 
0001 R15: 8801f4250100
2015-03-08T14:21:26.0+01:00 kooka kernel: FS:  7fb16c3988c0() 
GS:88021fc8() knlGS:
2015-03-08T14:21:26.0+01:00 kooka kernel: CS:  0010 DS:  ES:  CR0: 
80050033
2015-03-08T14:21:26.0+01:00 kooka kernel: CR2: 01f0 CR3: 
000144fa7000 CR4: 07e0
2015-03-08T14:21:26.0+01:00 kooka kernel: Stack:
2015-03-08T14:21:26.0+01:00 kooka kernel:  0180 8800da76c800 
001f 742383d8
2015-03-08T14:21:26.0+01:00 kooka kernel:  742383d8 880054f19000 
ffa1 0002
2015-03-08T14:21:26.0+01:00 kooka kernel:  742383d8 88009bb57500 
 a025b214
2015-03-08T14:21:26.0+01:00 kooka kernel: Call Trace:
2015-03-08T14:21:26.0+01:00 kooka kernel:  [] ? 
btrfs_ioctl_snap_create_v2+0xe4/0x140 [btrfs]
2015-03-08T14:21:26.0+01:00 kooka kernel:  [] ? 
btrfs_ioctl+0x18ca/0x2780 [btrfs]
2015-03-08T14:21:26.0+01:00 kooka kernel:  [] ? 
handle_mm_fault+0x896/0x1000
2015-03-08T14:21:26.0+01:00 kooka kernel:  [] ? 
pty_write+0x54/0x60
2015-03-08T14:21:26.0+01:00 kooka kernel:  [] ? 
remove_wait_queue+0x16/0x60
2015-03-08T14:21:26.0+01:00 kooka kernel:  [] ? 
__do_page_fault+0x1c9/0x550
2015-03-08T14:21:26.0+01:00 kooka kernel:  [] ? 
pick_next_task_fair+0x6c8/0x850
2015-03-08T14:21:26.0+01:00 kooka kernel:  [] ? 
do_vfs_ioctl+0x2e8/0x4f0
2015-03-08T14:21:26.0+01:00 kooka kernel:  [] ? 
__schedule+0x2b3/0x800
2015-03-08T14:21:26.0+01:00 kooka kernel:  [] ? 
SyS_ioctl+0x81/0xa0
2015-03-08T14:21:26.0+01:00 ko

Bug#678797: linux-source-3.2: Feature Request: BTRFS

[Stuart Chalmers]

Hi Jonathan,

I'm not sure about specific patches I'm afraid - the most common theme on 
the btrfs mailing list seems to be 'try the latest version'.

With this in mind, perhaps sync to the upcoming 3.6 kernel (not sure how easy 
or otherwise this is), or perhaps align to what Oracle and Suse have 
done for Enterprise Support:

https://btrfs.wiki.kernel.org/index.php/Getting_started#Enterprise_distributions_with_btrfs_support

However, I get a 'gut 
feel' (so no stats to back this up) that the amount of interest in btrfs 
will lead to a lot of instalations trying it, so shipping the most 
mature version as is practical may be sensible as warnings around 
backups etc are frequently ignored.  The 3.2 version being shipped isn't a big 
issue for me personally as it's working fine just now, so happy to be guided by 
the Debian maintainers in terms of cost/benefit.

Also, there was some mention of an upcoming update on btrfs-progs on the 
btrfs mailing list too - another candidate to sync perhaps?

Thanks.

Bug#678797: linux-source-3.2: Feature Request: BTRFS

[Stuart Chalmers]

Package: linux-source-3.2
Severity: wishlist

Dear Maintainer,

For the release of Wheezy, please consider merging as recent a version of BTRFS
code as is practical, to allow Wheezy to benefit from the bug fixes performed
upstream since the release of linux 3.2.

Thanks.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20120624102650.4107.29338.report...@toryboywheezy.lan

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

[Stuart Pook]

On 01/05/11 22:26, Thibaut Girka wrote:

Anyway, I'd be really interested to hear from Stuart Pook: his story
sounds exactly like mine.


I'm not sure exactly what to say. My screen/PC died on about 23 February. At that time it 
would not even show BIOS messages. I started to try and understand what was wrong at the 
end of March. According to a "ls -lrtc /boot" I was probably running 
2.6.37-1-amd64 on 23 February. Let me know if you need more information.

I read with interest the report of how to correct a broken EDID. I might give 
it a go but not before next week.  
https://bugs.freedesktop.org/show_bug.cgi?id=34554


But I'm no expert, and since this method tempers with your hardware, I'd
recommend you to be cautious.


Yes, especially as I only have one Benq FP241W.

Stuart



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4dbdc73b.3080...@pook.it

Bug#622993: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

[Stuart Pook]

_block_valid]*ERROR* EDID checksum is invalid, remainder is 34
May  1 12:27:01 kooka kernel: : [   44.224782] 
[drm:drm_edid_block_valid]*ERROR* EDID checksum is invalid, remainder is 34
May  1 12:27:01 kooka kernel: : [   44.224790] 
[drm:drm_edid_block_valid]*ERROR* EDID checksum is invalid, remainder is 34
May  1 12:27:02 kooka kernel: : [   44.916280] 
[drm:drm_edid_block_valid]*ERROR* EDID checksum is invalid, remainder is 34
May  1 12:27:02 kooka kernel: : [   44.916291] 
[drm:drm_edid_block_valid]*ERROR* EDID checksum is invalid, remainder is 34
May  1 12:27:02 kooka kernel: : [   45.087196] 
[drm:drm_edid_block_valid]*ERROR* EDID checksum is invalid, remainder is 34
May  1 12:27:02 kooka kernel: : [   45.087209] 
[drm:drm_edid_block_valid]*ERROR* EDID checksum is invalid, remainder is 34

thanks again
Stuart Pook (http://www.pook.it/)





--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4dbd7b90.8080...@pook.it

Bug#622993: linux-image-2.6.38-2-amd64: every 10s I get "[drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid ..."

[Stuart Pook]

Package: linux-2.6
Version: 2.6.38-3
Severity: normal

Every 10 seconds I get the messages at the end of my bug report in
/var/log/kern.log. My /var/log/kern.log is very big! Why is the kernel
telling me what I already know every 10 seconds?

I have a Benq Product Name FP241W manufactured February 2007 Revision
B4-125 and used to use the DVI input. The EDID data in the DVI input
suddenly failed and the my PC would not longer boot. I plugged my PC
into the HDMI input of the monitor and the machine boots but X does not
start at the correct resolution. It appears that the EDID data from HMDI
input does not propose "1920x1200". I created /etc/X11/xorg.conf

Section "Monitor"
Identifier "HDMI Monitor"
Modeline "1920x1200" 154.00  1920 1968 2000 2080  1200 1203 1209 1235 
+hsync +vsync
Option "PreferredMode"  "1920x1200"
EndSection

Section "Device"
Identifier "ATI"
Option "Monitor-DVI-I-1" "HDMI Monitor"
EndSection

Now using the HMDI input works but when the screen saver kicks in I get
a blue screen rather than have the monitor go into standby mode. This
seems to be how the HDMI input of my screen works. So once X is running
I unplug my PC from the HDMI input and plug it into the DVI input. All
works well, the screen saver makes the screen go into standby mode,
except that the kernel tells me that the EDID data is not correct every
10 seconds.  Is there a way to make it stop?

I have a "ASUS EN7300GT SILENT/HTD/256M" graphics card with a
"nVidia GeForce 7300GT" GPU and am using the
"NOUVEAU driver Date:   Thu Mar 24 02:13:12 2011 +1000"

Apr 16 14:54:53 kooka kernel: : [227022.188046] [drm:drm_edid_block_valid] 
*ERROR* EDID checksum is invalid, remainder is 34
Apr 16 14:54:53 kooka kernel: : [227022.188050] [drm:drm_edid_block_valid] 
*ERROR* Raw EDID:
Apr 16 14:54:53 kooka kernel: : [227022.188053] <3>a1 80 ff ff ff ff ff 00 09 
d1 db 76 be 0f 00 00  ...v
Apr 16 14:54:53 kooka kernel: : [227022.188056] <3>07 11 01 03 80 34 21 78 ea 
5a d5 a7 56 4b 9b 24  .4!x.Z..VK.$
Apr 16 14:54:53 kooka kernel: : [227022.188058] <3>13 50 54 bd ef 80 71 4f 81 
90 81 80 81 8c a9 40  .PT...qO...@
Apr 16 14:54:53 kooka kernel: : [227022.188061] <3>b3 00 01 01 01 01 28 3c 80 
a0 70 b0 23 40 30 20  ..(<..p.#@0 
Apr 16 14:54:53 kooka kernel: : [227022.188063] <3>36 00 07 44 21 00 00 1e d5 
09 80 a0 20 5e 63 10  6..D!... ^c.
Apr 16 14:54:53 kooka kernel: : [227022.188066] <3>10 60 52 08 78 2d 11 00 00 
1a 00 00 00 fd 00 38  .`R.x-.8
Apr 16 14:54:53 kooka kernel: : [227022.188068] <3>4c 1e 53 11 00 0a 20 20 20 
20 20 20 00 00 00 fc  L.S...  
Apr 16 14:54:53 kooka kernel: : [227022.188071] <3>00 42 65 6e 51 20 32 34 31 
57 0a 20 20 20 00 dc  .BenQ 241W.   ..
Apr 16 14:54:53 kooka kernel: : [227022.188073] 
Apr 16 14:54:53 kooka kernel: : [227022.285822] [drm:drm_edid_block_valid] 
*ERROR* EDID checksum is invalid, remainder is 34
Apr 16 14:54:53 kooka kernel: : [227022.285825] [drm:drm_edid_block_valid] 
*ERROR* Raw EDID:
Apr 16 14:54:53 kooka kernel: : [227022.285828] <3>a1 80 ff ff ff ff ff 00 09 
d1 db 76 be 0f 00 00  ...v
Apr 16 14:54:53 kooka kernel: : [227022.285831] <3>07 11 01 03 80 34 21 78 ea 
5a d5 a7 56 4b 9b 24  .4!x.Z..VK.$
Apr 16 14:54:53 kooka kernel: : [227022.285833] <3>13 50 54 bd ef 80 71 4f 81 
90 81 80 81 8c a9 40  .PT...qO...@
Apr 16 14:54:53 kooka kernel: : [227022.285836] <3>b3 00 01 01 01 01 28 3c 80 
a0 70 b0 23 40 30 20  ..(<..p.#@0 
Apr 16 14:54:53 kooka kernel: : [227022.285838] <3>36 00 07 44 21 00 00 1e d5 
09 80 a0 20 5e 63 10  6..D!... ^c.
Apr 16 14:54:53 kooka kernel: : [227022.285841] <3>10 60 52 08 78 2d 11 00 00 
1a 00 00 00 fd 00 38  .`R.x-.8
Apr 16 14:54:53 kooka kernel: : [227022.285843] <3>4c 1e 53 11 00 0a 20 20 20 
20 20 20 00 00 00 fc  L.S...  
Apr 16 14:54:53 kooka kernel: : [227022.285846] <3>00 42 65 6e 51 20 32 34 31 
57 0a 20 20 20 00 dc  .BenQ 241W.   ..
Apr 16 14:54:53 kooka kernel: : [227022.285848] 
Apr 16 14:54:54 kooka kernel: : [227022.383616] [drm:drm_edid_block_valid] 
*ERROR* EDID checksum is invalid, remainder is 34
Apr 16 14:54:54 kooka kernel: : [227022.383619] [drm:drm_edid_block_valid] 
*ERROR* Raw EDID:
Apr 16 14:54:54 kooka kernel: : [227022.383621] <3>a1 80 ff ff ff ff ff 00 09 
d1 db 76 be 0f 00 00  ...v
Apr 16 14:54:54 kooka kernel: : [227022.383624] <3>07 11 01 03 80 34 21 78 ea 
5a d5 a7 56 4b 9b 24  .4!x.Z..VK.$
Apr 16 14:54:54 kooka kernel: : [227022.383627] <3>13 50 54 bd ef 80 71 4f 81 
90 81 80 81 8c a9 40  .PT...qO...@
Apr 16 14:54:54 kooka kernel: : [227022.383629] <3>b3 00 01 01 01 01 28 3c 80 
a0 70 b0 23 40 30 20  ..(<..p.#@0 
Apr 16 14:54:54 kooka kernel: : [227022.383631] <3>36 00 07 44 21 00 00 1e d5 
09 80 a0 20 5e 63 10  6..D!... ^c.
Apr 16 14:54:54 kooka kernel: : [227022.383634] <3>10 60 52 08 78 2d 11 00 00 
1a 00 00 00 fd 00 38  .`R.x-.8
Apr 16 14:54:54 kooka kernel: : [227022.38363

Bug#597952: Initramfs.tools fail yet again

[George Stuart]

--- On Thu, 9/30/10, maximilian attems  wrote:

From: maximilian attems 
Subject: Re: Bug#597952: Initramfs.tools fail yet again
To: "George Stuart" 
Cc: 597...@bugs.debian.org
Date: Thursday, September 30, 2010, 6:25 AM

Please "reply to all", so that the bug report also gets your mail,
thanks.

On Tue, Sep 28, 2010 at 09:08:46AM -0700, George Stuart wrote:
> 
> 
> Out put from ls -l /var/lib/initramfs-tools
> 
> r...@debian:/home/chevy# ls -l /var/lib/initramfs-tools
> total 12
> -rw-r--r-- 1 root root 81 Sep 24 15:06 2.6.32-5-openvz-amd64
> -rw-r--r-- 1 root root 78 Aug 22 23:31 2.6.32-trunk-amd64
> -rw-r--r-- 1 root root 89 Sep 28 09:21 vmlinuz-2.6.32-5-openvz-amd64
> 
> 
> Results of COLUMNS=210 dpkg -l linux-image*
> r...@debian:/home/chevy# COLUMNS=210 dpkg -l linux-image*
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name                                           Version                    
>                     Description
> +++-==-==-
> un  linux-image                                                         
>                     (no description available)
> un  linux-image-2.6                                                     
>                     (no description available)
> ii  linux-image-2.6.32-5-openvz-amd64              2.6.32-23                  
>                     Linux 2.6.32 for 64-bit PCs, OpenVZ support
> ii  linux-image-2.6.32-trunk-amd64                 2.6.32-5                   
>                     Linux 2.6.32 for 64-bit PCs
> ii  linux-image-openvz-amd64                       2.6.32+28                  
>                     Linux for 64-bit PCs (meta-package), OpenVZ support
> r...@debian:/home/chevy# 

how did you generate linux-image-openvz-amd64, this is not
an official image?

thanks

-- 
maks

I got the image using aptitude.
r...@debian:/home/chevy# aptitude search linux-image
v   linux-image-
  
v   linux-image-2.6-
  
p   linux-image-2.6-amd64  - 
Linux 2.6 for 64-bit PCs (meta-package) 
 
p   linux-image-2.6-openvz-amd64   - 
Linux 2.6 for 64-bit PCs (meta-package), OpenVZ support 
 
p   linux-image-2.6-vserver-amd64  - 
Linux 2.6 for 64-bit PCs (meta-package), Linux-VServer support  
 
p   linux-image-2.6-xen-amd64  - 
Linux 2.6 for 64-bit PCs (meta-package), Xen dom0 support, Xen dom0 support 
 
p   linux-image-2.6.30-2-amd64 - 
Linux 2.6.30 image on AMD64 
 
p   linux-image-2.6.32-5-amd64 - 
Linux 2.6.32 for 64-bit PCs 
 
p   linux-image-2.6.32-5-amd64-dbg - 
Debugging infos for Linux 2.6.32-5-amd64
 
i A linux-image-2.6.32-5-openvz-amd64  - 
Linux 2.6.32 for 64-bit PCs, OpenVZ support 
 
p   linux-image-2.6.32-5-openvz-amd64-dbg  - 
Debugging infos for Linux 2.6.32-5-openvz-amd64 
 
p   linux-image-2.6.32-5-vserver-amd64 - 
Linux 2.6.32 for 64-bit PCs, Linux-VServer support  
 
p   linux-image-2.6.32-5-vserver-amd64-dbg - 
Debugging infos for Linux 2.6.32-5-vserver-amd64
 
p   linux-image-2.6.32-5-xen-amd64 - 
Linux 2.6.32 for 64-bit PCs, Xen dom0 support   
 
p   linux-image-2.6.32-5-xen-amd64-dbg - 
Debugging infos for Linux 2.6.32-5-xen-amd64
 
i   linux-image-2.6.32-trunk-amd64 - 
Linux 2.6.32 for 64-bit PCs 
 
p   linux-image-amd64  - 
L

Bug#597952: Initramfs.tools fail yet again

[George Stuart]

--- On Tue, 9/28/10, maximilian attems  wrote:

From: maximilian attems 
Subject: Re: Bug#597952: Initramfs.tools fail yet again
To: "George Stuart" , 597...@bugs.debian.org
Date: Tuesday, September 28, 2010, 10:24 AM

On Tue, Sep 28, 2010 at 06:14:55AM -0700, George Stuart wrote:
> Processing triggers for initramfs-tools ...
> update-initramfs: Generating /boot/initrd.img-vmlinuz-2.6.32-5-openvz-amd64
> grep: /boot/config-vmlinuz-2.6.32-5-openvz-amd64: No such file or directory
> WARNING: missing
 /lib/modules/vmlinuz-2.6.32-5-openvz-amd64
> Device driver support needs thus be built-in linux image!
> FATAL: modules must be specified using absolute paths.
> "vmlinuz-2.6.32-5-openvz-amd64" is a relative path
> FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
> No such file or directory
> FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
> No such file or directory
> FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
> No such file or directory
> FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
> No such file or directory
> FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
> No such file or directory
> FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
> No such file or directory
> FATAL: Could not load
 /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: No such file or 
directory
> WARNING: Couldn't open directory 
> /tmp/mkinitramfs_eZpHn8/lib/modules/2.6.32-5-openvz-amd64: No such file or 
> directory
> FATAL: Could not open 
> /tmp/mkinitramfs_eZpHn8/lib/modules/2.6.32-5-openvz-amd64/modules.dep.temp 
> for writing: No such file or directory

please post output of:

ls -l /var/lib/initramfs-tools

COLUMNS=210 dpkg -l linux-image*


Out put from ls -l /var/lib/initramfs-tools

r...@debian:/home/chevy# ls -l /var/lib/initramfs-tools
total 12
-rw-r--r-- 1 root root 81 Sep 24 15:06 2.6.32-5-openvz-amd64
-rw-r--r-- 1 root root 78 Aug 22 23:31 2.6.32-trunk-amd64
-rw-r--r-- 1 root root 89 Sep 28 09:21 vmlinuz-2.6.32-5-openvz-amd64


Results of COLUMNS=210 dpkg -l linux-image*
r...@debian:/home/chevy# COLUMNS=210 dpkg -l linux-image*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  
  Description
+++-==-==-
un  linux-image   
  (no description available)
un  linux-image-2.6   
  (no description available)
ii  linux-image-2.6.32-5-openvz-amd64  2.6.32-23
  Linux 2.6.32 for 64-bit PCs, OpenVZ support
ii  linux-image-2.6.32-trunk-amd64 2.6.32-5 
  Linux 2.6.32 for 64-bit PCs
ii  linux-image-openvz-amd64   2.6.32+28
  Linux for 64-bit PCs (meta-package), OpenVZ support
r...@debian:/home/chevy# 

Thanks 
George


  

Bug#597952: initramfs-tools not up-dating correctly after aptitude full-upgrade today.

[George Stuart]

--- On Sat, 9/25/10, maximilian attems  wrote:

From: maximilian attems 
Subject: Re: Bug#597952: initramfs-tools not up-dating correctly after aptitude 
full-upgrade today.
To: "George Stuart" 
Cc: 597...@bugs.debian.org
Date: Saturday, September 25, 2010, 4:00 PM

please keep bug report on cc, thanks.

On Fri, Sep 24, 2010 at 12:47:18PM -0700, George Stuart wrote:
> 
> 
> + ec2=0
> + ec3=0
> + [ 0 -ne 0 ]
> + [ 0 -ne 0 ]
> + [ 0 -ne 0 ]
> + [ -s /tmp/mkinitramfs-OL_T530Kv ]
> + [ n = y ]
> + rm -rf /tmp/mkinitramfs_SjKBkm
> + rm -rf /tmp/mkinitramfs-OL_T530Kv
> + exit 0

ok looks good.

> r...@debian:/home/chevy# sh -x /usr/sbin/update-initramfs -u -k 
> 2.6.32-5-openvz-amd64
> + rm -f /boot/initrd.img-2.6.32-5-openvz-amd64.dpkg-bak
> + return 0

same story here, so what is the trouble?

hmm please post full current apt log:
apt-get -f install

thanks

r...@debian:/home/chevy# apt-get -f install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
r...@debian:/home/chevy# 

this from /var/log/term.log may help
Log started: 2010-09-24  09:11:39
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 148349 files and directories currently installed.)
Preparing to replace dnsmasq-base 2.55-1 (using 
.../dnsmasq-base_2.55-2_amd64.deb) ...
Unpacking replacement dnsmasq-base ...
Preparing to replace initramfs-tools 0.98.2 (using 
.../initramfs-tools_0.98.3_all.deb) ...
Unpacking replacement initramfs-tools ...
Processing triggers for man-db ...
Setting up dnsmasq-base (2.55-2) ...
Setting up initramfs-tools (0.98.3) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-vmlinuz-2.6.32-5-openvz-amd64
grep: /boot/config-vmlinuz-2.6.32-5-openvz-amd64: No such file or directory
WARNING: missing /lib/modules/vmlinuz-2.6.32-5-openvz-amd64
Device driver support needs thus be built-in linux image!
FATAL: modules must be specified using absolute paths.
"vmlinuz-2.6.32-5-openvz-amd64" is a relative path
FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
No such file or directory
FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
No such file or directory
FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
No such file or directory
FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
No such file or directory
FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
No such file or directory
FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
No such file or directory
FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
No such file or directory
WARNING: Couldn't open directory 
/tmp/mkinitramfs_71tuS0/lib/modules/2.6.32-5-openvz-amd64: No such file or 
directory
FATAL: Could not open 
/tmp/mkinitramfs_71tuS0/lib/modules/2.6.32-5-openvz-amd64/modules.dep.temp for 
writing: No such file or directory
Log ended: 2010-09-24  09:11:48

Log started: 2010-09-24  11:17:14
Log ended: 2010-09-24  11:17:14

This may or may not help. From /var/log/dpkg.log
2010-09-24 09:11:39 startup archives unpack
2010-09-24 09:11:41 upgrade dnsmasq-base 2.55-1 2.55-2
2010-09-24 09:11:41 status half-configured dnsmasq-base 2.55-1
2010-09-24 09:11:41 status unpacked dnsmasq-base 2.55-1
2010-09-24 09:11:41 status half-installed dnsmasq-base 2.55-1
2010-09-24 09:11:41 status triggers-pending man-db 2.5.7-4
2010-09-24 09:11:41 status half-installed dnsmasq-base 2.55-1
2010-09-24 09:11:42 status half-installed dnsmasq-base 2.55-1
2010-09-24 09:11:42 status unpacked dnsmasq-base 2.55-2
2010-09-24 09:11:42 status unpacked dnsmasq-base 2.55-2
2010-09-24 09:11:42 upgrade initramfs-tools 0.98.2 0.98.3
2010-09-24 09:11:42 status half-configured initramfs-tools 0.98.2
2010-09-24 09:11:42 status unpacked initramfs-tools 0.98.2
2010-09-24 09:11:42 status half-installed initramfs-tools 0.98.2
2010-09-24 09:11:42 status half-installed initramfs-tools 0.98.2
2010-09-24 09:11:43 status half-installed initramfs-tools 0.98.2
2010-09-24 09:11:43 status unpacked initramfs-tools 0.98.3
2010-09-24 09:11:43 status unpacked initramfs-tools 0.98.3
2010-09-24 09:11:43 trigproc man-db 2.5.7-4 2.5.7-4
2010-09-24 09:11:43 statu

Bug#597952: Initramfs.tools fail yet again

[George Stuart]

Output from aptitude full-upgrade.
r...@debian:/home/chevy# aptitude full-upgrade
The following packages will be upgraded: 
  binutils console-setup iceweasel initramfs-tools keyboard-configuration 
libmozjs2d login passwd xulrunner-1.9.1 
9 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 16.8MB of archives. After unpacking 246kB will be freed.
Do you want to continue? [Y/n/?] 
Get:1 http://ftp.us.debian.org/debian/ squeeze/main login amd64 
1:4.1.4.2+svn3283-2 [783kB]
Get:2 http://ftp.us.debian.org/debian/ squeeze/main passwd amd64 
1:4.1.4.2+svn3283-2 [1,113kB]
Get:3 http://ftp.us.debian.org/debian/ squeeze/main binutils amd64 2.20.1-15 
[3,993kB]   
 
Get:4 http://ftp.us.debian.org/debian/ squeeze/main keyboard-configuration all 
1.56 [255kB]   
Get:5 http://ftp.us.debian.org/debian/ squeeze/main console-setup all 1.56 
[635kB] 
   
Get:6 http://ftp.us.debian.org/debian/ squeeze/main xulrunner-1.9.1 amd64 
1.9.1.13-1 [8,401kB]

Get:7 http://ftp.us.debian.org/debian/ squeeze/main libmozjs2d amd64 1.9.1.13-1 
[433kB]   
Get:8 http://ftp.us.debian.org/debian/ squeeze/main iceweasel amd64 3.5.13-1 
[1,110kB]   
 
Get:9 http://ftp.us.debian.org/debian/ squeeze/main initramfs-tools all 0.98.4 
[88.5kB]   
Fetched 16.8MB in 34s (486kB/s) 
  
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 148387 files and directories currently installed.)
Preparing to replace login 1:4.1.4.2+svn3283-1 (using 
.../login_1%3a4.1.4.2+svn3283-2_amd64.deb) ...
Unpacking replacement login ...
Processing triggers for man-db ...
Setting up login (1:4.1.4.2+svn3283-2) ...
(Reading database ... 148387 files and directories currently installed.)
Preparing to replace passwd 1:4.1.4.2+svn3283-1 (using 
.../passwd_1%3a4.1.4.2+svn3283-2_amd64.deb) ...
Unpacking replacement passwd ...
Processing triggers for man-db ...
Setting up passwd (1:4.1.4.2+svn3283-2) ...
Installing new version of config file /etc/cron.daily/passwd ...
(Reading database ... 148387 files and directories currently installed.)
Preparing to replace binutils 2.20.1-12 (using 
.../binutils_2.20.1-15_amd64.deb) ...
Unpacking replacement binutils ...
Preparing to replace keyboard-configuration 1.55 (using 
.../keyboard-configuration_1.56_all.deb) ...
Unpacking replacement keyboard-configuration ...
Preparing to replace console-setup 1.55 (using .../console-setup_1.56_all.deb) 
...
Unpacking replacement console-setup ...
Preparing to replace xulrunner-1.9.1 1.9.1.12-2 (using 
.../xulrunner-1.9.1_1.9.1.13-1_amd64.deb) ...
Unpacking replacement xulrunner-1.9.1 ...
Preparing to replace libmozjs2d 1.9.1.12-2 (using 
.../libmozjs2d_1.9.1.13-1_amd64.deb) ...
Unpacking replacement libmozjs2d ...
Preparing to replace iceweasel 3.5.12-2 (using 
.../iceweasel_3.5.13-1_amd64.deb) ...
Leaving 'diversion of /usr/bin/firefox to /usr/bin/firefox.real by iceweasel'
Unpacking replacement iceweasel ...
Preparing to replace initramfs-tools 0.98.3 (using 
.../initramfs-tools_0.98.4_all.deb) ...
Unpacking replacement initramfs-tools ...
Processing triggers for man-db ...
Processing triggers for menu ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Setting up binutils (2.20.1-15) ...
Setting up keyboard-configuration (1.56) ...
Setting up console-setup (1.56) ...
Setting up libmozjs2d (1.9.1.13-1) ...
Setting up xulrunner-1.9.1 (1.9.1.13-1) ...
Installing new version of config file /etc/gre.d/1.9.1.system.conf ...
Setting up iceweasel (3.5.13-1) ...
Setting up initramfs-tools (0.98.4) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for menu ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-vmlinuz-2.6.32-5-openvz-amd64
grep: /boot/config-vmlinuz-2.6.32-5-openvz-amd64: No such file or directory
WARNING: missing /lib/modules/vmlinuz-2.6.32-5-openvz-amd64
Device driver support needs thus be built-in linux image!
FATAL: modules must be specified using absolute paths.
"vmlinuz-2.6.32-5-openvz-amd64" is a relative path
FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
No such file or directory
FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.dep: 
No such file or directory
FATAL: Could not load /lib/modules/vmlinuz-2.6.32-5-openvz-amd64/modules.d

Bug#594845: Acknowledgement (linux-image-2.6.32-5-amd64: kernel BUG at /build/buildd-linux-2.6_2.6.32-20-amd64-lNUT1p/..../fs/sysfs/file.c:539)

[Russell Stuart]

> You are editing in the wrong place.  The patch needs to be applied in
> debian/build/source_amd64_none.

Ta.  I applied the patch to every copy of tun.c other than the one in
source_amd64_openvz_amd64, and now the my trace is printed as it should
be.  

And with the patch applied properly the problem disappears, so it does
indeed fix the problem.

> The debian/bin/test-patches script can handle this all for you.

Unfortunately the patch doesn't apply to source_amd64_openvz_amd64, and
test-patches dies as soon as that fails.  That is why I was doing it
manually.




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1283844141.4098.113.ca...@russell-laptop

Bug#594845: Acknowledgement (linux-image-2.6.32-5-amd64: kernel BUG at /build/buildd-linux-2.6_2.6.32-20-amd64-lNUT1p/..../fs/sysfs/file.c:539)

[Russell Stuart]

On Sun, 2010-09-05 at 01:45 +0100, Ben Hutchings wrote:
> Are you quite sure you used the modified kernel?

Nope. 

> 'cat /proc/version' will tell you for sure which version you are
> running.

$ cat /proc/version 
Linux version 2.6.32-5-amd64 (Debian 2.6.32-20.2) (russell-deb...@stuart.id.au) 
(gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Mon Sep 6 09:14:09 EST 2010

So that looks like I am running the right kernel.  But because the
symptoms didn't change overly I had my doubts from the beginning, and
thus have been trying to prove I was running the kernel with your patch
applied.  Doing that in various ways is why it took me a while to
respond to your request to test the patch.

One way I tried to confirm it by adding trace:

--- x/linux-2.6-2.6.32/drivers/net/tun.c2009-12-03 13:51:21.0 
+1000
+++ linux-2.6-2.6.32/drivers/net/tun.c  2010-09-06 08:09:44.068458190 +1000
@@ -36,7 +36,7 @@
 
 #define DRV_NAME   "tun"
 #define DRV_VERSION"1.6"
-#define DRV_DESCRIPTION"Universal TUN/TAP device driver"
+#define DRV_DESCRIPTION"Universal TUN/TAP device driver + 
0001-tun-Don-t-add-sysfs-attributes-to-devices-without-sy.patch applied"
 #define DRV_COPYRIGHT  "(C) 1999-2004 Max Krasnyansky "
 
 #include 
@@ -1006,7 +1006,9 @@
if (err < 0)
goto err_free_sk;
 
-   if (device_create_file(&tun->dev->dev, &dev_attr_tun_flags) ||
+   printk(KERN_INFO 
"0001-tun-Don-t-add-sysfs-attributes-to-devices-without-sy.patch\n");
+   if (!net_eq(dev_net(tun->dev), &init_net) ||
+   device_create_file(&tun->dev->dev, &dev_attr_tun_flags) ||
device_create_file(&tun->dev->dev, &dev_attr_owner) ||
device_create_file(&tun->dev->dev, &dev_attr_group))
printk(KERN_ERR "Failed to create tun sysfs files\n");

None of the trace is ever appears in /var/log/kern.log, which is to say
"grep 0001-tun /var/log/kern.log" prints nothing. Yet I am evidently
running a different kernel as I don't ever hit the BUG the buildd kernel
generates.  I don't have a clue what is going on.

The steps I used to generate the kernel are:

  $ apt-get source linux-2.6
  $ cd linux-2.6-2.6.32
  $ fakeroot debian/rules source
  $ fakeroot debian/rules setup
  $ patch -p1 
<.../0001-tun-Don-t-add-sysfs-attributes-to-devices-without-sy.patch
  $ ed drivers/net/tun.c  # add trace
  $ ed debian/changelog   # add rev 2.6.30-20.2
  $ fakeroot debian/rules binary
  $ sudo dpkg -i ../linux-image-2.6.32-5-amd64_2.6.32-20.2_amd64.deb
  $ sudo ed /boot/grub/grub.cfg   # set the default kernel
  $ sudo reboot -f





-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1283773622.4264.65.ca...@russell-laptop

Bug#594845: Acknowledgement (linux-image-2.6.32-5-amd64: kernel BUG at /build/buildd-linux-2.6_2.6.32-20-amd64-lNUT1p/..../fs/sysfs/file.c:539)

[Russell Stuart]

On Mon, 2010-08-30 at 14:48 +0100, Ben Hutchings wrote: 
> On Mon, 2010-08-30 at 17:34 +1000, Russell Stuart wrote:
> > The problem disappears in
> > linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.2.
> 
> Yes, as I expected.
> 
> Can you please test the attached patch against the version in unstable?
> Directions for rebuilding an official kernel package are at
> <http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official>.

Applied that.  It changed the problem.

Before I got a nice repeatable BUG.  Now the openvpn instance
unconditionally segfaults and normally nothing appears on the console or
in kern.log.  Once I got "lucky" and this appeared on the console:

Message from sysl...@toby at Sep  4 09:11:57 ...
 kernel:[52062.327222] [ cut here ]

Message from sysl...@toby at Sep  4 09:11:57 ...
 kernel:[52062.329577] invalid opcode:  [#1] SMP 

Message from sysl...@toby at Sep  4 09:11:57 ...
 kernel:[52062.330671] last sysfs
file: /sys/devices/virtual/misc/tun/uevent

Message from sysl...@toby at Sep  4 09:11:57 ...
 kernel:[52062.330671] Stack:

Message from sysl...@toby at Sep  4 09:11:57 ...
 kernel:[52062.330671] Call Trace:

Message from sysl...@toby at Sep  4 09:11:57 ...
 kernel:[52062.330671] Code: 74 0f 48 89 ef e8 24 07 00 00 eb 05
bb fe ff ff ff 89 d8 5b 5d 41 5c c3 48 85 ff 74 0e 48 8b 7f 30
48 85 ff 74 05 48 85 f6 75 04 <0f> 0b eb fe ba 02 00 00 00 e9 5d
ff ff ff 55 53 48 89 fb 48 c7 

The machine appears to freeze in various ways - eg you can't get a login
prompt to have a sniff around and the first command you type at an
existing shell prompt that requires disk IO freezes, and a "sleep 300;
sudo reboot -f" doesn't do anything.  On the other hand a "for f in
$(seq 1000); do echo $f; sleep 1; done" continues on as though nothing
has happened.  Disk IO is probably borked.




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1283556425.23992.14.ca...@russell-laptop

Bug#594845: Acknowledgement (linux-image-2.6.32-5-amd64: kernel BUG at /build/buildd-linux-2.6_2.6.32-20-amd64-lNUT1p/..../fs/sysfs/file.c:539)

[Russell Stuart]

The problem disappears in
linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.2.




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1283153685.4366.2.ca...@russell-laptop

Bug#591574: Xen + ATI Radeon HD - X Server not starting

[Stuart Chalmers]

Package: linux-image-2.6.32-5-xen-amd64
Version: 2.3.32-18

libc6 v2.11.2-2 (amd64)

When booting Xen (xen-hypervisor-4.0-amd64, v4.0.1~rc3-1) and the above kernel 
image, the system boots but is unable to launch an X server (xserver-xorg, 
v1:7.5+6) in the default configuration.  I believe that this is connected to 
the 
hardware acceleration (DRI/DRM) in the Radeon driver 
(xserver-xorg-video-[ati|radeon], v1:6.13.1-2) being enabled.  Note that Kernel 
Mode Setting works where it did not with the  previous 
linux-image-2.6.32-5-xen-amd64 that I had installed from Squeeze (I believe 
that 
it was v2.6.32-15).

As a workaround (hopefully temporary), I have added a small /etc/X11/xorg.conf 
to disable hardware acceleration and it enables the X server to start (no other 
options other than what's below).

--

Section "Device"
Driver"radeon"
Identifier "ATI RV730XT [Radeon HD 4670]"
Option"NoAccel" "on"
Option"ColorTiling" "off"
Option"DRI" "off"
EndSection

--

I have had a search on the Web and it seems that there is ongoing work within 
Xen to look to deal with this:

http://wiki.xensource.com/xenwiki/XenPVOPSDRM

I'd be very grateful if the appropriate code (possibly related to 
r600_ring_test 
for my own issues?) could be considered for inclusion into the Xen kernel to be 
shipped with Squeeze.  I myself am not overly familiar with applying patches, 
but am more than happy to help test this - be it running packaged, patched 
kernels or applying patches with appropriate guidance.

I have also detailed below the Xorg.0.log from the system booted without Xen 
(but with a Xen kernel) and without the /etc/X11/xorg.conf that I detailed 
above.

Thanks in advance for your help.  Please let me know if you need any more 
information.

--

X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32-5-amd64 x86_64 Debian
Current Operating System: Linux  2.6.32-5-xen-amd64 #1 SMP Sat Jul 24 
04:03:11 UTC 2010 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-xen-amd64 
root=/dev/mapper/- ro quiet
Build Date: 15 July 2010  03:08:26PM
xorg-server 2:1.7.7-3 (Cyril Brulebois ) 
Current version of pixman: 0.16.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug  3 23:42:40 2010
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(==) No Layout section.  Using the first Screen section.
(==) No screen section available. Using defaults.
(**) |-->Screen "Default Screen Section" (0)
(**) |   |-->Monitor ""
(==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
(II) Loader magic: 0x7c6000
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(++) using VT number 7

(--) PCI:*(0:1:0:0) 1002:9490:174b:e100 ATI Technologies Inc RV730XT [Radeon HD 
4670] rev 0, Mem @ 0xd000/268435456, 0xfdee/65536, I/O @ 
0xee00/256, 
BIOS @ 0x/131072
(II) Open ACPI successful (/var/run/acpid.socket)
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension SELinux
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.7.7, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/x

Bug#536309: linux-image-2.6.30-1-amd64: {/dev, /sys/class/vc}/{vcs, vcsa1} don't exist in 2.6.30

[Russell Stuart]

Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-1
Severity: normal


In 2.6.30 these files no longer appear:

  /dev/vcs1
  /dev/vcsa1
  /sys/class/vc/vcs1
  /sys/class/vc/vcsa1
  
All the other virtual console device files (eg /dev/vcs2) are OK.  If you
manually create /dev/vcsa1 it works as expected.

This is a buck pass from bug #535625.


-- Package-specific info:
** Version:
Linux version 2.6.30-1-amd64 (Debian 2.6.30-1) (wa...@debian.org) (gcc version 
4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Wed Jul 8 13:57:36 EST 2009

** Command line:
root=/dev/sda5 ro quiet resume=/dev/sda6

** Tainted: P (1)

** Kernel log:
[7.560570] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 
1.3.27ks
[7.560572] iwlagn: Copyright(c) 2003-2009 Intel Corporation
[7.560947] iwlagn :0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[7.560955] iwlagn :0c:00.0: setting latency timer to 64
[7.560991] iwlagn :0c:00.0: Detected Intel Wireless WiFi Link 5300AGN 
REV=0x24
[7.582923] iwlagn :0c:00.0: Tunable channels: 13 802.11bg, 24 802.11a 
channels
[7.582994]   alloc irq_desc for 31 on cpu 0 node 0
[7.582995]   alloc kstat_irqs on cpu 0 node 0
[7.583014] iwlagn :0c:00.0: irq 31 for MSI/MSI-X
[7.585583] dcdbas dcdbas: Dell Systems Management Base Driver (version 
5.6.0-3.2)
[7.732606] HDA Intel :00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 
21
[7.732644] HDA Intel :00:1b.0: setting latency timer to 64
[7.824734] phy0: Selected rate control algorithm 'iwl-agn-rs'
[7.863920] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input8
[7.960985] input: HDA Intel Mic at Sep Left Jack as 
/devices/pci:00/:00:1b.0/input/input9
[7.961044] input: HDA Intel Mic at Ext Right Jack as 
/devices/pci:00/:00:1b.0/input/input10
[7.961084] input: HDA Intel Line Out at Sep Left Jack as 
/devices/pci:00/:00:1b.0/input/input11
[7.961124] input: HDA Intel HP Out at Ext Right Jack as 
/devices/pci:00/:00:1b.0/input/input12
[8.063421] input: DualPoint Stick as 
/devices/platform/i8042/serio1/input/input13
[8.080553] input: AlpsPS/2 ALPS DualPoint TouchPad as 
/devices/platform/i8042/serio1/input/input14
[   14.025003] Adding 4192924k swap on /dev/sda6.  Priority:-1 extents:1 
across:4192924k 
[   14.529853] EXT3 FS on sda5, internal journal
[   15.072415] loop: module loaded
[   16.576361] fuse init (API version 7.11)
[   18.586483] NET: Registered protocol family 15
[   18.615046] alg: No test for cipher_null (cipher_null-generic)
[   18.615086] alg: No test for ecb(cipher_null) (ecb-cipher_null)
[   18.615188] alg: No test for digest_null (digest_null-generic)
[   18.615255] alg: No test for compress_null (compress_null-generic)
[   19.153917] Intel AES-NI instructions are not detected.
[   21.417473] e1000e :00:19.0: irq 29 for MSI/MSI-X
[   21.473114] e1000e :00:19.0: irq 29 for MSI/MSI-X
[   21.473633] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   23.001236] Clocksource tsc unstable (delta = -146643916 ns)
[   42.848951] lp: driver loaded but no devices found
[   42.901420] ppdev: user-space parallel port driver
[   52.600964] iwlagn :0c:00.0: firmware: requesting iwlwifi-5000-2.ucode
[   52.672630] iwlagn :0c:00.0: iwlwifi-5000-2.ucode firmware file req 
failed: -2
[   52.672777] iwlagn :0c:00.0: firmware: requesting iwlwifi-5000-1.ucode
[   52.723004] iwlagn :0c:00.0: Loaded firmware iwlwifi-5000-1.ucode, which 
is deprecated. Please use API v2 instead.
[   52.723155] iwlagn :0c:00.0: Firmware has old API version. Expected v2, 
got v1. New firmware can be obtained from http://www.intellinuxwireless.org.
[   52.723301] iwlagn :0c:00.0: loaded firmware version 5.4.1.16
[   52.887376] Registered led device: iwl-phy0::radio
[   52.887418] Registered led device: iwl-phy0::assoc
[   52.887462] Registered led device: iwl-phy0::RX
[   52.887498] Registered led device: iwl-phy0::TX
[   52.894993] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   53.253892] warning: `ntpd' uses 32-bit capabilities (legacy support in use)
[   57.523301] Registered led device: iwl-phy0::radio
[   57.523347] Registered led device: iwl-phy0::assoc
[   57.523384] Registered led device: iwl-phy0::RX
[   57.523421] Registered led device: iwl-phy0::TX
[   57.530814] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   57.975243] wlan0: authenticate with AP 00:21:29:d7:b7:15
[   57.975275] wlan0: privacy configuration mismatch and mixed-cell disabled - 
disassociate
[   57.977220] wlan0: authenticated
[   57.977227] wlan0: associate with AP 00:21:29:d7:b7:15
[   57.977233] wlan0: mismatch in privacy configuration and mixed-cell disabled 
- abort association
[   57.978385] wlan0: authenticate with AP 00:21:29:d7:b7:15
[   57.978408] wlan0: privacy configuration mismatch and mixed-cell disabled - 
disassociate
[   57.980343] wlan0: authenticated
[   57.980349] wlan0: associate with AP 00

Bug#530726: linux-image-2.6.29-2-xen-amd64: linux-image-2.6.29-2 does not build with the xen feature enabled

[Russell Stuart]

Package: linux-image-2.6.29-2-xen-amd64
Version: 2.6.29-5
Severity: serious
Justification: no longer builds from source


I am trying to build linux-image-2.6.29-2-xen-amd64 from the source
package, and admit I don't have a clue how to do this.  (Some doco
in debian/README.txt on how to use the featuresets would be nice).  In
the end I edited debian/config/defines and set "enabled" to "true"
for the xen feature.

The debuild without the xen featureset worked. With the xen feature
enabled it died trying to copy vmlimuz to the install directory.
This is because there is no vmliumz under arch/x86/boot.  There
is however a bzImage.  Changing line 418 in debian/rules.real
from:

  cp '$(DIR)'/arch/$(KERNEL_ARCH)/boot/vmlinuz 
$(INSTALL_DIR)/vmlinuz-$(REAL_VERSION)

to:

  cp '$(DIR)'/arch/$(KERNEL_ARCH)/boot/bzImage 
$(INSTALL_DIR)/vmlinuz-$(REAL_VERSION)

seemed to fix the problem. Well it does if:

  ls -l linux-image-2.6.29-2-xen-amd64_2.6.29-5_amd64.deb 
  -rw-r--r-- 1 it it 2159982 2009-05-27 17:22 
linux-image-2.6.29-2-xen-amd64_2.6.29-5_amd64.deb

means it is fixed.  Might introduce other problems though - I
didn't check.



-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages linux-image-2.6.29-2-xen-amd64 depends on:
ii  initramfs-tools   0.92o  tools for generating an initramfs
ii  linux-modules-2.6.29-2-xen-am 2.6.29-5   Linux 2.6.29 modules on AMD64

linux-image-2.6.29-2-xen-amd64 recommends no packages.

Versions of packages linux-image-2.6.29-2-xen-amd64 suggests:
ii  grub   0.97-47lenny2 GRand Unified Bootloader (Legacy v
ii  linux-doc-2.6.29   2.6.29-5  Linux kernel specific documentatio

-- 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#524442: Bug#515258: hal hangs with 2.6.29-rc5

[Stuart Pook]

This problem seems to have been solved in the kernel 2.6.30-rc2.
When using this kernel hald starts without any problems.

Can someone indicate where I can find a howto for compiling an
official kernel using Debian? kernel-package 12.009 says in
/usr/share/doc/kernel-package/NEWS.Debian.gz "we no longer
cater to official kernels." How does one now create an
.deb from an official kernel that makes a /boot/initrd.img image
when it is installed? I used to use make-kpkg but it belongs
to kernel-package and no longer creates a initrd even with the
option --initrd.

thanks

:; dpkg -l hal | sed -ne '$s/  */ /gp' 
ii hal 0.5.12~git20090406.46dc48-1 Hardware Abstraction Layer

:; uname -a
Linux kooka 2.6.30-rc2 #2 SMP Sun Apr 19 11:28:08 CEST 2009 i686 GNU/Linux
:; dpkg -l kernel-package | sed -ne '$s/  */ /gp' 
ii kernel-package 12.009 A utility for building Linux kernel related Debian packages.


--
If the From address bounces, please see http://www.pook.it/.



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

Bug#524442: linux-image-2.6.29-1-686: hangs starting hald when booting into multiuser mode

[Stuart Pook]

I didn't notice that dpkg had truncated the version of hal that I'm using.

:; dpkg -l hal | sed -ne '$s/  */ /gp'
ii hal 0.5.12~git20090406.46dc48-1 Hardware Abstraction Layer

--
If the From address bounces, please see http://www.pook.it/.



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

linux-kbuild

[Russell Stuart]

Hi.  I have a problem I am sure is not atypical.  My new laptop doesn't
work too well with the lenny 2.6.26 kernel.  This in itself isn't the
problem, nor is it surprising.  I don't actually recall ever getting a
new laptop that was fully supported by Debian stable.

In the past solving it has been a combination of waiting until a kernel
that did support it was packaged by Debian, then recompiling compiling
it myself.  As I use several kernel modules I usually end up having to
either fix the Debian versions so they compile or package the newer
upstream versions.  Tedious, but no big issue - at least no bigger than
I would face if I didn't use Debian.

And so it went with 2.6.28 in experimental.  Except when it came to
compiling the modules.  I ran into linux-kbuild.  A brief look revealed
a version for 2.6.28 it wasn't available in debian/pool.  A longer look
at the 2.6.26 version revealed it didn't come from any upstream package,
but was somehow hand crafted from the kernel source.  At that point I
would have been stuffed, except somehow you guys let some version of
linux-kbuild 2.6.28 escape to the web and I was able to find it with
google.  Comparing the source to 2.6.26, I still am no wiser about how
you put it together.

And so to the my real request: please make the same mistake with 2.6.29.
The linux-2.6 source package is bloody near useless without the matching
linux-kbuild, so if you aren't going to release it at the same time as
you release your first version of 2.6.29, please please let it "escape",
preferably with big hints planted around the web so I can find it.

--
Regards,
Russell Stuart


-- 
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

[Stuart Chalmers]

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.

Possible packages affected:

hal 0.5.11-6
linux-image-2.6.26-1-686 2.6.26-8
libc6-i686 2.7-16

Snip from dmesg - connecting phone, selecting mass storage and then 
disconnecting.

[  504.224151] usb 3-6: new high speed USB device using ehci_hcd and address 2
[  504.920374] usb 3-6: configuration #2 chosen from 1 choice
[  504.924358] usb 3-6: New USB device found, idVendor=0fce, idProduct=e0da
[  504.924368] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  504.924372] usb 3-6: Product: Memory Stick
[  504.924374] usb 3-6: Manufacturer: Sony Ericsson
[  504.924377] usb 3-6: SerialNumber: 3553530229124830
[  505.063405] Initializing USB Mass Storage driver...
[  505.070561] scsi0 : SCSI emulation for USB Mass Storage devices
[  505.074078] usbcore: registered new interface driver usb-storage
[  505.074087] USB Mass Storage support registered.
[  505.115660] usb-storage: device found at 2
[  505.115671] usb-storage: waiting for device to settle before scanning
[  510.112411] usb-storage: device scan complete
[  510.113138] scsi 0:0:0:0: Direct-Access Sony Eri Memory Stick0 
PQ: 0 ANSI: 0
[  510.199960] Driver 'sd' needs updating - please use bus_type methods
[  510.202825] sd 0:0:0:0: [sda] 15520084 512-byte hardware sectors (7946 MB)
[  510.206261] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
[  510.206271] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  510.208369] sd 0:0:0:0: [sda] 15520084 512-byte hardware sectors (7946 MB)
[  510.209626] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
[  510.209634] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  510.209640]  sda: sda1
[  510.212601] sd 0:0:0:0: [sda] Attached SCSI removable disk
[  540.528018] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  570.780020] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  601.068022] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  631.336020] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  661.644021] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  691.912036] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  692.111295] sd 0:0:0:0: [sda] Result: hostbyte=DID_ABORT 
driverbyte=DRIVER_OK,SUGGEST_OK
[  692.111308] end_request: I/O error, dev sda, sector 15520064
[  692.111314] Buffer I/O error on device sda, logical block 3880016
[  722.224020] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  752.492036] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  782.796021] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  813.100020] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  843.400021] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  871.880071] INFO: task vol_id:4543 blocked for more than 120 seconds.
[  871.880080] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  871.880084] vol_idD d73b4dbf 0  4543  1
[  871.880089]f6a38dc0 0082 f6ba d73b4dbf 0076 f6a38f4c 
c180bfa0  
[  871.880097]f70403fc 0005d342 254c  0005d342 f70403fc 
0005d342 c1801a60 
[  871.880103]c180bfa0 01453000 c1801a60 c0157e7b c02b8040 f6b99e50 
f6b99e50 c0156729 
[  871.880110] Call Trace:
[  871.880149]  [] sync_page_killable+0x0/0x2a
[  871.880162]  [] io_schedule+0x49/0x80
[  871.880171]  [] sync_page+0x33/0x36
[  871.880176]  [] sync_page_killable+0x5/0x2a
[  871.880180]  [] __wait_on_bit_lock+0x2a/0x52
[  871.880188]  [] __lock_page_killable+0x51/0x57
[  871.880196]  [] wake_bit_function+0x0/0x3c
[  871.880205]  [] generic_file_aio_read+0x331/0x4da
[  871.880226]  [] do_sync_read+0xbf/0xfe
[  871.880244]  [] autoremove_wake_function+0x0/0x2d
[  871.880252]  [] vma_merge+0xd3/0x142
[  871.880267]  [] security_file_permission+0xc/0xd
[  871.880276]  [] do_sync_read+0x0/0xfe
[  871.880281]  [] vfs_read+0x81/0x11e
[  871.880288]  [] sys_read+0x3c/0x63
[  871.880296]  [] sysenter_past_esp+0x78/0xb1
[  871.880315]  ===
[  873.664033] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  873.817233] sd 0:0:0:0: [sda] Result: hostbyte=DID_ABORT 
driverbyte=DRIVER_OK,SUGGEST_OK
[  873.817242] end_request: I/O error, dev sda, sector 15520068
[  873.817248] Buffer I/O error on device sda, logical block 3880017
[  903.980050] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  934.248034] usb 3-6: reset high speed USB device using ehci_hcd and address 2
[  964.508018] usb 3-6: reset high 

Bug#483538: linux-image-2.6-686: debug kernel parameter

[Peter Stuart]

Package: linux-image-2.6-686
Version: 2.6.24+13
Severity: normal

debug kernel parameters is unusable. when i specified this parameters i got 
lesser debugging information.
the "Begin: Running /scripts/init-premount ..." lines are missing.

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

Kernel: Linux 2.6.24-1-686 (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 linux-image-2.6-686 depends on:
ii  linux-image-2.6.24-1-686  2.6.24-6   Linux 2.6.24 image on PPro/Celeron

linux-image-2.6-686 recommends no packages.

-- no debconf information



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

Bug#411150: linux-image-2.6.21-1-686 (2.6.21-4) hangs during boot on Sony Vaio PCG-Z600LEK

[Stuart Pook]

Hi

I have just installed linux-image-2.6.21-1-686 on my Sony Vaio 
PCG-Z600LEK and it hangs during boot.  The messages are


ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd9ae, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using PIC for interrupt routing
Clocksource tsc unstable (delta = -371656950 ns)

The last line is not constant.

Clocksource tsc unstable (delta = -371660248 ns)

2.6.20-1~experimental.1~snapshot.8305 worked fine but I have never 
gotten 2.6.21 to boot. I never tried any other versions of 2.6.20.


Should I create a new bug report?

Stuart


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

Bug#421019: scanimage works on 2.6.20-1-686

[Stuart Pook]

Libsane bug number 419197 is interesting here as scanimage does in fact 
work even with 2.6.20-1-686. Perhaps the problem is in libsane but 
upgrading libsane to 1.0.19~cvs20070421-1 has not corrected the problem.


% scanimage -L
device `plustek:libusb:004:003' is a Canon CanoScan N670U/N676U/LiDE20 
flatbed scanner


Stuart


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

Bug#421019: linux-image-2.6.20-1-686: USB scanner works with 2.6.18-4 but fails with 2.6.20-1

[Stuart Pook]

Package: linux-image-2.6.20-1-686
Version: 2.6.20-2
Severity: normal


My Canon USB scanner has been working fine for ages but does not work
with linux-image-2.6.20-1-686. xsane detects the scanner and when asked
to scan thinks that the scanner is working however the scanner does not
react and xsane retrieves a black image. I have checked using 2.6.18-4-686
that the scanner is working correctly.

lsusb says that my scanner is a:
04a9:220d Canon, Inc. CanoScan N670U/N676U/LiDE 20

I am using xsane 0.99+0.991-2, xsane-common 0.99+0.991-2, libsane
1.0.18-6

My scanner is connected to a USB2 PCI card via a USB1.1 powered hub.

-- Package-specific info:
** Version: Linux version 2.6.20-1-686 (Debian 2.6.20-2) ([EMAIL PROTECTED]) 
(gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Sun Apr 15 
21:03:57 UTC 2007

** Not tainted

** Kernel log:
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker
  http://www.scyld.com/network/ne2k-pci.html
piix4_smbus :00:07.3: Found :00:07.3 device
PIIX4: IDE controller at PCI slot :00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
usb 5-1: new full speed USB device using uhci_hcd and address 2
usb 5-1: not running at top speed; connect to a high speed hub
usb 5-1: configuration #1 chosen from 1 choice
hub 5-1:1.0: USB hub found
hub 5-1:1.0: 4 ports detected
hda: SAMSUNG SV0432A, ATA DISK drive
usb 5-2: new full speed USB device using uhci_hcd and address 3
usb 5-2: configuration #1 chosen from 1 choice
hdb: LITE-ON DVDRW SOHW-1693S, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: 8421840 sectors (4311 MB) w/482KiB Cache, CHS=8912/15/63, UDMA(33)
 hda: hda1 hda2 hda3
Probing IDE interface ide1...
usb 5-1.2: new low speed USB device using uhci_hcd and address 4
usb 5-1.2: configuration #1 chosen from 1 choice
input: USB Keyboard USB Keyboard as /class/input/input1
hdc: ASUS CD-S520/A, ATAPI CD/DVD-ROM drive
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: HCI USB driver ver 2.9
hdd: SAMSUNG CD-R/RW SW-216B Q001 20010913, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
ACPI: PCI Interrupt :00:11.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> 
IRQ 11
eth1: RealTek RTL-8029 found at 0xec00, IRQ 11, 00:40:05:E2:EA:E9.
hdb: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdc: ATAPI 52X CD-ROM drive, 128kB Cache, UDMA(33)
hdd: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache, DMA
drivers/usb/input/hid-core.c: usb_submit_urb(ctrl) failed
drivers/usb/input/hid-core.c: timeout initializing reports
input: USB Keyboard USB Keyboard as /class/input/input2
input: USB HID v1.10 Device [USB Keyboard USB Keyboard] on usb-:00:07.2-1.2
usb 5-1.4: new low speed USB device using uhci_hcd and address 5
usb 5-1.4: configuration #1 chosen from 1 choice
input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as 
/class/input/input3
input: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with 
IntelliEye(TM)] on usb-:00:07.2-1.4
usbcore: registered new interface driver snd-usb-audio
usbcore: registered new interface driver hci_usb
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [EMAIL PROTECTED]
spurious 8259A interrupt: IRQ7.
ReiserFS: dm-1: found reiserfs format "3.6" with standard journal
ReiserFS: dm-1: using ordered data mode
ReiserFS: dm-1: journal params: device dm-1, size 8192, journal first block 18, 
max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: dm-1: checking transaction log (dm-1)
ReiserFS: dm-1: Using r5 hash to sort names
ReiserFS: dm-0: found reiserfs format "3.6" with standard journal
ReiserFS: dm-0: using ordered data mode
ReiserFS: dm-0: journal params: device dm-0, size 8192, journal first block 18, 
max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: dm-0: checking transaction log (dm-0)
ReiserFS: dm-0: Using r5 hash to sort names
ReiserFS: dm-3: found reiserfs format "3.6" with standard journal
ReiserFS: dm-3: using ordered data mode
ReiserFS: dm-3: journal params: device dm-3, size 8192, journal first block 18, 
max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: dm-3: checking transaction log (dm-3)
ReiserFS: dm-3: Using r5 hash to sort names
Adding 385520k swap on /dev/hde1.  Priority:10 extents:1 across:385520k
Adding 3387384k swap on /dev/mapper/vg0-swap1.  Priority:10 extents:1 
across:3387384k
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (3071 buckets, 24568 max)
eth0: DSPCFG accepted after 0

Bug#411150: linux-image-2.6.18-4-686: hangs in ACPI during boot on Sony Vaio PCG-Z600LEK

[Stuart Pook]

On 16/02/07 19:00, dann frazier wrote:

 Can you try the latest trunk snapshot (2.6.20-based) and see if the
problem has gone away?


Hi Dann

The problem certainly seems to have gone away as my machine boots every 
time now.  Thanks.


I'm using linux-image-2.6.20-1-686 version 
2.6.20-1~experimental.1~snapshot.8305



Stuart


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

Bug#411150: linux-image-2.6.18-4-686: hangs in ACPI during boot on Sony Vaio PCG-Z600LEK

[Stuart Pook]

Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-10
Severity: important

All the versions of linux-image-2.6.18-*-686 that I have tried normally
hang when booting on my Sony Vaio PCG-Z600LEK. Last time I had to boot
4 times before the machine booted correctly. I have to poweroff between
each boot attempt.

linux-image-2.6.16-2-686 boots everytime.

The first time the boot hung after these lines:
PIIX4 devres I PIO at 0398-0399
PIIX4 devres J PIO at 0398-0399
ACPI: Embedded Controller [EC0] (gpe 9) interrupt mode
The second time it hung after:
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (:00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
The third time it hung after:
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init

When the machine booted correctly (on the 4th attempt) dmesg said

BIOS-provided physical RAM map:
 BIOS-e820:  - 0009f800 (usable)
 BIOS-e820: 0009f800 - 000a (reserved)
 BIOS-e820: 000e8400 - 0010 (reserved)
 BIOS-e820: 0010 - 03ff (usable)
 BIOS-e820: 03ff - 03fff800 (ACPI data)
 BIOS-e820: 03fff800 - 0400 (ACPI NVS)
 BIOS-e820: fff8 - 0001 (reserved)
0MB HIGHMEM available.
63MB LOWMEM available.
On node 0 totalpages: 16368
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 12272 pages, LIFO batch:1
DMI 2.1 present.
ACPI: RSDP (v000 SONY  ) @ 0x000f6bb0
ACPI: RSDT (v001 SONY   Z3   0x20001225 PTL  0x) @ 0x03ffc1ca
ACPI: FADT (v001 SONY   Z3   0x20001225 PTL  0x000f4240) @ 0x03fff764
ACPI: BOOT (v001 SONY   Z3   0x20001225 PTL  0x0001) @ 0x03fff7d8
ACPI: DSDT (v001   SONY  Z3  0x20001225 MSFT 0x0107) @ 0x
ACPI: PM-Timer IO Port: 0x8008
Allocating PCI resources starting at 1000 (gap: 0400:fbf8)
Detected 694.900 MHz processor.
Built 1 zonelists.  Total pages: 16368
Kernel command line: root=/dev/hda2 ro 
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to d000 (01089000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 57068k/65472k available (1544k kernel code, 7996k reserved, 577k data, 
196k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1390.86 BogoMIPS (lpj=2781723)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383f9ff     
 
CPU: After vendor identify, caps: 0383f9ff     
 
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU: After all inits, caps: 0383f9ff   0040  
 
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to e000.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 16k freed
ACPI: Core revision 20060707
CPU0: Intel Pentium III (Coppermine) stepping 06
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 4746k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd9ae, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region 8000-803f claimed by PIIX4 ACPI
PCI quirk: region 1040-104f claimed by PIIX4 SMB
PIIX4 devres I PIO at 0398-0399
PIIX4 devres J PIO at 0398-0399
PCI: Firmware left :00:0b.0 e100 interrupts enabled, disabling
Boot video device is :01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Embedded Controller [EC0] (gpe 9) interrupt mode.
ACPI: PCI Interrupt Link [LNKA] (IRQs *9)
ACPI: PCI Interrupt Link [LNKB] (IRQs 9) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 9) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 9) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 11 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
pnp: 00:01: ioport range 0x398-0x399 has been rese

Bug#352765: linux-2.6: wrong drivers for tulip PCI IDs on alpha?

[Stuart T. R. Rowan]

My old alphastation 200 4/166 needs de4x5 for the onboard ethernet. Last
time I did an install, I think discover tried to use de2104x which just
didn't work, it modprobed, found it but no traffic etc.

tulip didn't even find the ethernet chip at all iirc.

Bit hand wavy I know but de4x5 is reliable and works on at least this
hardware so please don't drop it. 

lscpi:
:00:06.0 SCSI storage controller: LSI Logic / Symbios Logic 53c810 (rev 02)
:00:07.0 Non-VGA unclassified device: Intel Corporation 82378ZB/IB, 82379AB 
(SIO, SIO.A) PCI to ISA Bridge (rev 03)
:00:0b.0 Ethernet controller: Digital Equipment Corporation DECchip 21040 
[Tulip] (rev 23)
:00:0d.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03)
:01:04.0 VGA compatible controller: 3DLabs Permedia II 2D+3D (rev 01)
:01:05.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 
100] (rev 05)
:01:06.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 
100] (rev 05)

:00:0d.0 0604: 1011:0024 (rev 03)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- Reset- FastB2B-
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI- D1- D2- AuxCurrent=220mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Bridge: PM- B3+

Thanks,
Stu.



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

Re: stable kernel 2.6.8-2-686

[Stuart T. R. Rowan]

On Wed, 2006-01-18 at 10:03 +, Stuart T. R. Rowan wrote:
> On Tue, 2006-01-17 at 16:23 -0700, dann frazier wrote:
> > On Mon, 2006-01-16 at 23:07 +0000, Stuart T. R. Rowan wrote:
> > > Hi,
> > > 
> > > The 3c59x kernel module doesn't work with vlan (802.1q) tagged packets.
> > > Apparently the fix was committed somewhere around 2.6.10, anyway we've
> > > upgraded our stable box to vanilla kernel 2.6.15.1 to work around this
> > > issue -- no discarded packets at all now.
> > > 
> > > If there's gonna be an update to the stable kernel, a patch to make the
> > > 3c59x module work with vlans rather than silently failing might be a
> > > plan.
> > 
> > hey Stu,
> >   got a link to the appropriate changeset(s)?
> > 
> > 
> Hey Dann,
> 
> Yes! So the vlan patch turned up in patch-2.6.9.bz2.
> The changeset is on 
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git
> 3c59x.c has a history list here in case this builds on other non 2.6.8 
> patches:
> http://tinyurl.com/b8a95 On this you will clearly see the below commit listed:
> Title: [PATCH] VLAN support for 3c59x/3c90x
> commit 03e4b71f751da25d7b2d026ba6f4f904116e51e5
> Body:
>  This adds VLAN support to the 3c59x/90x series hardware.
> 
>  Stefan de Konink ported this code from the 2.4 VLAN patches and tested it
>  extensively. I cleaned up the ifdefs and fixed a problem with bracketing
>  that made older cards fail.
> 
> I hope that helps?
> 
> Thanks,
> Stu.
> (please keep me CC'd)
kernel bugzilla for further reference and explanation:
http://bugzilla.kernel.org/show_bug.cgi?id=2991

Stu.



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

Re: stable kernel 2.6.8-2-686

[Stuart T. R. Rowan]

On Tue, 2006-01-17 at 16:23 -0700, dann frazier wrote:
> On Mon, 2006-01-16 at 23:07 +0000, Stuart T. R. Rowan wrote:
> > Hi,
> > 
> > The 3c59x kernel module doesn't work with vlan (802.1q) tagged packets.
> > Apparently the fix was committed somewhere around 2.6.10, anyway we've
> > upgraded our stable box to vanilla kernel 2.6.15.1 to work around this
> > issue -- no discarded packets at all now.
> > 
> > If there's gonna be an update to the stable kernel, a patch to make the
> > 3c59x module work with vlans rather than silently failing might be a
> > plan.
> 
> hey Stu,
>   got a link to the appropriate changeset(s)?
> 
> 
Hey Dann,

Yes! So the vlan patch turned up in patch-2.6.9.bz2.
The changeset is on 
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/old-2.6-bkcvs.git
3c59x.c has a history list here in case this builds on other non 2.6.8 patches:
http://tinyurl.com/b8a95 On this you will clearly see the below commit listed:
Title: [PATCH] VLAN support for 3c59x/3c90x
commit 03e4b71f751da25d7b2d026ba6f4f904116e51e5
Body:
 This adds VLAN support to the 3c59x/90x series hardware.

 Stefan de Konink ported this code from the 2.4 VLAN patches and tested it
 extensively. I cleaned up the ifdefs and fixed a problem with bracketing
 that made older cards fail.

I hope that helps?

Thanks,
Stu.
(please keep me CC'd)


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

stable kernel 2.6.8-2-686

[Stuart T. R. Rowan]

Hi,

The 3c59x kernel module doesn't work with vlan (802.1q) tagged packets.
Apparently the fix was committed somewhere around 2.6.10, anyway we've
upgraded our stable box to vanilla kernel 2.6.15.1 to work around this
issue -- no discarded packets at all now.

If there's gonna be an update to the stable kernel, a patch to make the
3c59x module work with vlans rather than silently failing might be a
plan.

Thanks,
Stu.
(I'm not subscribed so please CC me on any replies)



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

Bug#80878: fwd: one hour cas1no payout.

[Stuart]

Try your luck with our new brand cas1no. +30% for every diposit.
One hour payout, never fast before. Try play for free.
The shortest distance between two points is under construction. 
http://www.wehiuhef.com/ In Europe an actor is an artist. In Hollywood, if he 
isn't working, he's a bum. You can tell more about a person by what he says 
about others than you can by what others say about him.
to get out please read on page above I know of no more encouraging fact 
than the unquestionable ability of man to elevate his life by conscious 
endeavor. No great intellectual thing was ever done by great effort.


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

Bug#303926: kernel-image-2.6.11-1-686: Loads IDE Modules permanently

[Stuart Sheldon]

Package: kernel-image-2.6.11-1-686
Version: 2.6.11-2
Severity: normal


Not sure if this is a kernel bug or not... Would like to remove unused modules
if possable


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (900, 'testing'), (100, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages kernel-image-2.6.11-1-686 depends on:
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities
ii  initrd-tools  0.1.77 tools to create initrd image for p
ii  module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo

-- no debconf information


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

Bug#291464: kernel-source-2.6.10: Kernel Panic with SMP PIII as NFS Client under heavy NFS Load

[Stuart Sheldon]

Package: kernel-source-2.6.10
Version: 2.6.10-4
Severity: important



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

Versions of packages kernel-source-2.6.10 depends on:
ii  binutils  2.15-5 The GNU assembler, linker and bina
ii  bzip2 1.0.2-1A high-quality block-sorting file 
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities

-- no debconf information
System kernel is installed on displays following message on screen:
Kernel panic - not syncing: Attempting to free lock with active block list 

References found in this thread from linux-kernel list:
http://seclists.org/lists/linux-kernel/2005/Jan/1198.html

This bug report is being generated from our main build machine, not system
that was kernel panic'ing. Thread was not clear if this was resolved with
the patch listed, but problem still exists in unpatched kernel-source-2.6.10-4.

Please advise if I can be of any assistance.

Stu Sheldon


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

Bug#291357: A Better Example

[Russell Stuart]

It appears the example I gave happens on a working
kernel as well.  This one doesn't:

[EMAIL PROTECTED]:~$ ssh 10.7.0.3
Linux titan.brisbane.lube 2.4.27-6-lube-686-smp #1 SMP Thu Jan 13 
16:01:29 EST 2005 i686 GNU/Linux

[EMAIL PROTECTED]:~$ ps -fu $LOGNAME
UIDPID  PPID  C STIME TTY  TIME CMD
rstuart  15870 15868  0 23:33 ?00:00:00 sshd: [EMAIL 
PROTECTED]/0
rstuart  15872 15870  2 23:33 pts/000:00:00 -bash
rstuart  15895 15872  0 23:33 pts/000:00:00 ps -fu rstuart
[EMAIL PROTECTED]:~$ (sleep 2; kill -9 15870) & sleep 12345
[1] 15900
Connection to 10.7.0.3 closed by remote host.
Connection to 10.7.0.3 closed.
[EMAIL PROTECTED]:~$ ssh 10.7.0.3
Linux titan.brisbane.lube 2.4.27-6-lube-686-smp #1 SMP Thu Jan 13 
16:01:29 EST 2005 i686 GNU/Linux

[EMAIL PROTECTED]:~$ ps -fu $LOGNAME
UIDPID  PPID  C STIME TTY  TIME CMD
rstuart  15872 1  0 23:33 ?00:00:00 -bash
rstuart  15901 15872  0 23:33 ?00:00:00 sleep 12345
rstuart  15905 15903  0 23:33 ?00:00:00 sshd: [EMAIL 
PROTECTED]/2
rstuart  15907 15905  2 23:33 pts/200:00:00 -bash
rstuart  15932 15907  0 23:33 pts/200:00:00 ps -fu rstuart
[EMAIL PROTECTED]:~$

Notice the sleep is still running.  On a working kernel is isn't
because it has been sent a SIGHUP.

By the way, it appears the code concerned was copied from 2.6.8,
or a 2.6 kernel a least.  In 2.6.8, the code looks like this:

/* Defer ldisc switch */
/* tty_deferred_ldisc_switch(N_TTY);

  This should get done automatically when the port closes and
  tty_release is called */

read_lock(&tasklist_lock);

When copied to 2.4.27, the code ended up like this:

/* Defer ldisc switch */
/* tty_deferred_ldisc_switch(N_TTY);

read_lock(&tasklist_lock);

When the trailing */ is restored, the kernel works again.





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

Bug#291357: kernel-source-2.4.27: SIGHUP not being sent when controlling process exits

[Russell Stuart]

Package: kernel-source-2.4.27
Version: 2.4.27-6
Severity: important



-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-6-lube-686-smp
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)

Versions of packages kernel-source-2.4.27 depends on:
ii  binutils  2.15-5 The GNU assembler, linker and bina
ii  bzip2 1.0.2-1A high-quality block-sorting file 
ii  coreutils [fileutils] 5.2.1-2The GNU core utilities

-- no debconf information

drivers/char/tty_io.c, line 768, contains this line:

/* tty_deferred_ldisc_switch(N_TTY);

Note: no trailing "*/".  I am not sure what was intended here,
but the net result is to comment out the code that sends a
SIGHUP to child processed when their leader exits.

This is bad, real bad.  This means that after:

login: me
$ sleep 1000
$ exit

sleep still runs.  The errant patch is in
093_tty_lockup.diff.bz2.



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