Bug#1012578: linux-image-5.18.0-1-amd64: 05e3:0722 Genesys Logic, Inc. SD/MMC card reader doesn't see the card

2022-06-09 Thread Vladimir Stavrinov
Package: src:linux
Version: 5.18.2-1
Severity: normal

Dear Maintainer,

that is card reader itself is being seen by the system:

lsusb -d 05e3:0722
Bus 001 Device 004: ID 05e3:0722 Genesys Logic, Inc. SD/MMC card reader

but it doesn't see the card:

dmesg -T | grep sdc
[Thu Jun  9 15:30:09 2022] sd 7:0:0:0: [sdc] Media removed, stopped polling
[Thu Jun  9 15:30:09 2022] sd 7:0:0:0: [sdc] Attached SCSI removable disk

mount /dev/sdc /mnt/sdcard
mount: /mnt/sdcard: no medium found on /dev/sdc.

I have explored the driver:

modinfo usb-storage | grep -i v05e3p0722

and it looks like there is no support for this device (no output from command
above), but I am not sure it is the case. In any case the system doesn't react
nighter on inserting or removing the card. I have recompiled this module where
supported device 05e3:0723 was replaced by 05e3:0722 without any changes in
system behaviour, though I understand it is not the right method. I have checked
this card on another system (notebook) and it works properly.

Here is additional information that may help:

udevadm info /dev/bus/usb/001/004

P: /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4
M: 1-1.4
R: 4
U: usb
T: usb_device
D: c 189:3
N: bus/usb/001/004
L: 0
V: usb
E: DEVPATH=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4
E: DEVNAME=/dev/bus/usb/001/004
E: DEVTYPE=usb_device
E: DRIVER=usb
E: PRODUCT=5e3/722/9843
E: TYPE=0/0/0
E: BUSNUM=001
E: DEVNUM=004
E: MAJOR=189
E: MINOR=3
E: SUBSYSTEM=usb
E: USEC_INITIALIZED=2168312
E: ID_VENDOR=Generic
E: ID_VENDOR_ENC=Generic
E: ID_VENDOR_ID=05e3
E: ID_MODEL=USB_Storage
E: ID_MODEL_ENC=USB\x20Storage
E: ID_MODEL_ID=0722
E: ID_REVISION=9843
E: ID_SERIAL=Generic_USB_Storage_9843
E: ID_SERIAL_SHORT=9843
E: ID_BUS=usb
E: ID_USB_INTERFACES=:080650:
E: ID_VENDOR_FROM_DATABASE=Genesys Logic, Inc.
E: ID_MODEL_FROM_DATABASE=SD/MMC card reader
E: ID_PATH=pci-:00:1a.0-usb-0:1.4
E: ID_PATH_TAG=pci-_00_1a_0-usb-0_1_4
E: ID_FOR_SEAT=usb-pci-_00_1a_0-usb-0_1_4
E: TAGS=:seat:
E: CURRENT_TAGS=:seat:


udevadm info /dev/sdc

P: 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host7/target7:0:0/7:0:0:0/block/sdc
M: sdc
U: block
T: disk
D: b 8:32
N: sdc
L: 0
S: disk/by-path/pci-:00:1a.0-usb-0:1.4:1.0-scsi-0:0:0:0
S: disk/by-diskseq/16
S: disk/by-id/usb-Generic_STORAGE_DEVICE_9843-0:0
Q: 16
E: 
DEVPATH=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host7/target7:0:0/7:0:0:0/block/sdc
E: DEVNAME=/dev/sdc
E: DEVTYPE=disk
E: DISKSEQ=16
E: MAJOR=8
E: MINOR=32
E: SUBSYSTEM=block
E: USEC_INITIALIZED=3242303
E: ID_VENDOR=Generic
E: ID_VENDOR_ENC=Generic\x20
E: ID_VENDOR_ID=05e3
E: ID_MODEL=STORAGE_DEVICE
E: ID_MODEL_ENC=STORAGE\x20DEVICE\x20\x20
E: ID_MODEL_ID=0722
E: ID_REVISION=9843
E: ID_SERIAL=Generic_STORAGE_DEVICE_9843-0:0
E: ID_SERIAL_SHORT=9843
E: ID_TYPE=disk
E: ID_INSTANCE=0:0
E: ID_BUS=usb
E: ID_USB_INTERFACES=:080650:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usb-storage
E: ID_PATH=pci-:00:1a.0-usb-0:1.4:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=pci-_00_1a_0-usb-0_1_4_1_0-scsi-0_0_0_0
E: UDISKS_PRESENTATION_NOPOLICY=0
E: DEVLINKS=/dev/disk/by-path/pci-:00:1a.0-usb-0:1.4:1.0-scsi-0:0:0:0
/dev/disk/by-diskseq/16
/dev/disk/by-id/usb-Generic_STORAGE_DEVICE_9843-0:0
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

lsusb -D /dev/bus/usb/001/004

Device: ID 05e3:0722 Genesys Logic, Inc. SD/MMC card reader
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize064
  idVendor   0x05e3 Genesys Logic, Inc.
  idProduct  0x0722 SD/MMC card reader
  bcdDevice   98.43
  iManufacturer   3 Generic
  iProduct4 USB Storage
  iSerial 2 9843
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   0x0020
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0x80
  (Bus Powered)
MaxPower  500mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass 8 Mass Storage
  bInterfaceSubClass  6 SCSI
  bInterfaceProtocol 80 Bulk-Only
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType

Bug#604470: linux-image-2.6.32-5-openvz-amd64: degraded inbound network bandwidth

