Bug#547270: marked as done (linux-image-2.6.26-2-686: laptop does not power off after a 'halt')
Your message dated Tue, 2 Jul 2013 22:28:33 +0200 with message-id 20130702202833.GC4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #547270, regarding linux-image-2.6.26-2-686: laptop does not power off after a 'halt' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 547270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-686 Version: 2.6.26-19 Severity: normal hi, I just installed lenny on my laptop (NEC Versa P8210). When I do a halt, the machine goes through the usual shutdown procedure, but finishes with [ some numbers ] Power Off (or something like that, I can't remember exactly). But the machine does not power off. dmesg appears to show ACPI loaded OK. I tried booting with acpi=ht, and acpi=off, but the machine doesn't even boot (I can write down those messages for you if you need them). This is a dual core machine, with flgrx module loaded, and iwl3945 for wireless. I can give you more info if you need, but it looks like 'reportbug' has appended lots of stuff. Thanks very much Matt -- Package-specific info: ** Version: Linux version 2.6.26-2-686 (Debian 2.6.26-19) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Aug 19 06:06:52 UTC 2009 ** Command line: root=/dev/mapper/vg-root ro ** Tainted: P (1) ** Kernel log: [ 29.193571] [fglrx] Reserved FB block: Unshared offset:7ffb000, size:5000 [ 60.800700] CPU0 attaching NULL sched-domain. [ 60.800715] CPU1 attaching NULL sched-domain. [ 60.805541] CPU0 attaching sched-domain: [ 60.805550] domain 0: span 0-1 [ 60.80] groups: 0 1 [ 60.805563] CPU1 attaching sched-domain: [ 60.805567] domain 0: span 0-1 [ 60.805571] groups: 1 0 [ 188.413614] CE: hpet increasing min_delta_ns to 15000 nsec [ 211.204513] [fglrx] It's not necessary to adjust system aperture on this ASIC [ 301.148261] Clocksource tsc unstable (delta = -76081519 ns) [ 324.695803] [fglrx] It's not necessary to adjust system aperture on this ASIC [ 338.843181] CPU0 attaching NULL sched-domain. [ 338.843191] CPU1 attaching NULL sched-domain. [ 338.868356] CPU0 attaching sched-domain: [ 338.868365] domain 0: span 0-1 [ 338.868367] groups: 0 1 [ 338.868372] CPU1 attaching sched-domain: [ 338.868375] domain 0: span 0-1 [ 338.868377] groups: 1 0 [ 4774.061635] eth0: no IPv6 routers present [ 4853.202303] ACPI: PCI interrupt for device :03:00.0 disabled [ 4854.243973] ACPI: PCI Interrupt :03:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 4854.244155] PM: Writing back config space on device :03:00.0 at offset 1 (was 12, writing 16) [ 4854.291483] Registered led device: iwl-phy0:radio [ 4854.291568] Registered led device: iwl-phy0:assoc [ 4854.291602] Registered led device: iwl-phy0:RX [ 4854.291634] Registered led device: iwl-phy0:TX [ 4854.299045] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 4854.329345] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 4854.332157] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex [ 4854.332539] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 4868.401186] eth0: no IPv6 routers present [ 4910.092370] eth0: no IPv6 routers present [ 4984.440319] wlan0: Initial auth_alg=0 [ 4984.440319] wlan0: authenticate with AP 00:17:9a:1c:f0:6e [ 4984.442201] wlan0: RX authentication from 00:17:9a:1c:f0:6e (alg=0 transaction=2 status=0) [ 4984.442201] wlan0: authenticated [ 4984.442201] wlan0: associate with AP 00:17:9a:1c:f0:6e [ 4984.444299] wlan0: RX AssocResp from 00:17:9a:1c:f0:6e (capab=0x471 status=0 aid=1) [ 4984.444299] wlan0: associated [ 4984.444299] wlan0: switched to short barker preamble (BSSID=00:17:9a:1c:f0:6e) [ 4984.444299] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 4998.845390] wlan0: no IPv6 routers present [ 5019.050951] wlan0: deauthenticate(reason=3) [ 5020.067559] wlan0: deauthentication frame received from unknown AP (SA=00:17:9a:1c:f0:6e BSSID=00:17:9a:1c:f0:6e) - ignored [ 5020.067559] wlan0: deauthentication frame received from unknown AP (SA=00:17:9a:1c:f0:6e BSSID=00:17:9a:1c:f0:6e) - ignored [ 5020.067559] wlan0: No STA entry for own AP 00:00:00:00:00:00 [ 5020.279498] ACPI: PCI interrupt for device :03:00.0 disabled [ 5029.763581] ACPI: PCI Interrupt :03:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 5029.763746] PM: Writing back config space on device :03:00.0 at offset 1 (was 12, writing 16) [ 5029.807180] Registered led device: iwl-phy0:radio [
Bug#545449: marked as done (linux-image-2.6.26-2-686: Error inserting ebt_ulog: Cannot allocate memory)
Your message dated Tue, 2 Jul 2013 22:28:33 +0200
with message-id 20130702202833.GC4762@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #545449,
regarding linux-image-2.6.26-2-686: Error inserting ebt_ulog: Cannot allocate
memory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
545449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.26-2-686
Version: 2.6.26-17lenny2
Severity: normal
ebt_ulog kernel module fails to load with the following error:
mull:~# modprobe ebt_ulog
FATAL: Error inserting ebt_ulog
(/lib/modules/2.6.26-2-686/kernel/net/bridge/netfilter/ebt_ulog.ko): Cannot
allocate memory
I also tried with various values of the nlbufsiz parameter, down to 0, but with
no results
mull:~# strace modprobe ebt_ulog
...
fcntl64(3, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=1}) = 0
open(/proc/modules, O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f09000
read(4, ebtables 16480 0 - Live 0xf89a800..., 1024) = 1024
read(4, de_cd_mod,serverworks,ide_pci_gen..., 1024) = 614
read(4, ..., 1024)= 0
close(4)= 0
munmap(0xb7f09000, 4096)= 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=9209, ...}) = 0
mmap2(NULL, 9209, PROT_READ|PROT_WRITE, MAP_PRIVATE, 3, 0) = 0xb7f07000
init_module(0xb7f07000, 9209, ) = -1 ENOMEM (Cannot allocate memory)
write(2, FATAL: Error inserting ebt_ulog (..., 124FATAL: Error inserting
ebt_ulog
(/lib/modules/2.6.26-2-686/kernel/net/bridge/netfilter/ebt_ulog.ko): Cannot
allocate memory
) = 124
exit_group(1) = ?
same problem reported in
https://lists.linux-foundation.org/pipermail/bugme-new/2005-May/012248.html
context: I was trying to setup a netflow probe with fprobe-ulog, for traffic
port-mirrored by a switch, but mirrored traffic was not captured by
iptables as it was directed to a foreign mac address.
-- Package-specific info:
** Version:
Linux version 2.6.26-2-686 (Debian 2.6.26-17lenny2) (da...@debian.org) (gcc
version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Fri Aug 14
01:27:18 UTC 2009
** Command line:
root=/dev/sda1 ro
** Not tainted
** Kernel log:
[1.013472] SCSI subsystem initialized
[1.013472] ACPI: PCI Interrupt :08:02.0[A] - GSI 18 (level, low) -
IRQ 18
[1.097991] scsi0 : IBM PCI ServeRAID 7.12.05 Build 761 ServeRAID 5i
[1.101107] scsi 0:0:0:0: Direct-Access IBM SERVERAID1.00
PQ: 0 ANSI: 2
[1.101107] scsi 0:0:15:0: Processor IBM SERVERAID1.00
PQ: 0 ANSI: 2
[1.111618] scsi 0:1:8:0: Processor IBM 32P0032a S320 1 1
PQ: 0 ANSI: 2
[1.133644] ACPI: ACPI0007:00 is registered as cooling_device0
[1.133664] ACPI: ACPI0007:01 is registered as cooling_device1
[1.263911] Driver 'sd' needs updating - please use bus_type methods
[1.263911] sd 0:0:0:0: [sda] 71096320 512-byte hardware sectors (36401 MB)
[1.263911] sd 0:0:0:0: [sda] Assuming Write Enabled
[1.263911] sd 0:0:0:0: [sda] Assuming drive cache: write through
[1.263911] sd 0:0:0:0: [sda] 71096320 512-byte hardware sectors (36401 MB)
[1.263911] sd 0:0:0:0: [sda] Assuming Write Enabled
[1.263911] sd 0:0:0:0: [sda] Assuming drive cache: write through
[1.263911] sda: sda1 sda2 sda5 sda6 sda7 sda8 sda9
[1.319915] sd 0:0:0:0: [sda] Attached SCSI disk
[2.017909] PM: Starting manual resume from disk
[2.043236] kjournald starting. Commit interval 5 seconds
[2.045364] EXT3-fs: mounted filesystem with ordered data mode.
[3.312028] udevd version 125 started
[3.663200] sd 0:0:0:0: Attached scsi generic sg0 type 0
[3.663200] scsi 0:0:15:0: Attached scsi generic sg1 type 3
[3.663200] scsi 0:1:8:0: Attached scsi generic sg2 type 3
[4.288513] Linux agpgart interface v0.103
[4.516133] input: Power Button (FF) as /class/input/input1
[4.544138] Uniform Multi-Platform E-IDE driver
[4.544228] ide: Assuming 33MHz system bus speed for PIO modes; override
with idebus=xx
[4.590035] ACPI: Power Button (FF) [PWRF]
[4.600902] usbcore: registered new interface driver usbfs
[4.600902] usbcore: registered new interface driver hub
[4.600902] usbcore: registered new device driver usb
[4.676428] piix4_smbus :00:0f.0: Found :00:0f.0 device
[4.688071] ohci_hcd: 2006 August 04 USB 1.1
Bug#549185: marked as done (libftdi1: ftdi_sio disconnects FT232RL after bitbanging)
Your message dated Tue, 2 Jul 2013 22:28:50 +0200 with message-id 20130702202849.GD4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #549185, regarding libftdi1: ftdi_sio disconnects FT232RL after bitbanging to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 549185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libftdi1 Version: 0.13-2 Severity: normal 1. Hooked the FT232RL to USB [ 1038.709289] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected [ 1038.709396] ftdi_sio: Detected FT232RL [ 1038.709509] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0 [ 1038.714366] usb 1-1: New USB device found, idVendor=0403, idProduct=6001 [ 1038.714443] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1038.714505] usb 1-1: Product: FT245R USB FIFO [ 1038.714560] usb 1-1: Manufacturer: FTDI [ 1038.714615] usb 1-1: SerialNumber: A6005qyc 2. sudo apt-get install libftdi-dev 3. gcc -lftdi -o /usr/share/doc/libftdi-dev/examples/bitbang2 /usr/share/doc/libftdi-dev/examples/bitbang2.c 4. /usr/share/doc/libftdi-dev/examples/bitbang2 -d 1 0x00 5. It works, but this appears in dmesg [ 1046.425463] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 1046.425567] ftdi_sio 1-1:1.0: device disconnected 6. /usr/share/doc/libftdi-dev/examples/bitbang2 -d 1 0xff 7. Doesn't work anymore :( -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-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 libftdi1 depends on: ii libc62.7-18 GNU C Library: Shared libraries ii libusb-0.1-4 2:0.1.12-13 userspace USB programming library libftdi1 recommends no packages. libftdi1 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz---End Message---
Bug#546147: marked as done (linux-image-2.6.26-2-686: System unstable after hung task with IO operations on a NCP file system)
Your message dated Tue, 2 Jul 2013 22:28:33 +0200 with message-id 20130702202833.GC4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #546147, regarding linux-image-2.6.26-2-686: System unstable after hung task with IO operations on a NCP file system to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 546147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-686 Version: 2.6.26-19 Severity: critical Justification: causes serious data loss Like #517449 bug, but with IO on a ncpfs. This bug increase load average (sendmail stopped etc). -- Package-specific info: ** Version: Linux version 2.6.26-2-686 (Debian 2.6.26-17lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Fri Aug 14 01:27:18 UTC 2009 ** Command line: root=/dev/md0 ro quiet hpet=disable ** Tainted: P (1) ** Kernel log: [1192888.515224] [c017c5cb] __link_path_walk+0xaf6/0xb0d [1192888.515239] [c018fcf2] __find_get_block_slow+0xdd/0xe6 [1192888.515253] [c0190061] __find_get_block+0x176/0x180 [1192888.515266] [c015accf] get_page_from_freelist+0xc1/0x3e3 [1192888.515287] [e0910170] __journal_file_buffer+0xa2/0x123 [jbd] [1192888.515308] [e0b5e9e4] ncp_compare_dentry+0x0/0x8d [ncpfs] [1192888.515323] [c0182dcf] __d_lookup+0x7d/0xd7 [1192888.515339] [c017a665] do_lookup+0x114/0x153 [1192888.515353] [c017bd99] __link_path_walk+0x2c4/0xb0d [1192888.515382] [c017c619] path_walk+0x37/0x70 [1192888.515395] [c017c8c8] do_path_lookup+0x122/0x184 [1192888.515408] [c017d125] __user_walk_fd+0x29/0x3a [1192888.515421] [c017d266] __user_walk+0xf/0x11 [1192888.515429] [c0173b69] sys_chdir+0x15/0x4f [1192888.515444] [c0115b67] do_page_fault+0x29b/0x5b8 [1192888.515457] [c0172b8d] filp_close+0x4d/0x53 [1192888.515470] [c0103853] sysenter_past_esp+0x78/0xb1 [1192888.515487] [c02b] aer_probe+0x85/0xff [1192888.515501] === [1192890.660071] INFO: task rsync:5706 blocked for more than 120 seconds. [1192890.660083] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [1192890.660089] rsync D 3d72aa8b 0 5706 1 [1192890.660098]df137540 0082 c0129b82 3d72aa8b 00042037 df1376cc c1409fa0 [1192890.660111]c0131a9a df78fbf4 0018b170 c017ec3e df78fbf4 c017ec5e 0001 [1192890.660124]d5397578 d5397580 d539757c df137540 c02b8a3c de9e5b9c def13b9c df137540 [1192890.660136] Call Trace: [1192890.660161] [c0129b82] del_timer_sync+0xa/0x14 [1192890.660186] [c0131a9a] remove_wait_queue+0xc/0x34 [1192890.660206] [c017ec3e] free_poll_entry+0xe/0x16 [1192890.660219] [c017ec5e] poll_freewait+0x18/0x4c [1192890.660231] [c02b8a3c] __mutex_lock_slowpath+0x50/0x7b [1192890.660257] [c02b88d2] mutex_lock+0xa/0xb [1192890.660265] [e0b635a7] ncp_lock_server+0xe/0x2e [ncpfs] [1192890.660295] [e0b623c1] ncp_get_volume_root+0x13/0x192 [ncpfs] [1192890.660314] [e0b62a60] ncp_lookup_volume+0x2c/0x8b [ncpfs] [1192890.660334] [e0b5e568] ncp_lookup_validate+0xdb/0x193 [ncpfs] [1192890.660437] [c0182dea] __d_lookup+0x98/0xd7 [1192890.660456] [c017a5a4] do_lookup+0x53/0x153 [1192890.660463] [c01dcf26] _atomic_dec_and_lock+0x2a/0x44 [1192890.660476] [c0186a74] mntput_no_expire+0x13/0xd9 [1192890.660492] [c017c5cb] __link_path_walk+0xaf6/0xb0d [1192890.660508] [c018fcf2] __find_get_block_slow+0xdd/0xe6 [1192890.660524] [c0190061] __find_get_block+0x176/0x180 [1192890.660537] [c015accf] get_page_from_freelist+0xc1/0x3e3 [1192890.660559] [e0910170] __journal_file_buffer+0xa2/0x123 [jbd] [1192890.660598] [e0b5e9e4] ncp_compare_dentry+0x0/0x8d [ncpfs] [1192890.660613] [c0182dcf] __d_lookup+0x7d/0xd7 [1192890.660629] [c017a665] do_lookup+0x114/0x153 [1192890.660644] [c017bd99] __link_path_walk+0x2c4/0xb0d [1192890.660672] [c017c619] path_walk+0x37/0x70 [1192890.660686] [c017c8c8] do_path_lookup+0x122/0x184 [1192890.660699] [c017d125] __user_walk_fd+0x29/0x3a [1192890.660712] [c017d266] __user_walk+0xf/0x11 [1192890.660719] [c0173b69] sys_chdir+0x15/0x4f [1192890.660737] [c0115b67] do_page_fault+0x29b/0x5b8 [1192890.660754] [c0172b8d] filp_close+0x4d/0x53 [1192890.660767] [c0103853] sysenter_past_esp+0x78/0xb1 [1192890.660787] [c02b] aer_probe+0x85/0xff [1192890.660803] === [1192890.660836] INFO: task rsync:4446 blocked for more than 120 seconds. [1192890.660842] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message.
Bug#603673: marked as done (RTL8111/8168B problems)
Your message dated Tue, 2 Jul 2013 22:28:50 +0200 with message-id 20130702202849.GD4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #558316, regarding RTL8111/8168B problems to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 558316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: netinstaller CD Image version: http://cdimage.debian.org/cdimage/squeeze_di_beta1/amd64/iso-cd/debian-squeeze-di-beta1-amd64-netinst.iso Date: 15-11-2010 Machine: Custom machine with Asus M4A88T-M mainboard Processor: AMD Athlon II X2 250 3.0 Ghz. Memory: 2 GB PC3 Kingston unbuffered ECC ( KVR1333D3E9S/2G ) Partitions: no partitons (problem was before partitioning) Output of lspci -knn (or lspci -nn): - 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS780 Host Bridge Alternate [1022:9601] Subsystem: ASUSTeK Computer Inc. Device [1043:843e] 00:01.0 PCI bridge [0604]: ASUSTeK Computer Inc. RS880 PCI to PCI bridge (int gfx) [1043:9602] 00:0a.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 5) [1022:9609] Kernel driver in use: pcieport 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [IDE mode] [1002:4390] Subsystem: ASUSTeK Computer Inc. M4A785TD Motherboard [1043:8389] Kernel driver in use: ahci 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Subsystem: ASUSTeK Computer Inc. Device [1043:8389] Kernel driver in use: ohci_hcd 00:12.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 Controller [1002:4398] Subsystem: ASUSTeK Computer Inc. Device [1043:8389] Kernel driver in use: ohci_hcd 00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] Subsystem: ASUSTeK Computer Inc. Device [1043:8389] Kernel driver in use: ehci_hcd 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] Subsystem: ASUSTeK Computer Inc. Device [1043:8389] Kernel driver in use: ohci_hcd 00:13.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 Controller [1002:4398] Subsystem: ASUSTeK Computer Inc. Device [1043:8389] Kernel driver in use: ohci_hcd 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] Subsystem: ASUSTeK Computer Inc. Device [1043:8389] Kernel driver in use: ehci_hcd 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 3c) Subsystem: ASUSTeK Computer Inc. M4A785TD Motherboard [1043:8389] 00:14.1 IDE interface [0101]: ATI Technologies Inc SB700/SB800 IDE Controller [1002:439c] Subsystem: ASUSTeK Computer Inc. Device [1043:8389] Kernel driver in use: pata_atiixp 00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M4A785TD Motherboard [1043:836c] Kernel driver in use: HDA Intel 00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] Subsystem: ASUSTeK Computer Inc. Device [1043:8389] 00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] 00:14.5 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller [1002:4399] Subsystem: ASUSTeK Computer Inc. Device [1043:8389] Kernel driver in use: ohci_hcd 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration [1022:1200] 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Address Map [1022:1201] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller [1022:1202] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control [1022:1203] 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Link Control [1022:1204] 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS880 [Radeon HD 4250] [1002:9715] Subsystem: ASUSTeK Computer Inc. Device [1043:843e] Kernel driver in use: radeon 01:05.1 Audio device [0403]: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200] [1002:970f] Subsystem: ASUSTeK Computer Inc. Device [1043:843e] Kernel driver in use: HDA Intel 02:00.0 Ethernet controller [0200]:
Bug#547181: marked as done (linux-image-2.6.30: SD card: wrong size detected)
Your message dated Tue, 2 Jul 2013 22:28:33 +0200 with message-id 20130702202833.GC4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #547181, regarding linux-image-2.6.30: SD card: wrong size detected to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 547181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.30-1-686 Version: 2.6.30-6 Severity: normal File: linux-image-2.6.30 My laptop has an internal SD card reader; if I insert there a 2GB SD card, it correctly gets mounted and recognized as such: 1) HAL mounts it: Sep 17 21:44:09 utumno hald: mounted /dev/mmcblk0p1 on behalf of uid 1000 2) an icon saying '2.0 GB Media' appears on the desktop 3) reading , writing to the device fully works. 4) 'cfdisk /dev/mmcblk0p1' reports it as a 2GB device: Disk Drive: /dev/mmcblk0p1 Size: 2002189824 bytes, 2002 MB Heads: 4 Sectors per Track: 16 Cylinders: 61101 However, if I first put the card in an external USB multi-card reader (which contains 4 LUNs: a SD/MMC, Memory Stick, SMC and a CF/MD) and then connect the Card Reader to the very same laptop, the SD card gets recognized as having size of only 1GB !! : 1) HAL mounts it: Sep 17 21:51:28 utumno hald: mounted /dev/sde1 on behalf of uid 1000 2) An icon saying '1.0 GB Media' (sic!) appears on the desktop. 3) (there's about 1.3 GB worth of stuff in the card ) reading most of the files works, but reading others results in Sep 17 21:51:29 utumno kernel: [ 6004.825176] sde1: rw=0, want=2798654, limit=1955199 Sep 17 21:51:29 utumno kernel: [ 6004.825186] attempt to access beyond end of device Writing always fails. 4) 'cfdisk /dev/sde1' prints Disk Drive: /dev/sde1 Size: 1001061888 bytes, 1001 MB Heads: 31 Sectors per Track: 62 Cylinders: 1017 The very same card and card reader used to work with some previous kernel, although last time I was using it was some 1 year ago... -- Package-specific info: ** Version: Linux version 2.6.30-1-686 (Debian 2.6.30-6) (wa...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-1) ) #1 SMP Sat Aug 15 19:11:58 UTC 2009 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.30-1-686 root=UUID=86daebf1-6bcc-4e26-9234-fdbd75874ee1 ro quiet ** Not tainted ** Kernel log: [ 5022.535055] FAT: Directory bread(block 2798624) failed [ 5022.535061] attempt to access beyond end of device [ 5022.535067] sde1: rw=0, want=2798626, limit=1955199 [ 5022.535072] FAT: Directory bread(block 2798625) failed [ 5022.535077] attempt to access beyond end of device [ 5022.535083] sde1: rw=0, want=2798627, limit=1955199 [ 5022.535088] FAT: Directory bread(block 2798626) failed [ 5022.535093] attempt to access beyond end of device [ 5022.535099] sde1: rw=0, want=2798628, limit=1955199 [ 5022.535104] FAT: Directory bread(block 2798627) failed [ 5022.535110] attempt to access beyond end of device [ 5022.535116] sde1: rw=0, want=2798629, limit=1955199 [ 5022.535121] FAT: Directory bread(block 2798628) failed [ 5022.535126] attempt to access beyond end of device [ 5022.535132] sde1: rw=0, want=2798630, limit=1955199 [ 5022.535137] FAT: Directory bread(block 2798629) failed [ 5022.535143] attempt to access beyond end of device [ 5022.535150] sde1: rw=0, want=2798631, limit=1955199 [ 5022.535155] FAT: Directory bread(block 2798630) failed [ 5022.535160] attempt to access beyond end of device [ 5022.535166] sde1: rw=0, want=2798632, limit=1955199 [ 5022.535171] FAT: Directory bread(block 2798631) failed [ 5022.535177] attempt to access beyond end of device [ 5022.535183] sde1: rw=0, want=2798633, limit=1955199 [ 5022.535188] FAT: Directory bread(block 2798632) failed [ 5022.535193] attempt to access beyond end of device [ 5022.535199] sde1: rw=0, want=2798634, limit=1955199 [ 5022.535204] FAT: Directory bread(block 2798633) failed [ 5022.535210] attempt to access beyond end of device [ 5022.535216] sde1: rw=0, want=2798635, limit=1955199 [ 5022.535221] FAT: Directory bread(block 2798634) failed [ 5022.535226] attempt to access beyond end of device [ 5022.535232] sde1: rw=0, want=2798636, limit=1955199 [ 5022.535237] FAT: Directory bread(block 2798635) failed [ 5022.535242] attempt to access beyond end of device [ 5022.535248] sde1: rw=0, want=2798637, limit=1955199 [ 5022.535253] FAT: Directory bread(block 2798636) failed [ 5022.535259] attempt to access beyond end of device [ 5022.535265] sde1: rw=0, want=2798638, limit=1955199 [ 5022.535270] FAT: Directory bread(block 2798637) failed [ 5022.535276] attempt to access beyond end
Bug#560425: marked as done (grub 0.97 doesn't work well on Panasonic CF-L2)
Your message dated Tue, 2 Jul 2013 22:28:50 +0200 with message-id 20130702202849.GD4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #560425, regarding grub 0.97 doesn't work well on Panasonic CF-L2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 560425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: grub Version: 0.97-47lenny2 Hello, I installed Debian Lenny from debian-503-i386-CD-1.iso to three PCs. PCs are Panasonic CF-L2P8W2S(PhoenixBIOS V2.00L11B). Two PCs is installed grub, they hang up when they boot. But one PC is installed lilo, it can boot. The details of hang up is here. quitet kernel option Booting 'Debian GNU/Linux, kernel 2.6.26-2-686' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/vmlinuz-2.6.26-2-686 root=/dev/hda1 ro quiet [Linux-bzImage, setup=0x3000, size=0x16c8f0] initrd /boot/initrd.img-2.6.26-2-686 [Linux-initrd @ 0xf8f9000, 0x5e6042 bytes ] no quitet kernel option Booting 'Debian GNU/Linux, kernel 2.6.26-2-686' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/vmlinuz-2.6.26-2-686 root=/dev/hda1 ro [Linux-bzImage, setup=0x3000, size=0x16c8f0] initrd /boot/initrd.img-2.6.26-2-686 [Linux-initrd @ 0xf8f9000, 0x5e6042 bytes ] Probing EDD (edd=off to disable)... ok noacpi and no quitet kernel option same. acpi=force and no quitet kernel option same. edd=off and no quitet kernel option same. And my trial and error is here. No CD-ROM Drive : NG No AC-adapter : NG With AC-adapter and No Battely : NG BIOS(Legacy USB=OFF) : NG BIOS(Flatpad=OFF) : NG BIOS(Speaker=OFF) : NG BIOS(Device Configuration=BIOS) : NG BIOS(Device Configuration=OS) : NG BIOS(Serial Port=OFF) : NG BIOS(Parallel Port=OFF) : NG BIOS(Boot Password=ON) : NG BIOS(Boot Password=OFF) : NG BIOS(Proccessor Serial Number =OFF) : NG BIOS(Proccessor Serial Number =ON) : NG Booting Windows 2000 Proffefional with ntloader : OK Booting Windows XP Proffefional with ntloader : OK Booting Caldera Dos : OK Booting Debian Installer with pxelinux.0 : OK Booting Debian Installer with isolinux : Probabry OK Booting Debian with lilo : OK And my noticed point is here. When I see grub screen, PC's system fan begins to rotates heavily. Thanks for your reading my cheap English. Regards, //Youhei Sakurai ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz---End Message---
Bug#610561: marked as done (installation-reports: r8196 based network card does not work with stock installer kernel)
Your message dated Tue, 2 Jul 2013 22:28:50 +0200 with message-id 20130702202849.GD4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #558316, regarding installation-reports: r8196 based network card does not work with stock installer kernel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 558316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: normal -- Package-specific info: Boot method: netinst .iso on usb stick Image version: debian-sq-di-rc1-amd64-netinst.iso Date: 19. Jan 2011 Machine: HP Pavilion dv6 Partitions: -- Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [E] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: This notebook (unfortunately) has a r8196 based network card, which requires non-free firmware. the stock installer-image asks for this firmware (rtl8168d-2.fw). i found this firmware and put it on the usb-stick. after that the installer does not ask for the firmware anymore, and dmesg shows that it has loaded the firmware and actually started the driver (link up etc). however dhcp config over the network fails, as does anything else. after tips from #debian-boot i replaced the r8169.ko that the installer loads with the one from linux-image-2.6.32-5-amd64_2.6.32-30_amd64.deb, which makes the installer work and configure the network correctly. so it seems that version of the driver is better than the older one... any questions or anything i shoudl try: holler regards robert ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz---End Message---
Bug#555531: marked as done (linux-image-2.6.26-2-amd64: sound not working in OSS games after update)
Your message dated Tue, 2 Jul 2013 22:28:33 +0200 with message-id 20130702202833.GC4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #31, regarding linux-image-2.6.26-2-amd64: sound not working in OSS games after update to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 31: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=31 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-19lenny2 Severity: normal After the latest kernel update, sound no longer works in tyr-quake or other id engine games. I have 'tyr-quake 0 0 disable direct' in /proc/asound/card0/pcm0p/oss. It was working the day before I updated. brandon@brandon-desktop:~$ tyr-quake Added packfile /home/brandon/.tyrquake/id1/pak0.pak (339 files) Added packfile /home/brandon/.tyrquake/id1/pak1.pak (85 files) Playing registered version. Console initialized. UDP, Local address: 127.0.1.1 UDP Initialized (127.0.1.1) Exe: 21:53:41 Nov 5 2009 8.0 megabyte heap Using XFree86-VidModeExtension Version 2.2 600k surface cache VID: shared memory id=589840, addr=0xf73ff000 VID: shared memory id=622609, addr=0xf73c Sound Initialization GETOSPACE: Invalid argument Um, can't do GETOSPACE? S_Startup: SNDDMA_Init failed. CD Audio Initialized CDAudio_Init: No CD in player. Callback: in_dgamouse ON Callback: _windowed_mouse OFF 3 demo(s) in loop Playing demo from demo1.dem. Quake Initialized= TyrQuake -- Version 0.61 -- Package-specific info: ** Version: Linux version 2.6.26-2-amd64 (Debian 2.6.26-19lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 21:38:07 UTC 2009 ** Command line: root=/dev/md1 ro quiet ** Tainted: P (1) ** Kernel log: [ 11.587012] ivtv: Start initialization, version 1.3.0 [ 11.587112] ivtv0: Initializing card #0 [ 11.587115] ivtv0: Autodetected Hauppauge card (cx23416 based) [ 11.587403] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18 [ 11.587411] ACPI: PCI Interrupt :05:08.0[A] - Link [APC3] - GSI 18 (level, low) - IRQ 18 [ 11.587419] ivtv0: Unreasonably low latency timer, setting to 64 (was 32) [ 11.639406] tveeprom 2-0050: Hauppauge model 26132, rev F0B2, serial# 9399668 [ 11.639409] tveeprom 2-0050: tuner model is TCL M2523_5N_E (idx 112, type 50) [ 11.639412] tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08) [ 11.639414] tveeprom 2-0050: audio processor is CX25841 (idx 35) [ 11.639416] tveeprom 2-0050: decoder processor is CX25841 (idx 28) [ 11.639419] tveeprom 2-0050: has no radio, has IR receiver, has IR transmitter [ 11.639421] ivtv0: Autodetected Hauppauge WinTV PVR-150 [ 11.639423] ivtv0: Reopen i2c bus for IR-blaster support [ 11.730777] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 22 [ 11.730781] ACPI: PCI Interrupt :00:04.0[A] - Link [APCJ] - GSI 22 (level, low) - IRQ 22 [ 11.730801] PCI: Setting latency timer of device :00:04.0 to 64 [ 11.930189] cx25840 2-0044: cx25841-24 found @ 0x88 (ivtv i2c driver #0) [ 11.939249] tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) [ 11.939270] wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0) [ 12.048024] input: PC Speaker as /class/input/input5 [ 12.052023] intel8x0_measure_ac97_clock: measured 54691 usecs [ 12.052026] intel8x0: clocking to 46878 [ 12.113405] tuner-simple 2-0061: creating new instance [ 12.113409] tuner-simple 2-0061: type set to 50 (TCL 2002N) [ 12.114714] ivtv0: Registered device video0 for encoder MPG (4096 kB) [ 12.114731] ivtv0: Registered device video32 for encoder YUV (2048 kB) [ 12.114748] ivtv0: Registered device vbi0 for encoder VBI (1024 kB) [ 12.114764] ivtv0: Registered device video24 for encoder PCM (320 kB) [ 12.114767] ivtv0: Initialized card #0: Hauppauge WinTV PVR-150 [ 12.114869] ivtv: End initialization [ 12.321773] pnp: the driver 'parport_pc' has been registered [ 12.321790] parport_pc 00:09: reported by Plug and Play ACPI [ 12.321838] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 12.362087] pnp: the driver 'mpu401' has been registered [ 12.386907] pnp: the driver 'ns558' has been registered [ 12.416083] parport_pc 00:09: driver attached [ 12.416901] mpu401 00:0b: driver attached [ 12.416922] ns558 00:0c: driver attached [ 12.443349] gameport: NS558 PnP Gameport is pnp00:0c/gameport0, io 0x201, speed 926kHz [ 13.462036] Adding 979956k swap on /dev/sda2. Priority:-1 extents:1 across:979956k [ 13.480001] Adding 979956k swap on
Bug#676453: marked as done (linux-image-3.2.0-2-amd64: pmount hangs while mounting an external USB disk partition)
Your message dated Tue, 2 Jul 2013 22:27:39 +0200
with message-id 20130702202738.GA4762@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #676453,
regarding linux-image-3.2.0-2-amd64: pmount hangs while mounting an external
USB disk partition
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
676453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.2.19-1
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
I tried to mount a partition on an external USB drive using pmount
/dev/sdb1 backups.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I can CTR-C the pmount, but it leave a mount process which looks like
it is spinning in the kernel. I cannot kill the mount process (even
with kill -9). I need to reboot to recover. Any process that does a
sync end up in D state but with no WCHAN listed, so, in particular,
the shutdown does not finish correctly.
ps -axlw shows:
4 0 8021 1 20 0 4168 772 - Rpts/6 49:41 /bin/mount
-t udf -o
nosuid,nodev,user,async,atime,noexec,uid=1000,gid=1000,umask=000,iocharset=utf8
/dev/mapper/_dev_sdb1 /media/backups
0 1000 9205 10570 20 0 3332 252 - Dpts/2 0:00 sync
so mount is trying to mount the partiation as a udf file system (it is
ext4) (this is a LUKS encrypted file system).
After rebooting I can mount the partition using pmount -t ext4 /dev/sdb1
backups.
* What was the outcome of this action?
See above.
* What outcome did you expect instead?
The partition to be mounted under /media/backups. This seemed to start
after I upgraded to this version of the kernel from version 3.2.18-1.
Other things may have changed around the same time, though.
*** End of the template - remove these lines ***
-- Package-specific info:
** Version:
Linux version 3.2.0-2-amd64 (Debian 3.2.19-1) (debian-kernel@lists.debian.org)
(gcc version 4.6.3 (Debian 4.6.3-7) ) #1 SMP Fri Jun 1 19:39:45 UTC 2012
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64
root=UUID=81315ca5-5c28-4aaf-a450-b08fa9306852 ro selinux=1 security=selinux
quiet nouveau.noaccel=1
** Tainted: PO (4097)
* Proprietary module has been loaded.
* Out-of-tree module has been loaded.
** Kernel log:
[100878.001494] e1000e :00:19.0: irq 46 for MSI/MSI-X
[100878.057351] e1000e :00:19.0: irq 46 for MSI/MSI-X
[100878.058290] ADDRCONF(NETDEV_UP): eth0: link is not ready
[100878.492800] e1000e :00:19.0: irq 46 for MSI/MSI-X
[100878.548616] e1000e :00:19.0: irq 46 for MSI/MSI-X
[100878.549237] ADDRCONF(NETDEV_UP): eth0: link is not ready
[100881.132723] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: None
[100881.133508] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[100885.020450] martian source 255.255.255.255 from 10.61.254.103, on dev eth0
[100885.020456] ll header: ff:ff:ff:ff:ff:ff:00:21:5e:bf:57:7c:08:00
[100891.288774] eth0: no IPv6 routers present
[100974.526489] type=1400 audit(1339027109.771:29): avc: denied { execmod }
for pid=940 comm=notes.bin path=/opt/ibm/lotus/notes/libnotesgtkfix.so
dev=sda1 ino=661126 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=system_u:object_r:file_t:s0 tclass=file
[100975.602479] type=1400 audit(1339027110.851:30): avc: denied { execstack }
for pid=960 comm=notes2
scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tclass=process
[102103.057524] type=1400 audit(1339028239.355:31): avc: denied { execmod }
for pid=26384 comm=plugin-containe
path=/usr/lib/flashplugin-nonfree/libflashplayer.so dev=sda1 ino=135390
scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:tmp_t:s0 tclass=file
[113210.419345] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[113210.439411] xhci_hcd :0f:00.0: WARN: short transfer on control ep
[113210.440030] xhci_hcd :0f:00.0: WARN: short transfer on control ep
[113210.440655] xhci_hcd :0f:00.0: WARN: short transfer on control ep
[113210.441283] xhci_hcd :0f:00.0: WARN: short transfer on control ep
[113210.441540] usb 2-1: New USB device found, idVendor=059f, idProduct=1051
[113210.441543] usb 2-1: New USB device strings: Mfr=2, Product=3,
SerialNumber=1
[113210.441545] usb 2-1: Product: Rugged Mini USB 3
[113210.441547] usb 2-1: Manufacturer: LaCie
Bug#609388: marked as done (Unsuccessful installation with squeeze beta2 installer and Realtek RTL8111DL)
Your message dated Tue, 2 Jul 2013 22:28:50 +0200 with message-id 20130702202849.GD4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #558316, regarding Unsuccessful installation with squeeze beta2 installer and Realtek RTL8111DL to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 558316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/squeeze_di_beta2/amd64/iso-cd/debian-squee ze-di-beta2-amd64-businesscard.iso http://cdimage.debian.org/cdimage/squeeze_di_beta2/amd64/iso-cd/debian-squee ze-di-beta2-amd64-netinst.iso Date: 2011-01-08 22:00 Machine: MSI 890GXM-G65 Processor: AMD Phenom II X6 1075T Memory: 8GB DDR3-1333 Partitions: Networking: Realtek RTL8111DL (integrated, wired) Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Both of the above mentioned disks successfully boot and the installer progresses until it presents an error requesting that rtl8168d-1.fw and rtl8168d-2.fw be provided via removable media. Neither files exist in firmware-nonfree_0.27.tar.gz (squeeze / testing) and the files in firmware-nonfree_0.28.tar.gz (sid / unstable) pacify the installer, but do not result in a functional network card, causing the installer to throw errors when DHPC configuration is attempted. Both the network card and the cabling are known good. I have been booting live CDs for various other distros for the past week and successfully surfing the web. SDC ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz---End Message---
Bug#558316: marked as done (netinstall fails with a Realtek RTL8169 Gigabit Ethernet card)
Your message dated Tue, 2 Jul 2013 22:28:50 +0200 with message-id 20130702202849.GD4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #558316, regarding netinstall fails with a Realtek RTL8169 Gigabit Ethernet card to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 558316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: netinstall Version: sorry, don't know how to obtain that info, see below for the package reference and date. Hardware: Intel D945GSEJT, Atom processor N270 @1.60Ghz, 1GB DDR2 Technical specs: http://downloadmirror.intel.com/17597/eng/D945GSEJT_TechProdSpec.pdf Software: Debian netinstall dated 05-09-09 04:25, downloaded from http://ftp.nl.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/ Linux kernel: 2.6.26-2-486 #1 Wed Aug 19 05:40:02 UTC 2009 Issue: While starting up a network installation off the latest Debian netinstall image, the installer subsystem is unable to retrieve an address from the DHCP server, and the installation fails. It appears that the kernel is unable to send a single network packet over the Realtek ethernet link: I've run a WireShark session on the DHCP server machine, and not a single IP packet is emitted from the to-be-installed system, once the initial PXE boot up sequence as completed. The hardware link and the DHCP server are ok, as the board (PXE BIOS) has successfully been able to boot the pxelinux.0 then the kernel image from the very same hardware/software installation. It looks like the problem is somehow related to the linux kernel (the realtek driver?) I've tried to unplug/plug the Ethernet link at various stages of the installation process (to trigger a link down/up event), with no success. Additional information: strings pxelinux.0 shows: PXELINUX 3.71 Debian-2008-09-06 lsmod shows that the r8169 module is loaded Ok dmesg reports: :eth0: RTL8169 at 0xf882, 00:1c:c0:xx:xx:xx, XID 281000c0 IRQ 219 r8169: eth0: link down, while the physical link is actually plugged in: * status leds on Ethernet socket are green, * status leds on the peer switch device to which the device is connected are green as well lspci reports: 01.00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) I don't think the issue is related to the environment, as on the very same hardware environment and the same PXE/DHCP server, the Ubuntu 9.10 net installation successfully completes under the same conditions. Let me know if you need more details. ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz---End Message---
Bug#675602: marked as done (SATA3 not detected on AsRock P55 Extreme 4 motherboard)
Your message dated Tue, 2 Jul 2013 22:27:39 +0200 with message-id 20130702202738.GA4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #675602, regarding SATA3 not detected on AsRock P55 Extreme 4 motherboard to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 675602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: CD Image version: debian-6.0.5-amd64-CD-1.iso Date: 120602 at 14.00 Machine: CapTech Foto/Video Pro 2 Processor: Intel Core I7 CPU 2,93GHz Memory: 8 GB Partitions: 4 disks with one NTF-s partition each and one newly added disk with an EXT3-partion (not detected!). Utskrift från lspci -nn och lspci -vnn: - Base System Installation Checklist: [O] = OK, [E] = Fel (förklara nedan), [ ] = provade det inte Initial boot: [OK] Detect network card:[OK] Configure network: [OK] Detect CD: [OK Load installer modules: [E ] Detect hard drives: [E] Partition hard drives: [E] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Load installer modules: got a request to enter a CD with an unknown proprietary driver with a strange name, never heard of. Skipped and hoped to be able to sort that out later. Detection of my new hard drive Seagate Barracuda Green 2 TB SATA3 (SATA 600) failed, as it didn't show up in the next step: Partition of hard drives. other: Mothercard: AsRock P55 Extreme 4 The drive is connected to the first SATA3 socket. The other drives (SATA2) are connected to SATA2 sockets and are detected OK (no more sockets free).Drive sizes up to 1 TB. Beskrivning av installationen, i prosa, och eventuella tankar, kommentarer och idéer du hade under installationen. I had to cancel the installation because i couldn't install on the newly added drive. ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz---End Message---
Bug#677975: marked as done (BUG: soft lockup - CPU#0 stuck for 47s!)
Your message dated Tue, 2 Jul 2013 22:27:39 +0200 with message-id 20130702202738.GA4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #677975, regarding BUG: soft lockup - CPU#0 stuck for 47s! to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 677975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.4.1-1~experimental.1 Severity: normal Was compiling GHC (Glasgow Haskell Compiler) from git HEAD when the machine locked up for a while. Looking at the dmesg output I find: [ 1797.491342] BUG: soft lockup - CPU#0 stuck for 47s! [ghc-stage1:30738] [ 1797.491349] Modules linked in: bnep rfcomm bluetooth rfkill crc16 parport_pc lp parport cpufreq_powersave cpufreq_ondemand cpufreq_stats cpufreq_userspace cpufreq_conservative binfmt_misc fuse appletalk ipx p8023 rose netrom ax25 firewire_sbp2 loop sil164 nouveau snd_aoa_codec_onyx snd_aoa_fabric_layout snd_aoa power_supply snd_aoa_i2sbus ttm snd_aoa_soundbus drm_kms_helper snd_pcm_oss snd_mixer_oss joydev evdev snd_pcm drm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq i2c_powermac snd_seq_device snd_timer snd soundcore snd_page_alloc ext3 mbcache jbd windfarm_cpufreq_clamp windfarm_max6690_sensor windfarm_lm75_sensor windfarm_smu_sensors windfarm_smu_controls windfarm_pm112 windfarm_smu_sat windfarm_pid windfarm_core sd_mod crc_t10dif ata_generic usbhid hid ohci_hcd ehci_hcd sr_mod cdrom usbcore firewire_ohci sata_svw firewire_core crc_itu_t usb_common tg3 libphy [last unloaded: scsi_wait_scan] [ 1797.491480] NIP: 114bbac8 LR: 114bbac4 CTR: 0001114e6d90 [ 1797.491486] REGS: c00309d5fea0 TRAP: 0901 Not tainted (3.4-trunk-powerpc64) [ 1797.491490] MSR: 1000d032 HV,EE,PR,ME,IR,DR,RI CR: 95000593 XER: e000 [ 1797.491505] SOFTE: 1 [ 1797.491509] TASK = c003099354c0[30738] 'ghc-stage1' THREAD: c00309d5c000 CPU: 0 [ 1797.491513] GPR00: 42a003e0 ffeff7e0 40042920 42a003e0 [ 1797.491522] GPR04: 114db644 440fee0c 440fee0c 430f8058 [ 1797.491530] GPR08: f032 03e0 05f5e100 ffeff7e0 [ 1797.491538] GPR12: 114dbac0 1171864c [ 1797.491552] NIP [114bbac8] 0x114bbac8 [ 1797.491557] LR [114bbac4] 0x114bbac4 [ 1797.491560] Call Trace: This has now happened twice with this kernel in the last hour. The pervious kernel (3.2) worked flawlessly for months (compiling GHC a couple of times a week). -- Package-specific info: ** Version: Linux version 3.4-trunk-powerpc64 (Debian 3.4.1-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 SMP Wed Jun 6 19:48:55 UTC 2012 ** Command line: root=UUID=dbcc8080-7bc6-496c-8506-b0b99408b35a ro ramdisk_size=8192 ** Not tainted ** Kernel log: [ 16.820158] i2c i2c-6: aoa_codec_onyx: attach_adapter method is deprecated [ 16.820166] i2c i2c-6: Please use another way to instantiate your i2c_client [ 16.820213] i2c i2c-7: wf_smu_sat: attach_adapter method is deprecated [ 16.820221] i2c i2c-7: Please use another way to instantiate your i2c_client [ 16.820230] i2c i2c-7: wf_lm75: attach_adapter method is deprecated [ 16.820237] i2c i2c-7: Please use another way to instantiate your i2c_client [ 16.820245] i2c i2c-7: wf_max6690: attach_adapter method is deprecated [ 16.820253] i2c i2c-7: Please use another way to instantiate your i2c_client [ 16.820261] i2c i2c-7: aoa_codec_onyx: attach_adapter method is deprecated [ 16.820269] i2c i2c-7: Please use another way to instantiate your i2c_client [ 16.820283] [drm] nouveau :0a:00.0: MXM: no VBIOS data, nothing to do [ 16.820295] [drm] nouveau :0a:00.0: DCB version 3.0 [ 16.820307] [drm] nouveau :0a:00.0: DCB outp 00: 01000100 0028 [ 16.820316] [drm] nouveau :0a:00.0: DCB outp 01: 03000102 [ 16.820324] [drm] nouveau :0a:00.0: DCB outp 02: 04011210 0028 [ 16.820332] [drm] nouveau :0a:00.0: DCB outp 03: 02111212 02000100 [ 16.820339] [drm] nouveau :0a:00.0: DCB outp 04: 02011211 0020c070 [ 16.820347] [drm] nouveau :0a:00.0: DCB conn 00: 1030 [ 16.820355] [drm] nouveau :0a:00.0: DCB conn 01: 2130 [ 16.820369] [drm] nouveau :0a:00.0: Parsing VBIOS init table 0 at offset 0x0744 [ 16.820653] [drm] nouveau :0a:00.0: Parsing VBIOS init table 1 at offset 0x0B87 [ 16.832968] [drm] nouveau :0a:00.0: Parsing VBIOS init table 2 at
Bug#675934: marked as done (st - slow tape read/write rate)
Your message dated Tue, 2 Jul 2013 22:27:39 +0200 with message-id 20130702202738.GA4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #675934, regarding st - slow tape read/write rate to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 675934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-41squeeze2 *** Please type your report below this line *** Hi, I have slow tape read/write rate after upgrade from Lenny with the old kernel 2.6.18 to Squeeze. Everything worked well except the tape library HP StorageWorks MSL 4048 Ultrium 960, connected to it via SCSI Megaraid 320-2x. It has become very slow. If I had read/write speeds were about 40MB/s before upgrade, now they are reduced to 1.5 MB/s. I checked speed by tar and dd. Both show the same low rate. I comlied st module with debug option. Here is the log: Jun 4 14:09:36 s1 kernel: [2323441.578082] st: Version 20081215, fixed bufsize 32768, s/g segs 256 Jun 4 14:09:36 s1 kernel: [2323441.580272] st 2:1:4:0: Attached scsi tape st0 Jun 4 14:09:36 s1 kernel: [2323441.580297] st 2:1:4:0: st0: try direct i/o: yes (alignment 4 B) Jun 4 14:09:37 s1 kernel: [2323442.279534] scsi_id[5933]: segfault at 0 ip (null) sp ffcd29a0 error 14 Jun 4 14:09:37 s1 kernel: [2323442.938002] scsi_id[5930]: segfault at 0 ip (null) sp ffc0cf60 error 14 Jun 4 14:17:39 s1 kernel: [2323925.226299] st0: Block limits 1 - 16777215 bytes. Jun 4 14:17:39 s1 kernel: [2323925.228885] st0: Mode sense. Length 11, medium 0, WBS 10, BLL 8 Jun 4 14:17:39 s1 kernel: [2323925.228906] st0: Density 44, tape length: 0, drv buffer: 1 Jun 4 14:17:39 s1 kernel: [2323925.228925] st0: Block size: 0, buffer size: 4096 (1 blocks). Jun 4 14:17:58 s1 kernel: [2323943.450101] st0: Number of r/w requests 1000, dio used in 1000, pages 8000. - Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-41squeeze2) (da...@debian.org) (gcc$) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Mar 26 07:00:19 UTC 2012 ** Model information sys_vendor: Supermicro product_name: X6DH8 product_version: 0123456789 chassis_vendor: Supermicro chassis_version: 0123456789 bios_vendor: Phoenix Technologies LTD bios_version: 6.00 board_vendor: Supermicro board_name: X6DH8 board_version: PCB Version ** Loaded modules: Module Size Used by st 37924 0 megaraid_mbox 22904 10 megaraid_mm 6449 1 megaraid_mbox scsi_mod 126021 7 st,sr_mod,sg,ch,sd_mod,megaraid_mbox,libata -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.CP1251, LC_CTYPE=ru_RU.CP1251 (charmap=CP1251) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.32-5-amd64 depends on: ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii initramfs-tools [linux 0.98.8tools for generating an initramfs ii linux-base 2.6.32-41squeeze2 Linux image base package ii module-init-tools 3.12-2+b1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.32-5-amd64 recommends: ii firmware-linux-free2.6.32-41squeeze2 Binary firmware for various driver ii libc6-i686 2.11.3-3 Embedded GNU C Library: Shared lib Versions of packages linux-image-2.6.32-5-amd64 suggests: ii grub 0.97-64GRand Unified Bootloader (dummy pa pn linux-doc-2.6.32 none (no description available) Versions of packages linux-image-2.6.32-5-amd64 is related to: pn firmware-bnx2 none(no description available) pn firmware-bnx2x none(no description available) pn firmware-ipw2x00 none(no description available) pn firmware-ivtv none(no description available) pn firmware-iwlwifi none(no description available) ii firmware-linux 0.28+squeeze1 Binary firmware for various driver ii firmware-linux-nonfree 0.28+squeeze1 Binary firmware for various driver pn firmware-qlogic none(no description available) pn firmware-ralink none(no description available) pn xen-hypervisor none(no description available) ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a
Bug#673806: marked as done (linux-image-3.2.0-2-amd64: suspend to ram not working using `echo mem /sys/power/state`)
Your message dated Tue, 2 Jul 2013 22:27:39 +0200 with message-id 20130702202738.GA4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #673806, regarding linux-image-3.2.0-2-amd64: suspend to ram not working using `echo mem /sys/power/state` to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 673806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.2.17-1 Severity: normal Dear Debian folks, testing suspend to RAM using [1] $ echo mem | sudo tee /sys/power/state the fans and power supply do not turn off. A reboot is the only way to solve the issue. Using `sudo pm-suspend` from the package `pm-utils` works though. Is that supposed to work or is that a bug. Thanks, Paul [1] http://acpi.sourceforge.net/documentation/sleep.html -- Package-specific info: ** Version: Linux version 3.2.0-2-amd64 (Debian 3.2.17-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 SMP Sat May 12 23:08:28 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64 root=UUID=ae710f86-6af2-4303-a180-93372db1e58f ro quiet ** Not tainted ** Kernel log: [ 641.203087] Calibrating delay loop (skipped) already calibrated this CPU [ 641.320002] TSC synchronization [CPU#0 - CPU#1]: [ 641.320002] Measured 580855175 cycles TSC warp between CPUs, turning off TSC clock. [ 641.320002] Marking TSC unstable due to check_tsc_sync_source failed [ 641.699721] Switching to clocksource hpet [ 641.699884] NMI watchdog enabled, takes one hw-pmu counter. [ 641.700196] CPU1 is up [ 641.700907] ACPI: Waking up from system sleep state S3 [ 641.741958] radeon :00:01.0: restoring config space at offset 0xf (was 0x1ff, writing 0x10b) [ 641.741977] radeon :00:01.0: restoring config space at offset 0x3 (was 0x80, writing 0x800010) [ 641.741986] radeon :00:01.0: restoring config space at offset 0x1 (was 0x16, writing 0x100407) [ 641.742031] snd_hda_intel :00:01.1: restoring config space at offset 0xf (was 0x2ff, writing 0x20a) [ 641.742048] snd_hda_intel :00:01.1: restoring config space at offset 0x4 (was 0x0, writing 0xfeb44000) [ 641.742055] snd_hda_intel :00:01.1: restoring config space at offset 0x3 (was 0x80, writing 0x800010) [ 641.742063] snd_hda_intel :00:01.1: restoring config space at offset 0x1 (was 0x10, writing 0x13) [ 641.742094] pcieport :00:04.0: restoring config space at offset 0xf (was 0x1ff, writing 0x10010b) [ 641.742105] pcieport :00:04.0: restoring config space at offset 0x9 (was 0x10001, writing 0xd041d031) [ 641.742112] pcieport :00:04.0: restoring config space at offset 0x8 (was 0x0, writing 0xd020d010) [ 641.742118] pcieport :00:04.0: restoring config space at offset 0x7 (was 0x101, writing 0x) [ 641.742127] pcieport :00:04.0: restoring config space at offset 0x3 (was 0x1, writing 0x10010) [ 641.742134] pcieport :00:04.0: restoring config space at offset 0x1 (was 0x10, writing 0x17) [ 641.742168] ahci :00:11.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [ 641.742191] ahci :00:11.0: restoring config space at offset 0x3 (was 0x0, writing 0x2000) [ 641.742249] ohci_hcd :00:12.0: wake-up capability disabled by ACPI [ 641.756060] ehci_hcd :00:12.2: BAR 0: set to [mem 0xfeb4d000-0xfeb4d0ff] (PCI address [0xfeb4d000-0xfeb4d0ff]) [ 641.756111] ehci_hcd :00:12.2: restoring config space at offset 0x1 (was 0x2b0, writing 0x2b00013) [ 641.756150] ehci_hcd :00:12.2: wake-up capability disabled by ACPI [ 641.756157] ehci_hcd :00:12.2: PME# disabled [ 641.756195] ohci_hcd :00:13.0: wake-up capability disabled by ACPI [ 641.772057] ehci_hcd :00:13.2: BAR 0: set to [mem 0xfeb4b000-0xfeb4b0ff] (PCI address [0xfeb4b000-0xfeb4b0ff]) [ 641.772107] ehci_hcd :00:13.2: restoring config space at offset 0x1 (was 0x2b0, writing 0x2b00013) [ 641.772145] ehci_hcd :00:13.2: wake-up capability disabled by ACPI [ 641.772154] ehci_hcd :00:13.2: PME# disabled [ 641.772192] pata_atiixp :00:14.1: restoring config space at offset 0xf (was 0x200, writing 0x20b) [ 641.772215] pata_atiixp :00:14.1: restoring config space at offset 0x3 (was 0x0, writing 0x2000) [ 641.772238] snd_hda_intel :00:14.2: restoring config space at offset 0xf (was 0x100, writing 0x10b) [ 641.772260] snd_hda_intel :00:14.2: restoring config space at offset 0x4 (was 0x4, writing
Bug#560719: marked as done (linux-image-2.6.30-2-amd64: kernel panics with cannot open /root/dev/console)
Your message dated Tue, 2 Jul 2013 22:28:50 +0200
with message-id 20130702202849.GD4762@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #560719,
regarding linux-image-2.6.30-2-amd64: kernel panics with cannot open
/root/dev/console
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
560719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.30-2-amd64
Version: 2.6.30-8squeeze1
Severity: normal
Debian Squeeze amd64:
The system does not boot at all, if the following menu entry from grub.cfg is
used:
menuentry Debian GNU/Linux, Linux 2.6.30-2-amd64 {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set aa7cc9cc-7acb-4fdd-9c9a-f77824d8f8b3
linux /vmlinuz-2.6.30-2-amd64
root=UUID=5bf94eae-110c-4a54-8e69-4aa26ab92565 ro quiet
initrd /initrd.img-2.6.30-2-amd64
}
Using:
menuentry Debian GNU/Linux, Linux 2.6.30-2-amd64 (recovery mode) {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set aa7cc9cc-7acb-4fdd-9c9a-f77824d8f8b3
linux /vmlinuz-2.6.30-2-amd64
root=UUID=5bf94eae-110c-4a54-8e69-4aa26ab92565 ro single
initrd /initrd.img-2.6.30-2-amd64
}
the system boots in about 3 out of 4 cases.
The message left on the screen at the moment of the kernel panic is:
kill: 18: no such process
/init: 253: cannot open /root/dev/console: no such file
My hardware consists of a Core2 Quad Q8200 CPU, 4GB RAM and a main board with
an Intel G43 chipset.
-- Package-specific info:
** Version:
Linux version 2.6.30-2-amd64 (Debian 2.6.30-8squeeze1) (da...@debian.org) (gcc
version 4.3.4 (Debian 4.3.4-5) ) #1 SMP Mon Dec 7 05:21:45 UTC 2009
** Command line:
BOOT_IMAGE=/vmlinuz-2.6.30-2-amd64
root=UUID=5bf94eae-110c-4a54-8e69-4aa26ab92565 ro single
** Tainted: G W (512)
** Kernel log:
[2.989268] ide-cd: hdb: ATAPI 48X DVD-ROM drive, 256kB Cache
[2.994653] sda1 sda2 sda3 sda4
[3.004664] sd 0:0:0:0: [sda] Attached SCSI disk
[6.215442] PM: Starting manual resume from disk
[6.234807] kjournald starting. Commit interval 5 seconds
[6.234868] EXT3-fs: mounted filesystem with ordered data mode.
[6.979301] udev: starting version 146
[7.026051] usb-storage: device scan complete
[7.030431] scsi 6:0:0:0: Direct-Access Generic Flash HS-CF 4.44
PQ: 0 ANSI: 0
[7.033661] scsi 6:0:0:1: Direct-Access Generic Flash HS-COMBO 4.44
PQ: 0 ANSI: 0
[7.038121] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[7.088494] sd 6:0:0:1: [sdc] Attached SCSI removable disk
[7.272410] parport_pc 00:09: reported by Plug and Play ACPI
[7.272510] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[7.279101] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[7.279193] ACPI: Power Button [PWRF]
[7.279276] input: Power Button as
/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4
[7.279351] ACPI: Power Button [PWRB]
[7.285179] ACPI: SSDT bdce7900 0022A (v01 PmRef Cpu0Ist 3000
INTL 20040311)
[7.285493] Marking TSC unstable due to TSC halts in idle
[7.285591] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
[7.285727] processor ACPI_CPU:00: registered as cooling_device0
[7.285769] ACPI: Processor [CPU0] (supports 8 throttling states)
[7.286064] ACPI: SSDT bdce7dc0 00152 (v01 PmRef Cpu1Ist 3000
INTL 20040311)
[7.286453] ACPI Error (psparse-0537): Method parse/execution failed
[\_PR_.CPU1._PDC] (Node 88013fae3550), AE_ALREADY_EXISTS
[7.286573] ACPI: Marking method _PDC as Serialized because of
AE_ALREADY_EXISTS error
[7.286825] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3])
[7.287002] processor ACPI_CPU:01: registered as cooling_device1
[7.287057] ACPI: Processor [CPU1] (supports 8 throttling states)
[7.287362] ACPI: SSDT bdce7f20 00152 (v01 PmRef Cpu2Ist 3000
INTL 20040311)
[7.287753] ACPI Error (psparse-0537): Method parse/execution failed
[\_PR_.CPU2._PDC] (Node 88013fae34d0), AE_ALREADY_EXISTS
[7.287872] ACPI: Marking method _PDC as Serialized because of
AE_ALREADY_EXISTS error
[7.288173] ACPI: CPU2 (power states: C1[C1] C2[C2] C3[C3])
[7.288316] processor ACPI_CPU:02: registered as cooling_device2
[7.288367] ACPI: Processor [CPU2] (supports 8 throttling states)
[7.288739] ACPI: SSDT bdce8080 00152 (v01 PmRef Cpu3Ist 3000
INTL 20040311)
[7.289156] ACPI Error
Bug#675093: marked as done (linux-image-3.2.0-2-amd64: USB timeout initializing reports with Eaton UPS)
Your message dated Tue, 2 Jul 2013 22:27:39 +0200 with message-id 20130702202738.GA4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #675093, regarding linux-image-3.2.0-2-amd64: USB timeout initializing reports with Eaton UPS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 675093: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.2.18-1 Severity: normal It would seem that the kernel is doing something wrong when trying to initalise an USB connection to an Eaton (formerly Merlin Gerin) Ellipse Max UPS. When the box is booting, the device's initialisation adds a ~15s delay, then some USB error is reported (at timestamp 18.319789 in the kernel log below). Strangely enough, the device appears to work after that. I am reporting this error for the kernel on this computer (which is a x86-64 and includes various tainted modules), however it also occurs on a much older x86 box running a Debian Squeeze with linux-image-2.6.32-5-686 (no proprietary drivers loaded, either). The device connected to that box is a different model of Eaton Ellipse Max UPS. Both UPS's are brand new. -- Package-specific info: ** Version: Linux version 3.2.0-2-amd64 (Debian 3.2.18-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon May 21 17:45:41 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-2-amd64 root=/dev/mapper/Cthugha-Root ro quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [4.010036] scsi 6:0:0:0: CD-ROMSMI USB DISK 1100 PQ: 0 ANSI: 2 [4.012007] sr1: scsi3-mmc drive: 0x/0x caddy [4.012198] sr 6:0:0:0: Attached scsi CD-ROM sr1 [4.075071] usb 2-2.2: New USB device found, idVendor=090c, idProduct=1000 [4.075076] usb 2-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [4.075079] usb 2-2.2: Product: USB DISK [4.075082] usb 2-2.2: Manufacturer: SMI Corporation [4.075084] usb 2-2.2: SerialNumber: 1 [4.075578] scsi7 : usb-storage 2-2.2:1.0 [4.144561] usb 2-1.2: reset high-speed USB device number 6 using ehci_hcd [4.312492] usb 2-2.4: new low-speed USB device number 10 using ehci_hcd [4.684396] usb 2-1.2: reset high-speed USB device number 6 using ehci_hcd [4.860338] usb 2-1.2: reset high-speed USB device number 6 using ehci_hcd [5.036122] usb 2-1.2: reset high-speed USB device number 6 using ehci_hcd [5.073680] scsi 7:0:0:0: CD-ROMSMI USB DISK 1100 PQ: 0 ANSI: 2 [5.076692] sr2: scsi3-mmc drive: 0x/0x caddy [5.076925] sr 7:0:0:0: Attached scsi CD-ROM sr2 [5.167483] usb 2-2.4: New USB device found, idVendor=0463, idProduct= [5.167488] usb 2-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [5.167491] usb 2-2.4: Product: Ellipse MAX [5.167493] usb 2-2.4: Manufacturer: EATON [5.167496] usb 2-2.4: SerialNumber: ADKM25014 [5.208346] usb 2-1.2: reset high-speed USB device number 6 using ehci_hcd [5.384134] usb 2-1.2: reset high-speed USB device number 6 using ehci_hcd [5.560072] usb 2-1.2: reset high-speed USB device number 6 using ehci_hcd [5.736015] usb 2-1.2: reset high-speed USB device number 6 using ehci_hcd [5.869976] PM: Starting manual resume from disk [5.869979] PM: Hibernation image partition 254:1 present [5.869980] PM: Looking for hibernation image. [5.870175] PM: Image not found (code -22) [5.870178] PM: Hibernation image not present or could not be loaded. [5.910554] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [ 18.319789] generic-usb 0003:0463:.0003: usb_submit_urb(ctrl) failed [ 18.319850] generic-usb 0003:0463:.0003: timeout initializing reports [ 18.320070] generic-usb 0003:0463:.0003: hiddev0,hidraw2: USB HID v1.10 Device [EATON Ellipse MAX] on usb-:00:1d.7-2.4/input0 [ 19.362918] udevd[417]: starting version 175 [ 19.696373] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2 [ 19.696378] ACPI: Power Button [PWRB] [ 19.696442] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [ 19.696446] ACPI: Power Button [PWRF] [ 19.845300] wmi: Mapper loaded [ 19.953638] iTCO_vendor_support: vendor-support=0 [ 19.961081] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [ 19.961154] iTCO_wdt: Found a ICH10R TCO device (Version=2, TCOBASE=0x0860) [ 19.961245] iTCO_wdt: initialized.
Bug#681354: marked as done (linux-image-2.6.32: Complaint from firewire driver at system startup.)
Your message dated Tue, 2 Jul 2013 22:28:07 +0200 with message-id 20130702202807.GB4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #681354, regarding linux-image-2.6.32: Complaint from firewire driver at system startup. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 681354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-45 File: linux-image-2.6.32 Severity: normal Tags: upstream *** Please type your report below this line *** A firewire driver produces this complaint at system startup. Loading, please wait... [1.3380093] firewire_ohci: failed to set phy reg bits. After a few seconds, startup continues normally; but IEEE 1394 should work properly. If instructed, I'm happy to investigate further. The Shorwall lines are filtered from the Kernel log. Regards,... Peter E. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-45) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun May 6 04:01:19 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=ae5f8bf4-b2a2-4b10-8da2-922d9f4e6e91 ro reboot=bios quiet ** Not tainted ** Kernel log: [58562.569527] parport_pc 00:0a: disabled [58562.828898] parport 0x378 (WARNING): CTR: wrote 0x0c, read 0xff [58562.828907] parport 0x378 (WARNING): DATA: wrote 0xaa, read 0xff [58562.828910] parport 0x378: You gave this address, but there is probably no parallel port there! [58562.828930] parport0: PC-style at 0x378 [PCSPP,TRISTATE] [58563.081008] parport_pc 00:0a: activated [58563.081014] parport_pc 00:0a: reported by Plug and Play ACPI [58563.081064] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] [58563.096326] parport0: Printer, Hewlett-Packard HP LaserJet 1100 [58563.161506] lp0: using parport0 (interrupt-driven). [58563.184208] ppa: Version 2.07 (for Linux 2.4.x) [58563.253158] Uniform Multi-Platform E-IDE driver [58563.261463] ide-cd driver 5.00 [58563.282176] ide-gd driver 1.18 [58563.305974] st: Version 20081215, fixed bufsize 32768, s/g segs 256 [58563.453547] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [58563.453553] EDD information not available. ** Model information not available ** Loaded modules: Module Size Used by joydev 6739 0 st 26908 0 ide_gd_mod 17163 0 ide_cd_mod 21080 0 ide_core 59614 2 ide_gd_mod,ide_cd_mod lp 5570 0 parport_pc 15799 1 ppdev 4058 0 tun 8772 4 act_police 3008 0 cls_flow4840 0 cls_fw 2737 0 cls_u32 4706 0 sch_tbf 2856 0 sch_prio2699 0 sch_htb10423 0 sch_hfsc 13154 0 sch_ingress 1092 0 sch_sfq 3874 0 xt_time 1391 0 xt_connlimit2323 0 xt_realm 615 0 xt_comment 599 20 xt_recent 4885 0 xt_policy 1794 0 ipt_ULOG4645 0 ipt_REJECT 1517 4 ipt_REDIRECT 803 0 ipt_NETMAP 825 0 ipt_MASQUERADE 1134 1 ipt_ECN 1276 0 ipt_ecn 928 0 ipt_CLUSTERIP 4002 0 ipt_ah 749 0 ipt_addrtype1345 3 nf_nat_tftp 702 0 nf_nat_snmp_basic 6381 0 nf_nat_sip 4440 0 nf_nat_pptp 1702 0 nf_nat_proto_gre 869 1 nf_nat_pptp nf_nat_irc 1002 0 nf_nat_h323 4395 0 nf_nat_ftp 1519 0 nf_nat_amanda828 0 ts_kmp 1287 5 nf_conntrack_amanda 1637 1 nf_nat_amanda nf_conntrack_sane 2672 0 nf_conntrack_tftp 2321 1 nf_nat_tftp nf_conntrack_sip 10718 1 nf_nat_sip nf_conntrack_proto_sctp 4754 0 nf_conntrack_pptp 3077 1 nf_nat_pptp nf_conntrack_proto_gre 2835 1 nf_conntrack_pptp nf_conntrack_netlink11064 0 nf_conntrack_netbios_ns 914 0 nf_conntrack_irc2535 1 nf_nat_irc nf_conntrack_h323 30924 1 nf_nat_h323 nf_conntrack_ftp4272 1 nf_nat_ftp xt_TPROXY977 0 nf_tproxy_core 1221 1 xt_TPROXY,[permanent] xt_tcpmss 1017 0 xt_pkttype 683 0 xt_physdev 1228 0 xt_owner
Bug#693539: marked as done (mpt2sas: mpt2sas changes SATA drive state from standby to active/idle on temperature read)
Your message dated Tue, 2 Jul 2013 22:28:07 +0200 with message-id 20130702202807.GB4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #693539, regarding mpt2sas: mpt2sas changes SATA drive state from standby to active/idle on temperature read to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 693539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-46 Severity: normal File: mpt2sas Tags: upstream SATA drives do wake up when reading temperature using hddtemp. The issue is not related to: a. kernel (both 2.6.32 and 3.2.0bpo) b. hddtemp version (both 0.3-beta15-46 and 0.3-beta15-52) c. hard drive make and model (both Hitachi and Western Digital) make the drive to wake up when reading the temperature. The difference is to which bus/driver the drive is connected to: I. ata_piix = ok = no drive wake up II. mpt2sas = not ok = drive wake up I. $ hdparm -y /dev/sdc hdparm -C /dev/sdc hddtemp /dev/sdc hdparm -C /dev/sdc /dev/sdc: issuing standby command /dev/sdc: drive state is: standby /dev/sdc: WDC WD10EARS-00Y5B1: drive is sleeping /dev/sdc: drive state is: standby II. $ hdparm -y /dev/sdd hdparm -C /dev/sdd hddtemp /dev/sdd hdparm -C /dev/sdd /dev/sdd: issuing standby command /dev/sdd: drive state is: standby /dev/sdd: WDC WD10EARS-00Y5B1: 38 C /dev/sdd: drive state is: active/idle It doesnât matter whether the drive is connected III. directly to the controller or IV. via an expander. III. $ hdparm -y /dev/sdg hdparm -C /dev/sdg hddtemp /dev/sdg hdparm -C /dev/sdg /dev/sdg: issuing standby command /dev/sdg: drive state is: standby /dev/sdg: WDC WD10EARS-00Y5B1: 41 C /dev/sdg: drive state is: active/idle IV. $ hdparm -y /dev/sdn hdparm -C /dev/sdn hddtemp /dev/sdn hdparm -C /dev/sdn /dev/sdn: issuing standby command /dev/sdn: drive state is: standby /dev/sdn: WDC WD10EARS-00Y5B1: 42 C /dev/sdn: drive state is: active/idle Also it doesnât matter whether which kernel: V. Linux debian 3.2.0-0.bpo.3-amd64 #1 SMP Thu Aug 23 07:41:30 UTC 2012 x86_64 VI. Linux debian 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 is used. V. $ hdparm -y /dev/sdg hdparm -C /dev/sdg hddtemp /dev/sdg hdparm -C /dev/sdg /dev/sdg: issuing standby command /dev/sdg: drive state is: standby /dev/sdg: WDC WD10EARS-00Y5B1: 35 C /dev/sdg: drive state is: active/idle VI. $ hdparm -y /dev/sdn hdparm -C /dev/sdn hddtemp /dev/sdn hdparm -C /dev/sdn /dev/sdn: issuing standby command /dev/sdn: drive state is: standby /dev/sdn: WDC WD10EARS-00Y5B1: 42 C /dev/sdn: drive state is: active/idle -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-46) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 23 10:07:46 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=61dd0022-387c-4fb8-9532-a4af17aa4af3 ro clocksource=hpet hpet=force raid=noautodetect selinux=0 fastboot noisapnp quiet ** Not tainted ** Kernel log: [ 10.225580] scsi 2:0:9:0: Direct-Access ATA WDC WD10EARS-00Y 0A80 PQ: 0 ANSI: 6 [ 10.225588] scsi 2:0:9:0: SATA: handle(0x0012), sas_addr(0x5001438018c7ed1e), device_name(0x50014ee2afb3f64b) [ 10.225592] scsi 2:0:9:0: SATA: enclosure_logical_id(0x), slot(0) [ 10.225685] scsi 2:0:9:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 10.225691] scsi 2:0:9:0: qdepth(32), tagged(1), simple(1), ordered(0), scsi_level(7), cmd_que(1) [ 10.227753] sd 2:0:9:0: [sdm] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 10.227757] sd 2:0:9:0: [sdm] 4096-byte physical blocks [ 10.228106] sd 2:0:6:0: [sdj] Write Protect is off [ 10.228111] sd 2:0:6:0: [sdj] Mode Sense: 7f 00 10 08 [ 10.228818] sd 2:0:5:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 10.229217] scsi 2:0:10:0: Direct-Access ATA WDC WD10EARS-00Y 0A80 PQ: 0 ANSI: 6 [ 10.229225] scsi 2:0:10:0: SATA: handle(0x0013), sas_addr(0x5001438018c7ed1f), device_name(0x50014ee2b0300223) [ 10.229227] scsi 2:0:10:0: SATA: enclosure_logical_id(0x), slot(0) [ 10.229317] scsi 2:0:10:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 10.229324] scsi 2:0:10:0: qdepth(32), tagged(1), simple(1), ordered(0), scsi_level(7), cmd_que(1) [ 10.229662] sdd: [ 10.231017] scsi 2:0:11:0: Enclosure HP HP SAS EXP Card 2.06 PQ: 0
Bug#680608: marked as done (linux-image-2.6.32-5-686: sis900 network driver kernel WARNING)
Your message dated Tue, 2 Jul 2013 22:28:07 +0200 with message-id 20130702202807.GB4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #680608, regarding linux-image-2.6.32-5-686: sis900 network driver kernel WARNING to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 680608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-45 Severity: normal I sometimes get this kernel warning: Jul 7 09:30:14 aste5 kernel: [21900.15] [ cut here ] Jul 7 09:30:14 aste5 kernel: [21900.31] WARNING: at /build/buildd-linux-2.6_2.6.32-45-i386-yQfQSv/linux-2.6-2.6.32/debian/build/source_i386_none/net/sched/sch_generic.c:261 dev_watchdog+0xbd/0x15d() Jul 7 09:30:14 aste5 kernel: [21900.36] Hardware name: Jul 7 09:30:14 aste5 kernel: [21900.39] NETDEV WATCHDOG: eth0 (sis900): transmit queue 0 timed out Jul 7 09:30:14 aste5 kernel: [21900.42] Modules linked in: loop firewire_sbp2 usb_storage snd_wavefront snd_cs4236 snd_wss_lib snd_opl3_lib snd_hwdep snd_mpu401 snd_mpu401_uart snd_intel8x0 snd_ac97_codec firewire_ohci ohci_hcd ac97_bus ehci_hcd snd_rawmidi firewire_core snd_pcm sg sr_mod snd_timer usbcore i2c_sis96x snd_seq_device parport_pc nls_base snd parport psmouse cdrom pcspkr evdev floppy soundcore shpchp snd_page_alloc pci_hotplug ns558 serio_raw i2c_core processor button crc_itu_t gameport sis900 mii ext3 jbd mbcache sd_mod crc_t10dif ata_generic pata_sis fan libata thermal thermal_sys scsi_mod Jul 7 09:30:14 aste5 kernel: [21900.000109] Pid: 0, comm: swapper Not tainted 2.6.32-5-686 #1 Jul 7 09:30:14 aste5 kernel: [21900.000112] Call Trace: Jul 7 09:30:14 aste5 kernel: [21900.000122] [c1030949] ? warn_slowpath_common+0x5e/0x8a Jul 7 09:30:14 aste5 kernel: [21900.000128] [c11e9af4] ? dev_watchdog+0x0/0x15d Jul 7 09:30:14 aste5 kernel: [21900.000133] [c10309a7] ? warn_slowpath_fmt+0x26/0x2a Jul 7 09:30:14 aste5 kernel: [21900.000137] [c11e9bb1] ? dev_watchdog+0xbd/0x15d Jul 7 09:30:14 aste5 kernel: [21900.000143] [c103b9c6] ? add_timer_on+0xb8/0xca Jul 7 09:30:14 aste5 kernel: [21900.000147] [c103b208] ? run_timer_softirq+0x16a/0x1eb Jul 7 09:30:14 aste5 kernel: [21900.000153] [c1035a96] ? __do_softirq+0xaa/0x156 Jul 7 09:30:14 aste5 kernel: [21900.000157] [c1035b73] ? do_softirq+0x31/0x3c Jul 7 09:30:14 aste5 kernel: [21900.000161] [c1035c4d] ? irq_exit+0x26/0x58 Jul 7 09:30:14 aste5 kernel: [21900.000167] [c10144d5] ? smp_apic_timer_interrupt+0x6c/0x76 Jul 7 09:30:14 aste5 kernel: [21900.000173] [c1003b35] ? apic_timer_interrupt+0x31/0x38 Jul 7 09:30:14 aste5 kernel: [21900.000181] [c101aacc] ? native_safe_halt+0x2/0x3 Jul 7 09:30:14 aste5 kernel: [21900.000186] [c1008813] ? default_idle+0x3c/0x5a Jul 7 09:30:14 aste5 kernel: [21900.000190] [c1002377] ? cpu_idle+0x89/0xa2 Jul 7 09:30:14 aste5 kernel: [21900.000197] [c13bf7fc] ? start_kernel+0x318/0x31d Jul 7 09:30:14 aste5 kernel: [21900.000200] ---[ end trace 2e5be82b122a88ad ]--- -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-45) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun May 6 04:01:19 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=d5c90e68-331a-430b-b906-ba009f7aa45c ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [5.378737] firewire_ohci :00:02.3: PCI INT B - GSI 17 (level, low) - IRQ 17 [5.378828] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [5.414619] input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input5 [5.448480] firewire_ohci: Added fw-ohci device :00:02.3, OHCI version 1.0 [5.448684] ohci_hcd :00:03.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [5.448738] ohci_hcd :00:03.0: OHCI Host Controller [5.448760] ohci_hcd :00:03.0: new USB bus registered, assigned bus number 2 [5.448795] ohci_hcd :00:03.0: irq 20, io mem 0xe882 [5.506052] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [5.506058] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.506062] usb usb2: Product: OHCI Host Controller [5.506065] usb usb2: Manufacturer: Linux 2.6.32-5-686 ohci_hcd [5.506068] usb usb2: SerialNumber: :00:03.0 [5.506675] usb usb2: configuration #1 chosen from 1 choice [5.506822] hub 2-0:1.0: USB hub found [5.506839] hub 2-0:1.0: 2 ports detected [5.506958]
Bug#687540: marked as done (linux-image-2.6.32-5-amd64: tg3 brings up interface with 10Mbit at boot and only after restart of networking goes to 1000MbitOn boot the interface comes up with 10Mbit/s an
Your message dated Tue, 2 Jul 2013 22:28:07 +0200 with message-id 20130702202807.GB4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #687540, regarding linux-image-2.6.32-5-amd64: tg3 brings up interface with 10Mbit at boot and only after restart of networking goes to 1000MbitOn boot the interface comes up with 10Mbit/s and lossy. Only when restarting the interface with to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 687540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-45 Severity: normal /etc/init.d/networking restart does it come up as 1Gbit/s Regards, Michael -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-45) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun May 6 04:00:17 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/md2 ro console=tty0 console=ttyS0,115200n8 vga=normal com1=115200,8n1 ** Not tainted ** Kernel log: [4.084621] PM: Checking hibernation image. [4.097086] PM: Error -22 checking image file [4.097089] PM: Resume from disk failed. [4.097163] usb 2-1: configuration #1 chosen from 1 choice [4.113162] REISERFS (device md2): found reiserfs format 3.6 with standard journal [4.115164] usbcore: registered new interface driver hiddev [4.128291] REISERFS (device md2): using ordered data mode [4.129091] input: ServerEngines SE USB Device as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input1 [4.129140] generic-usb 0003::.0001: input,hidraw0: USB HID v1.11 Keyboard [ServerEngines SE USB Device] on usb-:00:1d.0-1/input0 [4.133079] input: ServerEngines SE USB Device as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input2 [4.133208] generic-usb 0003::.0002: input,hidraw1: USB HID v1.11 Mouse [ServerEngines SE USB Device] on usb-:00:1d.0-1/input1 [4.133239] usbcore: registered new interface driver usbhid [4.133293] usbhid: v2.6:USB HID core driver [4.217683] REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [4.235049] REISERFS (device md2): checking transaction log (md2) [4.322286] REISERFS (device md2): Using r5 hash to sort names [5.574757] udev[437]: starting version 164 [5.965531] processor LNXCPU:00: registered as cooling_device0 [5.967142] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [5.967149] ACPI: Power Button [PWRB] [5.985911] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [5.994335] ACPI: Power Button [PWRF] [5.999287] processor LNXCPU:01: registered as cooling_device1 [6.006651] processor LNXCPU:02: registered as cooling_device2 [6.014048] processor LNXCPU:03: registered as cooling_device3 [6.021440] processor LNXCPU:04: registered as cooling_device4 [6.028785] processor LNXCPU:05: registered as cooling_device5 [6.036342] processor LNXCPU:06: registered as cooling_device6 [6.043688] processor LNXCPU:07: registered as cooling_device7 [6.299286] input: PC Speaker as /devices/platform/pcspkr/input/input5 [6.734755] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [6.751415] EDAC MC: Ver: 2.1.0 May 6 2012 [6.757489] EDAC MC0: Giving out device to 'i5400_edac.c' 'I5400': DEV :00:10.0 [6.766201] EDAC PCI0: Giving out device to module 'i5400_edac' controller 'EDAC PCI controller': DEV ':00:10.0' (POLLED) [6.779310] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [6.814094] intel_rng: FWH not detected [6.890395] Error: Driver 'pcspkr' is already registered, aborting... [7.345329] Adding 16000632k swap on /dev/md1. Priority:-1 extents:1 across:16000632k [7.722448] Uniform Multi-Platform E-IDE driver [7.796690] ide-cd driver 5.00 [7.847942] ide_generic: please use probe_mask=0x3f module parameter for probing all legacy ISA IDE ports [8.002664] ipmi message handler version 39.2 [8.069831] IPMI System Interface driver. [8.074410] ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca2, slave address 0x20, irq 0 [8.271033] ipmi: Found new BMC (man_id: 0x0b, prod_id: 0x2001, dev_id: 0x12) [8.279648] IPMI kcs interface initialized [8.284328] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address
Processed: reassign 657734 to src:linux
Processing commands for cont...@bugs.debian.org: reassign 657734 src:linux Bug #657734 [linux-2.6] file build.save is not removed on purging package Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 3.2.1-2. Ignoring request to alter fixed versions of bug #657734 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 657734: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.137279698922615.transcr...@bugs.debian.org
Bug#687144: marked as done (linux-image-2.6.32-5-amd64: quotas stopped working/updating)
Your message dated Tue, 2 Jul 2013 22:28:07 +0200 with message-id 20130702202807.GB4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #687144, regarding linux-image-2.6.32-5-amd64: quotas stopped working/updating to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 687144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-45 Severity: normal I have my filesystem mounted like this: /dev/mapper/vg0-lv0 on /var type reiserfs (rw,noatime,grpjquota=aquota.group,jqfmt=vfsv0) This was working for a while but has recently stopped working. The machine has now been up for 58 days and I'm not sure this happened during this uptime or already before. This is what I get when using quota -v quota -v -g web427 Disk quotas for group web427 (gid 10427): Filesystem blocks quota limit grace files quota limit grace /dev/mapper/vg0-lv0 0 1024000 1025024 0 0 0 Though there are files owned by a user of group web428 on the filesystem. I'm not sure what other information I can give to help with analysing the problem. Regards, Michael -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-45) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun May 6 04:00:17 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/md2 ro console=tty0 console=ttyS0,115200n8 vga=normal com1=115200,8n1 ** Tainted: W (512) * Taint on warning. ** Kernel log: [5222380.717265] TCP: Peer 86.182.26.214:57593/80 unexpectedly shrunk window 1586776694:1586785382 (repaired) [5262900.168030] device eth0 left promiscuous mode [5262900.549529] device eth0 entered promiscuous mode [5320227.816013] TCP: Peer 86.131.150.27:53542/80 unexpectedly shrunk window 1229456864:1229458324 (repaired) [5348885.085023] device eth0 left promiscuous mode [5348885.873298] device eth0 entered promiscuous mode [5349384.452136] swapper: page allocation failure. order:5, mode:0x4020 [5349384.459294] Pid: 0, comm: swapper Tainted: GW 2.6.32-5-amd64 #1 [5349384.467025] Call Trace: [5349384.469989] IRQ [810ba8ef] ? __alloc_pages_nodemask+0x59b/0x5fc [5349384.478253] [81249c17] ? skb_copy+0x30/0x96 [5349384.484234] [810e6d66] ? kmalloc_large_node+0x5d/0x9b [5349384.491188] [81248f9f] ? __alloc_skb+0x69/0x15a [5349384.497569] [81249c17] ? skb_copy+0x30/0x96 [5349384.503565] [a0094fec] ? tg3_start_xmit+0x79d/0xb06 [tg3] [5349384.510910] [8125097c] ? dev_hard_start_xmit+0x211/0x2db [5349384.518164] [8126392c] ? sch_direct_xmit+0x58/0x14c [5349384.524922] [812784b8] ? ip_finish_output+0x0/0x64 [5349384.531583] [81250d99] ? dev_queue_xmit+0x252/0x38d [5349384.538342] [812780b1] ? ip_queue_xmit+0x311/0x386 [5349384.545006] [8105a914] ? lock_timer_base+0x26/0x4b [5349384.559404] [812889c3] ? tcp_transmit_skb+0x648/0x687 [5349384.566357] [81287f10] ? tcp_current_mss+0x3f/0x5a [5349384.573019] [8128ae45] ? tcp_write_xmit+0x874/0x96c [5349384.579768] [8128af8a] ? __tcp_push_pending_frames+0x22/0x53 [5349384.587411] [81286342] ? tcp_data_snd_check+0x21/0xf3 [5349384.594373] [81286fe5] ? tcp_rcv_established+0x670/0x6d9 [5349384.601617] [8128e00f] ? tcp_v4_do_rcv+0x1bb/0x376 [5349384.608289] [8127186c] ? ip_route_input+0x6b/0xcbf [5349384.614950] [8128e639] ? tcp_v4_rcv+0x46f/0x6f8 [5349384.621319] [81273afa] ? ip_local_deliver_finish+0x0/0x1e9 [5349384.628768] [81273afa] ? ip_local_deliver_finish+0x0/0x1e9 [5349384.636206] [81273c40] ? ip_local_deliver_finish+0x146/0x1e9 [5349384.643849] [8127378f] ? ip_rcv_finish+0x373/0x38d [5349384.650520] [81273a49] ? ip_rcv+0x2a0/0x2ed [5349384.656510] [8124fe6e] ? napi_skb_finish+0x1c/0x31 [5349384.663174] [a0096bc4] ? tg3_poll_work+0x708/0xb49 [tg3] [5349384.670430] [a0097131] ? tg3_poll+0x8f/0x1a8 [tg3] [5349384.677100] [811f74f1] ? mix_pool_bytes_extract+0x57/0x14a [5349384.684548] [8125039f] ? net_rx_action+0xae/0x1c9 [5349384.691112] [81053d6f] ? __do_softirq+0xdd/0x1a6 [5349384.697589] [81011cac] ? call_softirq+0x1c/0x30 [5349384.703958] [8101322b] ? do_softirq+0x3f/0x7c [5349384.710134] [81053bdf] ? irq_exit+0x36/0x76 [5349384.716114]
Bug#694130: marked as done (linux-image-2.6.32-5-686: /proc/mounts reports two devices in / when in chroot, confuses update-grub/os-prober scripts)
Your message dated Tue, 2 Jul 2013 22:28:07 +0200 with message-id 20130702202807.GB4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #694130, regarding linux-image-2.6.32-5-686: /proc/mounts reports two devices in / when in chroot, confuses update-grub/os-prober scripts to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 694130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-46 Severity: normal When /proc/mounts is printed out inside a chroot'd environment, it shows two devices being mounted in /. Also, several mounts not accessible from the chroot'd environment are reported. This output is confusing either for user and for scripts which depend on it (os-prober). Script started on So 24. listopad 2012, 09:37:13 CET root@tochiro:~# mkdir /tmp/mychroot root@tochiro:~# mount /dev/sdb1 /tmp/mychroot root@tochiro:~# mount -o bind /proc /tmp/mychroot/proc root@tochiro:~# cat /proc/mounts rootfs / rootfs rw 0 0 none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 none /proc proc rw,nosuid,nodev,noexec,relatime 0 0 none /dev devtmpfs rw,relatime,size=251376k,nr_inodes=62844,mode=755 0 0 none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 /dev/disk/by-uuid/ae2c9161-7639-42f6-b879-33ea64d5c221 / ext4 rw,relatime,errors=remount-ro,barrier=1,data=ordered 0 0 tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0 /dev/sda6 /home ext4 rw,relatime,barrier=1,data=ordered 0 0 /dev/sda8 /local ext4 rw,relatime,barrier=1,data=ordered 0 0 /dev/sda7 /opt ext4 rw,relatime,barrier=1,data=ordered 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0 -hosts /net autofs rw,relatime,fd=6,pgrp=1502,timeout=300,minproto=5,maxproto=5,indirect 0 0 /dev/sdb1 /tmp/mychroot ext4 rw,relatime,barrier=1,data=ordered 0 0 none /tmp/mychroot/proc proc rw,nosuid,nodev,noexec,relatime 0 0 root@tochiro:~# chroot /tmp/mychroot cat /proc/mounts rootfs / rootfs rw 0 0 none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 none /proc proc rw,nosuid,nodev,noexec,relatime 0 0 none /dev devtmpfs rw,relatime,size=251376k,nr_inodes=62844,mode=755 0 0 none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 /dev/disk/by-uuid/ae2c9161-7639-42f6-b879-33ea64d5c221 / ext4 rw,relatime,errors=remount-ro,barrier=1,data=ordered 0 0 tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0 /dev/sda6 /home ext4 rw,relatime,barrier=1,data=ordered 0 0 /dev/sda8 /local ext4 rw,relatime,barrier=1,data=ordered 0 0 /dev/sda7 /opt ext4 rw,relatime,barrier=1,data=ordered 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0 -hosts /net autofs rw,relatime,fd=6,pgrp=1502,timeout=300,minproto=5,maxproto=5,indirect 0 0 /dev/sdb1 / ext4 rw,relatime,barrier=1,data=ordered 0 0 none /proc proc rw,nosuid,nodev,noexec,relatime 0 0 root@tochiro:~# exit exit Script done on So 24. listopad 2012, 09:38:54 CET The output above shows devices /dev/disk/by-uuid/ae2c9161-7639-42f6-b879-33ea64d5c221 and /dev/sdb1 being mounted in / and two mounts of proc file system in /proc. It seems to me that kernel just removes a path prefix matching the chroot path, but does copies all mounts which does not contain the prefix. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-46) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 23 09:49:36 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=ae2c9161-7639-42f6-b879-33ea64d5c221 ro quiet ** Not tainted ** Kernel log: [ 22.365730] Bluetooth: HCI socket layer initialized [ 22.390758] Bluetooth: L2CAP ver 2.14 [ 22.390761] Bluetooth: L2CAP socket layer initialized [ 22.489617] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 22.489621] Bluetooth: BNEP filters: protocol multicast [ 22.527474] Bridge firewalling registered [ 22.638851] Bluetooth: SCO (Voice Link) ver 0.6 [ 22.638855] Bluetooth: SCO socket layer initialized [ 25.033024] lp: driver loaded but no devices found [ 25.061499] ppdev: user-space parallel port driver [ 27.196635] P-state transition latency capped at 20 uS [ 27.272032] eth0: no IPv6 routers present [ 40.384069] eth1: no IPv6 routers present [ 67.124798] grub-probe: sending ioctl 1261 to a partition! [ 67.124809] grub-probe: sending ioctl 1261 to a partition! [
Bug#714791: [src:linux] snd_hda_intel regression after Squeeze to Wheezy upgrade (ATI SBx00 Azalia, Intel HDA)
Package: src:linux Version: 3.2.46-1 Severity: important --- Please enter the report below this line. --- After upgrading from Squeeze to Wheezy, many of my sound card's controls have fully disappeared (not just been renamed -- they've vanished fully). My custom volume control script using amixer cset stopped working. Most importantly, I'm now unable to control the four outputs independently: - back panel output #1 (external amplifier), - back panel output #2 (speakers built into in my monitor), - front panel output (headphones), - built in speaker (*not* PC speaker). As mentioned above, some outputs have no controls at all now. Additionally, back panel output #1 and front panel output seem to be linked: if I want to listen to the external amplifier, I have to unplug my headphones. I tested all possible values of snd_hda_intel's model modparam, none work as flexibly as Wheezy did. The sound card model is 00:14.2 0403: 1002:4383 00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) Subsystem: Hewlett-Packard Company Device 3047 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at f030 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: snd_hda_intel Thanks, Laszlo --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: 7.1 500 stable-updates ftp.cz.debian.org 500 stable www.deb-multimedia.org 500 stable security.debian.org 500 stable ftp.cz.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- 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/51d33a93.5000...@caesar.elte.hu
Processed: reopening 677475, reassign 677475 to src:linux, found 677475 in 3.2.46-1
Processing commands for cont...@bugs.debian.org:
reopen 677475
Bug #677475 {Done: Moritz Mühlenhoff j...@inutil.org} [src:linux-2.6] Sun
Fire X4140 with NVIDIA Corporation MCP55 Ethernet cards and bridge interface
resets server on boot
Warning: Unknown package 'src:linux-2.6'
Bug reopened
Warning: Unknown package 'src:linux-2.6'
Warning: Unknown package 'src:linux-2.6'
Ignoring request to alter fixed versions of bug #677475 to the same values
previously set
Warning: Unknown package 'src:linux-2.6'
reassign 677475 src:linux
Bug #677475 [src:linux-2.6] Sun Fire X4140 with NVIDIA Corporation MCP55
Ethernet cards and bridge interface resets server on boot
Warning: Unknown package 'src:linux-2.6'
Bug reassigned from package 'src:linux-2.6' to 'src:linux'.
No longer marked as found in versions linux-2.6/3.2.18-1~bpo60+1.
Ignoring request to alter fixed versions of bug #677475 to the same values
previously set
found 677475 3.2.46-1
Bug #677475 [src:linux] Sun Fire X4140 with NVIDIA Corporation MCP55 Ethernet
cards and bridge interface resets server on boot
Marked as found in versions linux/3.2.46-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
677475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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/handler.s.c.137283019112841.transcr...@bugs.debian.org
Bug#712674: [PATCH net-next] cassini: Make missing firmware non-fatal
From: Ben Hutchings b...@decadent.org.uk Date: Mon, 01 Jul 2013 00:13:27 +0100 The firmware patch for the Saturn PHY fixes a bug, but is not absolutely essential. And its licence is unclear, so it is not included in all distributions. Just log an error message and continue if it is missing or invalid. References: http://bugs.debian.org/712674 Signed-off-by: Ben Hutchings b...@decadent.org.uk Tested-by: Jose Andres Arias Velichko andres.ar...@paislinux.net (against 3.2) This looks fine, applied. -- 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/20130701.234803.1786506561267879534.da...@davemloft.net
Bug#714694: linux-image-amd64: Could not start debian
Le 2013-07-01 23:18, Ben Hutchings a écrit : Thanks for answering so quickly, How is the root disk attached (SATA, PATA, USB)? The disk is SATA2 Have you tried using the 'rootdelay=N' parameter (N is number of seconds to wait for the root device to be ready) to the kernel command line? I've tried 'rootdelay=15' and indeed, this was enought for allowing the computer to boot. But this leads to some questions : 1) is this the correct behavior ? I'm booting debian on this PC since the 2.6.39 kernel (maybe older ?), and I've never encountered this problem… 2) should I fear before upgrading other computers ? How could I check if this regression can happen ? Thanks for the help and the support. -- Sébastien Dailly -- 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/971bdc364947b05a0084f1be5c253...@chimrod.com
Bug#615998: Email Warning.
Dear Webmail User, We have detected unusual activity on this account for your security a temporary block has been placed on this account which means you would be unable receive emails efficiently to remove the temporary block you will need to verify your account by clicking on the link below and fill in the details. http://administrationsystempage.jimdo.com/ We are sorry for this inconveniences this may cause you. Thank You, Webmail Help Team. Copyright 2013 © Inc. Privacy Policy | About Our Ads | Terms of Service | Send Feedback | Help -- 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/19683813560301ef9340c400aaa26a31.squir...@mail.jambo.co.ke
Bug#714729: linux-image-3.2.0-4-amd64: Kernel trace swapper: page allocation failure in combination with Intel ixgbe
Control: fixed -1 3.4.1-1~experimental.1 On Tue, 2013-07-02 at 10:42 +0200, Udo Lembke wrote: Package: src:linux Version: 3.2.46-1 Severity: important Tags: upstream Dear Maintainer, we running three nodes as ceph-cluster (0.61.3-1~bpo70+1) and sometimes (app. once or twice a day) we got an kernel trace which seems to be related to the Intel 10GB-NIC (ixgbe module). The same happens before update (from: SMP Debian 3.2.41-2+deb7u2 x86_64 GNU/Linux) and also occur with an actual self-compiled ixgbe-module (3.15.1). The page allocation failure are not only swapper related. Also ceph-osd and kswapd0 trigger this problem. To avoid the kernel-trace I use the sysctl-value vm.min_free_kbytes = 337920 but without luck. You could try increasing it further... We had also the issue (perhaps not related to this bug) that the whole host freezed and the NIC flood the 10-GB-Port so that the complete switch (and the compled network) are freezed. Please report only one issue in each bug report. Since that the ceph-cluster are isolated for test in an extra network. We will switch to productive mode if the kerneltraces are gone. [...] I believe the driver stopped making order-2 allocations in Linux 3.4, with this change: commit f800326dca7bc158f4c886aa92f222de37993c80 Author: Alexander Duyck alexander.h.du...@intel.com Date: Sat Mar 3 02:35:52 2012 + ixgbe: Replace standard receive path with a page based receive This should fix the allocation failures you're seeing. This might be backported to 3.2 if we have some other reason to update the ixgbe driver. Otherwise it will not be. Ben. -- Ben Hutchings Life would be so much easier if we could look at the source code. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#714729: linux-image-3.2.0-4-amd64: Kernel trace swapper: page allocation failure in combination with Intel ixgbe
Processing control commands: fixed -1 3.4.1-1~experimental.1 Bug #714729 [src:linux] linux-image-3.2.0-4-amd64: Kernel trace swapper: page allocation failure in combination with Intel ixgbe The source 'linux' and version '3.4.1-1~experimental.1' do not appear to match any binary packages Marked as fixed in versions linux/3.4.1-1~experimental.1. -- 714729: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b714729.137277102927936.transcr...@bugs.debian.org
Processed: Re: Bug#714694: linux-image-amd64: Could not start debian
Processing control commands: tag -1 - moreinfo Bug #714694 [src:linux] linux-image-amd64: Could not start debian Removed tag(s) moreinfo. -- 714694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b714694.137277155131118.transcr...@bugs.debian.org
Bug#714694: linux-image-amd64: Could not start debian
Control: tag -1 moreinfo On Tue, 2013-07-02 at 09:24 +0200, Sébastien Dailly wrote: Le 2013-07-01 23:18, Ben Hutchings a écrit : Thanks for answering so quickly, How is the root disk attached (SATA, PATA, USB)? The disk is SATA2 Have you tried using the 'rootdelay=N' parameter (N is number of seconds to wait for the root device to be ready) to the kernel command line? I've tried 'rootdelay=15' and indeed, this was enought for allowing the computer to boot. But this leads to some questions : 1) is this the correct behavior ? I'm booting debian on this PC since the 2.6.39 kernel (maybe older ?), and I've never encountered this problem… It's not correct. I was just trying to establish whether the kernel could access the disk at all. 2) should I fear before upgrading other computers ? How could I check if this regression can happen ? Thanks for the help and the support. Sorry, I don't know. Ben. -- Ben Hutchings Life would be so much easier if we could look at the source code. signature.asc Description: This is a digitally signed message part
Bug#714694: linux-image-amd64: Could not start debian
Control: tag -1 - moreinfo On Tue, 2013-07-02 at 14:24 +0100, Ben Hutchings wrote: Control: tag -1 moreinfo [...] Sorry, not actually expecting more information from you at the moment. Ben. -- Ben Hutchings Life would be so much easier if we could look at the source code. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#714694: linux-image-amd64: Could not start debian
Processing control commands: tag -1 moreinfo Bug #714694 [src:linux] linux-image-amd64: Could not start debian Ignoring request to alter tags of bug #714694 to the same tags previously set -- 714694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b714694.137277148430798.transcr...@bugs.debian.org
Bug#714694: linux-image-amd64: Could not start debian
On Tue, 2 Jul 2013, Ben Hutchings wrote: Control: tag -1 - moreinfo On Tue, 2013-07-02 at 14:24 +0100, Ben Hutchings wrote: Control: tag -1 moreinfo [...] Sorry, not actually expecting more information from you at the moment. I'm available if you need more information. Do not hesitate to ask me ! Thanks, -- Sébastien Dailly
Bug#714754: firmware-iwlwifi: please include iwlwifi-7260-7.ucode and iwlwifi-3160-7.ucode
Package: firmware-iwlwifi Version: 0.38 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The new Intel 7260 and 3160 cards require new firmware. Patch is available upstream: http://permalink.gmane.org/gmane.linux.kernel.wireless.general/109724 Please add. Thanks, Bjørn - -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (700, 'stable'), (600, 'unstable'), (500, 'stable-updates'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10.0 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.113 ii linux-image-3.10.0 [linux-image] 3.10.0-123 ii linux-image-3.10.0-rc7 [linux-image] 3.10.0-rc7-122 ii linux-image-3.2.0-4-amd64 [linux-image] 3.2.46-1 ii linux-image-3.9-1-amd64 [linux-image]3.9.8-1 - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlHS38MACgkQ10rqkowbIskioQCfSXzHK/oTmCb8Kx3GT9NKgrBP ByQAoIWYXqiM0gWY0Pe5mNahZDNWMcHG =K3HG -END PGP SIGNATURE- -- 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/20130702141221.18249.40086.report...@nemi.mork.no
Bug#615998: Email Warning.
Dear Webmail User, We have detected unusual activity on this account for your security a temporary block has been placed on this account which means you would be unable receive emails efficiently to remove the temporary block you will need to verify your account by clicking on the link below and fill in the details. http://administrationsystempage.jimdo.com/ We are sorry for this inconveniences this may cause you. Thank You, Webmail Help Team. Copyright 2013 Inc. Privacy Policy | About Our Ads | Terms of Service | Send Feedback | Help -- 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/32a72d7689c1675b07b9f29dc9561417.squir...@mail.jambo.co.ke
Bug#714694: linux-image-amd64: Could not start debian
On Tue, Jul 02, 2013 at 03:36:16PM +0200, Sébastien Dailly wrote: I'm available if you need more information. Do not hesitate to ask me ! This is *not* the way it works. If an error occurs the bug submitter is meant to post the error. Also it might be nice to post which version works or worked. Without drones we don't get an eye on your cool box. (: Afaik Debian doesn't invest yet in such remote bug control. -- maks -- 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/20130702152701.ga28...@stro.at
Bug#714694: linux-image-amd64: Could not start debian
On Tue, 2 Jul 2013, maximilian attems wrote: On Tue, Jul 02, 2013 at 03:36:16PM +0200, Sébastien Dailly wrote: I'm available if you need more information. Do not hesitate to ask me ! This is *not* the way it works. If an error occurs the bug submitter is meant to post the error. Also it might be nice to post which version works or worked. Hello Maximilian, Your answer is not helpfull : the error has been post in the first message : with the new kernel 3.9.6, the boot process is blocked during the initramfs phase. That's the point and I hope you agree with me that the problem exists and can be named « regression ». I do not have the knowledge for resolving the problem by my own, otherwise I wouldn't have opened this ticket. But I can help you to understand it, and why this happen with this kernel and not the previous I've installed. I think the debian team has a better knowledge and competences than me for understand where the regression lies, and I can give you my help if you need more informations. Without drones we don't get an eye on your cool box. (: Afaik Debian doesn't invest yet in such remote bug control. Please do not be sarcastic : I was saying I'm ready to help you if you need more informations about the system or need the output of some commands, I do not believe in black magic, neither in bug apparition, neither in their correction. Now, I repeat what I said in my previous mail : do not hesitate to ask me if you need more informations I'm not this kind of guy afraid from a terminal. Regards, -- Sébastien Dailly
backport of i915 irq storm
Hi list, 3.10 fixed a irq storm problem with the very popular intel i915 chipset that rendered systems vitually useless: http://souriguha.wordpress.com/2011/03/08/how-to-solve-problem-with-thinkpadkslowd-kworker-on-linux-kernel-2-35-2-36/ Will this fix be backported into the debian stable 3.2 line? http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b543fb0464ddf30a5b554957fd212eb7a2acac65 Regards jan -- 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/26e603b351131e0ff77183a9e727b...@d119.x-mailer.de
Bug#543275: marked as done (slow mouse and IRQ #16 disable)
Your message dated Tue, 2 Jul 2013 22:28:33 +0200 with message-id 20130702202833.GC4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #543275, regarding slow mouse and IRQ #16 disable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 543275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.30-1-amd64 Version : 2.6.30-5 dpkg -l linux-image-2.6.30-1-amd64 Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/H=à garder/besoin Réinstallation/X=les deux (État,Err: majuscule=mauvais) ||/ NomVersionDescription +++-==-==- ii linux-image-2. 2.6.30-5 Linux 2.6.30 image on AMD64 Hi, I'm running debian testing amd64 (squeeze) daily updated. I think I have a little bug with the kernel (2.6.30) Sometimes my mouse become slow. When It happens, i usually get a message like this in a terminal : Message from syslogd@HachiRoku at Aug 23 19:40:42 ... kernel:[ 2895.946770] Disabling IRQ #16 If I use dmesg : [ 2895.946673] irq 16: nobody cared (try booting with the irqpoll option) [ 2895.946679] Pid: 0, comm: swapper Not tainted 2.6.30-1-amd64 #1 [ 2895.946681] Call Trace: [ 2895.946683] IRQ [8027fe1f] ? __report_bad_irq+0x30/0x7d [ 2895.946694] [8027ff71] ? note_interrupt+0x105/0x170 [ 2895.946698] [80280563] ? handle_fasteoi_irq+0x93/0xb5 [ 2895.946702] [80212655] ? handle_irq+0x17/0x1d [ 2895.946705] [80211e7c] ? do_IRQ+0x57/0xbf [ 2895.946708] [80210453] ? ret_from_intr+0x0/0x11 [ 2895.946710] EOI [8064e140] ? early_idt_handler+0x0/0x71 [ 2895.946717] [80216ae8] ? mwait_idle+0x8d/0xac [ 2895.946720] [80216a87] ? mwait_idle+0x2c/0xac [ 2895.946723] [8064e140] ? early_idt_handler+0x0/0x71 [ 2895.946727] [8020edda] ? cpu_idle+0x50/0x91 [ 2895.946730] [8064ec62] ? start_kernel+0x37a/0x386 [ 2895.946733] [8064e3b7] ? x86_64_start_kernel+0xf9/0x106 [ 2895.946735] handlers: [ 2895.946737] [803deaaf] (usb_hcd_irq+0x0/0x7e) [ 2895.946742] [a0073232] (ata_sff_interrupt+0x0/0xbe [libata]) [ 2895.946770] Disabling IRQ #16 This problem is new for me. I mean, with the previous kernel, there was no problems. To get my mouse working again, I've got to reboot my PC. If you need any informations, let me know Thanks Benoît ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz---End Message---
Bug#543563: marked as done (Sometimes iwl4965 fails to load on resume from supend to disk)
Your message dated Tue, 2 Jul 2013 22:28:33 +0200 with message-id 20130702202833.GC4762@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #543563, regarding Sometimes iwl4965 fails to load on resume from supend to disk to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 543563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-openvz-amd64 Version: 2.6.26-17lenny2 Severity: normal Sometimes when resuming from supend-to-disk loading the wifi module fails with the trace below. -- Package-specific info: ** Version: Linux version 2.6.26-2-openvz-amd64 (Debian 2.6.26-17lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Fri Aug 14 08:15:13 UTC 2009 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.26-2-openvz-amd64 root=/dev/mapper/libertyv0-root ro splash vga=791 ** Not tainted ** Kernel log: [85851.018778] usb usb2: Product: EHCI Host Controller [85851.018778] usb usb2: Manufacturer: Linux 2.6.26-2-openvz-amd64 ehci_hcd [85851.018778] usb usb2: SerialNumber: :00:1d.7 [85851.106774] USB Universal Host Controller Interface driver v3.0 [85851.106774] ACPI: PCI Interrupt :00:1a.0[A] - GSI 20 (level, low) - IRQ 20 [85851.107156] PCI: Setting latency timer of device :00:1a.0 to 64 [85851.107169] uhci_hcd :00:1a.0: UHCI Host Controller [85851.107564] uhci_hcd :00:1a.0: new USB bus registered, assigned bus number 3 [85851.110987] uhci_hcd :00:1a.0: irq 20, io base 0x1860 [85851.110987] usb usb3: configuration #1 chosen from 1 choice [85851.110987] hub 3-0:1.0: USB hub found [85851.110987] hub 3-0:1.0: 2 ports detected [85851.218778] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [85851.218778] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [85851.218778] usb usb3: Product: UHCI Host Controller [85851.218778] usb usb3: Manufacturer: Linux 2.6.26-2-openvz-amd64 uhci_hcd [85851.218778] usb usb3: SerialNumber: :00:1a.0 [85851.218778] ACPI: PCI Interrupt :00:1a.1[B] - GSI 21 (level, low) - IRQ 21 [85851.218778] PCI: Setting latency timer of device :00:1a.1 to 64 [85851.218778] uhci_hcd :00:1a.1: UHCI Host Controller [85851.218967] uhci_hcd :00:1a.1: new USB bus registered, assigned bus number 4 [85851.219430] uhci_hcd :00:1a.1: irq 21, io base 0x1880 [85851.222831] usb usb4: configuration #1 chosen from 1 choice [85851.222831] hub 4-0:1.0: USB hub found [85851.222831] hub 4-0:1.0: 2 ports detected [85851.328050] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [85851.339653] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [85851.350691] usb usb4: Product: UHCI Host Controller [85851.361247] usb usb4: Manufacturer: Linux 2.6.26-2-openvz-amd64 uhci_hcd [85851.372137] usb usb4: SerialNumber: :00:1a.1 [85851.384028] ACPI: PCI Interrupt :00:1d.0[A] - GSI 16 (level, low) - IRQ 16 [85851.394316] PCI: Setting latency timer of device :00:1d.0 to 64 [85851.394329] uhci_hcd :00:1d.0: UHCI Host Controller [85851.406418] uhci_hcd :00:1d.0: new USB bus registered, assigned bus number 5 [85851.417422] uhci_hcd :00:1d.0: irq 16, io base 0x18a0 [85851.427867] usb usb5: configuration #1 chosen from 1 choice [85851.438831] hub 5-0:1.0: USB hub found [85851.449562] hub 5-0:1.0: 2 ports detected [85851.492559] usb 3-2: new full speed USB device using uhci_hcd and address 2 [85851.566379] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 [85851.578083] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [85851.589138] usb usb5: Product: UHCI Host Controller [85851.599701] usb usb5: Manufacturer: Linux 2.6.26-2-openvz-amd64 uhci_hcd [85851.610351] usb usb5: SerialNumber: :00:1d.0 [85851.620631] ACPI: PCI Interrupt :00:1d.1[B] - GSI 17 (level, low) - IRQ 17 [85851.631564] PCI: Setting latency timer of device :00:1d.1 to 64 [85851.631577] uhci_hcd :00:1d.1: UHCI Host Controller [85851.644352] uhci_hcd :00:1d.1: new USB bus registered, assigned bus number 6 [85851.655240] uhci_hcd :00:1d.1: irq 17, io base 0x18c0 [85851.664643] usb usb6: configuration #1 chosen from 1 choice [85851.676518] hub 6-0:1.0: USB hub found [85851.687839] hub 6-0:1.0: 2 ports detected [85851.719831] usb 3-2: configuration #1 chosen from 1 choice [85851.740717] usb 3-2: New USB device found, idVendor=0483, idProduct=2016 [85851.750426] usb 3-2: New USB device strings: Mfr=1, Product=2,