2010-11-23 Thread Vladimir Stavrinov
On Tue, Nov 23, 2010 at 10:44:56AM +0300, Vladimir Stavrinov wrote:

 There is some other strange effect: after some idle time the network in
 the container stop working at all. I see this problem (drop
 connectivity) only on the new created for testing container may be
 because it is idle most of time, while other containers are production
 and are getting activity continuously.

Further investigation show that route to this container in the Hardware
Node was dropped for unknown reason. But it is repeated situation.
Adding it get connectivity back.

-- 

***
  Vladimir Stavrinov  *
 vstavri...@gmail.com  
***




-- 
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/20101123083635.ga5...@magus.playfast.oz



Bug#604470: linux-image-2.6.32-5-openvz-amd64: degraded inbound network bandwidth

2010-11-22 Thread Vladimir Stavrinov
Package: linux-2.6
Version: 2.6.32-27
Severity: normal


For traffic from Internet to Container the bandwidth cut down in 5-10 times
compared to Hardware Nodes. And for connection between two containers on
different Hardware Nodes but in the same Local Network inbound speed slow down
dramatically to 1 times. At the same time outbound bandwidth is close to
Hardware Node one. There are no such problems with kernel I've got from openvz
site:

http://download.openvz.org/kernel/branches/2.6.32/2.6.32-dzhanibekov.1/kernel-2.6.32-dzhanibekov.1.x86_64.rpm

as well as with old Debian kernel linux-image-2.6.26-2-openvz-amd64 thre are no
problem too.


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

** Model information
sys_vendor: HP
product_name: ProLiant DL180 G6  
product_version:  
chassis_vendor: HP
chassis_version:  
bios_vendor: HP
bios_version: O20

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port 
[8086:3406] (rev 13)
Subsystem: Hewlett-Packard Company Device [103c:330b]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit-
Address:   Data: 
Masking:   Pending: 
Capabilities: [90] Express (v2) Root Port (Slot-), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 64ns, 
L1 1us
ExtTag+ RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal+ Fatal+ 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x4, ASPM L0s L1, Latency 
L0 512ns, L1 64us
ClockPM- Surprise+ LLActRep+ BwNot+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ 
DLActive+ BWMgmt- ABWMgmt-
RootCtl: ErrCorrectable- ErrNon-Fatal+ ErrFatal+ PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range BCD, TimeoutDis+ ARIFwd+
DevCtl2: Completion Timeout: 260ms to 900ms, TimeoutDis- ARIFwd-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- 
SpeedDis-, Selectable De-emphasis: -6dB
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB
Capabilities: [e0] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Advanced Error Reporting
UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk:  DLP- SDES+ TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ 
RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
Capabilities: [150 v1] Access Control Services
ACSCap: SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ 
EgressCtrl- DirectTrans-
ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- 
EgressCtrl- DirectTrans-
Capabilities: [160 v0] Vendor Specific Information: ID=0002 Rev=0 
Len=00c ?

00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express 
Root Port 1 [8086:3408] (rev 13) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 256 bytes
Bus: primary=00, secondary=07, subordinate=07, sec-latency=0
I/O behind bridge: e000-efff
Memory behind bridge: fbe0-fbef
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-
BridgeCtl: Parity+ SERR+ NoISA- VGA- MAbort- Reset- FastB2B-

Bug#604470: linux-image-2.6.32-5-openvz-amd64: degraded inbound network bandwidth

2010-11-22 Thread Vladimir Stavrinov
There is some other strange effect: after some idle time the network in
the container stop working at all. I see this problem (drop
connectivity) only on the new created for testing container may be
because it is idle most of time, while other containers are production
and are getting activity continuously.

Here is what You asking for (netstat -s):

Ip:
7298988 total packets received
0 forwarded
0 incoming packets discarded
7262036 incoming packets delivered
4830632 requests sent out
Icmp:
13593 ICMP messages received
2 input ICMP message failed.
ICMP input histogram:
destination unreachable: 357
timeout in transit: 34
redirects: 13106
echo requests: 52
echo replies: 44
949 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
destination unreachable: 719
echo request: 178
echo replies: 52
IcmpMsg:
InType0: 44
InType3: 357
InType5: 13106
InType8: 52
InType11: 34
OutType0: 52
OutType3: 719
OutType8: 178
Tcp:
85940 active connections openings
91936 passive connection openings
303 failed connection attempts
3309 connection resets received
6 connections established
7227101 segments received
4776345 segments send out
32345 segments retransmited
9 bad segments received.
2180 resets sent
Udp:
20616 packets received
726 packets to unknown port received.
0 packet receive errors
20993 packets sent
UdpLite:
TcpExt:
265 invalid SYN cookies received
69 resets received for embryonic SYN_RECV sockets
163 packets pruned from receive queue because of socket buffer overrun
84541 TCP sockets finished time wait in fast timer
26 time wait sockets recycled by time stamp
5 packets rejects in established connections because of timestamp
27496 delayed acks sent
2 delayed acks further delayed because of locked socket
Quick ack mode was activated 8377 times
2255888 packets directly queued to recvmsg prequeue.
1439293771 bytes directly in process context from backlog
3017217537 bytes directly received in process context from prequeue
2255586 packet headers predicted
3511681 packets header predicted and directly queued to user
452075 acknowledgments not containing data payload received
717999 predicted acknowledgments
10 times recovered from packet loss due to fast retransmit
5885 times recovered from packet loss by selective acknowledgements
3 bad SACK blocks received
Detected reordering 10 times using FACK
Detected reordering 5 times using SACK
Detected reordering 3 times using time stamp
4 congestion windows fully recovered without slow start
24 congestion windows partially recovered using Hoe heuristic
181 congestion windows recovered without slow start by DSACK
95 congestion windows recovered without slow start after partial ack
8805 TCP data loss events
TCPLostRetransmit: 495
8 timeouts after reno fast retransmit
1603 timeouts after SACK recovery
1006 timeouts in loss state
14585 fast retransmits
503 forward retransmits
8431 retransmits in slow start
3385 other TCP timeouts
5 classic Reno fast retransmits failed
952 SACK retransmits failed
7885 packets collapsed in receive queue due to low socket buffer
8407 DSACKs sent for old packets
115 DSACKs sent for out of order packets
1623 DSACKs received
29 DSACKs for out of order packets received
27 connections reset due to unexpected data
18 connections reset due to early user close
188 connections aborted due to timeout
TCPDSACKIgnoredOld: 1238
TCPDSACKIgnoredNoUndo: 213
TCPSpuriousRTOs: 49
TCPSackShiftFallback: 49650
IpExt:
InOctets: 495299200
OutOctets: -1995348470
-- 

***
  Vladimir Stavrinov  *
 vstavri...@gmail.com  
***



-- 
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/20101123074456.ga3...@magus.playfast.oz



Bug#562847: closed by maximilian attems m...@debian.org (Bug#519800: fixed in initramfs-tools 0.94)

2010-04-13 Thread Vladimir Stavrinov
On Mon, Apr 12, 2010 at 07:14:24PM +0200, maximilian attems wrote:

 there is nothing wrong with a /boot/initrd.img-version-flavour.bak
 if initramfs creation goes wrong people expect it there.
 won't change that indeed.

According to FHS there are proper places for backup:

/var/backups

and temproary files:

/var/tmp

-- 

*
   Vladimir Stavrinov  **
***   v...@inist.ru   *
*




-- 
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/20100413085227.gb14...@vs.inist.ru



Bug#562847: closed by maximilian attems m...@debian.org (Bug#519800: fixed in initramfs-tools 0.94)

2010-04-12 Thread Vladimir Stavrinov
On Fri, Apr 09, 2010 at 03:42:57PM +0200, maximilian attems wrote:

  suggest move backup out of /boot. This way we can have a number of
  versions of initrd.

 no this is related to /boot space.

Wonderful! The hard logic. Yes, if You have too big /boot then You can
have lot of backup initrd there. But we want keep it small, isn't?.

 it was needed in the past and may still be helpful thus kept as option,
 but it will clutter much less.

It should not be option, it should be main functionality. And all
clutter should go out of /boot.

  Not enough as soon as old image remain in place while new one
  generated. Thus space needed is doubled in any way. It is good idea to
  generate the new image out of /boot and then replace old image with new
  one.

 this is admin error of too small /boot/.

How long You will repeat this absurdity? This will not admin error if
You will not use /boot for backup and temporary files. There are some
other places for this purposes, do You know?

 you context a change that was done for better reliability and
 you miss context of it, read
 https://wiki.ubuntu.com/HardyInitramfsErrorHandling

OK. I see, but there are nothing what I don't already know at least
related to this discussing. That is simple algorithm:

1. You backup old intrd image
2. You create new image as temporary file.
3. You move new image in place of old one.
4. If it fail due to low disk space You move back the old image
   into its' place.

And then You proudly say me that was done for better reliability! But
this is poor reliability. This way You solve only one case, when
system become unbootable: when new image are already overridden by old
one, but there are not enough space for that and You have not neither
new nor old image. But there are other cases when system become
unbootable, for example due to contents of new image itself. This is
common case, when You can not boot with new image, but old one already
overridden, because image was generated few times before system boot.
Please, don't tell me, this is admin error again.

I don't understand, why You don't agree to move backup and temporary
files out of /boot? In this case Your idea of reliability remain in
place: when You can not replace old image with new one due to low disk
space, You will roll back to the old image as You do this now.

-- 

*
   Vladimir Stavrinov  **
***   v...@inist.ru   *
*




-- 
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/20100412094246.gb27...@vs.inist.ru



Bug#562847: closed by maximilian attems m...@debian.org (Bug#519800: fixed in initramfs-tools 0.94)

2010-04-09 Thread Vladimir Stavrinov
On Thu, Apr 08, 2010 at 06:49:17PM +0200, maximilian attems wrote:

 indeed those two are not related, beside beeing closed by the same
 upload. 

There is long list of bug numbers in that message, but this only
included in the subject. It is confusing.

 562847 is closed by
 * update-initramfs: Default to not keep .bak backups.

This is not problem as everyone can turn off backup if need. But this is
bad idea. When You can't boot with new image, You will use backup. I
suggest move backup out of /boot. This way we can have a number of
versions of initrd.

 and thus allowing smaller /boot/

Not enough as soon as old image remain in place while new one 
generated. Thus space needed is doubled in any way. It is good idea to
generate the new image out of /boot and then replace old image with new
one.

 if that doesn't fit your /boot/ then this administration error.

No, as if it fit now, it will not fit in the future as image size rise.

If we agree that /boot should be small in order to comply FHS, then we
should take out from there all files not needed to boot, and don't use
this small space for temporary files.

It look like You don't read my initial bug report.
 
-- 

*
   Vladimir Stavrinov  **
***   v...@inist.ru   *
*




-- 
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/20100409065125.gc27...@vs.inist.ru



Bug#562847: closed by maximilian attems m...@debian.org (Bug#519800: fixed in initramfs-tools 0.94)

2010-04-08 Thread Vladimir Stavrinov
 with increasing
  timeout.
  .
[ Colin Watson ]
* mkinitramfs: Filter out looping or broken symlinks from the
  initramfs. (closes: #575157)
* mkinitramfs: set initramfs root to 755.
  .
[ Bert Schulze ]
* initramfs-tools: support different compression tools in mkinitramfs.
  (closes: #533903)
* mkinitramfs: -c compression support / commandline override.
  (closes: #576429)
 Checksums-Sha1: 
  5afd5d57aa19a5c0209eaecc9b1b1f9465753318 922 initramfs-tools_0.94.dsc
  509fb16736997ecba36f641127ceab5bea18f68d 71586 initramfs-tools_0.94.tar.gz
  02aca8c6e29acf625100c1551faf1dbc5b4a17d0 78974 initramfs-tools_0.94_all.deb
 Checksums-Sha256: 
  aee9a553dd3844532c464d9f649cbff02928568d037415dc8126bb6591e2b817 922 
 initramfs-tools_0.94.dsc
  25580b8f761e154cfa4efe6d4657b69b8a6403f7097dcfe2d50c2e64cc6f4e9b 71586 
 initramfs-tools_0.94.tar.gz
  a8abc65bdbf74bedb0bb77a8079d34b0b0ef8b41adde923e4748a673af770f3c 78974 
 initramfs-tools_0.94_all.deb
 Files: 
  c1dbcaa6efb98082c45257309ba20312 922 utils optional initramfs-tools_0.94.dsc
  0295a063638ef0e44a38ef9fa3d7f93f 71586 utils optional 
 initramfs-tools_0.94.tar.gz
  c66b55ac5c3d7e19cb57057489defa1d 78974 utils optional 
 initramfs-tools_0.94_all.deb
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (GNU/Linux)
 
 iEYEARECAAYFAku6RlIACgkQeW7Lc5tEHqh9MgCaAwfEx8qpBHws+lusrsXjVDTP
 OTMAmwU4vowqNyQHgtoTdNywtdHts2q5
 =MCMB
 -END PGP SIGNATURE-
 
 
 

Received: (at submit) by bugs.debian.org; 28 Dec 2009 14:02:35 +
X-Spam-Checker-Version: SpamAssassin 3.2.3-bugs.debian.org_2005_01_02
(2007-08-08) on rietz.debian.org
X-Spam-Level: 
X-Spam-Bayes: score:0. Tokens: new, 34; hammy, 151; neutral, 307; spammy,
0. spammytokens: hammytokens:0.000-+--H*M:reportbug, 
0.000-+--H*MI:reportbug,
0.000-+--H*x:reportbug, 0.000-+--H*UA:reportbug, 0.000-+--Severity
X-Spam-Status: No, score=-7.4 required=4.0 tests=AWL,BAYES_00,FOURLA,
HAS_PACKAGE,IMPRONONCABLE_1,IMPRONONCABLE_2,MURPHY_DRUGS_REL8,
MURPHY_WRONG_WORD2,PHONENUMBER,SPF_PASS,XMAILER_REPORTBUG autolearn=ham
version=3.2.3-bugs.debian.org_2005_01_02
Return-path: v...@inist.ru
Received: from ftp.inist.ru ([195.54.209.147] helo=vs.inist.ru)
by rietz.debian.org with esmtp (Exim 4.63)
(envelope-from v...@inist.ru)
id 1NPGB8-0007ni-U6
for sub...@bugs.debian.org; Mon, 28 Dec 2009 14:02:35 +
Received: from vs by vs.inist.ru with local (Exim 4.71)
(envelope-from v...@inist.ru)
id 1NPGB5-0004qS-G3; Mon, 28 Dec 2009 17:02:31 +0300
Content-Type: multipart/mixed; boundary1994949000==
MIME-Version: 1.0
From: Vladimir Stavrinov v...@inist.ru
To: Debian Bug Tracking System sub...@bugs.debian.org
Subject: gzip: stdout: No space left on device
Message-ID: 20091228140231.16715.57742.report...@vs.inist.ru
X-Mailer: reportbug 4.9
Date: Mon, 28 Dec 2009 17:02:31 +0300
Delivered-To: sub...@bugs.debian.org
 
 Package: initramfs-tools
 Version: 0.93.4
 Severity: wishlist
 Tags: patch
 
 
 I think, at least once You saw the message in subject. It is common
 problem: the /boot directory placed on separate partition that should be
 small. If there are more then one kernel, the disk space will be
 necessarily exhausted, because new kernel version require more disk space
 then old as usual. Turning off backup don't help because the old initrd
 removed after the new one created. To solve this problem the backups should
 be moved to separated directory and may be rotated. The old initrd should be
 moved there or removed before the new one will be created. All this work is
 done by script I have attached there. It is intended to be run before
 update-initramfs, but there are no triggers to do this. Using
 /etc/initramfs-tools/hooks don't help.  Please, add this functionality as
 options in config file.
 
 
 -- Package-specific info:
 -- /proc/cmdline
 BOOT_IMAGE=//vmlinuz-2.6.32-trunk-amd64 
 root=UUID=06779e83-c998-4a4b-bb52-f4bac1ee226a ro vga=795
 
 -- /proc/filesystems
   ext3
   fuseblk
 
 -- lsmod
 Module  Size  Used by
 vboxnetflt  9898  0 
 vboxnetadp  4177  0 
 vboxdrv  1709830  2 vboxnetflt,vboxnetadp
 i915  246815  1 
 drm_kms_helper 18771  1 i915
 drm   136351  3 i915,drm_kms_helper
 i2c_algo_bit4225  1 i915
 video  17333  1 i915
 output  1692  1 video
 ppdev   5030  0 
 lp  7462  0 
 kvm_intel  37600  0 
 kvm   210696  1 kvm_intel
 autofs420533  2 
 fuse   49662  1 
 tun10732  3 
 bridge 39310  0 
 stp 1440  1 bridge
 coretemp4165  0 
 snd_hda_codec_idt  42257  1 
 snd_hda_intel  17851  0 
 snd_hda_codec  52580  2 snd_hda_codec_idt,snd_hda_intel
 snd_hwdep

Bug#557068: kernel crash

2010-02-26 Thread Vladimir Stavrinov
On Thu, Feb 25, 2010 at 11:10:12PM +0100, Moritz Muehlenhoff wrote:

 The next release of Debian (6.0, code name Squeeze) will be based
 on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell

This machine was running with 2.6.32-trunk-686 kernel since it was
released (few months ago) without any problems. Yesterday it was booted
with 2.6.32-2-686. Second day - the flight is normal.

-- 

*
   Vladimir Stavrinov  **
***   v...@inist.ru   *
*




-- 
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/20100226091549.ga3...@vs.inist.ru



Bug#562847: gzip: stdout: No space left on device

2009-12-28 Thread Vladimir Stavrinov
Package: initramfs-tools
Version: 0.93.4
Severity: wishlist
Tags: patch


I think, at least once You saw the message in subject. It is common
problem: the /boot directory placed on separate partition that should be
small. If there are more then one kernel, the disk space will be
necessarily exhausted, because new kernel version require more disk space
then old as usual. Turning off backup don't help because the old initrd
removed after the new one created. To solve this problem the backups should
be moved to separated directory and may be rotated. The old initrd should be
moved there or removed before the new one will be created. All this work is
done by script I have attached there. It is intended to be run before
update-initramfs, but there are no triggers to do this. Using
/etc/initramfs-tools/hooks don't help.  Please, add this functionality as
options in config file.


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=//vmlinuz-2.6.32-trunk-amd64 
root=UUID=06779e83-c998-4a4b-bb52-f4bac1ee226a ro vga=795

-- /proc/filesystems
ext3
fuseblk

-- lsmod
Module  Size  Used by
vboxnetflt  9898  0 
vboxnetadp  4177  0 
vboxdrv  1709830  2 vboxnetflt,vboxnetadp
i915  246815  1 
drm_kms_helper 18771  1 i915
drm   136351  3 i915,drm_kms_helper
i2c_algo_bit4225  1 i915
video  17333  1 i915
output  1692  1 video
ppdev   5030  0 
lp  7462  0 
kvm_intel  37600  0 
kvm   210696  1 kvm_intel
autofs420533  2 
fuse   49662  1 
tun10732  3 
bridge 39310  0 
stp 1440  1 bridge
coretemp4165  0 
snd_hda_codec_idt  42257  1 
snd_hda_intel  17851  0 
snd_hda_codec  52580  2 snd_hda_codec_idt,snd_hda_intel
snd_hwdep   5220  1 snd_hda_codec
snd_pcm_oss32223  0 
snd_mixer_oss  12478  1 snd_pcm_oss
snd_pcm60263  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_timer  15406  1 snd_pcm
i2c_i8017510  0 
evdev   7336  14 
pcspkr  1699  0 
processor  29351  0 
i2c_core   15184  4 i915,drm,i2c_algo_bit,i2c_i801
snd44158  8 
snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
iTCO_wdt7525  0 
parport_pc 18839  1 
parport27666  3 ppdev,lp,parport_pc
soundcore   4582  1 snd
snd_page_alloc  6105  2 snd_hda_intel,snd_pcm
ext3  105843  7 
jbd36621  1 ext3
mbcache 4970  1 ext3
sg 18600  3 
usbhid 31068  0 
sr_mod 12250  0 
hid62649  1 usbhid
cdrom  28615  1 sr_mod
sd_mod 29401  9 
crc_t10dif  1276  1 sd_mod
ata_generic 2983  0 
ahci   31430  10 
pata_marvell2597  0 
firewire_ohci  19324  0 
firewire_core  36288  1 firewire_ohci
crc_itu_t   1307  1 firewire_core
ide_pci_generic 2788  0 
ide_core   76242  1 ide_pci_generic
libata130935  3 ata_generic,ahci,pata_marvell
e1000e109583  0 
uhci_hcd   18377  0 
ehci_hcd   30322  0 
intel_agp  25441  1 
agpgart24733  3 drm,intel_agp
scsi_mod  121285  4 sg,sr_mod,sd_mod,libata
usbcore   121015  4 usbhid,uhci_hcd,ehci_hcd
nls_base6377  1 usbcore
button  4618  1 i915
thermal11610  0 
fan 3346  0 
thermal_sys11878  4 video,processor,thermal,fan

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

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


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

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/bash

Versions of packages initramfs-tools depends on:
ii  cpio  2.10-1 GNU cpio -- a program to manage ar
ii  findutils 4.4.2-1utilities for finding files--find,
ii  klibc-utils   1.5.15-1   small utilities built with klibc f
ii  module-init-tools 3.11-1 tools 

Bug#562847: Acknowledgement (gzip: stdout: No space left on device)

2009-12-28 Thread Vladimir Stavrinov

Here is new version of backup-initrd script attached.

-- 

*
   Vladimir Stavrinov  **
***   v...@inist.ru   *
*
#!/bin/sh

version=${1:-$(uname -r)}
STORAGE=/var/backups
IMAGE=initrd.img-$version
STATEDIR=/var/lib/initramfs-tools
BOOTDIR=/boot


# Shamelessly ripped from /etc/cron.daily/standard
if cd $STORAGE  [ -s ${BOOTDIR}/$IMAGE ]; then
if ! cmp -s $IMAGE.0 ${BOOTDIR}/$IMAGE ; then
mv -v ${BOOTDIR}/$IMAGE $IMAGE
savelog -l $IMAGE  /dev/null
else
rm -v ${BOOTDIR}/$IMAGE
fi
touch ${BOOTDIR}/$IMAGE
sha1sum ${BOOTDIR}/$IMAGE  ${STATEDIR}/${version}
fi


Bug#562847: Acknowledgement (gzip: stdout: No space left on device)

2009-12-28 Thread Vladimir Stavrinov
On Mon, Dec 28, 2009 at 05:24:56PM +0300, Vladimir Stavrinov wrote:

 Here is new version of backup-initrd script attached.

Sorry, the new one again.
 


-- 

*
   Vladimir Stavrinov  **
***   v...@inist.ru   *
*
#!/bin/sh

version=${1:-$(uname -r)}
STORAGE=/var/backups
IMAGE=initrd.img-$version
STATEDIR=/var/lib/initramfs-tools
BOOTDIR=/boot


# Shamelessly ripped from /etc/cron.daily/standard
if cd $STORAGE  [ -s ${BOOTDIR}/$IMAGE ]; then
if ! cmp -s $IMAGE.0 ${BOOTDIR}/$IMAGE ; then
mv -v ${BOOTDIR}/$IMAGE $IMAGE
savelog -l $IMAGE  /dev/null
else
rm -v ${BOOTDIR}/$IMAGE
fi
fi
touch ${BOOTDIR}/$IMAGE
sha1sum ${BOOTDIR}/$IMAGE  ${STATEDIR}/${version}


Bug#539399: cifs crash with 2.6.30

2009-11-20 Thread Vladimir Stavrinov
This bug is fixed now.
I have tested the patch for kernel 2.6.31:

http://bugzilla.kernel.org/attachment.cgi?id=23847

It is OK. Please include it in new release.

-- 

*
   Vladimir Stavrinov  **
***   v...@inist.ru   *
*




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



Bug#557068: kernel crash

2009-11-19 Thread Vladimir Stavrinov
-1-686 depends on:
ii  debconf [debconf-2.0] 1.5.28 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs
ii  module-init-tools 3.11-1 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.31-1-686 recommends:
ii  firmware-linux-free   2.6.31-2   Binary firmware for various driver
ii  libc6-i6862.10.1-7   GNU C Library: Shared libraries [i

Versions of packages linux-image-2.6.31-1-686 suggests:
ii  grub  0.97-59GRand Unified Bootloader (dummy pa
pn  linux-doc-2.6.31  none (no description available)

Versions of packages linux-image-2.6.31-1-686 is related to:
pn  firmware-bnx2 none (no description available)
pn  firmware-bnx2xnone (no description available)
pn  firmware-ipw2x00  none (no description available)
pn  firmware-ivtv none (no description available)
pn  firmware-iwlwifi  none (no description available)
pn  firmware-linuxnone (no description available)
pn  firmware-linux-nonfreenone (no description available)
pn  firmware-qlogic   none (no description available)
pn  firmware-ralink   none (no description available)

-- debconf information:
  linux-image-2.6.31-1-686/postinst/missing-firmware-2.6.31-1-686:
  linux-image-2.6.31-1-686/postinst/bootloader-error-2.6.31-1-686:
  linux-image-2.6.31-1-686/postinst/bootloader-test-error-2.6.31-1-686:
  linux-image-2.6.31-1-686/postinst/depmod-error-initrd-2.6.31-1-686: false
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.31-1-686/prerm/would-invalidate-boot-loader-2.6.31-1-686: true
  linux-image-2.6.31-1-686/prerm/removing-running-kernel-2.6.31-1-686: true
-- 

*
   Vladimir Stavrinov  **
***   v...@inist.ru   *
*



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



Bug#539399: cifs crash with 2.6.30

2009-11-18 Thread Vladimir Stavrinov
On Wed, Nov 18, 2009 at 02:47:27AM +, Ben Hutchings wrote:

 Please report this upstream http://bugzilla.kernel.org and let us know
 the bug number.
 
I have no account there. What You prevent from doing so Yourself?

-- 

*
   Vladimir Stavrinov  **
***   v...@inist.ru   *
*



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



Bug#539399: cifs crash with 2.6.30

2009-11-17 Thread Vladimir Stavrinov
On Fri, Jul 31, 2009 at 06:55:30PM +0200, Daniel Baumann wrote:

This bug still exists with 2.6.31 too.

-- 

*
   Vladimir Stavrinov  **
***   v...@inist.ru   *
*



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



Bug#544398: linux-image-2.6.30-1-686: skge driver fail

2009-08-31 Thread Vladimir Stavrinov
ii  initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs
ii  module-init-tools 3.10-3 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.30-1-686 recommends:
ii  libc6-i6862.9-25 GNU C Library: Shared libraries [i

Versions of packages linux-image-2.6.30-1-686 suggests:
ii  grub  0.97-56GRand Unified Bootloader (dummy pa
ii  grub-legacy [grub]0.97-56GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.30  none (no description available)

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

-- 

*
   Vladimir Stavrinov  **
***   v...@inist.ru   *
*



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



Bug#539399: live-initramfs: kernel 2.6.30 crash

2009-07-31 Thread Vladimir Stavrinov
On Fri, Jul 31, 2009 at 05:50:13PM +0400, Vladimir Stavrinov wrote:

 picture for 686 and real hardware as well. initrd generated in chrooted
 environment serving as network root filesystem for diskless workstations.

This problem concern with network boot only, while using the same initrd to
boot from other media cause no problem. It is strange.





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



Bug#539399: live-initramfs: kernel 2.6.30 crash

2009-07-31 Thread Vladimir Stavrinov
On Fri, Jul 31, 2009 at 06:55:30PM +0200, Daniel Baumann wrote:

 cifs is crashing, this is not live specifc, reassigning to kernel.

Thanks.

-- 

*
   Vladimir Stavrinov  **
***   v...@inist.ru   *
*




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



Bug#539399: live-initramfs: kernel 2.6.30 crash

2009-07-31 Thread Vladimir Stavrinov
On Fri, Jul 31, 2009 at 08:18:21PM +0200, Daniel Baumann wrote:

 well, on non-network boot, the cifs module is not loaded, so no
 surprise about that :)

Yes, I see. I have sent this mail before received Your reassigning
message about cifs.
 




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



Bug#486834: xserver crash with linux-image-2.6.25-2-686 on startup

2008-12-27 Thread Vladimir Stavrinov
On Sat, Dec 27, 2008 at 05:55:01PM +0100, Moritz Muehlenhoff wrote:

  But still it working with 2.6.24 kernel as well as with previous release of
  2.6.25. There is no way to restore console and system might be rebooted on
  crash. Here is my video system:
 
 The followups indicate that this works with current versions of 
 xserver-xorg-video-intel and the kernel. Can you confirm?


I don't uisng 2.6.25 kernel any more. Nothing to say. With
2.6.26 there are no problems.


**
   Vladimir Stavrinov   **
***   v...@inist.ru   **
*   http://inist.ru/   ***
**




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



Bug#494455: linux-image-2.6.26-1-686: incorrect tuner type for saa7134 module

2008-08-18 Thread Vladimir Stavrinov
On Mon, Aug 18, 2008 at 06:01:54PM +0200, Marcel Tiede wrote:

 Hi Vladmimir,
 
 just saw your Bug report on debians buglist
 (http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=2;bug=494455) and
 would like to ask if you got any response regarding this topic?

No I don't got any response, but with recent kernel upgrade to
2.6.26-2 debian package version, this bug gone away and tv driver work
fine the same way as before. 

-- 

*
   Vladimir Stavrinov  **
***   [EMAIL PROTECTED]   *
*




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



Bug#486834: xserver crash with linux-image-2.6.25-2-686 on startup

2008-06-18 Thread Vladimir Stavrinov
Package: linux-image-2.6.25-2-686
Version: 2.6.25-5
Severity: normal


But still it working with 2.6.24 kernel as well as with previous release of
2.6.25. There is no way to restore console and system might be rebooted on
crash. Here is my video system:

00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE 
Chipset Integrated Graphics Device (rev 03)
kernel module: i915 or i830 (the same result)
xserver-xorg-video-intel  2:2.3.1-1 X.Org X server -- 
Intel i8xx, i9xx display driver

Tail from xorg log on crash:

Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x1ffe0001 getbl_err: 0x0021
ipeir: 0x iphdr: 0x54f6
LP ring tail: 0x0001baa0 head: 0x0001bac4 len: 0x0001f001 start 0x
eir: 0x esr: 0x0010 emr: 0xff7b
instdone: 0xff41 instpm: 0x
memmode: 0x instps: 0x0031
hwstam: 0xfffe ier: 0x0002 imr: 0x053c iir: 0x0080
Ring at virtual 0xaf915000 head 0x1bac4 tail 0x1baa0 count 32759
0001ba44: 03cc2000
0001ba48: 03c4020c
0001ba4c: 03c80210
0001ba50: 0100
0001ba54: 
0001ba58: 0010
0001ba5c: 0200
0001ba60: 54f6
0001ba64: 03cc2000
0001ba68: 03c40210
0001ba6c: 03c80214
0001ba70: 0100
0001ba74: 
0001ba78: 0010
0001ba7c: 0200
0001ba80: 54f6
0001ba84: 03cc2000
0001ba88: 03c40214
0001ba8c: 03c80218
0001ba90: 0100
0001ba94: 
0001ba98: 0010
0001ba9c: 0200
0001baa0: 54f6
0001baa4: 03cc2000
0001baa8: 03900318
0001baac: 0394031c
0001bab0: 0100
0001bab4: 
0001bab8: 0010
0001babc: 0200
0001bac0: 54f6
0001bac4: 03cc2000
Ring end
space: 28 wanted 32
(II) intel(0): [drm] removed 1 reserved context for kernel
(II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xe075b000 at 0xb7a5
(II) intel(0): [drm] Closed DRM master.

Fatal server error:
lockup

(II) AIGLX: Suspending AIGLX clients for VT switch


-- Package-specific info:

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

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.25-2-686 depends on:
ii  debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92b  tools for generating an initramfs
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-25  Yet Another mkInitRD

Versions of packages linux-image-2.6.25-2-686 recommends:
ii  libc6-i6862.7-12 GNU C Library: Shared libraries [i

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



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



Bug#435227: linux-image-2.6.22-1-686: yaird error: unrecognised line in /proc/bus/input/devices: U: Uniq= (fatal)

2007-07-30 Thread Vladimir Stavrinov
Package: linux-image-2.6.22-1-686
Version: 2.6.22-3
Severity: normal


This error from subject appear while upgrading from 2.6.22-2 to 2.6.22-3
and never seen before. As result, initrd does not generated. It is occur
on ones machines, but there are no such errors on others. I can't guess,
what is differ. If you think this is yaird bug, please forward this
report there. But if so, why it does not occur before?

-- Package-specific info:
** Version:
Linux version 2.6.22-1-686 (Debian 2.6.22-2) ([EMAIL PROTECTED]) (gcc version 
4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Mon Jul 23 13:23:02 UTC 
2007

** Tainted: PFSRMB

** Kernel log:
lo: Disabled Privacy Extensions
eth0: no IPv6 routers present
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (4031 buckets, 32248 max)
NET: Registered protocol family 4
pnp: Device 00:0a disabled.
vmmon: module license 'unspecified' taints kernel.
/dev/vmmon[4376]: VMCI: Driver initialized.
/dev/vmmon[4376]: Module vmmon: registered with major=10 minor=165
/dev/vmmon[4376]: Module vmmon: initialized
/dev/vmmon[4381]: Module vmmon: unloaded
/dev/vmmon[4690]: VMCI: Driver initialized.
/dev/vmmon[4690]: Module vmmon: registered with major=10 minor=165
/dev/vmmon[4690]: Module vmmon: initialized
pnp: Device 00:0a activated.
parport_pc 00:0a: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
/dev/vmnet: open called by PID 4718 (vmnet-bridge)
/dev/vmnet: hub 0 does not exist, allocating memory.
/dev/vmnet: port on hub 0 successfully opened
bridge-eth0: enabling the bridge
bridge-eth0: up
bridge-eth0: already up
bridge-eth0: attached
/dev/vmmon[4734]: Module vmmon: unloaded
pnp: Device 00:0a disabled.
bridge-eth0: down
bridge-eth0: detached
pnp: Device 00:0a activated.
parport_pc 00:0a: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
pnp: Device 00:0a disabled.
/dev/vmmon[2377]: VMCI: Driver initialized.
/dev/vmmon[2377]: Module vmmon: registered with major=10 minor=165
/dev/vmmon[2377]: Module vmmon: initialized
/dev/vmmon[2382]: Module vmmon: unloaded
/dev/vmmon[2743]: VMCI: Driver initialized.
/dev/vmmon[2743]: Module vmmon: registered with major=10 minor=165
/dev/vmmon[2743]: Module vmmon: initialized
pnp: Device 00:0a activated.
parport_pc 00:0a: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
/dev/vmnet: open called by PID 2775 (vmnet-bridge)
/dev/vmnet: hub 0 does not exist, allocating memory.
/dev/vmnet: port on hub 0 successfully opened
bridge-eth0: enabling the bridge
bridge-eth0: up
bridge-eth0: already up
bridge-eth0: attached
/dev/vmnet: open called by PID 2795 (vmware-vmx)
device eth0 entered promiscuous mode
audit(1185451241.617:2): dev=eth0 prom=256 old_prom=0 auid=4294967295
bridge-eth0: enabled promiscuous mode
/dev/vmnet: port on hub 0 successfully opened
/dev/vmmon[2804]: host clock rate change request 0 - 19
/dev/vmmon[2804]: host clock rate change request 19 - 27
/dev/vmmon[2804]: host clock rate change request 27 - 100
device eth0 left promiscuous mode
audit(1185452515.600:3): dev=eth0 prom=0 old_prom=256 auid=4294967295
bridge-eth0: disabled promiscuous mode
/dev/vmmon[2795]: host clock rate change request 100 - 0
vmmon: Had to deallocate locked 69190 pages from vm driver ce986000
vmmon: Had to deallocate AWE 2953 pages from vm driver ce986000
/dev/vmnet: open called by PID 3761 (vmware-vmx)
device eth0 entered promiscuous mode
audit(1185452735.097:4): dev=eth0 prom=256 old_prom=0 auid=4294967295
bridge-eth0: enabled promiscuous mode
/dev/vmnet: port on hub 0 successfully opened
/dev/vmmon[3779]: host clock rate change request 0 - 19
/dev/vmmon[3779]: host clock rate change request 19 - 27
/dev/vmmon[3779]: host clock rate change request 27 - 100
device eth0 left promiscuous mode
audit(1185453903.582:5): dev=eth0 prom=0 old_prom=256 auid=4294967295
bridge-eth0: disabled promiscuous mode
/dev/vmmon[3761]: host clock rate change request 100 - 0
vmmon: Had to deallocate locked 69188 pages from vm driver cfc0c000
vmmon: Had to deallocate AWE 2168 pages from vm driver cfc0c000
/dev/vmnet: open called by PID 4566 (vmware-vmx)
device eth0 entered promiscuous mode
audit(1185453972.581:6): dev=eth0 prom=256 old_prom=0 auid=4294967295
bridge-eth0: enabled promiscuous mode
/dev/vmnet: port on hub 0 successfully opened
/dev/vmmon[4573]: host clock rate change request 0 - 19
/dev/vmmon[4573]: host clock rate change request 19 - 27
/dev/vmmon[4573]: host clock rate change request 27 - 100
device eth0 left promiscuous mode
audit(1185454539.073:7): dev=eth0 prom=0 old_prom=256 auid=4294967295
bridge-eth0: disabled promiscuous mode
/dev/vmmon[4566]: host clock rate change request 100 - 0
vmmon: Had to deallocate locked 69188 pages from vm driver cfc0c000
vmmon: Had to deallocate AWE 3030 pages from vm driver cfc0c000
CIFS: Unknown mount option codepage
 CIFS VFS: Send error in SessSetup = -13
 CIFS VFS: 

Bug#376488: linux-headers-2.6.17-1-686: unmet dependencies

2006-07-03 Thread Vladimir Stavrinov
Package: linux-headers-2.6.17-1-686
Severity: normal


apt-get install linux-headers-2.6.17-1-686
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  linux-headers-2.6.17-1-686: Depends: linux-kbuild-2.6.17 but it is not 
installable
E: Broken packages

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)


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



Bug#303547: kernel-image-2.6.11-1-686-smp: MEGARAID_NEWGEN wanted

2005-04-07 Thread Vladimir Stavrinov
Package: kernel-image-2.6.11-1-686-smp
Severity: wishlist


Why it is not included? I compiled kernel 2.6.9 and 2.6.10
with this dirtier: 

CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=y
CONFIG_MEGARAID_MAILBOX=y

for LSI Logic / Symbios Logic MegaRAID 520 SCSI 320-1 Controller

It is working on our production Internet server for a half of year
without any problems. Did You plan include this driver into the package?


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)


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